Navigating the New EU Clinical Trials Regulation (CTR) for Drug Data Management

Since 31 January 2025, Regulation (EU) No 536/2014 is the only route for clinical trials in the EU/EEA: one application through CTIS covers all 30 participating countries, and the results must be published in the same system. The transitional period that let sponsors keep filing under the old Clinical Trials Directive ended on that date. If you manage drug data, the practical change is that trial data stopped being a national filing problem and became a single structured dataset problem.

Key takeaways

• One submission, 30 countries: CTIS (Clinical Trials Information System) is the single entry point for EU/EEA trial applications and results.
• Applications split into Part I (scientific, assessed once by a Reporting Member State) and Part II (national, assessed by each Concerned Member State).
• Results are mandatory and public. The lay summary is due within 12 months of trial end, and it cannot be deferred.
• CTIS is structured data entry, not a document drop-box. Field-level quality is checked at submission, not cleaned up later.
• CTIS does not consume FHIR. Your internal FHIR R4 pipeline and your CTIS submission are two separate jobs.

What is the EU Clinical Trials Regulation (EU CTR No 536/2014)?

Regulation (EU) No 536/2014 is the EU law that governs how clinical trials are authorised, conducted and reported across the EU/EEA. It entered into force in 2014, applied from 31 January 2022, and became the sole legal basis for new and ongoing trials on 31 January 2025. It replaced the Clinical Trials Directive 2001/20/EC, which was transposed differently in every member state. The European Medicines Agency's Clinical Trials Regulation hub is the authoritative starting point for the current text and guidance.

For a data person, the important sentence is this: the regulation defines a single EU dataset for trials. Not a single process — assessment is still split between a Reporting Member State and the Concerned Member States — but a single set of fields, a single identifier scheme, and a single publication surface.

What changed for data management when the CTR replaced the Directive?

The CTR moved trial data from 30 national formats into one EU-wide structure, with one EU trial number, one assessment report per part, and one public record. Under the Directive, each country had its own forms, its own identifiers and its own publication rules. Under the CTR, the same structured record is submitted once and reused for every Member State concerned.

The last row is the one that catches teams out. A PDF that satisfies a national reviewer may not satisfy a structured field with a controlled vocabulary. That work moves upstream into your authoring process.

What is CTIS, and what is its data role?

CTIS is the EU's central clinical trial system: it is the workspace where sponsors draft and submit applications, where regulators assess them, and where the public reads the outcome. The EMA's CTIS page describes it as the single entry point for clinical trial applications and the public register for trials conducted in the EU/EEA. It covers the 27 EU member states plus Iceland, Liechtenstein and Norway.

Three things about CTIS matter for data management.

• It is the system of record. If it is not in CTIS, the trial is not authorised in the EU/EEA.
• It is the publication surface. Trial records and results are public through the CTIS public portal, which replaced the EU Clinical Trials Register for CTR trials.
• It is a structured data system. Sponsors enter fields, select values and attach documents — the fields are the data, and the documents support them.

CTIS is not a FHIR server. It has no public FHIR API, and it does not accept FHIR bundles as an application format. Plan accordingly.

What are the EU CTR data requirements for a clinical trial application?

A CTR application is one submission containing two assessed parts. Part I covers the scientific and product-level content: the investigational medicinal product dossier, the protocol, the investigator's brochure, the paediatric investigation plan where relevant, and the labelling. Part II covers national content: informed consent arrangements, investigator suitability, recruitment, insurance, and data protection under Regulation (EU) 2016/679.

The structured fields you will be asked for include:

1. Trial identification — EU trial number, title, protocol code, phase, sponsor and any legal representative.
2. Organisation data — sponsor and site organisations, tied to registered identities in CTIS.
3. Product data — active substance, strength, pharmaceutical form, route, and the ATC code where one exists.
4. Population and design — condition, age range, endpoints, comparator, and the Member States concerned.
5. Substantial modifications — every change after authorisation creates a new version of the record, not an overwrite.

Two practical notes. First, product identity should come from one internal source, not be retyped per trial — substance names and ATC codes drift fastest when they are typed by hand. Second, organisation identity is validated at submission, so confirm your sponsor and site records exist before your submission window opens.

How do you submit clinical trial results data to CTIS?

Results are submitted through the same CTIS sponsor workspace, within fixed deadlines measured from the end of the trial in the last Member State concerned. The results section carries a summary of results in lay language plus the clinical study report. Publication happens on the CTIS public portal.

The lay summary cannot be deferred. The clinical study report can be deferred on justified scientific or technical grounds, but the justification itself is part of the record. This is the single most common compliance gap I see: teams treat results as a post-publication task and discover that the lay summary is a fixed-date deliverable that nobody owned.

Write the lay summary from the protocol, not from the CSR. By the time the CSR is locked, the deadline is close and the plain-language version becomes a rush job.

How do FHIR and EMA clinical trial data standards fit into the CTR?

They fit around CTIS, not inside it. EMA's data standards work — IDMP, the SPOR master data services, and the FHIR-based interfaces EMA has been building for regulatory submissions — governs how product and organisation data is identified and exchanged. CTIS itself expects structured entry through its own interface. So the realistic architecture is: your internal systems speak FHIR R4 and hold IDMP-aligned product identifiers, and a controlled mapping layer produces the CTIS submission.

If you are building that internal layer, our FHIR R4 implementation guide for medication data covers the resource shapes worth standardising on before you map to a regulator's fields. And because the same product identifiers feed both trial records and marketed-product records, the EMA IDMP 2026 deadlines guide is the companion piece — get the substance and product identifiers right once and both jobs get easier.

Honest limit: no amount of FHIR alignment removes the need to enter CTIS fields manually or through CTIS's own mechanisms. The win is consistency, not automation.

What is the impact of the CTR on multi-state trials and pharmaceutical data?

The CTR's biggest operational effect is that multi-state trials stop being N parallel projects. One application, one EU trial number, one results record — with national differences confined to Part II. For a sponsor running the same protocol in six countries, that removes six separate identifier schemes, six publication timelines and six result-reporting obligations.

It also raises the cost of getting product data wrong. A single incorrect ATC code or substance name propagates into every Member State concerned, the public record, and the results publication. There is no national reviewer who quietly fixes it for you.

The CTR applies in the EU/EEA only. Switzerland is not covered: Swiss trials run through Swissmedic and the cantonal ethics committees, not CTIS, and Swiss product identity runs on Pharmacode and BAG-SL entries rather than EU identifiers. If you operate in both, read our Swissmedic Spezialitätenliste 2026 overview — the register mechanics are genuinely different, and assuming CTIS equivalence is a common mistake. In the US, trial registration and results reporting run through ClinicalTrials.gov under separate rules, and product identity uses NDC rather than ATC. Three systems, three identifier families.

What are the practical challenges and best practices for data teams?

The recurring failures are organisational, not technical. The data is usually available somewhere; it is not owned by anyone, and it is not modelled as a single object. Four rules of thumb that have held up.

• Model the trial once. Build one internal trial object with CTIS field names as attributes. Every downstream artefact — application, results, publication — reads from it.
• Pin product identity to one source. Substance, strength, form and ATC come from a maintained catalogue, not from a protocol Word file.
• Version, never overwrite. Substantial modifications create new versions. If your database updates in place, you cannot reconstruct what was assessed.
• Assign the EU trial number an owner. It should appear in your CTMS, your safety database and your document management system with the same value and the same format.
• Start the lay summary at protocol finalisation. Twelve months sounds generous until the CSR slips.

A short pre-submission check catches most of it: organisation records exist and match, product identifiers resolve, the EU trial number is consistent across systems, Part II national documents are complete for every Member State concerned, and the results owner is named in the trial plan.

Next steps for ongoing CTR compliance

Start with the two registers you already have: your product catalogue and your organisation list. Confirm that every substance you trial carries a resolvable identifier and an ATC code where one exists, and that your sponsor and site organisations are registered correctly. Then map your internal trial object to the CTIS fields and keep that mapping under version control.

If you need a product reference layer to sit underneath that work — substance names, ATC codes, and national register identifiers for the EU, Switzerland and the US in one place — you can search the catalogue at drug-database.com and read the API reference before you decide whether you need an integration at all. For many teams, a lookup is enough.

FAQ

Does the EU Clinical Trials Regulation apply to trials that started before 2022?

No, not automatically. Trials authorised under the old Directive had until 31 January 2025 to transition into CTIS, and that window has closed. Any trial still running in the EU/EEA now sits under the CTR and its results obligations.

Is CTIS the same as the EU Clinical Trials Register?

No. The EU Clinical Trials Register published information on trials under the old Directive. For trials under the CTR, the CTIS public portal is the register, and it carries the full record from application through results.

Can a sponsor defer publication of clinical trial results in CTIS?

The clinical study report can be deferred on justified scientific or technical grounds. The summary of results in lay language cannot — it is due within 12 months of the end of the trial, or 6 months for a paediatric trial.

Do I need FHIR to submit to CTIS?

No. CTIS has no public FHIR interface. FHIR R4 and IDMP alignment help you keep product and organisation identifiers consistent internally, which reduces errors in the CTIS fields, but the submission itself goes through CTIS.

Does the CTR cover Swiss or US trial sites?

No. The CTR covers the EU/EEA — 27 member states plus Iceland, Liechtenstein and Norway. Swiss trials go through Swissmedic and cantonal ethics committees; US trials register on ClinicalTrials.gov. The data models and identifiers differ.