Disputing an NPDB Report: A Remedy for Inaccuracy, Not Injustice

A report appears in the National Practitioner Data Bank (npdb.hrsa.gov). The physician reads it and finds it wrong — sometimes factually, more often in the sense that the account it gives is unrecognizable as a description of what occurred. There is a dispute process, and it is a genuine remedy. It is also a much narrower one than its name suggests.

The governing regulation is 45 CFR 60.21 (official source), within Part 60 (official source). It provides that the subject of a report, or a designated representative, may dispute the accuracy of a report concerning themselves. The NPDB routinely mails or transmits electronically to the subject a copy of any report filed about them, and the subject may also request a copy.

The decisive constraint appears in the procedures for Secretarial review: the Secretary will only review the accuracy of the reported information, and will not consider the merits or appropriateness of the action or the due process that the subject received. HHS’s own system of records notice puts the same limit affirmatively — HHS can determine whether the report was legally required to be filed and whether it accurately depicts the action taken and the reporter’s basis for action.

This article works through the process on that understanding: the two stages, the four outcomes, what accuracy means in this context, and how to write a dispute that answers the question actually being asked.

The three questions that are in scope

Everything turns on identifying, precisely, what the reviewer is permitted to decide. Current NPDB guidance identifies three related questions.

The first is whether the report was submitted in accordance with NPDB reporting requirements, including whether the reporting entity was eligible to submit that type of report. A report can be improper because the reporting organization lacked authority to submit it, even when the described action genuinely occurred — for clinical privileges actions, the underlying duty runs through 42 U.S.C. § 11133 (law.cornell.edu) and its implementing regulations. If the reported action was not reportable, or the entity was not an eligible reporter for it, the regulation provides for the report to be voided. A reporting entity's delay in filing is not itself a ground for voiding an otherwise reportable event — late reporting is handled through separate compliance enforcement, not through Dispute Resolution.

The second is whether the report accurately depicts the action taken. This is accuracy in a specific sense: whether the action is described correctly — its nature, dates, duration, terms.

The third is whether the reporter's stated basis for the action is reflected in the reporter's own written record. That limb repays careful attention, because physicians consistently misread it. It asks whether the reported basis matches what the reporter's written findings actually say, not whether the basis was correct. A report stating that a committee acted on a finding of X is accurate if the committee's written findings do say X. It does not become inaccurate because the finding was wrong, unsupported, or reached unfairly. That distinction is the fulcrum of the entire process.

What is out of scope is stated in NPDB guidance directly: the underlying clinical conclusions, the proportionality of the action, and compliance with due-process requirements. A dispute arguing that the hearing was unfair, that the committee was biased, that the sanction was disproportionate, or that the conduct did not warrant action is arguing points the reviewer is expressly barred from considering — however well those points are made.

Stage one: Dispute Status and the reporting entity

The process does not begin with the federal government, and skipping the first stage forfeits the best available opportunity.

The NPDB process begins when the subject places the report into Dispute Status through the NPDB. The NPDB then notifies the reporting entity and organizations that received the report during the preceding three years; the dispute notation is also included in future query responses for as long as the report remains in Dispute Status, rather than triggering a separate notification to future queriers. The subject must then attempt to resolve the matter directly with the reporting entity. A subject seeking formal Dispute Resolution ordinarily must wait 60 days before requesting elevation — that wait may be shortened if the reporting entity provides written notice that it refuses to correct or void the report. Entering Dispute Status does not itself trigger federal review, and elevation is only one of several paths available at this point: a subject may instead leave the report in Dispute Status, withdraw the dispute notation, or use a Subject Statement without ever requesting Dispute Resolution. Only formal elevation carries the 60-day prerequisite, and it requires an affirmative request with supporting documentation and proof of the unsuccessful resolution attempt.

Stage one is strategically valuable for a reason that follows from the scope limits above. Before Secretarial review, only the reporting entity can directly submit a Correction Report or a Void to the NPDB — the subject cannot, and the NPDB itself will not rewrite a report at this stage. The reporting entity is not confined to the same narrow accuracy-and-compliance question the Secretary reviews: it can revise a report because the characterization was harsher than the facts warranted, because context was omitted, because on reflection the wording overstated the finding, while remaining responsible for filing an accurate report that satisfies applicable reporting requirements. None of those revision grounds require the Secretary's involvement, and all of them are available to the entity directly. During formal Dispute Resolution, by contrast, the NPDB may ultimately correct or void a report itself if the reporting entity does not substantiate or correct it — that federal authority is the thing stage one does not have and stage two does.

The stage-one submission should match the defect rather than default to one style. If the report contains factual or narrative inaccuracies, identify the disputed language, the supporting source document, and proposed corrective wording. If the action was not reportable, or the entity lacked authority to report it, state plainly which reporting requirement was not satisfied and request that the report be voided. Physicians who send an adversarial brief regardless of which defect is actually at issue frequently harden the position they needed to soften.

The subject may also add a Subject Statement to the report at any time, independently of the dispute process. This is covered in detail later in this article, including the strategic considerations that should inform whether and when to file one — it is not automatically advisable in every case.

Stage two: requesting elevation to Dispute Resolution

Where the entity will not act — or ordinarily, after the 60-day wait has run — the subject may request elevation to Secretarial Dispute Resolution.

The procedural requirements are specific. The subject must request review in the current format the NPDB specifies, submitting the request along with appropriate materials that support the subject's position and proof of the unsuccessful stage-one resolution attempt. Section 60.21 directs the Secretary to decide whether to correct the report within 30 days after the review request, though that period may be extended for good cause — that is the regulatory timeframe, not a guaranteed completion date. Current NPDB guidance states that elevated cases are reviewed in the order received, so the practical time to a decision can exceed the regulatory figure. The supporting materials are the substance of the exercise, and their character matters more than their volume.

Because the review is confined to reporting-requirement compliance, accuracy, and reflection of the reporter's stated basis — not how the reporting entity interpreted or applied its own bylaws — useful supporting material is documentary and objective: for clinical-privileges disputes, the final hearing-panel report is a particularly pertinent source; also useful are the final written decision, governing-body action, dated restriction notices, correspondence establishing dates, the committee's own written findings where they differ from the report's characterization of them, the terms of any resolution, and documentation of whether a qualifying investigation had reached final action or been formally closed at the relevant time. Bylaws provisions can supply relevant terminology or procedural structure, and remain useful documentary evidence where they objectively establish what authority a body possessed, what type of action its governing document purports to take, who constituted the authorized decision-making body, or whether the reporting entity was eligible to report at all — but Dispute Resolution will not adjudicate whether the entity properly interpreted or applied its bylaws, or afforded adequate process under them.

What is not useful, however compelling: character references, an account of the physician's clinical record, argument about proportionality, or evidence of procedural irregularity. These bear on merits and process, which the reviewer may not consider. Including them at length has a cost beyond wasted effort — it signals that the strongest available argument is out of scope, and it buries the points a reviewer is looking for.

NPDB guidance describes the request as requiring written documentation containing clear and brief factual information. Clear and brief is the operative instruction, and it is the opposite of most physicians' instinct at this moment.

What "accurately depicts the action" means in practice

The accuracy limb rewards specificity, and physicians tend to argue it at a level of generality that cannot succeed. It is worth working through the categories where discrepancies are actually found.

The nature of the action. Whether the action was a suspension, a restriction, a revocation, a denial, a non-renewal, or a voluntary surrender is a factual matter with a documentary answer. Reports sometimes describe an action in terms the institution's own records do not support — a restriction reported as a suspension, a non-renewal reported as a revocation.

Duration and dates. Effective date, end date, and total duration. These are mechanical, frequently wrong, and carry threshold consequences under the federal adverse-action limb in 42 U.S.C. § 11133 (law.cornell.edu), which reaches actions adversely affecting privileges for a period longer than 30 days. A duration error is not cosmetic — where the true duration falls below the threshold, the error may go to whether the report was required at all.

Scope. Which privileges were affected. A restriction limited to specified procedures, reported as a restriction of privileges generally, misdescribes the action.

The reporter's stated basis. Whether the report accurately conveys the basis the reporting body actually gave. The comparison is against the body's own written findings, and — as set out above — the question is whether the basis is accurately depicted, not whether it was correct.

The classification of a departure. Whether an exit is described as a resignation while under investigation is a question of what the entity accepted and when. NPDB material on clinical privileges reporting (official source) establishes that an investigation continues until the entity's decision-making authority takes final action, so whether final action had been taken at the relevant time is a factual question bearing directly on the description.

Each of these is provable from documents. None requires the reviewer to prefer the physician's account to the institution's — which is precisely why they are the arguments that work under 45 CFR 60.21 (ecfr.gov).

The four outcomes

The regulation sets out four dispositions. The current NPDB Guidebook groups them into three general categories — accurate, inaccurate or noncompliant, and outside scope — with the inaccurate/noncompliant category potentially resulting in either correction or voiding, so the four-way breakdown below and the Guidebook's three-category framing describe the same underlying outcomes.

Where the Secretary concludes the information is accurate and reportable, the Secretary informs the subject and the NPDB, includes a Secretarial Statement in the report describing the basis for the decision, and the report is removed from disputed status. The subject and reporting entity receive the decision letter; organizations that received the report during the preceding three years receive the report together with a summary of the decision, and the notation is reflected in future query responses.

Where the Secretary concludes the information is inaccurate, the Secretary informs the subject and directs the NPDB or the reporting entity to revise the report, includes a Secretarial Statement describing the findings, and distribution follows the same three-year-lookback pattern.

Where the Secretary determines the disputed issues are outside the scope of the Department's review, the Secretary informs the subject and the NPDB, includes a Secretarial Statement describing the findings, and the report is removed from disputed status, with distribution as above.

Where the Secretary determines the action was not reportable, the Secretary directs the NPDB to void the report. A voided report is removed from the subject's disclosable NPDB record; it does not carry a Secretarial Statement forward, since there is no report left to append one to. The NPDB distributes a void notice to the reporting entity, the subject, and organizations that received the report during the preceding three years, who are advised to destroy the voided report and any copies. Future queriers receive no disclosure of the voided report at all — unlike a correction, a void does not travel forward into later query responses.

Two features deserve emphasis. A completed Secretarial review finding the report accurate, inaccurate, or outside scope does add a federal statement to the report that remains — elevating a report is not always record-neutral, and merely entering Dispute Status without elevating does not by itself produce a final statement; the dispute notation can also be withdrawn before elevation. Describing an unsuccessful outcome as a "penalty" is argumentative; it is more accurate to call it a strategic consideration to weigh before elevating. And the outside-scope outcome is the specific disposition that most often awaits a physician who argued merits or process instead of the three questions actually in scope.

The subject statement: a genuine option, not an automatic one

Separate from disputing a report, the subject may add a Subject Statement at any time. The regulation describes a Subject Statement as permanently appended to the report, but current NPDB procedure resolves that in the subject's favor: the statement may be edited or removed at any time through the Report Response Service, notwithstanding the regulatory language. It is available whether or not a dispute is ever filed or succeeds, and current NPDB rules limit it to 4,000 characters, prohibit identifying patients, colleagues, or other individuals, and prohibit addresses, telephone numbers, and URLs. Distribution follows the same pattern as a correction: the reporting entity, three-year-lookback queriers, and future queriers.

Its value follows from how reports are actually read. A credentialing committee reviewing a report is performing an interpretive act under uncertainty: the structured fields establish what happened, and the committee must decide what it signifies. In the absence of any account from the practitioner, the committee supplies one — and, as a matter of this article's own analysis rather than documented credentialing data, institutional caution may supply an unflattering version.

But filing one is not automatically advisable, and treating it as a costless fallback is a mistake. A statement can create admissions, conflict with a position taken in litigation, a licensing proceeding, or a hearing, disclose facts not otherwise present in the report, undermine a pending correction or void request, or require revision once the reporting entity corrects the report on its own. Whether to file, and when, is a case-specific decision that benefits from counsel's judgment rather than a default yes.

As a matter of labeled drafting advice rather than an established credentialing rule: a specific factual clarification — an omitted date, the actual scope of a restriction the report states more broadly, remediation completed and when, the fact that a matter concerned a single episode — tends to read as more useful to a reader than a statement built around fairness or motive, which a reader may discount as self-serving. Length and framing are matters of professional judgment rather than settled fact, and a lawyer familiar with the specific matter is better positioned to weigh them than a general rule can be.

The practical instruction: if disputing, decide the Subject Statement question deliberately rather than by default, draft it while the facts are fresh if you decide to file, and have counsel review both the content and its interaction with any other pending proceeding before it is submitted.

Recharacterizing a grievance as an accuracy question

The practical skill is translation: finding the accuracy question inside a sense of injustice. It is often there, and it is often overlooked because the physician is focused on the larger wrong.

A physician who believes a finding was unsupported has no accuracy claim about the finding — but may have one if the report describes the finding in stronger terms than the committee’s written findings actually used. That is a discrepancy between the report and the source document, which is squarely accuracy.

A physician who believes a restriction was unjustified has no claim about justification — but may have one about the restriction’s duration, scope, or effective dates if the report misstates them. Duration in particular carries reportability consequences.

A physician who resigned and believes the resignation was mischaracterized has a potential reportability claim: whether an investigation was in fact open and had not reached final action at the relevant time is a factual question going to whether the report was required at all.

A physician who believes the action was administrative rather than disciplinary may have a reportability claim about whether it fell within the reporting duty.

The discipline required is to state the discrepancy and stop. "The report states the committee found X; the committee’s written findings, attached, state Y" is a complete and powerful accuracy argument. Adding "and in any event the finding was unjustified because …" converts a strong in-scope submission into one that invites the out-of-scope disposition. The temptation to add it is very strong, and resisting it is most of the craft.

Querying, self-query, and knowing what is there

A dispute presupposes knowledge of what a report says, and a surprising number of physicians do not have it.

The NPDB (official source) notifies the subject when a report is processed and provides access through the Report Response Service, and sends copies of subsequent corrections and revisions. As of May 2026, the NPDB consolidated these functions into a Personal Account: a free account lets a practitioner search for matching reports, view and respond to them, manage contact information, and receive email or text alerts about new reports. A paid annual subscription adds a certified Self-Query PDF and report-disclosure history. A Self-Query or certified Self-Query remains particularly useful before a credentialing or licensing submission, since it returns current NPDB information at that specific moment, but it is one feature of the Personal Account system rather than the only way to learn a report's content.

There are three reasons a physician should access every report promptly and keep current contact information on file with the NPDB, beyond simply waiting for notifications. Reports can be revised by the reporting entity after filing, and a physician who read the original may not have seen the current version. Multiple reports can exist for a single matter — a privileges action and a licensure action arising from the same events are separate reports with separate content. And a report the physician has never read cannot be disputed, while a report queried repeatedly before it is corrected has already done its work at credentialing committees that will not revisit their decisions.

The practical point about timing is worth stating plainly, because the regulation does not state it. Correction generally distributes to queriers from the preceding three years and to future queriers — a real benefit, and one bounded by that window rather than reaching every historical querier without limit. The intervening decisions were nonetheless made on the uncorrected report, and no notice reverses a privileges denial already issued. Speed is therefore not a procedural requirement but a substantive one.

As a matter of practical advice rather than a regulatory requirement — no universal frequency is prescribed — the habit worth adopting is to Self-Query before applying for privileges, licensure in another state, or payer enrollment, and to promptly open every report the NPDB sends notice of rather than deferring. Discovering an inaccurate report through a credentialing committee’s question is the worst available sequence, because the physician is then explaining a document they are reading for the first time to the people deciding on their application.

The confidentiality regime, and who it actually restricts

Two features of Part 60's disclosure framework bear on how a physician should think about a report's reach.

The first is that distribution on correction generally runs to queriers that received the report during the preceding three years, as well as future queriers — not to every historical querier without limit. That is a real benefit of a successful dispute, but the three-year lookback is a limit worth understanding rather than assuming away.

The second, and the one physicians most often get backwards: NPDB confidentiality restrictions bind hospitals, health plans, licensing agencies, attorneys, and other eligible queriers who receive information under the statute — not the subject of the report. As of the most recent inflation adjustment (January 28, 2026), the maximum civil money penalty for breaching NPDB confidentiality is $28,619 per violation, imposed pursuant to the procedures at 42 CFR part 1003 (ecfr.gov) — but that exposure runs to organizations that misuse or improperly redistribute a query response, not to the physician the report is about. Official NPDB guidance states directly that a subject who obtains information naming them, including a Self-Query response, may share that information with whomever they choose. An organization cannot freely redistribute its own query response merely because the practitioner consents — written practitioner consent does not eliminate the querying entity's own confidentiality restrictions, which run to the organization independently of anything the subject agrees to. The practitioner's own sharing of their own report, by contrast, is not itself a confidentiality violation. The underlying institutional records from which NPDB information was derived are also not rendered confidential merely because information from them was reported to the NPDB.

The subject's own access rights are separate and secure: the NPDB notifies the subject when a report is processed, provides Report Response Service access, and permits a Self-Query at any time. Every physician should exercise those rights periodically rather than discovering a report through a credentialing query. A report the physician has never read cannot be disputed, and a dispute mounted years later against a report that has already been queried repeatedly is a weaker instrument than the same dispute mounted promptly.

Why so many disputes fail

The failure modes are consistent enough to enumerate, and all of them are avoidable.

A recurring failure mode is scope. The physician argues the merits, proportionality, or due process, and the outcome is a determination that the disputed issues fell outside the Department’s review. NPDB guidance states the limit plainly, and disputes still fail on it often enough that it is worth naming as the single most avoidable mistake.

The second is volume without documents. A long narrative of events, however accurate, is not evidence of a discrepancy. The reviewer is comparing a report against source material. A submission without source material asks the reviewer to take the subject’s word against the reporting entity’s, which is not the comparison the process performs.

The third is skipping stage one, or treating it as a formality. The reporting entity can revise for reasons the Secretary cannot act on. A physician who moves quickly past the only decision-maker empowered to consider characterization and context has discarded the better remedy.

The fourth is delay. Reports are queried continuously. A dispute resolved after two years of queries has corrected the record for future queriers and, where identifiable, previous ones — but the intervening credentialing decisions were made on the uncorrected report.

The fifth is proceeding without counsel who has done this before. The submission is short, technical, and governed by a scope rule that runs against instinct. It is precisely the kind of document where experience is worth disproportionately more than effort.

The structural critique worth making

Three observations, on the assumption that a bounded accuracy review is a defensible design.

First, the scope limit is coherent but leaves a genuine gap. HHS is not an appellate body over hospital peer review, and it would be poorly placed to relitigate merits. The NPDB Dispute Resolution process is not a forum for reviewing underlying unfairness, discrimination, proportionality, clinical merits, or due process — that is the narrower, defensible statement. Whether some other internal, administrative, state, or federal judicial remedy exists for that underlying unfairness depends on the specific facts and governing law, and this article does not attempt to survey that landscape; internal peer review, addressed in the material on fair hearing rights (Fair Hearing Rights: California’s Principal Route to the Evidence Behind a Reportable Peer-Review Action) and bylaws as a source of rights (Medical Staff Bylaws as a Source of Rights: The Document Nobody Reads Until It Governs Them), is often the most immediate forum, but it is not necessarily the only one.

Second, the reporting entity holds a genuinely broader remedy at the Dispute Status stage than the Secretary's own review offers. It can revise for characterization and context, which the Secretary cannot address directly; it also authored the report and, as a matter of this article's own analysis rather than documented data, may have less institutional urgency to revisit it voluntarily than a compelled federal process would create.

Third, a completed Secretarial finding of accurate, inaccurate, or outside-scope does add a federal statement to the report, which is a real strategic consideration rather than a guaranteed cost — merely entering Dispute Status without elevating does not itself produce that statement, and the notation can be withdrawn. An unsuccessful or outside-scope Dispute Resolution decision may add a federal summary to the report, which is a consideration to weigh before elevation, not a reason to avoid a genuinely strong claim.

None of this argues against disputing an inaccurate report. It argues for doing it early, doing it narrowly, and doing it with someone who knows that the question on offer is accuracy — not justice.

What to do before there is anything to dispute

Almost everything that determines the outcome of a dispute happens before the report exists, which makes this the most useful section for a physician not currently in difficulty.

The review, as established above, compares the report against the action taken and the reporter’s stated basis. The reporter’s stated basis is drawn from the institution’s contemporaneous record — committee findings, minutes, correspondence. That record is therefore the substrate of any future accuracy claim, and it is written during a process in which the physician is a participant.

A physician who engaged with that record has, without intending it, built the evidentiary foundation of a possible dispute. If committee findings were corrected where factually wrong, if remediation and context were insisted into the written record, if characterizations reaching beyond the evidence were resisted in writing at the time — then a later report that overstates the findings is demonstrably discrepant from the source document, and that is precisely the in-scope argument the process rewards.

A physician who treated the internal process as something to endure has the opposite position. The institution’s record says what the institution chose, the report accurately reflects it, and the dispute has no purchase — not because the physician is wrong about what happened, but because nothing contemporaneous contradicts the report.

Three habits follow, and they cost little. Keep your own dated file as any process unfolds: what you were told, by whom, when, and what you provided. Correct factual errors in writing at the time, however minor and however awkward. And request copies of findings and decisions rather than relying on being told their substance.

The general principle is the one that runs through this whole series. Reports are permanent and disputes are narrow; the contemporaneous record is the only thing that reliably answers a report, and it can only be created before you need it — the same reasoning that governs an exit decision (Resignation During Investigation: The Exit That Creates the Record) and the state reporting duty (The 805 Report: How Hospital Peer Review Enters a California Licensing File).

What a corrected report looks like afterward

A physician contemplating a dispute should know what success actually produces, because it is not a clean file.

Under 45 CFR 60.21 (ecfr.gov), where the Secretary concludes information is inaccurate, the report is revised and a Secretarial Statement describing the findings is included, with the corrected report and statement distributed to the reporting entity, the subject, and queriers from the preceding three years and going forward. Where the action was not reportable, the report is voided and a void notice — not a Secretarial Statement — goes to the same recipients, who are advised to destroy the voided report and any copies.

So there are two materially different successful outcomes. A voided report is the clean one: the report should not have existed and is removed. A revised report is not clean — it is a corrected report carrying a federal statement that it was disputed and found inaccurate.

The second outcome is still clearly worth having, and the reasoning is worth being explicit about. A future querier reads the corrected content rather than the original, and reads alongside it a statement that the subject disputed the report and that the Department found the report inaccurate. That is a considerably better position than an uncorrected report with no annotation — an independent federal finding of inaccuracy is not something a physician can otherwise obtain.

What it is not is invisibility. Physicians who expect a successful dispute to erase the episode are surprised by the annotation, and occasionally regret a dispute that succeeded. The correct expectation is a corrected record with a documented history, not a blank one.

This also bears on the reportability argument’s relative value. Establishing that an action was not reportable produces a void — the strongest available outcome. Establishing that a report was inaccurate produces correction with annotation. Where both arguments are genuinely available on the facts, the reportability argument is worth leading with.

Reconsideration: a further step after an unfavorable decision

A Dispute Resolution decision is not necessarily the last word. Current NPDB guidance allows a subject to request reconsideration of a decision, and it is a step worth knowing about before assuming an unfavorable outcome is final.

Reconsideration is a limited administrative request, not a routine second appeal or an opportunity to relitigate the underlying merits. The request should identify new information that was genuinely unavailable during the original review, or explain specifically which issue the Secretary is asserted to have considered improperly — a located source document that surfaces after the fact, for instance, or a specific factual or procedural error in how the original decision was reached. Simply repeating rejected arguments is not a basis for reconsideration. On reconsideration, the prior decision may be affirmed, or a revised final decision may be issued.

Because reconsideration exists, an unfavorable outcome is a reason to review what went wrong — was the submission genuinely confined to the three in-scope questions, was the strongest documentary evidence actually included, is there a source document that surfaced too late to be part of the original submission — rather than an automatic dead end.

Timing, and the cost of a slow dispute

The regulation sets out no limitation period that bars a late dispute, but delay has substantive costs that operate independently of any deadline. They are worth stating because physicians consistently wait.

Queries accumulate. Hospitals are federally required to query when a practitioner applies for medical-staff appointment or clinical privileges, including temporary privileges; when the practitioner seeks to add to or expand existing privileges; and every two years thereafter while the practitioner remains on staff or holds privileges. Other eligible queriers — health plans, licensing agencies, other health care entities — have their own query authorities and obligations that vary and do not necessarily run on the same cycle. Correction distributes to queriers from the preceding three years and to future queriers, per 45 CFR 60.21 (ecfr.gov) — a real benefit, though it does not by itself require a prior credentialing body to reopen a completed decision. A privileges denial issued last year is not automatically revisited by a correction notice this year, though nothing prevents a body from choosing to reconsider.

Evidence degrades. An accuracy claim requires a source document contradicting the report. Institutional files are archived to policy, individuals move on, and the willingness to locate old committee findings declines with time. A dispute mounted promptly draws on material that still exists.

The institution's position hardens. A reporting entity asked to revise a recent report is being asked to correct something current. Asked years later, it is being asked to reopen a closed matter, and the people who could authorise that are no longer the people who made the decision.

And the physician's own account loses precision. A contemporaneous objection is corroborative; a recollection assembled later is not, however accurate.

The practical sequence is therefore: self-query on a schedule and always before any application, read what is actually there rather than what you were told, raise a discrepancy with the reporting entity immediately, and move to Secretarial review promptly if that fails. The data bank (official source) transmits reports to their subjects and permits self-query, so there is no structural reason for a physician to be unaware of what a report says.

Where the dispute process sits among the available routes

The dispute process is one of several routes, and physicians routinely choose it for problems it cannot solve while overlooking routes that could.

Where the report misdescribes the action or was not required, the dispute process is correct. That is precisely its scope — accuracy and reportability, per the framework in Part 60 (ecfr.gov).

Where the underlying action was unfair, the NPDB Dispute Resolution process is not the forum for that argument — it does not review discrimination, proportionality, clinical merits, or due process. Internal peer review, addressed in fair hearing rights (Fair Hearing Rights: California’s Principal Route to the Evidence Behind a Reportable Peer-Review Action) and medical staff bylaws (Medical Staff Bylaws as a Source of Rights: The Document Nobody Reads Until It Governs Them), is often the most immediate forum for that argument, though whether another administrative, state, or federal judicial remedy also exists depends on the specific facts and governing law.

Where the physician's objection is to how a matter was characterized rather than to a factual error, the reporting entity is the only body that can act, and it can act for reasons the Secretary cannot consider. That is stage one, and it is the stage most often treated as a formality.

Where a licensing inquiry has opened on the basis of the report, that is a separate proceeding on its own standard, and a favourable dispute outcome is useful evidence rather than a resolution.

And where the physician wants their account in the file regardless of any outcome, the subject statement does that and requires no dispute at all.

The choosing error worth avoiding: mounting a Secretarial review to express that an episode was unjust. It will be determined to be outside the scope of the Department's review, and that disposition adds a Secretarial Statement to the report recording that it was reviewed. A remedy used for the wrong problem does not merely fail — it leaves a mark.

Drafting the submission: a worked structure

The submission is short, technical, and unforgiving of scope errors. A structure that works, and the reasoning behind each element.

Open with the disposition sought, in one sentence. Void the report because the action was not reportable, or revise a specified statement because it is inaccurate. A reviewer reading 45 CFR 60.21 (official source) submissions is looking for which of the available outcomes is being requested.

State the discrepancy in a table or a numbered list. What the report says, what the source document says, and which attachment establishes it. Nothing else communicates an accuracy claim as efficiently, and it is the form a reviewer can verify without interpretation.

Attach the source documents, labelled to match. Committee written findings, the bylaws provision defining the action, dated correspondence, the resolution terms, documentation of investigation status.

Address reportability separately and first if it is available. Whether the action fell within the duty — for privileges actions, 42 U.S.C. § 11133 (law.cornell.edu) and the regulations at 45 C.F.R. Part 60 (ecfr.gov) — is the stronger argument because it produces a void rather than an annotated correction.

Stop. Do not add a section explaining the circumstances, the unfairness, or your record. The regulation confines review to accuracy and expressly excludes the merits, the appropriateness of the action, and the due process received. Material outside that scope does not merely fail to help; it invites the out-of-scope disposition and the Secretarial Statement that comes with it.

One structural note: keep the whole thing to a few pages plus attachments. Length signals a weak accuracy claim being compensated for, and the reviewer's question is narrow enough to answer briefly when the answer is good.

The subject statement as an independent, always-available option

Every route in this article can fail on the merits of a specific dispute. One instrument does not depend on the Secretary or the reporting entity agreeing with you — though, as covered earlier in this article, whether to use it is still a case-specific decision, not an automatic default.

A subject may add a statement to a report. It requires no dispute, no finding, and no cooperation from the reporting entity. It travels with the report and appears to every querier who reads it.

Why it matters follows from how reports are read. A credentialing committee has structured fields, a narrative written by the institution, and a queue. In the absence of any account from the practitioner, they construct one, and institutional caution constructs an unflattering version. A statement is the only counterweight that exists in the file.

What makes one effective is narrow. Facts a reader can verify: a date the report omits, the actual scope of a restriction the report states broadly, remediation completed and when, the fact that a matter concerned one episode rather than a pattern. Three sentences of that reads as confident.

What destroys one: complaint about the fairness of the process, characterization of colleagues’ motives, assertion that the action was unwarranted, or length. A reader who encounters those stops reading and discounts the whole statement — which leaves the physician worse off than silence, because it confirms the unflattering reading.

The timing point: draft it while the facts are fresh and the documents are obtainable. A statement assembled years later from memory is visibly that.

And draft it even when disputing. The dispute may fail, may be determined outside the scope of review under 45 CFR 60.21 (ecfr.gov), or may produce a correction that still carries a Secretarial Statement. In every one of those outcomes the physician's own account is the thing still doing work — and the data bank (npdb.hrsa.gov) transmits reports to their subjects, so there is no reason to be unaware of what needs answering.

Why the remedy is under-used by the people it exists for

A closing structural observation, because it explains something about the data that would otherwise mislead.

This article has not located current NPDB data establishing the dispute rate relative to total reports; where that comparison is made in secondary commentary, it is offered as a plausible hypothesis rather than a documented finding. What is documented is that several features of the process create real disincentives to use, discussed below — disincentives that would depress use regardless of the underlying accuracy rate.

Four features push toward non-use.

A completed Secretarial finding of accurate, inaccurate, or outside scope appends a Secretarial Statement to the report that remains — though merely entering Dispute Status without elevating does not. Under 45 CFR 60.21 (ecfr.gov), a finding that the report is accurate, a finding that it is inaccurate, and a determination that the issues were outside the scope of review all result in a statement being added. A physician with a genuine but arguable accuracy claim must weigh a possible correction against a federal annotation recording that the report was reviewed — which a future querier reads.

The scope rule runs against instinct. As set out throughout, the physician's strongest felt argument is the inadmissible one, and a submission that cannot resist making it produces the out-of-scope disposition.

The better remedy has no compulsion behind it. Stage one — the reporting entity — can revise for characterization and context, which the Secretary cannot, and faces no consequence for declining.

And the process requires documents the physician may not yet hold. In California, Evidence Code section 1157 (leginfo.legislature.ca.gov) restricts civil discovery of protected peer-review materials, but it does not make every relevant document categorically unavailable to the physician: a licentiate who timely invokes qualifying hearing rights may obtain relevant documentary information under Business and Professions Code sections 809.2 and 809.3. The practical availability of particular documents depends on the procedural posture, the nature of the record, and the governing statutes and bylaws — which is why forgoing an available hearing, rather than the statute itself, is frequently what leaves a physician without the source document an accuracy claim needs.

The combined effect is a remedy that is genuinely available, genuinely narrow, and structurally discouraging to marginal use. That is defensible as a design — a data bank whose contents could be casually contested would be worth less. It also means low dispute rates should not be read as evidence that reports are accurate, and anyone citing that statistic should say so.

If a report about you is inaccurate

Obtain and read the report. The NPDB transmits a copy to the subject, and you may request one — do not wait for a credentialing query to discover it.

Separate your objections into accuracy and reportability on one side, merits and process on the other. Only the first side is usable.

Go to the reporting entity first, and go non-adversarially — it can revise for characterization and context, which the Secretary cannot.

Quote the specific language you say is wrong and propose specific replacement language.

Assemble source documents: bylaws provisions, committee written findings, dated correspondence, resolution terms, investigation status.

Add a subject statement regardless of outcome — short, factual, verifiable, with no complaint about fairness.

On Secretarial review, submit clear and brief factual information with supporting materials, and cut every merits argument however strong.

Move quickly. Every month of delay is another interval of queries against the uncorrected report.

Keep your own dated file during any internal process — it is the only material that can later contradict a report.

The one sentence to keep in view

Dispute Resolution examines compliance with reporting requirements, accuracy of the action as depicted, and accuracy of the reporter’s stated basis — not the merits, proportionality, or due process received.

Read that before drafting, and again after. A recurring failure mode is a submission that could not resist arguing the thing that sentence excludes. The discipline it demands is genuinely difficult, because the physician’s strongest and most deeply felt argument is often the inadmissible one — and a submission that leads with it risks an outside-scope determination that still adds a federal summary to the report.

General educational information—not legal or medical advice

This article describes federal regulatory procedure for physicians, medical staff leaders, and health lawyers. It is not legal advice and creates no professional relationship. Dispute procedures, formats, and penalty amounts are set by regulation and subject to amendment and inflation adjustment. Any physician disputing a report should verify current requirements at 45 CFR 60.21 and retain counsel experienced in NPDB matters — the submission is short, technical, and unforgiving of scope errors.

Questions worth asking

Have I actually read the report, or only been told what it says?

Which of my objections concern accuracy or reportability, and which concern merits or process?

Is there a discrepancy between the report’s language and the reporting entity’s own written findings?

Was the action in fact reportable — was an investigation open, and had final action been taken?

Has the reporting entity been asked to revise, non-adversarially, before any federal filing?

Is my accuracy claim strong enough to justify a Secretarial Statement if it fails?

Takeaway

The NPDB dispute process is a remedy for inaccuracy, non-compliance with reporting requirements, and non-reportability — not for unfairness. Dispute Resolution examines whether the report complied with reporting requirements (including reporter eligibility), accurately depicts the action, and accurately reflects the reporter’s stated basis, expressly excluding the merits, proportionality, clinical validity, or due process received. The reporting entity, at the Dispute Status stage, holds a broader remedy than the Secretary does. Disputes succeed when they identify a documented discrepancy and stop; a Subject Statement, reconsideration, and (in California) statutory hearing-access rights are additional tools worth understanding on their own terms rather than treating the federal dispute alone as the whole remedy.

Sources and Authorities

The sources below are provided so readers can confirm the governing text and current agency guidance. Laws, regulations, agency pages, and implementation dates can change; time-sensitive requirements should be checked against the current official source.

California BPC Article 11, §§800–809.9 — leginfo.legislature.ca.gov

California BPC §805 — leginfo.legislature.ca.gov

California BPC §805.01 — leginfo.legislature.ca.gov

California Evidence Code §1157 — leginfo.legislature.ca.gov

42 U.S.C. §11111 — law.cornell.edu

42 U.S.C. §11112 — law.cornell.edu

42 U.S.C. §11133 — law.cornell.edu

NPDB Guidebook — Clinical Privileges — npdb.hrsa.gov

45 C.F.R. Part 60 — ecfr.gov

www.npdb.hrsa.gov — npdb.hrsa.gov

www.ecfr.gov — ecfr.gov

www.npdb.hrsa.gov — npdb.hrsa.gov

www.ecfr.gov — ecfr.gov

www.ecfr.gov — ecfr.gov

www.npdb.hrsa.gov — npdb.hrsa.gov

www.npdb.hrsa.gov — npdb.hrsa.gov

www.npdb.hrsa.gov — npdb.hrsa.gov

www.npdb.hrsa.gov — npdb.hrsa.gov

www.npdb.hrsa.gov — npdb.hrsa.gov

www.npdb.hrsa.gov — npdb.hrsa.gov

www.npdb.hrsa.gov — npdb.hrsa.gov

www.npdb.hrsa.gov — npdb.hrsa.gov

www.npdb.hrsa.gov — npdb.hrsa.gov

leginfo.legislature.ca.gov — leginfo.legislature.ca.gov

Case opinion — law.justia.com

Related Articles

• The Regulatory Cascade: One Fact, Nine Destinations, Five Standards of Proof
• The National Practitioner Data Bank: What It Is, What It Is Not, and Why the Distinction Matters
• What Gets Reported to the NPDB
• Medical Malpractice Payment Reporting