Clinician hours
Spent on documentation after the visit instead of with the next patient. Visiting nurses charting at midnight to close yesterday's episodes.
Home Health Coding. The closed loop documentation was missing.
OASIS chart review, ICD-10 coding, PDGM case-mix scoring, plan-of-care reconciliation, and survey readiness on one Operating System. Chart orientation and M-item lookups come off your QA and coding desks.
The problem
The playbook you've been handed.
Home health agencies have been trained to scale OASIS and coding accuracy the same way for decades. Add a QA reviewer when accuracy slips. Hire an OASIS specialist when LUPAs climb. Layer a coding vendor on top when PDGM scoring gets unpredictable.
By the time it's all stood up, you don't have a documentation strategy. You have a QA backlog, a coding vendor, an OASIS specialist team, and a survey readiness committee that all touch the same chart and none of which can see what the visiting clinician actually documented in the kitchen.
Here is where it breaks: the model assumes documentation is a clinician problem. It is a workflow problem that clinicians have been asked to solve in cars and kitchens. Every reviewer you add catches errors hours or days after the visit, when the clinical context has already faded and the correction takes longer than the original capture would have.
01
Visit volume rises.
More episodes, tighter PDGM scoring, more survey scrutiny.
02
Hire QA and OASIS specialists.
Slow, expensive, and the experienced talent pool is small in every market.
03
Buy a coding vendor.
Another handoff. The visiting clinician never hears back about what got changed.
04
Repeat.
Every CMS rule update. Every survey cycle. Every payer policy change.
It is not the QA budget. It is what happens between the seams.
When the visiting clinician, the QA reviewer, the OASIS specialist, the coder, and the survey readiness team all touch the same chart through different systems, the visiting clinician is the only one who actually saw the patient. Everyone else is reconstructing the visit from notes typed in a driveway.
The lightbulb
OASIS, coding, and the plan of care are the same encounter.
The visiting clinician captures structured fields in the EMR. OASIS items get filled in based on memory. The coder reconciles the chart days later. The QA reviewer catches inconsistencies after that. The answer is a single Operating System where OASIS review, coding, and plan-of-care reconciliation operate as one closed loop.
Engine 01
OASIS chart review.
M-items reviewed against the clinical narrative. Inconsistencies surfaced before submission.
Closed loop
Engine 02
Home health coding.
ICD-10 codes surfaced from the chart with PDGM case-mix scoring attached. Coder confirms. Plan of care reconciled.
Each OASIS finding, coding query, and survey outcome feeds back into the next chart so the same gap does not repeat.
OASIS chart review · M-item review with the clinical narrative attached
Every assessment reviewed against the chart.
Every OASIS assessment reviewed against the clinical documentation captured during the visit. M-items that conflict with the chart narrative flagged. Items missing supporting evidence surfaced with a draft query for the visiting clinician already prepared.
- 01
Assessment ingested.
OASIS assessment, visit notes, and supporting documentation read from the EMR.
- 02
M-items reviewed.
Every relevant M-item checked against the chart narrative for consistency and support.
- 03
Conflicts surfaced.
Inconsistencies and gaps flagged with chart excerpts and suggested corrections.
- 04
QA reviewer confirms.
Reviewer sees the conflict in context. Confirms the correction or routes a query to the visiting clinician. The art of medicine stays with the clinical team.
Home health coding and PDGM scoring · ICD-10 selection and case-mix accuracy
Primary and secondary diagnoses surfaced from the chart.
Primary and secondary diagnoses surfaced from the chart with supporting evidence. PDGM case-mix scoring calculated against the captured codes. Comorbidity adjustments and clinical groupings applied.
- 01
Documentation read.
Clinical narrative, OASIS, and ancillary documentation reviewed.
- 02
Codes surfaced.
ICD-10 codes recommended with chart evidence, PDGM grouping, and case-mix scoring attached.
- 03
Plan of care reconciled.
Coded diagnoses checked against the plan of care and certification documentation.
- 04
Coder confirms.
Coder reviews the recommendation with full context. Confirms or adjusts. Submits with PDGM scoring locked.
Full home health documentation lifecycle. Survey ready by default.
OASIS, coding, and plan of care on one Operating System.
Same chart. Same evidence model. Same audit trail. Findings from one workflow teach the others.
Documentation gaps caught while the visit is fresh.
Queries route to the visiting clinician within hours, not after the QA cycle has closed and the next three visits have already happened.
Your clinicians and coders make the call.
Ai Workers handle chart orientation, M-item review, and coding suggestion. Your QA reviewers, coders, and visiting clinicians own every submission.
Survey-ready provenance.
Every M-item, code, and plan-of-care reconciliation carries its evidence chain. CMS surveyors and MACs see what they need in one view.
The Glassbox. Every M-item, explained.
The Glassbox
Every recommendation arrives with the supporting documentation, M-item logic, ICD-10 evidence, and reasoning visible. No black box.
Full audit trail
Every M-item review, code, and query documented with chart excerpts, reasoning, and reviewer action. Survey, ADR, and audit ready at all times.
Current OASIS and coding guidelines
OASIS-E and successor versions, ICD-10, and PDGM scoring applied at the version in effect for the date of service.
EMR native
Reads from the EMR your visiting clinicians already use. Homecare Homebase, Axxess, MatrixCare, WellSky, and others supported. No second documentation system for the visiting clinician.
Human in the loop
Ai Workers prepare the work. Your reviewers, coders, and visiting clinicians apply their expertise and make the call.
Continuous learning
Every QA correction, coder confirmation, clinician query response, and survey outcome strengthens future recommendations across the workflow.
The next time someone tells you the answer to your LUPA rate or your survey readiness is more QA hours or another coding vendor, ask what that delivers for the visiting clinician documenting on a phone in a driveway tonight.
Home health documentation should give your visiting clinicians their time back. It should give your QA team accurate charts the first time. It should give your survey readiness leaders an audit defense that already exists, not one that has to be rebuilt after the ADR arrives.