top of page

ÜTS Document Application: Status Flow and the Class-Based Document Set

ÜTS document registration and device registration are separate applications. Document type selection, application type, the first registration and update flow, statuses, and class-dependent document business rules.

You have a folder from the manufacturer: a certificate, a declaration of conformity, instructions for use, an ISO certificate and a distributorship letter. You log in to ÜTS, open the device registration screen, and nothing is listed in the "Documents" field. The system is not at fault: on the device registration screen only documents that have previously been registered through a separate application and have reached "Registered" status are visible. That is, in ÜTS there is a document registration process that has to be completed before the device registration, with its own application type, its own chain of statuses and its own quantity limit.

This page describes that process as a flow from start to finish: how the decision on which document type to select is made, what the application type is determined by, what the difference is between first registration and update, which statuses the application passes through, what a document business rule means, and where the required document set changes according to the class of the device. We do not go into the details of each class; what is described here is the skeleton of the process, which works the same way for every class.

The source is 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). In places reference is also made to the Medical Device Regulation (Tıbbi Cihaz Yönetmeliği) published in the Official Gazette No. 31499 (bis) of 2/6/2021.

Document registration and device registration are two separate applications

This is the first point that confuses the process. Article 39(1) of the Manual says that an application must be made to the Agency for the assessment, according to the relevant medical device legislation and the provisions of the Manual, of document registration or update notifications made as stated in Articles 8, 9, 12, 13, 15, 16, 18, 19, 21, 22 or 23 of the Manual. This is the document application.

Article 40(1) of the Manual, on the other hand, describes an entirely different application: after the information required for the device registration notification has been added or updated in ÜTS as stated in Articles 25 to 33, 37 and 38 of the Manual, a device application must be made so that the medical devices that are ready for application reach "Registered" status in ÜTS. The two run from separate screens, receive separate numbers and are assessed separately.

The link between the two applications is one-way. Article 66(1) of the Manual says that, for a device registration notification under the MDR, according to the type and risk class of the device, the appropriate one or ones of the documents that are in "Registered" status in ÜTS as a result of the application made under the provisions of Article 39 must be linked to the device. The document comes first. If you start the device registration before the document registration is complete, the point to which you can progress ends at the "Documents" field.

The practical consequence concerns planning: you put in order not your device portfolio but your document portfolio. There may be hundreds of devices tied to the same declaration and the same certificate; all of them wait behind a single document registration.

The choice of document type is the decision that starts the process

ÜTS processes a document by its type, not by its name. Article 66(1) of the Manual lists the documents that can be linked under the MDR as the documents mentioned in Articles 7, 11, 17, 20, 22, 23 and 24 of the Manual; respectively, the EU Certificate (MDR/IVDR), the EU Declaration of Conformity (MDR/IVDR), the Instructions for Use, the Quality Management Document - ISO-13485, the Domestic Goods Certificate, the Authorised Distributorship Document and the Catalogue. Article 67(1) of the Manual gives the same list of articles for the IVDR.

On the old regulations side the list differs in two articles. Article 63(1) of the Manual lists the documents to be linked under the MDD as the documents mentioned in Articles 6, 10, 17, 20, 22, 23 and 24 of the Manual. Here Article 6 (EC Certificate) takes the place of Article 7, and Article 10 (Declaration of Conformity) takes the place of Article 11. Article 64(1) of the Manual repeats the same list for the AIMDD, and Article 65(1) for the IVDD.

So the first question is not "what class is my device" but "under which regulation was this document issued". If the regulation reference on the document is read wrongly, the wrong type is selected; once the wrong type is selected, the application type and the list of mandatory fields also run wrongly.

Some types have their own internal rules, and these should be known at the start of the process, not at the end. Article 20(5) of the Manual says that, for documents of the Quality Management Document - ISO-13485 type, the validity period cannot be more than 3 years. Article 24(2) of the Manual puts catalogues in a place of their own: uploaded catalogues are recorded in ÜTS without being subject to checking by the review expert. Article 23(1) of the Manual defines the Authorised Distributorship Document as a document issued by the manufacturer of the device on behalf of importer firms operating in our country; that is, this document does not belong in the own record of a domestic manufacturer.

The application type defines the firm's position, not the document

The step after choosing the document type is the application type, and the most common mistake here is trying to choose the application type according to the content of the document. Article 39(2) of the Manual says that, to make a document application, the "Create Document Application" ("Belge Başvurusu Oluştur") field on the "Document Application Procedures" ("Belge Başvuru İşlemleri") screen under the "Document" tab in ÜTS is entered; paragraph 3 says that the application type is selected from the list in the "Application Type" ("Başvuru Tipi") field on this screen.

Article 39(4) of the Manual lists the existing application types. Point (a) of the same paragraph defines "Document Application for Importer Firms" ("İthalatçı Firmalar için Belge Başvurusu"), point (b) "Document Application for Importer or Manufacturer Firms for other types (Instructions for Use, Intended Purpose Form, Quality Management Document - ISO13485, Domestic Goods Certificate, Authorised Distributorship Document)", point (c) "E-signed Document Application for Manufacturer Firms" ("İmalatçı Firmalar için e-imzalı Belge Başvurusu"), and point (ç) "Document Application under Announcement No. 2023/KK-1" ("2023/KK-1 Sayılı Duyuru Kapsamında Belge Başvurusu").

Which document type goes to which application type is written in the following paragraphs of the same article. Paragraph 5 says that the type in point (a) is selected for the document types mentioned in Articles 8, 12 and 15 of the Manual; these are importer firms' notifications of certificates, declarations of conformity and system and procedure pack declarations belonging to a foreign manufacturer. Paragraph 6 ties the document types mentioned in Articles 18, 19, 21, 22 and 23 of the Manual to the type in point (b). Paragraph 7 says that the type in point (c) is selected for the document types mentioned in Articles 9, 13 and 16 of the Manual; and paragraph 8 says that the type in point (ç) is used in the document applications mentioned in Articles 47 and 50 of the Manual.

When this mapping is read, the table becomes clear: types (a) and (c) are separated by who registers the same document. If an importer is registering a declaration of conformity belonging to a foreign manufacturer, type (a) is selected; if a domestic manufacturer is registering its own declaration, type (c) is selected. Type (b), on the other hand, collects supporting documents regardless of type and is open to both importers and manufacturers.

If the choice is made wrongly the system warns you but does not explain the reason. Article 39(9) of the Manual says that, after the application type is selected, documents are selected from the "Select Document" ("Belge Seç") screen in the "Documents to be Added to the Application" ("Başvuruya Eklenecek Belgeler") field on the same screen, and that only documents suitable for the selected application type are listed on this screen. That is, if the document you are looking for does not appear in the list, in most cases the document is not missing; the application type is wrong.

First registration notification and update notification share the same flow

The Manual describes document operations from start to finish with the pair "first registration or update notification". Article 8(1) of the Manual lists what importer firms will upload to the "Original Document" ("Orijinal Doküman") field in first registration or update notifications relating to the EC Certificate or the EU Certificate (MDR/IVDR) belonging to a foreign manufacturer. Article 12(1) of the Manual uses the same expression for declarations of conformity, and Article 23(4) of the Manual for the Authorised Distributorship Document.

The meaning of this expression is this: an update does not create a new document in ÜTS; it is a notification made on top of the existing document record; but it requires a new document application of its own. Article 8(6) of the Manual says that, for the assessment of applications created under the provisions of Article 39 for the document registration or update notifications mentioned in paragraphs 1 to 4, there is no need to physically send the uploaded documents to the Agency, and that making a registration or update application through ÜTS is sufficient. Article 12(4) of the Manual and Article 13(1)(e) of the Manual repeat the same result for declarations.

The most common reason for an update notification is a change in the document itself: a certificate revision, an extension of scope, a change in the manufacturer's address. Article 20(2) of the Manual says that, if the quality management document has been revised, the revision date will be entered as the "Document Start Date" ("Belge Başlangıç Tarihi"); if the document has not been revised and the start date is not clearly stated in the document, the most recent issue date will be entered. Paragraph 3 of the same article says that, where the revision number is stated next to the certificate number, the document number will be recorded together with the revision number. If you do not apply these rules in an update notification, a single document ends up looking like two different document records in the system.

The statuses an application passes through are a fixed chain

After the documents are selected, the application does not go to the Agency in a single move. Article 39(10) of the Manual says that the selected documents are listed under the "Documents to be Added to the Application" field and that, if a wrong document has been selected, it can be removed from the list with the "Remove" ("Çıkar") button. Paragraph 11 of the same article says that, when the set in the list is complete, the "Create Application" ("Başvuru Oluştur") button is pressed and the "Approve" ("Onayla") operation is carried out on the resulting "Document Application Summary" ("Belge Başvurusu Özeti") screen; and that only users of the relevant firm of the "Medical Device Registration Operator" ("Tıbbi Cihaz Kayıt Elemanı") type can carry out this operation.

Paragraph 12 of the same article sets the first checkpoint: if there is no situation contrary to the procedure and business rules in the document notifications of the application, the application is created in "Awaiting Signature" ("İmza Bekliyor") status. The negative reading of this sentence is important. If there is a violation, the application is not formed in this status at all; that is, it is not rejected and does not go to the Agency either; it stays with you.

Paragraph 13 defines the signature step: an application in "Awaiting Signature" status is electronically signed by the applicant signatory of the firm. Point (a) of the same paragraph says that applications containing document types mentioned in Articles 6, 7, 10, 11 and 14 of the Manual move to "Awaiting Payment" ("Ödeme bekliyor") status after being signed, and, for documents subject to a payment requirement, move to "Under Review" ("İncelemede") status after the application fee is paid and approved. Point (b) of the same paragraph says that documents other than these document types move directly to "Under Review" status the moment the application is electronically signed.

At the end of the chain there is the single sentence of paragraph 14: applications that do not reach "Under Review" status cannot be assessed by the Agency's review expert. Since a payment step enters in applications containing certificates, declarations of conformity and system and procedure pack declarations, assuming that a signed application is visible at the Agency is a frequent misconception.

The volume limit is also part of this flow. Article 39(15) of the Manual says that a document application contains at most 5 document notifications; Article 8(7) and Article 12(5) of the Manual repeat the same limit for their own document types. A set of twenty documents means at least four applications, and all of them have to reach "Registered" status separately.

The document business rule is the link between the class and the document set

"Document business rule" ("belge iş kuralı") is ÜTS's own term and refers to the set of rules that determines which documents will be linked to which device. Article 66(2) of the Manual says that the linking under the MDR is carried out in ÜTS according to the type and risk class of the device and according to the document business rules determined on the basis of the conformity assessment procedures mentioned in Article 61 of the Manual. Article 67(2) of the Manual ties the same structure for the IVDR to the procedures in Article 62 of the Manual.

The same logic works in the old regulations. Article 63(2) of the Manual ties the MDD linking to the procedures in Article 58 of the Manual, Article 64(2) ties the AIMDD linking to the procedures in Article 59, and Article 65(2) ties the IVDD linking to the procedures in Article 60.

The rule that follows is this: the document set ÜTS asks of you is not arbitrary; it is the reflection in ÜTS of the conformity assessment procedure of the device. Adding a document because "we have it, let's add it", and saying "we don't have it, let's skip it", are equally useless; the business rule looks for the document it looks for.

The running set of business rules changes as the class changes

The Manual shows a separate annex for each class group, and the class selection directly determines which annex will run. On the MDR side, Article 66(3) of the Manual says that the appropriate one of the business rules shown in Annex-88 will run for devices to be notified as "Class-I Other", "Class-Is", "Class-Im" or "Class-Ir"; paragraph 4 points to Annex-89 for "Class-IIa", and paragraph 8 to Annex-93 for "Class-III". There is no single annex for Class IIb; paragraphs 5, 6 and 7 of the same article direct to three separate annexes according to whether the device is implantable and whether it falls under MDR Annex VIII Rule-12.

On the IVDR side the distinction multiplies further. Article 67(3) of the Manual points to Annex-94 for "Class A" or "Class A Sterile"; paragraph 4 to Annex-95 for "Class B" or "Class C"; and paragraph 5 to Annex-96 for "Class D". Paragraphs 6, 7, 8 and 9 of the same article tie the groups of self-testing devices, near-patient testing devices and companion diagnostic devices, together with their classes, to separate annexes.

In the old regulations the grouping is coarser. Article 63(3) of the Manual gathers "Class-I Other", "Class-Is", "Class-Im" and "Class-IIa" devices under the MDD in a single annex, Annex-81; paragraph 4 points to Annex-82 for "Class-IIb" and paragraph 5 to Annex-83 for "Class-III". Article 64(3) of the Manual says that all devices under the AIMDD are classified in ÜTS in the same risk group as devices classified as Class-III under the MDD; paragraph 4 points to Annex-84 for them.

The most concrete provision showing where the set narrows is inside the declaration. Article 11(2)(ı) of the Manual asks that, in all EU declarations of conformity other than those whose scope covers only Class-I Other or Class A devices, the name and identification number of the notified body and the identification of the EU certificate or certificates issued be present. That is, in the only group where the notified body does not come into play, the declaration stands on its own; in all other groups the declaration refers to a certificate, and that certificate has to be recorded separately as well.

Another document added as the class rises is the instructions for use. The first sub-point of Article 17(2)(a) of the Manual says that, for Class-III and Class-IIb devices certified under the MDR and MDD, uploading to ÜTS the instructions for use issued by the manufacturer is mandatory. In terms of process, this means that in these classes the number of document applications rises by one item from the very start.

The device registration does not move forward until the documents are registered

The document-facing side of the device registration screen is described in Article 27(5) of the Manual. Sub-point (1) of point (a) of the same paragraph says that selecting the "Documents" field in ÜTS is a mandatory field; sub-point (2) says that the documents that must be added according to the appropriate one of the document business rules mentioned in Article 66 of the Manual, in line with the risk class of the device, will be selected from among the documents already in registered status in ÜTS as a result of the application made under Article 39 of the Manual. Sub-point (3) adds a sequence condition: before document selection in this field, it is mandatory that the class of the relevant device has been selected on the ÜTS registration screen, and the selection is made from the documents that can be selected according to the class of the device.

Article 30(5)(a) of the Manual repeats the same three rules for the IVDR registration screen, with reference to the business rules in Article 67 of the Manual. Article 25(5)(a) of the Manual ties the same structure for the old regulations to Article 63, 64 or 65 of the Manual.

The last link of the chain is the Basic UDI-DI. The first sub-point of Article 27(5)(c) of the Manual says that selecting this field is mandatory; the third sub-point says that, before making a selection on the "Select Basic UDI-DI" ("Temel UDI-DI Seç") screen, selecting from the "Documents" field, according to the business rule in Article 66 of the Manual, the documents associated with the device and with the device's Basic UDI-DI, that is, the EU Declaration of Conformity and the EU Certificate, is mandatory. The fourth sub-point says that through this screen a selection can be made only from among the Basic UDI-DI numbers associated with the selected EU Declaration of Conformity, and that more than one selection cannot be made in this field. Article 30(5)(c) of the Manual sets up the same order for the IVDR.

For this reason the approach "let's enter the device first and add the documents later" does not work. The document cannot be selected without the class being selected, and the Basic UDI-DI cannot be selected without the document being selected.

The device application has its own types and its own limits

After the documents reach "Registered" status and are linked to the device, the second application begins. Article 40(2) of the Manual says that the device application is made from the "Create Medical Device Application" ("Tıbbi Cihaz Başvurusu Oluştur") field on the "Medical Device Application Procedures" ("Tıbbi Cihaz Başvuru İşlemleri") screen under the "Medical Device" tab in ÜTS. Paragraph 3 of the same article lists the existing device application types: "Optical Products Application" ("Optik Ürünler Başvurusu"), "Active Implantable Medical Devices Application" ("Aktif İmplante Tıbbi Cihazlar Başvurusu"), "Class 3 Products Application" ("Sınıf 3 Ürünler Başvurusu"), "Other Products Application" ("Diğer Ürünler Başvurusu"), "Custom-Made Medical Device Application" ("Ismarlama Tıbbi Cihaz Başvurusu"), "System and Procedure Pack Application" ("Sistem İşlem Paketi Başvurusu") and "Products Under 2023/KK-1 & 2023/KK-2 Application" ("2023/KK-1 & 2023/KK-2 Kapsamında Ürünler Başvurusu").

The first step of this application is directed at the document. Article 40(5)(a) of the Manual says that the declaration linked to the relevant device is selected from the "Declaration" ("Beyan") field on the "Medical Device Application Summary" ("Tıbbi Cihaz Başvurusu Özeti") screen; point (b) says that only declarations linked to devices in "Ready for Application" ("Başvuruya Hazır") status are listed on this screen; and point (c) says that, since medical device applications can be formed only from devices linked to a single declaration, only one declaration can be selected from the list. The declaration is the roof of the device application.

The limits also vary by type. Point (ğ) of the same paragraph says that device applications of this type contain at most 500 medical device notifications; Article 40(6)(d) says that custom-made medical device and system and procedure pack applications contain at most 5 notifications. Paragraph 7 of the same article says that, in device applications under the old regulations, an application is allowed only for devices linked to the same GMDN code; paragraph 8 says that, in applications under the new regulations (except custom-made medical devices), an application can be made only for devices linked to the same Basic UDI-DI code.

The chain of statuses is similar but not the same. Article 40(5)(f) leaves the "Approve" operation again to users of the "Medical Device Registration Operator" type; point (g) says that the application is created in "Awaiting Signature" status, that it must be electronically signed by the signatory and brought to "Awaiting Payment" ("Ödeme Bekliyor") status, and that it moves to "Under Review" status once the fee is paid. While the payment step comes into play on the document side only for certain document types, in these device application types the payment step is part of the flow.

A negative decision is not the end of the process

When an application is rejected or a revision is requested, reapplying should not be the first reflex. Article 39(16) of the Manual says that, where a negative decision is given by the Agency on one or more of the notifications in a document application and this decision is thought to be contrary to the legislation and the provisions of the Manual, the firm can, before reapplying, use the "Submit Request" ("Talep Bildir") screen in ÜTS, select "Medical Device Document and Product Registration Procedures" ("Tıbbi Cihaz Belge ve Ürün Kayıt İşlemleri") as the "Request Area" and enter the relevant number in the "Medical Device/Document Application Number" ("Tıbbi Cihaz/Belge Başvuru Numarası") field, and thereby request that the decision be re-evaluated.

The same paragraph also binds the form of the request: the request must cite the legislation and/or the provisions of the Manual relating to the matter objected to; requests in which the application number is not entered, or which do not cite, are not taken into assessment. The same paragraph also says that the Agency will not be held responsible for applications that are sent for review by reapplying, without correction through the request.

Article 39(17) of the Manual defines the same route for the 3-day update period ("Request Update", "Güncelleme İste") decision. Article 40(9) of the Manual sets up the same mechanism for device applications and says that there the Device Application Number is entered in the "Medical Device/Document Application Number" field.

In applications containing certificates, the process continues even after a positive decision. Article 39(18) of the Manual says that, where an application contains notifications of the document types mentioned in Articles 6 and 7 of the Manual and the assessment ends positively, the validity and currency of the certificates that have reached registered status will be queried by the Agency through the notified body that issued the certificate or the competent authority that authorised that body. Point (a) of the same paragraph says that a 45-day revision procedure will be applied to certificates found not to be current; that, as an exception, only for EU certificates under the MDR and IVDR, and only for certificates revised because of an extension of product scope, a 120-day extension procedure will be applied instead of the 45-day revision procedure. Point (b) of the same paragraph says that a direct rejection procedure will be applied to certificates found to be invalid for reasons other than having lapsed, and that, for documents found to be forged or tampered with, a market surveillance and inspection process will also be started after the rejection. Both points say that these procedures will be carried out for all certificates registered in ÜTS with the same document number that are not current.

Firm registration and user authorisations are the precondition of the process

To make a document application, the firm must be registered in ÜTS under the right type. Article 5(1) of the Manual says that the registration to ÜTS of firms carrying out the sale and/or application of medical devices is carried out if they are authorised under the relevant legislation. Paragraph 2 of the same article says that firm registrations are made from MERSİS or VEDOP sources, and that if a firm has both a MERSİS and a VEDOP number the operation is carried out over the MERSİS number.

Paragraph 5 of the same article says that firms that will register in ÜTS under the type "Manufacturer/Importer/Dealer/Exporter" must hold a medical device sales centre licence and that the ÇKYS number must be entered as mandatory information during firm registration. Paragraph 6 of the same article says that, in firm transfer or merger operations, the signatories and users defined in ÜTS must be updated so that ÜTS activities continue; paragraph 7 says that, if the firm's responsible manager, title and address change, the changes are updated automatically in ÜTS once this information is updated in ÇKYS.

The counterpart of these paragraphs in the process is this: if the signatory is not current, the application gets stuck in "Awaiting Signature" status and the document registration is never completed.

What we do in document registration, and what we cannot do

Within medical device ÜTS registration consultancy, our concrete output in the document registration process is this:

  • Document inventory and type mapping: We map each document from the manufacturer to one of the types in Articles 6, 7, 10, 11, 17, 20, 22, 23 and 24 of the Manual, and we also notify in writing which of them has no counterpart in ÜTS.

  • Application type plan: We determine which document will go into which application type according to paragraphs 4 to 8 of Article 39 of the Manual, and we set up in advance the application groups of five documents each.

  • Business rule pre-check: We establish, according to the class of the device, which of Articles 63 to 67 of the Manual and which paragraph will run, and we report before the application any gap in the document set that business rule looks for.

  • Sequencing: We plan the steps of document application, the document reaching "Registered" status, document and Basic UDI-DI selection in the device record, and device application in line with the sequence condition in Article 27(5) of the Manual.

  • Management after the decision: In case of a negative decision or the giving of an update period, we prepare the "Submit Request" route under paragraphs 16 and 17 of Article 39 of the Manual so that it meets the citation requirement.

What we cannot do is clear as well. We cannot produce documents on your behalf: the declaration of conformity is issued by the manufacturer, the certificate by the notified body, and the instructions for use are prepared by the manufacturer. If the manufacturer does not have a document the business rule looks for, we have no solution that would close that gap; since Article 66(2) of the Manual ties the document business rule to the conformity assessment procedure, a missing document often means a missing procedure. Nor can we commit to the Agency's review result; Article 39(14) of the Manual leaves the assessment to the Agency's review expert.

The way of working is as follows: the firm defines a user authorisation for us from its own ÜTS firm page; we create the document notifications, the application groups and the device records with the "Medical Device Registration Operator" ("Tıbbi Cihaz Kayıt Elemanı") authorisation. Article 39(11) and Article 40(5)(f) of the Manual tie the "Approve" operation to this authorisation; the person who electronically signs both applications 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