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.

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.

Not assessed. No named or dated attestation and no trust centre located in this pass.

Not a regulated medical device and none claimed. As with Lime Health, the framework that actually governs this product is CMS assessment and payment policy rather than device oversight: OASIS is a mandated instrument and PDGM is a payment model, so failures surface as survey findings and claim denials.

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.

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.