The first AI-native EMR,
built from the ambient up.

Every EMR today was designed around forms. Lime is building an EMR designed around the patient encounter itself — where documentation writes itself, coding suggests itself, and compliance checks happen in real time.

Why now

Every home health EMR was built for a world without AI.

WellSky, HCHB, MatrixCare, Axxess — they're good at what they were built for: electronic forms, scheduling, and billing. But they were designed decades ago, before ambient AI was possible. Bolting AI onto a form-first EMR produces marginal gains. Rebuilding the EMR around AI is a step change.

Form-first

Legacy EMRs center the clinician on a screen full of checkboxes. The patient becomes secondary to the documentation.

Post-visit charting

30-45 minutes of documentation after every visit — most of it completed after hours, driving burnout and turnover.

AI as an afterthought

Legacy EMRs are retrofitting AI — a widget here, a button there. It's lipstick on decades-old architecture.

The path from Scribe to EMR

We didn't start by building an EMR.
We started by listening.

Lime Scribe is the foundation. Every ambient visit we capture is structured data — assessments, diagnoses, interventions, goals. That structured data is exactly what an EMR stores. The EMR is what that data becomes when you connect it to scheduling, billing, compliance, and reporting.

01
Today — Shipping

Ambient Scribe + AI Documentation Platform

Lime Scribe captures the patient encounter and auto-generates OASIS, HOPE, visit notes, and ICD-10 codes. OASIS QA, clinical notes, and admissions automation layer on top. Everything syncs natively to your existing EMR — WellSky, MatrixCare, Axxess, HCHB, DSL.

This is where every agency starts with Lime today.

02
In Development

Native Scheduling, Visits, and Care Plans

As the ambient platform matures, Lime is bringing scheduling, care planning, visit tracking, and case management into the platform itself. Agencies can run more of their day-to-day in Lime instead of flipping between tools.

03
Next

Billing, Claims, and PDGM Optimization

With documentation, coding, and QA already happening inside Lime, billing and claims are a natural extension. Clean claims flow directly from ambient-captured visits — no manual data rekeying, no lost charges, no chasing down OASIS corrections at end-of-episode.

04
The Vision

Lime EMR — The First AI-Native EMR for Home Health

A complete EMR where the clinician talks to the patient and the system does the rest. No forms. No after-hours charting. No 45-minute OASIS assessments. Ambient capture is the primary input — scheduling, documentation, coding, QA, billing, compliance, and analytics are all downstream of the visit itself.

What this means for agencies today

You don't have to wait for Lime EMR.
You can start building toward it now.

Every agency using Lime Scribe today is compounding value. The ambient visits you capture now are structured exactly the way the future Lime EMR needs them — so when more EMR functionality ships, you don't migrate, you expand.

Start today

Deploy Lime Scribe alongside your current EMR. Clinicians save 2-3 hours per day on documentation. OASIS time drops from 45 minutes to under 10. ROI shows up within the first month.

No rip-and-replace

Lime is designed to run alongside WellSky, MatrixCare, Axxess, HCHB, and DSL today. There is no "rip and replace your EMR to use Lime." The transition toward full EMR functionality will be agency-driven and gradual.

Data portability

Everything Lime captures is yours. Ambient visits, OASIS data, ICD-10 codes, and QA results are stored in open, portable formats — and sync natively to your current EMR. When Lime EMR is ready, your data is ready.

Early-partner status

Agencies that start with Lime now are shaping the roadmap. You'll have direct input into which EMR features ship next and how they work — and you'll be first in line when Lime EMR launches.

The design principles

What makes an EMR AI-native?

These are the principles guiding how we're building Lime EMR. Every design decision gets tested against them.

01

Ambient-first, not form-first.

The patient encounter is the primary input. Forms exist only as a fallback for edge cases — not as the center of the workflow. If a clinician is clicking through screens during a visit, we've failed.

02

Home health and post-acute from day one.

Lime EMR is not a general-purpose medical EMR. It's built specifically for OASIS, HOPE, PDGM, homebound status, skilled need, episode management, and all the workflows unique to home health and hospice.

03

Real-time QA, not retrospective.

Documentation gaps, OASIS inconsistencies, and coding errors get flagged during the visit — not three days later when the patient is already home. AI-native means closing the loop instantly.

04

Mobile-first. Field-first.

Home health clinicians work from smartphones and tablets in patient homes, cars, and parking lots. Lime EMR is built for that reality — not ported from a desktop-first design.

05

Open, portable, interoperable.

Your data stays yours. Lime EMR will support FHIR, open export, and bi-directional sync with existing EMRs — so agencies can migrate at their own pace, not ours.

Want to shape what
Lime EMR becomes?

The Lime team is talking directly with agencies about the EMR roadmap. If you're interested in being an early partner — or just want to understand where Lime is headed — book a 30-minute call.

Book a 30-minute call to learn about the Lime EMR roadmap.

Book a Demo