
MDR and IVDR Parameter Cards: ÜTS Class and Document Rules
The MDR and IVDR parameters in the ÜTS Registration Manual: the class field options, the class-based document business rules and the choice of Basic UDI-DI. A Medex ÜTS guide.
When you open an MDR record and an IVDR record side by side in ÜTS, you see that the screens are not the same: a field asked on one side is missing on the other, the risk class lists are of different lengths, and two fields where you give the same answer open different sets of documents. In the sector the phrase "parameter card" is used to describe this difference; but when your application is rejected, that phrase never appears in the reason for rejection.
There is a simple reason: the term "parameter card" does not exist in the Manual on Registration Procedures of Medical Devices in the Product Tracking System (Tıbbi Cihazların Ürün Takip Sistemine Kayıt Süreçlerine İlişkin Kılavuz). The Manual does the same job with the concepts of "data fields", "document business rules" and "conformity assessment procedures". Leaving the sector phrase aside, this page compares, for the MDR and the IVDR, the fields that actually govern the assessment, and shows at which point a wrong field choice stops an application. The sources are the Manual named above and the Medical Device Regulation (Tıbbi Cihaz Yönetmeliği) published in the Official Gazette No. 31499 (bis) of 2/6/2021.
The Manual uses the word "parameter" in two narrow senses
Searching for the term as it stands is the shortest way to understand what is expected. Article 43(1) of the Manual says that, where a device registered in ÜTS under the same barcode has records belonging to different firms and there are data differences between these records, the "product parameters (data fields)" in the relevant device records must be made identical and consistent in ÜTS before the first device application to be made under Article 40 of the Manual. Here the Manual gives its own definition in brackets: a parameter is a data field.
The second use is narrower. Article 27(9)(b) of the Manual states that storage and use conditions are added to ÜTS by entering parameters through the "Add Storage/Use Condition" ("Saklama/Kullanım Koşulu Ekle") screen, and lists the types: Storage Environment Temperature, Humidity, Altitude and Pressure, and Use Environment Temperature, Humidity, Altitude and Pressure, and Special Storage Conditions. Article 30(9)(b) of the Manual sets up the same structure on the IVDR side.
Apart from this, the Manual does not use the word "parameter" in the context of a device record. So what this page describes is the real counterpart in the Manual of the whole the sector calls a "parameter card": the mandatory fields on the device registration screen and the document business rule those fields trigger.
The centre of gravity of the assessment lies in three fields
Not all of the dozens of fields on the registration screen carry equal weight. The Manual says directly which ones require assessment by the Agency. Article 43(4)(d) of the Manual states that, for records with the same barcode, requests relating to fields other than those requiring Agency assessment, such as "Class", "GMDN" and "EMDN", are corrected automatically by ÜTS if the firms accept unanimously. Point (e) of the same paragraph states that if the request relates to one of these three fields, the request will be submitted to the Agency's assessment in "Under Review" ("İncelemede") status.
This trio is the backbone of the "Classification Information" heading of the MDR and IVDR registration screens. Article 27(4) of the Manual lists the fields under this heading on the MDR side as Class, GMDN, Branch Type Code, EMDN Term and Selected EMDN Term. Article 30(4) of the Manual lists the same five fields on the IVDR side. The heading is the same; the difference in content starts at the "Class" field.
The Class field offers seven options in the MDR and thirteen in the IVDR
Article 27(4)(a)(3) of the Manual lists the risk classes that can be selected under the MDR: Class-I Other (not sterile and without a measuring function), Class-Ir (reusable surgical instruments), Class-Im (with a measuring function), Class-Is (with a sterile function), Class-IIa, Class-IIb and Class-III.
Article 30(4)(a)(3) of the Manual lists the IVDR options: Class A Sterile, Class A, Class B, Class C, Class D, Self-Test Device (Class B), Self-Test Device (Class C), Self-Test Device (Class D), Near-Patient Test Device (Class B), Near-Patient Test Device (Class C), Near-Patient Test Device (Class D), Companion Diagnostic Device (Class C) and Companion Diagnostic Device (Class D).
The difference is not only in the number. In the IVDR list, the risk class and the manner of use are squeezed into a single choice: "Class C" and "Self-Test Device (Class C)" are separate options, and although they have the same risk class, they are tied to different business rules. On the MDR side, the manner of use is carried not in a separate field but inside the class name (Class-Is, Class-Im, Class-Ir).
How classification is carried out is a separate subject, and the Manual refers it to other articles: Article 27(4)(a)(4) of the Manual refers to Article 56 of the Manual for the MDR classification rules, and Article 30(4)(a)(4) refers to Article 57 of the Manual for the IVDR rules.
The document business rule runs automatically after the class selection
The Class field is the most expensive field of the record, because it determines which documents you can link. Article 66(1) of the Manual says that, for a device registration notification under the MDR, according to the type and risk class of the device, the appropriate one of the documents in "Registered" ("Kayıtlı") status in ÜTS and mentioned in Articles 7, 11, 17, 20, 22, 23 and 24 of the Manual must be linked to the device.
Paragraph 2 of the same article explains the mechanism: this linking is carried out according to the document business rules determined by the type and risk class of the device and on the basis of the conformity assessment procedures mentioned in Article 61 of the Manual. Paragraphs 1 and 2 of Article 67 of the Manual make the same statements on the IVDR side; the only difference is that the reference for conformity assessment procedures is to Article 62 of the Manual.
So the document list you see on the screen is not a menu of choices. The class and type of the device first determine which conformity assessment procedure applies, and that in turn determines which set of documents will be looked for.
There are six separate business rule sets in the MDR and seven in the IVDR
Article 66 of the Manual distributes the MDR business rules across separate annexes by risk class. Paragraph 3 points to Annex-88 for Class-I Other, Class-Is, Class-Im and Class-Ir devices; paragraph 4 to Annex-89 for Class-IIa; paragraph 5 to Annex-90 for Class-IIb excluding implantable devices and the devices under Rule 12 in MDR Annex VIII; paragraph 6 to Annex-91 for implantable Class-IIb devices other than sutures, staples, dental fillings, dental braces, dental crowns, screws, wedges, plates, wires, pins, clips and connectors; paragraph 7 to Annex-92 for Class-IIb devices under Rule 12; and paragraph 8 to Annex-93 for Class-III.
Article 67 of the Manual defines seven sets on the IVDR side. Paragraph 3 points to Annex-94 for Class A or Class A Sterile; paragraph 4 to Annex-95 for Class B or Class C; paragraph 5 to Annex-96 for Class D; paragraph 6 to Annex-97 for Self-Test Device (Class B) or Near-Patient Test Device (Class B); paragraph 7 to Annex-98 for Self-Test Device (Class C) or Self-Test Device (Class D); paragraph 8 to Annex-99 for Near-Patient Test Device (Class C) or Near-Patient Test Device (Class D); and paragraph 9 to Annex-100 for Companion Diagnostic Device (Class C) or Companion Diagnostic Device (Class D).
The practical consequence is this: in the IVDR, two devices of the same risk class are subject to different business rules if one is near-patient and the other is a companion diagnostic. A record in which the class is chosen on the basis of "the risk is the same, it makes no difference" gets stuck at the document screen.
The documents field does not open until the class is selected
The order is built into the system. Article 27(5)(a)(3) of the Manual says that, before selecting a document in the "Documents" field, the class of the relevant device must have been selected on the ÜTS registration screen, and that the selection in this field is made from among the documents that can be selected according to the class of the device. Sub-point (2) of the same point states that the documents to be added are selected according to the appropriate one of the business rules in Article 66 of the Manual and from among the documents already in registered status in ÜTS as a result of the application made under Article 39 of the Manual.
This directly explains a very common mistake: a document does not appear in the device record until it reaches "Registered" status in ÜTS. Having uploaded the document is not enough; the document application under Article 39 of the Manual must have concluded.
The Basic UDI-DI selection depends on the document selection
The third link in the chain is the Basic UDI-DI. Article 27(5)(c)(3) of the Manual says that, before selection is made on the "Select Basic UDI-DI" ("Temel UDI-DI Seç") screen, the documents related to the relevant device and to the Basic UDI-DI of the device (the EU Declaration of Conformity, the EU Certificate) must have been selected from the "Documents" field according to the document business rule in Article 66 of the Manual. Sub-point (4) of the same point states that selection can be made only from among the Basic UDI-DI numbers associated with the selected EU Declaration of Conformity, and that more than one selection cannot be made. Article 30(5)(c) of the Manual sets up the same dependency on the IVDR side, with reference to Article 67 of the Manual.
The order is: class, then document, then Basic UDI-DI. If you chose the class wrongly, you stop not at the third step but at the second, and you do not see why.
The Characteristics heading asks different questions in the two regulations
This is where the difference the sector calls a "parameter card" is most visible. Article 27(7) of the Manual on the MDR side and Article 30(7) on the IVDR side list the fields under the "Characteristics" ("Özellikler") heading. Some fields are common: point (ç) in both includes the MRI Safety Information and the shelf life, calibration, maintenance, sterile packaging and sterilisation method fields.
The fields that exist in the MDR card but not in the IVDR card are these:
Latex and Phthalate/DEHP: Points (d) and (e) of Article 27(7) of the Manual make these two questions mandatory in the MDR record.
Nanomaterial: Point (g) of the same paragraph asks whether the device contains nanomaterial; point (ğ) asks, if "Yes", for the type of nanomaterial with the options Particle, Aggregate, Agglomerate and Unknown.
Whether it is implantable: Point (h) of the same paragraph makes this field mandatory. This field is not only information; the Annex-91 business rule in Article 66(6) of the Manual is specific to implantable Class-IIb devices.
Medicinal product and human blood component: Point (u) of the same paragraph asks whether the device contains a substance considered a medicinal product, and point (ü) whether it contains a medicinal product derived from human blood or plasma.
Fields specific to the IVDR card require a separate set of information
In the IVDR record, questions come up that have no counterpart in the MDR:
Content of microbial origin: Article 30(7)(p) of the Manual asks whether the device contains cells or substances of microbial origin.
Whether it is a new type of device: Point (ş) of the same paragraph makes this field mandatory and gives its definition. A device is regarded as a "new device" if a device of this kind for the relevant analyte or other parameters has not been continuously available in Türkiye or EU member states during the last three years, or if the procedure involves an analytical technology that has not been continuously used in connection with a specific analyte or other parameters during the last three years.
Whether it is for self-testing or near-patient testing: Point (t) of the same paragraph makes this field mandatory, and its sub-point (3) requires that, if the device is a self-test or near-patient test device, this indicator be present on the label and/or the sales packaging and in the instructions for use, and that the field be selected as "Yes".
Product image standards: Point (z) of the same paragraph states that, when the Sağlık Market or SGK reimbursement field is selected as "Yes", at least three photographs are required for each device, and for devices with inner and outer packaging, at least three photographs for each packaging type.
There is also a warning on the sales legislation side. Article 30(7)(u)(4) of the Manual states that the current Annex-3 of the Medical Device Sales, Advertising and Promotion Regulation (Tıbbi Cihaz Satış, Reklam ve Tanıtım Yönetmeliği) contains no device within the scope of the IVDR, and that selecting the relevant field as "No" is therefore mandatory. On the MDR side, the same question is a real choice; Article 27(7)(z) of the Manual lists the Annex-3 devices one by one.
It must also be written that the source is internally inconsistent in one place: point (çç) of Article 30(7) of the Manual asks whether the device was manufactured by another manufacturer and says that, if "Yes", the field in point (dd) will open; on the other hand, sub-point (1) of point (dd) states that the field is mandatory "when point (cc) is selected as Yes". The Manual does not reconcile these two references. On the MDR side the same structure is consistent: Article 27(7)(gg) of the Manual asks the question, and point (ğğ) defines the field in which the manufacturing firm is selected.
The CMR question refers to a different annex in the two regulations
The last content heading of the registration screen also diverges. Article 27(10)(a) of the Manual shows that in the MDR record the question is asked whether the device contains CMR and/or endocrine-disrupting substances "as specified in Annex I 10.4.1". Article 30(10)(a) of the Manual asks the same question in the IVDR record "as specified in Annex I 10.3". Two different annex numbers for the same device family mean two different thresholds; copying a single declaration from the manufacturer into both records does not give the correct result.
The list of headings at the top of the record is also different. Article 27(1) of the Manual lists the headings on the MDR screen as ten. Article 30(1) of the Manual gives the same headings for the IVDR, but the paragraph numbering is different: "Application Status" ("Başvuru Durumu") is regulated in paragraph 11 on the MDR side and in paragraph 12 on the IVDR side.
A wrong field choice stops the application at three separate points
A wrong choice does not always come back as a rejection; most often you get stuck at an earlier point.
The first point is the notification stage. Article 40(5)(g) of the Manual says that, if there is nothing contrary to the procedure and business rules in the device notification belonging to the application, the application will be created in "Awaiting Signature" ("İmza Bekliyor") status. If there is a violation, the application is not created at all. Article 39(12) of the Manual sets up the same logic on the document side.
The second point is grouping. Article 40(8) of the Manual states that, in device applications under the New Medical Device Regulations (except custom-made devices), applications are allowed only for devices linked to the same Basic UDI-DI code. Point (c) of paragraph 5 of the same article states that medical device applications can be formed only from devices linked to a single declaration.
The third point is the review stage. Article 27(2)(b)(4) of the Manual states that a device application made for a device record whose barcode has not been entered into ÜTS as it appears in its technical documents will end negatively; sub-point (6) of point (f) of the same paragraph states that a device application whose product name does not make clear what the device is, is incomplete, is not in Turkish or does not match the label will be rejected. Article 27(4)(b)(5) of the Manual, in turn, makes it mandatory that the information in the description of the GMDN code the device is matched to be consistent with product characteristics such as whether the device is single-use and whether it is sterile; the same rule is repeated for the IVDR in Article 30(4)(b)(5) of the Manual.
When a rejection or revision decision arrives, reapplying is not the first option. Article 40(9) of the Manual says that, if the decision is thought to be contrary to the legislation, before making a new device application a re-evaluation of the decision can be requested through the "Submit Request" ("Talep Bildir") screen by selecting the area "Medical Device Document and Product Registration Procedures" and entering the Device Application Number; and that the request must refer to the legislation and Manual provisions on the point objected to.
A field mismatch in records with the same barcode holds the application
If you are not the only firm importing a device, the application may not open even when your own record is correct. Article 43(2) of the Manual says that, in the event of a mismatch between the data fields in device records with the same barcode, the firm will first create a request application according to the work steps in Article 44 of the Manual.
Paragraph 3 of the same article defines the process: the request is submitted for the opinion of the other firms that have records with the same barcode; at this stage the request is in "Opinions of Other Firms Awaited" ("Diğer Firmaların Görüşleri Bekleniyor") status, the period for giving an opinion is 5 days, and firms that do not give an opinion within this period are deemed to have accepted the request. This period written in the Manual is not a commitment but a procedural rule; the Manual gives no commitment on how long it takes for the request to conclude.
What we do on field selection, and where responsibility lies
MEDx Kurumsal Danışmanlık decides the field selections one by one before registration, within medical device ÜTS registration consultancy. The concrete outputs are:
Field map: A list, filled in device by device according to Articles 27 and 30 of the Manual, of the mandatory fields on the MDR and IVDR registration screens for your device portfolio.
Class-document consistency check: Verifying in advance which business rule in Article 66 or 67 of the Manual the selected class triggers and whether your document set satisfies that rule.
Document-Basic UDI-DI chain: Checking the relationship between the EU Declaration of Conformity and the Basic UDI-DI according to Article 27(5)(c) of the Manual, and a request list prepared to obtain missing information from the manufacturer.
Application grouping: Building application packages based on Basic UDI-DI, in line with Article 40(8) of the Manual.
Same-barcode mismatch file: Preparing the request to be opened under Articles 43 and 44 of the Manual, and its grounds.
What we cannot do is clear too. The final decision on the risk class of the device is made by the manufacturer; the classification rationale is part of the technical documentation, and a consultant cannot produce this rationale in the manufacturer's place. For the GMDN code, Article 27(4)(b)(8) of the Manual states that GMDN Agency data will be accepted as correct and valid in queries; the code comes from the manufacturer's documents. The manufacturer obtains the Basic UDI-DI from the issuing entity. The answers to fields such as CMR, nanomaterial, microbial content and analyte information also come from the manufacturer's technical documentation; we can place this information in the correct field, but we cannot produce it.
The way of working is this: your firm defines a user authorisation for us from its own ÜTS firm page, we create the records with the "Medical Device Registration Operator" ("Tıbbi Cihaz Kayıt Elemanı") authorisation, and the person who electronically signs the application remains your firm's signatory.
