AlethianAI

The agent roster is the product. Reception, intake, documentation, coding, billing, and inbox management are each performed by a model, and there is no non AI version of the offering.

No escalation criteria, confidence thresholds or human review gates were located, and the platform is sold on autonomy: an autonomous call centre, agents operating as a coordinated network, and reduced clinical support staff cost as the stated commercial benefit.

Three of the agents take consequential action rather than drafting for review. The inbox manager works refills, lab results and follow ups. The coder assigns billing codes. The receptionist speaks to patients unsupervised. Each needs a defined boundary and none is published: what a refill agent may action without a clinician, what happens to an abnormal lab result, whether a code is submitted or suggested, and when a call is handed to a person.

The scribe is stated to link documentation to code evidence, which is a real traceability feature and is credited on the transparency axis. Traceability after the fact is not the same as a control before it.

For an early stage platform whose value proposition is replacing support staff capacity, the oversight model is the single most important thing to establish before deployment.

No foundation model is named, no architecture is described, no evaluation methodology is published and no accuracy figure was located for any of the agents.

Two things are worth crediting inside the grade. The company states it holds licensed American Medical Association CPT content used for scribe training and code suggestion, which is a specific and externally checkable licensing fact rather than a general assurance, and it is the correct basis for a product suggesting procedure codes. And the scribe is described as producing documentation with evidence links back to the codes it supports, which gives a coder or auditor a traceable path from a code to the language that justified it.

That traceability is the right design. What is missing is any measure of whether it is correct. For a platform generating documentation, assigning codes and marketing audit defence, the useful numbers are the rate at which suggested codes are accepted unchanged, and how often a code survives payer review. Neither is published.

One input is named and externally checkable, which is more than most of this tier offers. The company states it holds licensed procedure code content from the professional body that maintains it, used for scribe training and code suggestion. That is a specific licensing fact rather than a general assurance, it is verifiable in principle, and it is the correct basis for a product suggesting procedure codes, since using that content without a licence is itself a problem.

Naming one contributing data source answers part of what this axis asks. What is absent is everything else. No foundation model provider, model class or version is named, no hosting arrangement is published, and no sub processor list was located, and the content flowing through that unnamed chain is broad for an early stage company: call audio from a reception agent, symptom and history detail captured at intake, encounter recordings and generated notes, and laboratory results and messages handled by an inbox agent.

The training question is the one to press and it is only half answered. The licensed content statement tells a buyer about one input and nothing about the others, so establish whether encounter audio, generated notes or intake responses from one practice improve models serving another. Those answers are cheap to give while a company is small and much harder to unwind once a corpus exists.

No evidence retrieved. The company emerged from stealth in late 2025 with a seed round and publishes no customer counts, named references, deployment figures, or measured outcomes. The claimed capability set is unusually broad for a company at this stage, covering reception, intake, documentation, coding, billing, and inbox in one platform, and a buyer should verify that each agent is production ready rather than roadmap. This grade reflects absence of evidence, not evidence of poor performance.

No retention period, no statement on whether customer data is used to train or improve models, and no de identification posture was located.

The surface is wide for an early stage company and it spans the most sensitive material a practice holds. Call audio from the reception agent, symptom and history detail captured during intake, encounter recordings and generated notes from the scribe, lab results and messages handled by the inbox agent.

The training question is the one to ask first. The company states it uses licensed CPT content for scribe training, which tells a buyer something about one input and nothing about the others. Establish whether encounter audio, generated notes or intake responses from one practice are used to improve models serving another, and what is retained after a note is filed. Those answers are cheap to give while a company is small and much harder to unwind once a corpus exists.

The company states it is a HIPAA compliant platform with comprehensive audit trails supporting CMS compliance and payer audits. No business associate agreement terms, no privacy notice and no supporting documentation were located.

Business associate status is structurally certain given the platform records encounters, captures patient history and writes to the electronic health record.

The audit trail claim is the part worth testing rather than accepting. Comprehensive audit trails for payer audits describe a billing evidence function, which is not the same as the access logging the security rule requires. Establish whether access to protected health information is logged at the individual user level, whether agent actions are attributable and reviewable, and how a practice would reconstruct who or what touched a record during an investigation. Those are different questions from whether a claim can be defended.

No SOC 2, HITRUST or ISO 27001 attestation was located across two differently phrased searches, and no trust centre or security page was found. The company describes itself as a HIPAA compliant platform meeting healthcare security requirements, which is a self assertion rather than an independent examination.

Stage context, so the grade reads fairly: the company emerged from stealth in late 2025 with a seed round, and a completed attestation would be unusual that early. The absence is not a judgement on the team.

It does matter more than usual for two reasons. The stated target buyers are small clinics and practices in rural and underserved areas, which are the organisations least equipped to run their own vendor security assessment and most reliant on published assurance. And the platform holds an unusually wide data surface for a young company, spanning call audio, intake responses, clinical documentation, coding and the clinical inbox. Ask what attestation is in progress and on what timeline.

No FDA clearance, device authorisation or clinical decision support exemption analysis was located, and the question is live here rather than academic.

The medical assistant agent is described as performing intake, triage and history capture. Triage is the word that matters. Software that assesses a patient's presenting symptoms and influences urgency or routing sits close to the device boundary, and whether it stays outside depends on whether a clinician can independently review the basis of its output. Most of the agents on this platform are plainly administrative. That one is not, and no analysis of where it falls was published.

Two further regimes apply and are unaddressed. The coder and biller agents shape what is submitted for payment, and liability under the False Claims Act sits with the practice rather than the vendor. And the receptionist agent places outbound calls, which reaches the consumer telephone consent framework, where the FCC has ruled that AI generated voices require prior express consent.

Ask which agents the company treats as non device and on what reasoning, and ask to see it written down.

No AI governance framework, model monitoring disclosure or bias evaluation was located.

The company's own positioning raises the bar rather than lowering it. It markets itself on preserving access in rural and underserved communities facing large reductions in state health funding, and that is a claim about equity, not only efficiency. A vendor making an access claim carries a stronger duty to publish evidence for it than one selling time savings.

The mechanism is direct. Conversational agents handle reception and patient intake, and speech recognition and language understanding vary with accent, dialect, speech rate and language. In a rural or underserved practice that variation determines who can book an appointment, complete an intake, or get a refill handled without reaching a human. Where the product's purpose is to replace clinical support staff, a patient the system cannot understand has fewer fallbacks than before, not more.

Nothing published reports performance by language or population, and nothing describes what happens when an agent fails to understand a patient.

The traceability design is the right one and it carries the grade. The scribe is described as producing documentation with evidence links back to the codes it supports, so a coder or auditor can follow a code to the language that justified it rather than accepting an assignment on trust.

That is the same principle credited elsewhere in this index and it is more valuable in coding than in note text, because a code determines what is billed and the exposure for a wrong one sits with the practice submitting rather than with the vendor suggesting. It also matters for the product's own audit defence positioning, since an audit defence is only as good as the evidence path it can produce. What is missing is any measure of whether the links point at the right things.

No accuracy figure, error rate or evaluation methodology was located for any of the agents, and for a platform generating documentation, assigning codes and marketing audit defence the useful numbers are the rate at which suggested codes are accepted unchanged and how often a code survives payer review. Neither is published. No warranty, indemnity or remediation commitment was found. Ask for both rates, and for what the vendor commits to when a code it suggested is denied or reversed.

Bidirectional integration with Epic, Cerner, and Allscripts is stated, with real time note completion during encounters and paperless intake syncing to the EHR. Graded conservatively because the claim is vendor asserted with no marketplace listing, certification, or customer reference retrieved to corroborate it, and bidirectional write access to three major EHRs is a substantial claim for a company selling for under a year.

No hosting provider, region, tenancy model or data residency commitment was located, and no subprocessor list is published.

Two subprocessor layers are near certain given what the product does, and neither is disclosed. The reception agent implies telephony carriage and speech processing, which are usually operated by third parties rather than built in house. And a platform generating documentation and suggesting codes at this scale implies a language model provider.

That second point is the one to press. Establish where inference executes, which model providers are involved, whether encounter content leaves the practice boundary on every note, and what those providers retain of prompt and completion data. A young company assembling a stack quickly will add subprocessors as it grows, so ask for the list now and ask to be notified when it changes.

No public pricing. Contact the vendor. Direct sales to clinics, MSOs, and hospitals with implementation and EHR integration included, marketed on reduced clinical support staff cost.

Scope is stated clearly by function and by buyer. The agent roster covers reception and scheduling, intake and history capture, documentation, coding, billing and clinical inbox management, sold to clinics, management services organisations and hospitals, with an initial geographic focus on Washington State and stated attention to rural and underserved providers.

Naming a starting market rather than claiming national coverage is the right posture for a company at this stage and it is credited.

Held at B rather than A because no specialty scoping is stated at all, and specialty is where this kind of platform usually breaks. Documentation, coding and intake differ substantially between primary care, behavioural health, orthopaedics and oncology, and a roster this broad from a company selling for under a year is unlikely to be equally mature across them. A buyer should establish which specialties are in production today rather than which are supported in principle.