Augnito

States plainly that it owns and trains its own AI models rather than orchestrating someone else's, and the evidence supports it: separate speech models tuned per medical specialty is a first party training decision, not something achievable by prompting a general purpose API. The parent's transcription heritage is a services business, but the product assessed here is model work.

No review gate between generation and transfer is described, and no acceptance rate, edit burden figure or confidence threshold was located.

The second pass confirms why this is the first thing to establish in writing rather than a routine gap. The product does not stop at a note. It generates and sends clinical letters, captures clinical coding, and performs live translation during the consultation. Each of those carries consequences outside the chart, and each warrants a different answer about what the clinician confirms and when.

Outbound letters are the sharpest. A letter that has been sent has reached another clinician or a patient and cannot be recalled by editing the record afterwards. Establish whether the clinician approves each letter before dispatch, what the default is, and whether sending can be automated.

Translation is the second, and no peer in this lane resolves it well. Where the system renders speech across languages inside a live exchange, the clinician cannot verify the rendering unless they speak both languages, so the ordinary review gate does not function. One vendor in this category publishes an explicit caveat that its product cannot act as an interpreter and that a native speaker must corroborate. No comparable statement was located here.

The vendor markets quality assurance as a feature without describing what performs it or what it checks. That phrase is the natural place to start: if a quality assurance step exists it may already be the review gate this axis is asking about, and if it is automated it is not oversight in the sense intended.

Ask what the clinician confirms for a note, a letter, a code and a translation, treating each separately.

Useful architectural disclosure undermined by unfalsifiable accuracy language. On the positive side, Augnito describes a genuinely distinctive design: it owns and trains its models, and ships multiple speech models tuned to specific specialties rather than one general model behind specialty templates, which is a structural choice a buyer can interrogate. Against that, the accuracy claims are the weakest in this category.

Spectra is marketed at 99.9 percent accurate speech recognition with no methodology, reference standard or denominator, and Omni's materials claim transcription with absolute accuracy, which is not a property any speech system possesses and cannot be tested. A vendor competing on measurable accuracy should publish measurements.

This record carries the most unusual corpus provenance in the lane, and it belongs on this axis because the question of what fed the model is inseparable from who else has held the content. The company owns and trains its own models and ships several speech models tuned to particular specialties rather than one general model behind templates, which is a genuinely short chain and a design a buyer can interrogate. Where the training material came from is the substantive disclosure.

The parent has supplied clinical transcription as a service since 2001 with delivery teams in England and India, and an account of the product's development describes a large existing database of medical voice recordings from doctors of many nationalities working in that health service as the basis of the speech engine's accent handling, which is the product's principal claim. So a corpus accumulated under service contracts appears to underpin a commercial speech product.

That may be entirely proper, the contracts may permit it and the material may have been de identified, and the speakers are clinicians rather than patients, but it is a change of purpose from the one the recordings were collected for, and dictated clinical content concerns patients even when the voice is a doctor's.

The current chain is otherwise unenumerated: no hosting or cloud arrangement is published, no sub processor list was located, and the human transcription operation spans two countries without any statement of which entity holds what. Ask on what basis the historic corpus was used for model development, whether the originating organisations agreed, and whether a current customer's dictation joins it.

No peer reviewed study, controlled evaluation or independent assessment located. NHS trust and private provider adoption is asserted across UK and global deployments, and the parent has a long NHS transcription history, but deployment history is not evidence of the AI product's benefit and this index does not treat it as such. Community based nursing deployment is described in case study form rather than measured.

No statement on audio or transcript retention, de identification, or whether customer data trains models was located. The earlier assessment noted this matters more here because the vendor trains its own models and competes on accuracy gained from training data. The second pass finds where that data came from, and it is the most consequential item on this record.

The parent company has supplied clinical transcription to the health service and private providers since 2001, with delivery teams in England and India. An account of the product's development states plainly that one of the company's advantages was a large existing database of medical voice recordings, representing doctors from all over the world with varying accents who worked in that health service. That accumulated corpus is described as the basis of the speech engine's accent handling, and accent handling is the product's principal claim.

So recordings gathered over two decades under contracts to provide transcription as a service appear to underpin a commercial speech product. That may be entirely proper. The contracts may permit it, the material may have been de identified, and the speakers are clinicians rather than patients. It is still a change of purpose from the one the recordings were collected for, and dictated clinical content is about patients even when the voice is a doctor's.

The questions are answerable and a buyer should ask them: on what basis was that corpus used for model development, what de identification was applied, whether the originating organisations agreed, and whether a current customer's dictation joins it.

Ask also for the retention schedule and the training position for new customers in contract language rather than marketing.

No business associate agreement posture was located, and deployment is centred on the United Kingdom health service and international markets under the British data protection regime rather than the United States rule.

The scoping is largely clean and this axis would read as not applicable were the vendor's reach narrower. It is not. The company markets to global hospitals, launched first in India, and sells its speech engine to other software vendors who may deploy it anywhere including the United States. So a United States buyer, or a buyer of a third party product built on this engine, needs an answer that the vendor's home market materials do not give.

Two questions follow and they are more specific than the usual pair.

First, establish whether an agreement is available at all. A vendor operating principally under a different regime may have no mechanism to offer one, and using the tool on protected health information without it is itself a violation however secure the product is. The same instruction applies to any software vendor embedding this engine: their own agreement with a United States customer does not automatically extend to their supplier.

Second, and specific to this vendor, establish where processing and any human review occur. The company operates delivery teams in two countries and its origins are in human transcription, so the location of people, not only servers, is a live question. Under the United States rule an offshore human reviewing protected health information is a permitted arrangement only if it is papered, and a buyer should see how.

Ask for the agreement, the processing and review locations, and the subprocessor list.

No named or dated attestation and no trust centre were located.

The expectation here is higher than for most vendors in this lane, and the reason is the customer base rather than the company's size. Supplying the United Kingdom health service brings a defined set of assurance requirements, principally the national data security and protection toolkit, which suppliers handling patient data are expected to complete annually and which produces a published, dated status. Beyond it, ISO 27001 and the national cyber essentials scheme are the usual accompaniments, and a peer in this category publishes all three alongside a dated attestation and a subprocessor list.

So unlike much of this lane, the relevant evidence for this vendor is standardised, annual and published by design. A supplier with two decades of health service work will hold a toolkit status. That none of it appears on the product's own materials is a publication gap rather than, most likely, a compliance one, and it is straightforwardly fixable.

Two features of the business raise what an examination would need to cover. The company has historically delivered services through teams in two countries, so personnel security, access control and offshore working arrangements are substantive rather than boilerplate. And it sells its speech engine as an interface and development kit for third party clinical systems, so other vendors inherit this posture into their own products and pass it downstream.

Ask for the toolkit status and its date, whether ISO 27001 is held, and specifically what the scope covers across the ambient product, the speech engine and the interface offering.

No clearance claimed and none located. The phrase flagged in the earlier assessment is confirmed on the vendor's own material and should be pressed, because it does work it cannot support.

The ambient product is described as delivering approved suggestive feedback, with the health service named as the approver. Approval or adoption by a health system is a procurement outcome, not a regulatory classification. No health service approves a medical device; a regulator registers or certifies one. Using an institution's name in that position invites a reader to hear regulatory sanction where none has been described, and a buyer should ask precisely what was approved, by whom, and against what.

The underlying question is live rather than academic. In the United Kingdom, software delivering clinical suggestion falls to be assessed against the medical device framework, and the threshold sits at intended purpose rather than at technical sophistication. A peer in this lane holds a Class I registration with the national regulator for an ambient documentation product and publishes it, which establishes both that the question applies to this category and that the answer is obtainable. No such registration was located here.

The surrounding feature set makes the intended purpose question harder rather than easier. Alongside notes the product captures clinical coding, generates and sends clinical letters, and performs live translation. Letters that leave the organisation and translation inside a clinical exchange both carry consequences beyond the chart.

Ask what the approval refers to, whether a regulatory assessment of intended purpose has been performed, and if so what classification resulted.

The most specific engagement with accent variation of any vendor in this index, and simultaneously the clearest case of a vendor asserting rather than demonstrating it. Augnito does not gesture at multilingual support; it names the accents it claims to handle, including Indian English, African English, Welsh, Scottish and Irish, alongside capture in more than 37 languages and per specialty speech models.

Naming the specific speaker populations rather than hiding behind a language count is meaningfully better than the category norm, and this index's standing concern is precisely that speech models degrade on accents underrepresented in training data. But the marketing frames the product as accent agnostic and absolutely accurate, which converts a measurable property into an unfalsifiable claim. Of every vendor assessed here, this is the one that should publish word error rates broken down by accent, because it is the one selling on them. Doing so would move this to A immediately.

Two passes located no terms of service, no warranty or indemnity language, no remediation commitment and no falsifiable performance measurement. What is published instead is the weakest set of accuracy claims in this lane, and their weakness is of a particular kind that matters here. One product is marketed at 99.9 percent accurate speech recognition with no methodology, reference standard or denominator.

Another is described as transcribing with absolute accuracy, which is not a property any speech system possesses and which no test could confirm. A claim that cannot be true is worse than silence for a buyer trying to establish reliance, because it forecloses the conversation rather than opening it, and a vendor competing explicitly on measurable accuracy is the one vendor that should be publishing measurements.

The jurisdictional floor that lifts other non United States vendors in this lane applies only partially here. Operations span England and India and the product sells across several markets, so whether the recorded patient holds an enforceable correction right depends on where a given deployment processes data rather than on anything inherent to the vendor. A buyer should establish that for its own deployment rather than assuming it. Ask for an accuracy figure with a defined denominator and reference standard, for the terms, and for which regime governs processing in your contract.

Integration is offered as a capability rather than a fixed list, through an API and SDK designed to add speech and voice command into clinical software, EPR, PACS and RIS systems, alongside direct note and letter transfer into the electronic patient record. Covering radiology reporting systems as well as record systems is broader than most scribes attempt. Held at B because named production integrations were not enumerated or verified in this pass, so breadth is architectural rather than demonstrated.

No hosting region, residency option or subprocessor detail was located. Delivery is cloud across desktop, browser and mobile with no voice profile training required.

The earlier assessment identified processing location as a specific question rather than a generic one, and the second pass confirms why. The company operates delivery teams in England and India, and has done so throughout the two decades it has supplied clinical transcription. That is a stated operational fact rather than an inference.

For a health service buyer this is the first question their governance process will ask, and it has two parts that should not be collapsed. Where does automated processing run, meaning transcription and note generation. And separately, does any human ever see the content, and where are they. The second matters because this company's origins are in human transcription delivered from two countries, so a hybrid or fallback path is plausible in a way it would not be for a vendor with no such history. If any content reaches a person for quality assurance, correction or escalation, that is a transfer regardless of where the servers sit.

The vendor markets quality assurance as a feature of the ambient product without describing who or what performs it. That phrase should be resolved directly.

The interface product raises a third question. The company sells its speech capability as an interface and development kit for other software vendors to embed, so a clinician may be using this engine inside a third party clinical system, with residency governed by an agreement they never saw.

Ask for the processing region, whether human review occurs and where, the subprocessor list, and what quality assurance means operationally.

Publishes the pricing mechanism but not the price. Materials describe a simple recurring monthly fee with no capital investment required, which tells a buyer the shape of the commitment and is more than silence, but no rate, tier or per clinician figure was located. Compare the vendors graded A on this axis, which publish the mechanism AND the number.

Among the broadest coverage in this category and enumerated rather than implied. Spectra spans more than 55 medical specialties, Omni captures in clinic, over video call and via telemedicine, and coverage explicitly includes general practice, nursing including community based nurses, psychiatry, surgery and cardiology, with a speech model tuned per specialty rather than one model reused. Capture runs to more than 37 languages with live translation. The community nursing use case, where the clinician is rarely near a desktop, is a setting most competitors in this category do not address at all.