HealthSplash’s $1B Fraud: What It Means for DME Coding Compliance

On October 15, 2026, the Department of Justice announced that Brett Blackman, the founder and CEO of health care software company HealthSplash, was sentenced to 19 years in prison for his role in a scheme that billed Medicare and other federal health programs more than $1 billion for orthotic braces and related durable medical equipment (DME). The Department of Justice press release details a scheme that ran on paperwork that looked clean on its face — until investigators pulled the thread on how those orders were actually generated.

For DME suppliers, orthotics coders, and the compliance teams that support them, the case is less a cautionary tale about one bad actor than a preview of exactly where auditors are looking in 2026 and 2027: the gap between a signed physician order and whatever actually happened with the patient.

What the Scheme Actually Looked Like

According to DOJ, HealthSplash acquired an internet-based platform called Power Mobility Doctor Rx (DMERx) in 2017 and used it to generate doctors’ orders for orthotic braces and other DME at scale. Telemarketing networks and foreign call centers pushed Medicare beneficiaries to accept multiple braces, often with little or no interaction between the beneficiary and the prescribing physician. Physicians were paid per signed order — in some cases without ever speaking to the patient at all — and the group edited orders to strip out references to telemedicine before submitting claims, specifically to avoid triggering a Medicare audit.

The numbers are what make this case stand out even in a field full of fraud settlements: Medicare was billed for braces for more than 346,000 beneficiaries, averaging four braces each, with at least 21 billed to each of over 1,200 people. Codefendant Gary Cox was separately sentenced to 15 years in December 2025.

Why This Matters Beyond One Fraud Case

The Documentation Trail Is the Whole Case

Every element DOJ cited — the absence of a real physician-patient interaction, the post-hoc edits to orders, the sheer volume of braces per beneficiary — is a documentation pattern, not a coding error. That distinction matters for compliance teams building audit defenses: a technically correct HCPCS L-code on a clean-looking order does not protect a claim if the underlying medical necessity documentation doesn’t hold up to scrutiny.

Telehealth-Originated Orders Draw Extra Scrutiny

CMS and OIG have flagged telehealth-generated DME orders as a recurring audit target since the pandemic-era expansion of telehealth billing flexibilities, and this case shows why: the orders in question were specifically edited to obscure their telemedicine origin. Any practice or supplier still relying on third-party telehealth platforms to generate DME orders should expect that relationship itself to be part of an auditor’s checklist.

The pattern lines up with several things CMS and OIG auditors are already trained to flag, including:

• Unusually high brace-per-beneficiary ratios compared to regional or specialty norms
• Orders generated through a third-party platform rather than the treating physician’s own EHR
• Little or no documented physician-patient interaction supporting medical necessity
• Marketing or lead-generation arrangements tied to referral volume
• Orders edited or resubmitted shortly before claim submission

Practical Takeaways for Coding and RCM Teams

None of this requires a new coding guideline to act on. Compliance and coding leads can tighten their own posture now by auditing a sample of DME orders for a documented physician-patient encounter prior to signature, flagging any supplier or ordering relationship that routes through a third-party telehealth platform, and confirming that medical necessity notes — not just the signed order — are retained and retrievable if a payer or OIG request comes in. Coders reviewing high-volume orthotic or DME claims should treat a lack of clinical context around the order as a red flag worth escalating, not a formatting issue to code around.

The HealthSplash case is also a reminder that these schemes rarely stay contained to one company. DOJ noted that HealthSplash’s platform connected pharmacies, DME suppliers, marketers, and telemedicine companies into a single referral network — meaning any organization that did business with a platform like DMERx, even without knowledge of the underlying fraud, could face its own documentation review.

The Broader Compliance Lesson

Federal fraud enforcement in 2026 continues to center on the same question coding teams should be asking internally: does the paper trail actually reflect what happened with the patient? As Assistant Attorney General Colin M. McDonald noted in the DOJ release, the scheme was built to “steal as much as possible from the Medicare trust fund” — and it took a 23-day jury trial and a multi-agency investigation involving HHS-OIG, the FBI, VA-OIG, and DCIS to unwind it. For coding and compliance teams, the more realistic goal isn’t catching fraud at that scale — it’s making sure routine DME and orthotics documentation never resembles the pattern DOJ just spent years prosecuting.

Keeping that documentation trail clean, consistent, and audit-ready across thousands of claims is exactly the kind of work that benefits from automation built around coding accuracy rather than volume alone. Medikode’s automated medical coding platform is built to help coding and compliance teams maintain that level of consistency at scale.