Qualification
Does the product have an individual or public-health medical purpose under the MDR, and what is the device boundary?
European Union regulatory market
We help medical device software teams define their MDR route, build Annex II and III documentation, plan clinical evidence and prepare for conformity assessment.
Discuss your market plan →Pathways and services
Qualification, Rule 11 classification, conformity-assessment planning and technical documentation.
View service →EvidenceClinical evaluation strategy, literature methods, evidence-gap analysis and PMCF planning.
View service →Use safetyUse specification, use-related risk analysis and IEC 62366-1 lifecycle evidence.
View service →LifecyclePMS plans and reports, PMCF interfaces, vigilance support and PSUR structures where applicable.
View service →What we need to determine
Does the product have an individual or public-health medical purpose under the MDR, and what is the device boundary?
How do Rule 11 and other applicable rules map to the information supplied by the software and the clinical consequence of decisions?
Can the manufacturer self-declare, or is a notified body needed for the class and route?
How will clinical, performance, usability and software evidence demonstrate each applicable safety and performance requirement?
How we work
Document medical purpose, software boundary, class, rationale and economic-operator model.
Map GSPRs, standards, evidence, QMS work and notified-body dependencies.
Develop controlled Annex II and III technical documentation with the required cross-references.
Support conformity assessment and establish registrations, PMS, vigilance and change control.
Core regulations, standards and guidance
FAQ
MDR classification, notified-body scope, transitional provisions and EUDAMED duties can change with product facts and implementation dates. Confirm the current legal and authority position for each market action.
No. Qualification depends on intended purpose and whether the software performs an action on data for the benefit of individual patients beyond storage, communication or simple search. Wellness and administrative products may fall outside the MDR, but the reasoning should be documented.
No. Rule 11 can lead to class IIa, IIb or III depending on the significance and consequences of the information supplied for diagnostic or therapeutic decisions; other software may be class I. The exact intended purpose and foreseeable clinical scenario control the analysis.
No. Correct use of a harmonized standard can provide a presumption of conformity for covered requirements, but the manufacturer remains responsible for all applicable GSPRs and for justifying alternatives or gaps.
No. Four modules became mandatory on 28 May 2026, while the vigilance/PMS and clinical-investigation modules follow separate functionality notices and transition dates. Current Commission notices and national arrangements should be checked at the time of action.
No. Predetics can support strategy and documentation. Where notified-body involvement is required, only a designated notified body can perform that conformity assessment and issue the relevant certificate; the manufacturer affixes the CE mark after completing applicable requirements.