For hospital pharmacies whose article master, availability checks and substitution research still run by hand across separate systems. pharmazie.com puts the pharmaceutical databases you open one after another behind a single query.






Since the house list is exported and taken over automatically in SAP, nobody wants to do that by hand.
Head pharmacist, university hospital
Everything around the pharmacy is automated, and then the drug data arrives as a task for a person. The manual step is not a habit, it is what is left when the reference data and the system that consumes it were never designed to meet. It survives because it always works well enough to postpone the real fix by another quarter.
It is a drama every time. If the data update does not finish at the weekend, on Monday we have the wrong data in the system.
Managing director, supplying pharmacy
Nobody notices a stale record until an order fails, a report is wrong or a package that changed months ago is dispensed against an old entry. The change happened outside the house, so no internal process catches it, and the correction lands on whoever is on shift. That is why the cleanup is always someone doing it again by hand.
We look into every wholesaler separately, enter the PZN and see whether it is available. [A central search] would be a big time saving.
Pharmacist, military hospital
The information exists, it is just scattered across as many logins as you have suppliers. The cost is not the missing answer, it is the walk to get it, repeated for every product on a day when shortages are the normal state. And because each system is fine on its own, no single vendor ever owns the fragmentation.
Icebergsearch queries the databases you would otherwise open one after another and brings the results back together. Hospital pharmacies tell us the inefficiency is not any single lookup, it is the number of places a lookup has to happen.
A substitution decision runs along three axes, and those are exactly the axes your ERP usually does not carry. The active substance dossiers hold the pharmacological and toxicological detail behind the product, so the comparison happens on the substance and not on a product name.
When a product is not available locally, the answer is usually already on the market somewhere else. Our customers use the ABDA database German Finished Medicines together with International Medicines to open international procurement routes for medicines that are unavailable in Germany, for example individual imports in accordance with §73.3 AMG.
Once you have swapped a product, the risk profile has changed with it. The CAVE and interaction modules run the check against the ABDA databases rather than against a house list somebody maintains on the side.
pharmazie.com brings the databases a hospital pharmacy would otherwise open one after another into a single search. You look up a substance, check a substitution across substance, dosage form and strength, run a CAVE and interaction check, and reach international sources when a product is not available in Germany, all from one query over 25+ databases drawn only from official sources.
A substitution decision runs along three axes, and those are exactly the axes a hospital ERP usually does not carry. The Icebergsearch queries the connected databases together and returns the active substance, dosage form and strength on one card, so you judge whether a candidate genuinely matches instead of reading three systems side by side. That is the daily work of a hospital pharmacy, compressed into one lookup.
When a product is not available locally, the answer is often already on the market somewhere else, and a documented shortage is what legitimises an individual import under §73(3) AMG. Through the ABDA database German Finished Medicines together with the international medicines data, you find the PZN and the foreign equivalent in the same view, which is what customers in international procurement use us for.
Once you swap a product, the risk profile changes with it. The CAVE and interaction modules run the check against the ABDA database, so a substitution and its safety review sit in the same place rather than in a second tool opened after the fact. Shortage data for Germany is updated daily and carries EU and international alternatives, so the lookup stops being a tour of supplier portals.
One expectation we correct up front rather than let you discover later. Master-data delivery and ERP synchronisation are not part of what this page covers, so if automated export into SAP is the requirement, that is a different conversation.
The fastest way to judge fit is a 30-minute demo on your own products. Bring a section of your house list or a shortage you are working now, and we will run it live.
More clarity, faster research, and faster decision-making.






The shortage data for Germany is updated daily and carries EU and international alternatives, so the lookup stops being a tour of supplier portals. What we will not claim on this page is a proactive push: whether you get a pop-up or an e-mail when a product you carry goes short is exactly the kind of thing customers ask us in calls, and it is not something we have documented for hospital pharmacies. Ask for it live in the demo and make us show it rather than describe it. If alerting is the whole reason you are here, say so in the first five minutes.
Honestly: that is not what our data does, and it is the single most common expectation we have to correct in this segment. We tell you what the alternatives are, in Germany and internationally, and what the regulatory and substance-level facts behind them are. We do not run a live stock query into each wholesaler and report back who has three packs on the shelf this afternoon. If you are currently entering the PZN into every wholesaler portal one by one, we shorten the research half of that job, not the ordering half.
Through the ABDA database German Finished Medicines together with International Medicines, which is what our customers in international procurement use to find medicines that are locally unavailable, in Germany for example individual imports in accordance with §73.3 AMG. One limit worth naming: a clean automatic mapping from a German PZN to the foreign product name is something several customers have asked us for, and we are not going to present it as a finished feature here. Bring a handful of your real cases to the call and we will run them in front of you.
We are not going to answer this one from marketing. It is a fair and specific question, it comes up repeatedly, and how the platform behaves when a search genuinely has no alternative to offer is not documented in anything we can stand behind on a public page. So: unknown until you have seen it. It takes about a minute to check in the demo, and if the answer disappoints you, you will have found out before signing rather than after.
For the German market there is the Drug Pricing Germany Tool and the Transparency List AVWG, and customers do use us for price history that reaches further back than what they had before. For import prices specifically, we have no verified claim, and pretending otherwise would waste your time and ours. Treat German price transparency as covered and import price comparison as an open question to test in the demo with your own products.
For this segment, our answer is that data delivery and ERP synchronisation are not part of what this page covers. There is no export or interface feature approved for hospital pharmacies here, so a delta export, a CSV that your ERP reads without a decimal separator fight, an API or an MSV3 connection all belong in a different conversation. That conversation exists, it is just not this page. Two things to bring: the volume you need, because larger raw data exports sit under their own licence model, and the name of the system that has to consume the file.