Medscape Scribe

The artifact is wholly model generated, but the competitive asset is the audience rather than the model. Medscape is a clinical information business whose reach across United States physicians long predates this product, and Scribe is given away inside it. Same reasoning applied to Doximity Scribe: nothing is sold on model quality, so adoption follows distribution and price.

Draft and review, with a named review step rather than an implied one: the product includes a feature called Scribecheck for quick review of generated output before use. Naming and shipping a review affordance is more than most free tools do. Held at B because no acceptance rate, edit burden figure or confidence threshold is published, and because no EHR write back was located, meaning the clinician necessarily handles the note anyway.

No accuracy figure, model card, named models or evaluation methodology located. Capability is described functionally, real time transcription and template based summarisation, with no measurement attached.

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, and nothing states whether content is used to train or improve models. One real commitment exists and it is worth crediting precisely rather than generally: transcripts are automatically deleted after seventy two hours.

A specific published window is rare in this category and it is the kind of statement a buyer can hold a vendor to, which puts it ahead of the vague promises of prompt deletion that are the norm here. It bounds persistence without answering enumeration, and it is drawn around one artefact. The commitment covers transcripts, and nothing was located about audio, which is the more sensitive artefact and the one whose handling most peers address first, nor about the generated note.

So a buyer knows how long one derived text persists and cannot say who processed it, what happened to the recording, or whether either fed a model. Ask for the audio position, the training position, and a sub processor list.

No study, controlled evaluation, accuracy benchmark, third party rating or published adoption figure located. Launch materials describe expected benefits rather than measured ones.

One specific, checkable commitment: transcripts are automatically deleted after 72 hours. A published retention window is rare in this category and it is the kind of statement a buyer can hold a vendor to.

Held at B rather than A because it is the only commitment located. It covers transcripts rather than audio, and nothing was found on whether content is used to train models, which is the disclosure that separates the A grades on this axis.

Described as HIPAA compliant with patient data security emphasised. Business associate agreement terms are not published, and because the tool is free and reached inside an account a clinician already holds, use can begin with no agreement conversation at all, which is the same governance gap this index flags for Doximity Scribe.

No named or dated attestation, no SOC 2 report of either type, no ISO 27001 and no trust centre were located for this product.

The expectation here is raised rather than lowered by the vendor's position. This is not a startup shipping a first product. The scribe sits inside a long established clinical information service operated by a large publicly listed health media company, distributed to a physician audience numbering in the hundreds of thousands. An organisation of that size will already hold security certifications for its wider estate, which makes the question one of scope and publication rather than existence.

That distinction is the useful one for a buyer. Where a parent's programme exists, it describes the parent's platform, and a scribe added to a content and reference service is a materially different processing surface from the one that programme was built around. Serving articles and drug monographs is not the same as recording clinical encounters. Ask which report covers the scribe specifically, whether ambient capture and the summarisation pipeline are inside the assessed boundary, and what period it covers.

The distribution model raises the stakes in the same way it does for the other free scribe reaching a national physician audience. Because the tool is adopted by individual clinicians inside an application they already use, no institutional security review occurs anywhere in the path. Nobody with the expertise to ask these questions is positioned to ask them, which places more weight on the vendor publishing the answers unprompted.

The seventy two hour deletion commitment is a real control and is credited elsewhere. It is a policy the vendor states rather than a control anyone has examined.

No clearance claimed and none required for ambient documentation. No United States device pathway attaches to a note the clinician reviews and moves into the chart themselves.

The product is one of the narrower records in this category and that is worth recording as a positive rather than as an absence. It transcribes the encounter and produces a summary in one of three standard note formats. No coding engine, no risk adjustment scoring, no order generation, no decision support layer and no patient facing component were located within it. The scope expansion pattern documented across most of this lane is not present.

One scoping point belongs alongside it, and it is the same one that applies to the other free scribe distributed through a physician network. The same publisher operates a separate generative product on the same platform that answers clinical questions and returns synthesised responses with links to reference material. That is clinical reference rather than documentation, it occupies different territory, and it is a different product from the scribe. This record assesses the scribe. A clinician moving between the two inside one application will experience them as a single service, so a buyer evaluating the platform should scope them separately and ask about each.

The adoption path is worth noting for completeness. Because the tool reaches clinicians directly inside a service they already use, rather than through institutional procurement, the ordinary checkpoint at which an organisation would assess a clinical AI product does not occur. Nothing is being circumvented, since no pathway attaches, but responsibility rests wholly with the individual clinician who signs the note.

Markets are United States only, restricted to physicians with an account.

No fairness statement, no subgroup analysis, no accuracy breakdown by accent, dialect or speaker population, and no evaluation methodology were located.

The reasoning from the earlier assessment stands and it is the same argument that applies to the other free scribe distributed at national scale. A tool given away inside a service most United States physicians already use will encounter the full range of patient speech, and any performance variation propagates nationally rather than within one practice.

One feature of this particular distribution sharpens it further. The scribe was added to an existing clinical reference and news product rather than sold as a documentation system. A physician opening it is inside an application they already trust for drug information and clinical content, and the scribe inherits that trust without having earned it separately. Trust transfer of that kind is efficient and it is also why the evidentiary obligation should be higher rather than lower: the user is not evaluating a new vendor, they are using another feature of a familiar service.

The absence of any institutional review compounds it. No procurement process sits anywhere in the adoption path, so nobody with the expertise to ask about subgroup performance is positioned to ask.

The question this axis exists to raise remains unanswered by every vendor in this segment, and the two best placed to answer it are the two giving the product away to a national physician audience. Both have the scale to generate the evidence cheaply, and neither publishes it.

Ask for accuracy by accent and dialect, the composition of any evaluation set, and whether performance is monitored after release.

Two passes located no accuracy or error figure, no published limitations, no evaluation methodology and no warranty, indemnity or remediation commitment. Capability is described functionally as real time transcription and template based summarisation with no measurement attached to either, so a buyer has nothing to hold the vendor to and nothing to tell a reviewing clinician where to look.

The distribution route is worth naming because it changes who is exposed rather than only what is disclosed. This product reaches clinicians through a large professional network they already belong to, which means adoption can happen at the individual level without an institutional evaluation, without a procurement exercise and potentially without the employing organisation knowing the tool is in use on its encounters.

That is the same shadow adoption structure recorded elsewhere in this lane, and its consequence is the same: the party carrying the medicolegal and record integrity risk is the organisation whose charts receive the output, and it has no agreement with the vendor and no way to audit what produced the note. Establish whether the tool is in use in your organisation and on what terms, and ask the vendor for an accuracy figure with a definition and for what it commits to when a note is wrong.

No record system integration, write back mechanism or named system was located. The product runs inside the publisher's own mobile application and website, with recording in the app and editing on the website, and the vendor states notes can be integrated into the record system without describing how. On the evidence the clinician moves the note by hand.

That gap collides with the vendor's own retention policy in a way that deserves setting out, because it turns a privacy control into a documentation risk.

Transcripts and summaries are stated to be deleted automatically after seventy two hours. As a stewardship commitment that is genuinely good and rare in this category, and it is credited on the relevant axis. But the deletion is a hard clock, and the only way to get the note out before it fires is manual transfer. A clinician who is away for a long weekend, off sick, or simply behind after a heavy clinic does not lose a convenience. The encounter loses its documentation, and an undocumented encounter is a billing problem, a continuity problem and a medico legal exposure at once.

This is the second shape of the same structural fault in this lane. One peer defines retention by a workflow event, deletion on confirmed transfer, while the integration that would confirm transfer is still a roadmap. Here retention is defined by a clock with no integration to beat it. In both cases the retention commitment and the integration story are load bearing for each other and only one is delivered.

Ask whether any direct integration exists, and what the recovery path is for a note that expired unsent.

No hosting region, residency option, subprocessor list or model provider was located. Delivery is through the publisher's mobile application and website.

One commitment is stated and it is worth crediting properly, because most of this category offers nothing comparable. Transcripts and summaries are deleted automatically after seventy two hours. That is a specific period a buyer can hold the vendor to, published at launch and repeated consistently since, rather than the vague assurance of prompt deletion that is the norm here. It materially reduces what residency would protect, since nothing accumulates.

It is one element rather than an answer. A peer in this lane publishes a stated default period and names the standard used to destroy data at the end of it; another names the model provider processing the encounter and states the agreement in place with them. This record has the period and neither of the others.

So the exposure concentrates in the window and the pipeline, which is where nothing is described. Seventy two hours of transcripts sitting somewhere is a smaller surface than indefinite retention and it is not nothing, and the deletion commitment says what the vendor does rather than what any processor it uses does. If an external speech or language service handles the encounter, that provider's retention is a separate question the seventy two hour figure does not answer.

Also unstated: whether audio is retained at all as distinct from transcripts, which several peers address explicitly and this vendor does not.

Ask for the hosting region, the subprocessor list, the model provider, and whether the seventy two hour clock binds subprocessors.

Free, stated plainly, with eligibility bounded and published: physicians in the United States, reached through an existing Medscape account with no tier, no quote and no procurement step. As with Doximity Scribe, a published zero is the most transparent commercial position available, and its market effect is to remove note generation as a thing anyone can charge a premium for on its own.

Template coverage is stated and slightly unusual in composition: SOAP, history and physical, and the problem oriented medical record. The last is a structure organised by problem rather than by visit, which almost no competitor offers as a standard template and which suits longitudinal care.

Against that, availability is restricted to physicians in the United States, no specialty count or tuning is described, and no language coverage was located.