EUDAMED Clinical Investigations Module: What It Requires
- May 26
- 8 min read
Most clinical affairs teams treat EUDAMED as a reporting portal. That framing is a costly mistake. What the EUDAMED Clinical Investigations module requires goes significantly further than uploading documents to a central registry. The Clinical Investigations and Performance Studies (CI/PS) module is a structured regulatory compliance platform where every submission is validated, every data field carries legal weight, and every multilingual document must meet certified quality standards. If your organization is running EU medical device clinical investigations under MDR or IVDR, this article gives you the exact requirements, the translation obligations, and the preparation steps that separate a clean submission from a rejected one.
Table of Contents
Key Takeaways
Point | Details |
CI/PS module is not yet mandatory | The module activates only after a formal notice in the OJEU; no voluntary transition period exists. |
SRN required before submission | Manufacturers must complete actor registration and hold a Single Registration Number before filing any clinical investigation data. |
Structured data formats are enforced | Investigation summaries, SAE reports, and end-of-study results must meet validated EUDAMED data specifications or face rejection. |
Translation quality is a compliance variable | Patient-facing documents and investigator reports submitted across EU member states must meet ISO 17100, ISO 13485, and ISO 27001 standards. |
QMS integration is non-negotiable | EUDAMED does not replace internal regulatory discipline; it requires version control, CAPA records, and traceability to be managed in your QMS first. |
What the EUDAMED Clinical Investigations module requires
The CI/PS module is the most operationally complex component of EUDAMED. As of May 2026, the module is pending official activation and is not yet mandatory. It becomes mandatory only after a formal functionality notice is published in the Official Journal of the European Union. There is no voluntary use window before that point.
Once active, the module serves as a centralized registry covering the full regulatory lifecycle of MDR Article 62 clinical investigations and IVDR performance studies. That lifecycle includes:
Registration of new clinical investigations and performance studies prior to initiation
Modification submissions for substantial changes to approved protocols
Serious adverse event (SAE) reporting and device deficiency notifications during the study
End-of-study results publication for regulatory transparency obligations
Summary results disclosure accessible to competent authorities and, in many cases, the public
Before any of this is possible, your organization must complete actor registration in EUDAMED’s Actors module and obtain a Single Registration Number. Non-EU manufacturers must register through an EU Authorized Representative. Without the SRN, no lawful data submission can occur. That prerequisite alone has created delays for CRO teams who assumed the CI/PS module onboarding would work independently.
The CI/PS module’s timeline is distinct from the other five EUDAMED modules, several of which are already mandatory. That distinction matters for resourcing: your team cannot borrow lessons directly from the UDI or Notified Body modules because the CI/PS activation model and data scope differ substantially. Plan for it separately.
Data requirements for CI/PS module submissions
The module does not accept free-text document uploads in place of structured data entries. Structured submissions of investigation summaries, SAE reports, and end-of-study data in specified formats validated by competent authorities are required. Non-compliance with these data standards leads directly to submission rejection.
Here is the sequence of data obligations your team must prepare for:
Clinical investigation registration data. This includes the study title, sponsor identification (with SRN), device description, primary and secondary endpoints, study design, and participating member states. All fields must match the data already present in your technical file and investigator brochure.
Protocol modification records. Any substantial change requires a modification submission with a clear description of the change, the rationale, and the supporting evidence. Competent authorities use this data to track protocol drift over time.
Serious adverse event reports. SAEs must be submitted within the regulatory timelines set by the relevant competent authority. Each report requires structured fields covering event description, device involvement assessment, severity grading, and corrective actions taken.
Periodic and end-of-study reporting. Periodic safety update data and end-of-study reports must be submitted in EUDAMED’s validated format. For multi-site studies, consolidated reporting across all participating countries requires that each site’s data be reconciled before submission.
Summary results publication. Sponsors carry a transparency obligation to publish layperson-accessible summaries. These summaries must be accurate, sufficiently complete, and, critically, linguistically appropriate for the populations in which the study was conducted.
Discrepancies between your internal technical file and your EUDAMED submissions are a known audit trigger. Data alignment failures between internal documentation and EUDAMED submissions cause regulatory delays and audit findings. For multi-site studies, this risk multiplies: each site generates its own documentation trail, and your consolidated submission must reflect a coherent, validated dataset.
Pro Tip: Run a structured gap analysis against every required EUDAMED data field before your first live submission. Map each field to its source document in your QMS. If you cannot trace a field back to a controlled document, you have a compliance gap, not just a data entry problem.
Translation and linguistic quality requirements
The CI/PS module requires multilingual document management across up to 27 EU member states. That is where many clinical affairs and CRO teams encounter compliance exposure they did not anticipate at the study design stage.
Patient-facing documents, including informed consent forms, participant information sheets, and lay summaries of results, must be available in the official language of each country where the study is conducted. The requirements go beyond accuracy. Certified clinical SME translation under ISO 17100, ISO 13485, and ISO 27001 is the recognized standard for reducing regulatory risk and maintaining multilingual documentation integrity.
Several specific risks apply to CI/PS submissions:
Informed consent translation errors that alter the meaning of eligibility criteria, risk descriptions, or withdrawal rights create direct patient safety exposure and immediate regulatory grounds for study suspension.
Investigator report translation failures that introduce inconsistencies across sites can cause competent authorities to question data integrity at the consolidated reporting stage.
Lay summary inaccuracies in translated versions undermine the transparency obligation that the module is specifically designed to enforce.
Terminology drift across languages is a particularly serious risk for multi-site studies where different translators handle the same protocol. Without a governed Term Base, the same adverse event may be described with different terminology in German, Polish, and Romanian site documents.
Generic neural machine translation tools are not adequate for this environment. Consumer or broadly available SaaS translation engines present inconsistent terminology control and variable handling of negation and domain nuance. For EUDAMED-grade documentation, those failure modes are not acceptable.
Adverbum’s AI+HUMAN hybrid translation workflow is built for exactly this regulatory context. The process begins with asset integration, ingesting client Translation Memories and Term Bases to enforce terminology consistency from the first output. The proprietary LLM-based LangOps System then generates target language content constrained by your approved terminology and style guidance. A certified medical subject-matter expert reviews each document for technical accuracy, regulatory compliance, and contextual nuance. QA follows ISO 17100 and ISO 18587, with additional checks against MDR requirements where applicable.
Pro Tip: Establish a master Term Base for your clinical investigation before translation work begins. Every term covering adverse events, device descriptions, and inclusion criteria should be locked in that Term Base and applied consistently across all languages and all sites throughout the study lifecycle.
For further detail on managing multilingual clinical document risks across EU sites, the guidance is worth reviewing before your next protocol submission.
Preparing submissions: a practical framework
Getting to a clean, audit-ready CI/PS submission requires structured preparation well before the module goes live for your study. The following comparison captures what teams that prepare systematically achieve versus those that address issues reactively.
Preparation area | Proactive approach | Reactive approach |
Data attribute audit | Complete field-by-field review against EUDAMED data model before submission | Identify missing data only after submission rejection |
QMS integration | EUDAMED fields mapped to controlled documents with version control | Manual re-entry from uncontrolled working files |
Translation governance | Unified Term Base and ISO-certified translation workflow from study start | Ad hoc translation with no terminology control across sites |
Cross-functional alignment | Regulatory, Quality, IT, and CRO teams synchronized on submission calendar | Siloed workflows with mismatched data versions at submission deadline |
SAE reporting readiness | Pre-built reporting templates validated against EUDAMED field requirements | Improvised SAE reports formatted inconsistently per site |
Performing a complete attribute assessment of device data before testing submissions to EUDAMED is documented best practice for minimizing validation errors and delays. Early testing reveals system validation discrepancies that you can correct before mandatory reporting deadlines create pressure.
Strong QMS integration is non-negotiable here. EUDAMED is a transparency tool. It does not substitute for the internal regulatory discipline your QMS is supposed to enforce. Version control, CAPA records, and traceability documentation all need to exist in a controlled state within your own systems before they are reflected in a EUDAMED submission.
Coordinated workflows between Regulatory Affairs, Quality, IT, and CRO teams prevent the inefficient remediation cycles that delay market access. If those teams are not synchronized on a shared data governance plan before submission, you will discover the misalignments at the worst possible time.
My perspective on EUDAMED CI/PS compliance
I’ve reviewed how early adopters in the medical device space have positioned themselves for the CI/PS module, and the pattern I keep seeing is the same one that caused problems in the UDI and Vigilance modules: organizations treat EUDAMED as the compliance destination rather than the compliance output.
The module does not generate compliant data. It receives it. If your internal clinical investigation documentation is incomplete, mistranslated, or inconsistently structured across sites, submitting it to EUDAMED does not fix those problems. It exposes them to competent authorities in a centralized, auditable format.
What I’ve found actually matters is building the QMS backbone first. A robust QMS with SOPs for clinical project management is the most reliable path to CI/PS module readiness. That includes SOPs for translation quality that specify ISO 17100 certification requirements, not just “translate into local language.”
The translation issue specifically is underestimated. Multi-site studies in five or more member states mean five or more language-specific documents per protocol version, per amendment, per SAE report. Without ISO-certified clinical SME review and a governed terminology infrastructure, terminology drift is not a risk. It is a certainty.
Start preparation now, not when activation is announced. The CI/PS module has no voluntary transition phase. Once the OJEU notice publishes, the clock starts immediately.
How Adverbum supports EUDAMED-grade clinical translation
Clinical investigation submissions to EUDAMED require translation quality that most general-purpose language service providers are not equipped to deliver. AD VERBUM holds ISO 17100, ISO 13485, and ISO 27001 certifications, making it one of the few providers positioned to meet the full compliance profile for CI/PS documentation.
The AI+HUMAN hybrid translation workflow handles the complete document set your team needs: informed consent forms, investigator brochures, SAE reports, lay summaries, and protocol amendments. Every translation is produced through the proprietary LangOps System, constrained by your approved Term Bases, and reviewed by a certified medical SME before QA sign-off. Turnaround runs 3x to 5x faster than traditional workflows without compromising the audit trail your notified body or competent authority will expect.
For clinical affairs teams preparing for EUDAMED CI/PS activation, Adverbum’s certified localization services cover all 27 EU member state languages, including regional variants, with full data sovereignty through private EU-hosted infrastructure.
FAQ
What does the EUDAMED CI/PS module require for registration?
The CI/PS module requires sponsors to hold a valid SRN from the Actors module before filing any clinical investigation data. Registration submissions must include structured data on study design, device identification, endpoints, and participating member states.
When does the CI/PS module become mandatory?
The module becomes mandatory only after a formal functionality notice is published in the Official Journal of the European Union. There is no voluntary use period before that publication.
What data formats does EUDAMED accept for clinical investigation submissions?
EUDAMED requires structured submissions using validated data fields specified by competent authorities. Free-text document uploads do not satisfy the module’s data quality standards, and non-compliant submissions are rejected.
Are translations of clinical investigation documents required for EUDAMED?
Yes. Patient-facing documents and study summaries must be available in the official language of each participating member state. Certified clinical SME translation meeting ISO 17100 and ISO 13485 standards is the recognized compliance standard for these submissions.
What happens if EUDAMED submission data conflicts with your technical file?
Data discrepancies between your EUDAMED submissions and internal technical documentation are a documented audit trigger. Competent authorities treat these conflicts as indicators of broader documentation integrity problems, which can delay study approval or trigger formal corrective action requests.
Recommended