This artifact helps select the conformity assessment route for a medical device under Regulation (EU) 2017/745 before placing it on the EU market or putting it into service.
The route decision should connect device classification, Article 52, designation scope, QMS readiness, technical documentation, clinical evidence, certificates, and retained evidence.
route selection under the EU Medical Device Regulation starts with the device's intended purpose and risk class, then maps that class to the conformity assessment procedures in Article 52. Record the result in a route memo showing whether notified body involvement is required, which Annex route applies, whether the chosen notified body is designated for the device type, and what evidence must be ready for application review, audit, technical documentation assessment, and certification.
1
Section 1
Start with MDR classification and the Article 52 route
Classify the device under Article 51 and Annex VIII before choosing a path. The MDR divides devices into classes I, IIa, IIb, and III by intended purpose and inherent risks; that classification drives the Article 52 conformity assessment procedure.
For class III devices, Article 52 points to Annex IX, or Annex X coupled with Annex XI. For class IIb devices, Article 52 points to Annex IX with technical documentation assessment for representative devices per generic device group; class IIb implantable devices generally require assessment of every device, except the exempted sutures, staples, dental fillings, dental braces, tooth crowns, screws, wedges, plates, wires, pins, clips, and connectors. For class IIa devices, Article 52 points to Annex IX with representative technical documentation assessment per category, or Annexes II and III coupled with an Annex XI route. For class I devices, the manufacturer normally declares conformity after drawing up Annexes II and III technical documentation, but involvement is triggered for sterile devices, measuring devices, and reusable surgical instruments, limited to the relevant sterile, metrological, or reuse aspects.
Do not treat a legacy certificate, distributor request, or preferred relationship as the route decision. The route decision should show the class, the Article 52 paragraph, the chosen Annex path, any special procedure, and the reason a notified body is or is not involved.
Record the intended purpose, claims, accessories, software role, invasiveness, duration of use, active status, implantable status, sterilization, measuring function, and reusable surgical instrument status.
Map the selected class to Article 52 paragraphs 3, 4, 6, 7, or 8, then identify the Annex IX, X, XI, or XIII route used.
Flag additional procedures under Article 52 where the device contains medicinal substances, human or animal tissues or cells, absorbed substances, or other special characteristics covered by Article 52 paragraphs 9 to 11.
Escalate classification disputes with the through the competent-authority path described in Article 51 rather than silently accepting an unsupported class.
Current consolidated MDR text used to verify conformity assessment route language and manufacturer evidence duties.
Prior to placing a device on the market
2
Section 2
Decide when notified body involvement is required
A is required when the applicable conformity assessment procedure calls for third-party intervention. Article 52 makes that involvement compulsory for class IIa, IIb, and III devices, and limited but still required for class I devices placed on the market sterile, with a measuring function, or as reusable surgical instruments.
When involvement is required, Article 53 allows the manufacturer to apply to a notified body of its choice only if that notified body is designated for conformity assessment activities related to the device type. The route memo should therefore pair the Article 52 route with evidence that the selected notified body can assess the product, not only that the body has a valid notified body number.
Avoid relying on voluntary or unregulated certificates as route evidence. NANDO warns that certificates issued outside a 's notified area do not prove compliance with EU harmonisation legislation.
For class I devices, document why no is needed or identify the limited sterile, measuring, or reusable surgical instrument scope that must be assessed.
For class IIa, IIb, and III devices, record the selected conformity assessment route, the application status, and the expected certificate type.
For class III implantable devices and class IIb active devices that administer or remove medicinal products, check whether the Article 54 clinical evaluation consultation procedure applies or an Article 54 exception is documented.
Reject certificate evidence that is outside the 's legislation, device type, or conformity assessment task.
Supports checking notified body identification, tasks, regular updates, and the warning that voluntary certificates are not recognised compliance evidence.
only notified bodies may issue certificates of compliance
3
Section 3
Check designation scope before application
The selection step should verify both legislation and scope. The Commission's notified body page explains that designated notified bodies are published in NANDO and can be filtered by legislation for Regulation (EU) 2017/745. The NANDO legislation search is the public route for finding bodies notified to carry out conformity assessments for a selected legislation.
Check the designation codes as well as the 's name. MDCG 2019-14 explains that designating authorities use MDR codes to define a notified body's designation scope and that notified bodies use them to describe staff qualifications and allocate conformity assessment teams. Manufacturer-side route evidence should therefore include the device's MDA or MDN code, applicable MDS and MDT codes, and the rationale for any difficult code choices.
MDA and MDN codes describe the device design and intended purpose; MDS codes identify specific characteristics such as sterility or medicinal substances; MDT codes describe production technologies and processes. MDCG 2019-14 recommends one MDA or MDN code per device, normally the highest applicable entry in the list, all applicable MDS codes, and the MDT codes describing the main production processes. Record the device fact behind each code and any exceptional selection rationale. The verifies the proposed codes at application review and makes the final assignment.
If the cannot confirm that the device and technologies fit its designation and resources, treat that as a route blocker before submitting a full application package.
Save the NANDO evidence showing the body is listed for Regulation (EU) 2017/745, not only for older medical device directives or a different product law.
Match the product's design and intended purpose to the relevant MDA or MDN code and assign all applicable horizontal MDS and MDT codes.
Ask the to confirm application feasibility, technical documentation review competence, audit competence, and any special-process competence before relying on the route.
Keep the number, legal entity name, legislation filter, scope codes, application review outcome, and contract or refusal record together.
Supports use of MDA, MDN, MDS, and MDT codes for notified body designation scope, application review, and allocation of competent assessment staff.
define the notified body scope of designation
4
Section 4
Prepare the QMS, technical documentation, and clinical evidence package
Route selection is only useful if the application package can survive review. Article 10 requires manufacturers to keep technical documentation up to date, draw up the EU declaration of conformity after the applicable conformity assessment, keep relevant certificates available where applicable, and establish a quality management system proportionate to the device risk class and type.
For routes, prepare the QMS evidence, Annexes II and III technical documentation, risk management file, clinical evaluation report, PMCF or PMS plans where applicable, standards or common specifications rationale, labeling and instructions for use, supplier and critical subcontractor records, and change-control history before application review.
Clinical evidence readiness matters because MDR defines clinical evidence as clinical data and clinical evaluation results of sufficient amount and quality to allow a qualified assessment of safety and clinical benefit. Annex XIV requires clinical evaluation results and supporting clinical evidence to be documented in a clinical evaluation report and included in technical documentation.
For Annex IX routes, prepare QMS procedures, audit evidence, technical documentation samples, clinical evaluation, PMS links, and change-control records.
For Annex X plus Annex XI routes, prepare the type-examination file, production quality assurance or product verification evidence, and the certificate cross-reference.
For limited class I involvement, separate the notified-body-reviewed sterile, measuring, or reusable surgical instrument aspects from the manufacturer self-declaration file.
Do not submit a route application until open clinical evidence gaps, intended-purpose inconsistencies, unresolved classification assumptions, and missing technical documentation sections are visible as managed risks.
Keep a compact route-selection record that a reviewer can follow without reconstructing the product history. The record should prove the class, route, scope check, application state, readiness package, certificate state, and unresolved blockers.
For issued certificates, retain the certificate type and the Annex XII content applicable to that type. Technical documentation assessment, type-examination, and product verification certificates identify the device, intended purpose, risk class, and Basic UDI-DI. QMS and quality assurance certificates identify devices or device groups and class, with intended purpose required for class IIb. Keep conditions of validity, supplements, amendments, surveillance reports, and links to the EU declaration of conformity and technical documentation. For refused, withdrawn, or transferred applications, retain the correspondence and the Article 53 declaration history.
Reopen the route decision after intended-purpose changes, design changes, sterilization or measuring changes, software changes, supplier or critical subcontractor changes, standards or common specifications changes, clinical evidence changes, certificate restrictions, scope changes, or authority feedback.
Classification memo: intended purpose, Annex VIII rules applied, class conclusion, classification dispute handling, and approval.
Article 52 route table: class, paragraph, Annex path, involvement, special procedures, and rationale.
scope pack: NANDO listing, legislation filter, scope codes, fee or application references, feasibility outcome, contract, withdrawal, refusal, or transfer evidence.
Readiness pack: QMS index, Annexes II and III technical documentation index, clinical evaluation report, PMS and PMCF links, risk management links, standards or common specifications rationale, and labeling.
Certificate pack: certificate number, type, validity conditions, scope, amendments, supplements, surveillance records, EU declaration of conformity, and competent-authority correspondence.
NANDO source for checking notified body identity, notified tasks, list update status, and warnings about unregulated or voluntary certificates.
Supports checking notified body identification, tasks, regular updates, and the warning that voluntary certificates are not recognised compliance evidence.
Supports retaining NANDO scope evidence because public lists identify notified bodies and the tasks for which they have been notified.
"Lists of Notified Bodies can be searched"
More quoted passages
"only notified bodies may issue certificates of compliance"