Medical Coding Fraud: What Does the Documentation Actually Support?

Medical coding fraud concerns arise when coding is used to misrepresent care or other facts supporting a claim. A wrong code alone does not establish fraud. The useful starting point is the gap between the submitted claim, the documentation, the applicable billing rule, and what the people involved knew.

For a coder, that gap may appear as pressure to use an unsupported diagnosis, ignore a correction, or select a service level the available record does not justify. Your task in raising a concern is to describe the discrepancy accurately, not to reach a legal verdict from one screen.

When does a coding discrepancy become a fraud concern?

A discrepancy becomes more concerning when the record suggests more than an isolated mistake or an unresolved coding question. Repeated instructions to disregard known documentation problems, for example, deserve a different review from an error promptly identified and corrected.

CMS coding guidance emphasizes that the medical record should support the codes reported. That establishes a practical question for review: what documentation supports the actual claim?

The legal inquiry goes further. Under the civil FCA, knowledge can include actual knowledge, deliberate ignorance, or reckless disregard; specific intent to defraud is not required. That does not mean every billing mistake creates FCA liability. A potential case must satisfy the applicable legal elements.

Our Medicare upcoding guide addresses the specific concern of billing at an unsupported level. This article focuses on how a coding employee can describe and route a broader documentation concern.

Five hypothetical medical coding situations to examine

Reviewing what is missing is often more useful than naming a scheme. The examples below are invented workplace situations, with possible explanations and questions rather than conclusions about liability.

Use this comparison to keep uncertainty visible when preparing a coding review request.

Medical coding fraud red flags compared with questions for documentation review

Situation	Possible explanation	Question to resolve
A diagnosis appears on a claim but not in the record you reviewed.	Relevant documentation may exist elsewhere.	Which authenticated record supports it?
A supervisor requests a higher service level.	The original selection may have overlooked supported work.	What documented facts justify the change?
A corrected claim appears to retain the original error.	The correction may not have reached the final submission.	Which version was actually sent?
A template repeats identical findings across encounters.	Some information may legitimately recur.	Were the individual encounters documented accurately?
A modifier is requested without an explanation.	There may be an applicable billing rule or missing context.	What rule and encounter facts support its use?

A red flag identifies a question, not its answer. The next step is to establish the relevant record and rule, keeping the claim version and dates clear.

Take the corrected-claim example. Seeing an old code in a work queue does not prove that it reached a payer. Conversely, a note saying “corrected” does not establish what was submitted. The distinction between a draft, an internal instruction, and a transmitted claim belongs in the factual account.

How to question an unsupported coding change

Ask for the documentation and reasoning supporting the change. A neutral, specific question is easier to answer than a broad accusation about fraud.

An employee might ask: “Which part of the record supports this diagnosis?” or “Which policy applies to the requested modifier?” These are example questions, not mandatory scripts. They keep the discussion tied to the work and create an opportunity for missing information to be identified.

If the explanation is still unclear, record what was asked and what response was given. Distinguish an instruction to investigate a code from an instruction to submit it regardless of the record. Preserve the difference in your notes rather than summarizing both as pressure.

The most useful coding concern names the claim discrepancy, the supporting record, and the question that remains unanswered.

Do not alter a record to demonstrate that a problem exists. A review should evaluate the evidence as it stands and follow the organization’s authorized correction process.

Which coding facts belong in a lawful evidence checklist?

A useful checklist describes the relevant transactions and decisions without collecting unnecessary patient information. Explain what records exist and how you know about them before deciding whether any document should be shared.

The categories below help separate firsthand observations from assumptions about what happened elsewhere in the billing process.

• The discrepancy: the diagnosis, service description, modifier, or other fact you believe lacks support.
• The record reviewed: what documentation was available to you in your authorized role.
• The claim status: draft, submitted, corrected, denied, or unknown.
• The instruction: who requested a change, when, and the reason given.
• The scope: one event or a pattern you can describe with specific examples.

Keep private identifiers out of an initial informal summary unless they are necessary and the recipient has an appropriate, secure way to receive them. Do not use a personal device or account to bypass access restrictions.

Where a document may contain privileged legal advice or sensitive clinical information, ask qualified counsel about handling it. The existence of a whistleblower concern does not resolve every confidentiality question.

How internal coding review differs from external fraud reporting

An internal coding review asks an organization to examine a claim or process. An external report gives information to an appropriate authority. Neither automatically creates a private lawsuit or establishes eligibility for an award.

The correct external route depends on the payer and subject. A Medicare concern differs from a dispute involving only private insurance. HHS-OIG’s reporting guidance identifies its remit and reporting process. Our healthcare fraud reporting guide helps distinguish common routes.

If you are also concerned about employment consequences, track those events separately. A report about coding and a complaint about retaliation address different conduct. Do not assume an internal investigation resolves the filing requirements for an employment claim.

What medical coding staff should avoid concluding too early

A coding employee should avoid presenting an incomplete observation as proof of intent, a final claim submission, or a legal violation. Accuracy strengthens a concern more than an alarming label does.

A useful report says “I could not find supporting documentation in the records available to me,” rather than “No documentation exists anywhere.” It says “I was instructed to change the code,” rather than “The payer was billed,” when the submission status is unknown.

It is equally important to include a correction or explanation that resolves the issue. A factual account is not weakened by acknowledging that some examples were legitimate. That distinction helps a reviewer focus on the remaining discrepancies.

For context on other billing patterns, see our Medicare fraud examples. Use the examples to frame questions, not to assign a legal label to an encounter without examining its facts.

Medical coding fraud questions

Questions about coding fraud usually concern the difference between a mistake, an unsupported claim, and a reportable pattern. These answers keep that distinction at the center of the review.

What is medical coding fraud?

It is the use of coding to misrepresent facts relevant to billing or payment in circumstances that meet an applicable fraud standard. Whether a particular code does so requires the record, the billing rules, and the surrounding knowledge to be assessed.

How does medical coding fraud differ from upcoding?

Upcoding concerns billing at an unsupported higher level or for a more intensive service. Medical coding concerns can involve other discrepancies too, such as an unsupported diagnosis or modifier; not every discrepancy is fraudulent.

How do you report healthcare fraud involving coding?

Identify the payer, the discrepancy, and the facts you can support, then use the appropriate reporting channel. Avoid unnecessary patient-data disclosure, and distinguish a regulatory report from a potential civil action.