Blog · Credentialing
How to Read an NPDB Query Response During Credentialing

An NPDB query response is the document the National Practitioner Data Bank returns after it processes your query. It has a header plus three sections: Section A shows the identifying information you submitted, Section B shows your organization’s information and the statutes under which you can query, and Section C summarizes which types of reports, if any, were found [1]. If reports were found, they follow on the next pages, each with its own header, Summary of Action, lettered sections, and footer [1]. This guide walks the response field by field and shows what each part means for a credentialing file.
Last verified: November 5, 2026. Facts in this guide are cited to official NPDB (HRSA) and federal regulation sources, listed at the end.
What is in an NPDB query response
An NPDB query response identifies whether there are any reports in the NPDB on the subject of the query and presents copies of all reports [2]. The pieces, in the order you read them:
| Part of the response | What it contains | What to do with it |
|---|---|---|
| Header | Data Bank Control Number (DCN), process date, page number, the subject’s name, and your organization as the authorized user [1] | Record the DCN. The NPDB asks you to have it ready when you contact them about a query or report [1][2]. |
| Section A – Subject Identification Information | The identifying information you supplied for the subject [1] | Verify it is correct. If it is wrong, submit a new one-time query with the correct information or update the continuous query [1]. |
| Section B – Continuous Query Enrollment Information or Query Information | Your organization’s information and the statutes of law under which you can query [1] | Confirm your organization is properly registered: the NPDB checks how an entity is registered before releasing information and releases only what that registration lawfully permits [8]. |
| Section C – Summary of Reports on File | The types of reports found, if any, such as clinical privilege actions or medical malpractice payments [1] | Use it as an index, then read each report in full [1]. |
| Report pages (if any) | A header, Summary of Action, lettered sections A–F, and a footer for each report found; Section F appears only when the NPDB holds supplemental identifiers [1] | Read thoroughly: the NPDB says this is necessary to accurately interpret the context and severity of the action [1]. |
Why Section A is the field most worth checking
The NPDB releases information about a subject only if the identifying information in your query matches the information in a report submitted to the NPDB [2]. The NPDB warns that if the information submitted in a query does not accurately identify the intended practitioner, the query may not match reports naming that practitioner that carry the correct identifiers [2].
That makes a clean Section A the difference between a meaningful “no reports found” and an unusable one. Compare Section A against the provider’s application line by line before you file the response. On the IQRS, maintaining a Subject Database pre-populates query and report forms, and the IQRS will not generate a query for a record that is missing required fields [2].
How to read an NPDB report inside the response
Each report in the response opens with a header carrying the same fields as the NPDB query response header: a Data Bank Control Number, process date, page number, the subject’s name, and your organization as the authorized user [1]. Then comes the Summary of Action: the subject’s name, the organization that submitted the report, the date of the action, the type of action (State Licensure Action, Clinical Privilege Action, Health Plan Action, and so on), the basis for action, and any related reports [1]. The lettered sections follow.
Sections A through F of a report
- Section A – Reporting Entity. Contact information for the organization that submitted the report, and whether the report is initial, a revision, or a correction [1]. A revision or correction tells you the record has moved; check whether your file holds the superseded version.
- Section B – Subject Identification Information. Identifiers supplied by the reporting organization, including date of birth, education, and state license number [1]. Compare these with your own file to confirm you have the right practitioner.
- Section C – Information Reported. The incident, and when and why the action was taken; the content differs by type of action [1]. This is the section your committee actually needs.
- Section D – Subject Statement. Additional information provided by the subject [1].
- Section E – Report Status. Whether the report is being disputed by the subject, and the status of the dispute [1].
- Section F – Supplemental Identification Information on File. Additional identifiers such as a maiden name, an additional license number, or a National Provider Identifier. If there is no supplemental information, this section does not appear in the report [1].
- Footer. The law that required the action to be reported: Title IV, Section 1921, or Section 1128E [1].
Section F’s absence is informative rather than alarming: it simply means the NPDB holds no extra identifiers [1]. The footer is worth noting in your file because it tells you which statute compelled the report [1], and the statute also governs what your registration lets you see [8].
What Section E dispute status does and does not mean
This is the field most often misread. A subject may dispute a report and enter it into Dispute Status at any time, disagreeing with its factual accuracy or with whether it was submitted in accordance with NPDB reporting requirements [6]. But entering a report into Dispute Status does not trigger a review of the report by the NPDB [6]. A dispute notation is the subject’s position, not a finding.
A review happens at the next step. The subject may request Dispute Resolution once the report is in Dispute Status and the subject has waited 60 days after entering it, during which the subject attempted to contact the reporting entity and can verify that effort [6]. If the reporting entity states in writing during those 60 days that it refuses to correct or void the report, the subject may ask for immediate elevation without waiting the full 60 days [6]. Under 45 CFR 60.21, where the reporting entity does not revise the information or does not respond to the subject within 60 days, the subject may ask the Secretary to review the report for accuracy, and the Secretary will decide whether to correct the report within 30 days of the request, a time frame that may be extended for good cause [7].
What Dispute Resolution can and cannot review
What that review can reach is narrow. Dispute Resolution can determine whether the report was submitted in accordance with NPDB reporting requirements, whether it accurately depicts the action taken as reflected in the written record the reporting entity provided, and whether the reporter’s stated basis is reflected in that record [6]. It does not review the underlying reasons for the report or the due process the subject received; those are between the subject and the reporting entity [6][7]. For a malpractice payment report, the review can determine only whether the report accurately depicts that a payment was made on behalf of the claimant [6]. Late reporting is not grounds for dispute: eligible entities must report medical malpractice payments and other reportable actions within 30 calendar days of the date the payment was made or the action was taken, and timeliness is handled through the NPDB’s compliance program instead [6].
Two distribution rules affect your file. A dispute notation is sent to the reporting entity and all queriers who received the report within the past 3 years, and travels with the report to future queriers [6]. A Subject Statement behaves the same way: it is sent to the reporting entity and all queriers who received a copy of the report within the past 3 years, and is included with the report for future queriers [5]. So a response you pulled last year can be followed by material you did not ask for, and the subject may modify or remove a Subject Statement at any time through the Report Response Service [5].
Deadlines that catch credentialing teams
- 45 days to retrieve. Entities must retrieve official query responses within 45 days of processing, or they will be required to resubmit their queries and pay the associated query fee [2]. Entities that want to keep responses should download them [2].
- One business day before you call. If you do not receive a query response within one business day of submission, contact the NPDB Customer Service Center to request a query status [2].
- Do not resubmit. Resubmitting a query on that subject produces duplicate transactions and duplicate query fees [2]. Call instead.
- Missing report? If, based on a query response, you believe a reportable action was not submitted, go to the Subjects Queried page (or the Multiple-Name Query Responses page for bundled responses), click the Reporting Compliance link, and provide the information about the missing report [2].
- Continuous Query enrollments. Enrollment confirmations are available for the entire enrollment period as long as the enrollment is not canceled [2].
A decision rule for the credentialing file
Work each NPDB query response in this order:
- Record the DCN and the process date from the header in the provider’s file [1].
- Read Section A against the application. If an identifier is wrong, treat the result as inconclusive and submit a corrected one-time query or update the continuous query [1][2].
- Read Section C. If no reports were found, file the response with the date and move on, remembering that NPDB information should not be used as the sole source of verification of professional credentials [3].
- If reports were found, read each one in full, not the summary alone [1].
- In Section A of each report, note whether it is initial, a revision, or a correction, and pull the earlier version if you hold one [1].
- Read Section C of the report for what happened, then Section D for the subject’s statement and Section E for dispute status, treating a dispute notation as unreviewed [1][6].
- Check the footer to see which statute required the report [1].
- Download and store the response before the 45-day retrieval window closes [2].
- Route the response into your credentialing committee review with the rest of the credentialing file, and re-run it on your medical staff reappointment cycle.
How much weight to give the response
The NPDB is explicit about its own limits. The information in the NPDB should serve only to alert eligible entities that there may be a problem with the performance of a particular practitioner, entity, provider, or supplier; it is primarily a flagging system that may alert users that a more comprehensive review of qualifications and background may be prudent [3]. It is meant to be used as one of many tools for licensing, certification, hiring, credentialing, and contracting decisions, in conjunction with other resources [9]. NPDB information should not be used as the sole source of verification of professional credentials [3], so license verification still runs through the state licensing board, as in nurse license verification for credentialing, and exclusion checks run on their own track, as in the effect of an OIG exclusion.
One report type deserves specific care. A settlement of a medical malpractice claim may occur for reasons that do not necessarily reflect negatively on the practitioner’s professional competence or conduct, and as indicated in Title IV, a payment made in settlement should not be construed as a presumption that malpractice has occurred [3]. Write that distinction into your committee’s standard for reading Section C of a malpractice payment report.
Who may see the response
Information reported to the NPDB is confidential and may not be disclosed except as specified in the NPDB statutes (Title IV, Section 1921, Section 1128E) and the implementing regulations at 45 CFR Part 60 [3][4]. The confidentiality provisions allow an eligible entity that receives NPDB information to disclose it to others who are part of an investigation or peer review process, as long as the information is used for the purpose for which it was provided, and everyone involved is then subject to the same confidentiality provisions [4]. The OIG has been delegated the authority to impose civil money penalties on those who violate the confidentiality provisions of Title IV [3]. The summary above is a plain-language summary of those rules, not legal advice; check your own counsel’s guidance before you set a distribution practice.
Practically, that argues for storing responses where access is controlled and recorded rather than in shared mailboxes or drives, and for keeping the distribution list to the people working the file.
Keep query responses moving through your process
Incredable lets you build automated workflows that align with your credentialing process for efficiency and compliance, so a retrieved response has a defined next step instead of sitting in an inbox. Its task management module lets teams assign, track, and complete tasks using a visual Kanban board and integrated time tracking.
Sources
- NPDB (HRSA), How to Interpret Query Responses and Reports. Verified November 5, 2026.
- NPDB Guidebook, Chapter D: Queries – Query Processing and Query Responses. Verified November 5, 2026.
- NPDB Guidebook, Chapter A: Introduction and General Information. Verified November 5, 2026.
- NPDB Guidebook, Chapter D: Queries – Confidentiality. Verified November 5, 2026.
- NPDB Guidebook, Chapter F: Subject Statements. Verified November 5, 2026.
- NPDB Guidebook, Chapter F: The Dispute Process. Verified November 5, 2026.
- Legal Information Institute, Cornell Law School, 45 CFR 60.21 – How to dispute the accuracy of National Practitioner Data Bank information. Verified November 5, 2026.
- NPDB Guidebook, Chapter D: Queries – Overview. Verified November 5, 2026.
- NPDB Guidebook, Chapter E: Reports – Overview. Verified November 5, 2026.
