Lime Health AI Review: OASIS Scribe, Intake and Sentinel QA

Lime’s core documentation product captures visits, flags gaps and provides ICD-10 suggestions. The public site names connections with several home health EHRs and describes patient information flowing in and completed documentation flowing back. The published model is assistance for an agency’s clinicians, coders and reviewers, rather than a claim that those roles disappear.

Evaluate the connection with your specific forms and workflow. Ask the field clinician to change a draft, the coder to reject a suggestion and the reviewer to inspect the result in the EHR. Note where each person works and whether edits remain consistent. A list of supported EHR brands is only the starting point; the useful outcome is a completed record that the agency can explain and maintain.

Lime Intake describes monitoring referral portals, fax and email, extracting packet information and applying agency-defined admission criteria. Accepted patients are created in the EMR, while unresolved judgment calls are routed to staff. An intake pilot should therefore test decisions and exception handling as well as document extraction.

Sentinel QA describes automated review of visit notes and surrounding chart material through existing system access, with findings returned to the established workflow. Its page says support starts with Homecare Homebase and additional EMRs are onboarding. This is different from assuming every Lime integration supports every new product. Ask for the currently supported combination of product, EHR and workflow in writing, then test a disputed finding and the escalation that follows it.

Lime’s EMR page is explicit about stages. It labels ambient documentation and associated workflows as shipping, native scheduling and care plans as in development, billing and claims as next, and the complete EMR as the vision. These labels are more useful for procurement than treating an EMR navigation link as proof of a deployed replacement system.

If your agency needs to replace its EHR now, require a current production demonstration of every essential workflow before including a roadmap feature in the decision. If the goal is to add AI while keeping the EHR, assess that present-day package on its own merits. Avoid tying the pilot’s success to an unspecified future migration. Record any promised capability, target delivery date and contractual remedy separately from what the team can use today.

Lime’s pricing page describes volume-based per-chart pricing and a pilot before commitment. It lists integration, onboarding and support among the included elements, and describes virtual staff augmentation. Sentinel QA uses a separate per-review description. No numeric standard rate is published in the reviewed pricing material, so a comparison needs a current written quote.

Define whether an admission, routine visit, recertification and resubmission count as different billable events. If virtual staff are included, specify their duties, hours, response times and access. Ask whether intake and Sentinel are in the same package or separate agreements. Use the agency’s actual monthly mix to compare total cost, including the internal time spent supervising exceptions. That produces a more useful budget than multiplying an unspecified chart rate by an average census.