top of page

Why Is a ÜTS Application Rejected

Your application was rejected and the reasoning consists of a single line. This page lists the concrete reasons for which ÜTS document and device applications end with a negative result, together with the Guide article each reason rests on

Why Is a ÜTS Application Rejected? Rejection Reasons Based on the Legislation

Your application was rejected and the reasoning consists of a single line. This page lists the concrete reasons for which ÜTS document and device applications end with a negative result, together with the Guide article each reason rests on. You can jump straight to the full list under “Rejection and Revision Reasons”; the later sections group the same reasons by topic.

Rejection, Revision and “Request Update”: Three Different Decisions

A negative decision in ÜTS has no single name, and which decision you received determines the step you take. Article 39, paragraph 16 of the Guide provides that where a “Rejection” or “Revision” decision is issued on a document application and the decision is considered contrary to the legislation, a re-evaluation can be requested through the “Report Request” screen before a new application is made. Article 40, paragraph 9 of the Guide defines the same route for device applications.

  • Rejection: The application ends negatively. You either correct it and reapply, or first use the Report Request route.

  • Revision: A revision is issued on the document or device record; the Report Request route is open against this decision as well.

  • Request Update: Under Article 39, paragraph 17 of the Guide, a 3-day update period is given. If the decision is wrong, you can ask for re-evaluation before making the update.

There is also a separate mechanism tied to how current certificates are. Article 39, paragraph 18 of the Guide states that when an application containing an EC or EU Certificate ends positively, the validity and currency of the certificates will be queried by the Agency through the notified body or the authority that designated it. Under subparagraph (a) of the same paragraph, a 45-day revision applies to certificates found not to be current; as an exception, a 120-day extension applies only to EU certificates under MDR and IVDR, and only to those revised because of a scope extension. These periods are periods that the legislation grants to the parties.

Rejection and Revision Reasons: 36 Concrete Items

The list below is compiled from provisions of the Guide that state a negative outcome or set out a requirement. Each item gives the cause first, then what to do.

  • Cause: An e-Apostille document was uploaded as a printout instead of the original. Subparagraph (c) of paragraph 1 of Articles 8, 12, 15 and 21 of the Guide and subparagraph (c) of paragraph 4 of Article 23 require the original issued digitally by the authority to be uploaded; the third sub-subparagraphs state that documents that cannot be verified because the original was not uploaded are not accepted. Action: Upload the original file received from the authority, not a printout.

  • Cause: The e-signature cannot be verified, or a document with an invalid e-signature was uploaded. The third sub-subparagraph of subparagraph (ç) of paragraph 1 of Article 8 and the second sub-subparagraphs of the corresponding subparagraphs of Articles 12, 15, 21 and 23 state that such documents are not accepted. Action: Request a verifiable original file and test the verification in advance.

  • Cause: The information entered in ÜTS differs from the information in the document. Paragraph 2 of Articles 6 and 7 lists the fields checked on certificates, and paragraph 2 of Articles 10 and 11 lists those checked on declarations; they require the information entered in the system to be the same as the information in the document. Action: Enter the name, address, document number, regulation, annex and dates by reading them from the document.

  • Cause: The annexes or additional pages of the document were uploaded incompletely. Paragraph 6 of Articles 6 and 7, paragraph 7 of Article 10, paragraph 6 of Article 11 and paragraph 4 of Article 20 require the document to be uploaded in full with all its annexes and additional pages. Action: Merge the annex pages and scope lists into a single file.

  • Cause: A domestic manufacturer application was made without an e-signature or with the wrong application type. Paragraph 1 of Article 9, subparagraphs (a) and (ç) of paragraph 1 of Article 13 and subparagraph (a) of paragraph 1 of Article 16 make the “e-signed Document Application for Manufacturer Firms” type mandatory and require the document to be e-signed by the “Responsible Manager” or the “Signatory”. Action: Correct the application type and have the registered authorised person e-sign the document.

  • Cause: The name of the authorised person in the document does not match the name of the e-signature holder. The second sub-subparagraph of subparagraph (a) of paragraph 2 of Article 9 and the second sub-subparagraphs of subparagraph (ç) of paragraph 1 of Articles 13 and 16 require the first name and surname of the authorised person written in the document to match those of the person who e-signed it. Action: Make the name in the document text and the e-signature holder identical.

  • Cause: The first issue date of an MDD/AIMDD declaration of conformity is 26/05/2021 or later. Paragraph 8 of Article 10 of the Guide states that the first issue date of these declarations must be before 26/05/2021. Action: Obtain the version dated before 26/5/2021; if the current declaration is not linked to the old version, upload the old version in the technical documentation field.

  • Cause: The first issue date of an IVDD declaration of conformity is 26/05/2022 or later. Paragraph 9 of Article 10 of the Guide states that the first issue date of these declarations must be before 26/05/2022. Action: Provide the version before 26/5/2022 and its link to the old version.

  • Cause: A generic product expression was used in the declaration of conformity. Paragraph 5 of Article 10 of the Guide requires the scope to identify the product, giving as an example that detail such as forceps, retractor and dilator should be given instead of “Surgical hand instruments”. Action: Upload the detail list, in line with the same paragraph, in the “Technical Documentation for the Product(s) in the Document” field.

  • Cause: The “EU Authorised Representative” field was left blank for a manufacturer outside the EU/Türkiye. Subparagraph (a) of paragraph 7 of Article 12 of the Guide makes an entry in this field mandatory for EU Declaration of Conformity notifications of manufacturers not established in an EU member state or in Türkiye. Action: Enter the representative and fill in the “Authorisation Document” field that opens below it.

  • Cause: The notified body is not defined in ÜTS, or does not hold authority under the relevant regulation. Paragraph 7 of Articles 6 and 7 state that if the body is not defined in ÜTS, a request will be opened from the “Notified/Conformity Assessment Body Transactions” field, and that if authority is established in the NANDO query, the body will be added. Action: Open the definition request before the document application.

  • Cause: More than 5 document notifications were made in one document application. Paragraph 15 of Article 39 of the Guide states that a document application can contain at most 5 document notifications; the same limit is repeated in paragraph 7 of Article 8 and paragraph 5 of Articles 12 and 15. Action: Split the documents into groups of five.

  • Cause: The sworn translator’s name and surname, stamp/signature/seal or declaration is missing in the sworn translation. Subparagraph (b) of paragraph 2 of Articles 8, 12, 15 and 21 and subparagraph (b) of paragraph 5 of Article 23 require these three elements. Action: Ask the translation office for the copy that carries the declaration and the stamp.

  • Cause: The whole document was uploaded to the “Turkish Document” field. Subparagraph (a) of paragraph 2 of Articles 8, 12, 15 and 21 and subparagraph (a) of paragraph 5 of Article 23 state that only the Turkish part of the document certified by a sworn translator is uploaded to this field. Action: Remove the pages in the foreign language.

  • Cause: The user manual was not uploaded for a class where it is mandatory. Paragraph 2 of Article 17 of the Guide makes uploading the manual mandatory for Class III and Class IIb under MDR and MDD, Class IIa if a manual has been issued, Class B, C and D under IVDR together with Self-Test, Near-Patient Test and Companion Diagnostic devices, List A and List B devices in Annex II and Self-Test Devices under IVDD, and AIMDD devices. Action: If there is no manual for an MDD Class IIa device, use the Intended Use Form route.

  • Cause: The user manual was updated but the update date or information was not entered. Paragraph 3 of Article 18 of the Guide requires at least one of the update date and/or the update information to be entered into ÜTS. Action: Enter the revision information from the manual’s identification block into the field.

  • Cause: The Intended Use Form was altered or uploaded unsigned. Subparagraph (d) of paragraph 2 of Article 19 of the Guide states that the form is uploaded unaltered and either wet-signed or e-signed. Action: Upload it signed, without breaking the format in Annex-15.

  • Cause: The Domestic Goods Certificate has no brand name and the “Brand Name” field in ÜTS was not filled in. The first sub-subparagraph of subparagraph (d) of paragraph 4 of Article 22 of the Guide requires the “Brand Name” field on the Domestic Goods Certificate screen in ÜTS to be filled in if the certificate has no brand name. Action: Enter the brand in line with the rules in Articles 25, 27 or 30.

  • Cause: The original language of the domestic manufacturer’s document is not Turkish. Subparagraph (c) of paragraph 1 of Articles 13 and 16 and subparagraph (a) of paragraph 3 of Article 9 state that documents whose original language is Turkish are accepted. Action: Issue the document in Turkish.

  • Cause: The revision date was not entered as the start date; the first issue date was entered instead. Paragraph 4 of Articles 6 and 7 and paragraph 2 of Article 20 state that if the document has been revised, the revision date is entered as the start date. Action: Find the revision date in the certificate and correct the field.

  • Cause: The certificate number was not entered together with the revision number. Paragraph 5 of Articles 6 and 7 and paragraph 3 of Article 20 state that if the revision number is shown together with the document number, the certificate is recorded with the revision number, giving the “XXXXX.Rev.1” format as an example. Action: Enter the number in the form it has in the document, with the revision suffix.

  • Cause: A document labelled “Annexed” that is not permitted for the device class was linked. Articles 63 to 67 of the Guide show which Annex is applied according to the type and risk class of the device; the tables in Annex-81 to Annex-100 give the permitted class, regulation and applied annex combinations. Action: Open the table for the class and compare the combination of the document exactly.

  • Cause: A type-examination certificate was linked alone and the second certificate is missing. Annex-83 shows, for MDD Class III, an “Annex-2 Article 4 Design Examination” certificate alongside the “Annex-2 Full Quality Assurance System” certificate, and Annex-89 to Annex-93 show dual certificate combinations for the MDR classes. Action: Also link to the device the second certificate shown with a “+” in the table.

  • Cause: A certificate labelled “Excluding Article 5” was linked to an IVDR self-test, near-patient or companion diagnostic device. Annex-95 shows the certificate annexed as “Annex IX Chapter II (Excluding Article 5)” for Class B and Class C, while Annex-97 to Annex-100 require the certificate annexed as “Including Article 5” for Self-Test, Near-Patient Test and Companion Diagnostic devices. Action: Choose the correct variant according to the device type.

  • Cause: The barcode was not entered exactly as it appears in the documents or on the label. The third and fourth sub-subparagraphs of subparagraph (b) of paragraph 2 of Articles 25, 27 and 30 require the barcode to be entered exactly, and state that an application for a device record whose barcode is not entered as in its technical documents will end negatively. Action: Compare the barcode on the label, the declaration and the certificate.

  • Cause: The record was opened with the multi-pack barcode instead of the smallest package. The sixth sub-subparagraphs of subparagraph (b) of paragraph 2 of Articles 25 and 27 state that the record is made with the barcode of the smallest package, and that multi-pack barcodes are added to the “Placing on the Market Information” field after registration. Action: Open the record with the unit package barcode.

  • Cause: A device with the same barcode was registered under a different brand name. The sixth sub-subparagraph of subparagraph (d) of paragraph 2 of Article 25 and the sixth sub-subparagraphs of subparagraph (e) of paragraph 2 of Articles 27 and 30 state that devices with the same product number cannot be registered under different brand names. Action: View the other records from the “Products with the Same Barcode” screen and make the brand field consistent.

  • Cause: No brand was declared, or the company name with its corporate suffix was written in the brand field. The second to fourth sub-subparagraphs of subparagraph (d) of paragraph 2 of Article 25 and the same sub-subparagraphs of subparagraph (e) of paragraph 2 of Article 27 state that devices without a declared brand will not be registered and that abbreviations of commercial status such as GmbH, Inc and A.Ş must not appear in the brand field. Action: Remove the company suffixes from the brand field.

  • Cause: The product name was entered incompletely, in an unintelligible way, or in a way that does not match the label. The fourth sub-subparagraph of subparagraph (e) of paragraph 2 of Article 25 and the sixth sub-subparagraphs of subparagraph (f) of paragraph 2 of Articles 27 and 30 state that an application with a product name that is not understandable, incomplete, not in Turkish or not matching the label will end negatively. Action: Write the product name in Turkish and consistent with the label.

  • Cause: Both the Version/Model and the Reference/Catalogue Number fields were left blank. The seventh sub-subparagraphs of subparagraphs (ğ) and (h) of paragraph 2 of Article 27 and of subparagraph (ğ) of paragraph 2 of Article 30 require information to be entered in at least one of the two fields, and state that both cannot be left blank and “NONE” cannot be written. Action: Enter whichever of them appears in the documents.

  • Cause: An unclear, unreadable product image was uploaded. The eighth sub-subparagraphs of subparagraph (a) of paragraph 6 of Articles 25, 27 and 30 state that the image is uploaded in jpeg, jpg, pdf or png format and that applications with unclear images will end negatively. Action: Upload an image that shows the device clearly.

  • Cause: Only a package or packaging image was uploaded. The fifth sub-subparagraphs of subparagraph (a) of paragraph 6 of Articles 25 and 27 state that images clearly showing the photograph or technical drawing of the device must also be uploaded; the sixth sub-subparagraphs define the exception: if sterility and reliability are impaired when the package is opened and/or the device is in liquid form, only a packaging image can be uploaded. Action: Unless you fall under the exception, add an image of the device itself.

  • Cause: An image of another device, or the catalogue itself, was uploaded as an image. The third and fourth sub-subparagraphs of subparagraph (a) of paragraph 6 of Article 25 state that images of other devices are not uploaded even if they belong to similar devices, and that the catalogue itself or an image of multiple devices that makes the device harder to understand is not uploaded. Action: Put the catalogue in the catalogue field and the device image in the image field.

  • Cause: A commercial suffix or expression such as “WhatsApp” was used in the image file name. The ninth sub-subparagraphs of subparagraph (a) of paragraph 6 of Articles 25, 27 and 30 require image names to be descriptive and state that commercial expressions such as “WhatsApp” must not appear in them. Action: Rename the files with names such as “OuterBox.png”.

  • Cause: The GMDN code is inconsistent with features of the device such as being sterile or single-use. The fifth sub-subparagraphs of subparagraph (b) of paragraph 4 of Articles 25 and 27 require consistency between the information in the GMDN description and the features of the device; the sixth sub-subparagraphs require the relevant field to be set to “Yes” if the description of a reusable device says single-use and the device is used on a single patient more than once. Action: Compare the GMDN description with the device’s features.

  • Cause: The EMDN code that appears in the document was not selected, or a higher-level code was selected instead of the terminal term. The fifth sub-subparagraphs of subparagraph (ç) of paragraph 4 of Articles 27 and 30 require the most detailed code and terminal term to be selected if the code appears in at least one of the documents; the ninth sub-subparagraph in Article 27 states that only the most detailed codes will be added to ÜTS. Action: Select the term at the lowest level of the seven-level hierarchy.

Rejections Caused by Document Approval and Upload

Approval routes vary by document type, and not every route is open for every document. Paragraph 1 of Article 8 of the Guide lists, for certificates issued by notified bodies established abroad, apostille, embassy/consulate approval, a verifiable e-Apostille original, a verifiable e-signed original, and publication on the notified body’s query site or in EUDAMED; paragraph 3 shows that if the certificate was issued by a body established in Türkiye and authorised by the Agency, the “original of the certificate” option is added to the list.

For the declaration of conformity the list is narrower. Paragraph 1 of Article 12 of the Guide defines only four routes: apostille-approved, embassy/consulate-approved, verifiable e-Apostille-approved original, and original of a verifiable e-signed document. The notified body query site and EUDAMED routes are not defined for declarations in this paragraph.

Rejections Caused by Translation

Translation is the easiest rejection reason to fix but the one that repeats most often. Subparagraph (b) of paragraph 2 of Article 8 of the Guide requires the translation to contain the translator’s name and surname, stamp/signature/seal, and a declaration that the translation is faithful to the original; the absence of any one of these three elements makes the document incomplete. Subparagraph (a) of the same paragraph states that only the Turkish part is uploaded to the “Turkish Document” field. If the document is prepared in Turkish or in several languages including Turkish, under subparagraph (b) of paragraph 4 of Article 8 it is uploaded only to the “Original Document” field.

Mismatch Between Document Content and ÜTS Data

The review specialist compares every field you enter in ÜTS with the document. Because the Guide lists which fields are checked by document type, this check is not guesswork.

  • EC Certificate: Paragraph 2 of Article 6 of the Guide lists ten fields: the manufacturer’s name and address; the EU authorised representative, if any; the certificate number; the name, identification number and address of the notified body; the regulation it belongs to; the annex applied; the start and end dates; the product scope; and the binding signature.

  • EU Certificate: Paragraph 2 of Article 7 of the Guide extends the list by adding the Single Registration Number, Basic UDI-DI, risk class, references to previous certificates, references to test and audit reports, surveillance information, and the conditions and limitations on validity.

  • Declaration of Conformity: Paragraph 2 of Article 10 of the Guide lists the manufacturer information, the EU authorised representative if any, device information, regulation, class and/or annex applied, dates, and the name, title and signature/stamp information of the authorised person.

  • EU Declaration of Conformity: Paragraph 2 of Article 11 of the Guide adds the Basic UDI-DI, the statement that the declaration is issued under the manufacturer’s sole responsibility, risk class, references to common specifications, notified body and certificate numbers, and the place and date of issue.

The same sentence appears in all four articles: the information entered in the system must be the same as the information in the document.

Rejections Caused by Dates and Revisions

Date fields look minor but are bound by two separate provisions. Paragraph 4 of Articles 6 and 7 of the Guide states that if the document has been revised, the revision date is entered as the start date; paragraph 5 states that if the revision number is shown together with the document number, the certificate is recorded with its revision number. Paragraph 8 of Article 10 of the Guide says that an updated MDD/AIMDD declaration is expected to be linked to its version dated before 26/5/2021. Certificate annexes depend on the main certificate: paragraph 3 of Articles 6 and 7 states that an annex made to a certificate is valid for as long as the certificate it is attached to is valid.

Document Business Rule Mismatch: The Wrong “Annexed” Label

In ÜTS a document is not kept merely as an “EC Certificate” or an “EU Declaration of Conformity”. The tables in Annex-81 to Annex-100 of the Guide define each document with the triple of “Class” + “Regulation” + “Applied Annex”; in Annex-83 the declaration required for MDD Class III takes the form “Declaration of Conformity of «Class-III» Class and/or «93/42/EEC» Regulation and «ANNEX-2 Full Quality Assurance System» Annexed”. This triple must match exactly one of the combinations permitted for the class of the device. Article 63 of the Guide lists which Annex is applied for which class under MDD, Article 66 under MDR and Article 67 under IVDR.

Rejections Caused by Barcode and Identifying Information

The fourth sub-subparagraph of subparagraph (b) of paragraph 2 of Article 25 of the Guide leaves no room for doubt: an application for a device record whose barcode is not entered as it appears in its technical documents ends negatively, and the label/sales package, declaration of conformity and EC certificate are given as examples of technical documents. The barcode format must also comply with the rules of the issuing agency; the fifth sub-subparagraphs of the same subparagraphs give, for a device allocated under the HIBCC standard, the compatibility of the reference/catalogue number with the barcode in the form “+XXXXreferencecodeXX”.

Rejections Caused by Product Name, Brand and Model

The brand field directly determines whether the registration can be carried out. The second sub-subparagraph of subparagraph (d) of paragraph 2 of Article 25 of the Guide states that devices with no declared brand will not be registered in ÜTS. Entering the barcode in the wrong field is a separate error: the sixth sub-subparagraph of subparagraph (f) of paragraph 2 of Article 25 states that the Primary or Secondary Product Number must not be entered in the Version/Model field, and the eighth sub-subparagraph of subparagraph (ğ) of paragraph 2 of Article 27 states the same for the UDI-DI Number. The same prohibition applies to the Reference/Catalogue Number field.

Rejections Caused by Images and Labels

The image field is limited in number and format. The seventh sub-subparagraph of subparagraph (a) of paragraph 6 of Article 25 of the Guide states that at most 10 images can be uploaded to this field; the eighth sub-subparagraph states that files are uploaded in jpeg, jpg, pdf or png format and that applications with unclear images end negatively. On the label side, consistency of content is sought: subparagraph (b) of paragraph 7 of Article 27 of the Guide lists the common information required on the label and/or sales package under Chapter III of Annex I to the MDR; the product name, the manufacturer’s name and address, the EU authorised representative where necessary, and, for imported devices, the importer’s name and address are among them. Its counterpart under the older regulations is subparagraph (b) of paragraph 7 of Article 25.

Rejections Caused by Classification and Code Mismatch

The GMDN field is not a free-choice field. The fifth sub-subparagraph of subparagraph (b) of paragraph 4 of Article 25 of the Guide requires consistency between the information in the GMDN description and the features of the device; the third sub-subparagraph states that if the code appears in at least one of the documents, that code is selected. On the EMDN side the requirement is conditional: the first sub-subparagraph of subparagraph (ç) of paragraph 4 of Article 27 states that the field is optional if the code is not in the documents, and the fifth sub-subparagraph states that it is mandatory to select the most detailed code and terminal term if it appears in one of the documents. Paragraph 11 of Article 43 of the Guide states that if documents linked to a device become inconsistent with the class as a result of updating the “Class” field, a revision is issued on the devices with the relevant barcode.

Rejections Caused by Application Design: Limits, Declarations and Grouping

Some rejections are tied not to the content of the document but to how the application is built. The Guide sets quantity and grouping limits for each application type.

  • 5-document limit: Under paragraph 15 of Article 39 of the Guide, a document application contains at most 5 document notifications.

  • 500-device limit: Under subparagraph (ğ) of paragraph 5 of Article 40 of the Guide, Optical, Active Implantable, Class 3, Other Products and 2023/KK-1 & 2023/KK-2 applications contain at most 500 device notifications.

  • 5-device limit: Under subparagraph (d) of paragraph 6 of Article 40 of the Guide, Custom-Made Medical Device and System Procedure Pack applications contain at most 5 device notifications.

  • Single-declaration rule: Under subparagraph (c) of paragraph 5 of Article 40 of the Guide, device applications can be made up only of devices linked to a single declaration.

  • Same GMDN grouping: Under paragraph 7 of Article 40 of the Guide, only devices linked to the same GMDN code are allowed in applications under the older regulations.

  • Same Basic UDI-DI grouping: Under paragraph 8 of Article 40 of the Guide, only devices linked to the same Basic UDI-DI code are allowed in applications under the new regulations, except for custom-made devices.

Rejection Reasons Specific to a Free Sale Certificate Application

The rejection reasons of a free sale certificate application are listed in paragraph 2 of Article 42 of the Guide.

  • Unsuitable device status: Under subparagraph (ı), the application is rejected if it contains a device in “Rejected” or “Unique Product Exists in the System” status.

  • 1000-unit limit: Under subparagraph (j), at most 1000 devices can be added to the application.

  • Mixed regulations: Under subparagraph (k), devices under MDR, IVDR and MDD/AIMDD/IVDD cannot appear together.

  • Different Basic UDI-DI: Under subparagraph (l), the Basic UDI-DI information of the devices must be the same in MDR or IVDR applications.

  • English product name mismatch: Under subparagraph (h), the English product names must match the Turkish product names in ÜTS exactly.

Rejection Reasons Specific to a Period Extension Application

The rejection reasons of MDR and IVDR transition period extension applications are regulated separately in Articles 46 and 49 of the Guide.

  • Submitting the contract text: Paragraph 15 of Article 46 and paragraph 14 of Article 49 of the Guide do not accept an agreement text or audit plans attached instead of the Notified Body Confirmation Letter.

  • More than one document: Paragraph 18 of Article 46 and paragraph 17 of Article 49 state that a request can be made for only one document in a single application.

  • Application without a petition: Paragraph 8 of Article 46 and paragraph 7 of Article 49 state that applications without a petition are not accepted.

  • Inconsistency in evidence documents: Paragraph 10 of Article 46 and paragraph 9 of Article 49 require that there be no inconsistency between the Manufacturer’s Declaration and the notified body letters.

  • Manufacturer information mismatch: Paragraph 11 of Article 46 and paragraph 10 of Article 49 require additional evidence documents that resolve the mismatch to be attached.

Forged and Falsified Documents: Rejection and Market Surveillance

The heaviest consequence arises where there is doubt about the validity of a document. Subparagraph (b) of paragraph 18 of Article 39 of the Guide states that certificates determined to be invalid for reasons other than losing their currency are rejected directly; for documents determined to be forged or tampered with, a market surveillance and inspection process is also started after the rejection. The same subparagraph adds that these actions will also be taken for other certificates with the same document number.

The Correct Order After a Rejection

After a rejection the first reflex is to open a new application; the Guide suggests a different order. Paragraph 16 of Article 39 of the Guide provides that, if the decision is considered contrary to the legislation, re-evaluation can be requested before reapplying by using the “Report Request” screen, selecting “Medical Device Document and Product Registration Transactions” as the “Request Area” and entering the relevant number in the “Medical Device/Document Application Number” field.

Two conditions determine whether this route works. The same paragraph states clearly that requests in which the application number is not entered, and requests that do not cite the legislation or the Guide on the point being objected to, will not be considered. The paragraph also states that the Agency will not be held responsible for applications that are resubmitted for review without being corrected on the basis of the request.

Pre-Application Checklist That Reduces the Risk of Rejection

The list below reduces the 36 reasons above to an order that can be scanned before applying.

  • Document approval route: Determine which of the routes in Articles 8, 12, 15, 21 and 23 of the Guide applies.

  • Translation: Check the translator’s declaration, the stamp and the upload of the Turkish part only, according to the translation paragraphs of the same articles.

  • Dates and revision: Verify the start date and the revision number according to Articles 6, 7 and 20 of the Guide.

  • Document business rule: Compare the combination against Articles 63 to 67 of the Guide and the tables in Annex-81 to Annex-100.

  • Barcode: Verify, under Articles 25, 27 and 30 of the Guide, that the barcode was entered as it appears in the documents and on the smallest package.

  • Name and brand: Check, under the brand and product name subparagraphs of the same articles, that the fields are filled in, in Turkish and consistent with the label.

  • Image: Review the number, format, clarity and file names of the images under paragraph 6 of the same articles.

  • Class and codes: Compare the class, GMDN and, where applicable, EMDN selections with the documents under paragraph 4 of Articles 25 and 27 of the Guide.

  • Application design: Check compliance with the quantity, single-declaration and grouping limits in Articles 39 and 40 of the Guide.

Companies can also run these checks from their own ÜTS company pages by granting user authority to a consultant; the consultant creates and approves the records with the “Medical Device Registration Officer” authority, while the person who signs the application electronically remains the company’s signatory under paragraph 13 of Article 39 of the Guide.

You can find the counterpart of this topic in EU legislation in our English article on MDR labelling requirements.

Ü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