
ÜTS Document Registration
I uploaded the documents, filled in the fields, saved, and I have been waiting for months. This is the most common complaint in ÜTS, and almost every time the cause is the same: the record was created, but the application was never submitted
ÜTS Document Registration and Document Application: Step-by-Step Screen Guide
I uploaded the documents, filled in the fields, saved; I have been waiting for months. This is the complaint heard most often in ÜTS, and its cause is almost every time the same: the record has been created, but the application has not been submitted. Document registration and document application are two separate procedures, and until the second is done nothing reaches the Agency.
This page explains document registration screen by screen, based on Article 39 of 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) and Articles 6 to 24, which regulate the document types: how the application type is selected, how the document fields are filled in, how the notified body is introduced to the system, and when an update notification is required.
The Difference Between "Document Registration Notification" and "Document Application"
The Manual repeats the same sentence in every article that regulates a document type. Article 8(8), which regulates certificate notifications, Article 12(6) for the declaration of conformity, Article 15(6) for the system/procedure pack (SİP) declaration, Article 18(6) for instructions for use, Article 21(10) for the ISO 13485 certificate, Article 22(10) for the domestic product certificate and Article 23(10) for the authorised distributorship certificate say that the procedures to be carried out for document registration and update applications in ÜTS are described in Article 39.
A document notification is the creation of the document's information and documents in ÜTS; a document application is the submission of these created notifications to the Agency. Article 39(1) of the Manual states this clearly: in order for document registration or update notifications to be assessed according to the relevant legislation and the provisions of the Manual, an application must be made to the Agency.
The provision that puts the distinction most harshly is Article 39(14): applications that do not reach "Under Review" ("İncelemede") status cannot be assessed by the Agency review expert. Your record is in the system and your files may be uploaded; if the application has not reached this status, nobody looks at it.
• Notification stage: The document type is selected, the fields are filled in, and the original and, where applicable, the Turkish document are uploaded.
• Application stage: The application type is selected, the documents are added to the application, the "Approve" ("Onayla") action is taken, the electronic signature is applied and, if required, the fee is paid.
• Result: Only when the second stage is completed does the application fall in front of the review expert.
Where Is a Document Application Created?
The location of the screen is described word for word in the Manual. According to Article 39(2), to make a document application, you enter the screen of the same name from the "Create Document Application" ("Belge Başvurusu Oluştur") field on the "Document Application Procedures" ("Belge Başvuru İşlemleri") screen under the "Document" ("Belge") tab in ÜTS.
Next comes selecting the application type. According to Article 39(3), the application type of the documents to be applied for is selected from the list in the "Application Type" ("Başvuru Tipi") field on the "Create Document Application" screen. Then, under Article 39(9), the documents are selected from the "Select Document" ("Belge Seç") screen in the "Documents to Be Attached to the Application" ("Başvuruya Eklenecek Belgeler") field on the same screen.
The same paragraph says that only documents suited to the type selected in the "Application Type" field are listed on the "Select Document" screen. If you selected the wrong type, the document you are looking for does not appear in the list at all; the system gives no error message, the document is simply not there. Under Article 39(10), a document selected by mistake can be removed from the list by pressing the "Remove" ("Çıkar") button.
Four Document Application Types and the Right Choice
Article 39(4) of the Manual lists the four document application types currently in the list. Choosing the right type is the first decision that determines the whole process, because the type determines which document types will be listed and which additional fields will open.
• Document Application for Importer Firms: The type under which the importer notifies the certificates and declarations of the foreign manufacturer.
• Document Application for Other Types for Importer or Manufacturer Firms: The type used for Instructions for Use, Intended Purpose Form, Quality Management Certificate (ISO 13485), Domestic Product Certificate and Authorised Distributorship Certificate.
• e-Signed Document Application for Manufacturer Firms: The type used by domestic manufacturers for documents belonging to their own products.
• Document Application under Announcement No. 2023/KK-1: The type under which certificates that have received transition period extension approval are notified.
The entry into force of this paragraph is tied to a separate condition. According to Article 69(1)(a) of the Manual, the provisions in Article 39(4) enter into force together with the ÜTS Version Update through which the procedures and principles concerned become technically functional in ÜTS; the Manual does not state the date of this update. For a period, the type list you see on the screen and the list you read in the Manual may differ.
"Document Application for Importer Firms"
According to Article 39(5) of the Manual, in applications for the document types mentioned in Articles 8, 12 and 15 of the Manual, the type in point (a) of paragraph 4 is selected as the "Application Type".
These three articles are regulated for importing firms' documents belonging to a foreign manufacturer: Article 8 covers the "EC Certificate" ("EC Sertifikası") and "EU Certificate (MDR/IVDR)" ("AB Sertifikası (MDR/IVDR)"), Article 12 covers the "Declaration of Conformity" ("Uygunluk Beyanı") and "EU Declaration of Conformity (MDR/IVDR)" ("AB Uygunluk Beyanı (MDR/IVDR)"), and Article 15 covers "SİP Declaration (MDR) (Article-22)" ("SİP Beyanı (MDR) (Madde-22)") notifications. This is the type mainly used by a firm that brings devices from abroad.
"Instructions for Use, Intended Purpose Form, ISO 13485, Domestic Product and Authorised Distributorship" Application
According to Article 39(6) of the Manual, in applications for the document types mentioned in Articles 18, 19, 21, 22 and 23 of the Manual, the type in point (b) of paragraph 4 is selected as the "Application Type".
Five document types are gathered in this one type: Article 18 regulates the instructions for use, Article 19 the intended purpose form/declaration, Article 21 the ISO 13485 quality management certificate, Article 22 the domestic product certificate and Article 23 the authorised distributorship certificate. The type's name mentions both importer and manufacturer because these documents go through the same type for both sides.
"e-Signed Document Application for Manufacturer Firms"
According to Article 39(7) of the Manual, in applications for the document types mentioned in Articles 9, 13 and 16 of the Manual, the type in point (c) of paragraph 4 is selected as the "Application Type".
This type is mandatory for domestic manufacturers. Article 9(1) of the Manual provides that, in applications made after the "EC Certificate" or "EU Certificate (MDR/IVDR)" notifications of domestic manufacturing firms for their own products, it is mandatory to apply by selecting "e-Signed Document Application for Manufacturer Firms" ("İmalatçı Firmalar için e-imzalı Belge Başvurusu") as the Document Application Type and that the option "Are you the manufacturer of the products covered by the document?" ("Belge kapsamındaki ürünlerin üreticisi firması siz misiniz?") must be selected as "Yes". The same two conditions are repeated for declarations of conformity in points (a) and (b) of Article 13(1), and for the SİP declaration in points (a) and (b) of Article 16(1).
"Document Application under Announcement No. 2023/KK-1"
According to Article 39(8) of the Manual, in the document applications mentioned in Articles 47 and 50 of the Manual, the type in point (ç) of paragraph 4 is selected as the "Application Type". Article 47 regulates ÜTS applications within the scope of the MDR transition period extension, and Article 50 those within the scope of the IVDR transition period extension.
This type has an important precondition. According to point (a) of Article 47(3) of the Manual, before a document registration/update application is made in ÜTS in order to define the MDR transition period on the EC certificate to which the devices are linked, an application for that certificate must have been made in EBS (Electronic Application System) under Article 46, and the Agency must have allowed the extension on the basis of that application. If this step is skipped, the document registration/update application made in ÜTS is rejected under the same point. After the extension approval is obtained, under point (g) of the same paragraph, "Document Application under Announcement No. 2023/KK-1" ("2023/KK-1 Sayılı Duyuru Kapsamında Belge Başvurusu") is selected as the "Application Type" at the application stage.
How Many Documents Can Be Added to One Document Application?
The limit is clear. According to Article 39(15) of the Manual, a document application contains at most 5 document notifications. The same limit is repeated in the document type articles: Article 8(7), Article 12(5) and Article 15(5) state that a document application whose procedures and principles are set out in Article 39 allows at most 5 document registration/update notifications.
For an importer with a wide portfolio this requires applications to be planned in advance. Grouping the documents by which device groups they will open makes the registration order clear: once which documents are completed, which device registration can I start?
Who Does the "Approve" Action, Who Signs?
Creating the application and signing it are the work of two different people. According to Article 39(11) of the Manual, if all the documents that must be in the application are in the "Documents to Be Attached to the Application" list, the "Create Application" ("Başvuru Oluştur") button is pressed and the "Approve" action is taken on the "Document Application Summary" ("Belge Başvurusu Özeti") screen that appears. The same paragraph states that only the firm's users of the "Medical Device Registration Operator" ("Tıbbi Cihaz Kayıt Elemanı") type can perform this action.
An approved application is not yet considered to have gone to the Agency. According to paragraph 12, if there is nothing contrary to the procedure and business rules in the document notifications of the application, the application is created in ÜTS in "Awaiting Signature" ("İmza Bekliyor") status. According to paragraph 13, an application in "Awaiting Signature" status is signed electronically by the applicant signatory of the firm.
In practice, the working model with a consultant is built on this distinction: the firm assigns the "Medical Device Registration Operator" authority to the consultant from its own page in ÜTS, the consultant creates the notifications and takes the "Approve" action, and the electronic signature step stays with the firm's signatory.
Paid Document Types and the "Awaiting Payment" Status
After the signature, the path the application follows splits in two depending on the document types it contains. According to point (a) of Article 39(13) of the Manual, among the electronically signed applications, those containing document types mentioned in Articles 6, 7, 10, 11 and 14 of the Manual move to "Awaiting Payment" ("Ödeme Bekliyor") status. The document types regulated in these articles are, respectively, the EC Certificate, the EU Certificate (MDR/IVDR), the Declaration of Conformity, the EU Declaration of Conformity (MDR/IVDR) and the SİP Declaration (MDR) (Article-22). For documents with a payment requirement, once the application fee is paid and approved, the application moves to "Under Review" ("İncelemede") status.
Point (b) of the same paragraph separates the other documents: documents other than these types move to "Under Review" status the moment the document application is signed electronically. Applications containing instructions for use, an intended purpose form, an ISO 13485 certificate, a domestic product certificate and an authorised distributorship certificate fall in this second group and do not require a separate payment step.
An application moves between three stops: "Awaiting Signature", "Awaiting Payment" where required, and "Under Review". Applications stuck at the first two stops are not assessed.
"Original Document" and "Turkish Document" Fields
There are two separate fields on the document upload screen, and what goes into these fields is regulated in detail in the Manual. According to Article 8(2), where the condition mentioned in the first paragraph exists, the complete Turkish translation of the document uploaded to the "Original Document" ("Orijinal Doküman") field, made by a sworn translator, is uploaded to the "Turkish Document" ("Türkçe Doküman") field.
Point (a) of the same paragraph draws a critical limit here: only the Turkish part of the document approved by the sworn translator is uploaded to the "Turkish Document" field. In other words, it is not correct to merge the original document and its translation into a single file and upload it to the Turkish field. According to point (b), the translation must contain the translator's name and surname, stamp/signature/seal, and the translator's declaration that the translation was made faithfully to the original document.
What is uploaded to the Original Document field depends on who issued the document and where. Article 8 of the Manual lists the following options for a certificate issued by a notified body established outside Turkey: the apostille-certified copy, the copy certified by a Republic of Türkiye embassy or consulate, the verifiable e-apostilled original and the e-signed original. Among these options there are also routes under which, if the certificate is not e-signed, a copy certified by a Turkish notary is accepted, provided that the certificate can be verified with all its pages on the notified body's official query site or in EUDAMED. Which route suits your document is examined in detail on the page that deals with translation and apostille. Paragraph 5 of the same article adds that, so that the review expert can assess the uploaded documents more easily, a searchable format is preferred.
The Right Answer to "Is the Original Document in Turkish?"
This question on the screen determines whether you will upload a translation. According to point (b) of Article 8(4) of the Manual, if the original document was prepared in Turkish or in multiple languages including Turkish, the "Is the Original Document in Turkish?" ("Orijinal Doküman Türkçe mi?") option in the system is selected as "Yes" and the upload is made only to the "Original Document" field. According to point (a) of the same paragraph, if the original document was prepared in a foreign language, the option is marked "No" and the sworn translator's translation is uploaded to the Turkish field.
The same logic is repeated for the other document types. Points (b) and (c) of Article 9(2), which regulates the certificate notifications of domestic manufacturers, Article 21(4), which regulates the ISO 13485 certificate, and Article 23(6), which regulates the authorised distributorship certificate, set the same rule: if the document is in Turkish or in multiple languages including Turkish, "Yes" is selected and the upload is made only to the original field; nothing is uploaded to the Turkish field.
The instructions for use are an exception. According to point (c) of Article 18(1) of the Manual, if the original document was prepared in Turkish by the manufacturer, the most current original instructions for use in the technical file, prepared in at least one of the official languages of the EU, are uploaded to the "Original Document" field, and the most current instructions for use in the technical file prepared in Turkish are uploaded to the "Turkish Document" field. The same point also states that Turkish is not an official language of the EU.
Document Start Date and Revision Number Entry
There are two fields that produce the most mismatches during review: the document start date and the document number.
• If the document has been revised: According to Article 6(4) of the Manual, if the document has been revised, the revision date is entered as the document start date. The same rule is repeated in Article 7(4) for EU certificates and in Article 20(2) for the ISO 13485 certificate.
• If the document has not been revised and no date is stated explicitly: According to the same paragraphs, the most current issue (signature) date on the certificate is entered as the document start date.
• If there is a revision number: According to Article 6(5) of the Manual, where the revision number is stated on the EC certificate and shown together with the document number, the certificate is recorded together with its revision number. The example format given in the Manual is XXXXX.Rev.1. The same rule is found in Article 7(5) for EU certificates and in Article 20(3) for the ISO 13485 certificate.
A record that skips these three rules causes the information in the document and the information in the system to diverge, and it comes back at the review stage.
All Annexes and Additional Pages of the Document Must Be Uploaded
The Manual repeats the requirement of complete upload in four separate document types with almost the same sentence. According to Article 6(6) of the Manual, the EC certificate must be uploaded and submitted to the Agency completely, together with all its annexes and additional pages. The same requirement is found in Article 7(6) for the EU certificate, in Article 10(7) for the declaration of conformity, in Article 11(6) for the EU declaration of conformity and in Article 20(4) for the ISO 13485 certificate.
In the field, where this requirement is violated most is the annex lists of certificates. When the cover page is uploaded and the annex pages showing the product scope are skipped, it becomes impossible to link the device to the document.
If the Notified Body Is Not Defined in ÜTS: NANDO and "Report Request"
If the body that issued the certificate is not defined in the system, you cannot start the document registration. According to Article 6(7) of the Manual, if the notified body that issued the EC certificate is not defined in ÜTS as a notified body, then before the ÜTS document registration procedures for that certificate, a request is opened through the "Notified/Conformity Assessment Body Procedures" ("Onaylanmış/Uygunluk Değerlendirme Kuruluş İşlemleri") field, using the "Report Request" ("Talep Bildir") screen in ÜTS, for the body to be added to ÜTS or for authority to be defined under the relevant legislation.
How the request is concluded is written in the same paragraph. If, as a result of queries made on the "NANDO Notified Bodies" query site pursuant to the request, it is established that the conformity assessment body concerned has been designated as a notified body, the body is added to ÜTS and defined according to the Old Medical Device Regulations under which it was designated. For EU certificates the same process is regulated in Article 7(7); there the body is defined according to the New Medical Device Regulations under which it was designated.
A subtle point follows from this: because the body definition is regulation-based, even if the body is registered in ÜTS, its authority may not be defined for the regulation to which your document belongs. Seeing "the body exists in the system" is not a sufficient check on its own.
The Information Entered in ÜTS Must Match the Document
For each document type the Manual lists the fields to be checked in the system, and it ends all of them with the same sentence. After listing the fields that must be on the EC certificate, Article 6(2) of the Manual says that the information entered in ÜTS and the information on the certificate must be the same. The same provision is found in Article 7(2) for the EU certificate, in Article 10(2) for the declaration of conformity, in Article 11(2) for the EU declaration of conformity, in Article 20(1) for the ISO 13485 certificate, in Article 22(4) for the domestic product certificate and in Article 23(2) for the authorised distributorship certificate.
The fields checked vary by document type. For the EC certificate they are the manufacturer's name and address, the certificate number, the name and identification number of the notified body, the regulation it belongs to, the annex under which it was issued, the document start and end dates and the product scope. For the EU certificate, additional fields are added to this list, such as the manufacturer's Single Registration Number, the Basic UDI-DI and the conditions concerning the validity of the certificate.
The Agency's Certificate Query After Document Registration
The process does not end once your document reaches "Registered" ("Kayıtlı") status. According to Article 39(18) of the Manual, if the document application contains notifications of the document types mentioned in Articles 6 and 7 and the assessment has a positive result, the validity and currency of the certificates that reach registered status are queried by the Agency through the notified body that issued the certificate or the competent authority that designated that body.
Two actions are defined depending on the result of the query. According to point (a) of the same paragraph, a 45-day revision procedure is applied to certificates found not to be up to date; as an exception, only for EU certificates under the MDR and IVDR, and only for certificates revised because of an extension of the product scope, a 120-day extension procedure is applied instead. According to point (b), certificates found to be invalid for reasons other than having lost their currency are rejected directly; for documents found to be forged or tampered with, a market surveillance and inspection process is also started after the rejection. Both actions are also carried out for all certificates registered in ÜTS that are not up to date and are associated with the same document number.
The 45 days and 120 days here are the revision and extension periods that the legislation grants to the party concerned; they are not an indicator of how long an application will take to conclude. How process follow-up is carried out is covered on our ÜTS Process Management and Follow-up page.
Are the Documents Physically Sent to the Agency?
No. According to Article 8(6) of the Manual, for the Agency to assess the document applications created under the provisions of Article 39 for document registration or update notifications, there is no need to physically send the documents uploaded to the "Original Document" and, if any, "Turkish Document" sections to the Agency. The same paragraph states that, after the relevant provision of Article 69 enters into force, the petition in Annex-2 will also no longer need to be sent physically.
The same provision is repeated for the other document types: Article 12 for declarations of conformity, Article 15 for the SİP declaration, Article 18 for instructions for use, Article 21 for the ISO 13485 certificate, Article 22 for the domestic product certificate and Article 23 for the authorised distributorship certificate contain the same provision. Point (g) of Article 47(3) of the Manual says the same for applications within the scope of the transition period extension.
The one notable exception to this rule is on the firm side, not the document side: under Article 5(3) of the Manual, the documents required for the registration of an ordinary partnership firm are sent to the Agency through EBS (Electronic Application System).
When Is a Document Update (Revision) Notification Required?
Document registration is not a one-time procedure. When your certificate is revised, your instructions for use are updated or your quality certificate is renewed, the record on the ÜTS side must be updated as well.
• When the certificate is revised: Under Article 6(4) and (5) of the Manual, it is notified again with the document start date updated to the revision date and the document number updated together with the revision number. For EU certificates the same rule is in Article 7(4) and (5).
• When the instructions for use are updated: According to Article 18(3) of the Manual, if the instructions for use have been updated, entering at least one of the update date and/or the update information of the document in ÜTS is mandatory.
• When the ISO 13485 certificate is renewed: According to Article 20(2) of the Manual, if the document has been revised, the revision date is entered as the "Document Start Date". According to paragraph 5 of the same article, the validity period of such documents cannot exceed 3 years.
• For the domestic product certificate: According to Article 22(5) of the Manual, the validity period of the domestic product certificate is one year from the date of issue.
Update notifications, like the first registration, are tied to an application under Article 39; having the notification updated in the system is not enough on its own.
Five Common Mistakes in a Document Application
The five headings below gather the most common points where the provisions above are violated. All five can be prevented before the application is submitted.
• Selecting the wrong application type: Under Article 39(9) of the Manual, only the documents suited to the selected type are listed on the "Select Document" screen; with the wrong type, the document you are looking for does not appear at all.
• Exceeding the limit of 5 documents: Under Article 39(15), a document application contains at most 5 document notifications.
