What manufacturers don’t realize about public EUDAMED data

Written by HATEM RABEH, MD, MSc Ing

Your Clinical Evaluation Expert And Partner

in
S

Most regulatory teams focus on getting the EUDAMED registration completed. They work through the UDI-DI assignment, the device description, the SRN linkage. But few stop to consider what happens after submission. What pieces of their clinical evaluation strategy become visible to the world.

This matters because transparency is not just a regulatory ideal. It is a structural shift in how medical device information is controlled and accessed.

The Public Access Framework Under MDR Article 33

MDR Article 33 establishes the structure for public access to device information through EUDAMED. The regulation distinguishes between data that must be made publicly available and data that remains restricted to competent authorities and Notified Bodies.

The distinction is clear in the regulation text. But the practical implications are often missed until the data is already live.

What becomes public is not limited to basic device identification. It extends into areas that touch clinical evaluation work directly. The clinical evidence summary, the summary of safety and clinical performance for implantables and Class III devices, the intended purpose, and the results of any conformity assessment procedures.

Each of these data points reveals strategic choices about clinical development, literature search boundaries, equivalence claims, and risk-benefit conclusions.

What Specifically Becomes Public

The list is defined in MDR Article 33(3). I work with this list every time a manufacturer prepares their technical documentation because the public-facing data must align perfectly with what the Notified Body reviews internally.

Here is what goes public:

Device identification and classification. The UDI-DI, device name, trade name, risk class, and nomenclature code. This tells the world exactly what category your device sits in and how it is regulated.

Intended purpose and indications for use. This is written in the IFU and echoed in the clinical evaluation report. Once public, any discrepancy between your external claims and your internal clinical justification becomes visible to auditors, complainants, and legal teams.

Summary of safety and clinical performance. For Class III and implantable devices, this is a required public document. It summarizes the clinical data, the risk-benefit analysis, and the post-market evidence. It is not a marketing brochure. It is a clinical declaration.

Many manufacturers treat the SSCP as a simplified version of the clinical evaluation report. That is a mistake. The SSCP is a standalone public document. If your clinical evaluation contains weak literature support or unsupported equivalence claims, the SSCP will either expose that or create inconsistencies that Notified Bodies will flag.

Certificate information. The Notified Body name, certificate number, and certificate status. This makes it transparent who certified your device and whether that certification remains valid. If the certificate is suspended or withdrawn, it becomes immediately visible.

Conformity assessment results. The type of conformity assessment procedure used and the conclusion. This signals whether the device went through full review, whether clinical investigation data was required, and whether any conditions were attached.

Here is where manufacturers underestimate the exposure. The combination of these data points reveals the clinical pathway the device followed. If a competitor analyzes your EUDAMED entry, they can reconstruct whether you used equivalence, whether you conducted clinical investigations, and what literature base you relied on.

What Stays Restricted

Not everything is public. MDR Article 33(4) specifies data that remains accessible only to competent authorities, the European Commission, and Notified Bodies.

This includes the full technical documentation, detailed risk management files, complete clinical evaluation reports, and post-market surveillance data sets. The internal CER, the literature appraisals, the equivalence justifications, and the PMCF protocols remain confidential.

But here is the tension. The public data must be consistent with the confidential data. If your SSCP claims robust clinical evidence but your CER relies on a single weak equivalence argument, that misalignment will surface during surveillance or re-certification.

I have seen audits where the Notified Body cross-references the SSCP against the full CER specifically to identify inconsistencies. If the public summary overstates the evidence, the entire clinical evaluation comes under scrutiny.

The Strategic Implication for Clinical Evaluation

The public nature of EUDAMED data changes how clinical evaluation must be structured. You are no longer writing only for the Notified Body. You are writing for a public record that can be analyzed by competitors, regulators in other jurisdictions, reimbursement bodies, and legal teams.

This requires a different level of discipline. Every claim in the clinical evaluation must be defensible at the summary level. Every equivalence argument must hold up under external review. Every literature search must be reproducible.

One area this affects directly is equivalence claims. If your clinical evaluation relies on equivalence to a predicate device, the SSCP will describe that clinical strategy in general terms. If a competitor reviews your SSCP and challenges the equivalence basis, you must be able to defend it publicly.

I have worked with manufacturers who realized post-submission that their equivalence claim was based on assumptions that would not survive public examination. Once the SSCP was live, they faced pressure from both the market and the Notified Body to strengthen the clinical data.

Another implication is the literature search timeline. If your SSCP references clinical data up to a certain date, any gap between that date and the certificate issue date signals a potential weakness in ongoing surveillance. Notified Bodies will ask why the literature was not updated closer to certification. The public record makes that gap visible.

How to Prepare Your Clinical Evaluation for Public Exposure

The discipline starts during CER development. You write knowing that a summary version will be public. That changes the rigor required.

First, every equivalence claim must be demonstrated with clear technical and clinical comparison tables. The SSCP will reference equivalence without showing the full analysis. But the claim itself must be defensible if questioned publicly. That means your CER must include side-by-side material composition, dimensional analysis, and clinical outcome comparison. If any element is missing, the public claim collapses under scrutiny.

Second, the literature search must be fully reproducible. Document your search strings, databases, inclusion criteria, and date ranges. The SSCP will describe the scope of the literature review. If a regulator or competitor attempts to replicate your search and finds different results, you need to explain why. That explanation only holds if your methodology is transparent and consistent.

Third, your risk-benefit analysis must be stated clearly in both the CER and the SSCP. The public summary cannot obscure risks. If the full CER identifies residual risks that require mitigation through PMCF, the SSCP must acknowledge that. Any attempt to soften the risk language in the public version will be flagged by the Notified Body.

Fourth, keep the intended purpose and claims tightly aligned across all documents. The IFU, the CER, the SSCP, and the EUDAMED registration must use consistent language. Even small variations will be interpreted as evidence of unclear clinical positioning. Notified Bodies will require harmonization before certification.

Finally, plan for the SSCP early. Many manufacturers treat it as a late-stage summary task. That leads to rushed writing and inconsistencies. The SSCP should be drafted in parallel with the CER. Both documents should mature together. That ensures alignment and reduces the risk of public-private mismatches.

The Consequences of Misalignment

When the public EUDAMED data does not match the internal technical documentation, the consequences escalate quickly.

The Notified Body will issue a finding. The finding will require you to either revise the public data or strengthen the clinical evaluation. Both paths delay certification. If the misalignment is significant, the Notified Body may suspend the review until the issue is resolved.

Competent authorities can also access both the public and restricted data. If they identify discrepancies during market surveillance, they may initiate an investigation. This can lead to device recalls, certificate suspension, or enforcement action.

Beyond regulatory consequences, public data affects market perception. Investors review EUDAMED entries to assess clinical robustness. Competitors analyze SSCP documents to identify weaknesses in clinical claims. Reimbursement bodies use public data to evaluate clinical value. Any weakness in your public clinical summary affects commercial success.

I worked with a manufacturer whose SSCP claimed extensive clinical evidence. The CER was based on a single clinical investigation with limited endpoints. When a competitor raised questions publicly, the competent authority requested a full review of the clinical evaluation. The manufacturer had to conduct additional clinical work to support the public claim. The delay cost them market position.

What This Means for Your Next Submission

If you are preparing a EUDAMED registration, treat the public data as carefully as you treat the technical file. Every statement in the SSCP must be traceable to the CER. Every claim in the intended purpose must be supported by clinical evidence. Every risk-benefit conclusion must hold up under external review.

Review your draft SSCP alongside the CER before submission. Identify any language that overstates the evidence. Identify any claims that cannot be defended publicly. Revise both documents to ensure alignment.

Ask yourself: if a competitor analyzed this SSCP, what questions would they raise? If a competent authority compared this SSCP to the full CER, what inconsistencies would they find? If an investor reviewed this SSCP, would they believe the clinical strategy is robust?

If you cannot answer those questions confidently, the clinical evaluation is not ready for public exposure. And if the clinical evaluation is not ready for public exposure, the EUDAMED registration is premature.

The shift to transparency under MDR is permanent. The discipline required to manage that transparency must become part of how clinical evaluation is planned and executed from the start.

In the next part of this series, I will walk through the EUDAMED Actor Registration process and what goes wrong when manufacturers misunderstand the economic operator roles.