EU MDR and CE marking for medical devices

EU MDR 2017/745 replaced the Medical Device Directive with a substantially more demanding technical documentation framework. The transition has not been a paperwork expansion—it has been an evidence-quality reckoning. Notified bodies that previously reviewed documentation at a surface level are now conducting deep technical reviews of clinical evaluation methodology, GSPR conformance rationale, and post-market surveillance infrastructure. Engineering teams that treated CE marking as a documentation exercise under MDD are discovering that EU MDR requires the engineering evidence to actually exist, not merely be described.

MANKAIND supports engineering teams pursuing CE marking by ensuring that the technical documentation is a structured reflection of the engineering work—not a retrospective assembly of documents that approximate what the engineering work looked like. The technical file is built continuously from engineering decisions, not compiled at the end of development.

General Safety and Performance Requirements: a design specification framework

The General Safety and Performance Requirements in Annex I of EU MDR are not compliance checkboxes. They are a structured engineering specification framework. GSPR 1 requires that devices achieve the performance intended by the manufacturer and not compromise clinical condition or patient safety. GSPR 6 requires that risks be reduced as far as possible while maintaining the benefit-risk ratio. GSPR 10 through 22 address specific engineering characteristics—chemical, physical, biological, radiation, software, and usability requirements—that the device must meet.

Demonstrating GSPR conformance means showing, for each applicable requirement, that the engineering design satisfies it—through conformance with a harmonized standard, through reference to a common specification, or through an alternative technical solution supported by specific evidence. The GSPR checklist is the backbone of the technical file's design documentation section, and it must be connected to the actual design and testing records that substantiate each claim.

MANKAIND maintains the GSPR mapping as a live document that tracks the engineering evidence for each applicable requirement. When a design change is made, the platform flags which GSPR entries are potentially affected and prompts the engineering team to update the conformance evidence. The checklist is never out of date because it is connected to the engineering record, not maintained separately from it.

Harmonized standards: the technical shortcut that requires engineering discipline

Conformance with a harmonized standard creates a presumption of conformance with the GSPR provisions the standard covers. That presumption is valuable—it reduces the evidentiary burden significantly for teams that can genuinely demonstrate standard conformance. The challenge is that claiming standard conformance requires demonstrating it, and notified bodies are increasingly rigorous about the difference between a standards claim and a standards demonstration.

For a device claiming conformance with ISO 10993-1 on biocompatibility, the technical file must contain the biological evaluation plan, the individual test reports, and the biological evaluation report that integrates them into a risk-based conclusion. For a device claiming conformance with IEC 60601-1 on electrical safety, the test reports must cover the specific configurations in which the device will be used. MANKAIND maps the device's characteristics to the applicable harmonized standards suite early in development, generates the standard conformance tracking structure, and maintains the connection between each standard's requirements and the engineering evidence that satisfies them.

Clinical evaluation: engineering evidence for clinical claims

The clinical evaluation under EU MDR is not a literature review. It is a structured engineering and clinical argument that the device achieves its intended purpose in the intended population under the intended conditions of use, and that the benefits outweigh the risks. For many devices, that argument must be supported by clinical data—either from clinical investigations conducted with the device itself, or from equivalent devices whose clinical data can be legitimately referenced.

Equivalence is where engineering decisions become acutely important. EU MDR's equivalence criteria—technical, biological, and clinical—require that the device be equivalent to the predicate in all three dimensions. The technical equivalence assessment is a detailed engineering comparison: same design principles, same materials in contact with human body, same anatomical location, same clinical procedures. MANKAIND supports the equivalence analysis by maintaining the device's engineering specifications in a structured format that can be systematically compared against the equivalent device's known characteristics—and by tracking whether design changes during development invalidate a previously established equivalence claim.

For novel devices without an adequate equivalent, the clinical evaluation must be supported by clinical investigation data. The clinical investigation plan must define endpoints that directly address the GSPR—not generic effectiveness endpoints, but device-specific performance metrics tied to the intended purpose. MANKAIND connects the clinical investigation plan to the GSPR conformance framework, ensuring that the study is designed to generate the specific evidence the technical file requires.

Post-market surveillance: the engineering obligation that begins at clearance

EU MDR's post-market surveillance requirements are substantially more demanding than MDD. The PMS plan, the periodic safety update report (PSUR), and the post-market clinical follow-up (PMCF) plan are mandatory for all devices, and the PSUR must be updated annually for Class III devices and every two years for Class IIb. The PMCF plan must address any residual clinical uncertainty identified in the clinical evaluation—which means that every gap in the pre-market clinical evidence becomes an explicit post-market engineering obligation.

MANKAIND generates the PMS plan and PMCF plan from the clinical evaluation's identified gaps and the benefit-risk analysis's identified residual risks. When the clinical evaluation concludes that certain patient subpopulations were underrepresented in the pre-market data, that conclusion becomes a PMCF study specification—not a narrative note. The post-market surveillance infrastructure is designed from the clinical evidence gaps, not specified independently.

Unique Device Identification and the technical file lifecycle

UDI requirements under EU MDR create a connection between the physical device, its labeling, and its technical documentation that must be maintained throughout the product lifecycle. Design changes that affect the device identifier require technical file updates. New configurations require UDI assignments. Legacy devices transitioning from MDD certificates to EU MDR technical files require a systematic review of the existing documentation against the new requirements.

MANKAIND maintains the connection between the UDI structure, the device configurations in the technical file, and the design and manufacturing documentation that covers each configuration. When a new variant is added or a design change modifies a covered configuration, the platform identifies the technical file sections that require updating and generates the change assessment documentation that the notified body will expect.

EU MDR compliance is ultimately an engineering evidence problem. The regulation demands that the technical documentation contain sufficient evidence to demonstrate that the engineering was done right—not that the documentation was assembled correctly. MANKAIND ensures that the engineering and the evidence are built together, from the first design decision to the last post-market surveillance report.