Navigating MDCG Guidance: Which Documents Matter and When

What MDCG guidance actually is — and is not

The Medical Device Coordination Group is a body of national competent authority representatives that coordinates MDR implementation across EU member states. The guidance documents it publishes are not legally binding — they do not amend the regulation, and manufacturers are not technically required to follow them. In practice, however, this distinction matters less than it sounds.

Notified Bodies reference MDCG guidance in their audits. National competent authorities use it to inform market surveillance decisions. When you submit technical documentation, auditors and reviewers will expect your approach to be consistent with relevant MDCG positions unless you have documented reasons to deviate. Ignoring MDCG guidance without acknowledgement is not a defensible position — taking a different approach with a reasoned explanation usually is.

The guidance landscape has grown substantially since MDR came into force. There are now over 80 published documents covering everything from borderline products to UDI labelling to clinical evaluation methodology. Not all of them are equally relevant to your situation — knowing which ones matter for your device type and compliance stage is worth the time to figure out.

The most practically relevant documents

A few MDCG guidance documents come up constantly in practice, regardless of device type:

MDCG 2020-5 and its updates — Clinical Evaluation is the reference point for understanding what the regulation expects from your clinical evaluation report. It aligns with the MEDDEV 2.7/1 Rev 4 tradition but adds MDR-specific requirements. If your clinical evaluation is being scrutinised by a Notified Body, this document tells you what framework they will use.

MDCG 2020-6 — Sufficient Clinical Evidence for Legacy Devices addresses a specific problem many manufacturers face during the MDD-to-MDR transition: you have a device with a long clinical history under MDD, but MDR requires updated clinical evidence. This document provides the framework for demonstrating when existing clinical data is sufficient and when new clinical investigations are needed. It is essential reading if you are transitioning a legacy device.

MDCG 2019-11 (updated) — Software Qualification and Classification is the go-to reference for software classification decisions. It includes decision trees and examples. If you are dealing with any software component — standalone medical device software, software integrated into hardware, or mobile apps — this document should be part of your classification documentation.

MDCG 2021-24 — Classification of Medical Device Software extends and refines the software classification guidance specifically under Rule 11 of Annex VIII. If your classification analysis involves software at Class IIa or above, this is not optional background reading.

MDCG 2022-2 — Guidance on General Safety and Performance Requirements (GSPR) provides the authoritative interpretation of Annex I. Your GSPR checklist — which has to document how each requirement is met — should be built with this guidance in view.

MDCG 2022-5 — Borderline and Classification is the reference document for borderline determinations. It includes worked examples and tables covering specific product types. If you are documenting a scope decision or a borderline product analysis, this document provides the framework regulators will expect you to have used.

How guidance gets updated — and what to do about it

MDCG guidance is not static. Documents get revised, sometimes substantially. MDCG 2020-1 on clinical evaluation, for example, has gone through multiple revisions, and each revision has shifted expectations for what a compliant clinical evaluation looks like.

One thing that catches teams off guard: if your technical documentation references a specific MDCG guidance document version and that document has since been updated, your documentation may be out of alignment with current expectations even if it was correct when written. Keeping a short log of the MDCG guidance versions you referenced during your last documentation cycle — and checking for updates at each PSUR review — is a simple practice that prevents silent drift.

The MDCG guidance registry is maintained on the European Commission website. The documents are organised by topic area and include publication and revision dates. Building a review of recently updated documents into your annual surveillance routine takes less than an hour and is worth doing.

Guidance on the EUDAMED and UDI area

The UDI and EUDAMED guidance documents are in a category of their own because they have direct operational consequences — getting your UDI assignment wrong, or failing to register correctly in EUDAMED, can affect your ability to legally sell. MDCG 2018-1 v5 (EUDAMED guidance) and the UDI guidelines are updated regularly as the database systems evolve. These are documents your regulatory affairs team or regulatory operations team needs to track actively, not just read once.

Building a guidance reference map for your device

A useful practice: when you begin work on a new device or a significant update, build a short guidance map — a list of the MDCG documents relevant to that device type, class, and intended purpose, along with their current version and the date you last checked for updates. This does not need to be a formal document; a working note in your project file is enough. When a Notified Body auditor asks what guidance you used, you have a clear answer. When guidance is updated, you have a starting point for assessing whether your documentation needs revision.