emtelligent

The medical language engine is the entire company. Purpose built models trained on what the vendor describes as billions of clinical data points, developed by computer scientists working with physicians, and every product in the suite is a surface on that one engine. Infrastructure sold as an engine rather than as a finished application does not reduce centrality: Corti sits in the ambient scribe category on the same reasoning, graded A for owning the model despite selling through an SDK.

Oversight is the stated design goal rather than an afterthought. The chief executive frames the problem the product solves as prior systems having difficulty referencing source data reliably enough to allow proper human review, and the company markets auditable answers. Clinical Workflow is explicitly an AI assisted review interface for clinicians, coders and reviewers, so human review is the product surface rather than a step bolted on after generation. Uncertainty detection is itself a form of calibrated output, since a system that marks a hedged finding as hedged is telling the reviewer where to look. Held at B for two reasons. No confidence threshold, routing rule, abstention behaviour or error rate is published. And when the engine runs as embedded infrastructure inside someone else's platform, emtelligent does not control what oversight the downstream integrator applies, or whether the end user knows a third party engine produced the structured data. That is the same limitation this index recorded for SimboAlphus: a good primitive is not an oversight mechanism once someone else is holding it.

The best technical capability disclosure in this category, and it is checkable rather than atmospheric. Instead of claiming AI powered summaries, the company names the specific tasks its engine performs: entity linking to clinical ontologies, polarity and uncertainty detection, experiencer detection, measurement and temporality, relations, and medication identification with follow up detection. Those are the right things to name. Polarity determines whether no evidence of pneumonia becomes pneumonia in a summary, and experiencer determines whether a mother's breast cancer becomes the patient's. They are the two failure modes most likely to corrupt a chart summary without anyone noticing, and no other vendor in this lane names either. Held at B rather than A because none of it is quantified: no accuracy figure, no benchmark result, no model card and no published evaluation exists for any of the named capabilities. The marketing also carries unfalsifiable superlatives, the most accurate and feature rich medical AI platform on the market and unparalleled accuracy, and clinical grade is a coinage with no standard behind it. Publishing per capability accuracy, particularly on negation and experiencer, would move this to A immediately and would set the benchmark for the category.

Commercial traction stated without a published measure of benefit, which this index grades C. Optum is described as a beta customer, which is a meaningful named reference given its scale, and the company reports traction with real world evidence companies and data resellers serving pharma. Against that, no accuracy benchmark, no peer reviewed evaluation, no independent assessment and no named health system deployment with outcome data was located. For a product whose whole claim is superior extraction accuracy against general purpose models, the absence of a published comparison is the gap that matters. Ask for a head to head on a held out corpus with the error taxonomy broken out.

The deployment architecture is the substantive privacy answer here and it is a good one. Products can be deployed in the vendor's environment, in the customer's own environment, or in a private cloud, which means an organisation can process clinical text without it leaving infrastructure it controls. That is engineered privacy rather than a policy promise, in the same class as on device or on premise processing elsewhere in this index, and it is the strongest structural PHI position in this category so far. Held at B rather than A because no retention period, no statement on whether customer data is used to train or improve models, and no de identification posture was located, and because the default vendor hosted option carries none of the protection the customer hosted option does. Establish which deployment applies to your contract, because the PHI posture differs completely between them.

No HIPAA compliance statement and no business associate agreement terms were located on any retrieved surface. Not Rated records absent evidence rather than an assessed weakness. Two things sharpen the question for this vendor specifically: it is a Canadian company serving United States payers and health systems, so cross border handling should be established alongside the BAA, and where it operates as embedded infrastructure inside another vendor's platform the business associate chain runs through that platform rather than directly, so ask who signed what and with whom.

No SOC 2, ISO 27001, HITRUST or other attestation was located, and no trust centre or security page was found. Not Rated reflects absent retrieval rather than an assessed weakness. Given that the customer hosted deployment option would move much of the security burden onto the customer's own environment, establish which controls the vendor attests to in each of its three deployment modes rather than treating the answer as uniform.

No FDA clearance, device authorisation or regulatory pathway statement was located. Not Rated reflects absent retrieval. The company's radiology specific applications within its developer suite are the place a buyer should press, since image adjacent and report adjacent products in that specialty are the most heavily regulated territory in this index and the boundary between structuring a report and interpreting one is where the analysis turns.

Credit first, because the framing is genuinely more honest than the category norm. The company states plainly that unaligned generative models are not accurate enough for medical use, names hallucination and non determinism as real problems rather than competitor problems, and identifies unreliable source referencing as an obstacle to human review. Very few vendors describe the weaknesses of their own technology class in their own marketing. Against that, no fairness, subgroup or demographic performance disclosure of any kind was located, no error analysis is published, and the accuracy claims are superlatives rather than measurements. One structural point specific to infrastructure vendors deserves recording: when this engine sits inside a data aggregator feeding downstream analytics used in payer and life sciences decisions, any systematic extraction error propagates into decisions made by parties who may not know the engine is in the stack and cannot evaluate it. The absence of published subgroup performance matters more in that position, not less.

Interoperability here means standards and formats rather than EHR embedding, and on that measure it is solid. Extracted concepts are mapped to clinical ontologies with ICD-10 and SNOMED searchable directly, structured output is designed to feed downstream systems, and Document Manager ingests bundled PDFs, paper forms and complex documents rather than requiring clean structured input. The engine is proven as an embedded layer inside larger aggregator platforms. Held at B because no EHR vendor is named anywhere, no EHR integration mechanism is described, and this is not a product a clinician opens inside the chart. For a health system evaluating the summarisation offering rather than the engine, establish how output actually reaches the care team.

The first A on this axis in this category and the only vendor here offering real choice. Products can be deployed inside the vendor's environment, inside the customer's own environment, or in a private cloud. That means an organisation can decide that clinical text never leaves infrastructure it controls, which is the property this index credits as the ambient instance of the where does the data go frame, and which Corti holds in the scribe lane. Every other product reviewed in this category is hosted software with no alternative. Two gaps keep this from being a complete answer and should be raised in diligence: no residency regions are named for the vendor hosted option, and no portability commitment is described, so a buyer should confirm what happens to extracted structured data and ontology mappings if the relationship ends.

No price, tier or pricing mechanism is published for any product in the suite. Not Rated is the house convention for absent pricing rather than a low grade. Pricing is likely to vary substantially across the three deployment modes and between direct and embedded distribution, so a buyer should establish which model applies before comparing this to anything else in the category.

Broad by buyer type rather than by clinical specialty, which is the correct shape for an engine. Four distinct markets are served: payers, health systems, pharmaceutical and life sciences companies, and health technology and data services providers. Named use cases span chart review, care gap identification, patient transitions, quality improvement, coding support, actuarial analysis, population cohort work and real world evidence. Radiology specific applications exist in the developer suite. Graded B rather than A because the specialty depth stops at radiology and because the breadth comes from a general engine applied across markets rather than from instrument level behaviour in any one of them.