Sample Healthcare
Sample Healthcare sells document processing automation across the administrative span of a healthcare organisation, from patient intake through to insurance appeals, under the name Clinical Reasoning System. It deploys as AI copilots integrating with EMR and revenue cycle systems, claims deployment in days, and reports automating up to 85 percent of correspondence tasks with 2 to 5 times speedups. Customers are described by type rather than name: publicly traded companies and national provider groups, a top diagnostics provider that used it on prior authorisations, and a major health system that increased patient intake capacity. Two things distinguish it and both belong in an evaluation. The first is an engineering grade auditability layer, which is more developed than the norm in this category. The company describes end to end visibility across every dataset, decision and hand off, audit trails that trace any value back to its source, anomaly alerts, and versioned lineage graphs. That is provenance treated as infrastructure rather than as a user interface feature. The second is a statement of intent that almost no vendor in this index makes in public. The company describes its trajectory plainly: it starts by making a team roughly ten times faster, its systems then learn from that team, and eventually they fully automate, with the qualifier that the customer stays in control. Most vendors in this category present human oversight as a permanent design property. This one presents it as a stage, and says the system learns from the people whose work it will eventually take over. That candour is worth crediting and the implication is worth understanding before signing, and it is discussed on the autonomy axis. Evidence is thin. No customer is named, no funding was located, no accuracy figure is published, and parts of the company's own website still carry unreplaced placeholder text, so several axes below are graded low or Not Rated on that basis.
Capability Axes
The reasoning and extraction engine is the product. There is no system of record, services organisation or prior software platform underneath, and every described capability, document processing, insight extraction from medical records, correspondence automation and the copilots themselves, is model output. The company's stated endpoint of full automation only makes sense for a company whose product is the model.
This vendor states its autonomy trajectory openly and that candour deserves credit before the grade is explained. The company describes a progression: it starts by making a team roughly ten times faster, its systems then learn from that team, and eventually they fully automate, with the customer staying in control. Almost every other vendor in this index presents human oversight as a permanent design property. This one presents it as a stage on the way somewhere else, and says plainly that the system learns from the people whose work it is heading toward absorbing. Graded C because nothing governs the transition. No accuracy bar, confidence threshold or performance gate is published for when a workflow graduates from assisted to autonomous, no abstention behaviour is described, and no statement identifies which workflows are considered safe to automate fully and which are not. The audit trail and lineage capability is real and valuable, but it is forensic: it lets an organisation reconstruct what a system did after the fact, it does not prevent the system doing it. Ask what the criteria for full automation are, who signs off on each graduation, and whether appeals and clinical adjacent workflows are treated differently from correspondence.
One strong infrastructure property and no model level disclosure. Versioned lineage graphs, end to end visibility across datasets, decisions and hand offs, and audit trails tracing any value back to its source are genuine engineering artefacts rather than interface features, and they are more developed than most of this category offers. Against that, no model or model family is named, no accuracy figure exists, no evaluation methodology was located, and the precision claim is expressed as unparalleled, which is unfalsifiable as written. The phrase your data, your models, your intelligence suggests customers may bring or control their own models, which would be a significant disclosure if true and is nowhere explained. Ask what it means.
Outcomes claimed, none verifiable. Customers are described only by type: publicly traded companies, national provider groups, a top diagnostics provider and a major health system. No organisation is named, no case study exists, no funding was located and no independent evaluation was found. The published figures do not reconcile cleanly either, with 85 percent of tasks automated, 2 to 5 times speedups and roughly 10 times faster teams offered as separate claims with no baseline, denominator or measurement method. One customer outcome sentence on the company's own site is garbled to the point of being unreadable, and parts of the site still carry unreplaced placeholder text, which is weak evidence that the public material has been reviewed carefully.
No retention period, de identification posture or explicit training use commitment was located. Not Rated reflects absent retrieval. One statement bears directly on this and needs clarifying rather than crediting: the company says its systems learn from the customer's team over time. Establish exactly what that learning uses, whether it is confined to a single customer's environment or informs models used elsewhere, and what happens to that learned behaviour if the relationship ends.
A precision that matters. The company references HIPAA in a specific and narrow context, stating that its audit trails satisfy HIPAA, SOC 2 and FDA RECORD KEEPING requirements in real time. That is a claim about the auditability of its logs, not a statement that the company is HIPAA compliant, and it is certainly not a business associate agreement commitment. No compliance statement and no BAA terms were located anywhere. Graded C rather than Not Rated because a HIPAA adjacent claim exists and it is a narrower one than a reader skimming the page would take it to be.
New variant for the compliance language watchlist this index maintains. The site says its audit trails satisfy SOC 2 record keeping requirements. SATISFYING A STANDARD'S RECORD KEEPING REQUIREMENTS IS NOT THE SAME AS HOLDING AN ATTESTATION AGAINST THAT STANDARD, and the two read almost identically at a glance. No SOC 2 report, ISO 27001 certification, HITRUST certification, trust centre or security page was located. Graded C because a real capability is described, comprehensive logging, while the credential a security review actually asks for is absent. Ask directly whether a SOC 2 report exists, of which type, and over what period. Joins SOC 2 aligned, SOC 2 certified data centres and certified providers at all stages on the watchlist.
No FDA clearance, device authorisation or regulatory pathway statement was located. Not Rated reflects absent retrieval. FDA appears once on the site, again in the record keeping phrase, alongside HIPAA and SOC 2. That is an unusual reference for an administrative document processing product and it is unexplained: it may indicate life sciences or regulated manufacturing customers with part 11 style record keeping obligations, or it may be loose marketing. Worth asking which, because the answer says something about who the real customer base is.
The grade describes disclosure and the credit is genuine. Stating publicly that the endpoint is full automation, and that the systems learn from the team in the meantime, is more honest than the standard permanent human in the loop framing that several competitors offer without qualification. Auditability is treated as infrastructure. Against that, no fairness, subgroup or demographic performance disclosure of any kind was located, no governance framework or responsible AI documentation exists, no criteria are published for what may be automated, and the accuracy claim is an unfalsifiable superlative. The workflows named, prior authorisation and insurance appeals, sit on the payer facing side where this index holds that automating an approval is low risk while automating a denial or an appeal outcome is not, and nothing addresses that distinction.
Integration with EMR and revenue cycle systems is claimed alongside deployment in days, which is the right shape for a document workflow product that has to reach both clinical and financial systems. Nothing is named: no EHR, no revenue cycle platform, no integration standard, no marketplace listing and no customer deployment. An organisation cannot establish whether its own stack is supported without asking, and the deploy in days claim is unverifiable without knowing what it integrates with.
No hosting model, cloud provider, region, residency commitment or customer hosted option was located. Not Rated reflects absent retrieval. The statement that your data, your models and your intelligence remain always under your control implies something meaningful about deployment or model ownership but is not explained anywhere, and a claim of control is not a description of architecture. Ask what it actually means in deployment terms.
No price, tier or pricing mechanism was located. Not Rated is the house convention for absent pricing rather than a low grade. The commercial arguments offered, defensible return on every workflow and multiples of speed improvement, describe claimed value rather than cost.
Coverage is described by workflow rather than by care setting or specialty, and the span claimed is wide: patient intake at one end through to insurance appeals at the other, with correspondence processing and prior authorisation named in between. Buyer types include a diagnostics provider and a health system, which are genuinely different organisations with different document problems. Graded C because no clinical setting, specialty or instrument level behaviour was located, and because the breadth is asserted across a very wide span with only two unnamed customer anecdotes supporting it.
Pricing
Vendor-published figures are labeled as such. Figures labeled “Estimated” are derived from third-party sources and have not been confirmed by the vendor.
| Entry Price | Pricing Basis | BAA Tier | Implementation | Source |
|---|---|---|---|---|
|
Not published
|
Undisclosed. Sold to provider groups, health systems and diagnostics organisations. | Not published. Note that the HIPAA reference on the site concerns audit trail record keeping, not a compliance or BAA commitment. | Not published. Deployment in days is claimed alongside EMR and revenue cycle integration, with no stated implementation cost. | Vendor Published |
No price, tier or pricing mechanism was located, so commercial transparency is Not Rated per the house convention rather than graded down. The most important commercial question here is not price, it is the automation trajectory. The company states that its systems make a team faster, then learn from that team, and eventually fully automate. That has direct commercial consequences a buyer should get in writing rather than discover. Establish what the criteria are for a workflow to graduate from assisted to autonomous, who approves each graduation, and whether the buyer can decline. Establish whether pricing changes as automation increases, since a per seat or per user model and an outcome or per transaction model behave very differently when the seats are the thing being automated away. And establish what the learning uses, whether it stays inside your environment, and what happens to it at termination, because a system trained on your team's judgement is an asset created by your staff and its ownership should be explicit. Then the usual items. Which systems it actually integrates with, since EMR and revenue cycle integration is claimed and nothing is named. What the published figures mean, since 85 percent of tasks, 2 to 5 times speedups and 10 times faster teams are three different claims with no baseline or method. And whether a SOC 2 attestation exists, since the site references satisfying SOC 2 record keeping requirements, which is not the same thing and a security review will catch the difference.