top of page

ÜTS Document Registration Consultancy

In UTS, a document is known not by its name but by three labels: the device class, the regulation the document belongs to, and the annex under which the conformity assessment was carried out.

ÜTS Document Registration Consultancy

UTS Document Registration Consultancy: Document Type Selection and Correct Registration

Document registration and document application are two separate processes

This is the point companies most often confuse. Entering the document into UTS is half the job; forwarding the entered notification to the Authority is a separate step carried out on a separate screen.

Article 8(8) of the Guide states that the steps for document registration and update applications are described in Article 39. Article 39(2) of the Guide provides that the application is made from the "Create Document Application" field under the "Document Application Processes" screen, under the "Document" tab in UTS. A company that saves the notification and skips this step may wait for months believing the document is under review.

The result of this distinction is visible on the device side. Article 63(1) of the Guide, for MDD, and Article 66(1), for MDR, require that for a device registration notification, the suitable document among those in "Registered" status in UTS, following an application under Article 39, is linked to the device. Until the document reaches "Registered" status, it is not listed among the documents selectable on the device registration screen.

Which of the four document application types should be selected

The type you choose when creating the application determines which documents can be added to it. If the wrong type is selected, the document you are looking for does not appear in the list at all, and companies often assume the document was not registered in the system.

Article 39(4) of the Guide lists four application types.

  • Document application for importer companies: under the fifth paragraph of the same article, this type is selected for the document types mentioned in Articles 8, 12 and 15 of the Guide. The EC certificate of a foreign manufacturer, the EU certificate, the declaration of conformity, the EU declaration of conformity and the SIP declaration belong to this group.
  • Document application for other types, for importer or manufacturer companies: under the sixth paragraph, this type is used for the instructions for use, the intended use form, ISO 13485, the Domestic Goods Certificate and the Authorised Distributorship Certificate.
  • E-signed document application for manufacturer companies: the seventh paragraph links the document types mentioned in Articles 9, 13 and 16 of the Guide, namely the certificates and declarations of a domestic manufacturer for its own product, to this type.
  • Document application under Announcement No. 2023/KK-1: the eighth paragraph provides that transition period applications under Articles 47 and 50 of the Guide are made with this type.

The screen behaviour after selecting a type is also defined. Article 39(9) states clearly that the "Select Document" screen lists only the documents suitable for the selected application type. If you cannot see your document in the list, the first thing to check is not the registration of the document but the application type you selected.

How a document is defined in UTS: class, regulation and annex

UTS document business rules assess the risk class of the device together with the regulation and annex information of the document. Of two certificates issued by the same notified body, one may be linkable to your device while the other may not, because their annex information differs.

Article 63(3) to (5) of the Guide refer, for MDD classes, to the business rules in Annexes 81, 82 and 83; Article 66(3) to (8) refer, for MDR classes, to the business rules in Annexes 88 to 93. These annexes show line by line which declaration and certificate combinations are valid for each class.

For MDR Class IIb and Class III, a type examination alone is not enough: the business rules in Annexes 90, 91, 92 and 93 require that an EU certificate under Regulation 2017/745 with an attached Annex X Type Examination be accompanied by an EU certificate with an attached Annex XI Part A Production Quality Assurance or Annex XI Part B Product Verification.

For MDR Class IIa the table is different: Annex 89 accepts on its own an EU certificate with an attached Annex XI Part A or Annex XI Part B for Class IIa. It also shows that an EU certificate with an attached Annex IX Chapters I and III Quality Management System Assessment may optionally be accompanied by an EU certificate with an attached Annex IX Chapter II Technical Documentation Assessment.

For MDD Class III, design examination is required: Annex 83 provides that an EC certificate under Directive 93/42/EEC with an attached Annex 2 Full Quality Assurance System must be accompanied by an EC certificate with an attached Annex 2 Article 4 Design Examination. The same annex defines two further combinations: a certificate with an attached Annex 3 Type Examination accompanied by a certificate with an attached Annex 4 EC Verification or Annex 5 Production Quality Assurance.

The first thing we do before taking the document registration is to compare the set of certificates you hold with the business rule table for the device class. If a leg is missing, it must be seen at the request stage with the manufacturer, not at the document registration stage.

The output of this comparison is concrete: we prepare a matching list for each device group showing which documents are mandatory and which optional, which document is registered with which annex information, and how a missing item is requested from the manufacturer. The request letter to your manufacturer is built on this list. Specifying which certificate issued under which annex is required, rather than writing "send your certificate", reduces the number of rounds in correspondence with overseas parties.

Approved originals required before the document application

There are three things that must be available before we open the application file. Creating a notification without completing them is the shortest route into a correction cycle.

  • Complete certificate: Article 6(6) of the Guide requires the EC certificate, and Article 7(6) the EU certificate, to be uploaded and submitted to the Authority complete with all annexes and additional pages. The first page of a certificate often does not contain the product scope; the scope is in the annexes.
  • Approved original of the declaration and, where applicable, the power of attorney: Article 12(1) of the Guide lists the approval routes accepted for declarations of conformity and EU declarations of conformity. Article 12(7)(b) provides that for manufacturers not established in an EU member state or in Türkiye, the agreement between the manufacturer and the EU Authorised Representative and/or the power of attorney is uploaded to the "Power of Attorney" field.
  • Revision number and revision date: Article 6(4) and (5) of the Guide show that the revision information directly affects the document start date and the document number. If this information is not written on the certificate, we obtain written confirmation from the manufacturer.

Operations within the scope of the service

The division of work in document registration consultancy is defined from the start. From your company page in UTS you grant us the "Medical Device Registration Officer" authority; the choice of approval route, field-by-field data entry, business rule checks and the creation of the application are carried out by us. Article 39(11) of the Guide provides that only users of the relevant company with the "Medical Device Registration Officer" type may create and approve an application.

The signature remains with you. Article 39(13) provides that an application in "Awaiting Signature" status is signed electronically by the company's authorised signatory. E-signature is not delegated, and we do not ask for it to be delegated; the person who views the content of the application and signs it is your company's authorised signatory. Responsibility for the accuracy of the data in the uploaded documents also remains with your company.

Article 39(13)(a) provides that applications containing documents of the types mentioned in Articles 6, 7, 10, 11 and 14 of the Guide move to "Payment Pending" status after signature, and to "Under Review" once payment is approved. Under (b), other document types move directly to "Under Review" when signed. Article 39(14) provides that applications that do not reach "Under Review" cannot be evaluated by the Authority's review expert.

Rules for writing the certificate number

How the certificate number is combined with the revision number may look like a small detail, but when the information entered into UTS does not exactly match the information in the document, the review gets stuck at that point. Articles 6(2) and 7(2) of the Guide state clearly that the information entered into UTS must be the same as that in the certificate.

If the revision number is shown together with the document number: Article 6(5) and Article 7(5) of the Guide provide that in this case the certificate is recorded together with its revision number, giving the format XXXXX.Rev.1 as an example. The same rule is repeated for ISO 13485 in the third paragraph of Article 20.

If the document has been revised: Article 6(4) and Article 7(4) provide that the revision date is entered as the document start date. For ISO 13485 the same provision is in the second paragraph of Article 20.

If there is no revision and no date is stated: the same paragraphs provide that in this case the most recent issue (signature) date shown on the certificate is entered as the document start date.

Validity periods differ by document type

The end date entered at document registration is subject to a set of rules independent of what is written on the document. The periods below are the maximum validity periods the legislation gives to the documents; they have no bearing on how long the work will take.

  • Old-regulation EC certificates: Article 6(3) of the Guide states that, for EC certificates under the old regulations, excluding the EC Verification Certificate and the EC Type Examination Certificate, validity may not exceed 5 years. The same paragraph provides that validity may be extended, at the manufacturer's request and based on re-assessment, by further periods of not more than 5 years each.
  • EU certificates: Article 7(3) of the Guide states that EU certificates issued under the new regulations remain valid for the period stated on the certificate, not exceeding 5 years, and for as long as no change or update is made to the certificate during that period.
  • ISO 13485: Article 20(5) of the Guide states that for such documents the validity period may not exceed 3 years.
  • Additions to a certificate: the third paragraphs of both Article 6 and Article 7 provide that any addition to a certificate remains valid for as long as the certificate to which it was added remains valid.
  • Domestic Goods Certificate: this document is outside the list above and has an annual calendar. Article 22(5) of the Guide states that its validity period is one year from the date of issue.

If the notified body is not defined in UTS, the application does not proceed

If you cannot select the body that issued the certificate when opening the document registration, the problem is not on your side. Paragraphs 6(7) and 7(7) of the Guide treat this situation as a separate step, which must be completed before document registration.

Under those paragraphs, if the notified body that issued the certificate is not defined in UTS, a request is opened from the "Notified/Conformity Assessment Body Processes" field using the "Submit Request" screen in UTS. The Authority checks through the NANDO notified bodies query site; if the body is confirmed as a notified body authorised under the relevant legislation, it is added to UTS and defined according to the regulations it is authorised for.

The second case is more subtle: the body may be registered in UTS, but may not have an authority defined for the regulation your document belongs to. The same paragraphs make this a request matter too. Before starting the document registration, we check both the existence of the body and its authority for the regulation.

Mandatory and optional document distinction defines the scope

It is not necessary to prepare the whole document set with the same urgency. The Guide explicitly classes some documents as optional and states that their rejection does not affect the registration status of the device.

  • Authorised Distributorship Certificate: Article 23(9) of the Guide states that this document is not a document that must be uploaded to UTS, and that even if the document registration falls into rejection for any reason, the devices linked to it remain in registered status.
  • ISO 13485: Article 21(9) of the Guide repeats the same provision for the document named "Quality Management Certificate – ISO-13485".
  • Domestic Goods Certificate: Article 22(9) of the Guide provides that, even if the registration of this document falls into rejection, the linked devices remain registered.
  • Catalogue: Article 24(2) of the Guide states that uploaded catalogues are recorded in UTS without being checked by the review expert.

This distinction lets us plan which document goes with which sequence and in which application. Dealing with optional documents before the mandatory legs are complete delays device registration.

Number of documents that can be included in one application

The limit is clear. Article 39(15) of the Guide states that a document application will contain at most 5 document notifications. The same limit is repeated in Article 8(7) and Article 12(5).

For companies with many certificates, this limit directly affects application planning. Rather than grouping documents randomly in fives, we bring together in the same application the documents that will be used together in a device registration, so that a delay in one group does not hold up other devices. We set up application grouping on this logic.

The EU Authorised Representative field cannot be left empty

For EU declaration of conformity notifications of manufacturers not established in an EU member state or in Türkiye, this field is mandatory and cannot be left blank.

The field is mandatory: Article 12(7)(a) of the Guide states that for EU Declaration of Conformity (MDR/IVDR) registration notifications of these manufacturers, entry in the "EU Authorised Representative" field on the UTS registration screen is mandatory.

What is uploaded to the Power of Attorney field: paragraph (b) of the same article provides that the agreement between the manufacturer and the EU Authorised Representative and/or the power of attorney is uploaded; alternatively, the output from the EUDAMED website's actor screen, on which the authorised representative's details are clearly visible, may also be uploaded.

No apostille is required: paragraph (c) clearly states that the original of the document together with its sworn Turkish translation is uploaded to the "Power of Attorney" field, and that no apostille or embassy or consulate approval is required on the original power of attorney. The first sub-item of the same paragraph provides that if a EUDAMED output is uploaded, a sworn Turkish translation does not additionally need to be uploaded.

The reverse is also defined. Paragraph (d) of the same article provides that manufacturers established in an EU member state or in Türkiye may not appoint an EU Authorised Representative; this obligation applies only to manufacturers established outside. For a German manufacturer, trying to fill this field is not a problem to be solved but a wrong assumption.

Certificate query after registration

The job is not finished when the document reaches "Registered" status. Article 39(18) of the Guide provides that where an EC certificate or EU certificate is included in an application and the assessment concludes positively, the validity and currency of the certificates that reach registered status will be checked by the Authority through the notified body that issued them, or the competent authority that authorised that body.

Two separate actions depend on the result of this check. Paragraph (a) of the same article provides that certificates found not to be current will be subject to a 45-day revision process; exceptionally, 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 process applies instead of the 45-day revision. These periods are the times the legislation gives the company to update the document.

Paragraph (b) provides that certificates found not to be valid for reasons other than being out of date will be subject to direct rejection, and that for documents found to be forged or altered, the post-rejection market surveillance and inspection process will also be initiated.

The common sentence in both paragraphs is critical for companies with a portfolio: these actions are carried out for all certificates linked to the same document number that are registered in UTS and are not current. In other words, one certificate losing its currency affects your other registrations under the same number at the same time. Tracking the document portfolio by certificate number is therefore part of the after-registration service.

What is open if the decision is negative

When a rejection or revision decision arrives, the first reflex is to reapply; the Guide sets out another route before that. Article 39(16) of the Guide provides that where a rejection or revision decision for one or more document notifications in an application is considered contrary to the regulation and the Guide, a re-evaluation of the decision may be requested through the "Submit Request" screen in UTS before reapplying.

The format of this request is also defined. Under the same paragraph, the "Request Field" is "Medical Device Document and Product Registration Processes" and the application number is entered in the "Medical Device/Document Application Number" field. The request must refer to the regulation and Guide provisions relating to the matter being contested. The same paragraph makes clear that requests in which the application number is not entered or which contain no reference to a provision will not be taken into consideration.

The same route is open for decisions that give a 3-day update period. Article 39(17) of the Guide provides that if an "Request Update" decision is considered erroneous, a request may be opened in the same way before the update is carried out. Both paragraphs also state that the Authority is not responsible for files reapplied or updated without the request being corrected. For this reason we write objection texts with provision references; an objection without a reasoned basis is not taken into consideration and only delays the file.

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