EMDN and GMDN Code Determination: For ÜTS Product Registration
We extract GMDN, EMDN and branch type codes from your documents and check them against the ÜTS registration Guide.

EMDN and GMDN Code Determination Service
We extract the GMDN code, the EMDN term and the ÜTS branch type of your medical device from your documents, check them against the ÜTS registration rules, and make them ready for registration. If the code is written in the document, we take it as the basis; if it is not, we determine together the code coming from the manufacturer or the most suitable code that describes the device. For each device we deliver a table showing where the code came from and which rule it rests on. To start, send your declaration of conformity, your certificate if any, and your device list; you can use our price quote form.
Who it is for
- Importers: those who carry the codes in the foreign manufacturer's documents into the ÜTS product registration and whose application came back because of a code mismatch
- Domestic manufacturers: those who will write the EMDN and GMDN code in a declaration of conformity for the first time
- Manufacturers who will register devices in EUDAMED: those who want consistent terminology in ÜTS and EUDAMED for the same device
- Companies that will register many products in bulk in ÜTS: those who want the codes checked one by one on each row
- Manufacturers who will renew the declaration of conformity: those who want the code in the declaration to stay the same as in the ÜTS records
Legal basis
Which terminology manufacturers who use EUDAMED will use is written in the Medical Device Regulation:
"Manufacturers and other natural or legal persons required by this Regulation to use the European database on medical devices (EUDAMED) shall use the terminology provided free of charge by the Commission." (Medical Device Regulation Art. 26/1)
Which GMDN code is selected in ÜTS is determined by the TİTCK ÜTS registration Guide. The rule for registering a device under the MDR is as follows:
"If the GMDN code describing the device appears in at least one of the documents of the device (EU certificate, EU Declaration of Conformity), the GMDN code stated in that document or those documents is selected in this field." (Guide on the Registration Processes of Medical Devices in the Product Tracking System, TCKKD-KLVZ-03, Art. 27/4-b-3)
The description of the code and the characteristics of the device must also match:
"Consistency is mandatory between the information in the description of the GMDN code to which the device is matched and product characteristics such as whether the device is single-use and/or sterile." (TCKKD-KLVZ-03 Art. 27/4-b-5)
For EMDN too, the code written in the document is decisive:
"If the EMDN code describing the device appears in at least one of the documents of the device (EU certificate, EU Declaration of Conformity), it is mandatory to select in this field the most detailed code and terminal term of the EMDN code stated in that document or those documents." (TCKKD-KLVZ-03 Art. 27/4-ç-5)
The same rules are in Article 30 of the Guide for registering devices under the IVDR, and for GMDN and branch type for registering devices under the older regulations in Article 25.
Three fields in ÜTS: GMDN, EMDN and branch type
The Classification Information section of the ÜTS product registration has three terminology fields. All three describe the same device, but each has its own rule.
- GMDN: a mandatory field, and each device has only one GMDN code (Art. 27/4-b-1, b-2). If the code is not in the document, the code obtained from the manufacturer is selected, and if there is none, the most suitable code describing the device (Art. 27/4-b-4). In code queries, GMDN Agency data is the basis (Art. 27/4-b-8).
- EMDN: if the code is written in the document, selecting it is mandatory; if it is not in the document, it is optional until the Agency takes a new decision (Art. 27/4-ç-1). Each device has a single EMDN code and the most detailed code and terminal term is always selected; higher-level codes are not added to ÜTS (Art. 27/4-ç-3, ç-4, ç-9).
- Branch type: a mandatory field. If there is no option that describes the device exactly, the branch type that describes it most suitably is selected (Art. 27/4-c-1, c-2).
We explain what these fields mean on our page on the GMDN and EMDN code in ÜTS, and where to find the EMDN code in the question how to select an EMDN code. This page is the service of determining and checking the codes for your device.
The same code in ÜTS and EUDAMED
When registering a device in EUDAMED, one of the basic data elements entered in the UDI database is the medical device terminology code; Annex VI Part B of the Medical Device Regulation lists this code with reference to Art. 26. The ÜTS Guide also defines EMDN as the terminology to be used in registering devices in EUDAMED and ÜTS (Art. 27/4-ç-2). For this reason, the EMDN code of the same device in EUDAMED and in ÜTS must be the same.
When the two records are made at different times by different people, the codes often diverge. We prepare the code table as a single source; the declaration of conformity, the ÜTS record and the EUDAMED record are all fed from the same table. For the EUDAMED record itself, see our EUDAMED registration consultancy page.
Code checks in bulk registration
When many products are registered in ÜTS with a bulk file, a code error repeats not in one row but in all rows of the same family. In the bulk file we compare the GMDN, EMDN and branch type code of each row with the document it is tied to. We check that the codes of devices tied to the same document are consistent with each other, and that devices tied to different GMDN codes are handled separately. Before the file goes to ÜTS, we filter out errors originating from codes.
Not to be confused with classification
GMDN and EMDN name what the device is; they do not determine the risk class. The risk class is determined by the classification rules of the regulation and is a separate field in ÜTS. For class determination, see our medical device classification consultancy page; the code determination service does not change the class, it takes the class written in the document as the basis.
What we check
- That the GMDN and EMDN codes written in the declaration of conformity and the certificate are the same as each other and as the code to be entered in ÜTS.
- If the EMDN code in the document is at a higher level, that the most detailed terminal term related to that code and suitable for the device is selected (Art. 27/4-ç-5).
- That the single-use and sterile information in the GMDN description is consistent with the device's label, instructions for use and the other fields in ÜTS.
- If the GMDN description of a reusable device contains a single-use statement, that the relevant field in ÜTS is marked according to the Guide (Art. 27/4-b-6).
- If devices of the same family are tied to different GMDN codes, that the applications are separated accordingly.
- That the branch type matches the intended purpose of the device.
We do not change the code in the document
We do not change the code written in the document with our own interpretation. If we see a mismatch between the code in the document and the device, we write it to you with the reasoning; the correction is made in the manufacturer's document and the code in the document is entered in ÜTS. We do not fill in by guess a GMDN code that we cannot verify.
Rejection reasons we encounter in ÜTS
- The EMDN code was written in the declaration of conformity but the EMDN field in the ÜTS record was left empty. We have seen many rejections for this reason; if the code is in the document, it is also in the ÜTS record.
- A higher-level code was entered in the EMDN field instead of the detailed terminal term of the code in the document.
- The GMDN description described a single-use device while the device was reusable, or the sterile status did not match.
- The GMDN code in ÜTS was different from the code in the declaration of conformity.
We explained an example of a rejection originating from GMDN on our page on devices tied to different GMDN codes.
If the code is not defined in ÜTS
If the GMDN code or branch type describing the device is not defined in ÜTS, a GMDN Addition or Branch Type Addition request is opened from the Report Request screen in ÜTS (Art. 27/4-b-7, c-3). If the EMDN code is in the European Commission's EMDN list but not in ÜTS, an EMDN Addition request is opened from the same screen (Art. 27/4-ç-8). We prepare the text of the request and write its reasoning with the Guide article.
Process
- You send the declaration of conformity, the certificate if any, the device list, and the label and instructions for use.
- For each device we extract the codes written in the documents; if there is no code in the document, we ask for the information from the manufacturer.
- We check the codes against the rules of the ÜTS registration Guide and list the mismatches with their reasoning.
- We send the code table and obtain your or the manufacturer's approval.
- If the ÜTS registration is with us, we enter the codes into the record ourselves; if needed, we open the Report Request application.
Deliverables
- A code table by device: GMDN code and term, EMDN code and terminal term, branch type, the source of each code and the Guide article it rests on.
- A list of the mismatches we see between the document and the device, and the text of the correction request to be sent to the manufacturer.
- If needed, the ÜTS Report Request text.
- If bulk registration will be made, the ÜTS bulk registration file with the codes processed.
What we need from you
- The declaration of conformity, signed and in its current version.
- The certificate, if a notified body is involved.
- The device list: product name, model or reference number, risk class.
- The label and instructions for use, to check the single-use and sterile information.
- The GMDN and EMDN code information, if the manufacturer has it.
Out of scope
- Notified body conformity assessment and CE certification.
- Testing and laboratory processes, including laboratory selection and test arrangement.
- Interpreting or changing your technical specifications.
- Finding an importer or distributor.
Related services
- ÜTS Product Registration Consultancy
- EUDAMED Registration Consultancy
- MDR and IVDR Declaration of Conformity Preparation
Frequently asked questions
Is the EMDN code mandatory in ÜTS?
If the EMDN code is written in the device's declaration of conformity or EU certificate, yes; it is mandatory to select it with the most detailed code and terminal term. If it is not in the document, it is optional until the Agency takes a new decision (TCKKD-KLVZ-03 Art. 27/4-ç-1, ç-5).
Can a device have more than one GMDN code?
No. According to the Guide, each device has only one GMDN code and only one EMDN code (Art. 27/4-b-2, ç-4).
What is done if there is no GMDN code in the document?
The GMDN code obtained from the manufacturer is selected. If the manufacturer has no GMDN code, the most suitable code describing the device is selected (Art. 27/4-b-4). In this case we determine the code together and write the reasoning in the table.
If the code in the document looks wrong to us, do you change it?
No. We do not change the code written in the document. We report the mismatch with the reasoning, and the correction is made in the manufacturer's document.
What is the difference between GMDN and EMDN?
In the Guide, GMDN is defined as the Global Medical Device Nomenclature, and GMDN Agency data is the basis in code queries. EMDN is the European terminology used in registering devices in EUDAMED and ÜTS. We explained the differences on our glossary page.
By what is the branch type selected?
The branch type that describes the device exactly is selected; if there is no exact match, the one that describes it most suitably is selected. If there is no suitable branch type, a Branch Type Addition request is opened in ÜTS (Art. 27/4-c-2, c-3).
Do the same rules apply to IVD devices?
Yes. Article 30 of the ÜTS registration Guide, which regulates the registration of devices under the IVDR, sets the same rules for the GMDN, branch type and EMDN fields. For IVD devices too, the code in the document is the basis.
Do we have to give you the ÜTS record for code determination too?
No. You can also take only the code table; your own team makes the record. If you give us the ÜTS record, we enter the codes into the record ourselves.
