top of page

ÜTS Process Management and Tracking

You submitted your application to ÜTS, but the screen shows "Awaiting Signature" and has not changed for weeks. Or a "Revision" decision has arrived, you disagree with it, and you are looking for a way other than filing a new application.

ÜTS Application Tracking: Statuses, Report Request and the Objection Route

You submitted your application to ÜTS, but the screen shows "Awaiting Signature" and has not changed for weeks. Or a "Revision" decision has arrived, you disagree with it, and you are looking for a way other than filing a new application.

This page explains the Guide definitions of application and registration statuses in ÜTS, the three separate uses of the "Report Request" screen, and the cases in which an objection request is not taken into evaluation. All periods given are periods granted to the parties in the Guide on Registration Processes of Medical Devices to the Product Tracking System; they are not a commitment on how long a process will take.

Application Status Glossary

The status of an application in ÜTS tells you directly where that application is stuck in the chain. Article 39 of the Guide describes this chain step by step for document applications.

  • Awaiting Signature: The document application has been created and the "Approve" action has been completed on the "Document Application Summary" screen, but it has not yet been signed electronically. Under the twelfth paragraph of Article 39, if there is nothing contrary to procedure and business rules in the document notifications of the application, the application is created in this status.

  • Awaiting Payment: Under subparagraph (a) of the thirteenth paragraph of Article 39, electronically signed applications that contain document types mentioned in Articles 6, 7, 10, 11 and 14 of the Guide move to this status. For documents subject to payment, once the application fee is paid and approved, the application moves to "Under Review".

  • Under Review: Under subparagraph (b) of the same paragraph, documents other than the document types in subparagraph (a) move to this status as soon as the application is signed electronically. This is the only status in which an Agency expert can carry out an evaluation.

For device applications the chain is one step longer. Subparagraph (g) of the fifth paragraph of Article 40 of the Guide requires that, for a device application to go to the Agency in the "Under Review" status, it must first be signed electronically by the authorized signatory and brought to the "Awaiting Payment" status, and then the application fee must be paid.

My Application Did Not Move to "Under Review"

This is one of the most frequently asked questions in ÜTS, and the answer is written in a single sentence in the Guide. The fourteenth paragraph of Article 39 states that applications that do not reach the "Under Review" status cannot be evaluated by the Agency review expert. The same statement is repeated for device applications in subparagraph (g) of the fifth paragraph of Article 40.

In other words, while your application is in the "Awaiting Signature" or "Awaiting Payment" status, nothing is being processed on the Agency side. The party that is waiting is not the Agency but the company. The missing link in the chain is one of these three:

  • Approval step missing: Under the eleventh paragraph of Article 39, only users of the company with the user type "Medical Device Registration Officer" can perform the "Approve" action on the "Document Application Summary" screen. If this user type is not defined, the application cannot be created at all.

  • E-signature step missing: Under the thirteenth paragraph of Article 39, an application in the "Awaiting Signature" status is signed electronically by the company's applicant authorized signatory. If no authorized signatory is defined in the system or their e-signature cannot be used, the application stops here.

  • Payment step missing: For applications containing a document type subject to a fee, the application does not progress until the fee is paid and approved.

Reading the label on the status screen is the fastest way to find out at which step the problem lies. Checking these three steps before writing to the Agency solves most cases.

Device Registration Statuses: Draft, Ready for Application, Registered, Rejected, Deleted

The status of device registrations works separately from application statuses. Subparagraph (a) of the tenth paragraph of Article 25 and subparagraph (a) of the eleventh paragraph of Article 27 of the Guide state that the "Is it ready for application?" field on the device registration screen determines this status.

  • Draft: When "No" is selected in the "Is it ready for application?" field, that is, when the registration notification will be updated later or is not yet ready to be sent to application, the device is saved in this status.

  • Ready for Application: When the field is set to "Yes", that is, when the registration notification takes its final form, the device moves to this status and is listed on the "List My Medical Devices" screen.

  • Registered: The status reached after the Agency evaluates the device application positively.

  • Rejected: The status in which the application has ended negatively.

  • Deleted: Under the eighth paragraph of Article 34 of the Guide, device registrations in the "Registered" status and (except those with a Reject-3 decision) in the "Rejected" status are not deleted from ÜTS; they are moved to the "Deleted" status.

The seventh paragraph of the same article states that device registrations in the "Draft" and "Ready for Application" statuses are actually deleted from ÜTS. The ninth paragraph clarifies who has the authority to delete: device registrations can only be deleted by the relevant company, and the Agency does not delete device registrations in ÜTS.

What Is the "Report Request" Screen and What Request Areas Does It Have?

"Report Request" is a single screen in ÜTS, but it is used for three very different purposes. Separating these three ensures that the request lands in the right place.

First, adding an organization that is not defined in ÜTS to the system. Second, adding a code or value that is not found in the drop-down lists on the registration screens. Third, objecting to a rejection, revision or update decision given by the Agency.

The key field of the screen is "Request Area". Under which request area you open your request determines which team and which evaluation flow it goes to. A request opened under the wrong request area can wait in the wrong queue even if its content is correct. For some code and value additions the Guide defines separate, named request areas, while it groups the rest under the "Medical Device Document and Product Registration Operations" area; objections are also opened through this area.

Code and Value Addition Requests

If you cannot find the value you are looking for in a list while registering a device, you need to open a request rather than leave the field blank. The Guide lists these requests together with their field names.

  • Adding a GTİP Code: If the GTİP number of the device does not exist in the system, this request area is selected to ask for the number to be added (third sub-item of subparagraph (c) of the third paragraph of Article 25 and third sub-item of subparagraph (ç) of the third paragraph of Article 27).

  • Adding a GMDN: If the GMDN code that defines the device is not defined in ÜTS, a request is opened through this area. If the request is found appropriate and the code is confirmed to be correct and valid in the GMDN query, the code is defined (seventh sub-item of subparagraph (b) of the fourth paragraph of Article 25).

  • Adding an EMDN: If the EMDN code that defines the device is defined in the European Commission's EMDN link but is not defined in ÜTS, a request is opened through this area (eighth sub-item of subparagraph (ç) of the fourth paragraph of Article 27). GMDN and EMDN are not interchangeable fields in ÜTS; they are two separate fields, and separate request areas are defined for both.

  • Adding a Branch Type: If there is no branch type that defines the device, a request is opened through this area (third sub-item of subparagraph (c) of the fourth paragraph of Article 25).

  • Adding Other MDR/IVDR Special Conditions: If the warning, precaution or special condition that needs to be selected is not in the list, this request area is selected (third sub-item of subparagraph (ç) of the ninth paragraph of Article 27).

  • Adding a CMR / ED Substance: If the CMR or endocrine-disrupting substance that needs to be selected is not in the list, this request area is selected (third sub-item of subparagraph (b) of the tenth paragraph of Article 27).

Some other values besides these are requested through the "Medical Device Document and Product Registration Operations" area instead of a separate request area: a sterilization method not in the list (fourth sub-item of subparagraph (s) of the seventh paragraph of Article 25), a measurement type or unit not in the list (third sub-item of subparagraph (a) of the eighth paragraph of Article 25) and a storage or use condition measurement unit not in the list (subparagraph (b) of the ninth paragraph of Article 25). For sterilization method and measurement type requests, the Guide requires detailed information and reference documents on the relevant method or unit to be uploaded as an attachment to the request.

Notified Body / Conformity Assessment Body Operations

If the notified body that issued the certificate is not defined in ÜTS, the document cannot be registered. The seventh paragraph of Article 6 of the Guide for EC certificates and the seventh paragraph of Article 7 for EU certificates show the same solution: before the document registration operations, a request is opened through the "Report Request" screen, under the "Notified/Conformity Assessment Body Operations" area, for the notified body to be added to ÜTS or for authority to be defined within the scope of the relevant legislation.

The process after the request is also written in the article. The Agency carries out a query through the NANDO Notified Bodies query website; if it is established that the relevant conformity assessment body has been authorized as a notified body, the body is added to ÜTS and defined according to the regulations under which it is authorized. Doing this step before the document application prevents the application from running into business rules.

Objecting to a Rejection or Revision Decision: Before Reapplying

The sixteenth paragraph of Article 39 of the Guide defines a route other than reapplying against negative decisions. If a negative decision is given by the Agency for one or more of the notifications within a document application (any "Rejection" or "Revision" decision) and it is believed that this decision is contrary to the relevant legislation and the Guide, the company can request re-evaluation of the decision before making a new document application.

The purpose stated in the article is clear: to have the decision corrected, without reapplying, for an application evaluated incorrectly by the Agency. How to open the request is also described step by step.

  • Screen: The "Report Request" screen in ÜTS is used.

  • Request Area: The "Medical Device Document and Product Registration Operations" area is selected.

  • Number field: The Document Application Number assigned to the application in question is entered in the "Medical Device/Document Application Number" field.

  • Content: The request refers to the provisions of the legislation and/or the Guide relating to the matter objected to.

For device applications, the same route is defined in the ninth paragraph of Article 40 of the Guide. The difference lies in a single field: instead of the Document Application Number, the relevant Device Application Number is entered in the number field.

For Which Two Reasons Is Your Objection Request Not Taken into Evaluation?

The Guide draws a clear limit here. The last sentence of the sixteenth paragraph of Article 39 lists two cases, and the same sentence is repeated for device applications in the ninth paragraph of Article 40.

  • Application number not entered: Requests in which the relevant application number has not been entered in the "Medical Device/Document Application Number" field are not taken into evaluation.

  • No reference to legislation or the Guide: Requests that do not refer to the provisions of the legislation or the Guide relating to the matter objected to are not taken into evaluation.

The practical result is this: a request written as "we disagree with this decision, please look again" is not evaluated, even if it is right in substance. In the body of the request you need to state which article, which paragraph and which subparagraph you rely on. Placing the relevant Guide provision next to the rejection reason is a precondition for the objection to be processed.

The "Request Update" Decision and the 3-Day Update Period

Not every negative decision given by the Agency is a rejection or revision. The seventeenth paragraph of Article 39 of the Guide defines a separate decision type: giving a 3-day update period for one or more of the document notifications, that is, a "Request Update" decision.

When this decision arrives, the objection route is also open. The same paragraph states that if the decision is thought to be contrary to the legislation and the Guide, the company can request re-evaluation of the decision through the "Report Request" screen before carrying out the update. The route is the same: the "Medical Device Document and Product Registration Operations" request area, the Document Application Number and a reference to the legislation.

The 3 days here is the update period the Agency gives to the company. It is not a period showing how long the process will take, and the two should not be confused. All periods in the Guide are of this nature: periods granted to the parties.

Certificate Currency Query: 45 Days and 120 Days

There is also a control step after your document application has ended positively. The eighteenth paragraph of Article 39 of the Guide regulates the following: where document types mentioned in Articles 6 and 7 are included in the document application (EC Certificate or EU Certificate) and the application ends positively, the validity and currency of the certificates that have reached the registered status are queried by the Agency through the notified body that issued the certificate or the competent authority that authorized that body.

Depending on the result of the query, two different operations are applied.

  • Certificates determined not to be current: Under subparagraph (a) of the same paragraph, a 45-day revision process is applied.

  • Exception — 120-day extension: Again under subparagraph (a), only for EU Certificates under MDR and IVDR, and only for certificates revised because of an extension of the product scope, a 120-day extension process is applied instead of the 45-day revision process.

  • Reasons other than losing currency: Under subparagraph (b), certificates determined to be invalid for reasons other than having lost their currency are rejected directly.

The two conditions for the 120-day extension are required together: the document must be an EU Certificate under MDR or IVDR, and the reason for revision must be an extension of the product scope. If either condition is missing, the 45-day revision applies.

Other Records Linked to the Same Document Number Are Also Affected

This is the easiest part of the process to overlook. The eighteenth paragraph of Article 39 of the Guide repeats the same sentence in both subparagraph (a) and subparagraph (b): the operations mentioned above are also carried out for all certificates associated with the same document number that are already registered in ÜTS and are not current.

In other words, a revision or rejection decision given for a single record you opened under one certificate number also covers your other records linked to the same number. For companies that have dozens of device records under a single EU certificate of a manufacturer, the impact can be large. When a certificate is revised or loses its currency, you need to filter the record list by that document number and see all the records that will be affected in advance.

Rejection and the PGD Process for a Forged or Falsified Document

Subparagraph (b) of the eighteenth paragraph of Article 39 defines one more consequence. A rejection is applied to documents determined to be forged or tampered with; after the rejection, the PGD process is also started so that the necessary actions can be taken.

What PGD means is written in the definitions section of Article 4 of the Guide: Market Surveillance and Inspection refers to the activities carried out and measures taken by the Agency to check and ensure that devices meet the requirements set out in the relevant European Union harmonization legislation and do not endanger health, safety or other aspects of the protection of the public interest.

This is a situation that is no longer a registration problem but has become a matter of inspection. Obtaining documents from abroad directly from the manufacturer and in their unaltered form, and not processing copies passed through intermediaries, reduces this risk.

What to Do in the "Awaiting Payment" Status?

The answer is one sentence: the application does not move to "Under Review" until the fee is paid. Subparagraph (a) of the thirteenth paragraph of Article 39 of the Guide states that for the document or documents subject to payment, the application moves to "Under Review" after the application fee is paid and approved. For device applications, subparagraph (g) of the fifth paragraph of Article 40 sets the same condition.

In this case the party waiting is not the Agency but the company. As long as payment is not made, the application does not enter the review queue at all. Determining from the start who is responsible for following the payment step prevents the process from getting stuck here.

Where Do You Find the Application Number?

ÜTS assigns a number to every document and device application, and this number is a precondition for request operations. The sixteenth paragraph of Article 39 of the Guide mentions the Document Application Number, and the ninth paragraph of Article 40 mentions the Device Application Number. Both articles require this number to be entered in the "Medical Device/Document Application Number" field on the "Report Request" screen and state that a request without it will not be taken into evaluation.

The practical result: do not move past an application without recording its application number. Looking for the number after the decision arrives wastes time, and entering a wrong number causes the request not to be processed.

Responsibility for Applications Resubmitted Without Correction

While defining the objection route, the Guide also draws a limit of responsibility. The sixteenth paragraph of Article 39 states that the Agency is not held responsible for applications that are resubmitted for review without correction through the request. The same approach exists in the seventeenth paragraph: the Agency is not held responsible for applications for which an update operation is performed without correction through the request.

These two sentences determine the order of objection and correction. If you are going to object to a decision, resubmitting the same application without correction before waiting for the result of your objection is not a protective act. A safer order is to first clarify in which direction the decision will go, and then either correct and resubmit or act according to the result of the objection.

Monitoring Records Whose Document Expiry Date Is Approaching

Application tracking is not only about monitoring pending applications; it also covers the expiry dates of registered documents. The Guide defines upper limits by document type.

  • EC Certificate: Under the third paragraph of Article 6 of the Guide, EC certificates under the Old Medical Device Regulations, except the EC Verification Certificate and the EC Type Verification Certificate, have a validity period, and this period cannot exceed 5 years.

  • EU Certificate (MDR/IVDR): Under the third paragraph of Article 7, EU certificates issued under the New Medical Device Regulations remain valid for the period stated in the certificate, not exceeding 5 years. For both document types, the validity can be extended in additional periods, each not exceeding 5 years, based on re-evaluation upon the manufacturer's application.

  • Quality Management Document – ISO 13485: Under the fifth paragraph of Article 20, the validity period of this type of document cannot exceed 3 years.

  • Domestic Goods Certificate: Under the fifth paragraph of Article 22, the validity period is one year from the date of issue.

The Domestic Goods Certificate, which has a one-year validity period, is the document most often overlooked in tracking lists. For companies taking part in public tenders, the expiry of this document can have commercial consequences regardless of the device registration.

How to Set Up an Internal Tracking List?

The Guide does not describe a tracking list format; what follows is a recommendation from practice. Its logic is still based on the fields in the Guide: also record on your side every number and every status that ÜTS gives you.

  • Application number: Document Application Number or Device Application Number. Since it is a precondition for objection and request operations, it should be the first column.

  • Status: The current ÜTS status, such as Awaiting Signature, Awaiting Payment or Under Review.

  • Decision and decision date: The rejection, revision or update decision and the date the decision arrived.

  • Responsible person: Who will take the next step. Since the approval step lies with the registration officer and the signature step with the authorized signatory, this column often carries two different names.

  • Next action and its date: The periods written in the Guide are entered in this column.

The only periods to be entered in the calendar are those stated in the source: 3 days in a "Request Update" decision, the 45-day revision for certificates determined not to be current, the 120-day extension in the case of an extension of the product scope for MDR and IVDR EU certificates, and the 10-day payment period in subparagraph (ö) of the second paragraph of Article 42 for free sale certificate applications. Apart from these, no date of the form "it will conclude in so many days" should be written for any stage; the Guide does not define such a period.

Setting up process tracking this way removes the two situations that waste the most time in ÜTS: believing that an application waiting on your own side is waiting at the Agency, and taking the wrong step within the objection period. For details on document registration, product registration, reasons for rejection and the MDR transition, you can look at our ÜTS Document Registration, ÜTS Product Registration, Why Is a ÜTS Application Rejected and ÜTS Registration in the MDR and IVDR Transition pages; for correcting a rejected file, see our Correcting a Rejected ÜTS Application service.

ÜTS Registration

Medical Device ÜTS Registration Consultancy

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