Direct answer: The EU Medical Device Regulation (MDR, Regulation (EU) 2017/745) is not covered by "ISO 13485/CE certificate" and you are done. It has applied since 26 May 2021 and determines the conformity-assessment route by device class (I, Is, Im, IIa, IIb, III); it requires GSPR/technical documentation, clinical evaluation/PMCF, PMS/vigilance, UDI/EUDAMED, CE/DoC, labelling/IFU, an EU authorised representative (AR) and a Person Responsible for Regulatory Compliance (PRRC). A manufacturer's MDR page should state product/class, CE/notified body, technical file/clinical, PMS/vigilance, UDI/EUDAMED, roles and transition—not just "CE/ISO 13485 certified".

This guide is for medical device, consumable, diagnostic equipment, rehabilitation/care, medical software (MDSW), medical component and contract manufacturers in Changzhou and nearby areas. It explains how to write and accept an MDR page. Information is current to 2026-11-05. It is a review of public rules and project practice, not EU legal, medical-device safety, clinical, testing or compliance advice; the specific classification, GSPR, clinical, CE, UDI/EUDAMED, vigilance and transition depend on the regulation, harmonised standards, notified bodies and the competent authority.

Three things to remember

MDR applies from 26 May 2021; class determines the route: Class I (non-sterile/non-measuring) can self-declare, while Is/Im/IIa/IIb/III generally need a notified body. Technical file/GSPR/clinical evaluation/PMCF/PMS/vigilance is one system, not one certificate. EUDAMED's four modules are mandatory from 28 May 2026; a non-EU manufacturer needs an EU AR/PRRC, and labels/IFU/UDI must match.

How does the MDR page relate to IVDR, GPSR, ISO 13485 and UDI/recall pages?

IVDR covers in-vitro diagnostic devices (2017/746); GPSR is the consumer-safety baseline; ISO 13485 is a quality-management-system standard, not CE/product approval; the UDI/recall/IFU page is a specific-topic example; the recall/traceability page answers incident handling. The MDR page answers "how this device is classified, which conformity route applies, and how the technical file/clinical/PMS/UDI/roles are handled". MDR is the device-specific law and prevails over GPSR for the aspects it covers; ISO 13485 proves a system but does not replace CE/technical file/clinical/UDI.

Common breakpoints: treating ISO 13485 as CE; treating all Class I as self-declared (Is/Im need a notified body); missing clinical/PMS in the technical file; expired CE certificates; no UDI/EUDAMED; no AR/PRRC; wrong label/IFU language; no vigilance/recall process. A page that states classification, route, documents, clinical, PMS, UDI and roles gives R&D, quality, regulatory and export sales one playbook.

Page/topicAnswersCoversCannot replace
MDR 2017/745Classification/CE/clinical/PMSMedical devicesIVDR/GPSR/ISO
IVDRIn-vitro diagnosticsIVDMDR devices
GPSRConsumer-safety baselineGeneral safetyMDR-specific rules
ISO 13485Quality management systemSystemCE/product approval
UDI/recallIdentification/traceability/incidentsSpecific topicsAll MDR
Notified bodyConformity assessmentIIa+ etc.System certification

This page map is editorial; MDR duties follow Regulation (EU) 2017/745 and the European Commission medical devices page.

Which products are in scope, and how are they classified?

MDR applies to medical devices and their accessories, including software (MDSW) and some products without a medical purpose listed in Annex XVI (e.g. certain cosmetic/tattoo/contact-lens products); in-vitro diagnostics follow IVDR. Classification by risk/invasiveness/duration/local/systemic effects is I, Is (sterile), Im (measuring), IIa, IIb, III; the rules are in Annex VIII. Class I non-sterile/non-measuring can generally self-declare; Is/Im/IIa/IIb/III generally need a notified body. A wrong classification makes the route/CE/file wrong.

Acceptance checks: product/intended purpose; device/MDSW/Annex XVI; classification rule/class; Is/Im; IVD exclusion; components/accessories; customer/authority confirmation. Common gaps: treating MDSW as ordinary software; treating all Class I as self-declared; ignoring Is/Im; wrong classification rule; treating a component as a standalone device; mixing IVD into MDR.

ClassDefinition/routeEvidenceCommon gap
Class ILow risk; non-sterile/non-measuring can self-declareClassification/DoCAll I self-declared
Is/ImSterile/measuring; usually notified bodyClassification/certificateIgnored
IIaMedium-low risk; notified bodyCertificateWrong route
IIbMedium-high risk; notified bodyCertificateWrong route
IIIHigh risk; notified body/expertCertificateWrong route
MDSWSoftware as a deviceClassification/fileOrdinary software
Annex XVINo medical purpose but coveredListIgnored

Classification follows MDR Article 51/Annex VIII and Commission guidance; confirm specific products with regulatory/notified bodies.

What is the timeline and transition?

MDR 2017/745 was published on 5 May 2017, entered into force on 25 May 2017 and applies from 26 May 2021, replacing MDD 93/42/EEC/AIMDD 90/385/EEC. Transition was extended by Regulation (EU) 2023/607: subject to conditions (QMS, notified-body application/contract, no serious safety issues, etc.), devices covered by MDD certificates may continue to be placed in stages—Class III/implantable IIb until 31 December 2027, other IIb/IIa/Is/Im until 31 December 2028 (subject to the regulation/notified body); Class I has separate arrangements. EUDAMED's four modules are mandatory from 28 May 2026.

Do not present "MDR applies in 2021" as "all old certificates expired in 2021", nor "transition extension" as "no need to move to MDR". State "application/transition conditions/class deadlines/EUDAMED/Member State enforcement", subject to the OJ/Commission/notified body.

DateEventWhoWhat the page should state
2017-05-25MDR entry into forceAllIn force ≠ applies
2021-05-26MDR appliesDevicesReplaces MDD/AIMDD
2023/607Transition extensionLegacy-certificate devicesConditions/classes
2026-05-28EUDAMED 4 modules mandatoryManufacturer/AR/importerActor/UDI/certificate/vigilance
2027-12-31Class III/implantable IIb deadlineRelevant devicesPer regulation
2028-12-31Other IIb/IIa/Is/ImRelevant devicesPer regulation

Timeline follows MDR, Regulation (EU) 2023/607, the EUDAMED page and notified bodies; transition conditions may affect specific dates.

How should GSPR and the technical file be accepted?

MDR Annex I General Safety and Performance Requirements (GSPR) are the core; the technical file should cover device description/specifications, GSPR checklist/conformity, risk management (ISO 14971), design/manufacturing, materials/biocompatibility, electrical/EMC/software/cybersecurity (where applicable), sterilisation/packaging/stability, labels/IFU and clinical evaluation/PMS. The file must match the specific model/version/plant; changes require assessment/update. One template cannot cover all products.

Acceptance checks: GSPR checklist; risk management; technical-file structure; materials/biocompatibility; electrical/software/cyber; sterilisation/packaging; labels/IFU; clinical/PMS; version/change. Common gaps: missing GSPR; boilerplate risk file; file/model mismatch; software/cyber omitted; sterilisation/packaging validation missing; change not updated.

ModuleWhat to confirmEvidenceCommon gap
GSPRAnnex I checklist/conformityMatrixMissing items
RiskISO 14971/measuresFileBoilerplate
Design/manufacturingSpec/drawings/processFileMismatch
Materials/biocompatibilityCompatibility/toxicologyReportMissing
Electrical/softwareEMC/cybersecurityTestingOmitted
Sterilisation/packagingValidation/stabilityReportMissing
Labels/IFULanguage/symbols/warningsSampleMismatch
Clinical/PMSEvaluation/planReportMissing

GSPR/technical file follow MDR Annexes I–III, harmonised standards and notified-body requirements; this is not technical-file advice.

How should clinical evaluation, PMCF and PMS be accepted?

Clinical evaluation needs a plan, data/literature, analysis, conclusions and a report; PMCF (post-market clinical follow-up) is planned/executed by risk/device type; PMS (post-market surveillance) needs a system, data collection/analysis, PSUR/periodic reporting (by class) and trend/risk reassessment. Insufficient clinical evidence/PMCF can affect CE; PMS is not "after-sales statistics" but must feed back into risk/design/labels. MDSW/high-risk devices are stricter.

Acceptance checks: clinical evaluation plan/report; data/literature; PMCF plan/results; PMS system; PSUR/report; trend/risk; update. Common gaps: boilerplate clinical report; irrelevant literature; no PMCF; PMS collects complaints only; missing PSUR; no trend analysis; no update.

StepWhat to confirmEvidenceCommon gap
Clinical planObjective/method/dataPlanNone
Clinical reportAnalysis/conclusionReportBoilerplate
PMCFPlan/resultsReportNot done
PMSSystem/dataRecordsComplaints only
PSURClass/periodReportMissing
TrendAnalysis/reassessmentRecordNo analysis
UpdateRisk/design/labelsChangeNot updated

Clinical/PMCF/PMS follow MDR Articles 61, 83–86, Annexes XIV/III and MDCG guidance; specific plans follow clinical/regulatory confirmation.

How should CE, conformity assessment and notified bodies be accepted?

Class I non-sterile/non-measuring can self-declare (still requiring technical file/DoC/CE); Is/Im/IIa/IIb/III generally need a notified body (some IIa routes allow sampling); III/implantable devices have additional expert/clinical requirements. CE marking plus an EU Declaration of Conformity (DoC); notified-body certificates have scope/validity/conditions; changes/new versions require assessment. CE is not a permanent certificate; a notified body/authority may suspend/withdraw it.

Acceptance checks: class/route; notified-body certificate/scope/validity; DoC; CE marking; technical file; changes; suspension/withdrawal record. Common gaps: wrong Class I route; expired/wrong-scope certificate; missing DoC; CE placement; change not assessed; unaware of suspension.

ElementWhat to confirmEvidenceCommon gap
Class/routeI/Is/Im/IIa/IIb/IIIClassificationWrong route
Notified bodyCertificate/scope/validityCertificateExpired
DoCLaw/class/signatureDoCMissing
CEMarking/placement/sizeSampleWrong placement
Technical fileGSPR/clinical/PMSFile packMissing items
ChangesDesign/process/softwareAssessmentNot assessed
StatusSuspension/withdrawal/conditionsNotified bodyUnaware

CE/conformity assessment follows MDR Article 52/Annexes IX–XI, notified-body certificates and Commission guidance.

How should UDI and EUDAMED be accepted?

MDR requires UDI (Unique Device Identification) for traceability; EUDAMED is the EU medical-device database with Actor, UDI/Device, Notified Bodies/Certificates and Vigilance modules. From 28 May 2026, the first four modules are mandatory (subject to the Commission notice): manufacturers/ARs/importers must register the Actor, register UDI/devices, certificate information and vigilance reports. UDI must be marked on the label/packaging (by class/level) and match EUDAMED/traceability. EUDAMED is not optional; it is part of MDR compliance.

Acceptance checks: UDI assignment/standard; label/packaging; EUDAMED Actor/UDI/certificate/vigilance; data consistency; AR/importer registration; updates; customer/authority lookup. Common gaps: no UDI; missing label; not registered; inconsistent data; AR not registered; certificate not registered; vigilance not reported.

ElementWhat to confirmEvidenceCommon gap
UDIStandard/assignment/levelRecordNone
Label/packagingUDI carrier/placementSampleMissing
EUDAMED ActorManufacturer/AR/importerSRNNot registered
UDI/DeviceDevice/UDI dataRegistrationNot registered
CertificateNotified body/certificateRegistrationNot registered
VigilanceIncident/reportRecordNot reported
ConsistencyLabel/database/fileCross-checkMismatch

UDI/EUDAMED follow MDR Articles 27–34, Regulation (EU) 2024/1860, the EUDAMED page and Commission notices; mandatory modules/timing may change.

How should PMS vigilance, incidents and recalls be accepted?

The manufacturer needs a vigilance system: serious incidents/death/serious deterioration must be reported to the authority under MDR (timelines by risk/Member State); field safety corrective action (FSCA)/recall must be notified/executed/recorded; trend reporting/PSUR by class; importers/distributors must inform the manufacturer/authority of incidents. Recall/corrective action must match UDI/traceability/EUDAMED; customer/patient communication must be clear. PMS/vigilance is not "after-sales records"; it is a legal duty.

Acceptance checks: vigilance procedure/owner; reporting timelines/channels; FSCA/recall; trend/PSUR; importer/distributor notification; records; EUDAMED; customer communication. Common gaps: unaware of reporting; late; customer-only report; no FSCA record; no trend analysis; EUDAMED not reported; recall without traceability.

StepWhat to doEvidenceCommon gap
Vigilance procedureOwner/timeline/channelProcessNone
Serious incidentReport to authorityReceiptNot reported
FSCA/recallNotify/execute/recordRecordNone
Trend/PSURAnalysis/reportReportMissing
Importer/distributorNotify/cooperateRecordNo notification
EUDAMEDVigilance registrationRecordNot reported
TraceabilityUDI/batch/customerSystemBroken

Vigilance/recall follows MDR Articles 87–92, MDCG guidance and competent-authority requirements; timelines/formats follow Member State implementation.

What do manufacturers, ARs, PRRCs, importers and distributors do?

Manufacturer: classification/GSPR/technical file/clinical/PMS/CE/DoC/UDI/EUDAMED/vigilance/recall. A non-EU manufacturer must appoint an EU authorised representative (AR); the PRRC (Person Responsible for Regulatory Compliance) must have qualifications/duties ensuring compliance/files/vigilance; AR/PRRC may overlap but need authority/resources. Importer: verify CE/DoC/UDI/EUDAMED/labels, indicate name/address, keep documents, cooperate on vigilance/recall. Distributor: check/storage/transport/cooperate. Define roles/contracts; customers/authorities will check.

Acceptance checks: AR mandate; PRRC qualification/duties; importer marking; distributor checks; vigilance/recall cooperation; EUDAMED; contract. Common gaps: no AR; nominal PRRC; importer not marked; distributor not checking; unclear roles; no cooperation clause.

RoleMain dutyEvidenceCommon gap
ManufacturerClassification/file/CE/UDI/vigilanceFile packAssumes export exempts it
AREU contact/files/cooperationMandateNone
PRRCCompliance/files/vigilanceQualification/appointmentNominal
ImporterVerify/identify/files/cooperateLabel/recordNo marking
DistributorCheck/storage/cooperateChecklistNo checks
VigilanceReport/recall/recordsProcessNone

Role duties follow MDR Articles 10–16 and Commission guidance; confirm mandates/contracts by actual role.

How should labels, IFU and language be accepted?

Labels/IFU must include: manufacturer/AR name/address, device name/model, UDI, CE, classification/warnings/contraindications, instructions, language (sales country), symbols/sterile/single-use/expiry/storage, etc.; MDSW also needs software version/cybersecurity/licence; electronic IFU is possible but must meet regulatory/accessibility requirements. Labels/IFU must match the technical file/clinical/UDI/EUDAMED; wrong language is a common cause of penalties/delisting.

Acceptance checks: manufacturer/AR; model/UDI; CE; warnings/contraindications; language; symbols; sterile/expiry; software; consistency. Common gaps: no AR; missing UDI; wrong language; incomplete warnings; wrong symbols; electronic IFU inaccessible; database mismatch.

ElementWhat to stateEvidenceCommon gap
Manufacturer/ARName/addressLabelNo AR
Model/UDIIdentification/traceabilityLabelNo UDI
CEMarking/placementSampleWrong placement
Warnings/contraindicationsRisk/useIFUIncomplete
LanguageSales countryMulti-languageEnglish only
Sterile/expiryStatus/dateLabelMissing
SoftwareVersion/cybersecurityIFUIgnored
ConsistencyLabel/file/databaseCross-checkMismatch

Labels/IFU follow MDR Articles 10 and 23–27, Annex I and sales-country language requirements.

How should the website MDR page be written?

A public page should include: products/classification, CE/notified body, GSPR/technical file, clinical/PMCF/PMS, UDI/EUDAMED, vigilance/recall, AR/PRRC/importer/distributor roles, labels/IFU/language, transition/customer data and version/contact. Write verifiably: state "we have classification/file/CE/UDI/process", not "all devices are CE/ISO 13485 compliant/absolutely safe".

Separate "public information" from "customer/regulatory documents": technical files, clinical/testing, CE certificates and UDI/EUDAMED data are provided per permission/contract; the public page gives scope, classification, process and contacts, and does not publish patient/customer/clinical sensitive data. If supplying components or carrying out contract manufacturing, state that the company supports the device manufacturer/brand owner with files/UDI and does not declare the whole device CE. Multilingual pages should match sales countries.

SectionWhat to writeEvidenceAvoid
Scope/classDevice/I/IIa/IIb/IIIClassification"All devices"
CE/notifiedRoute/certificate/DoCCertificate"ISO = CE"
Technical/clinicalGSPR/clinical/PMSFile"Certificate is enough"
UDI/EUDAMEDIdentifier/registration/vigilanceRecord"Can wait"
RolesAR/PRRC/importer/distributorMandateSelf only
Labels/IFULanguage/warnings/UDISampleWrong language
Transition2023/607/classesRegulation"All expired in 2021"
Contact/versionData request/dateFormNo entry

This page structure is editorial; external claims must be truthful and verifiable, per MDR, notified bodies and the competent authority.

What must not be written?

High-risk claims: "ISO 13485 = CE/compliance" (system ≠ product approval); "all Class I self-declare" (Is/Im need a notified body); "a CE certificate is permanent" (scope/validity/conditions); "all old certificates expired in 2021" (2023/607 transition); "EUDAMED can wait" (four modules mandatory 2026-05-28); "technical file = one certificate" (GSPR/clinical/PMS/UDI); "one clinical evaluation is enough" (PMCF/PMS); "the importer is responsible, so we are fine" (manufacturer/AR/PRRC duties remain); "absolutely safe/zero risk" (cannot guarantee). These are inaccurate or misstate responsibility.

Safer wording: "product/class, CE/notified body, technical/clinical/PMS, UDI/EUDAMED, roles, labels/IFU, transition, subject to MDR/notified bodies/authorities". External promotion must also comply with advertising/fair-competition law; patient/clinical/customer information needs authorisation/redaction.

Page wordingProblemSuggested wordingBasis
"ISO = CE"System ≠ approvalState separatelyMDR
"All I self-declare"Is/Im need NBClass/routeMDR
"CE forever"Scope/validityCertificate/maintenanceMDR
"All expired 2021"2023/607 transitionTransition/classesMDR
"EUDAMED can wait"Mandatory 2026-05-28Registration/UDIMDR
"Certificate = file"GSPR/clinical/PMSTechnical fileMDR
"One clinical"PMCF/PMSOngoingMDR

These red lines are editorial; whether a claim is false advertising/non-compliant is determined by regulators and the contract, and this is not legal advice.

Go-live acceptance checklist

Ten checks: product/classification, CE/notified body, GSPR/technical file, clinical/PMCF/PMS, UDI/EUDAMED, vigilance/recall, AR/PRRC/importer/distributor, labels/IFU/language, transition, page wording/version. Each needs an owner, evidence and review date. The pass condition is not "the page says CE", but that a customer/authority can see the classification, route, file/clinical/UDI status and who is responsible.

Before go-live, run one real device/model through: classification → CE/notified → technical/clinical → UDI/EUDAMED → vigilance → roles → labels → transition → page wording. Any step that fails is a gap in the page or the process.

CheckPass conditionEvidenceIf it fails
Product/classI/Is/Im/IIa/IIb/IIIClassificationClassify
CE/notifiedRoute/certificate/DoCCertificateFix route
Technical fileGSPR/risk/testingFile packComplete
Clinical/PMSEvaluation/PMCF/PSURReportAdd
UDI/EUDAMEDUDI/registration/dataRecordRegister
Vigilance/recallReport/FSCA/traceabilityProcessBuild
RolesAR/PRRC/importer/distributorMandateAppoint
Labels/IFULanguage/warnings/UDISampleFix label
Transition2023/607/classesStatementAdd
WordingNo "ISO = CE/absolute"Page testRemove

This checklist is editorial; specific compliance requirements follow MDR, notified bodies and the competent authority.

Who should read this, who should not, and what decisions does it support?

It suits medical device, consumable, diagnostic equipment, rehabilitation/care, MDSW, medical component and contract manufacturers in Changzhou and nearby areas; also R&D, quality, regulatory, export sales and website teams assessing an MDR page. It does not suit businesses that do not sell to the EU, products that are not devices/IVD, or those wanting one page to replace classification/clinical/CE/legal advice.

Read it if your product is a device/MDSW; an EU customer/notified body asks about classification/CE/UDI; you are building or revising an MDR page; or you need to separate MDR, IVDR, GPSR, ISO 13485, UDI and recall. Skip it if you treat ISO 13485 as CE, all Class I as self-declared, or EUDAMED as optional. It supports self-review of classification, route, files, clinical/PMS, UDI/EUDAMED, roles, labels and page wording.

FAQ

Does MDR apply now?

MDR 2017/745 entered into force on 25 May 2017 and has applied since 26 May 2021, replacing MDD/AIMDD. Transition was extended by Regulation (EU) 2023/607: subject to conditions (QMS, notified-body application/contract, no serious safety issues), legacy-certificate devices may continue in stages—Class III/implantable IIb until 31 December 2027, other IIb/IIa/Is/Im until 31 December 2028 (subject to the regulation/notified body).

How is classification done?

Under MDR Annex VIII, devices are I, Is (sterile), Im (measuring), IIa, IIb or III; Class I non-sterile/non-measuring can generally self-declare, while Is/Im/IIa/IIb/III generally need a notified body; MDSW/Annex XVI products are also covered. A wrong classification makes the route/CE/file wrong—confirm with regulatory/notified bodies.

How are CE/notified bodies handled?

Class I non-sterile/non-measuring can self-declare (still requiring technical file/DoC/CE); Is/Im/IIa/IIb/III generally need a notified body, with additional expert/clinical requirements for III/implantable devices. CE marking plus DoC; certificates have scope/validity/conditions, and changes/new versions need assessment; CE is not a permanent certificate.

What about clinical/PMS?

Clinical evaluation needs a plan/data/literature/analysis/report; PMCF is planned/executed by risk/device; PMS needs a system/data/analysis/PSUR/trend/risk reassessment; missing clinical/PMCF can affect CE. PMS is not after-sales statistics; it must feed back into risk/design/labels.

When are UDI/EUDAMED required?

MDR requires UDI for traceability; EUDAMED's first four modules (Actor, UDI/Device, Notified Bodies/Certificates, Vigilance) are mandatory from 28 May 2026 (subject to the Commission notice). Manufacturers/ARs/importers must register/report, and UDI label/database/file must match.

How should the website/customer statement be written?

State products/classification, CE/notified body, GSPR/technical file, clinical/PMCF/PMS, UDI/EUDAMED, vigilance/recall, AR/PRRC/importer/distributor roles, labels/IFU/language and transition; do not write "ISO 13485 = CE/all Class I self-declared/CE forever/EUDAMED can wait/absolutely safe". Patient/clinical documents are provided on a need-to-know basis.

One-sentence takeaway

A Changzhou manufacturer's MDR page is not about "ISO 13485/CE certificates". It should turn product/classification, CE/notified body, GSPR/technical file, clinical/PMCF/PMS, UDI/EUDAMED, vigilance/recall, AR/PRRC/importer/distributor roles and labels/IFU into a verifiable checklist—so a customer/authority can see the classification, route, file/clinical/UDI status and who is responsible.

Method and limitations

This is a review of public rules and project practice, not an audit or legal opinion on any company's products, medical-device safety, clinical, testing, CE, UDI/EUDAMED or compliance. No undisclosed patient/clinical/customer data were used. Classification, route, files, clinical, PMS, UDI, roles and acceptance items are editorial suggestions, not safety/clinical/legal conclusions. Specific classification, GSPR, clinical, CE, UDI/EUDAMED, vigilance and transition depend on the regulation, harmonised standards, notified bodies and the competent authority.

Sources and scope

Information is current to 2026-11-05. The following are EU official/legal pages; their articles, annexes, guidance and notices control.

  1. Regulation (EU) 2017/745 on medical devices (MDR), adopted 5 April 2017, published 5 May 2017: EUR-Lex. Classification, GSPR, clinical, CE, UDI/EUDAMED, vigilance, roles and transition.
  2. European Commission, Medical Devices sector: European Commission. MDR/IVDR implementation, guidance, notified bodies and market surveillance.
  3. European Commission, Medical Devices — EUDAMED: European Commission. EUDAMED modules, 28 May 2026 mandatory use and registration.
  4. Regulation (EU) 2023/607 amending MDR/IVDR transition: EUR-Lex. Legacy-certificate transition/conditions/classes.
  5. European Commission, Medical Devices — New regulations: European Commission. MDR/IVDR application, guidance and updates.
About the author

Lingyi Information Official (delivery team) supports requirements, proposals, and acceptance for enterprise websites, brand and brochure design, smart manufacturing, and AI projects. This article is public research and project practice, not EU legal, medical-device safety, clinical, testing or compliance advice; specific projects follow the regulation, standards, notified bodies and the competent authority.

Turn the MDR page into a reviewable checklist

Bring the product/classification, CE/notified body, technical/clinical files, UDI/EUDAMED and role arrangements. We will map route, files, vigilance and labels into a reviewable checklist.

Book an MDR page review