Lime Health AI

Ambient capture and structured assessment generation are the product, and the company's stated trajectory runs outward from the scribe into a full AI native EMR for home health, on the argument that every ambient visit already produces the structured data an EMR stores. The certified coder review layer is verification of model output rather than a services business the AI was added to.

The most complete oversight architecture located in this index, and it edges the others on one word: default.

A certified home health coder verifies every OASIS item, ICD-10 code and visit detail before anything syncs to the EHR, and the vendor states explicitly that this clinician in the loop review is standard with every engagement rather than an upsell. Every other human review vendor here, Speke, ScribeRyte, Scribble and Commure, sells verification as a tier a buyer may decline.

Three further elements complete it. The reviewer is a credentialed domain specialist rather than a general scribe, which matters when the artifact is a CMS assessment. Real time quality checks flag missed OASIS sections and weak narratives while the clinician is still in the home, so gaps are fixed at source rather than by a return visit. And the review is audit logged, producing a trail of what was checked.

Coding is also positioned explicitly as a co pilot suggesting codes for review rather than replacing human judgement.

One genuinely useful architectural feature: ICD-10 suggestions are delivered with clinical evidence mapping, showing which parts of the documentation support each code. That is the same traceability principle that earned Abridge credit for Linked Evidence, and it is rarer in coding than in note generation.

Against that, no accuracy figure, model card, named models or evaluation methodology was located, and the vendor's own time saving claims are inconsistent, appearing as a 75 percent reduction in documentation time in one place and 50 percent in another.

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. The human tier is at its maximum on this record and that is the point worth carrying into diligence.

Because coder verification is universal rather than optional, a human workforce reads one hundred percent of charts rather than a subset the buyer chose, so every encounter this product touches is read by a person as a matter of design. That is the price of the oversight strength recorded elsewhere on this record and the two should be evaluated as one decision.

None of that workforce is enumerated: not where it sits, not whether coders are employees or contracted, not how they are vetted, and not whether review happens onshore. An audit logged review trail exists, which records that access occurred without telling a buyer who holds it. Ask for the list of entities and countries whose staff read charts, and for a sub processor list covering the automated path.

Third party review presence on G2 including a named medical coder and OASIS reviewer, which is a venue the vendor does not control. Beyond that, claims of two to three hours saved daily and elimination of after hours charting carry no denominator, cohort or method, and no study, controlled evaluation, accuracy benchmark or named agency customer was located. Graded C on the standing precedent that adoption and testimony are not evidence of benefit.

The audit logged review trail is a real control and a signed business associate agreement is stated plainly rather than implied. The tension worth naming is the same one this index flagged for Speke, at its maximum here: because coder verification is universal rather than optional, a human workforce reads one hundred percent of charts, not a subset a buyer chose. That is the price of the autonomy A above, and the two should be evaluated together. Nothing was located on where that coder workforce sits, on audio or transcript retention, or on whether customer content trains models.

States HIPAA compliance and a signed business associate agreement directly, alongside audit logging. Specific terms are not published for inspection, and buyers should confirm the agreement covers the certified coder review workforce and not only the software.

A second pass located no SOC 2 report of either type, no HITRUST certification, no ISO 27001, no penetration testing statement and no trust centre. Enterprise grade security remains a marketing phrase rather than a standard.

What the second search did establish makes the absence matter more here than it would for a comparable vendor, and it comes from the service model rather than from the software. Every note this product generates is reviewed by a credentialed home health coder before it reaches the customer's record system. The vendor presents that as standard with every engagement rather than as a paid upgrade, and as a quality control it is a genuine strength.

It also means the vendor employs or contracts people whose job is to read patients' clinical documentation at scale, routinely and by design. That is a materially larger internal access surface than a pure software vendor carries, and it is precisely the territory an independent examination covers: how staff are vetted, how access is provisioned and revoked, what a reviewer can see beyond the note in front of them, whether that access is logged, and what happens when a reviewer leaves.

None of it is answerable from published material. The coding credential held by reviewers speaks to their competence at coding and says nothing about the controls governing their access to patient information.

Ask for the report and its scope, and separately for the access control model covering the review workforce, including where those reviewers sit and whether they are employees or contracted.

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

The instruments involved are federally mandated. OASIS-E2 is the home health patient assessment, HOPE is its hospice counterpart, and the patient driven groupings model is the methodology home health is reimbursed under. Accuracy failures surface as survey findings, claim denials and audit exposure rather than as device incidents, and CMS assessment and payment policy is the governing regime.

That produces an incentive structure sharper than the coding boundary elsewhere in this category. Across most of this index a scribe suggesting billing codes shapes reimbursement for care already delivered. Here the same answers serve as the clinical assessment, as the payment case mix, and through publicly reported quality measures as the agency's own quality score. One artefact drives three outcomes, and software populating its items determines all three at once. Ask which direction the system resolves ambiguity where an assessment item could defensibly be scored two ways.

HOPE deserves separate attention because it is recent. It replaced the previous hospice assessment instrument in 2025, so any tool completing it works against a young instrument carrying less accumulated interpretive guidance than OASIS has. Establish how the vendor keeps pace as that guidance develops, and what happens to documentation generated against a superseded version of either instrument.

On the coding gradient, with the strongest counterweights of any vendor on it.

The gradient language is present: ICD-10 codes are described as validated for PDGM optimisation, and PDGM grouping determines what an episode pays, so optimisation is not a neutral word.

What sits against it is unusual. Codes are mapped to the clinical evidence supporting them, so a reviewer can see why each was suggested. Coding is stated to be a co pilot rather than a replacement for human judgement. And a credentialed coder verifies every one before submission, which puts an independent professional between the model's suggestion and the claim, the exact checkpoint this index found missing at OmniMD and MarianaAI.

The vendor also publishes a decomposed accuracy claim, which is more than most in this tier offer. Structured assessment items are said to approach 99 percent because the model has explicit field mappings, while narrative sections approach 95 percent on first generation. Stating a mechanism for why two parts of the same output differ is a real disclosure habit and it is credited here.

It does not move this grade, for two reasons. The decomposition is by task type rather than by population, and what this axis asks is how performance varies across speakers and settings rather than across output formats. And the figures are vendor generated, with no methodology, denominator or independent validation published, so they are claims rather than measurements.

No fairness statement and no performance breakdown by speaker characteristic was located, and language coverage is English and Spanish only. For a workforce visiting patients in their own homes, frequently elderly and frequently with speech affected by illness, that is the breakdown which would matter most.

Two mechanisms here are among the better ones in the lane and they work together, which is why this sits at the top of the middle band. The first is traceability applied to coding, which is rarer than traceability applied to notes: diagnosis code suggestions are delivered with clinical evidence mapping showing which parts of the documentation support each code.

That converts a coder's review from a trust exercise into a checkable one, and it is the same principle that earns credit elsewhere in this index for mapping generated text back to its source. It matters more in coding, because a wrong code shapes what is billed and creates false claims exposure for the organisation submitting it, and a coder who can see the supporting documentation can refuse a suggestion on the evidence rather than on instinct.

The second is that human coder verification is universal rather than optional, so unlike peers where review is a paid tier or a sample of unknown size, the correction step covers every chart. A correction mechanism with known coverage is worth considerably more than one with unknown coverage. An audit logged review trail and a signed business associate agreement complete the position. Held at C because nothing stands behind the output.

No accuracy figure or evaluation methodology was located, the vendor's own time saving claims are inconsistent at 75 percent in one place and 50 percent in another, and no warranty, indemnity or remediation commitment was found. Ask for a coding accuracy figure measured before verification, since that is what the verification is correcting.

Effectively complete coverage of one segment's EMR market, with the depth that matters. As of mid 2026 Lime integrates bidirectionally with WellSky, MatrixCare, HCHB, Axxess, DSL and Netsmart, which between them account for the overwhelming majority of home health and hospice agencies.

More importantly it syncs structured OASIS fields and care plans rather than pushing narrative text, which is the difference between a scribe that saves typing and one that completes the regulatory instrument. Verified notes sync ready for billing with, in the vendor's phrasing, zero rework.

Not previously assessed, and the second pass changes what the question is rather than simply answering it.

The conventional gaps remain. No hosting region is stated, no residency option is offered, and no subprocessor list was located. Nothing establishes whether encounter audio or transcript is processed by a third party model service, which provider that would be, or what it retains. Delivery is cloud based, with capture through a mobile application used inside patients' homes and native integration into the major post acute record systems.

The material fact for this axis is not architectural. Every note passes through a credentialed human reviewer at the vendor before it reaches the customer's record system. Data residency is normally a question about which jurisdiction's servers hold the data and therefore whose authorities can reach it. Here there is a second and more immediate answer: the documentation is read by identifiable people working for the vendor, and where those people sit is a residency fact in its own right. A note reviewed by a person in another country has crossed a border regardless of where the database lives.

That is not a criticism of the model, which is a real quality control and is offered as standard rather than as a paid extra. It is a scoping point a buyer will not find on an architecture diagram and is unlikely to think to ask about.

Ask three things: the hosting region and whether it can be pinned by contract, which model provider processes the encounter, and where the review workforce is located. The last of those may matter more than the first two.

No published rate card, tier structure or pricing model located. The mobile application is free to download but the platform is sold to agencies through a demo led process. Worth noting for comparison purposes that the price necessarily includes human coder review of every chart, so it is not comparable with software only per clinician rates elsewhere in this category.

Deep in a setting this index otherwise barely reaches, and specialised at the level of the regulatory instrument rather than the note template. Coverage spans home health and hospice for nurses, therapists and field clinicians, generating OASIS-E2 assessments, HOPE hospice evaluations, daily visit notes, care plans and ICD-10 coding, with PDGM and homebound status documentation handled as first class concerns.

The vendor's own argument is the right one: an ambient tool that produces only SOAP notes does not serve this setting, because the document that matters is a structured CMS assessment. English and Spanish. Mobile and iPad first, which suits clinicians documenting in patients' homes rather than at a workstation.