German & DACH Pharmaceutical Data Sources Compared

If you work for a non-German company and need reliable German or DACH pharmaceutical data, the first surprise is that the market is not one product. It is a stack of sources, each authoritative for a different layer, and the right answer depends entirely on what you are trying to do. A regulatory-affairs team, a market-access analyst and a procurement lead are all asking for "German drug data", yet each needs a different source. Choosing the wrong one costs weeks.

This guide groups the sources by data type, because that is how the decision is actually made. For each layer you will find what it is good for, where its limits are, and how to reach it with English access. At the end, a decision table maps the job to the source so you can route your own case in seconds.

One theme runs through every layer, so it is worth stating up front: the German market is unusually well documented, but the documentation is fragmented and German-first. There is an authoritative source for almost any question you can ask, yet those sources were never designed to be queried together, and most were never designed to be read in English. A team based in Munich absorbs that friction as background noise. A team based in Boston, Basel or Barcelona feels it as a hard barrier. Knowing which layer answers your question, and how to reach it without a German-speaking colleague on standby, is most of the battle.

1. Regulatory and authorisation data: the official agencies

For authorisation status, safety information and regulatory facts, the authoritative sources are the public agencies. Treat them as your system of record: no commercial provider overrides them on the question of whether a product is authorised.

• EMA (European Medicines Agency) for centrally authorised products, EU-level safety and shortage coordination, and product information. The public EMA medicines database is fully English.
• BfArM (Germany) for national authorisations, the German drug shortage register and classification systems. BfArM maintains English pages under its information on medicinal products portal.
• BASG/AGES (Austria) and Swissmedic (Switzerland) for the remaining DACH jurisdictions.

The federal PharmNet.Bund drug information system aggregates several of these German feeds, but the underlying data is German-first and the portals are not built to be queried together.

Use them for

Ground-truth regulatory status, safety signals, authorisation history and shortage notifications.

Where they stop

The agencies are not designed as a single, joined, machine-readable product-master feed across countries. Each portal answers its own question in its own format, mostly in German. If you need to merge authorisation status with pricing, availability and pack-level detail, that integration work is left to you. A second point is easy to miss: the agencies publish the regulatory truth, but they do not publish it on the identifier a commercial team works with. There is no reliable way to walk from an EMA product-information entry to a specific pack on a pharmacy shelf without a bridge, and that bridge is the product master described next.

2. Product-master and article data: the German basis

For structured product data such as active ingredient, strength, dosage form, pack size, product identifier and images, the authoritative German basis is the IFA Article Master. It is complemented by the ABDA data sources, including the ABDA-Artikelstamm, which are included alongside it rather than replacing it. This layer carries the PZN (Pharmazentralnummer), the central product number you join everything else on.

The IFA is the body that issues the PZN. Its PZN reference page is available in English and explains how the identifier is structured and assigned. If you plan to combine several German sources, decide early that the PZN is your primary key: it is the identifier every downstream dataset can be linked back to.

Use it for

Catalogue and master-data management, pack-level verification, and anything keyed to a specific product presentation.

Where it stops

Raw article data is the foundation, not the finished working feed. On its own it does not give you daily shortage status, pricing history or the analytics context most commercial teams need, and access is German-first. Registration and data-recipient access at source are aimed at the German pharmacy supply chain rather than at an international analytics team, so a non-German buyer usually reaches this layer more efficiently through a service that has already licensed and structured it and exposes it in English on the PZN.

3. Market-share, sales and forecasting data: the analytics houses

For sales volumes, market share and forecasting, the large commercial analytics providers are the reference. IQVIA is the best-known name here, alongside market-access-focused data services in the same category (for example pricing and access analytics such as the NAVLIN family of services). These are premium, sales-out oriented datasets built for commercial strategy.

Use them for

Market sizing, competitive share, launch tracking and commercial forecasting.

Where they stop

They are not the place to obtain the full authorised product master or day-to-day shortage and pricing detail at pack level. Their strength is aggregated commercial insight, not the operational reference data that procurement, regulatory and supply teams work with daily. They are also priced and licensed for strategic use, so pointing a data pipeline at them for routine pack-level lookups is rarely the right economics. Most teams run the analytics houses in parallel with an operational reference layer rather than expecting either to do the other's job.

4. Reimbursement and AMNOG data: the specialists

For German reimbursement and AMNOG pricing, specialist monitors track negotiated prices and HTA outcomes at product level over time. These are single-purpose tools focused on the reimbursement question: what was the added-benefit assessment, what price was negotiated, and how has it moved.

Use them for

Health economics and outcomes research, launch pricing models and reimbursement analysis across the German market.

Where they stop

A reimbursement monitor is deliberately narrow. It does not carry the product master, availability, shortage status or the broader active-ingredient dossiers, and it is typically German-first with no cross-source join.

5. The consolidation layer: one search across the stack

The gap every source above leaves is integration. A non-German team rarely wants five subscriptions in five formats, each with its own login and its own identifier scheme. It wants the answer in one place, joined on one key, in a language the whole team reads. This is the role pharmazie.com, operated by DACON Datenbank Consulting GmbH (founded 1989), plays for the German-speaking markets: more than 25 pharmaceutical databases in a single search, keyed on the PZN.

What sits inside that one search:

• the IFA Article Master and ABDA data sources as the product basis, with the IFA Article Master as the authoritative basis for authorised German products;
• structured active-ingredient dossiers for 63,589 active and excipient substances, including a dedicated field for antibiotic spectrum and resistances;
• daily-updated product-master, shortage and news data, and bi-weekly price updates;
• product data across more than 50 countries, with English access for international teams;
• data licensing and PZN/JSON API access for analytics and master-data pipelines;
• the MSV3-Client interface on the procurement side (availability query and digital ordering), live and in production as a standard add-on module.

The Eisbergsuche® search sits on top, so a single query resolves across the full stack rather than one database at a time. Two boundaries stated honestly, because credibility matters more than the pitch:

Price data is deepest for DACH plus some additional EU countries rather than Europe-wide, and further countries are being added in the coming months. The national shortage registers, above all the BfArM register, remain the system of record for shortage status itself; the consolidation layer surfaces and joins that information, it does not replace the register.

The practical value of this layer is not that it holds data the agencies do not. It is that everything arrives already joined on the PZN and already in English, so an analyst in another country stops paying the fragmentation tax described at the start. Instead of reconciling an EMA export, an IFA extract, a pricing file and a shortage list by hand, the analyst asks one question and receives one answer with every layer attached to the same pack. For a data-science or master-data team, the API access matters as much as the search: it means the joined feed can flow into an internal system rather than living in a browser tab.

Decision table: which source for which job

Read this table top to bottom by the job you actually have, not by the vendor you have heard of. The final row is where a non-German team consolidates the rest.

A short checklist before you subscribe

Before you commit to any source or stack of sources, run these five questions. They separate the teams that buy the right layer from the teams that pay for four subscriptions and still cannot join the data.

1. What is the job? Regulatory status, product master, market share and reimbursement are four different layers. Name yours before you shop.
2. What is your join key? If you will merge sources, standardise on the PZN now, because it is the identifier every German dataset links back to.
3. What language does your team read? Official German portals are German-first. If your analysts work in English, factor English access in from the start.
4. How fresh does it need to be? Product, shortage and news data can move daily; pricing on a bi-weekly cadence. Match the update frequency to the decision it feeds.
5. Feed or portal? A human-readable portal answers one question at a time. Analytics and master-data pipelines need licensing and API access, so confirm that before you buy.

Bottom line

For regulatory ground truth, go to the agencies: EMA at EU level, BfArM, BASG/AGES and Swissmedic across DACH. For market share and forecasting, go to the analytics houses. For AMNOG reimbursement history, go to the specialist monitors. And for the day-to-day working data, product master, active ingredient, availability, shortages and DACH pricing, joined on the PZN and reachable by API in English, a single consolidation layer over the German sources is the pragmatic choice for a non-German team.

That is where pharmazie.com fits: not a replacement for the agencies, but the layer that brings 25+ of these databases into one English-accessible search so your team stops stitching formats together and starts working from one joined feed. If you want to see the 25+ databases in a single search against your own product list, book a demo and we will run your cases live.