
GMDN and EMDN Codes
When you register your device in ÜTS, two separate nomenclature codes are requested, and a widespread piece of misinformation circulates in the market that the two replace each other
GMDN and EMDN Codes: Two Separate Mandatory Fields in ÜTS
When you register your device in ÜTS, two separate nomenclature codes are requested, and a widespread piece of misinformation circulates in the market that the two replace each other. The sentence "GMDN has been abolished, EMDN is now used" does not match the provisions of the TİTCK Guide. The Guide defines GMDN and EMDN separately, regulates them as separate screen fields and sets separate selection rules for each.
This page explains, with source articles, the definition of the two codes, which one is mandatory on which registration screen, what to do if the code is not in the document, how to have a code that is not defined in ÜTS added, and how to change these fields after registration. The references belong to TİTCK's "Guide on Registration Processes of Medical Devices to the Product Tracking System" (TCKKD-KLVZ-03) and the Medical Device Regulation.
What Is GMDN, and Is It Still Mandatory in ÜTS?
GMDN is defined in the definitions article of the Guide as "GMDN (Global Medical Devices Nomenclature)". It is an international term system that describes a device by its generic type; each term has a code number and a description.
The answer on the ÜTS side is clear: GMDN is a mandatory field on all three device registration screens. The fourth paragraph of Article 25 of the Guide regulates device registration under the old regulations (MDD, AIMDD, IVDD), the fourth paragraph of Article 27 regulates device registration under MDR, and the fourth paragraph of Article 30 regulates device registration under IVDR. In all three, the first sentence of the GMDN sub-item under the "Classification Information" heading is the same: this field is a mandatory field to be selected in ÜTS.
The requirement continues in system/procedure pack registrations. The fifth paragraph of Article 26 of the Guide lists the GMDN field as a mandatory field in a SİP registration under the old regulations, and the sixth paragraph of Article 28 does the same for a SİP registration under MDR.
Device registration under the old regulations: GMDN mandatory, fourth paragraph of Article 25 of the Guide
Device registration under MDR: GMDN mandatory, fourth paragraph of Article 27 of the Guide
Device registration under IVDR: GMDN mandatory, fourth paragraph of Article 30 of the Guide
SİP registration under the old regulations: GMDN mandatory, fifth paragraph of Article 26 of the Guide
SİP registration under MDR: GMDN mandatory, sixth paragraph of Article 28 of the Guide
What Is EMDN?
EMDN is defined in the definitions article of the Guide as "EMDN (European Medical Device Nomenclature): European Medical Device Nomenclature (Terminology)". It is a separate nomenclature system, independent of GMDN, with its own tree structure and its own term list.
Sub-item (ç) of the fourth paragraph of Article 27 of the Guide states EMDN's function explicitly: EMDN is the terminology to be used when registering devices in the EUDAMED database and in ÜTS. The same sub-item refers to Annex-22 of the Guide for the basic explanations on the structure of EMDN. That is, EMDN is the system that determines by which term a device is referred to on the European database side; ÜTS also keeps this term in its own record.
Why Is the View That GMDN Has Been Abolished Not Correct?
This claim contradicts the source at four separate points. None is open to interpretation; all four are provisions written in the Guide.
Separate definitions: the definitions article of the Guide defines GMDN in sub-item (ö) and EMDN in sub-item (k) separately. No wording is used in which one replaces the other.
Separate screen fields: on the MDR and IVDR registration screens, GMDN and EMDN are regulated in different sub-items under the "Classification Information" heading, with different selection rules. They are not a single field.
Application grouping still depends on GMDN: the seventh paragraph of Article 40 of the Guide says that in device applications under the old regulations, applications are allowed only for devices linked to the same GMDN code. An application is not grouped on the basis of a field that has been abolished.
Both are separate items in the data change list: the seventh paragraph of Article 44 of the Guide lists the fields for which a data change request can be made. In this list GMDN is in sub-item (c) and EMDN is in sub-item (ş). Their being two separate items in the same list directly shows that they are separate data fields in ÜTS.
A fifth piece of evidence can be added. The eighth and ninth paragraphs of Article 10 of the Guide list the cases in which the declaration of conformity can be updated for devices benefiting from the transition provisions. Apart from the scope of products in the declaration and "significant changes" in the design and intended purpose of the devices, updates can be made for changes such as a change of manufacturer address, a change of manufacturing site, a change of EU authorized representative and a change of GMDN code. A change of a code that has been abolished would not be counted as a ground for update.
Every Device Has Only One GMDN Code
The Guide repeats this rule on all three registration screens: each device has only one GMDN code. The provision appears with the same sentence in the GMDN sub-item of the fourth paragraph of Article 25, in the GMDN sub-item of the fourth paragraph of Article 27 and in the GMDN sub-item of the fourth paragraph of Article 30. It has a counterpart on the SİP side as well: the fifth paragraph of Article 26 of the Guide says each SİP has only one GMDN code, and the sixth paragraph of Article 28 says the same rule for SİPs under MDR.
In practice this rule is a burden on companies that try to bring different variants of the same product family together in a single record. If two variants fall under different GMDN terms, two separate device records are needed. The approach of "let's mark the closest one, it is the same family anyway" turns into an error that has to be corrected later with a data change request.
What to Do If the GMDN Code Is Not in the Document?
The Guide defines a tiered order here; the order cannot be skipped. The GMDN sub-item of the fourth paragraph of Article 25 of the Guide and the GMDN sub-item of the fourth paragraph of Article 27 give the same steps.
First step: if the GMDN code identifying the device appears in at least one of the documents of the device, the GMDN code stated in that document is selected. On the old regulations side these documents are the EC certificate and the declaration of conformity; on the MDR and IVDR side, the EU certificate and the EU declaration of conformity.
Second step: if the GMDN code of the device does not appear in the documents, the GMDN code obtained from the manufacturer is selected.
Third step: if the manufacturer does not have a GMDN code, the most appropriate GMDN code identifying the device is selected.
The practical meaning of this order is as follows: if the code is in the document, there is no debate, that code is entered. If it is not in the document, the manufacturer is asked first; the code received by correspondence is put on record. Only if the manufacturer has no code either does the choice fall to the registering party, and this choice must really identify the device.
If the GMDN Code Is Not Defined in ÜTS: "GMDN Addition" Request
Finding the right code does not mean that the code can be selected in ÜTS. The seventh sub-item of the GMDN sub-item of the fourth paragraph of Article 25 of the Guide and the seventh sub-item of the GMDN sub-item of the fourth paragraph of Article 27 regulate this case: if the GMDN code identifying the device is not defined in ÜTS, a request is opened for the addition of that code through the "GMDN Addition" field on the "Report Request" screen in ÜTS.
Acceptance of the request is tied to two conditions. The request must be found appropriate and the code must be confirmed as correct and valid in the GMDN query; in addition, the code must cover a device or devices within the scope of the Medical Device Regulations. If these conditions are met, the relevant GMDN code is defined in the field.
In practice, this step is the item in the registration calendar that is easiest to overlook in catalogues with many products. Checking in advance, while drawing up the product list, which codes are already defined in ÜTS prevents entering an unexpected request process at the registration stage.
The GMDN Description Must Be Consistent With the Device Characteristics
The code number being correct is not enough; the description text of the code must not contradict the characteristics of the device either. The fifth sub-item of the GMDN sub-item of the fourth paragraph of Article 25 of the Guide states that consistency is mandatory between the information in the description of the GMDN code to which the device is mapped and product characteristics such as whether the device is single-use and whether it is sterile. The same provision is also in the relevant sub-items of Articles 27 and 30.
The sixth sub-item gives an example of how this consistency works on the single-use axis. The description of the GMDN code of a single-use device contains the expression single-use. On the other hand, if the description of the GMDN code of a reusable device contains an expression related to single use and the device is one that is used more than once on a single patient, selecting "Yes" in the relevant field on the registration screen is mandatory. The Guide here refers to sub-item (j) of the seventh paragraph in Article 25 and to sub-item (k) of the seventh paragraph in Article 27.
GMDN Agency Data Is the Basis
Which source will be used as the basis in code verification is also written. The eighth sub-item of the GMDN sub-item of the fourth paragraph of Article 25 of the Guide and the corresponding sub-item of Article 27 state that in GMDN code queries the data of the GMDN Agency is accepted as correct and valid.
The seventh sub-item of the same sub-items sets one more limit: only correct and valid GMDN codes are defined in ÜTS. Read together, these two sentences show that codes copied from second-hand lists, old catalogue records or the ÜTS records of peer companies are not accepted as a basis. Verification is made on the data of the GMDN Agency.
Is EMDN Mandatory or Optional?
The EMDN field is designed with a different logic from GMDN: it is a conditional field. The first sub-item of sub-item (ç) of the fourth paragraph of Article 27 of the Guide and the first sub-item of sub-item (ç) of the fourth paragraph of Article 30 describe in which cases this field is optional: until a new decision is taken by the Agency on the subject, and if the EMDN code identifying the device does not appear in at least one of the documents of the device (EU certificate, EU declaration of conformity), selecting the field in ÜTS is optional.
The opposite of the condition creates an obligation. The fifth sub-item of the same sub-items says that if the EMDN code identifying the device appears in at least one of the documents, selecting in this field the most detailed code and the terminal term of the EMDN code stated in that document is mandatory.
If the document has an EMDN code: the field is mandatory; the most detailed level of the code in the document is selected
If the document has no EMDN code: the field is optional until the Agency takes a new decision
If it is not in the document but the manufacturer has it: under the sixth sub-item of the same sub-item, the EMDN code obtained from the manufacturer can be selected; if the manufacturer has no code either, the most appropriate code identifying the device can be selected
The optionality is temporary and is tied to a new decision of the Agency. That a field that can be left empty today may become mandatory tomorrow is foreseen in the text of the legislation itself.
In EMDN the Most Detailed (Terminal) Term Is Selected
There is no freedom of choice in EMDN; the system always asks for the lowest level. The third sub-item of sub-item (ç) of the fourth paragraph of Article 27 of the Guide states that the most appropriate code for the device is selected from the "Select EMDN Term" screen and that the most detailed code appropriate to the device and the terminal term (the lowest level according to the seven-level tree-like hierarchy model) is always selected as the EMDN code.
The fifth sub-item makes this rule valid in the face of the document as well. Even if the documents containing the code carry a higher-level code and terminal term, the most detailed EMDN code related to the EMDN code in the relevant document and appropriate to the device is selected for the field. The ninth sub-item clarifies the system's side: only the most detailed EMDN codes and terminal terms defined at the official link are added to ÜTS; less detailed (higher-level) codes are not added.
Entering a higher-level code just because it is written on the certificate is therefore not an accepted path. The code on the certificate is the starting point; what is entered is the terminal term linked to that code and suited to the device.
The EMDN Seven-Level Hierarchy and Free Access
The structure of EMDN is tree-shaped. The second sub-item of sub-item (ç) of the fourth paragraph of Article 27 of the Guide calls this structure a "seven-level tree-like hierarchy model" and refers to Annex-22 of the Guide for the basic explanations on the structure. The upper levels show broad categories and the lower levels show progressively narrower product definitions; what is requested in the registration is the term at the tip of the branch.
You do not need to pay for access. The seventh sub-item of the same sub-item states that all EMDN codes can be accessed free of charge from the European Commission's webgate.ec.europa.eu/dyna2/emdn/ link. The same sub-item says that all the codes at this link are also in the "Select EMDN Term" screen in ÜTS and in the "List EMDN" screen under the "Definition" section. That is, you can verify the correct code from outside before entering it into ÜTS.
"EMDN Addition" Request
On the EMDN side too, a difference may arise between ÜTS and the source list. The eighth sub-item of sub-item (ç) of the fourth paragraph of Article 27 of the Guide regulates this case: if the EMDN code identifying the device is defined at the official link but is not defined in ÜTS, a request is opened for the addition of that code through the "EMDN Addition" field on the "Report Request" screen in ÜTS.
The acceptance condition is the same here. If the request is found appropriate and the code is confirmed as correct and valid in the EMDN query, the code is defined in the field. The same sub-item states that only correct and valid EMDN codes are defined in ÜTS and that in EMDN queries the data at the Commission's link is accepted as correct and valid.
Every Device Has Only One EMDN Code
The single-code rule applies to EMDN as well. The fourth sub-item of sub-item (ç) of the fourth paragraph of Article 27 of the Guide and the fourth sub-item of sub-item (ç) of the fourth paragraph of Article 30 say that each device has only one EMDN code.
This should be read together with the single-code rule in GMDN. A device record has one GMDN code and one EMDN code; the two are not alternatives to each other but two separate fields of the same record. If your device falls under two different EMDN terminal terms, this is often a sign that two separate products have been gathered in a single record.
The Role of GMDN in Application Grouping
GMDN is not merely an identification field; it also determines how the application file is grouped. The seventh paragraph of Article 40 of the Guide states that in device applications under the old Medical Device Regulations, applications are allowed only for devices linked to the same GMDN code.
The operational counterpart of this is as follows: if you want to bring a product group under MDD, AIMDD or IVDD together in a single application, the GMDN code of all devices in that group must be the same. Devices falling under different GMDN codes cannot be combined in the same application and are split into separate applications. For companies that register in bulk, the application plan is therefore built according to the GMDN code.
GMDN or EMDN Change: Always Agency Approval
Changing these fields after the registration is complete is not an ordinary update. Sub-item (e) of the fourth paragraph of Article 43 of the Guide states that if the request concerns the change of fields requiring the Agency's assessment such as "Class", "GMDN" and "EMDN", the request will be submitted to the Agency's assessment in "Under Review" status. Sub-item (d) of the same article says that for fields other than these, if the relevant companies accept unanimously, the request moves directly to "Accepted" status. The distinction is clear: these three fields are not closed by agreement between companies.
The seventh paragraph of the same article makes the rule absolute: data change requests concerning fields requiring the Agency's assessment such as "Class", "GMDN" and "EMDN" are submitted to the Agency's assessment and approval in every case mentioned in the fourth, fifth and sixth paragraphs of the article.
The eighth paragraph lists what the assessment is based on: the provisions in the regulation covering the device and in the Guide, the documents and device notification records of the device in ÜTS, the guides 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 image records submitted with the request. This list also tells you what evidence to attach to a change request.
Where Does the Terminology Appear in the Regulation?
The starting point of the "GMDN was abolished" claim is often Article 26 of the Medical Device Regulation. The title of the article is "Medical device terminology" and its text says: manufacturers and other natural or legal persons required to use the European database on medical devices (EUDAMED) under this Regulation use the terminology provided free of charge by the Commission.
The scope of the article must be read carefully. The provision regulates that those required to use EUDAMED will use the terminology provided free of charge by the Commission. There is no statement in the text that GMDN has been abolished, that it will no longer be requested in ÜTS or that EMDN has taken the place of GMDN. The situation on the ÜTS side is seen in the list in the seventh paragraph of Article 44 of the Guide: GMDN and EMDN stand side by side in the same list as two separate data fields.
GMDN and EMDN Comparison
The comparison below summarizes the provisions given on the page. Each line is based on the relevant article in the Guide.
Definition: GMDN is defined as the Global Medical Device Nomenclature in sub-item (ö) of the definitions article of the Guide. EMDN is defined as the European Medical Device Nomenclature (Terminology) in sub-item (k) of the same article.
Mandatory status: GMDN is a mandatory field on all three registration screens under the fourth paragraphs of Articles 25, 27 and 30. EMDN is a conditional field under sub-items (ç) of the fourth paragraphs of Articles 27 and 30: mandatory if the code appears in at least one of the documents, otherwise optional until the Agency takes a new decision.
In which registrations it is requested: GMDN is requested in SİP registrations as well as medical device registrations under Articles 26 and 28. The EMDN field is regulated on the MDR and IVDR device registration screens in Articles 27 and 30.
Source database: in GMDN queries the data of the GMDN Agency is accepted as correct and valid. In EMDN queries the data at the Commission's webgate.ec.europa.eu/dyna2/emdn/ link is accepted as correct and valid; these codes are accessed free of charge.
Structure and selection level: in GMDN the single term identifying the device is selected and the description of the code must be consistent with device characteristics such as single-use and sterile. In EMDN the lowest level according to the seven-level tree-like hierarchy model, that is the most detailed code and terminal term, is selected.
Single-code rule: each device has only one GMDN code. Each device has only one EMDN code. The two rules apply independently of each other.
If the code is not in ÜTS: for GMDN a request is opened from the "GMDN Addition" field on the "Report Request" screen, and for EMDN from the "EMDN Addition" field on the same screen. In both, the request must be found appropriate and the code must be confirmed as correct and valid.
Role in application grouping: in device applications under the old regulations, under the seventh paragraph of Article 40, an application can be made only for devices linked to the same GMDN code. No such grouping rule is regulated for EMDN.
Change procedure: both are fields submitted in every case to the Agency's assessment and approval under the seventh paragraph of Article 43; they are not corrected automatically by agreement between companies.
Code selection is one of the most expensive steps of the registration process to correct afterwards. A wrong GMDN code spoils not only one field but also the application grouping linked to that code; an EMDN term selected at the wrong level can be corrected after registration only with a data change request approved by the Agency. The codes should therefore be verified together with the document side while drawing up the product list: the code in the certificate and declaration of conformity, the code from the manufacturer and the code defined in ÜTS should be compared at the same table.
Companies can also carry out this work by opening user authorization to a consultant from their own ÜTS company page. The consultant does the code matching with the "Medical Device Registration Officer" authorization, opens the necessary "GMDN Addition" and "EMDN Addition" requests and creates the device records; the person who signs the application electronically remains the company's authorized signatory, and responsibility for the accuracy of the data remains with the company.
If you also place your device on the EU market, you can take a look at our English guide on the EMDN code.
