NPI vs DEA Number vs CAQH ID: What's the Difference?

A credentialing coordinator pulls up a new physician's file and needs four things before lunch: the NPI, the DEA number, the CAQH ID, and whatever the payer portal insists on calling the 'Medicare provider number.' Type dea number lookup by npi into a search bar hoping one system will hand over the other, and you'll come away empty-handed. NPI, DEA registration, and CAQH ProView are three separate identifier systems, run by three separate organisations, for three separate reasons — and none of them cross-reference each other in any public database.

That's not a technical oversight. Each identifier was built for a different job: paying claims, authorising controlled-substance prescriptions, and cutting down duplicate credentialing paperwork. Confuse them and you'll waste an afternoon searching a registry that was never designed to hold what you're looking for. Here's what each one actually is, and where you actually find it.

It matters more than it sounds. Send a claim with the wrong number in the wrong field, or hand a payer a CAQH ID where they expected a PTAN, and the file bounces back for correction — sometimes weeks later, once someone finally reads past the first line of the rejection notice. Getting all four identifiers sorted before they're needed saves that round trip.

Provider identifiers explained: three systems that don't talk to each other

Anyone who works in billing, prescribing, or payer enrollment ends up juggling several ID numbers for the same person. They look similar on a printed page. They are not interchangeable, and mixing them up on a claim or a credentialing application is a common source of delay.

NPI: the billing and claims identifier

The National Provider Identifier is issued by the Centers for Medicare & Medicaid Services (CMS) through the National Plan and Provider Enumeration System (NPPES), as required under HIPAA. Every individual clinician and healthcare organisation that files electronic claims needs one. It's free to obtain, it's public — searchable in the NPI registry — and it's a 10-digit number with a Luhn check digit built into the last position, which is how systems catch typos before a claim gets rejected.

For the full mechanics, see what an NPI number is, how the NPI registry works, and how the check digit gets validated. It also carries a taxonomy code describing the provider's specialty, which is a separate piece of metadata worth understanding in its own right — see how NPI taxonomy codes work. Providers who don't have an NPI yet can see how to apply for one; the process is free and generally straightforward, since NPPES was built specifically to make enumeration simple.

DEA number: authorisation to prescribe, not proof of identity

A DEA number is issued by the US Drug Enforcement Administration to practitioners authorised to prescribe, dispense, or otherwise handle controlled substances. It has nothing to do with claims or enumeration — it's a controlled-substance authorisation, administered by a completely different federal agency for a completely different purpose than the NPI. The DEA number is an alphanumeric identifier tied to the registrant and their specific business activity, and it's renewed periodically rather than issued once for life.

Because DEA registration and NPI enumeration are handled by separate agencies with separate databases, a DEA number can't be derived from an NPI, and NPPES doesn't store or expose it anywhere in a provider's public record. That's the detail that trips up most searches, and it's worth its own section below.

DEA registration also isn't automatically tied to a single physical location or a single role. A physician who works across two hospital systems, or a nurse practitioner supervising prescribing across a group practice, may hold registration details specific to how and where they're authorised to prescribe. None of that nuance shows up anywhere near an NPI record — the NPI describes who a provider is for billing purposes, not what they're licensed to prescribe or where.

CAQH ID: a private credentialing shortcut

CAQH ProView is a private, non-governmental credentialing database. Many US health plans use it so providers don't have to re-key the same enrollment and credentialing information for every payer they work with. A CAQH ID is assigned by CAQH itself when a provider registers — it isn't issued by any federal agency, and it isn't a claims identifier. Like a DEA number, it's absent from NPPES: there's no such thing as a caqh lookup by npi number through the public registry. If a practice needs a provider's CAQH ID, the provider or their credentialing contact has to supply it directly, or the practice pulls it from its own credentialing file.

Not every payer participates, and not every provider needs a CAQH ID — it depends on which health plans a practice contracts with. A specialist billing only a handful of payers that don't use CAQH ProView may never need to register at all, which is part of why the CAQH ID is so easy to overlook until the moment a new payer contract specifically asks for it.

PTAN and the 'Medicare provider number': legacy terminology

Before HIPAA standardised the NPI, providers were tracked with plan-specific numbers. Medicare's version survives today as the PTAN — Provider Transaction Access Number — an identifier tied to a provider's individual Medicare enrollment record. Some billing staff still say 'Medicare provider number' out of habit; functionally, they usually mean the PTAN. The NPI is the identifier used across HIPAA transactions generally, but Medicare enrollment still tracks a separate PTAN alongside it, and the two aren't interchangeable on a claim. Anyone attempting a medicare provider number lookup by npi is really after the provider's Medicare enrollment record — and the PTAN sits inside that record, not inside NPPES.

A related search — a primary care physician id number lookup — usually just means finding that physician's NPI, since that's the standard identifier used across referrals, claims, and most patient-facing portals today. But if a specific payer or Medicare Administrative Contractor is asking for 'the ID number,' it's worth confirming whether they mean the NPI or the PTAN. Sending the wrong one is a routine cause of enrollment hold-ups.

Why weren't these systems ever merged into one lookup?

It's a reasonable question, and the short answer is jurisdiction. NPPES exists because HIPAA required a single standard identifier for claims — that's a CMS mandate. DEA registration exists because Congress gave the DEA authority over controlled substances specifically, which is a law-enforcement function, not a billing one. CAQH ProView exists because private health plans chose to pool their credentialing data through a shared vendor, which is a business decision, not a regulatory one. Three different mandates, three different owners, three different databases — merging them would mean rewriting the legal basis each one runs on.

• NPI — search the public NPI registry by name, practice location, or NPI number.
• DEA number — verify through the DEA's own registration verification channels, or check the provider's credentialing file.
• CAQH ID — obtained directly from the provider's CAQH ProView profile, or from the practice's credentialing records.
• Medicare PTAN — found in the provider's Medicare enrollment record, not in NPPES or CAQH ProView.

Can you look up a DEA number by NPI?

Directly, through NPPES or any public NPI registry: no. The registry stores enumeration data — name, taxonomy, practice address, NPI status — and nothing about DEA registration. The two systems were never built to be cross-linked, so a dea number lookup by npi in the literal sense returns nothing, no matter how the search is phrased or which tool runs it.

What actually works instead: verify DEA registration status through the DEA's own registration verification channels, or request the number directly from the practice's credentialing file, since it's routinely collected during onboarding and kept alongside the provider's other enrollment paperwork. If you're confirming a prescriber before dispensing, or before adding them to a formulary system, going straight to the DEA's own verification process is the reliable route — not a workaround through NPPES.

And a CAQH lookup by NPI number?

Same answer, same reason. CAQH ProView isn't connected to NPPES, so there's no public tool that accepts an NPI and hands back a CAQH ID. The provider registers with CAQH directly and shares the resulting ID with whichever plans or practices need it — usually once, during initial credentialing, then it's kept on file from then on.

A credentialing file, four different searches

This is exactly the situation a credentialing coordinator runs into when onboarding a new hire. The NPI is the easy part — a quick NPI registry search by name and practice location confirms it, and the check digit catches any transcription errors on the intake form. The DEA number has to come from the provider directly or from a DEA verification check, because no amount of searching NPPES will surface it. The CAQH ID likewise has to come from the provider's CAQH ProView profile, not from a claims registry. And the PTAN gets pulled from the practice's Medicare enrollment records, since it was assigned when the provider enrolled with Medicare specifically — a separate step from getting an NPI at all.

By the time the file is complete, it usually cites four different sources for four different numbers: NPPES for the NPI, a DEA verification record for the DEA number, a CAQH ProView export for the CAQH ID, and a Medicare enrollment letter for the PTAN. Coordinators who keep a running template with all four fields, and a note on where each one came from, spend far less time chasing corrections later.

None of that is a flaw in any one system. It's four organisations solving four different problems, and a credentialing file that treats them as one lookup ends up with three empty fields.

Patientary's own NPI lookup runs on live CMS NPPES data, and the same dataset is available programmatically through the MCP server for anyone building tools that need to verify a provider automatically — that's the reference layer Patientary is built to be, for people and for AI agents alike. It only ever answers for the NPI, though. DEA and CAQH questions still need to go to the DEA and CAQH directly, and there's no shortcut that changes that.