Scribble by IKS Health

IKS Health is a care enablement services business and Scribble spans both sides of the line: Scribble Now is genuinely AI first, while Transcribe and Live are majority human labour with technology supporting them. Strip the generative layer out and a substantial virtual scribing and transcription business remains, which is the moat is not the model pattern this index applies across the human scribe cluster of Speke, ScribeRyte and iScribeHealth.

Worth recording that the human workforce is also an ASSET to the AI here rather than only a legacy: the vendor states that having scribes on staff enables expert review of the AI output, improving it.

The strongest oversight architecture assessed in this category, and it earns the grade on a design property no competitor offers. Other vendors sell oversight as a tier chosen at contract; Scribble builds an escalation path into the workflow so a clinician can select the level of support per encounter based on complexity, sending a straightforward visit to full automation and a complex or high risk one up the chain without leaving the product.

That matches oversight intensity to clinical risk, which is what this axis is actually asking about. The upper tiers are substantive rather than cosmetic: Scribble Swift puts a trained scribe on hallucination detection, and Scribble Pro escalates to clinician level review with medications, problem lists, orders and other clinical data reconciled explicitly to eliminate hallucinations and misinterpretation. Held short of perfection only by the absence of any published error rate or acceptance figure for the automated tier, which is the number that would tell a buyer when to escalate.

Technology is described only as automated speech recognition plus generative AI, with no accuracy figure, model card, named models or evaluation methodology located. What the vendor does specify precisely is turnaround, with distinct service levels of roughly two minutes, one to two hours and four hours by tier, which is unusual operational disclosure and lets a buyer plan around it. But turnaround measures speed, not correctness, and the accuracy claim rests on the human layers rather than on any published model performance.

Nothing identifies any party in the chain: no model or model family, no foundation model provider, no hosting arrangement and no sub processor list was located in two passes. As with several vendors in this lane the chain includes people, since trained staff read draft documentation containing patient information as a standard part of the tiered service, and that workforce is not enumerated in any respect.

Where it sits, whether review is onshore, how staff are vetted and whether they are employees or contracted are all unstated. One engineered control belongs on the record because it bounds part of that access surface concretely: in the virtual scribing tier, scribes never access video during telehealth encounters.

A restriction implemented in the system rather than promised in a policy is worth more, and it is the sort of control a buyer should ask to have described for every other content type the reviewers can reach. Ask for the list of entities and countries that receive recordings or drafts, what each tier's reviewers can see, and for a sub processor list covering the automated path.

Genuine third party recognition, with one precision that matters. IKS Health was named a 2026 Best in KLAS provider in the virtual scribe category, which is buyer survey based rather than vendor asserted and is the kind of evidence this index has credited before, but the award category is virtual scribing rather than ambient AI, so it validates the services business and the organisation rather than the generative product specifically.

Three 2026 Black Book awards and a named customer executive at a regional physician group add to the picture. No study, controlled evaluation or published accuracy benchmark for the AI tiers was located.

The human review layers create the same exposure this index graded down for Speke and ScribeRyte: trained staff read draft documentation containing PHI, and nothing was located about where that workforce sits or how it is vetted. One specific engineered control deserves credit against that: in the virtual scribing tier, scribes never access video during telehealth encounters, which is a designed restriction on what a human reviewer can see rather than a policy promise. No retention schedule, de identification practice or statement on whether customer content trains models was located.

No product specific business associate agreement posture, template or scope statement was located.

The earlier assessment noted that a buyer should confirm any agreement covers the review workforce and not only the software. The second pass shows why that matters more here than anywhere else in this category, and that the question is not one question but several.

The suite runs five tiers with materially different human involvement. At one end the software processes the encounter with no person at the vendor reading it. At the other, vendor staff work inside the customer's record system with access to pre charting and the clinician's inbox. Between them sit tiers where scribes validate drafts and where clinicians employed by the vendor reconcile medications, problem lists and orders. The business associate relationship therefore has a different shape at every tier, and an agreement scoped to one does not describe another.

That produces a specific diligence instruction rather than a general one. Establish which tier the agreement was written for, whether it names the review workforce as well as the platform, whether workforce members are employees or subcontracted, and whether subcontracting brings further parties into scope. Where staff hold live record access, establish what their permissions reach beyond the encounter, since inbox access exposes correspondence about patients who were never recorded at all.

The encounter to reimbursement integration the vendor markets extends the question again, because coding and revenue cycle functions handled by the same organisation involve the same protected information moving to a different team for a different purpose.

No SOC 2 report of either type, no HITRUST certification, no ISO 27001 and no trust centre were located in a second pass.

One credential the vendor does hold should be named and correctly classified, because it is the kind of item that inflates a compliance list. It has been recognised by a healthcare research firm as a category leader for virtual scribe services. That is a market and customer satisfaction assessment based on provider feedback. It is a meaningful third party signal about service quality and it is not a security examination, which is a different kind of object entirely. Laws, regulators, market rankings and control attestations are four separate things and only the last speaks to this axis.

The absence carries more weight here than for a pure software vendor, for the reason established elsewhere in this lane. This organisation's service model puts its own people inside customer record systems, at some tiers with access extending to pre charting and clinician inboxes. That is a large standing internal access surface, and it is precisely the territory an independent examination covers: how staff are vetted, how access is provisioned and revoked, what a reviewer can see beyond the record in front of them, whether that access is logged, and what happens when a reviewer leaves or a subcontract ends.

Scale compounds it. This is an established enterprise supplier working with large provider organisations, and buyers of that size normally treat an examined posture as a procurement baseline rather than an option.

Ask for the report and its scope, and separately for the access control and monitoring model covering the review workforce.

No clearance claimed and none required for ambient documentation. No United States device pathway attaches.

What governs is payment integrity, and this record carries a version of the coding boundary that differs in kind from the rest of the category. At the reconciliation tier the vendor performs evaluation and management coding itself and describes this as removing the burden of coding from the clinician workflow entirely. The clinician then reviews and signs a note carrying a code selected by someone else, at a different organisation, working from audio rather than from the encounter itself.

That raises an accountability question the ordinary coding suggestion does not. A suggestion leaves the clinician choosing. Coding performed by the vendor leaves the clinician attesting to a choice made elsewhere, and the attestation is what a payer relies on. Establish what the clinician is shown about why a code was selected, and whether they can see the alternative the coder rejected.

The framing around it is one directional in a way this index tracks. The vendor describes the reconciliation tier as reducing the risk of undercoding. Undercoding is named as the risk; overcoding is not mentioned. A service that only ever moves in one direction across a defensible range is not correcting error, it is correcting in one direction, and the accuracy claim should be tested both ways.

The vendor has also integrated the scribe natively across revenue cycle management and coding, describing the result as a connected encounter to reimbursement platform. That is the closed loop from clinical encounter to claim, stated as the product architecture rather than as a consequence.

A published 2025 policy analysis documents ambient scribes producing measurable rises in work relative value units and in documented risk adjusted diagnoses per encounter, and treats whether that reflects better documentation or more intensive coding as unresolved. That question applies here with particular force, because the coding is not merely suggested by software but performed as a service.

Graded up on candour and architecture rather than on a disclosure document.

IKS Health publishes an unusually honest assessment of its own product category, writing that ambient scribe adoption outpaced validation and oversight and introduced risks including hallucinations, data inaccuracies and gaps in contextual nuance. A vendor naming the failure mode of the category it sells into is rare, and the escalation architecture is the design response to it, which makes the criticism structural rather than rhetorical.

Two things hold it at B. No fairness statement, subgroup analysis or accent and dialect performance disclosure was located. And the E&M coding in the top tier is framed partly as reducing the risk of undercoding, which is a revenue direction, though it sits at the mild end of the gradient this index tracks and is paired with clinician reconciliation and audit ready framing.

Two things keep this in the middle band, and both are unusual enough to name. The first is a published service level, with distinct turnaround tiers of roughly two minutes, one to two hours and four hours. That is a real commitment a customer can hold the vendor to and almost nobody in this lane publishes one at all, so it deserves credit even though it commits to speed rather than to correctness, which is the thing this axis actually asks about.

A buyer should read it for what it is: an operational promise about when a note arrives, not a promise about whether it is right. The second is an engineered restriction on the human layer. In the virtual scribing tier, scribes never access video during telehealth encounters, which is a designed limit on what a human reviewer can see rather than a policy assurance, and this index credits structural controls over promised ones consistently. What is absent is everything about output.

No accuracy figure, model card or evaluation methodology was located, and the accuracy case rests on the human review layers rather than on any published model performance, which means the vendor is asking a buyer to trust a process rather than a measurement. No warranty, indemnity or remediation commitment was found. Ask for an accuracy figure for each tier separately, since the automated and human reviewed paths are different products.

Notes are delivered into the record rather than transferred, with direct access to Scribble inside Epic through the Connection Hub, which the vendor positions as reducing IT burden at deployment. The upper tiers go further than text: clinical information is extracted into discrete data fields and mapped to clinician selected diagnoses, and medications, labs, imaging, referrals and follow ups are queued for sign off. Structured extraction rather than narrative delivery is the meaningful distinction. Held at B because Epic is the only named integration path verified in this pass.

No hosting region, residency option or subprocessor list was located, and nothing establishes where inference runs or whether a third party model service processes the audio.

The more important finding is structural, and it reframes what a buyer is choosing. This is not one product but a suite of tiers, and the tiers are marketed on turnaround time: minutes for the fully automated option, about an hour where human scribes validate the draft, four hours where clinician scribes reconcile medications, problem lists and orders, plus a transcription service with human editing and a dedicated virtual scribe service covering pre charting and inbox management.

Turnaround is the visible difference. The consequential difference is who sees the data. At the fastest tier no person at the vendor reads the encounter. At the middle tiers a scribe does. At the reconciliation tier a clinician employed by the vendor works inside the record. At the virtual scribe tier vendor staff have live access to the record including the clinician's inbox, which reaches far beyond the encounter being documented. Selecting a tier is therefore a data access decision presented as a speed decision, and a buyer evaluating turnaround will not necessarily see that.

Workforce location follows directly and is not published. The vendor's own material refers to the longevity of its domestic resources, a phrase that distinguishes them from something else without saying what. For a service where people rather than only systems read patient records, where those people sit is a residency fact in its own right.

One specific control is credited: for telehealth encounters the vendor states its scribes never access video.

Ask which tier is contracted, where its workforce operates, and what those staff can reach inside the record beyond the note.

No published rate card for any of the five tiers. That is a larger gap here than for a single product vendor, because the tiers differ from one another by successive layers of human labour, so the price ladder across Now, Swift and Pro would show what each level of verification costs. Enterprise sold to health systems and physician groups.

Coverage extends across the visit rather than sitting inside it: pre visit chart preparation with prior visit and external record summarisation, live documentation using the clinician's own templates and macros, visit summaries and discharge instructions ready by check out, and referral letters, clearance documents and care coordination afterwards. Telehealth is supported across platforms. Problem based charting is offered as a distinct note structure, which suits complex multi problem patients better than a standard SOAP note. No specialty count or language coverage published.