OIG’s Deistic Home Health Audit Is a Case Study in Coding Automation Gaps

The HHS Office of Inspector General published a Medicare home health agency provider compliance audit on August 6, 2026, covering Deistic Home Health Care, Inc. (Report No. A-05-24-00007, posted August 10). Of 100 sampled claims, only 63 fully complied with Medicare billing and coding requirements. The other 37 failed for reasons that will sound familiar to any coding or compliance team: documentation that didn’t support the codes billed, and encounters that didn’t meet Medicare’s face-to-face requirements before a plan of care was certified.

The dollar figures are modest by OIG standards — an estimated $43,074 in net overpayments against $15.3 million in Medicare payments reviewed for the audit period — but the failure pattern is not modest at all. It’s the same pattern that shows up across specialty coding, outpatient billing, and now home health: claims get submitted before anyone checks whether the documentation actually supports them.

What the Audit Found

According to OIG’s published report, the errors broke down into two categories: 36 claims failed to meet Medicare billing and coding requirements, meaning the codes submitted weren’t supported by what was in the medical record, and 5 claims did not meet Medicare’s face-to-face encounter requirements, which mandate that a physician or allowed practitioner document an in-person encounter related to the primary reason for home health care before certification. Four of those claims had both problems at once.

OIG’s stated root cause was direct: Deistic “did not always review medical record documentation to prevent the incorrect billing of Medicare claims.” The agency recommended Deistic refund the estimated $43,074 to the federal government. Deistic did not comment on the draft report and voluntarily terminated its Medicare provider agreement on August 1, 2025 — before the final report was even issued.

Why This Keeps Happening in Home Health

Face-to-face documentation is a timing problem, not just a content problem

The face-to-face requirement isn’t just about whether an encounter happened — it’s about whether the encounter is documented, dated, and tied to the certifying diagnosis before the claim goes out the door. When that link is loose (an encounter note filed late, a diagnosis that doesn’t match the plan of care, a certifying physician who wasn’t the one who saw the patient), the claim can look complete on submission and still fail an audit months or years later.

Coding requirement failures are a documentation-review problem

OIG’s finding that 36 claims lacked documentation to support the billed codes is not a story about coders making things up. It’s almost always a story about coders working from incomplete charts, under production pressure, without a systematic check between what the clinician wrote and what got billed. Manual chart review can’t scale to catch this consistently across thousands of home health episodes a year — which is exactly why OIG keeps finding it, agency after agency, audit after audit.

This Isn’t an Isolated Finding

OIG’s home health compliance audit program runs continuously, and Deistic is one of a rotating set of agencies reviewed each cycle. It follows a similar pattern to OIG’s August 3, 2026 report finding an estimated $15.2 million in improper Medicare payments for sacroiliac joint injections — different care setting, same underlying failure: coding and billing proceeding without a documentation check that would have caught the mismatch before the claim was submitted. Across both audits, the gap isn’t clinical judgment. It’s the review step between documentation and code selection.

Where Automated Coding Validation Closes the Gap

The specific failure types OIG cited in the Deistic audit map closely to checks that automated, documentation-aware coding systems are built to run before a claim ever reaches a payer:

• Documentation-to-code matching — flagging when a billed code isn’t supported by anything in the chart, rather than relying on a coder to catch the gap manually.
• Face-to-face encounter presence checks — confirming a qualifying encounter exists, is dated appropriately, and is tied to the certifying diagnosis before certification is finalized.
• Certifying-provider consistency checks — verifying the practitioner who documented the encounter matches the one certifying the plan of care.
• Pre-submission holds — routing claims with unresolved documentation gaps to review instead of letting them go out and surface as overpayments a year later.
• Audit-ready evidence trails — keeping the documentation link for every code visible and retrievable, so a compliance team isn’t reconstructing support after the fact when OIG comes calling.

None of this requires clinical judgment an algorithm shouldn’t be making. It requires consistency: applying the same documentation check to claim number 1 and claim number 10,000, every time, before submission rather than after an auditor samples 100 claims and finds 37 that don’t hold up.

What Compliance Teams Should Take From This

The Deistic audit is a useful reminder that home health agencies of every size are subject to the same documentation-support standard as hospitals and specialty practices — and that OIG’s sampling methodology means a 37% error rate on 100 claims extrapolates to real financial exposure. Agencies that rely on manual chart-to-code review as their only safeguard are, in effect, betting that human review will catch what a systematic check would catch automatically. OIG’s report record suggests that bet doesn’t pay off often enough.

Documentation-to-code validation, face-to-face and encounter-requirement checks, and audit-ready evidence trails belong in the coding workflow itself, so gaps like the ones OIG found at Deistic surface before submission — not after an audit sample finds them. That’s the workflow behind Medikode’s automated medical coding platform.