Billing Company Fraud: Diagnosis Changes After a Denial

Medical billing company diagnosis code fraud occurs when a billing service knowingly substitutes a false diagnosis to get a claim paid. For someone working denied claims, the instruction may arrive after Medicare or Medicaid has already refused payment. You know what the original claim said, what changed and who wanted it changed. Those decisions inside the billing company can be central to a physician billing fraud case.

What Changed After the Denial?

The central comparison is the diagnosis supported by the patient’s record against the diagnosis used on the resubmitted claim. The denial explains why payment stopped. The edit shows what the billing service changed to try again, and the payer’s response shows what happened next.

That sequence sits inside the ordinary work of collecting payment for health care. Health Care Administration: Managing Organized Delivery Systems, published by Jones and Bartlett Publishers in 2011, describes a revenue cycle running from registration and coverage checks through coding, denial follow-up and receipt of payment. Its discussion of denied claims being corrected and refiled explains why the billing office returns to a claim after the first submission. It also identifies the gap: staff submitting claims may lack the clinical information needed to correct them.

For an insider, the useful question is where the replacement diagnosis came from. We examine the clinical information available to the biller, the reason given for the change and the instructions that connected it to resubmission. When a claim rests on a false clinical premise, that same comparison reaches medical necessity fraud.

Who Could Change the Diagnosis Code?

A healthcare billing company can prepare and resubmit a claim for care someone else delivered. The person who treated the patient, the employee who edited the claim and the manager who approved the instruction may occupy different parts of the business. We trace those roles separately, including what each person saw before the claim went back to the payer.

The chapter Implementing a Physician Practice Compliance Program in the same textbook identifies coding assumptions made without adequate medical documentation, particularly when someone other than the physician chooses the code. It also identifies improper changes to existing medical records and the need to review a billing company’s automated software.

A changed diagnosis on the bill and a changed diagnosis in the medical record leave different questions about who entered the information and why. We look at both versions and the authority behind each change, rather than assigning the billing decision to whoever signed the original clinical note.

We ask what staff had permission to change, what the software did and what clinical information was required. An employee who knows how denied claims were handled may be able to explain the instruction behind a repeated change.

Medical Business Service and the Rejected Radiology Claims

Medical Business Service agreed to a $1,950,000 settlement over allegations that it changed diagnosis codes on denied radiology claims to bypass Medicare and Medicaid coverage restrictions. The Justice Department’s October 2014 announcement concerned alleged conduct from 2008 through 2010. A whistleblower brought the False Claims Act case against the radiology billing company.

The whistleblower’s complaint described employees changing diagnosis codes across stacks of denied claims without referring to medical records. According to the complaint, they used a commercially published diagnosis codebook. Just the codebook.

The complaint also attributed a blunt instruction to a manager:

We see the absurdity in that alleged instruction: the claim had to get paid, but the patient’s record had dropped out of the decision. The collections target was driving the diagnosis. For someone working the denial queue, the complaint describes pressure from inside the business to find a diagnosis that would unlock payment.

The whistleblower also alleged that the company’s Duluth operations center employed no certified coders and provided employees no coding training. It gives us a concrete question about the operation: what was staff being taught to do when a claim came back unpaid?

The complaint extended the allegation beyond the company’s own employees. It alleged that records showed a Technosoft employee changing diagnoses on denied claims without supporting clinical information. That makes the handoff between billing organizations part of the story, with the same question at each stage: who supplied the diagnosis that reached the government?

The settlement resolved allegations against Medical Business Service. We examine the contracting radiologists’ knowledge separately by asking what information reached them, what changes they authorized and what instructions they gave.

Medical Reimbursement Systems and the Warning That Came First

Medical Reimbursement Systems accepted responsibility for seeking a TRICARE bonus for a physician practice that did not qualify. The Justice Department announced its $500,000 settlement in January 2016. Here the payment premise was geographic eligibility for a Health Professional Shortage Area bonus.

The bonus added 10% to eligible payments. An employee warned management in 2009 that the Watertown practice did not qualify, yet the bonus billing continued through October 2014. The warning went in writing to a vice president, and the claims kept going. The company acknowledged that seeking the bonuses for the practice was inappropriate.

The billing company was paid a percentage of net collections. That arrangement tied its compensation to the money collected for its client. We would put the contract beside the warning and the later bonus claims: the commercial incentive, the information management received and the billing that followed all belong in the same account.

For a billing-company employee, the parallel with Medical Business Service is the decision to pursue payment using a false premise. One case concerned alleged diagnosis substitutions after rejection. The other concerned continued certifications for a geographic bonus after an internal warning. Each turns attention to the vendor’s own role in preparing claims for government money.

What Evidence Does a Whistleblower Need?

Useful evidence connects the original clinical record, the denied claim, the change, the resubmission and the people who understood the difference. A coder may know how the diagnosis was selected. A billing employee may know why the claim was returned to the payer, while a manager or compliance employee may know what warning reached the person controlling that work.

In its 2017 article Busting Bad Medicine: a Call to Action Addressing Healthcare, Fraud, Waste, and Abuse, the Journal of AHIMA recommends comparing billing with the health record’s treatment date, treatment and signature. It also emphasizes witnesses who can explain what happened. The records and the person who understands the workflow supply different parts of the account.

For diagnosis changes after a denial, we connect these pieces:

• The original claim and denial: the diagnosis submitted, the service billed and the payer’s stated reason for refusing payment.
• The clinical record: the diagnosis and treatment documented for that encounter, with the relevant dates and signatures.
• The edit and its authority: the original and revised versions, any available edit history, and the instruction or clinical information offered to support the change.
• The resubmission and payment: what went back to the payer and whether the revised claim produced a payment.
• The warning and the response: who received the concern, what it identified and whether the same billing continued afterward.
• The collections arrangement: how the vendor earned its fee and how management connected staff decisions to getting claims paid.

The Medical Business Service complaint makes the payment end of that sequence concrete. It alleged particular resubmissions with falsified diagnoses followed by Medicare payments. A denial log explains why a claim stalled, while the revised claim and payment record connect the changed diagnosis to government money.

Written procedures matter alongside the transaction records. A billing-system manual can describe how edits are supposed to operate, while an employee’s account can explain the instructions actually given. We examine those instructions against the clinical documentation and the claims they produced.

When the Payment Target Drives the Diagnosis

We want to know who chose the unsupported diagnosis, who approved it and how it reached Medicare or Medicaid. Those are the connections we develop with someone considering a physician practice qui tam case. We work through the false information, its effect on government payment and the knowledge inside the billing operation. A whistleblower case under the False Claims Act can pay 15% to 30% of what the government recovers.

You Know Why the Diagnosis Changed

If you worked the denied claims, saw diagnoses replaced or warned management about unsupported billing, speak with our whistleblower experts about the decisions behind those claims. We build the case with you around the clinical records, the billing instructions and the government payments, and bring in medical billing fraud whistleblower lawyers who understand outsourced collections. We stay beside you as your knowledge of the billing operation becomes the foundation of your case.