MDR Notified Body Scope: The Codes Manufacturers Skip

A CE mark under EU MDR does not come from a Notified Body — it comes from a Notified Body whose designation actually covers your device's classification codes. MDCG 2019-14 sets out the code system every competent authority uses to limit what a given Notified Body may assess, and manufacturers who pick a well-known name without checking it discover the mismatch at technical review — not before.

The code system behind every designation

Every Notified Body's MDR designation is built from the same code catalogue. EU MDR & IVDR classification decides which codes apply to your device; MDCG 2019-14 decides which Notified Bodies are authorized to assess devices carrying those codes. The two systems are related but distinct, and conflating them is exactly how manufacturers end up applying to a Notified Body that cannot actually review their file.

Where the scope actually gets checked

A Notified Body's designation can be narrowed at the competent authority's discretion during the designation process itself — a body might hold a general non-active-implant designation while being explicitly excluded from a specific implant category, or cover software broadly while excluding a specific risk classification. None of that shows up until someone checks the code-level detail. At the technical-review stage, the Notified Body verifies (or assigns) the code for your device and confirms the application falls inside its own designation — which means a scope mismatch surfaces after you have already committed months to that relationship, not before.

• Check NANDO before you shortlist, not after you apply. The European Commission's NANDO database lists each Notified Body's current codes and any stated limitations.
• Match codes to your actual classification, not your device category. Two devices in the same therapeutic area can carry different MDS/MDT codes depending on sterilization, nanomaterial content, or software classification.
• Ask for confirmation in writing. A sales conversation is not a designation check; get the Notified Body to confirm scope against your specific codes before signing.
• Re-check scope on a significant device change. A design change can shift which codes apply, even to a device already certified by that Notified Body.

The scope mismatch does not surface when you sign the application. It surfaces at technical review, months later, when the Notified Body finally checks whether the codes on your device are the codes on its own designation. Why NANDO comes before the shortlist

Building the check into your CE marking strategy

Verifying designation scope is a small, bounded task next to the cost of discovering it late: a code-by-code comparison against NANDO, in writing, before an application goes in. It belongs inside your broader CE marking strategy, not as an afterthought once a Notified Body has already been chosen on reputation or price. For manufacturers weighing a change of Notified Body mid-review, the same code check tells you whether a switch actually solves the problem or just moves it. Our European regulatory strategy team runs this verification before a client commits to any Notified Body relationship.