Guide

Your NPDB file: disputes, statements, and what stays visible

Summary

Yes, you can dispute an NPDB report and you can attach a Subject Statement to it, but the two do different jobs. A Subject Statement is your account, added to the report and shown to everyone who queries it. A dispute contests whether the report is factually accurate or was even reportable; it never re-argues the underlying board or malpractice action. A disputed report stays visible while it is reviewed, so both tools manage the record rather than erase it.

By Gale Editorial · Updated 2026-07-27. Every figure cited to a dated source. How we write.

Can you dispute or annotate an NPDB report about you?

Yes, and you actually have two separate tools that do different things. A Subject Statement is your own account of the matter, attached to the report so that everyone who later queries it reads your side alongside the reporter's. A formal dispute is a challenge to whether the report is factually accurate or whether it should have been filed at all. One adds context; the other contests the record.

Start from what neither tool can do, because that saves wasted effort. A dispute is narrow: it reaches factual accuracy and whether the matter was reportable, not whether the underlying action against you was fair. And neither tool simply deletes a report that is accurate and was properly filed. The reporting entity, and if needed the Secretary's dispute-resolution process, are who decide a dispute, not you and not the querier. Knowing that boundary keeps your effort aimed where it can actually work.

Subject Statement vs dispute: what each one does

The two tools sit at different levels of the record, and choosing well depends on what is actually wrong. A Subject Statement never changes the report; it permanently attaches your narrative so future queriers see it. A dispute asks that the report be corrected or voided because it is inaccurate or was not reportable. You can use one, the other, or both, but they answer different questions about the report.

ToolWhat it doesWhat it cannot do
Subject StatementAttaches your written account; shown to every querierChange, correct, or remove the report
DisputeContests factual accuracy or whether the matter was reportable; can lead to a correction or a voidRe-argue the merits of the underlying action

The practical read: if the report is accurate but you want context, use a Subject Statement. If a fact in it is wrong, or it describes something that was never reportable, dispute it. If the report is accurate and you simply disagree with the discipline behind it, neither tool is your remedy, and pointing them at the merits wastes the one narrow opening you have.

What a dispute cannot do: it is not a merits appeal

The single most useful thing to understand is what a dispute is not. It is not an appeal of the underlying action. A dispute can fix a report that is inaccurate or that never should have been filed, but it cannot overturn the board order, settlement, or privilege decision the report describes. Other systems give you a merits appeal, Medicare's post-payment audits, for instance, run through a five-level appeals process 1, but the Data Bank is not one of them.

Keeping appeal, grievance, dispute straight is what keeps your effort aimed correctly: an appeal seeks to change an outcome, a grievance complains about how a process was run, and an NPDB dispute contests only the accuracy or reportability of a filing. The place to change the outcome is the original forum, the board hearing, the court, or the hospital peer-review process. Because the report follows the outcome of that action, correcting the action is what ultimately corrects the report; the dispute cannot do that work for you.

Who sees the report while it is disputed

A dispute does not hide the report. While it is under review, the report stays visible to queriers, flagged as disputed and accompanied by any Subject Statement you added, so the people credentialing you see both the report and your challenge to it. This matters because credentialing bodies query the Data Bank routinely, work within a verification aging window, and recredential you on a recurring cycle, so the report surfaces again and again until it is resolved 2.

What appears depends on what was filed. Board actions, including consent orders, along with certain malpractice payments and privilege actions, all reach the Data Bank, and a license surrender is a report too, so ending a case by surrendering does not keep it off your file. That is exactly why a Subject Statement earns its place: it travels with the report to every future querier, so even a report you cannot remove arrives with your account attached rather than standing alone.

The dispute sequence, step by step

Work a disputed report in order, because a narrow, factual challenge succeeds far more often than a broad one. Start with the npdb self-query so you see exactly what was reported, word for word. Then contact the reporting entity directly and ask it to correct or void the report, since the reporter can amend its own filing fastest. If it refuses, file the formal dispute, add a Subject Statement, and escalate to the Secretary's dispute-resolution process.

  • Self-query first. See the exact language before you argue with it; you cannot dispute what you have not read.
  • Go to the reporter before the process. The entity that filed the report can correct or void it directly, which is faster than a formal review.
  • Keep the dispute narrow. Contest a specific inaccuracy or the reportability of the matter, not the fairness of the discipline behind it.
  • Attach a Subject Statement in parallel. Whether or not the dispute succeeds, your account then travels with the report.
  • Bring in counsel for a high-stakes report. When the report threatens your panels or privileges, discipline-and-credentialing counsel helps frame a dispute that stays within the narrow lane where it can win.

Writing a Subject Statement that helps

A Subject Statement is read by every future querier, so its tone does more work than its length. The convention among people who handle these well is to keep it short, factual, and non-defensive: state what happened in plain terms, note the current status or resolution, and avoid re-arguing guilt or relitigating the case. A statement that sounds aggrieved tends to hurt; one that sounds measured and resolved tends to help.

A useful test before you submit it: read the statement as if you were a credentialing reviewer meeting you for the first time through this one paragraph. Does it leave you calmer or more worried? Naming the resolution, any remediation completed, and the current clean status generally reassures a reviewer more than a defense of the underlying facts, which invites them to re-open a question the report has already answered. Write for the reader you are trying to reassure, not the board you are still frustrated with.

Common questions

Only if it was factually inaccurate or was never reportable, in which case the reporting entity or the Secretary's dispute process can correct or void it. A report that accurately describes a real, reportable action stays in the Data Bank; the dispute process is not a way to erase an accurate report. A Subject Statement can add your context, but it does not remove anything.

A Subject Statement attaches your written account to the report, is always visible to queriers, and changes nothing in the report itself. A dispute formally contests whether the report is accurate or was reportable and can lead to a correction or a void. You can file both. Neither re-argues the merits of the board or malpractice action underneath the report.

No. A disputed report stays visible while it is under review, flagged as disputed and shown with any Subject Statement you attached, so credentialers see both. Because plans query the Data Bank during credentialing and recredential on a recurring cycle, the report keeps surfacing until the dispute is resolved. Disputing manages how the report reads, not whether it appears.

First, the reporting entity, which can amend or void its own filing, and that is usually the fastest route. If the matter is not resolved there, the Secretary's dispute-resolution process reviews it. Both look only at whether the report is factually accurate and whether it was reportable. Neither reviews the merits of the underlying action, which belongs to the forum that decided it.

If the underlying board order, judgment, or peer-review decision is what is wrong, contest it in that forum, because the report follows the outcome of that action. The NPDB dispute only corrects reporting errors, not the decision behind them. Sometimes both are appropriate: challenge the action where it lives, and dispute any factual error in how it was reported.

Run your practice on Gale

The software is free. Gale earns one flat 3.5% all-in per paid transaction — only on transactions that actually pay. No subscription, no setup fee, no network cut.

Start or manage a practice →

References

  1. 1.Centers for Medicare & Medicaid Services (2026). Medicare Fee for Service Recovery Audit Program. Centers for Medicare & Medicaid Services (CMS). linkCited as a contrasting example of a genuine merits appeal, the five-level Medicare appeals process, to clarify that an NPDB dispute is not an appeal of the underlying action.
  2. 2.National Committee for Quality Assurance (2026). Credentialing — NCQA. National Committee for Quality Assurance (NCQA). linkThat plans following NCQA standards query the NPDB during primary-source verification and recredential on a recurring cycle, so a report keeps surfacing during credentialing while a dispute is pending.

https://www.gale.care/for-providers/eck-npdb-report-dispute · 2 sources. Competitor details are cited to dated public sources and maintained as they change; figures are estimates, not commitments. Synthetic demonstration.

Findability, by specialty

How practices like yours get found in local search and AI answers — the honest playbook, per specialty.

SEO for private practices · SEO for AI search / answer engines (all verticals)