Doximity Scribe

The artifact is wholly model generated, but the competitive asset is not the model. Doximity's moat is a professional network reaching more than 80 percent of United States physicians, built over fifteen years, and Scribe is given away free inside it. Nothing is being sold on model quality, which is the distinguishing feature of this entry: adoption will follow distribution and price rather than performance.

Graded B on the same moat is not the model reasoning applied to Conveyor AI and Chartnote, and deliberately not the C given to EHR bundled products, because Scribe is a product a clinician actively chooses to open rather than a module inside a system they were already required to use.

No review gate, sign off step, confidence threshold, acceptance rate or edit burden figure is described in the located material.

The structural observation from the earlier assessment stands and is worth keeping, because it is the honest description of what actually happens. No record system write back is documented, so the clinician necessarily handles the note before it reaches the chart. That functions as a human gate in the same way it does for the other transfer based products in this category. It is a consequence of the integration gap rather than a designed oversight mechanism, and it will weaken rather than strengthen if write back is added later.

The second pass adds one relevant statement of position. The vendor says notes are private to the individual clinician and frames this as keeping them in control of their own documentation, citing the sanctity of the clinician patient relationship. That is a meaningful architectural choice rather than a slogan: notes belonging to the clinician rather than to an organisation means no administrator, employer or the vendor itself is positioned between the draft and the chart.

It cuts two ways and a buyer should see both. It preserves clinician autonomy and it also means there is no institutional review layer, no quality assurance pass and no organisational visibility of edit burden or error patterns. Where a health system deploys a scribe it usually wants those. Here the product is adopted by individual clinicians rather than procured by institutions, so the oversight that exists is whatever each clinician performs.

Ask for an edit rate, the behaviour on low confidence output, and whether any organisational reporting exists for practices with multiple users.

The workflow is described in stages, live transcription then transcript processing then note generation, but nothing is measured. No accuracy figure, model card, named models or evaluation methodology was located, which is a notable omission for a product distributed at this scale. The beta produced millions of notes across more than 10,000 clinicians, so the data to publish an accuracy or edit burden figure plainly exists.

One half of this axis is answered cleanly and the other is untouched. On whether content reaches third parties, the audio commitment is among the clearest in the category and is stated without hedging: no audio is stored or retained, recordings are processed securely in real time and immediately discarded once the note is generated.

A commitment that raw capture never persists limits what any party in the chain could hold, and it is verifiable in the sense that it is a definite claim rather than a use limitation open to interpretation. The gap in that commitment is specific and worth pressing, because it is drawn around one content type: it covers audio, and no equivalent statement was located on whether generated notes or transcripts are used to train or improve models.

Transcripts and notes are the derived content, they persist by definition since the clinician keeps the note, and they carry the clinical substance. On enumeration there is nothing. No foundation model provider, model class or version is named, no hosting arrangement is published, and no sub processor list was located.

The workflow is described in stages, live transcription then transcript processing then note generation, which tells a buyer the shape of the pipeline without naming anything that runs it. Ask the training question about transcripts and notes specifically rather than about recordings, and ask for a sub processor list.

Adoption at scale is documented, with more than 10,000 clinicians generating millions of notes during a beta that ran over a year, but that measures usage rather than benefit. No study, controlled evaluation, accuracy benchmark, third party rating or published outcome data was located. Graded C on the standing precedent that scale of use does not substitute for evidence of benefit, the same call applied to Infervision, QuantHealth and Oracle Health.

One of the clearest data commitments in this category, stated plainly and without hedging: no audio is stored or retained, recordings are processed securely in real time and immediately discarded once the note is generated, and notes are private to the individual user rather than visible to an employer or organisation. Privacy to the clinician matters here in a way it does not for enterprise products, because a free tool adopted individually sits outside institutional oversight. One gap keeps the record honest rather than the grade: the commitment covers AUDIO, and no equivalent statement was located on whether generated notes or transcripts are used to train models.

The strongest position on this axis in the wave, and it is structural rather than promissory. Doximity states that ALL users are covered by a business associate agreement, which removes the question every other free or self serve product in this category leaves open. Elsewhere here a clinician can begin generating notes on a free tier before any agreement conversation happens; here coverage is automatic and universal. For a product that will be adopted by individual clinicians without procurement involvement, that is the single most important commercial safeguard.

The earlier assessment noted that a certification programme would be expected of a listed company and declined to assume one. It exists. The vendor states that its platforms and data are SOC 2 Type 2 certified, with data encrypted in transit and at rest, and maintains a security page.

SOC 2 Type 2 is the stronger of the two report types, testing whether controls operated effectively across a period rather than whether they were suitably designed at a point in time. Naming Type 2 specifically is worth crediting, since several vendors in this lane assert SOC 2 without ever stating a type.

One formulation in the same sentence should be corrected rather than repeated, and it matters because this vendor's material reaches an unusually large clinical audience. The claim is phrased as being SOC 2 Type 2 and health privacy and health technology statute certified. There is no certification for either statute. They are laws, compliance with them is a self assessment or a contractual position, and no body awards a certificate. The attestation is real; the phrasing attaches the word certified to two things that cannot carry it. A reader could reasonably come away believing three certifications exist where one does.

Two things hold this short of the top grade. The claim sits in a support article rather than a trust centre carrying a dated report, an audit period and a scope statement. And scope is a live question here because the company operates a broad platform of which the scribe is one product, so which systems the report covers is not something a buyer can infer.

Ask for the report, its period, and whether the scribe and its processing path are inside the assessed boundary.

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 scribe is one of the narrower products in this category and that is worth recording as a positive. No coding engine, no risk adjustment scoring, no order generation, no patient facing component and no revenue cycle module were located within it. It transcribes, summarises and produces a note in the clinician's chosen template. The scope expansion pattern documented across most of this lane is absent from this product.

One scoping point belongs alongside it. The same company publishes separate tools on the same platform, including one that answers clinical questions and surfaces drug monograph information. That is clinical reference rather than documentation, and it sits in the territory occupied by dedicated reference products. It is a different product from the scribe and this record assesses the scribe, but a clinician using both experiences them as one environment, and a buyer evaluating the platform should scope them separately.

One consequence of the distribution model deserves noting for completeness rather than as a criticism. Because the tool is adopted directly by individual clinicians rather than procured by institutions, the usual organisational assessment that would sit between a clinical AI product and its use does not occur. No device pathway attaches, so nothing is being circumvented. But the ordinary checkpoint at which a health system would ask about accuracy, oversight and data handling is simply absent from the adoption path, and the responsibility sits wholly with the individual clinician who signs the note.

Markets are United States only, with eligibility limited to verified clinicians.

The absence here carries more weight than for any other vendor in this index, and the second pass makes the reason sharper rather than merely larger.

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

Reach is the first reason. This is a documentation tool distributed free to verified United States clinicians on a platform the company states reaches the large majority of American physicians, following a beta in which thousands of members generated millions of notes. Any performance variation across accent or dialect therefore propagates at national scale rather than within one practice, and it does so without a procurement process anywhere in the path that might have asked the question.

The second reason is where the vendor has chosen to concentrate adoption, and it points directly at the populations the evidence would concern. The company is offering the tool together with free onboarding assistance to free and charitable clinics across the country. Those clinics serve the uninsured and underinsured, and their patient populations include a disproportionate share of people whose first language is not English and whose speech is least likely to be well represented in the data these systems are trained on.

So the deployment most likely to encounter degraded performance is the one being actively promoted, at no cost, to organisations with no capacity to evaluate it. That is a good thing to do with a useful product and it raises the evidentiary obligation rather than lowering it.

Of every vendor in this index this one is among the best placed to publish subgroup performance, and among the most consequential for not doing so.

Two passes located no terms governing the documentation capability, no accuracy or error figure, no published limitations, and no warranty, indemnity or remediation commitment. The absence of a measurement is conspicuous rather than ordinary here, because the data plainly exists: the product reached millions of generated notes across more than ten thousand clinicians in beta, so edit burden and correction rates are things this vendor can compute and has chosen not to publish.

The distribution model creates a recourse problem the enterprise products in this lane do not have, and it deserves stating plainly because it inverts who is exposed. The tool is adopted by individual clinicians at no cost, and notes are private to the user rather than visible to an employer or organisation.

That is a real privacy benefit for the clinician and it means a health system may not know the tool is in use, will have no contract governing it, may have no business associate agreement covering the encounters it processes, and has no way to audit the documentation it produces. The institution still carries the medicolegal and record integrity consequences of notes in its own charts.

So the party with the exposure has no relationship with the vendor, no route to raise a defect and frequently no knowledge that the system exists, which is the harmed party structure this axis tracks, appearing at the institutional level rather than the patient level. Establish whether the tool is in use in your organisation, on what agreement, and what governs the encounters it captures.

The clearest limitation of the product. No integration with any electronic health record was located: the documented ecosystem connections are to Doximity's own products, Dialer for calls and telehealth and Ask for evidence queries, not to record systems. That means the note is generated outside the chart and the clinician moves it, so a free scribe still carries a manual transfer cost per encounter. For an individual clinician that may be an acceptable trade against a competitor charging hundreds a month; for a practice wanting structured data in the record it is disqualifying.

This is the most complete answer to this axis in the ambient scribe category, and it answers the question most vendors here leave entirely open.

The vendor names the third party that processes the encounter. Its support material states plainly that a named commercial model provider supplies the transcription and summarisation technologies powering the scribe, and that a business associate agreement is in place with that provider. Almost nothing else in this lane does both. Several name a provider without stating terms; most say nothing at all and leave a buyer to infer whether encounter content leaves the vendor's environment.

Alongside it the vendor states that no audio is stored or retained, that recordings are processed in real time and discarded once the note is generated, and that data is encrypted in transit and at rest. The no retention position materially reduces what residency would protect, because the audio does not come to rest anywhere.

Three things hold it short of the top grade. No hosting region is stated and no residency option is offered. No full subprocessor list was located, so the named model provider is the one link disclosed rather than the chain. And a business associate agreement constrains a processor's permitted uses without publishing its retention terms, so what that provider holds during and after processing, and for how long, is still unanswered.

Ask for the subprocessor list, the hosting region, and the retention and zero retention configuration on the model provider account. But recognise the starting position: this vendor has already told you who processes the conversation, which is more than most will confirm on request.

There is nothing to disclose because there is nothing to pay, and the eligibility is stated precisely rather than buried: free to all verified United States physicians, nurse practitioners, physician assistants and medical students, with no tiers, no usage caps located, no upsell path and no procurement conversation. Against competitors in this category quoting hundreds of dollars per provider per month, that is a structural price position rather than a discount.

Worth recording alongside it: Doximity provides Scribe, free onboarding assistance and Dialer Pro telemedicine at no cost to free and charitable clinics across the United States, which extends access to settings that generally cannot fund documentation technology at all.

Broad by eligibility rather than by tuning. Available to physicians, nurse practitioners, physician assistants and medical students across all specialties and practice areas, usable at in person visits and through Doximity Dialer for telehealth calls and video. Custom templates and freeform notes are supported. Held at B because no specialty specific models, specialty count or language coverage was located, and availability is United States only.