NPPES (CMS NPI Registry) vs IQVIA OneKey: Side-by-Side Comparison
NPPES is the free federal system of record for NPIs used by covered providers in HIPAA standard transactions. Its administrative fields do not establish licensure or credentialing. IQVIA OneKey is a commercial HCP/HCO reference database for life-sciences field operations.
NPPES (CMS NPI Registry) vs IQVIA OneKey, across 8 dimensions
| Dimension | NPPES (CMS NPI Registry) | IQVIA OneKey |
|---|---|---|
| Data type | Federal provider identity — 10-digit NPI, taxonomy code, practice address | Global HCP/HCO reference data — specialties, affiliations, publications, call-plan data, DEA (where applicable) |
| Coverage | 8 million+ active NPI records (individuals + organizations) | Millions of HCPs and HCOs across 100+ countries (per IQVIA marketing) |
| Refresh cadence | CMS publishes weekly; Fonteum's newest serving-table system date was 2026-06-10 when checked 2026-07-12 | — (not publicly disclosed) |
| License / Cost | U.S. government public-domain works (17 U.S.C. § 105) — free to use and redistribute with attribution | Enterprise license; pricing by quote |
| API access | Public REST API at npiregistry.cms.hhs.gov/api — no key required for basic lookups | OneKey API for licensed customers; not a public open API |
| Source provenance | Responses identify available source, date, and limitation fields; coverage varies and facts are not individually signed | Proprietary reference methodology; field-level lineage not publicly documented |
| Primary use case | NPI lookup, submitted taxonomy fields, and joins where another source supplies NPI | Pharma field force alignment, HCP targeting, medical affairs management, global HCO mapping |
| Pricing | Free (federal public domain) | By quote; pricing not publicly posted |
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 as the federal source for assigned NPIs and available submitted taxonomy and address fields for enumerated records. It is free and is the assigning source for the HIPAA identifier; other provider questions require their own primary sources.
When to use IQVIA OneKey
Use IQVIA OneKey when the work is pharma field force execution and requires global HCP coverage, publication records, call-plan data, or HCO affiliation mapping beyond the federal identity layer.
Common questions
- Does IQVIA OneKey use NPPES data?
- IQVIA OneKey incorporates federal data including NPPES as an input into its global HCP reference database, layering proprietary enrichment on top. The NPPES data itself is publicly available; IQVIA's value is in the enrichment and global coverage layers, not in NPPES access specifically.
- Is NPPES sufficient for pharma field-force targeting?
- NPPES provides the NPI, taxonomy, and address for U.S. prescribers, but lacks prescribing volume, publication records, call-plan data, and the global HCP coverage that pharma field operations require. IQVIA OneKey or similar commercial platforms are needed for the enrichment layer.
- What does NPPES not include?
- NPPES does not include prescribing volume, patient panel size, clinical publication records, DEA registrant data, HCO affiliation details, or any commercial intelligence. It is strictly the federal administrative identifier record. For enriched provider intelligence, commercial platforms like IQVIA OneKey or federal enrichment sources (PECOS, Open Payments, Care Compare) add the next layer.
- Can I reproduce IQVIA OneKey data independently?
- No. IQVIA OneKey is built on proprietary reference data whose sourcing and methodology are not publicly documented. NPPES, by contrast, is fully reproducible — the weekly CSV is publicly downloadable, and a team can independently verify any NPI record against the primary source.
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.