Navigating the New European Medicines Agency (EMA) Data Catalog: A Guide for Accessing Centralized Drug Information

EMA data catalog access starts with the two public catalogues EMA and HMA launched for real-world data sources and studies. The Catalogue of RWD sources is live and lets you filter human and veterinary data sources by domain. If you need centralized European drug information, start there—not a national register.

Key takeaways

• EMA and HMA operate two public catalogues: one for real-world data sources and one for studies.
• The RWD sources catalogue is searchable without an account and supports human and veterinary filters.
• EMA identifiers (ATC, Orphanet, EMA product ID) do not replace national codes such as Swiss Pharmacode or BAG-SL.
• Developers should map catalogue fields to FHIR R4 resources and schedule regular reconciliation, not real-time sync.
• Search the catalogue directly at the EMA catalogue of RWD sources before building any downstream integration.

What is the EMA data catalog, and why does it matter now?

The EMA data catalog is the Agency's public interface for centralized medicinal product information and, following the HMA collaboration, for real-world data sources and studies. It matters because it replaces fragmented national lookups with a single EU-wide entry point for regulatory and real-world drug data. Pharmacists use it to verify marketed products; developers use it to build downstream feeds. It is not a dosing reference, and it does not confer market authorization in any individual member state.

EMA and HMA launched two public catalogues for real-world data: the Catalogue of RWD sources and the Catalogue of studies. The sources catalogue is the one most relevant to day-to-day drug information work. You can browse it at the EMA catalogue of RWD sources and see all human data sources or all veterinary data sources with a single filter toggle. For a pharmacist, that means you can check whether a real-world data source covers a specific therapeutic area before you rely on it for health technology assessment or formulary work. For a developer, it means the catalogue is a discovery layer, not necessarily the final data store.

What changed in the EMA data landscape over the last 12 months?

The most concrete change is the launch of the two public EMA-HMA catalogues for real-world data. Before this, real-world data sources were scattered across member states and often required direct contact with institutions. Now, the catalogue of RWD sources centralizes discovery, and the companion catalogue of studies does the same for ongoing and completed research. This is a structural change to EMA's public data access, not a cosmetic redesign.

What did not change: national medicines databases still operate independently. EMA's centralized data covers products authorized through the centralized procedure. It does not absorb every national authorization, and it does not replace the Swissmedic Spezialitätenliste or the US NDC directory. If your workflow spans the EU and Switzerland, you still need to query both systems.

How do I access and search the EMA data catalog as a pharmacist?

Go to the Catalogue of RWD sources, select the human data source filter, and search by active substance, indication, or data source name. You do not need an account to browse; login is only required for account-specific actions. The interface returns source descriptions and links to underlying studies where available.

Here is the workflow I use:

1. Open the EMA catalogue of RWD sources.
2. Choose "See all Human data sources" if you are working with human medicines.
3. Enter your search term—active substance or therapeutic area—and review the returned sources.
4. Click into a source to see its description and any linked studies.
5. Record the source identifier and the date you checked it, because catalogue entries can change between authorizations.

If you are verifying whether a product has centralized EMA data, cross-check the result against the national register of the member state where you dispense. The catalogue tells you what exists at EU level; it does not tell you what is on the shelf in your pharmacy today.

How do developers integrate with the EMA data catalog API?

Developers integrate with the EMA data catalog by reading its published endpoints and mapping results to FHIR R4 resources such as Medication and MedicinalProductDefinition. Start with the catalogue's API reference, then build a sync job that pulls changed records rather than reindexing everything daily. I have seen teams break integrations by treating the catalogue as a static database; it is not.

For developers, the practical pattern is:

• Fetch the source record from the EMA catalogue.
• Map ATC and Orphanet codes to your internal terminology.
• Store the EMA reference identifier as a foreign key, not as your primary key.
• Run a reconciliation job weekly against national registers where you operate.

If you are already working with EMA submissions, read our guide on EMA IDMP 2026 deadlines and FHIR submission readiness to see how the catalogue fits into the broader IDMP timeline. For the FHIR mapping layer itself, our FHIR R4 implementation guide covers the resource profiles you will likely need.

Which identifiers matter in the EMA data catalog?

The EMA system relies on ATC codes for therapeutic classification, Orphanet codes for orphan designations, and EMA internal product identifiers for centralized authorizations. These are not interchangeable with NDC or Pharmacode. If you are building a cross-border feed, you need a mapping table, not a direct substitute.

The rule I follow is: never use an ATC code as a product key. ATC classifies the substance; it does not identify a specific strength, dosage form, or marketing authorization. For that, you need the EMA product identifier and, in Switzerland, the Pharmacode and BAG-SL entry. Our guide on mapping RxNorm, SNOMED CT, and ATC covers the cross-system logic in more detail.

How does EMA data differ from Swissmedic and other national databases?

EMA holds centralized authorization data for the EU; Swissmedic holds the Swiss Spezialitätenliste (BAG-SL) for the Swiss market. A product authorized through EMA's centralized route still needs a separate Swiss registration and Pharmacode to be dispensed in Switzerland. Do not treat an EMA entry as proof of Swiss market availability.

The difference matters at the point of dispensing. In the EU, an EMA centralized authorization is valid across member states, but national reimbursement and dispensing rules still apply. In Switzerland, the BAG-SL is the authoritative list for reimbursed medicines, and Pharmacode is the machine-readable identifier on packaging. If you are comparing EMA data to national databases, expect three mismatches: authorization status, packaging identifiers, and reimbursement flags.

For the Swiss side, our guide to the Swissmedic Spezialitätenliste explains how to navigate the new digital landscape and where BAG-SL fits.

How does EMA verify and keep its drug data current?

EMA's verification runs through the centralized authorization procedure and the HMA-EMA catalogue governance. Data is updated when marketing authorization holders submit variations or when new studies are registered in the catalogue. There is no real-time guarantee; treat the catalogue as a source of record that still requires your own reconciliation before dispensing or publishing.

My rule of thumb is to check the "last updated" field on any catalogue entry and compare it against the national register before making a formulary decision. If the catalogue entry is older than the national record, trust the national record for local availability. If you are building an API integration, cache with a short TTL and revalidate on a schedule you control.

What should I do next with the EMA data catalog?

Search the catalogue for your product's active substance, verify the identifier set, and decide whether you need a manual lookup or an API sync. Pharmacists should bookmark the human data sources view; developers should schedule a quarterly reconciliation against national registers. The catalogue is a strong starting point for EU-wide drug information, but it is not the only source you need.

If you want a single source of truth that already normalizes EMA, Swissmedic, and FDA identifiers, you can search our drug database.

FAQ

Is the EMA data catalog the same as the EMA drug product database?

No. The EMA data catalog is the discovery interface for centralized product information and real-world data sources; the drug product database is the underlying authorization record. Use the catalog to find what exists, and the product database for the authoritative regulatory details.

Do I need an account to use the EMA data portal?

No. Browsing the Catalogue of RWD sources is public. An account is only required for certain account-specific actions, not for searching or viewing source descriptions.

Can I use EMA data to dispense medicine in Switzerland?

Not by itself. EMA centralized authorization does not replace Swiss registration. You need the product listed in the Swissmedic Spezialitätenliste (BAG-SL) and a valid Pharmacode for dispensing in Switzerland.

How often is the EMA real-world data catalogue updated?

EMA updates the catalogue when marketing authorization holders submit variations or when new studies are registered. There is no published real-time refresh schedule, so verify the "last updated" date on each entry before relying on it.

Should I build my integration on FHIR R4?

Yes, if you are exchanging medicinal product data. Map EMA catalogue fields to FHIR R4 resources such as Medication and MedicinalProductDefinition, and keep a local reconciliation step for national identifiers.