Enzo Health

Built AI native by design rather than retrofitted, with the company describing an EHR constructed around the model rather than a model added to an EHR. Every stage it covers, from referral analysis through documentation to claim preparation, is model driven.

The design intent is stated plainly and it is to act first: Enzo does not just record what happened, it takes the next step before anyone has to ask, with the team only needing to review and approve. Across the episode that means analysing referrals, verifying eligibility, building schedules, coordinating supplies, generating OASIS documentation, checking codes and preparing clean claims automatically.

A review and approve gate is asserted but not described, and no confidence threshold, accuracy rate or abstention behaviour was located for any of those steps. Acting ahead of the human across an entire episode with one undefined approval step is a wide surface for a single gate to cover.

The accuracy claim of 95 percent or better carries no methodology, reference standard, denominator or definition of what was measured, and it is the only performance figure published. Capability is otherwise described in behavioural terms, such as knowing the difference between small talk and a clinical finding, which is a useful way to explain the problem and not a measurement of how often it succeeds. No model card or evaluation protocol located. One version detail worth checking: Enzo describes OASIS-E1 fields while the current instrument in the segment is OASIS-E2, so establish which version the product actually produces.

Nothing identifies any party in the chain: no model or model family, no foundation model provider, no hosting arrangement and no sub processor list was located in two passes. Encryption and a full audit trail are stated, which record and protect access rather than naming who has it. The content types make the silence broader than for a capture only product.

This platform ingests referral documents, photographs of medication labels and recorded visits across an entire episode of care, so the unnamed chain is handling images and documents originating outside the practice as well as speech captured inside it.

Photographs in particular are worth a specific question, because an image of a medication label is taken in a patient's home and may incidentally capture surroundings, other labels or people, and image handling is rarely covered by a retention policy written for audio. Ask for a sub processor list, whether any third party model provider processes images or documents, and for retention stated separately for photographs, referral documents and recordings.

One named customer testimonial from a registered nurse at a Utah home health and hospice agency describing improved OASIS coding, plus claims of 75 percent less charting time carrying no denominator or method. No study, controlled evaluation, accuracy benchmark, third party rating or deployment count was located.

Encryption and a full audit trail on every note are stated, and an audit trail is a genuine control that most vendors in this category omit.

Held at C because nothing else is disclosed: no retention schedule for audio or transcripts, no de identification practice and no statement on whether customer content trains models, despite the product ingesting referral documents, medication label photographs and recorded visits across the whole episode.

HIPAA compliance and audit ready records are stated consistently across product materials. Business associate agreement terms are not published for inspection.

A second pass located no named or dated attestation, no SOC 2 report of either type, no HITRUST certification, no ISO 27001 and no trust centre. The vendor describes HIPAA compliant infrastructure, which is a self description rather than an examination, and there is no certification for the health privacy rule in any case.

One published statement deserves close reading, because the qualifier inside it is doing a great deal of work. The company states that patient health information is processed inside its own platform and is never sent to external AI services in a way that would compromise protected health information. That is not a statement that protected health information is never sent to external model services. It is a statement that it is never sent in a way the vendor considers compromising, which leaves the vendor as the judge of precisely the question the buyer is asking. Set against the plainer commitments some competitors in this category now make, either naming their model providers outright or stating flatly that no patient audio or clinical data routes to third party services, this phrasing is conspicuously softer. Ask directly whether encounter audio or transcript reaches any external model provider, which ones, and under what retention terms.

The absence matters more than a small vendor's ordinarily would. This is now a full electronic record holding the complete patient episode, for agencies the company states collectively support more than five hundred thousand patients annually, following a substantial funding round. Custodial scale of that kind is normally where an independently examined posture becomes the procurement baseline rather than a nice to have.

The grade reflects what a counterparty can verify before contracting, not a judgement that controls are absent.

No clearance claimed and no United States device pathway attaches. This axis does not read as an absence on this record, because a real and demanding regulatory framework does govern the product. It simply is not device regulation.

The product completes OASIS, the federally mandated patient assessment instrument for home health. That instrument is not documentation in the ordinary sense. The same answers drive three things simultaneously: the clinical care plan, the payment case mix under the patient driven groupings model, and the publicly reported quality star ratings the agency is measured against. Failures surface as survey findings, claim denials and audit exposure rather than as adverse event reports, and CMS assessment and payment policy is the governing regime.

That makes the incentive question sharper here than anywhere else in this category. Elsewhere in this index a scribe suggesting billing codes is shaping reimbursement for care already delivered. Here the assessment instrument, the payment instrument and the quality instrument are the same artefact, so a system populating its items determines all three at once. The vendor markets accuracy and increased reimbursement together and quotes a coding accuracy figure alongside revenue outcomes. Ask which direction the system resolves ambiguity in when an OASIS item could defensibly be scored two ways.

The stated control is human in the loop by design, with the software drafting, the clinician reviewing and the clinician signing. For a mandated assessment the clinician attests to, that is the right control and it is the same one the rest of this category relies on.

Scope note: this is now a full electronic record for home health rather than a scribe alone, and the company states it is expanding into skilled nursing and hospice, which carry their own mandated instruments. United States only.

On the coding gradient in its home health form, with a defensive framing. PDGM relevant diagnoses are generated, codes are checked and clean claims prepared automatically, and the QA guardrails are described as catching documentation issues BEFORE they impact reimbursement or compliance, which is downside protection rather than revenue maximisation and puts it nearer ScribeEMR than MarianaAI.

What is absent is any independent check: unlike Lime, which places a credentialed coder between the model and the claim, nothing here describes a human with coding credentials reviewing before submission. No fairness statement, subgroup analysis or accent disclosure was located.

A full audit trail on every note is a genuine control that most vendors in this category omit, and it is the reason this sits in the middle band rather than at the floor. An audit trail is what makes a later dispute answerable: it lets an organisation reconstruct what the system produced, what a clinician changed and when, which is the evidence any correction or complaint would need. Against that, the accuracy position is weak and one version detail carries real regulatory weight.

The published figure of 95 percent or better arrives with no methodology, reference standard, denominator or definition of what was measured, and it is the only performance number offered. More consequentially, the product is described as producing fields for a superseded revision of the standardised assessment instrument used in this segment, while the current revision is a later one.

In home based care the assessment instrument is not documentation, it drives payment grouping and quality reporting, so producing an outdated version is a billing and compliance exposure rather than a cosmetic lag, and it falls on the agency submitting rather than on the vendor generating. Establish which revision the product actually produces today, on what release cycle instrument updates ship, and what the vendor commits to when the version is behind. Ask separately for an accuracy figure with a definition.

The vendor makes two claims that sit awkwardly together and names no system to support either. One page states that Enzo connects directly with your existing EHR so notes flow without manual re entry; another states that Enzo REPLACES your legacy EHR and every point solution running on top of it. Those are different products with different implementations, and no named integration, architecture or certification was located for the first. Contrast Lime Health in the same segment, which names six post acute EMRs and specifies bidirectional structured field sync. Establish which of the two propositions is on the table before evaluating.

One genuinely useful property, no residency detail. Enzo states the scribe works in low connectivity, rural locations and spotty signal, which is a real requirement in home health where visits happen in patients' houses rather than clinics and where most cloud dependent tools simply fail. Delivered across web, Android and Android tablet. No hosting region, residency option or sub processor detail was located.

A figure exists but tells a buyer very little. A software directory populated by the vendor itself lists subscription pricing ranging between 500 and 8,000 US dollars a month, a sixteenfold spread with no stated basis, no unit and no tier definition, and no rate card was located on the vendor's own site. A free trial is referenced. Graded C rather than Not Rated because a range is published, but it cannot be budgeted from.

Home health focused and specialised at the level of the regulatory instrument rather than the note template, producing start of care and visit documentation structured for OASIS fields, PDGM relevant diagnoses and care plan goals.

One capability stands out as evidence the product was designed from fieldwork: a clinician can photograph a medication label and have it documented automatically, which is how medication reconciliation actually happens in a patient's home and which nothing else in this index offers. Held at B rather than A because Lime Health covers the same segment with the current OASIS-E2 instrument plus HOPE hospice assessments, and no language coverage is published here.