top of page

What Is an EMDN Code? The EMDN Field in ÜTS and the Selection Rules

What is an EMDN code, and which field in the ÜTS registration does it go into? The seven-level structure, the link to EUDAMED, the mandatory and optional field rule, and choosing the most detailed code.

In a device record you have reached the "Classification Information" heading, and next to GMDN there is also an EMDN Term field. The EU declaration of conformity from your manufacturer has an EMDN code, but it is a three-character high-level code, and you found that code in the list and selected it. This selection will most likely not be accepted, because for this situation the source states clearly what is to be done, and what it states is not to select the high-level code.

This page sets out, in the source texts' own sentences, what EMDN is, its relationship to EUDAMED and UDI, the structure of the code, the field in ÜTS where it is entered, under which condition the field is mandatory and under which it is optional, and how a wrongly selected code is corrected. The classification rules themselves are not the subject of this page; this is the nomenclature side.

The sources are the Manual on Registration Procedures of Medical Devices in the Product Tracking System (Tıbbi Cihazların Ürün Takip Sistemine Kayıt Süreçlerine İlişkin Kılavuz) with its Annex-22, and the Medical Device Regulation (Tıbbi Cihaz Yönetmeliği) published in the Official Gazette No. 31499 (bis) of 2/6/2021.

EMDN is the name of the terminology obligation

The source of the terminology obligation is the Regulation, but the Regulation does not use the abbreviation. Article 26 of the Medical Device Regulation says that manufacturers and other natural or legal persons required to use the European database on medical devices under this Regulation will use the terminology provided free of charge by the Commission. The word "EMDN" does not appear in the text of the article; what it says is that the terminology is provided free of charge by the Commission and that its use is compulsory.

The abbreviation is defined by the Manual. Article 4(1)(k) of the Manual defines EMDN, with the expansion European Medical Device Nomenclature, as the European Medical Device Nomenclature, that is, terminology. Point 3 of Annex-22 of the Manual sets the relationship directly: under Article 26 of the MDR and Article 23 of the IVDR, EMDN is intended to support the EUDAMED functioning relating to medical devices.

So the concrete counterpart of the abstract terminology obligation in the Regulation is EMDN, and the text that makes this link is an annex of the Manual. Knowing this distinction matters for being able to answer the question "on the basis of which article" in an audit.

The EUDAMED link makes EMDN a registration field

To understand why EMDN appears in front of you as a data field, one has to look at the purposes of EUDAMED. Article 33(1)(b) of the Medical Device Regulation lists, among the purposes of EUDAMED, enabling the unique identification of devices on the market and facilitating their traceability.

Point 4 of Annex-22 of the Manual makes this concrete: among the various uses of EMDN is its use by manufacturers for the registration of medical devices in EUDAMED, where medical devices will be associated with their UDI-DI number. Point 5 of the same annex says that, because EMDN serves regulatory purposes primarily to support the requirements of the MDR and IVDR, it plays an important role in MDR/IVDR device documentation and technical documentation, in technical documentation sampling carried out by notified bodies, and in post-market surveillance, vigilance and post-market data analysis.

The continuation of the same point says that EMDN is intended to give patients a basic device description concerning their own devices and all other devices registered in EUDAMED and available on the market. The code is not a label but a search and grouping key. A wrong code not only breaks your record; it also upsets which group your device will be analysed with in surveillance and vigilance data.

The source and availability of the code

Where the code comes from is also written down. Point 6 of Annex-22 of the Manual says that EMDN was established in accordance with the criteria and requirements set by the EU regulators in the European Commission and the MDCG, following the European Commission's notice that it would base the future EMDN on the National Classification of Medical Devices used by the Italian Ministry.

Point 7 of the same annex says that all stakeholders can have free access to the whole of EMDN; so a wide group of stakeholders such as manufacturers, patients, research organisations, practitioners, hospitals and pharmacies can use it. Article 27(4)(ç)(7) of the Manual repeats the same information on the ÜTS side, stating that all the codes can be reached free of charge at the European Commission's EMDN query address, and that all the codes at that address are also on the "Select EMDN Term" ("EMDN Terim Seç") screen and on the "List EMDN" ("EMDN Listele") screen under the "Definition" section in ÜTS.

The measure of a code's validity is also this address. Sub-point 8 of the same point says that, in EMDN code queries, the data at the Commission's EMDN query address will be accepted as correct and valid, and that only correct and valid EMDN codes will be defined in ÜTS.

Structure: a seven-level tree and at most thirteen characters

Knowing what the code looks like is half of selecting the right code. The "structure of EMDN" heading in Annex-22 of the Manual says that EMDN is characterised by an alphanumeric structure built in a seven-level tree-like hierarchy and groups medical devices into three main levels: the first hierarchical level is categories, the second hierarchical level is groups, and the third hierarchical level is types, expanding where necessary into several levels of detail.

The same section also gives the reading of the code: each alphanumeric code begins with a letter indicating the category to which the device belongs, followed by two numbers indicating the group and a series of numbers indicating the type; the maximum number of characters is set at thirteen.

And the critical sentence is at the end of the same section: using the tree-like hierarchy of EMDN, users should always assign to their devices the most detailed and terminal term available, that is, the lowest level in the tree. This sentence is the direct answer to the mistake at the start of the page.

In which field of ÜTS the code is entered

The EMDN field is repeated in three separate articles, for three separate record types, and in all three it is in the same place.

  • Devices under the MDR: Article 27(4) of the Manual lists the fields under the "Classification Information" heading; point (ç) of the same paragraph is the "EMDN Term" field.

  • Systems and procedure packs under the MDR: Article 28(6) of the Manual sets up the same heading for the SİP record; point (ç) of the same paragraph is the SİP's EMDN Term field.

  • Devices under the IVDR: Article 30(4)(ç) of the Manual regulates the same field for the IVDR record.

In all three articles there is also a second field that shows the result of the selection. Article 27(4)(d)(1) of the Manual says that the information on the EMDN code selected in the field in point (ç) of the same paragraph will appear in the "Selected EMDN Term" ("Seçilen EMDN Terim") field; sub-point 2 says that, if the code was selected wrongly, this selection can be removed through the "Remove" ("Çıkar") field in the relevant field. The same provision is repeated for IVDR devices in Article 30(4)(d) of the Manual.

Correcting a wrong code is this simple while the record is still in your hands. After the record reaches "Registered" status the situation changes; we return to it under a separate heading below.

Is the field mandatory or optional: the source has written a conditional rule

This is the most misunderstood point about EMDN, and the source's sentence must be read carefully.

Article 27(4)(ç)(1) of the Manual says that, until a new decision is taken by the Agency on the subject, selecting this field in ÜTS is optional if the EMDN code identifying the device is not in at least one of the documents belonging to the device, that is, in the EU certificate or the EU declaration of conformity.

Sub-point 5 of the same point sets up the opposite: if the EMDN code identifying the device is in at least one of the documents belonging to the device, selecting in this field the most detailed code and terminal term of the EMDN code stated in the relevant document or documents is mandatory.

Read together, the two sub-points give this rule: the field being optional is not an exemption but a condition. If there is a code in the document, the field is mandatory. If there is no code in the document, the field is for now a matter of choice, and this holds until a new decision by the Agency. So before skipping EMDN as "optional anyway", the thing to do is open the EU declaration of conformity and the EU certificate from the manufacturer and check whether there is an EMDN code in them.

The same rule applies to systems and procedure packs. Article 28(6)(ç)(1) of the Manual says that the field is optional if the EMDN code identifying the SİP is not in the SİP Declaration and/or the EU certificate; sub-point 5 of the same point says that, if the code is in at least one of these documents, selecting the most detailed code and terminal term is mandatory.

If the document has a high-level code, the most detailed code is still selected

The source directly prohibits the mistake described at the start of the page. The second sentence of Article 27(4)(ç)(5) of the Manual says that, in documents where the EMDN code is given, even if the EMDN code is a higher-level code and terminal term, the most detailed EMDN code appropriate to the device and associated with the EMDN code in the relevant document will be selected in this field.

Sub-point 9 of the same point closes the rule on the system side too: only the most detailed EMDN codes and terminal terms defined at the Commission's EMDN query address are added to ÜTS; less detailed, that is, higher-level EMDN codes are not added.

Sub-point 3 of the same point sets a general rule in the same direction: the EMDN code most appropriate to the device is selected from the "Select EMDN Term" screen, and the most detailed code and terminal term appropriate to the device, that is, the lowest level according to the seven-level tree-like hierarchy model, is always selected as the EMDN code.

The practical result: if the code in the document the manufacturer sent you is at category or group level, you do not select that code; you go down the branch under it and select the terminal term that covers your device. This is not an interpretation; it is what the same sub-points write.

What to do if there is no code in the document at all

This is common in imported products. Article 27(4)(ç)(6) of the Manual gives two options: if the device's EMDN code is not in the documents belonging to the device, the EMDN code obtained from the manufacturer may be selected, or, if the manufacturer does not have an EMDN code, the most appropriate EMDN code identifying the device may be selected.

The order matters. The manufacturer is asked first; if the manufacturer has no code, the most appropriate code identifying the device is selected. Choosing a code on your own is the second option, which comes into play only when the manufacturer has no code. The same provision is repeated for the SİP in Article 28(6)(ç)(6) of the Manual, and for IVDR devices in Article 30(4)(ç)(6).

There is one more limit that must not be forgotten: sub-point 4 of Article 27(4)(ç) of the Manual says that each device has only one EMDN code. The same provision is repeated for the SİP in Article 28(6)(ç)(4) of the Manual: each SİP has only one EMDN code. If your device seems to fit more than one branch, this is not a multiple-selection situation but a sign that your intended purpose has not been defined narrowly enough.

If the code you are looking for is not in ÜTS

A code found in the Commission's list may not be defined in ÜTS. Article 27(4)(ç)(8) of the Manual regulates this situation: if the EMDN code identifying the device is defined at the Commission's query address but not in ÜTS, a request is opened through the "Submit Request" ("Talep Bildir") screen in ÜTS, in the "EMDN Addition" ("EMDN Ekleme") area, for the addition of that code; if the request is found appropriate and the code is confirmed in the query to be correct and valid, the relevant EMDN code is defined in this field.

Note the order: the code being in the Commission's list is a precondition. A request to have a code that is not in the list added to ÜTS runs into the rule in the last sentence of the same sub-point, "only correct and valid EMDN codes are defined in ÜTS".

The same addition mechanism exists for neighbouring fields. Article 27(4)(b)(7) of the Manual shows the same "Submit Request" route for the GMDN code, and Article 27(4)(c)(3) for the branch type code.

EMDN, GMDN and branch type are on the same screen but are not the same thing

All three fields are under the "Classification Information" heading, and none of the three takes the place of another.

Article 27(4)(b)(1) of the Manual says that the GMDN field must be selected in ÜTS. Sub-point 2 of the same point says that each device has only one GMDN code; sub-point 8 says that, in GMDN code queries, the data of the GMDN Agency will be accepted as correct and valid. Sub-point 1 of point (c) of the same paragraph says that the branch type code is also a mandatory field, and sub-point 2 says that the branch type that exactly identifies the device, or, if there is no exactly defined option, identifies it most appropriately, will be selected.

The asymmetry here is important: GMDN and branch type are mandatory fields, while EMDN is subject to the conditional regime described above. Assuming that all three are mandatory, or that all three are optional, leads to errors in two different directions.

There is also a consistency rule on the GMDN side, and the same logic should be applied in selecting EMDN. Article 27(4)(b)(5) of the Manual says that consistency is mandatory between the information in the description of the GMDN code to which the device is matched and product features such as whether the device is single-use and/or sterile. Sub-point 6 of the same point describes the concrete form of this inconsistency: the GMDN code description of a single-use device contains the expression single-use; on the other hand, if the GMDN code description of a reusable device contains an expression about single use, and the device is one used several times on a single patient, selecting the relevant feature field as "Yes" is mandatory.

A code that contradicts the intended purpose and the class shakes the whole record

The most frequent and most expensive mistake is the code not matching the device's intended purpose. Article 4(1)(jj) of the Manual defines the intended purpose as the use for which a device is intended according to the data supplied by the manufacturer on the label, in the instructions for use or in promotional or sales materials or statements, or as specified by the manufacturer in the performance evaluation.

This definition also determines the source of the code to be selected: the code is selected not according to how you promote the product but according to how the manufacturer declares the intended purpose. The intended purpose declaration and the risk class on the same screen are also tied together. Article 27(4)(a)(2) of the Manual says that the device's risk class under the MDR is selected from the relevant field; sub-point 4 of the same point says that additional information on the classification rules is in Article 56 of the Manual.

The conclusion that the four fields in the same paragraph, that is, class, GMDN, branch type and EMDN, must not contradict one another follows from these provisions as a whole. Selecting class III for a device and marking a low-risk consumable branch on the EMDN side disturbs not two fields alone but the consistency of the record.

The key that ensures the consistency of the record is in the same article. Article 27(5)(c)(1) of the Manual says that the Basic UDI-DI field must be selected in ÜTS; sub-point 2 of the same point says that the Basic UDI-DI is the main key in EUDAMED and ÜTS and in the relevant documents for linking devices of the same manufacturer with the same intended purpose, risk class and essential design and manufacturing characteristics. Inconsistency between the EMDN codes of devices gathered under the same Basic UDI-DI removes the function of this main key.

Changing the code after the record has entered the system is a separate process

After the record reaches "Registered" status, correcting EMDN is no longer a one-sided action. Article 43(1) of the Manual says that, where records belonging to different firms exist for a device registered in ÜTS under the same barcode and there are data differences among them, the relevant product parameters must be made identical and consistent in ÜTS before the first device application.

Paragraph 7 of the same article brings EMDN within this scope by name: data change requests relating to fields requiring Agency assessment, such as "Class", "GMDN" and "EMDN", are in every case mentioned in paragraphs 4, 5 and 6 of the same article submitted to the Agency's assessment and approval. So even if the other firms accept unanimously, the EMDN field is not corrected automatically; it goes to the Agency.

Paragraph 8 of the same article lists the sources according to which the Agency makes this assessment: the relevant provisions in the regulation and manual covering the device, the document and device notification records in ÜTS belonging to the device, the guidance and announcements prepared by the Commission and the Agency, the data on the relevant official query sites for fields such as GMDN and EMDN, and the evidence documents and visual records submitted with the request. Paragraph 3 of the same article says that the request is submitted for the opinion of the other firms that have a record with the same barcode and that the period for giving an opinion is 5 days.

The practical lesson is this: selecting the EMDN code correctly at the first registration is incomparably easier than correcting it afterwards.

EMDN and UDI do not replace each other

One last distinction. EMDN is a nomenclature system, UDI is an identification system, and their functions are different.

Article 27(1)(a) of the Medical Device Regulation says that the UDI consists of a UDI device identifier specific to a manufacturer and a device and a UDI production identifier identifying the device production unit. Article 29(1) of the same Regulation says that, before placing a device on the market, the manufacturer will assign a Basic UDI-DI to the device and enter it into the UDI database together with the other core data elements. Article 4(1)(ggg) of the Manual also defines the Basic UDI-DI as the main key used for linking devices with the same intended purpose, risk class and essential design and manufacturing characteristics.

UDI singles out the device, EMDN classifies the device. As stated in point 4 of Annex-22 of the Manual, EMDN is a terminology with which medical devices will be associated, in EUDAMED, with their UDI-DI number; it is not the UDI-DI itself. A record may have a correct barcode but a wrong EMDN code; the reverse is also possible. Check the two fields separately.

What we do in code selection, and who makes the decision

Within medical device ÜTS registration consultancy, the outputs we produce on the EMDN side are these:

  • Document scan: We scan the EU declaration of conformity, the EU certificate and the SİP declaration from your manufacturer for an EMDN code, and determine, according to sub-points 1 and 5 of Article 27(4)(ç) of the Manual, whether the field is mandatory or optional.

  • Terminal term selection: If the code in the document is a high-level one, under sub-points 5 and 9 of the same point we determine, with reasons, the most detailed code and terminal term under that code that suits the device.

  • Consistency check: We compare the selected EMDN code with the class, GMDN, branch type, intended purpose declaration and Basic UDI-DI, and report any contradiction before registration.

  • EMDN addition request: For codes that are in the Commission's list but not defined in ÜTS, we prepare the "Submit Request" application under sub-point 8 of the same point.

  • Correction file: If an EMDN correction is needed on a registered device, we collect the evidence set listed in Article 43(8) of the Manual and write the data change request.

  • SİP and IVDR matching: For systems and procedure packs and for devices under the IVDR, we make separate code selections under Article 28(6)(ç) and Article 30(4)(ç) of the Manual.

What we cannot do is clear too. We cannot create an EMDN code; point 6 of Annex-22 of the Manual says that the nomenclature was established according to criteria set by the regulators of the European Commission and the MDCG, and the validity of the code pool is tied to the Commission's query address in point 7 of the same annex and in Article 27(4)(ç)(8) of the Manual. Nor can we change the code written in the manufacturer's document; if there is a code in the document, sub-point 5 of the same point makes it mandatory to select the most detailed code associated with that code, and selecting a different branch conflicts with this provision. We also cannot commit to the outcome of the Agency's EMDN assessment; Article 43(7) of the Manual ties this field to the Agency's approval.

The way of working is as under the other headings: the firm opens a user authorisation for the consultant from its own ÜTS firm page, the registration fields including EMDN are filled in with the "Medical Device Registration Operator" ("Tıbbi Cihaz Kayıt Elemanı") authorisation, and the person who electronically signs the application remains the firm's signatory.

Tıbbi Cihaz ÜTS Kayıt Danışmanlığı

Request an ÜTS registration consultancy quote

Ehlibeyt Mahallesi, Tekstilciler Caddesi No: 35/7 06520 Çankaya / Ankara - TÜRKİYE

Cevizli Mahallesi, Zuhal Caddesi Ritim İstanbul B Blok, No:44 Maltepe / İstanbul - TÜRKİYE

info@medexmedikal.com
+90 505 580 4622
+90 312 389 1354

ÜTS Guides · Legislation Calendar · Glossary · ÜTS Guide Index · Frequently Asked Questions

Services: ÜTS Consultancy · Who Carries Out the ÜTS Registration? · ÜTS Document Registration Consultancy · ÜTS Product Registration Consultancy · Importer ÜTS Registration Consultancy · Sales Centre Authorisation Certificate · EUDAMED Registration Consultancy · MDR/IVDR Declaration of Conformity · Technical File Preliminary Review · Label and Instructions for Use Check · PRRC Service · PMS and PSUR · Clinical Evaluation · EMDN and GMDN Code Determination · Certificate of Free Sale · EUDAMED XML Generator · ÜTS Registration Training · Correction of a Rejected ÜTS Application

KVKK and Privacy Policy | Cookie Policy | Accessibility Statement

© 2026 Medex Kurumsal Danışmanlık Ltd. Şti.

bottom of page
WhatsApp Hemen Ara