OASIS accuracy vs. documentation review — what agencies actually need
In home health, OASIS accuracy drives payment through the case-mix that feeds PDGM, so "OASIS coding" and "OASIS accuracy" are the terms every agency searches. But two different jobs hide inside that phrase, and conflating them is where a lot of rework comes from.
Two different jobs
Coding and OASIS review (scrubbing) is the work of assigning and validating the coded values — checking response values against the rules, catching inconsistencies, applying ICD-10 and case-mix logic. Many agencies do this with a dedicated coder or an outsourced coding/review service, and it is a real specialty.
Documentation review is a step earlier: does the visit note actually support the assessment? An OASIS item can be coded to a perfectly legal value and still be wrong — or indefensible in an audit — if the narrative underneath it doesn't back it up. This is a documentation-quality problem, and it starts at the visit, not at the coding desk.
Why the order matters
Coding can only be as good as the documentation it's built on. When the narrative is thin, contradictory, or missing the specific detail an item requires, the downstream effects are predictable: the coder sends it back, the clinician reconstructs details from memory days later, the assessment sits unfinished, and — in the worst case — a value that isn't supported by the record surfaces during a survey or audit.
Raising the quality and completeness of the visit documentation before it reaches coding is the highest-leverage, least-glamorous fix in the whole workflow. It shrinks the rework loop and gives whoever codes the assessment something solid to work from.
Where MediScribe Flow sits — and where it doesn't
MediScribe Flow is a documentation review tool, not a coder and not a scrubber. It does not assign OASIS codes for you, replace your coder or coding service, or guarantee reimbursement, coding accuracy, or that a record will pass an audit.
What it does is make the documentation-quality step fast and visible at the point of care. A clinician dictates the visit; the app drafts the structured document oriented around the current OASIS-E2 items, and — for each item — shows the supporting evidence quoted from the narrative so the clinician can confirm it is actually supported. Items the narrative doesn't support are left blank or flagged for review rather than guessed. A coverage view highlights what still needs attention before the document moves on.
The practitioner reviews and is responsible for every item and any coding. Think of MediScribe Flow as the step that hands your coder or coding service a better first draft — one where every answer is tied to what the clinician actually documented — not a replacement for the coding work itself.