SummaryEvery pharmaceutical product in the German market carries a PZN, the Pharmazentralnummer. It is the number on the package, in the ordering system and on the prescription record. But a number on its own answers almost nothing: not what the product costs, not what its approved product information says, not whether it is currently available. This article explains what the PZN is, what turns a bare lookup into a research system, and how one search resolves a single number into the full context a professional needs. It is written for healthcare professionals, not patients.
The PZN (Pharmazentralnummer) is the central identifier for medicinal products, medical devices and other pharmacy items in the German market. It is an eight-digit number assigned and maintained by IFA GmbH, which operates the information service for the German pharmaceutical market. Every product in distribution has one, and it is the key that ordering systems, wholesalers, pharmacies and billing all use to refer to the same item unambiguously. To understand how the PZN is structured, see our explainer on the German drug databases.
A simple lookup takes a PZN and returns the product name. That confirms identity, and nothing more. In practice a professional question is never just "which product is this?" It is "what does it cost, what does its Fachinfo say, is it available right now, and what are its other identifiers?" Those answers live in separate places: the price in the price data, the product information in the Fachinfo, the availability in the shortage register, the cross-references in the identifier registry. A bare lookup leaves all of that unresolved, so the number becomes the start of four more searches rather than the end of one.
The difference between a lookup and a research system is what the number resolves into. A research system treats the PZN as a key and returns the connected data in one view: the current price, the approved product information, the supply status, the pack and dosage-form details, and the related identifiers. Instead of confirming a name, it answers the professional question in one step. That is the line between looking something up and actually researching it.
The table sets a bare lookup against a research system on the dimensions that matter to a professional.
| Dimension | Bare PZN lookup | PZN research system |
|---|---|---|
| Product identity | Name and number | Name, number, pack, dosage form |
| Price | Not included | Current price, resolved from the PZN |
| Product information | Not included | Fachinfo / product information linked |
| Supply status | Not included | Current availability / shortage status |
| Related identifiers | Not included | Cross-references to other identifiers |
| Number of tools | Several | One search |
The mechanism is consolidation. Because the underlying databases, the identifier registry, the price data, the Fachinfo and the shortage register, are held together and keyed on the PZN, a single query can join them. A professional enters the PZN (or the product name, which resolves to the PZN) once, and the system returns price, product information and current supply status side by side. That is the Eisbergsuche® principle: the visible search box sits on top of many connected databases, so one entry surfaces everything attached to it.
The price is one of the data points a PZN resolves into. Rather than confirming the product name in one place and then opening a separate price source, a research system returns the current price directly from the PZN. For the detail on how German pharmaceutical prices are constructed, from manufacturer price through the statutory mark-ups, see our article on German drug databases and how price data fits into them.
Supply status is the data point that changes most often, and the one a bare lookup never carries. A shortage that is registered against a product should be visible the moment you resolve its PZN, not in a separate register you have to check by hand. A research system attaches the current availability to the PZN so that identity, price and supply status arrive together. For the wider picture on tracking shortages, see our overview of drug shortage management tools.
The users are the professional roles for whom the PZN is a daily key: purchasing and supply teams resolving availability and price before they order, pharmaceutical manufacturers and market-access teams checking how a product sits in the German market, hospital pharmacies, and IT teams that need the data through an interface rather than a screen. In each case the requirement is the same: not a name for a number, but the full context behind the number, in one place. The platform is for healthcare professionals only, not for patients.
Yes, and for system-to-system use it is the point. When a PZN needs to be resolved not by a person at a screen but inside an ERP, a pharmacy system or a market-access model, the same consolidated data is available through an interface, so the research system becomes a data source your own software queries. That is how the one-search principle scales from a single professional to an integrated workflow.
The PZN is the right key for the German pharmaceutical market, but a key is only useful for what it opens. A bare lookup opens a name; a research system opens the price, the Fachinfo and the current supply status in one search. pharmazie.com is the consolidated pharmaceutical data platform of DACON Datenbank Consulting GmbH, bundling 25+ specialist databases into a single search, for healthcare professionals only, so that one PZN resolves into the full context, on screen or through an API. The clearest way to see it is a short demo.
Related: German drug databases compared · Drug shortage management tools
The PZN (Pharmazentralnummer) is the eight-digit central identifier for pharmaceutical products, medical devices and other pharmacy items in the German market, assigned and maintained by IFA GmbH. Every product in distribution has one, and ordering systems, wholesalers, pharmacies and billing all use it to refer to the same item unambiguously.
Yes. Supply status is the data point that changes most often and is missing from a bare lookup. A research system attaches the current availability or shortage status to the PZN, so identity, price and supply status arrive together the moment you resolve the number, instead of in a separate shortage register you check by hand.
A lookup takes a PZN and returns the product name, confirming identity and nothing more. A research system treats the PZN as a key and resolves it into the connected data, current price, Fachinfo, supply status and related identifiers, in one view. The difference is between confirming a name and answering the actual professional question.
Yes. For system-to-system use the same consolidated PZN data is available through an interface, so an ERP, a pharmacy system or a market-access model can resolve a PZN in software rather than at a screen. That is how the one-search principle scales from a single professional to an integrated workflow.
In a consolidated research system the price is resolved directly from the PZN rather than looked up in a separate source. You enter the PZN (or the product name, which resolves to the PZN) once, and the current price is returned alongside the product information and supply status, so you do not open a second tool for the price.
It is for the professional roles for whom the PZN is a daily key: purchasing and supply teams, pharmaceutical manufacturers and market-access teams, hospital pharmacies, and IT teams that need the data through an interface. It is a tool for healthcare professionals, not for patients.