NPDB queries are formal searches of the National Practitioner Data Bank that reveal a practitioner's history of malpractice payments and adverse actions — and for hospitals and many health care entities, they are not optional. A query returns every report the federal Data Bank holds on a practitioner that your organization is legally authorized to see, giving credentialing committees a nationwide view of licensure discipline, clinical-privileges actions, exclusions, and settlement history that no single state board or resume would surface. Understanding what an NPDB query reveals, and when the law requires one, is fundamental to a defensible credentialing program.
What is the National Practitioner Data Bank?
The National Practitioner Data Bank (NPDB) is a federal repository created by Congress under the Health Care Quality Improvement Act of 1986 and related statutes. As the NPDB explains, it “collects information on medical malpractice payments and certain adverse actions” and discloses that information only to entities legally eligible to query, per its querying overview. It is administered by the Health Resources and Services Administration (HRSA), and its purpose is to prevent practitioners from crossing state lines to escape a disciplinary history. The NPDB is a flagging system, not a verification service — it points you to actions that warrant a closer look, which you then investigate through the reporting source.
What is the difference between an NPDB query and a report?
These two words describe opposite directions of information flow, and conflating them is a common source of confusion. A report is submitted to the NPDB by an eligible entity when a reportable event occurs — a malpractice payout, a license suspension, a clinical-privileges revocation. A query is a request from the NPDB: you ask, and the Data Bank returns any reports on file. Reporting is an obligation that falls on payers, boards, hospitals, and peer-review bodies; querying is the credentialing activity most organizations perform routinely. All reports must be submitted within 30 days of the action or payment, according to the NPDB's Guidebook.
What does an NPDB query reveal?
A query surfaces the reportable actions and payments the Data Bank collects. Under the governing statutes, these include:
- Medical malpractice payments resulting from a written claim or judgment.
- Adverse licensure actions related to professional competence or conduct taken by state boards.
- Adverse clinical-privileges actions taken by hospitals and health care entities.
- Adverse professional-society membership actions related to competence or conduct.
- DEA controlled-substance registration actions.
- Exclusions from Medicare, Medicaid, and other federal health care programs.
- Negative actions or findings by peer-review and private accreditation organizations, plus health-care-related criminal convictions and civil judgments.
That breadth is what makes the NPDB uniquely valuable: a single query consolidates federal, state, and private-sector actions that would otherwise require dozens of separate inquiries. It does not, however, replace direct verification of a license or board certification — the NPDB tells you whether an action exists, while primary-source verification confirms the credential itself is current and valid.
Who is eligible to query, and what a query does not show
Not everyone can query the NPDB. An organization must be registered and authorized under the governing statutes, and it receives only the reports it is legally entitled to see — the NPDB releases information strictly according to the querier's registration and eligibility. Hospitals, other health care entities that conduct formal peer review, state licensing boards, and health plans are typical eligible queriers, as detailed in the NPDB's Guidebook chapter on queries; a query can also be run by an authorized agent, such as a credentials verification organization acting on the entity's behalf. Individual practitioners may run a self-query on themselves, which is why applicants sometimes arrive with one in hand — useful context, but not a replacement for the organization's own query.
It is just as important to understand what an NPDB query does not reveal. It is not a criminal background check, not a credit report, and not confirmation that a license is active today. It surfaces reported actions and payments — nothing more. A practitioner with a spotless query may still have an expired license or an unreported concern, which is precisely why the NPDB sits alongside, not in place of, direct primary-source verification and exclusion screening in a complete file.
One-Time Query vs. Continuous Query
The NPDB offers two query products, and the distinction matters for ongoing monitoring. A One-Time Query returns a snapshot: as the NPDB puts it, “you will not be notified of any new reports submitted to the NPDB after the initial query date.” A Continuous Query enrolls a practitioner for a year-long period and delivers both the initial response and “all new or updated report notifications during the year-long enrollment,” with email alerts issued within 24 hours of the NPDB receiving a new report, per the Continuous Query guidance.
Continuous Query is the stronger compliance posture because it closes the gap between credentialing events: instead of learning about a license suspension at the next reappointment, you learn about it the day after it is reported. (Note that the NPDB is consolidating its One-Time and Continuous Query services into a single “NPDB Query” product in December 2026.) Pairing Continuous Query with monthly exclusion monitoring gives an organization near-real-time awareness of the two event types most likely to create liability.
When is an NPDB query required?
Hospitals face the clearest mandate. Federal law requires a hospital to query the NPDB when a practitioner applies for medical staff appointment or clinical privileges, and again as part of the mandatory two-year review of privileges or medical staff membership — a cadence the NPDB describes directly in its querying guidance. Enrolling practitioners in Continuous Query satisfies these mandatory querying obligations. Beyond hospitals, a range of eligible entities — health plans, medical groups, and others engaged in professional review — may and often do query as part of credentialing, and accreditors such as NCQA and The Joint Commission expect an NPDB query in the credentialing file.
How NPDB queries fit into credentialing
Within a credentialing workflow, the NPDB query is one input among several, and its output has to be handled correctly. A “self-query” result the applicant brings is not a substitute for the organization's own query. When a query returns a report, the credentialing committee must review it, document its analysis, and factor it into the appointment decision — a clean query and a query with reports are handled very differently, but both must be retained in the file. That documentation is a required component of an audit-ready credentialing file, and the query must be re-run at each recredentialing cycle or continuously through enrollment.
Practitioners also have rights in the system that credentialing teams should understand. A practitioner who believes a report about them is factually inaccurate may add a statement to the report and formally dispute it, and unresolved disputes can be elevated for review by the Secretary of HHS. When a disputed report appears in a query response, the committee should weigh the practitioner's statement as part of its review rather than treating the report as the final word.
Treat the query response itself as a dated artifact. Archive the full response, record the date it was run and who reviewed it, and store it with the rest of the file so the query's currency can be proven at survey. A query run too far ahead of the credentialing decision can be challenged as stale, just like any other verification, so time it to the committee's calendar.
Many groups route NPDB querying through a credentials verification organization; understanding what a CVO does helps clarify which party holds the NPDB registration and performs the query. However the work is divided, the standard is the same: query at appointment, query at reappointment or continuously, review every report, and prove it in the file. Handled that way, NPDB queries move from a box-checking chore to what they were designed to be — an early-warning system that protects patients and the organization alike.
See your own numbers in 60 seconds
CredTek gets providers in-network 40–60% faster — built and run by operators with decades of enterprise credentialing experience, with a human approval gate on every submission.
Run the ROI calculator →