.png)
SummaryIreland is the English speaking entry point to European medicine pricing, and its price file is both easier and harder to use than it looks. Easier, because the reimbursement list downloads as a plain CSV without any authentication. Harder, because that endpoint is undocumented, the terms prohibit commercial use without written consent, and the file carries a five digit house code that matches nothing outside the system that issued it.
The health service publishes a list of items that are reimbursable under the state schemes. It is the operative Irish price reference for community pharmacy.
| Property | Value |
|---|---|
| Price level | Reimbursement price, equal to the manufacturer price plus 8 percent wholesale markup |
| Cold chain products | Markup of 12 percent instead of 8 |
| Format | CSV and JSON, through an undocumented endpoint |
| Rhythm | Monthly |
| Code | Internal five digit scheme code |
| Pack size | Not reliably structured |
| Legal basis of the markup | S.I. No. 279/2013 |
On 5 September 2026 the file returned HTTP 200 at 1,114,128 bytes.
The derivation is arithmetically the simplest in Europe: divide by 1.08, or by 1.12 for cold chain products.
The difficulty is not the division. It is knowing which divisor applies. The cold chain property, which decides between the two, is not in the price file. It has to come from the product information, where storage between 2 and 8 degrees is stated. Any implementation that applies 1.08 to everything will be systematically wrong on exactly the products where the amounts are largest, because cold chain products skew expensive.
The resulting manufacturer figure is therefore derived twice over: once through a markup removal, and once through an external attribute that decides which markup applies. Both facts belong in the metadata.
Take a reimbursement price of 108.00 euro. For a normal product the manufacturer level is 100.00 euro. For a cold chain product the same published figure implies 96.43 euro, because the divisor is 1.12 rather than 1.08.
The difference of 3.57 euro per pack is not a rounding artefact. It is 3.3 percent of the derived value, applied consistently to the part of the assortment where unit prices are highest: biologicals, vaccines, insulins. A pipeline that ignores the cold chain flag therefore overstates manufacturer revenue exactly where the amounts matter most, and the error is invisible in an average across the whole file.
The same example shows why the divisor and its source belong in the data model as two separate fields. One says which rule was applied. The other says where the evidence for that rule came from, which in this case is a document outside the price file entirely.
Our initial assessment of Ireland was too optimistic. On closer inspection the price file carries only an internal five digit code, and that code is meaningless outside the reimbursement system. There is no shared key between the price file and the national authorisation register: no GTIN, no ATC code, no authorisation number.
A join is therefore possible only through name similarity, strength and pack size. That is fuzzy matching, with all that implies: a matching rule, a confidence score, a sampling review and a documented error rate. For a dataset that will be sold, sampling is not optional.
Two consequences follow for anyone planning Irish coverage.
Budget for the join, not for the download. The file is small and arrives in seconds. The work is in connecting it to everything else.
Ask for a key. Where a formal request for reuse is made, it is worth asking explicitly that a linkable identifier be added to the file. That is a cheap change for the publisher and it removes the entire fuzzy matching layer for every user.
The bulk access is technically open and free of charge. The terms of use prohibit commercial use without written consent. At first sight that looks like a dead end. It is not, because the Irish implementation of the European rules on the reuse of public sector information changes the procedure.
Three properties of that framework matter:
One detail decides whether a request is taken seriously: the older 2005 instrument has been expressly revoked, so any correspondence must cite the 2021 version. Citing the repealed one signals that the request has not been prepared.
That is why Ireland sits in the middle wave of a European build rather than at the back. The authorisation register is free. Only the price part needs a decision, and the decision is procedurally bounded.
The bulk route is an undocumented endpoint found in the front end code of the search application. It works, it is fast, and nothing obliges anyone to keep it. There is no archive either: what you can retrieve is the current state, and a month you did not fetch is a month you cannot reconstruct.
Two operational rules follow. Archive every retrieval yourself, with the date and the byte count. And monitor the status code, because the failure mode here is an endpoint that returns something other than the file rather than a file with wrong contents.
Against Belgium, Ireland loses on identification and wins on nothing: the Belgian file carries a pack specific code and a structured quantity, the Irish file carries a code that leaves the building. Against Spain, Ireland has the simpler formula and the weaker key. Against France, it has no tax step at all, but it also has no code that doubles as a GTIN.
Ranked by total implementation effort, Ireland sits in the middle of the European field, and almost all of that effort is in one place: connecting the price file to everything else. That is a useful thing to know before committing a schedule, because the download takes minutes and the join takes weeks.
Ireland is a small market and a disproportionately useful one for a European price product, for three reasons.
Language. It is the EU market where the price documentation, the terms and the correspondence are all in English, which lowers the cost of every subsequent step.
Cross-border sourcing. Irish prices are a regular reference point in parallel trade and shortage sourcing decisions, because the market is adjacent to the British system and inside the single market.
A clean legal test case. The reuse framework is well documented and the procedure is time bound. A request in Ireland produces an answer, which is more than can be said for several larger markets where terms are silent and no procedure exists.
It tells you the reimbursement price that the state scheme applies, which is the operative figure for community pharmacy and a defensible ceiling for a procurement conversation.
It does not tell you the manufacturer price, which has to be derived, nor what a hospital paid after a tender, nor anything about products outside the reimbursement schemes. As everywhere in Europe, the published figure is a list price, and the contract price sits below it and is not published.
Ireland gives you a free, small, monthly price file with the simplest back calculation in Europe and two real obstacles behind it: a house code that joins to nothing and terms that require a written decision before commercial use. Both are solvable, and the procedural route is unusually clear, with a deadline and an appeal path. Plan the join and the letter, not the download.
Related reading: European Drug Pricing Database: how cross-border prices work and Pharma pricing Germany: how the system works, plus ex-factory price and wholesale and pharmacy margins.
pharmazie.com is the consolidated pharmaceutical data platform by DACON Datenbank Consulting GmbH that bundles 25+ specialist databases into a single search, exclusively for healthcare professionals. Price coverage focuses on the DACH region and a number of further EU countries, with more countries following in the coming months.
