ÜTS Registration Officer Authority
You have decided to work with a consultant and the first question is: what exactly will this person be able to do in my ÜTS account? The answer is written in the legislation, and the boundary is clear.

ÜTS “Medical Device Registration Officer” Authority: Operations That Can and Cannot Be Delegated
You have decided to work with a consultant, and the first question that comes to mind is: what exactly will this person be able to do in my ÜTS account? The answer is written in the legislation and its boundary is not vague. The delegated authority extends up to creating and approving the application, while the electronic signature stays with your company’s signatory.
This page explains what the authority is, where it ends and what happens if it is not opened. The references are to the TİTCK “Guide on the Registration Processes of Medical Devices in the Product Tracking System” (TCKKD-KLVZ-03) and the Regulation on Medical Device Sales, Advertising and Promotion.
Summary of the authorization model
In ÜTS, an application reaches the Agency through two separate actions by two separate people. The first is “Approve”, the second is the electronic signature. The Guide ties these two actions to two separate roles, and this separation also draws the boundary of the consultancy relationship.
Article 39, paragraph eleven of the Guide states that, in a document application, the “Approve” action is performed on the “Document Application Summary” screen that appears after pressing the “Create Application” button, and that only users of the relevant company of the “Medical Device Registration Officer” type can perform this action.
The same rule applies on the device side. Article 40, paragraph five, subparagraph (f) of the Guide states that only users of the company of the “Medical Device Registration Officer” type can perform the “Approve” action on the “Medical Device Application Summary” screen. Article 40, paragraph six, subparagraph (c) repeats the same provision for custom-made medical device and system procedure pack applications.
The authority you open for the consultant is exactly this user type. We do not ask for any other authority type, and we do not need one.
Note the wording: the Guide says users “of the relevant company”. In other words, the registration officer works not from the consultancy company’s own ÜTS account but as a user linked to your company record. Even if the consultant changes, the records stay in your company’s account; there is no data set to be moved, transferred or reclaimed. This is the most practical way to protect your company if the service relationship ends.
Opening authority for a consultant in ÜTS: the route followed in practice
We need to state a limit clearly here. The Guide defines the “Medical Device Registration Officer” user type as a provision and states what a user of this type can do; however, it does not document the names of the user management screens in ÜTS or the click sequence. For this reason, we give the following not as a legal provision but as the route we follow in practice.
- The user is defined from the company’s own page: In practice, the authority is defined not from the consultant’s own account but from the company’s own page in ÜTS. The company both opens and closes the authority.
- The defined type must be correct: Article 39, paragraph eleven and Article 40, paragraph five, subparagraph (f) of the Guide authorize only the “Medical Device Registration Officer” type for the “Approve” action. If a different type is defined, the application cannot be approved.
- Access verification: Once the authority is defined, the first thing we do in practice is to verify that the “Document Application Operations” screen under the “Document” tab, described in Article 39, paragraph two of the Guide, and the “Medical Device Application Operations” screen under the “Medical Device” tab, described in Article 40, paragraph two, open.
- Checking the signatory record: Our second check in practice is that the person who will sign is currently defined in ÜTS. Article 5, paragraph six of the Guide states that, in company transfer and merger processes, the signatories and users defined in ÜTS must be updated so that the company’s ÜTS activities can continue.
We do not guess screen names. Presenting you with a screen name that the Guide does not state as if it were a provision would turn into incorrect information at the first screen update.
Where the authority ends: the e-signature
The authority extends up to the creation and approval of the application. What follows belongs to your company, and this boundary is enforced by the system itself.
Article 39, paragraph twelve of the Guide states that, after the “Approve” action, if there is no violation of procedure or business rules, the application will be created in ÜTS in the “Awaiting Signature” status. Paragraph thirteen continues: an application in the “Awaiting Signature” status is signed electronically by the company’s applicant signatory.
The same flow exists on the device side. Article 40, paragraph five, subparagraph (g) of the Guide states that, for an application to go to the Agency in the “Under Review” status, it must first be signed electronically by the company’s signatory and moved to the “Awaiting Payment” status, and then move to the “Under Review” status once the application fee is paid.
The step after the signature also differs by document type. Subparagraph (a) of Article 39, paragraph thirteen of the Guide states that applications containing the document types mentioned in Articles 6, 7, 10, 11 and 14 move to the “Awaiting Payment” status after being signed and to the “Under Review” status once payment is made and approved. Subparagraph (b) of the same paragraph states that applications other than these document types move directly to the “Under Review” status at the moment they are signed. In other words, applications containing certificates and declarations of conformity have a payment step after the signature; applications made up of documents such as instructions for use or ISO 13485 do not.
For domestic manufacturer documents, the system hardens this boundary even further. Article 13, paragraph one, subparagraph (ç), sub-item 1 of the Guide states: ÜTS allows a document application only if the document in question is signed electronically by the “Responsible Manager” or the “Signatory”.
Why the e-signature is not delegated
Some service providers may ask you for your e-signature. We do not, and there are two reasons, both written in the legislation.
First, the e-signature is an identity instrument bound to a person, and the legislation looks for a name match. Article 9, paragraph two, subparagraph (a), sub-item 2 of the Guide states that, if the name and surname of the signing official appear in writing on the original of the undertaking, the name and surname of the official on the document and the name and surname of the person registered as the “Responsible Manager” or “Signatory” who electronically signs the document must match. Article 13, paragraph one, subparagraph (ç), sub-item 2 of the Guide repeats the same requirement for the declaration of conformity. A signature made with someone else’s e-signature breaks this match from the start.
Second, responsibility for the accuracy of the data already lies with the company. Article 31, paragraph four of the Regulation on Medical Device Sales, Advertising and Promotion states that the accuracy of the information on devices recorded in the system is the responsibility of the sales center that makes the product registration. This is not a responsibility that can be transferred by contract. When the signature stays with the company, there is no ambiguity about who bears the responsibility.
The practical benefit for you is this: you see the application before signing. Every application we approve reaches you in the “Awaiting Signature” status; you are not obliged to sign without checking its content.
Do the signatory and the registration officer have to be the same person?
No. The Guide regulates these two functions in two separate places: the approving party is the registration officer, and the signing party is the signatory. Article 39, paragraph eleven of the Guide defines the former and paragraph thirteen defines the latter.
In small companies, these two functions may be combined in one person; if the company’s signatory is also defined as a registration officer, that person performs both actions. Even then, the role separation in the system does not disappear; it is simply held by the same person.
In consultancy, the separation effectively splits the work in two. The registration officer authority is with us, and the signing authority is with you. This is a split in which the company does not lose control: we prepare and approve the application, and you make the decision to send it.
What happens if the authority is not opened
If the authority is not opened, the file can be prepared but the application is not created. This is a blockage that many companies notice late.
Article 39, paragraph eleven of the Guide locks the “Approve” action to users of the “Medical Device Registration Officer” type. If this action is not performed, the “Awaiting Signature” status in paragraph twelve never arises. If “Awaiting Signature” does not arise, no signature can be made; if no signature can be made, the application cannot move to the “Under Review” status.
The Guide states the result of the chain explicitly. Article 39, paragraph fourteen and Article 40, paragraph five, subparagraph (g) form the same sentence: applications that do not reach the “Under Review” status cannot be evaluated by the Agency review expert.
In other words, even if your documents are complete, your translations are in place and your barcodes are correct, your file never reaches the Agency until the authority is defined. You do not have a pending application; you have no application at all.
What the person you authorize can see and do
The scope of the authority is limited to the three screens described in the Guide. These three are the area in which the consultant actually works.
- Document Application Operations screen: Article 39, paragraph two of the Guide states that, in order to make a document application, the relevant screen is entered through the “Create Document Application” area on the “Document Application Operations” screen under the “Document” tab. Paragraph three states that the application type, and paragraph nine that the documents to be attached to the application, are selected on this screen. The approval action is subject to the authority in paragraph eleven.
- Medical Device Application Operations screen: Article 40, paragraph two of the Guide states that a device application is started from the “Medical Device Application Operations” screen under the “Medical Device” tab. Paragraph five lists the steps from selecting the declaration to selecting the product and, with subparagraph (f), ties approval to the registration officer.
- Report Request screen: Article 6, paragraph seven of the Guide states that, to add a notified body not defined in ÜTS, a request is opened through the “Notified/Conformity Assessment Body Operations” area on the “Report Request” screen. Article 39, paragraph sixteen states that a request for re-evaluation against a rejection or revision decision is likewise opened from this screen.
We do not need any function outside these three screens. We do not ask for access to your company’s commercial data, bank details or signing instrument.
It is also necessary to write what the authority cannot do, because the boundary has two sides. The registration officer authority cannot sign the application; Article 39, paragraph thirteen of the Guide ties the signature to the company’s applicant signatory. It also cannot change the Agency’s decision; Article 39, paragraph eighteen of the Guide states that the validity and currency of certificates that reach the registered status will be queried by the Agency through the notified body or the competent authority that authorizes it. The only thing that can be done against a revision or rejection decision resulting from this query is the request route in paragraph sixteen of the same article.
When personnel change, ÜTS gets blocked
Authorization is not a one-time operation. If personnel changes in the company are left without a counterpart on the ÜTS side, a running process stops.
Article 5, paragraph six of the Guide states that, in company transfer and merger processes, the signatories and users defined in ÜTS must be updated for the company’s ÜTS activities to continue. In other words, if the signatory has left, no application can be signed until the person to replace them is defined in ÜTS.
Some changes are reflected automatically. Article 5, paragraph seven of the Guide states that, when the company’s responsible manager, title and address change, the changes will be updated automatically in ÜTS if the relevant information is updated in ÇKYS. This distinction matters: ÇKYS is sufficient for title and address, but not for signatory and user definitions.
In practice, the only thing we ask of our customers is to notify us in advance of a change of signatory. This is the most common reason an application we have prepared remains unsigned.
Training obligation of the person who registers in ÜTS
The person you authorize also has a competence requirement, and this requirement is written in the Regulation. Article 26, paragraph ten of the Regulation on Medical Device Sales, Advertising and Promotion states that persons who perform medical device registration in the Agency’s registration and information management system on behalf of the sales center must successfully complete the training determined by the Agency.
Article 28/A of the same Regulation also regulates that this competence can be lost.
- Cancellation of the training: Paragraph two of Article 28/A states that, if it is determined that transactions have repeatedly been made in the registration and information management systems contrary to the procedures and principles determined by the Agency, the training received by the persons who make these transactions pursuant to Article 26, paragraph ten will be cancelled.
- Restriction of access to the system: Paragraph one of Article 28/A states that, if the Agency determines that applications have been made to the registration and information management systems with false information and documents, it may restrict the access of the persons or organizations that make these transactions to the relevant systems.
These two provisions also show what question to ask when choosing a consultant. The question is not the price, but whether this requirement is met.
Revoking the authority
That the authority can be revoked is the side of this model that favors the company. Article 39, paragraph eleven of the Guide ties the “Approve” authority to the company’s own users; the user list belongs to the company’s own record.
Article 5, paragraph six of the Guide writes the updating of users defined in ÜTS as the company’s obligation. In other words, it is the company that adds and removes the user; the consultant’s approval or participation is not required.
In practice this means: when the service ends, or when the relationship ends for any reason, you do not need to apply to anyone to remove the consultant’s user definition. You close the authority where you opened it. Because the Guide does not state the name of this screen, we do not give a screen name here; however, the two provisions above show that the process is under the company’s control.
There is also a contractual side. When the authority is revoked, the records and applications created up to that day remain in the company’s ÜTS account; these are the company’s records, not the consultant’s.
Three benefits of authorization for the company
Delegating authority is not a convenience but an arrangement that narrows the surface for error. It has a concrete counterpart in three places.
- Correct completion of mandatory fields: Article 27, paragraph one of the Guide states that the information to be entered in a device registration under MDR is grouped under the headings “Identifying Information”, “Import/Manufacture Information”, “Classification Information”, “Product Documents”, “Product Images”, “Features”, “Dimension Information”, “Storage/Use Condition Information”, “CMR and/or Endocrine Disrupting Substance Information” and “Application Status”. Paragraphs two to eleven of the same article define the fields under these headings one by one, and most of them are marked “a field that must be selected in ÜTS”.
- Selecting document labels appropriate to the class: Articles 63 to 67 of the Guide define a separate document business rule annex for each regulation and each class; these annexes are Annex-81 to Annex-100 of the Guide. A document is held with the class, regulation and annex triple, and it must match the combination permitted for the device’s class. Barcode and UDI data are handled within the same discipline.
- Objection citing the legislation if a rejection comes: Article 39, paragraph sixteen of the Guide states that re-evaluation can be requested from the “Report Request” screen against a rejection or revision decision; however, the same paragraph sets two conditions. Requests in which the application number is not entered, or in which no reference is made to the legislation or Guide concerning the point objected to, are not evaluated.
What we promise is not an outcome but a method: filling in the fields by showing their source, linking the document to the class with the appropriate label, and, in case of an unfavorable decision, opening the objection with its number and citation. We do not give a commitment on when or how an application will be concluded; the Guide does not contain such a commitment in any of its articles. See also the declaration of conformity and CE marking article for the conformity declaration step.
To get started, you can request a quote for ÜTS registration consultancy.
