NPPES (CMS NPI Registry) vs Doximity: Side-by-Side Comparison
NPPES is the federal primary source for U.S. healthcare provider identity — 8 million+ NPI records, publicly downloadable, weekly-refreshed. Doximity is a professional network where ~80% of U.S. physicians maintain profiles. They serve different purposes: NPPES is the authoritative identifier record; Doximity is the clinician-facing social graph.
NPPES (CMS NPI Registry) vs Doximity, across 8 dimensions
| Dimension | NPPES (CMS NPI Registry) | Doximity |
|---|---|---|
| Data type | Federal provider identity — 10-digit NPI, taxonomy code, practice address | Physician professional network — peer connections, CME, secure messaging, NPI cross-reference |
| Coverage | 8 million+ active NPI records (individuals + organizations) | ~80% of U.S. physicians; 2M+ total clinicians (publicly disclosed) |
| Refresh cadence | CMS publishes weekly; Fonteum's newest serving-table system date was 2026-06-10 when checked 2026-07-12 | Self-maintained by clinicians; no public refresh cadence |
| License / Cost | U.S. government public-domain works (17 U.S.C. § 105) — free to use and redistribute with attribution | Free for clinicians; B2B/pharma advertising — pricing not public |
| API access | Public REST API at npiregistry.cms.hhs.gov/api — no key required for basic lookups | EHR partner integrations; not a public open API |
| Source provenance | Responses identify available source, date, and limitation fields; coverage varies and facts are not individually signed | NPI cross-reference for identity; self-attested credentials; no per-field provenance chain |
| Primary use case | NPI lookup, submitted taxonomy fields, and joins where another source supplies NPI | Clinician networking, referrals, CME credit, pharma outreach |
| Pricing | Free (federal public domain) | Free for clinicians; pharma/industry licensing — pricing not public |
Cells marked “—” indicate values not publicly documented by the respective platform. No data has been estimated or fabricated.
Which platform fits your team
When to use NPPES (CMS NPI Registry)
Use NPPES when the need is the federal record for NPI assignment and submitted taxonomy, address, and enumeration fields. Treat those fields as administrative data, not credentialing decisions, and join another source only when it supplies the NPI.
When to use Doximity
Use Doximity when the goal is reaching clinicians directly — for professional networking, CME delivery, or pharma sales-force alignment. Doximity's NPI cross-reference makes its profiles reasonably accurate for identity, but it is a professional network, not a regulatory data source.
Common questions
- Is Doximity a replacement for NPPES?
- No. CMS assigns NPI numbers through NPPES for use in HIPAA standard transactions. Doximity is a professional network that can cross-reference NPI but is not the assigning authority. NPPES is the primary source for NPI administrative fields; it is not a licensure or credentialing authority.
- Can I get NPI data from Doximity?
- Doximity cross-references clinician profiles with NPI numbers, but the data is not available in bulk via a public API or download. CMS NPPES provides the full 8M+ NPI record set as a free weekly CSV download and via a public REST API at npiregistry.cms.hhs.gov/api.
- Which is more current — NPPES or Doximity?
- NPPES is the CMS record for NPI assignment, but its names, addresses, taxonomies, and credential text depend on provider submissions and can be stale. Doximity profiles are maintained on their own schedule. Currency must be evaluated field by field from the applicable source date.
- What does Fonteum add on top of NPPES?
- Fonteum can connect NPPES to PECOS, QPP MIPS, Open Payments, and the NPI-bearing subset of OIG LEIE where the source supplies the same NPI. Facility sources generally use CCN, and state records may use license numbers or names, so those sources retain their own keys and limitations.
Last updated 2026-05-31. See all comparisons at /compare →
Add federal-data citations to your agent in 60 seconds.
Connect the hosted MCP server to your agent, or call the API with an issued bearer credential. See the developer docs for the current public contract.