What is IQVIA OneKey?
IQVIA OneKey is a b2b contact & company data tool. Global healthcare reference database built from IQVIA's massive pharmaceutical data business. Strong international coverage, but the platform feels dated and pricing is opaque.
Best for: Global pharma and life sciences teams that need international provider data
Best For
Global pharma and life sciences teams that need international provider data
IQVIA OneKey Overview
IQVIA OneKey is the reference database the pharmaceutical industry quietly runs on. It sits underneath the commercial operations of most top-20 pharma companies, feeding clean provider identities into their CRMs, MDM systems, and territory tools. The dataset is enormous: more than 10.9 million healthcare professionals across roughly 248 physician specialties, with over 1,000 attributes available in IQVIA's wider ecosystem. If you sell drugs globally and need one consistent ID for every doctor in 100 countries, this is the standard.
OneKey's reason to exist is the OneKey ID, a persistent unique identifier that ties a provider record to every other IQVIA dataset. IQVIA also owns the prescribing data, claims, and market measurement, so a pharma commercial team can start with a OneKey provider record and connect it straight to that doctor's prescribing behavior, affiliations, and the facilities they practice at. No other reference vendor connects identity to that depth of transactional data inside one company.
The data gets maintained through a blend of primary research (people actually calling and confirming), government and licensing sources, transactional signals, and customer change requests. IQVIA publishes audit results to defend the quality; the 2026 demographic audit reported 100% accuracy on its random sample. The platform is delivery-agnostic. You can pull data through an API, pre-built CRM connectors (Veeva, Salesforce), flat-file feeds, or the OneKey web interface and List Finder for building targeted lists.
The catch is that OneKey shows its age and its price. The web tooling feels like enterprise software from a decade ago, and pricing is custom, opaque, and aimed squarely at companies with real budgets. US-only sales teams that just need clean physician contacts often find faster, cheaper answers from Definitive Healthcare, Veeva OpenData, or a per-record service. OneKey earns its keep when global reach and prescribing-data linkage are non-negotiable.
OneKey is actually a family of products, not a single SKU, and that confuses a lot of evaluators. The core is OneKey Reference, which is the HCP and HCO identity dataset. On top of that, IQVIA layers OneKey Insights (engagement and digital-channel signals on each HCP), OneKey List Finder (the web tool for building targeted lists), and the OneKey API and Data Stream for keeping CRMs and MDM systems current. Most pharma commercial deals bundle Reference plus an integration channel plus a list-building tool, with engagement signals added when digital and omnichannel marketing teams are involved. Scoping which pieces you actually need is the single biggest lever on contract size.
Integration is where IQVIA quietly outflanks rivals. OneKey ships with native connectors for Veeva CRM, Salesforce Life Sciences Cloud, IQVIA's own Orchestrated Customer Engagement (OCE), and Reltio MDM. There is also a documented REST API for custom pipelines and pre-built mappings for common pharma data lakes on Snowflake and Databricks. The practical impact: a Veeva-running biopharma can wire OneKey into the CRM in weeks rather than quarters, and the OneKey ID flows through MDM so every downstream system (Veeva, ERP, finance, transparency reporting) joins on the same key. Teams without this integration depth typically rebuild the equivalent themselves at higher cost and lower data freshness.
Pros & Cons
Use Cases
Global Pharma Aligning Territories Across 40 Countries
A top-20 pharma company is launching an oncology drug across North America, Europe, and Asia-Pacific. Each market has different provider registries, naming conventions, and licensing bodies, which normally means 40 messy reference files. The team uses OneKey as the single global reference, assigning every target oncologist a OneKey ID and mapping their hospital affiliations. Territory alignment that used to take a quarter and constant reconciliation now runs off one consistent dataset. Field reps in every country work from the same provider universe, and headquarters can roll up targeting globally without manual matching.
Linking Provider Identity to Prescribing Behavior
A specialty pharma commercial team wants to focus reps on high-value prescribers rather than spraying the whole specialty. Starting from OneKey provider records, they connect each target's OneKey ID to IQVIA prescribing data and rank physicians by volume and trend in the relevant therapeutic class. Reps get call lists that prioritize doctors already writing in the category plus rising prescribers worth an early visit. Because the identity and behavioral data share one ID, there's no fragile vendor-to-vendor matching, and the segmentation refreshes cleanly each cycle.
Feeding Clean HCP Data Into Veeva CRM via MDM
A mid-size biopharma running Veeva CRM struggles with duplicate and stale physician records that confuse reps and break compliance reporting. They wire OneKey into their master data management layer as the trusted source, using the OneKey ID as the golden key for HCP identity. Pre-built connectors and the OneKey Data Stream keep records current as providers move practices or change affiliations. Duplicate rates drop, reps trust the data in the field, and aggregate-spend reporting maps cleanly to verified provider identities.
Key Features
- Global provider database
- Prescribing data
- Affiliation mapping
- Compliance tracking
- Territory planning
- CRM integration
Pricing
| Plan | Price |
|---|---|
| Enterprise | Custom pricing only |
Pricing as of 2026. Check IQVIA OneKey's website for current pricing.
Pricing Analysis
IQVIA does not publish OneKey pricing, and there's no self-serve or trial tier. Everything runs through enterprise contracts negotiated with IQVIA's commercial team, scoped by geography, the number of attributes and datasets you license, delivery method (API, feeds, connectors, web), and how OneKey ties into other IQVIA assets like prescribing and claims data.
Expect real money. Industry reporting puts top-20 pharma spend on IQVIA's real-world data and reference assets in the multi-million-dollar-per-year range, though a narrow OneKey-only reference license for a smaller company lands well below that. Pricing typically scales with country coverage and dataset breadth, so a US-only reference feed costs far less than global coverage plus prescribing linkage. Because nothing is published, the only way to get a real number is a scoped conversation with IQVIA.
For budgeting, treat OneKey as a strategic, multi-year platform commitment rather than a tool you trial and cancel. If your use case is narrow (US physician contacts for a small sales team), the enterprise minimums will likely feel steep, and a per-record provider service or Definitive Healthcare will be more cost-effective. If you need global identity plus IQVIA data linkage, OneKey's pricing is the price of admission to a capability nobody else sells.
Frequently Asked Questions
What is IQVIA OneKey used for?
OneKey is a healthcare provider reference database that gives pharma and life sciences teams clean, consistent identity data on doctors and healthcare organizations worldwide. Its main job is to be the single source of truth for who a provider is, where they practice, and how they're affiliated. Commercial teams use it to align sales territories, feed CRMs and MDM systems, and connect provider identity to prescribing and claims data through the OneKey ID.
How much does IQVIA OneKey cost?
IQVIA doesn't publish OneKey pricing; it's sold through custom enterprise contracts only. Cost depends on country coverage, how many datasets and attributes you license, and delivery method. Larger pharma deals reach the millions per year across IQVIA's data assets, while a narrow US-only reference feed costs much less. You'll need to contact IQVIA for a scoped quote.
How is OneKey different from Veeva OpenData?
Both provide HCP reference data, but OneKey's edge is global coverage and direct linkage to IQVIA's prescribing and claims datasets. Veeva OpenData is built to plug natively into Veeva CRM and is strong on US physicians, but its international coverage is thinner. If you already run Veeva CRM and sell mostly in the US, OpenData is the path of least resistance. If you need global reach or prescribing-data linkage, OneKey wins.
Does OneKey include physician prescribing data?
OneKey itself is a reference and identity dataset, but its real value is that the OneKey ID connects each provider to IQVIA's prescribing and claims data, which are licensed separately. So you don't buy prescribing data inside OneKey; you license it alongside and join it through the shared ID. That single-vendor linkage is the main reason global pharma chooses OneKey over standalone contact providers.
Is IQVIA OneKey good for US-only sales teams?
It can be overkill. OneKey's strengths are global coverage and IQVIA data linkage, capabilities a US-only team may never use while still paying enterprise prices. For US physician contacts and prospecting, Definitive Healthcare, Veeva OpenData, or a per-record provider service usually deliver what you need faster and cheaper. Choose OneKey when global reach or prescribing linkage genuinely matters.
What is the OneKey ID and why does it matter?
The OneKey ID is a persistent unique identifier IQVIA assigns to every healthcare professional and healthcare organization in the OneKey universe. It stays with the provider across moves, name changes, and affiliation changes. The reason it matters is data joining: because IQVIA also licenses prescribing (LRx, Xponent), claims, and market-measurement datasets, the OneKey ID is the single key that joins identity to behavior across all of those. Without it, joining provider records across vendors or even across IQVIA's own datasets requires fragile name-and-address matching.
How does OneKey integrate with Veeva CRM?
IQVIA ships a pre-built connector for Veeva CRM that syncs OneKey HCP and HCO records into Veeva accounts, including affiliations and the OneKey ID as a stamped attribute. Most pharma running both treat OneKey as the source of truth in their MDM layer (often Reltio), then push the cleaned records into Veeva on a nightly or near-real-time cycle. Veeva's Network MDM can sit between them. Deployment time is usually 4-10 weeks depending on whether you also enable OneKey Insights and engagement signals.
What are the main IQVIA OneKey alternatives?
Veeva OpenData is the closest US-focused alternative and integrates more cleanly if you already run Veeva CRM. Definitive Healthcare offers broader US commercial intelligence (facilities, executives, financials) and is friendlier for medtech and health-IT sellers. Symphony Health provides prescribing and projected claims data competing with IQVIA's RWD assets. Komodo Health competes on patient-journey analytics rather than reference identity. For pure US physician contacts at lower cost, per-record services like Provyx or NPPES-based providers cover the basics.
Does IQVIA OneKey have an API?
Yes. The OneKey API is a REST interface for querying provider records, affiliations, and IDs programmatically, and the OneKey Data Stream is a feed-based option for keeping warehoused copies current. Both require an enterprise contract; there is no public sandbox or free tier. Most teams use the API for ad-hoc lookups and the Data Stream for CRM and MDM synchronization, since streaming updates avoid the latency of nightly batch refreshes.
Similar Tools
Reviewed by Rome Thorndike. Last verified 2026-06-03.
Pricing, features, and ratings are based on vendor documentation, public filings, product demos, and feedback from sales teams using these tools in production. We update reviews when vendors ship major releases or change pricing.