top of page

Correcting a Rejected ÜTS Application

Your application was rejected or received a revision, and your first reflex is to correct the same file and send it again

Correcting a Rejected ÜTS Application

Correcting a Rejected ÜTS Application and the Objection Route

Your application was rejected or received a revision, and your first reflex is to correct the same file and send it again. Stop before doing that: the Guide defines a separate route to use before reapplying, and it removes the Agency's responsibility for companies that skip this route.

This page first explains what you should do, then what kind of decision you have received, and what we ask from you to review the file. The references are to the TİTCK "Guide on the Registration Processes of Medical Devices in the Product Tracking System" (TCKKD-KLVZ-03).

The objection stage before reapplying

If you think the decision is contrary to the legislation, the first thing to do is not to reapply but to request a re-evaluation. Article 39, paragraph 16 of the Guide sets up this route for document applications, and Article 40, paragraph 9 sets it up in the same way for device applications. Both paragraphs state the purpose plainly: to have the decision corrected, without reapplying, for an application that the Agency has evaluated wrongly.

The route itself consists of three steps, and all three are named in the Guide.

  • Screen: The "Report Request" screen in ÜTS is used.
  • Request Field: The "Medical Device Document and Product Registration Transactions" field is selected.
  • Application number: In the relevant field "Medical Device/Document Application Number", the Document Application Number or Device Application Number assigned to the application in question is entered.

This route is not only for "Rejection" decisions. Both paragraphs define the scope as "any “Rejection” or “Revision” decision". If you received a revision, the same route is open.

The scope of the route is also narrow, and knowing this saves time. The request is opened not for the application as a whole, but for one or more of the document or device notifications within the application. If an application contains five documents and only two received an unfavorable decision, the objection is limited to those two notifications. So the first thing we separate when reading the decision screen is whether the unfavorable decision was given to the whole application or to a single notification within it.

Why your objection is not taken into evaluation

There are two typical reasons for receiving no answer at all after a request is opened, and both are written in the same paragraph of the Guide. Article 39, paragraph 16 and Article 40, paragraph 9 state that requests will not be evaluated in two cases.

  • If the application number is not entered: Requests in which the relevant number is not entered in the "Medical Device/Document Application Number" field are not evaluated. Writing the number in the request text is not enough; the field itself must be filled in.
  • If there is no reference to legislation: Requests that do not refer to the legislation or Guide provisions concerning the objected matter are not evaluated. Saying "this decision is wrong" is not enough; you must write under which article it is wrong.

There is also a third point, and its consequences cannot be corrected retroactively. Article 39, paragraph 16 states that the Agency will not be held responsible for applications that are sent for review by reapplying without being corrected through the request. In other words, if you skip this route and resend the same file, you have narrowed your own ground for objecting to the decision that follows.

When an "Request Update" decision arrives

Not every unfavorable decision is a rejection or a revision. For one or more of the notifications within an application, the Agency may also give a 3-day update period; in ÜTS this appears as the "Request Update" decision.

This three-day period is a period granted to the company by the legislation; it is not an indication of how long the work will take. Article 39, paragraph 17 of the Guide states that if you think this decision is contrary to the legislation or the Guide, the same "Report Request" route can be used before the update is made. The Request Field is again "Medical Device Document and Product Registration Transactions" and the mandatory field is again the Document Application Number.

The same paragraph also regulates the shift of responsibility here: the Agency is not held responsible for applications for which an update is made without being corrected through the request. The same paragraph also repeats that requests without a number and without references will not be evaluated.

In practice this is the most commonly confused type of decision. Companies see that they must do something within three days and make the update directly; if the decision itself is wrong, the right to object passes unused.

Revision and rejection are not the same

The difference between the two decisions determines whether the file can be saved. Article 39, paragraph 18 of the Guide states that where a document application contains an EC Certificate or EU Certificate and the evaluation is positive, the validity and currency of the certificates that become registered will be queried by the Agency through the notified body that issued the certificate or the competent authority that authorized it. The result of the query is tied to two separate subparagraphs.

  • A certificate that is not current receives a revision: Under subparagraph (a) of the same paragraph, a 45-day revision is applied to certificates determined not to be current.
  • The exception is for MDR and IVDR certificates: The same subparagraph states that 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 is applied instead of the 45-day revision.
  • Reasons other than currency bring a direct rejection: Under subparagraph (b) of the same paragraph, a direct rejection is applied to certificates determined to be invalid for reasons other than having lost currency.

The 45 and 120 days here are periods that the legislation gives to the parties. They show the time given to obtain the current version of the certificate and upload it to ÜTS; they do not show how long an application takes to conclude.

The practical result of the distinction is this: if you received a revision, your file is not closed; you have a period allowed to update the document and replace it, and the first task in that period is to ask the manufacturer for the current certificate. If you received a direct rejection, there is no such period; there either an objection is built on a ground showing the decision's conflict with the legislation, or the application is rebuilt from the beginning. For this reason, the first question we ask in every file that comes to us is "was it rejected or did it receive a revision"; although the two decisions look similar on the same screen, they do not require the same work.

Rejection of one application can affect other records

The effect of the decision is often not limited to a single application, and this is the point that surprises companies most. Both subparagraph (a) and subparagraph (b) of Article 39, paragraph 18 carry the same sentence: the transactions mentioned above are also carried out for all certificates already registered in ÜTS that are not current and are associated with the same document number.

That is, if a revision or rejection arises over one certificate number, your other records associated with the same number receive the same transaction. For companies with many barcodes tied to the same document in their portfolio, this means a single decision moves dozens of records.

A similar chain effect exists on the class side. Article 43, paragraph 11 of the Guide states that if, as a result of updating the "Class" data field, the documents tied to the relevant device records become incompatible with the device class, a revision will be given to the devices with the relevant barcode. For this reason, when reviewing a rejection file we look not only at the rejected application but also at the other records tied to the same document number and the same barcode.

The file needed for review

The set we need to read the file quickly is short. If you send the following four in a single folder, we complete the first reading and tell you in writing which route is open.

  • Application number: The Document Application Number or Device Application Number. Without this number the objection cannot be opened; Article 39, paragraph 16 and Article 40, paragraph 9 of the Guide leave requests without a number out of evaluation.
  • A screenshot showing the decision reasoning: The Guide does not ask for a screenshot; in practice we ask for it. The reasoning sentence written by the Agency is the only data that determines which article the objection will be based on.
  • The final version of the documents uploaded to the application: Article 6, paragraph 6 and Article 7, paragraph 6 of the Guide require the certificate to be uploaded complete with all its annexes and additional pages. We need to see whether the uploaded file is actually complete.
  • The original document page related to the rejected field: Article 6, paragraph 2 and Article 7, paragraph 2 of the Guide state that the information entered in ÜTS and the information on the certificate must be the same. We need the relevant page of the document to make this comparison.

After you send these four items, we ask nothing else from you. We read the file and tell you in writing one of three results: there is a ground for objection and we state under which article we will base the request; there is no ground for objection and we state which part of the application must be rebuilt; or the decision comes not from a technical deficiency but from the document itself and we must first correspond with the manufacturer. Whichever of the three results comes out, we give the reasoning together with the article number.

The most common rejection reasons on the document side

The following are the reasons we encounter most in document applications. For the full catalog of rejection reasons, see our page explaining why an ÜTS application is rejected; here we collect only those we most often resolve in an objection file.

  • The information entered in ÜTS differs from the information in the document: The second paragraphs of Articles 6 and 7 of the Guide for certificates, and the second paragraphs of Articles 10 and 11 for declarations of conformity, set the same provision: the information entered in the system and the information in the document must be the same.
  • Annexes and additional pages uploaded incompletely: The sixth paragraphs of Articles 6 and 7 of the Guide require the certificate to be uploaded complete with all its annexes and additional pages.
  • A printout uploaded instead of the original of an e-signed or e-apostilled document: Subparagraphs (c) and (ç) of Article 8, paragraph 1 of the Guide make it mandatory to upload the original of the relevant document to ÜTS so that verification can be made, and sub-subparagraph 3 of the same subparagraphs states that documents that cannot be verified because the original was not uploaded will not be accepted.
  • The whole document uploaded in the "Turkish Document" field: Subparagraph (a) of Article 8, paragraph 2 of the Guide states that only the Turkish part of the sworn-translator-approved document is uploaded to this field.
  • A missing element in the translation: Subparagraph (b) of the same paragraph requires the sworn translator's name and surname, stamp, signature or seal, and the translator's declaration that the translation was made faithfully to the original document.
  • The "EU Authorized Representative" field left empty: Subparagraph (a) of Article 12, paragraph 7 of the Guide makes it mandatory to enter this field in registration notifications of the "EU Declaration of Conformity (MDR/IVDR)" belonging to manufacturers not established in an EU member state or in Türkiye.

The most common rejection reasons on the device side

In device applications the reasons come more from data entry and images. Five of them are written in the Guide directly as "the application results unfavorably" or an equivalent expression.

  • The barcode not entered as it appears in the documents: Sub-subparagraph 4 of subparagraph (b) of Article 25, paragraph 2 and sub-subparagraph 4 of subparagraph (b) of Article 27, paragraph 2 of the Guide state that an application for a device record whose barcode is not entered into the system as it appears in its technical documents will result unfavorably.
  • An unclear and unreadable image uploaded: Sub-subparagraph 8 of subparagraph (a) of Article 25, paragraph 6 of the Guide expressly states that the application will result unfavorably in this case.
  • Only a package image uploaded: Sub-subparagraph 5 of the same subparagraph states that, as the product image, not only the package or packaging of the device will be uploaded, and that images clearly showing a photograph or technical drawing of the device must also be uploaded. The exception is in sub-subparagraph 6: if opening the package would compromise the sterility and reliability of the device, or if the device is in liquid form, only the package image may be uploaded.
  • Commercial expressions in the image name: Sub-subparagraph 9 of the same subparagraph requires image file names to describe the device and the image, and states in particular that commercial extensions and expressions such as "WhatsApp" must not appear in image names.
  • Inconsistency between the GMDN description and the product characteristics: Sub-subparagraph 5 of subparagraph (b) of Article 25, paragraph 4 and sub-subparagraph 5 of subparagraph (b) of Article 27, paragraph 4 of the Guide make it mandatory that the information in the description of the GMDN code to which the device is matched is consistent with product characteristics such as whether the device is single-use and whether it is sterile.

The wrong "Attached" label: the invisible rejection reason

In some rejections, when the reasoning is read, it says "the document is already there" and no error can be found. In these files the problem is usually not the existence of the document but its label. ÜTS holds a document not only by its number but by the triple of class, regulation and annex applied. If this triple does not exactly match the combination permitted for the device's class, the document is not linked to the device.

All the combinations are in the document business rule annexes shown separately for each regulation and class in Articles 63 to 67 of the Guide, that is, in the annexes between Annex-81 and Annex-100. Two examples show the type of problem.

  • MDD Class III: Article 63, paragraph 5 of the Guide points to Annex-83 for this class. None of the combinations in Annex-83 is built with a single certificate: "ANNEX-2 FULL QUALITY ASSURANCE SYSTEM" with "ANNEX-2 ARTICLE 4, DESIGN EXAMINATION", or "ANNEX-3 TYPE EXAMINATION" with "ANNEX-4 EC VERIFICATION", or "ANNEX-3 TYPE EXAMINATION" with "ANNEX-5 PRODUCTION QUALITY ASSURANCE" are requested together. A type examination certificate alone is not sufficient.
  • IVDD Annex-2 List A: Article 65, paragraph 3 of the Guide points to Annex-85 for this class. There, next to the EC Certificate labeled "ANNEX-4 FULL QUALITY ASSURANCE SYSTEM", an EC Certificate labeled "ANNEX-4 ARTICLE 4, DESIGN EXAMINATION" is requested.

In these files the solution is not to obtain a new document; it is often to register in ÜTS, with the correct label, the second certificate that is already in hand.

If a forged or tampered document is alleged

There is one category that an objection does not resolve, and this must be said at the outset. Article 39, paragraph 18, subparagraph (b) of the Guide states that for documents determined to be forged or tampered with, after the rejection transaction the PGD process will also be started so that the necessary actions can be taken.

PGD is defined in Article 4 of the Guide as market surveillance and inspection, and it is an inspection activity carried out by the Agency. This is not a file that closes with the correction of a technical deficiency.

When you encounter such a reasoning, the first thing to do is to go to the source of the document: ask the notified body that issued the certificate, or the manufacturer, directly for verification. In such files we do not write an objection text; we first establish whether the document was actually issued by that body.

Rejection on the data change side

A rejection decision does not always come from a registration application. Imported product data change requests, opened when there are data differences between records of different companies with the same barcode, can also be rejected, and this side has its own rules.

  • A rejection decision is reasoned: Article 43, paragraph 10 of the Guide states that if, as a result of the Agency's evaluation, the request is not found suitable, the request will be rejected with its reasoning and will move to "Rejected" status in ÜTS.
  • Some fields always go to the Agency: Paragraph 7 of the same article states that requests concerning fields for which the Agency's evaluation is required, such as "Class", "GMDN" and "EMDN", will in every case be submitted for the Agency's evaluation and approval. The unanimity of other companies is not sufficient in these fields.
  • A separate application for each field: Article 44, paragraph 9 of the Guide states that a selection will be made for only one of the listed data fields, and if a change is requested in different data fields too, a separate application will be made for each field.
  • The place of the evidence document is fixed: Paragraph 10 of the same article states that the documents and images in the nature of evidence documents submitted to other companies and the Agency in the evaluation of the request will be uploaded to the "Submitted Document and Image Field".

Another period on this side is also one the legislation gives to the parties: Article 43, paragraph 3 of the Guide defines the period for other companies with records with the same barcode to express their opinion as 5 days, and states that companies that do not express an opinion within this period will be deemed to have accepted the request.

Scope and limits of the service after a rejection

This is the most honest part of this page. No guarantee of result can be given after a rejection. The Guide contains no commitment in any article on when or how an application will conclude; it is also not possible for a consultant to give such a commitment on behalf of the Agency.

What we promise is the method. We read the file, determine what kind of decision it is, and, if there is a ground that can be objected to, we open the request with the two conditions sought by Article 39, paragraph 16 of the Guide: the application number entered in the correct field and a clear reference to the legislation or Guide on the matter objected to.

If there is no ground for objection, we say that too. In files where the certificate has really lost currency, the document is really incompatible with the class, or the entered data really differs from the document, opening an objection only wastes time. In those files the work is to complete what is missing and rebuild the application.

For us to take over this work, it is enough for you to define a user of the "Medical Device Registration Officer" type for our staff from your company page. Under Article 39, paragraph 13 and Article 40, paragraph 5, subparagraph (g) of the Guide, the electronic signature of the rebuilt application remains with your company's authorized signatory.

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