Board certification: what payers require vs what they prefer

What NCQA's credentialing standards actually require

No. The credentialing framework most health plans build their process around requires primary-source verification of your license, a National Practitioner Data Bank query, malpractice history review, and recredentialing at a minimum every 36 months — board certification is not one of the elements that framework mandates 1Ref 1National Committee for Quality Assurance (2026).Credentialing — NCQA.That NCQA's credentialing standards require primary-source license verification, an NPDB query, and recredentialing at least every 36 months, without mandating board certification.. A plan can credential a licensed clinician who has never sat for a specialty board exam, provided the license, work history, and screening checks all come back clean.

That distinction matters because it separates a hard credentialing requirement from a preference a specific plan or specific network product layers on top. Confusing the two leads to assuming a panel is closed to you when the real requirement is simply the standard license-and-screening file every credentialed clinician already has to produce.

The standard also sets an aging window on how old a piece of verification evidence can be before it has to be re-pulled — typically measured in months, not years — which is a very different thing from a specialty-board credential, since a license verification expires on a schedule and a board certification doesn't work the same way at all.

Where board certification shows up anyway

Individual payers sometimes reference board certification as a preferred qualification inside a specialty network, a tiered-network product, or a designated "center of excellence" style program — Anthem's provider policies 2Ref 2Anthem (2026).Anthem Provider Policies.That Anthem publishes its own provider and network policies, cited as one named example of a payer referencing specialty-network criteria, not as what all payers require. and UnitedHealthcare's policies and protocols 3Ref 3UnitedHealthcare (2026).UnitedHealthcare Policies and Protocols.That UnitedHealthcare publishes its own provider and network policies, cited as a second named example of a payer referencing specialty-network criteria, not as what all payers require. are examples of payers that publish this kind of specialty-network criteria on their own provider portals. Where it appears, it's usually a factor in which network tier or which specialty designation you're placed under, not a gate on basic panel participation.

Your own contract and the credentialing manual for the specific plan and product you're applying to control what's actually required for your specialty — a general industry pattern is not a substitute for reading your own agreement, and one payer's tiered-network preference says nothing about what another payer requires.

This is worth treating as a factual, payer-by-payer detail rather than a general rule: one plan's tiered-network program referencing certification says nothing about whether a different plan, or a different product from the same plan, does the same thing. Reading the specific provider policy for the network you're applying to beats extrapolating from what you've heard about the industry generally.

What actually blocks credentialing without it

The checks that can genuinely stop a credentialing file are a different list entirely: your CAQH ProView profile has to be complete and current, since that's the self-reported data most commercial plans pull from directly 4Ref 4CAQH (2026).CAQH.That CAQH operates ProView, the self-reported provider profile most commercial payers pull directly for credentialing.; an NPDB query has to come back without an unresolved adverse action 5Ref 5Health Resources and Services Administration (2026).National Practitioner Data Bank.That the NPDB collects malpractice payments and adverse licensure/privilege actions, which hospitals and plans query as part of credentialing.; and a screen against the OIG's exclusions list has to come back clear, since federal program payment can't be made for services from an excluded individual 6Ref 6HHS Office of Inspector General (2026).Exclusions Program.That OIG excludes individuals from federal health programs and that no federal program payment may be made for services from an excluded person, screened via the public LEIE..

None of these three checks care whether you're board certified. They care whether your license is real and current, whether your record is clean, and whether you're excluded from federal health programs — the actual gates every credentialed clinician has to clear, certified or not.

A gap or an inconsistency in any of these three — an expired license verification, an unresolved NPDB entry, a name that doesn't match across your CAQH profile and your exclusion screening — is what actually stalls a file. Board certification, or the lack of it, simply isn't part of that mechanism.

Checking your own file before you apply

Any practitioner can self-query the NPDB for a modest fee and see exactly what a credentialing committee will see when it pulls your record 7Ref 7Health Resources and Services Administration (2026).NPDB Self-Query.That any practitioner can self-query the NPDB for a fee and see exactly what a credentialing committee will see.. Doing this before you apply to a new panel, rather than finding out what's in your file at the same time a reviewer does, turns a potential surprise into something you can address or explain proactively.

A self-query is also the moment to confirm your CAQH profile, your license status, and your malpractice history are all internally consistent with each other, since a credentialing reviewer cross-references all of them against the same NPDB record.

It's a cheap, low-effort step relative to the time a credentialing delay can cost, and it puts you in the same position as the reviewer rather than reacting after the fact to a question you didn't see coming.

Credentialing, contracting, and hospital privileges are three different tracks

Board certification questions often get tangled up with a related but separate track: privileges without a hospital job, which is its own credentialing process built around a facility's medical staff bylaws rather than a payer's panel requirements. A solo outpatient clinician who never needs hospital privileges can be fully credentialed and in-network without ever touching that process.

It also helps to keep credentialing, enrollment, contracting as three distinct steps rather than one blurred process — credentialing verifies who you are, enrollment sets up how you get paid, and contracting sets the rates and terms, and board certification (where it matters at all) touches contracting far more than it touches the credentialing verification step itself.

Keeping these three tracks separate in your own head also helps when a payer's verification letters arrive asking to confirm your license and history — that's a credentialing-stage request, not a signal that your contract terms or your hospital status are in question.

What recredentialing checks about certification later

Recredentialing on the standard cycle re-verifies the same core file — license status, NPDB, exclusions, malpractice history — rather than introducing a new board-certification requirement partway through your relationship with a plan. If you obtained a specialty certification after your initial credentialing, updating your CAQH profile and file is worth doing anyway, since it's the update most likely to affect a tiered-network placement down the line.

A credentialing verification organization handling this work on a plan's behalf still follows the same NCQA-style standards, so the underlying requirements don't change based on which entity is doing the verifying — only the day-to-day contact point does.

Whether a plan uses its own staff or hands the work to a credentialing verification organization, the underlying standards it's checking against don't change — cvos and ncqa standards go together, and a CVO doing the legwork is still verifying the same license, NPDB, and exclusion file, not a different one.

The same questions resurface the day you're credentialing employee #1: a new associate's file gets checked against the identical license, NPDB, and exclusion standards yours was, board certification included or not, so the process you went through as the founder is a reasonable preview of what hiring later will involve.