Article 10(9) requires manufacturers to establish, document, implement, maintain, update, and continually improve a quality management system proportionate to the device type and risk class.
This page helps map MDR QMS procedures to regulatory strategy, design and production controls, risk management, clinical evaluation, PMS, vigilance, UDI and EUDAMED data, supplier controls, CAPA, management responsibility, and conformity-assessment records.
An MDR controls the manufacturer's work beyond the quality manual. Article 10 connects regulatory compliance, device design and manufacture, risk management, clinical evidence, post-market data, vigilance, UDI registration, supplier control, corrective action, management accountability, and the records a notified body or competent authority can inspect.
1
Section 1
Article 10 QMS scope
For devices other than investigational devices, Article 10(9) requires the manufacturer to run a documented that covers the parts of the organisation dealing with quality of processes, procedures, and devices. The system must be proportionate to the risk class and type of device, so a low-risk Class I device and a high-risk implantable device should not have identical review depth, evidence gates, or management escalation.
The Article 10 list is the minimum map for the . It includes regulatory compliance strategy, conformity-assessment and change-management procedures, general safety and performance requirements, management responsibility, resources, supplier and subcontractor controls, risk management, clinical evaluation and PMCF, product realisation, UDI verification and registration consistency, PMS, stakeholder communication, vigilance reporting, CAPA effectiveness, output monitoring, data analysis, and product improvement.
The MDR duty and a standards-based certification are related but different. Article 10(9) creates the manufacturer's legal duty. Under Article 8, voluntary use of a harmonised standard whose reference is published in the Official Journal can create a presumption of conformity for the requirements the standard covers. A certificate to a quality standard does not by itself prove compliance with every MDR duty, device, or current technical-documentation record.
Start the scope from the device family, risk class, intended purpose, manufacturer role, production model, and conformity-assessment route.
Maintain a regulatory strategy procedure that links classification, applicable general safety and performance requirements, harmonised standards or common specifications, notified-body interactions, and change assessment.
Make management responsibility visible through named process owners, approval gates, resource decisions, quality objectives, review minutes, and escalation criteria for risk, clinical, PMS, vigilance, and CAPA signals.
Keep supplier and subcontractor control inside the , including qualification, purchasing requirements, design or manufacturing handoffs, change notification, performance review, and corrective-action follow-up.
The should make design and manufacture traceable from intended purpose through requirements, hazards, risk controls, verification, validation, labelling, release, and service provision. Article 10 requires devices to be designed and manufactured in accordance with MDR requirements, while Annex I treats risk management as a continuous lifecycle process.
Clinical evaluation cannot sit outside the quality system. Article 10 points to Article 61 and Annex XIV, which require a documented clinical evaluation and PMCF. The should therefore define when clinical evaluation plans, clinical evaluation reports, PMCF plans, PMCF evaluation reports, risk files, claims, instructions for use, and technical documentation are updated together.
Link design inputs to intended purpose, user needs, GSPRs, risk controls, standards or common specifications, verification evidence, validation evidence, and production release criteria.
Require risk-management updates when production data, complaints, PMS findings, clinical data, usability findings, supplier changes, or field safety information changes the benefit-risk determination.
Keep clinical evaluation records objective and current, including favourable and unfavourable data, evidence gaps, equivalence rationale where used, PMCF outputs, and the connection to technical documentation.
Use change-control gates that decide whether a design, material, software, manufacturing, supplier, labelling, or claims change affects conformity assessment, clinical evaluation, UDI data, PMS, or vigilance obligations.
Article 83 makes post-market surveillance an integral part of the Article 10 . The QMS should specify how complaints, service data, trend signals, user feedback, literature, registry data, clinical follow-up, distributor information, and field data are gathered, analysed, escalated, and used to update risk management, clinical evaluation, labelling, technical documentation, and product improvement.
Vigilance needs a separate reporting workflow with intake triage, causal-assessment records, serious-incident decisions, field safety corrective action decisions, field safety notices, authority communication, notified-body communication where applicable, and CAPA linkage. UDI and EUDAMED controls should verify Basic UDI-DI and UDI-DI assignments, device-registration data consistency, and the data used in certificates, declarations of conformity, labels, technical files, and EUDAMED submissions.
Define PMS data sources, review frequency, trend thresholds, report ownership, and update rules for PMS reports or PSURs according to the device class and conformity route.
Route serious incident and field safety corrective action decisions through trained vigilance owners, with evidence for reportability, timing, follow-up, and authority submissions.
Treat UDI as master data controlled by the : assign, verify, approve, and reconcile identifiers across labels, declarations, certificates, technical documentation, and EUDAMED records.
Keep EUDAMED actor and device-registration responsibilities assigned, with access continuity, submission evidence, correction logs, and release checks before new or changed devices are placed on the EU market.
Records for conformity assessment and authority review
A record set should let a notified body or competent authority reconstruct the manufacturer's decisions without relying on staff memory. Article 10 requires current technical documentation, an EU declaration of conformity after the applicable conformity assessment, UDI and registration compliance, and long-term availability of the technical documentation, declaration, and relevant certificates.
For conformity assessment, keep the evidence tied to the device or device group under review: scope and classification rationale, regulatory strategy, design history, manufacturing controls, supplier files, risk-management file, clinical evaluation file, PMS plan and outputs, vigilance file, UDI records, EUDAMED records, CAPA logs, management-review records, internal audits, change-control records, notified-body submissions, and certificate conditions.
Retain technical documentation, declarations, and relevant certificates for at least 10 years after the last covered device is placed on the market, and at least 15 years for implantable devices.
Make CAPA files show the problem statement, risk assessment, containment, root cause, correction or corrective action, effectiveness check, owner, due date, and resulting updates to risk, clinical, PMS, labelling, suppliers, or production controls.
Do not rely on standalone ISO certificates, supplier declarations, or historic test reports unless the record shows how they apply to the current device version, intended purpose, risk class, production process, and MDR obligation.
Commission explanation of harmonised standards, Official Journal references, voluntary use, and their role in demonstrating conformity with covered EU legal requirements.
Commission EUDAMED source for the system modules covering actor registration, UDI/device registration, notified bodies and certificates, clinical investigations, vigilance/PMS, and market surveillance.