EU MDR 2017/745 · implementation · evidence · market access
MDR implementation challenges and practical solutions
Most MDR projects do not fail because one document is missing. They fail because the documents describe different devices.
The intended purpose shapes classification. Classification shapes the conformity route. Claims shape clinical evidence. Market data changes risk conclusions. This guide shows how to keep that chain intact and how to recover it when the project has fragmented.
Find the weak link ↓routePurpose · class · evidence
- 01DefineDevice and route
- 02ProveRisk and evidence
- 03ControlQMS and supply
- 04LearnPMS and change
Every claim, identifier and conclusion points to the same approved device
The implementation diagnosis
Treat MDR compliance as a controlled dependency chain
A late clinical report may be a symptom of an unstable intended purpose. A UDI problem may be a symptom of weak configuration control. Fixing the visible document without fixing the upstream decision only moves the finding.
One approved baseline
- Legal manufacturer and device family are defined
- Purpose, claims, class and conformity route agree
- Risk, clinical and technical evidence are traceable
- QMS processes produce device-specific records
- Market data returns to the evidence baseline
Documents move independently
- Marketing changes claims outside change control
- Risk and clinical teams use different configurations
- Suppliers change critical inputs without assessment
- Registration data conflicts with labels and certificates
- PMS reports do not update benefit-risk conclusions
Close gaps in dependency order. Confirm the device and route before repairing evidence, repair evidence before finalising the submission, and keep the approved baseline under change control after market access.
Find the weak link
Diagnose the project by the evidence it cannot produce
Choose the area where progress has stopped. The visible symptom, underlying failure and evidence needed to regain control are rarely the same thing.
The team cannot agree what must be submitted
Classification, product scope, conformity route or transition status changes as different documents are reviewed.
- ROOT FAILURE
No approved regulatory baseline
- CONTROL
Purpose and classification rationale
- EVIDENCE
Device-family and route decision record
The file is large but the claims remain unsupported
Literature, testing and risk records exist, yet they do not answer the clinical and safety questions created by the intended purpose.
- ROOT FAILURE
No claim-to-evidence architecture
- CONTROL
Evidence questions and acceptance criteria
- EVIDENCE
Traceable appraisal and gap decisions
Procedures exist but records do not tell one story
Design, suppliers, production, release, complaints and change control operate as separate quality-system islands.
- ROOT FAILURE
Generic QMS without product interfaces
- CONTROL
Process ownership and configuration control
- EVIDENCE
End-to-end decision trails
Registration and post-market data diverge from the device
UDI, EUDAMED, labels, economic-operator records and PMS outputs are updated by different owners on different schedules.
- ROOT FAILURE
No regulatory master-data governance
- CONTROL
Data ownership and change triggers
- EVIDENCE
Aligned identifiers and lifecycle updates
Ten recurring implementation challenges
Replace generic advice with a verifiable control
Each challenge needs an accountable owner, a controlled decision and evidence that can survive technical-documentation review, QMS audit and post-market change.
- 01REGULATORY ROUTE
Unstable intended purpose and classification
Approve the device definition, claims, qualification, classification rationale, applicable rules and conformity route as one controlled baseline.
- 02CLINICAL EVIDENCE
Claims outrun the available data
Turn every performance, benefit and safety claim into an answerable evidence question with predefined acceptance criteria.
- 03TECHNICAL DOCUMENTATION
The file contains contradictions
Use a traceability model that connects purpose, design inputs, risks, GSPRs, verification, validation, clinical evidence and labelling.
- 04QUALITY MANAGEMENT
The QMS is certified but not MDR-specific
Integrate Article 10(9), PRRC responsibilities, UDI, PMS, vigilance, regulatory communication and device evidence into operating processes.
- 05NOTIFIED BODY
Application starts before readiness
Select an MDR-designated body with the right scope and codes, then submit a stable device portfolio and complete application package.
- 06UDI AND EUDAMED
Regulatory data has no single owner
Govern Basic UDI-DI, UDI-DI, EMDN, actor, device and certificate data through the same approval and change system as labels and files.
- 07SUPPLY CHAIN
Critical suppliers change outside visibility
Define specifications, validation, quality agreements, notification duties, monitoring and escalation in proportion to supplier risk.
- 08TRANSITION
Legacy status is treated as a pause
Control transition conditions, significant changes, surveillance, PMS and certification milestones as active compliance obligations.
- 09POST-MARKET SYSTEM
Market data is reported but not used
Return complaints, vigilance, trends, literature and PMCF to risk management, clinical evaluation, benefit-risk and CAPA.
- 10PROJECT GOVERNANCE
Resources follow document count instead of risk
Plan work by regulatory dependency, evidence uncertainty, patient impact and market deadline, with one accountable decision owner.
Ask five teams to describe the same device
Regulatory, clinical, risk, quality and marketing should give compatible answers about the intended purpose, users, population, indications, claims, configuration and limitations. Differences reveal implementation risk before an assessor finds it.
The evidence chain
Make every downstream file inherit the same regulatory truth
A strong technical file is not a collection of finished documents. It is a controlled chain in which each conclusion has an upstream basis and a downstream consequence.
A change is not local when it changes the device story
A new claim, supplier, material, algorithm, sterilisation parameter, shelf life, user population or market can affect several links at once. The impact assessment should identify every technical, clinical, regulatory, QMS, labelling, registration and post-market output that must be reviewed.
The first ninety days of recovery
Restore control before producing more documents
This sequence is designed to recover a delayed or fragmented programme. It creates a submission-ready direction, not a promise that certification can be completed within ninety days.
- 01WEEKS 1–2
Freeze the moving target
List devices, variants, markets, certificates, deadlines, current claims and open changes. Stop uncontrolled parallel drafting.
- 02WEEKS 2–3
Confirm the legal route
Approve purpose, qualification, classification, transition status, conformity route, Notified Body need and responsible legal entities.
- 03WEEKS 3–5
Create the evidence baseline
Map risks, GSPRs, claims, testing, clinical evidence, labels, identifiers and PMS to the controlled device configuration.
- 04WEEKS 5–7
Rank gaps by consequence
Separate market-stopping, safety-critical and assessment-critical gaps from editorial work and optional improvements.
- 05WEEKS 6–10
Close connected work packages
Assign one owner per decision trail and close upstream rationale, evidence, downstream documents and QMS records together.
- 06WEEKS 9–11
Run challenge reviews
Test classification, clinical sufficiency, risk controls, supplier evidence, PMS and data consistency with independent reviewers.
- 07WEEKS 11–13
Lock the submission baseline
Resolve contradictions, approve the configuration, verify the application package and place remaining actions under formal control.
Notified Body interaction
Prepare for assessment without expecting consultation
The Notified Body must remain independent. It can explain its application process and raise findings, but it cannot design the manufacturer’s regulatory, clinical or quality solution.
Verify designation and technical scope
Use NANDO and the Notified Body’s documented scope to confirm relevant MDR codes, device competence and conformity-assessment capability. Compare capacity, process, fees and languages.
Submit a stable and complete portfolio
Define legal entities, sites, device families, classes, codes, routes and certificates consistently. Incomplete or shifting scope creates avoidable questions and delay.
Close causes, not only comments
For each finding, identify the requirement, affected devices, root cause, correction, systemic action, updated evidence and effectiveness check.
New EU rules improve predictability
Commission Implementing Regulation (EU) 2026/977 introduces uniform requirements for certain Notified Body QMS and procedural practices, including elements affecting applications, communication, timelines and fees.
Predictability does not replace readiness
The manufacturer still owns classification, evidence, the QMS, application completeness, responses, changes and continued conformity.
Assessment is not outsourced compliance
A contract or scheduled audit is not evidence of conformity. Readiness exists only when the submitted device story is complete, consistent and operating in practice.
The submission test
Can an assessor move from one claim to the market-control loop?
Select a headline performance claim. Trace it through intended purpose, classification, risks, GSPRs, design requirements, verification, clinical evaluation, labelling, PMS indicators and change control. A broken link predicts questions better than document count.
- 01Claim
- 02Risk
- 03Proof
- 04Label
- 05PMS
UDI, EUDAMED and supply-chain control
Manage regulatory data as part of the device configuration
Registration is not a final clerical step. The data published or exchanged across the market must remain aligned with the approved device, economic operators and certificate status.
Control the identifier hierarchy
Define device families, Basic UDI-DI, UDI-DI assignment, packaging levels and triggers for a new identifier.
Approve one regulatory record
Align actor, device, EMDN, certificate, label, declaration and technical-documentation data before submission.
Make verification possible
Provide authorised representatives, importers and distributors with current information, responsibilities and escalation routes.
Update every affected destination
Use defined triggers, owners, approvals and reconciliation checks for internal systems, labels, partners and EUDAMED.
Expensive implementation mistakes
Work that looks fast but creates another cycle
The most costly shortcuts create polished outputs before the regulatory and evidence assumptions underneath them have been approved.
Starting with document templates
Templates organise information but cannot decide the device scope, route, evidence questions or acceptance criteria.
Copying a competitor’s classification
Small differences in purpose, mechanism, duration, anatomy or software function can change the applicable rule.
Calling literature a clinical evaluation
Search results are not enough without systematic appraisal, applicability, claim coverage and a conclusion on sufficiency.
Treating the Notified Body as the project designer
Independence limits consultation. The manufacturer must arrive with justified decisions and controlled evidence.
Buying software before defining data governance
A system can store UDI or QMS data, but it cannot fix unclear ownership, inconsistent source records or missing change triggers.
Closing findings only in the cited document
A local edit leaves the same cause active in related devices, procedures, records, labels, registrations and market controls.
Practical questions
MDR implementation FAQ
Open the question that affects your regulatory route, evidence plan, assessment or recovery programme.
What is usually the hardest part of MDR implementation?+
The hardest part is keeping the regulatory strategy, product claims, risk management, clinical evidence, technical documentation, QMS and post-market processes consistent. A document can look complete in isolation and still fail because it describes a different intended purpose, device configuration or risk conclusion from the rest of the file.
Where should an MDR implementation project start?+
Start by fixing the legal manufacturer, device family, intended purpose, qualification, classification, conformity-assessment route and transition status. These decisions determine the evidence, QMS controls, Notified Body involvement, registration and timelines that follow. Drafting documents before fixing the route usually creates expensive rework.
Can an ISO 13485 certificate solve MDR implementation gaps?+
No. ISO 13485 provides a strong quality-management framework, but the manufacturer must deliberately integrate MDR requirements such as regulatory strategy, GSPRs, clinical evaluation, PMCF, UDI, registration, PMS, vigilance and regulatory communication. Product-specific conformity is not established by the ISO certificate alone.
How much clinical evidence is enough under the MDR?+
There is no universal number of studies or publications. The evidence must be sufficient for the device characteristics, intended purpose, claims, risks, state of the art and remaining uncertainty. The manufacturer should define the questions in the clinical evaluation plan, appraise relevant data, identify gaps and use PMCF or a clinical investigation when existing evidence cannot close them.
Should a manufacturer contact several Notified Bodies at once?+
A manufacturer may compare suitable Notified Bodies before contracting, but selection should focus on MDR designation scope, relevant codes, competence, capacity, application requirements, fees and realistic timing. Once a conformity-assessment relationship exists, responsibilities and any transfer must be carefully controlled. A Notified Body assesses conformity and cannot design the manufacturer’s solution as a consultant.
Is EUDAMED only an IT task?+
No. EUDAMED exposes the quality of the manufacturer’s master data and regulatory decisions. Actor details, Basic UDI-DI structure, device identifiers, nomenclature, certificates and status information must agree with labels, declarations, technical documentation and internal records. Ownership, approval and change control are therefore more important than data entry alone.
Can legacy-device transition deadlines replace MDR implementation?+
No. Transitional provisions provide additional time only when all applicable conditions are met. They do not remove ongoing MDR obligations such as PMS, vigilance, economic-operator requirements and restrictions on significant changes, nor do they eliminate the need to complete MDR conformity assessment within the applicable transition route.
How can a delayed MDR project be recovered?+
Freeze uncontrolled drafting, confirm the regulatory route, establish one device and evidence baseline, rank gaps by market and patient risk, assign accountable owners, then close connected evidence trails in dependency order. A focused ninety-day recovery phase can restore control and submission readiness, but it cannot guarantee certification within ninety days.
Primary sources
Use the current legal text and implementation guidance
MDR implementation guidance and EUDAMED arrangements continue to evolve. Confirm the current official version when making a device-specific decision.
Regulation (EU) 2017/745
Current consolidated MDR legal text
Implementing Regulation (EU) 2026/977
Uniform requirements for Notified Body procedures
MDCG guidance index
Current European Commission implementation guidance
EUDAMED overview
Official modules, information and rollout resources
NANDO information system
MDR-designated Notified Bodies and scopes
MDCG 2020-6
Sufficient clinical evidence for legacy devices
Turn a fragmented programme into one controlled route
Need to diagnose or recover an MDR implementation project?
MDRC can confirm the regulatory route, map evidence and QMS dependencies, prioritise critical gaps, prepare the Notified Body application, review technical documentation and establish a practical recovery plan.
