Knowtex

Founded by AI researchers to build this product and nothing else. Notably the founders spent a year working as human scribes alongside physicians while building it, which is domain grounding rather than model work but explains why the output targets notes, codes and orders together rather than notes alone.

Generates diagnostic and billing codes and orders in real time from the conversation, with the chief executive describing order entry as the natural extension of ambient documentation and the focus of the 2026 roadmap. That places Knowtex on the same side of the split as Oracle Health and Sunoh.ai rather than with the vendors that only suggest, and no confidence threshold, order level accuracy rate, abstention behaviour or review gate description was located.

The reasoning the chief executive gives publicly, that a system accurate enough to generate a note is accurate enough to propose the orders implied by it, is a claim that should be substantiated with an order level accuracy figure rather than asserted by analogy.

No accuracy figure, model card, named models or evaluation methodology located. Specialty specific tailoring is claimed as an architectural property but not described. The competitive federal evaluation noted under evidence implies performance was measured by an external party, which makes the absence of any published performance figure more conspicuous rather than less.

Nothing public names a party, and unusually there is good reason to believe a full enumeration exists in reviewable form, which is what places this above the vendors that simply have nothing. A federal authorisation to operate requires documented system boundaries and a component inventory, and the accompanying privacy assessment addresses permitted use, disclosure and retention directly.

A vendor that has completed that process has answered these questions to a regulator's satisfaction and has published none of the answers, which makes this a disclosure choice rather than an absence of governance, and makes the material very likely obtainable in diligence. What is public is bare: no foundation model provider, model class or version, no hosting arrangement, no sub processor list, and no statement on whether an external model service processes encounters.

The content involved raises the stakes of that silence above the category norm. Veterans' records carry service connected conditions, mental health and substance use content at elevated prevalence, and information bearing on benefits entitlement, all of which attract protections beyond the ordinary health privacy rule. A buyer should know which parties handle it. Ask for the component inventory and privacy documentation from the federal assessment, and for a sub processor list scoped to the commercial product rather than the federal one.

Unusually strong independent validation for a company of this size, though not clinical outcome evidence. Knowtex placed in the top three of the 2024 Department of Veterans Affairs AI Tech Sprint for Ambient Scribe, a structured competitive evaluation run by the government rather than the vendor, and was subsequently awarded a 15 million dollar VA contract through federal procurement, deploying from October 2025 across the largest integrated health system in the United States.

Neither of those is a testimonial and neither can be commissioned. An earlier pilot ran at the University of Rochester Medical Center from February 2023. Held at B rather than A because no published outcome data, accuracy result or peer reviewed study was located; what is evidenced is that competent external parties assessed it favourably, not what it achieved clinically.

No statement on audio or transcript retention, de identification or training use was located.

The earlier assessment's instruction stands and the second pass strengthens it: the answers very likely already exist in contract form. A federal health deployment brings obligations beyond the commercial privacy baseline, including federal records requirements, system of records notices governing how a federal agency may hold and use personal information, and the privacy impact assessment that accompanies an authorisation to operate. Those documents address retention, permitted use and disclosure directly. A vendor that has been through that process has answered these questions to a regulator's satisfaction and has published none of it.

One question is specific to this deployment and worth asking plainly. Veterans' health records include service connected conditions, mental health and substance use content at elevated prevalence, and information bearing on benefits entitlement. Content of that kind carries protections beyond the ordinary health privacy rule, and a documentation product capturing it should be able to say what it retains and for how long.

A second follows from a detail in the contracting notice. The system is designed so a provider can initiate a recording without manually entering patient identifying information, meaning the association between an encounter and a patient is established by the system from record context rather than by the clinician. That is a genuine workflow improvement and it moves an attribution decision into software. Establish what confirms the recording is attached to the right patient.

The training question is unanswered in either direction and matters more where federal data is involved.

Ask for the retention schedule, the training position, and the privacy documentation from the federal assessment.

No published business associate agreement posture was located.

The federal deployment makes this axis read differently than it does for a purely commercial vendor, and the distinction is worth setting out because buyers conflate the two.

A federal health agency is a covered entity and its vendors are business associates, so an agreement exists. But the agreement is not the whole of the contractual position in that setting. Federal deployment brings its own instruments: the contract itself with its data clauses, a privacy impact assessment, the security assessment supporting an authorisation to operate, and the rules governing how a federal agency may hold personal information. Those are the documents that actually constrain what this vendor may do with veterans' encounters, and they are more prescriptive than a commercial agreement.

The practical consequence for a commercial buyer is a question rather than a reassurance. Terms negotiated for a federal customer do not transfer, so establish what a commercial agreement with this vendor contains, whether the retention and use limitations match the federal ones, and whether processing for commercial customers happens in the same environment or a separate one.

The vendor also reports deployment across a large number of commercial health systems alongside the federal contract, so both postures exist in parallel and a buyer should be clear which applies to them.

Ask for the agreement, whether a separate environment serves commercial customers, and whether the data handling commitments made to the federal customer are offered commercially or only there.

No named or dated attestation and no trust centre were located, and the grade records what a counterparty can verify. The substance behind that grade is unusually favourable and should be read with the note rather than from the letter.

The lead identified in the earlier assessment is confirmed. The vendor holds a federal contract to deploy across the veterans health system, awarded following a competitive evaluation challenge and reported at fifteen million dollars, with rollout from October 2025 across a system comprising one hundred and seventy medical centres and more than a thousand outpatient sites. Reporting of the award notes that the selected companies then had to clear additional hurdles before integration, and a senior official described the privacy and consent work involved as substantial.

Deployment at that scale inside a federal health system requires an authorisation to operate and the security assessment that produces it. That process examines control implementation against a federal control baseline, is granted by a named authorising official, and is a materially higher bar than a commercial attestation. It is very unlikely this vendor does not hold one.

So this is a publication gap rather than a control gap, and it is the most consequential unpublished artefact in this category. A vendor holding federal authorisation and not saying so is leaving its strongest evidence unused, and every commercial buyer evaluating it is asking for a lesser assurance than the one that already exists.

Ask directly for the authorisation, its impact level, its date, and the boundary it covers. Ask separately whether a commercial attestation exists for deployments outside the federal environment, since the authorisation may not extend to them.

No clearance claimed and none required for documentation. The direction of travel flagged in the earlier assessment is no longer a roadmap and the record should be corrected on that point.

The vendor describes its platform as covering the full care journey: pre visit insight and chart summarisation, in visit ambient documentation, and post visit specialty specific coding, order automation, and clinical decision support. Decision support is named as a current platform capability rather than a future one, and order automation sits alongside it. A separate announcement describes the platform generating notes, codes and orders.

Those are three different regulatory conversations and a buyer should hold them apart. A note the clinician signs attracts no pathway. An order is an action taken on a patient rather than a description of one. Decision support is the category where the exemption depends on a professional being able to review the basis of a recommendation independently, and where intended purpose rather than technical sophistication sets the threshold. Ask what the decision support does, what it is grounded in, and what the clinician is shown before acting.

One piece of evidence about the regulatory environment deserves recording because it comes from the deploying institution rather than the vendor. A senior official at the health system publicly described substantial policy work on informed consent and the protection of veterans' privacy preceding rollout. The largest integrated health system in the country treated consent as the hard problem in adopting ambient documentation, which is the clearest institutional confirmation in this index that consent is the live regulatory question for this category rather than device classification.

Ask how consent was resolved, since that answer exists.

No fairness statement, subgroup analysis or accent and dialect performance disclosure was located.

The earlier assessment identified why this gap carries particular weight here and the second pass sharpens it into something closer to a missed opportunity than an omission.

The veterans health system serves more than nine million people and is the largest integrated health system in the country. Its population differs from the commercial average in ways that bear directly on speech recognition and on documentation quality: an older and predominantly male cohort, high prevalence of hearing loss, traumatic brain injury, post traumatic stress and substance use, distinctive regional distribution including substantial rural enrolment, and clinical vocabulary specific to service connected conditions.

Every one of those characteristics is a plausible source of differential performance, and the deployment makes them measurable. The system has extensive research infrastructure, standardised records across all sites, and a mandate to evaluate what it adopts. A vendor operating at that scale inside that system is better positioned than almost any other in this category to produce subgroup evidence, and a national deployment generates the sample size that makes such evidence meaningful rather than anecdotal.

So the question here is not whether the vendor could publish evidence but whether the evaluation is being done and by whom. Deployment evaluations conducted by the health system may exist without the vendor holding or publishing them.

Ask what performance evaluation accompanies the federal deployment, whether results are broken out by patient or clinician characteristics, and whether any of it will be published.

More accountability apparatus surrounds this product than most in the lane, and none of it is published or necessarily portable, which is why it sits in the middle band. The federal deployment brings obligations that do not apply to a commercial scribe: federal records requirements, notices governing how an agency may hold and use personal information, and a privacy impact assessment accompanying an authorisation to operate.

For patients inside that system, federal privacy law also gives an individual a route to seek amendment of a record held about them, which is a genuine statutory mechanism rather than a vendor courtesy. A competitive federal evaluation additionally implies that performance was measured by an external party, which is more independent assessment than almost any peer has had. The problem is that none of it travels and none of it is visible.

No figure from that evaluation is published, no privacy documentation is public, and a commercial buyer inherits none of the federal apparatus, which is the certification does not transfer pattern this index has recorded in several other forms. One design detail deserves specific attention because it moves a decision into software without a described control.

A provider can initiate a recording without manually entering patient identifying information, so the association between an encounter and a patient is established by the system from record context rather than by the clinician. Attaching a note to the wrong patient is among the most consequential documentation errors possible, and nothing published describes what confirms the match or what happens when it is wrong. Ask for the evaluation results, the privacy documentation, and the attribution control.

Positioned as EHR agnostic and deeply integrated into workflow, accessible from mobile, tablet or computer with no dedicated hardware, and designed to fit team based care. The VA deployment is meaningful evidence that integration works at scale in a complex federal record environment.

Held at B because no named commercial EHR integrations, certification programme listings or write back architecture were enumerated or verified in this pass, so breadth outside the federal deployment is asserted rather than demonstrated.

No hosting region, residency configuration or subprocessor detail was located.

The federal deployment implies a government cloud posture and that is the specific thing to confirm rather than assume. Federal health workloads are normally required to run in an authorised environment, physically and logically separated from commercial infrastructure, operated by screened personnel and subject to the boundary defined in the authorisation. If this vendor operates such an environment, its answer to this axis for federal work is strong and documented.

What does not follow is that a commercial customer receives the same thing. Running a federal enclave is expensive, and vendors commonly operate two environments with different controls, different personnel access and different subprocessors. A commercial buyer reading a federal deployment as evidence of their own posture would be making the same error this index has recorded elsewhere, where a parent's compliance programme was read across to a specific product.

So the questions are: which environment serves commercial customers, what boundary and controls apply there, and which of the federal protections carry over.

The model provider question is unanswered and matters here. The vendor is backed by a major cloud provider among its investors, which suggests but does not establish where workloads run, and nothing states whether an external model service processes encounters or what it retains. In a federal enclave that question has a documented answer; commercially it does not.

Ask which environment applies to your deployment, the boundary description, the subprocessor list for each, and the model provider.

No rate card, but an unusual accidental disclosure worth using. Because the VA award is a federal procurement, its value is public at 15 million US dollars, which gives buyers something almost nothing else in this category offers: a real, externally verified enterprise scribe contract figure to benchmark against, rather than a vendor quoted range.

That is transparency by operation of procurement law rather than by vendor choice, so it says nothing about how this vendor prices commercially, but it is a genuine data point in a category where every enterprise number is otherwise negotiated in private.

Specialty specific by design rather than one model behind templates, with oncology workflows named explicitly, and the VA deployment spans 170 medical centres and 1,193 outpatient clinics covering effectively every specialty and care setting in a national system. Held at B because that breadth currently rests on a single customer relationship rather than a distributed commercial base, and no specialty count or language coverage is published.