.png)
Summary"We need market data" means two completely different things in pharma, and the confusion regularly costs a project. One is sales and prescription data, describing what was actually sold and prescribed. The other is master data, describing which articles exist, what they cost and what status they carry. IQVIA stands for the first. A search for an alternative is therefore worth pausing on, because the useful answer often is not a different analytics vendor at all: it is a different class of data.
This guide separates the two questions, names the mistake that costs the most, and explains what actually drives cost on each side. Third parties are named for orientation only; nothing here is a commercial recommendation about them.
IQVIA is a healthcare data and analytics provider. The core of the offering is market data in the narrow sense: sales and revenue measurement, prescription data, market shares, development over time, panels and the analyses derived from them.
Those are questions of the form:
For those questions a market research provider is the right route, and an article master is not. An article master does not know what was sold. No amount of field coverage changes that, because the data was never collected as a movement.
A pharmaceutical article master describes the market as an inventory rather than as a movement. It answers:
These are operational questions. They arise in master data management, procurement, billing, pricing and regulatory affairs, meaning wherever people work with specific articles every day. For the German market that layer is described in the pharmaceutical article master explained.
| Sales and prescription data | Article master and price data | |
|---|---|---|
| Describes | what was sold and prescribed | which articles exist and what applies to them |
| Unit | volume, revenue, share, usually aggregated | the individual article, identified by its code |
| Typical user | market access, business intelligence, strategy | master data, procurement, billing, regulatory |
| Time reference | retrospective, by period | state as of a date, continuously updated |
| Typical misuse | deriving a price for a specific pack from it | deriving a market share from it |
| Commercial model | quoted individually, no public price | priced by module, delivery form and cadence |
The most common is the attempt to get a defensible price for a specific pack out of aggregated market data. An average revenue per unit is not a dispensing price. It mixes trade levels, rebates, pack sizes and periods, and it cannot be back-calculated to a single article. Anyone pricing or costing on that basis is building on a number that was never made for the purpose, and the error does not announce itself: the figure looks plausible right up until someone checks it against an invoice.
The second most common runs the other way: estimating market share from an article master. The inventory says which articles exist. How often they cross a counter is not in it.
There is a third, subtler version. Teams sometimes use analytics data to answer a compliance question, for instance whether a product is still in distribution. Market data is retrospective and periodised; an article that left the market this week is still fully present in last quarter's panel. Status questions belong to the master data side by construction.
With market data providers there is usually no publicly stated price. Cost depends on scope, granularity, region, number of users and contract term, and pricing runs through a quotation. That is standard for the category and not a criticism in itself. It does make comparison hard, which is one reason searches for alternatives are so frequent.
With master data the structure is different. Price depends on three things: which modules you need, in which form you take them, and at what cadence. Those are answerable in a first conversation rather than after a scoping exercise. The trade-off between a raw licence and a maintained interface is set out in raw licence versus API for German drug data.
Sometimes the original question is genuinely a market research question, and then the honest answer is that a reference data platform is not the substitute. In that case the useful distinctions when comparing providers are coverage per country, the granularity you are actually allowed to see, whether the panel is projected or census-based, and the contract term. A broader map of the provider landscape, including where analytics houses sit relative to regulatory registers and reference data, is in European pharmaceutical data providers compared and, for the German-speaking markets, in German and DACH pharmaceutical data sources compared.
More often than the distinction suggests. A typical market access question runs: how has my product developed against the competition, and what does that mean for pricing? The first half is a market data question, the second is a master data question. The two datasets complement each other; they do not substitute for each other, and a budget that assumes one will cover both usually discovers the gap late.
The join between them is the product identifier. In Germany that is the PZN. Anyone bringing analytics data and master data together needs it on both sides. Without it, the join degrades into name matching, which is unreliable in exactly the cases that matter: generics with near-identical brand names, parallel imports, and pack variants that differ only in size.
This is also where cross-border projects get harder, because the identifier changes at every border. That problem, and the practical ways teams bridge it, is covered in pharma data for analytics teams.
One question is usually enough: do you want to know what happened, or what applies?
A practical test: write the question down as a sentence and look at the verb. Past tense with a quantity is analytics. Present tense with a status or a price is master data. It sounds crude and it resolves most procurement arguments in a minute.
pharmazie.com is the consolidated pharmaceutical data platform operated by DACON Datenbank Consulting GmbH, on the market since 1989. It brings 25+ pharmaceutical databases into a single search, the Eisbergsuche®, and is addressed exclusively to healthcare professionals rather than patients.
It answers the second class of question: which article, which pack, which price at which trade level, which status, which product information, and the equivalent product in another market. Product data covers 50+ countries; price data is focused on DACH with further countries following. Portal access starts at 135 EUR per month, net plus VAT, with the current scope on the pricing page.
It does not answer the first class. It does not measure sales, prescriptions or market share, and it is not a substitute for a panel provider where that is genuinely the question. Saying so is not modesty, it is the point of the article: choosing by data class first and by vendor second is what keeps the project out of trouble.
Sales and prescription data describe a movement. An article master describes an inventory. Both questions are legitimate and they are rarely the same one. The most expensive mistake is deriving a pack price from aggregated market data; the mirror image is estimating share from an inventory. If you need both, fix the joining identifier before you sign either contract.
If you want to check whether your question is a master data question, bring it along and book a demo.
This content is addressed to healthcare professionals and does not constitute medical advice. Third parties are named for orientation only; no commercial recommendation is implied. Last reviewed: September 2026.
