top of page

UDI-DI and Barcode Rules

You are holding a box; it bears several barcodes, a reference code and sometimes a separate UDI line. Which of them to use for the ÜTS registration

UDI-DI, Basic UDI-DI and Barcode: Which Number Is the ÜTS Registration Made With?

You are holding a box; it bears several barcodes, a reference code and sometimes a separate UDI line. Which of them to use for the ÜTS registration, whether a new number will be needed later, and where the Basic UDI-DI fits among them are the most confused points of the registration process.

Based on the relevant articles of the TİTCK Guide, this page covers, one by one, the choice of barcode organisation, which package's barcode the registration is made with, the distinction between primary and secondary product numbers, the difference between UDI-DI and Basic UDI-DI, and all of the changes that require a new UDI-DI.

Choosing the Barcode Organisation / UDI Issuing Entity

The name of the field varies by framework: it appears as "Primary Barcode Organisation" on the old regulation screen and as "UDI Issuing Entity" on the MDR and IVDR screens. Both are mandatory, and the standard under which the number of the device was allocated is selected.

The third sub-item of subparagraph (a) of paragraph 2 of Article 25 of the Guide states that the barcode organisations and standards authorised under the Old Medical Device Regulations are GS1, HIBCC and ICCBBA; subparagraph (a) of paragraph 3 of Article 26 defines the same three organisations for SIP records under the old regulations. On the side of the new regulations one organisation is added to the list: the third sub-item of subparagraph (a) of paragraph 2 of Article 27 of the Guide states that the UDI issuing entities authorised under the MDR are GS1, HIBCC, ICCBBA and IFA. The same four organisations are listed in subparagraph (a) of paragraph 4 of Article 30 for IVDR device records and of Article 28 for MDR SIP records.

  • GS1: Valid under the old regulations, the MDR and the IVDR.

  • HIBCC: Valid under the old regulations, the MDR and the IVDR.

  • ICCBBA: Valid under the old regulations, the MDR and the IVDR.

  • IFA: Can be selected only in records under the MDR and the IVDR.

Choosing the Organisation for Custom-Made Devices

The same list of four is used in records of custom-made medical devices (CMD). The third sub-item of subparagraph (a) of paragraph 10 of Article 29 of the Guide states that the barcode organisations and standards registered in ÜTS and authorised for CMDs are GS1, HIBCC, ICCBBA and IFA. The fourth sub-item of the same subparagraph also lists the official websites of these organisations.

The difference here is that most CMDs have no barcode at all. For this possibility the Guide defines a separate option, covered below.

Which Package's Barcode Is the Registration Made With?

The Guide gives a single answer to this question: the smallest package. The sixth sub-item of subparagraph (b) of paragraph 2 of Article 25 of the Guide states that, in principle, the device is registered in ÜTS with the barcode of the smallest package placed on the market (the unit package or single package), and therefore the barcode allocated to the smallest package of the device placed on the market is entered in this field. The same provision is repeated word for word in the sixth sub-item of subparagraph (b) of paragraph 2 of Article 27 for the MDR and of Article 30 for the IVDR.

Multi-package barcodes are not lost; they are simply left for later. The same sub-item states that the barcode or barcodes of the sales package or packages containing several products, formed by putting together several of the devices registered with the barcode allocated to the smallest package, will be added, together with their content quantities, to the "Market Placement Information" field on the ÜTS screen of the relevant device after the ÜTS device registration is completed.

Paragraph 1 of Article 36 of the Guide describes this process: after the device reaches "Registered" status, associating the barcodes of boxes/packages and containers holding multiple products with the single-product barcode (Primary Product Number or UDI-DI Number) is done through the "Add Market Placement Information" screen. Instead of trying to enter the carton barcode at the time of registration, you need to complete the registration and add it afterwards.

The Barcode Is Entered Exactly As It Is

No operation such as correction, space removal or adding a prefix can be made on the barcode. The third sub-item of subparagraph (b) of paragraph 2 of Article 25 of the Guide states that the barcode allocated to the device under standards such as GS1, HIBCC or ICCBBA must be entered into the system exactly as it is, without any change. The same rule is repeated in the third sub-item of subparagraph (b) of paragraph 2 of Article 27 for the MDR and of Article 30 for the IVDR.

The most frequent mistake in practice is copying only a part of the human-readable portion of the barcode seen on the label or dropping the leading characters. Since the system compares the barcode with other records and documents, such a shortening directly produces a mismatch.

An Application Whose Barcode Does Not Match the Label Ends Negatively

The consequence is written expressly in the Guide. The fourth sub-item of subparagraph (b) of paragraph 2 of Article 25 states that the device application made under Article 40 for a device record whose barcode is not entered into the system as it appears in the technical documents (label/sales package, declaration of conformity, EC certificate) will end negatively. On the MDR and IVDR side the same provision is in the fourth sub-item of subparagraph (b) of paragraph 2 of Articles 27 and 30, and the documents compared are listed as the EU declaration of conformity and the EU certificate. The check before registration is therefore simple: the barcode on the label, in the declaration of conformity and on the certificate must be the same.

Consistency Between the Reference/Catalogue Number and the HIBCC Barcode

In the HIBCC standard there is a structural link between the barcode and the reference/catalogue number, and the Guide gives this link in an exact format. The fifth sub-item of subparagraph (b) of paragraph 2 of Article 25 of the Guide states that the format of the Primary Product Number must comply with the allocation rules set by the barcode organisation to which it was allocated, and gives an example: for a device whose barcode is allocated under the HIBCC standard, the reference/catalogue number must be consistent with the barcode; the consistency between the HIBCC barcode and the reference/catalogue number takes the form +XXXXreferencecodeXX.

The same format is repeated in the fifth sub-item of subparagraph (b) of paragraph 2 of Article 27 for the MDR and of Article 30 for the IVDR, and in the sixth sub-item of subparagraph (b) of paragraph 10 of Article 29 for CMD records. The practical meaning is this: for a device with an HIBCC barcode, the reference/catalogue number you enter into ÜTS is expected to coincide with the character string in the middle of the barcode. If they do not coincide, one of the fields has been entered wrongly.

Secondary Barcode Organisation and Secondary Product Number

A device may have barcodes from two different standards. The old regulation screen offers a separate pair of fields for this situation. Subparagraph (c) of paragraph 2 of Article 25 of the Guide states that if the device has 2 separate barcodes allocated by two different barcode organisations and standards, the standard of the barcode organisation not entered in the system as the Primary Barcode Organisation is selected in this field. The SIP counterpart of the same article in Article 26 is subparagraphs (b) and (c) of paragraph 3.

The second field becomes mandatory conditionally. The first sub-item of subparagraph (ç) of paragraph 2 of Article 25 of the Guide states that the Secondary Product Number field is mandatory if a Secondary Barcode Organisation is selected in ÜTS. The third and fourth sub-items of the same subparagraph state that the rule of entering the barcode exactly as it is and the provision that the application ends negatively if it does not match the technical documents also apply to the secondary barcode.

There is no secondary barcode field on the MDR and IVDR screens; in these frameworks there is a single UDI-DI Number field. If your device is registered with two barcodes from the MDD period, you need to decide which number is the UDI-DI in the MDR record.

What Is the UDI-DI Number and Where Is It Entered in ÜTS?

UDI is not a single number but a structure. The definitions in Article 4 of the Guide divide it into three tiers: UDI is the unique device identifier created through a globally accepted device identification and coding standard, which allows a specific device on the market to be identified unambiguously and which consists of the UDI-DI and the UDI-PI. UDI-DI is a unique numeric or alphanumeric code specific to a device model. UDI-PI is a numeric or alphanumeric code that identifies the production unit.

The same distinction is established in subparagraph (a) of paragraph 1 of Article 27 of the Medical Device Regulation: the subparagraph states that a UDI consists of a UDI device identifier (UDI-DI), specific to a manufacturer and a device, providing access to the information laid down in Part B of Annex VI, and a UDI production identifier (UDI-PI) that identifies the device production unit and, if applicable, the packaged devices.

What is entered into ÜTS is only the DI part of this structure. Subparagraph (b) of paragraph 2 of Article 27 and subparagraph (b) of paragraph 2 of Article 30 of the Guide state that entering the UDI-DI Number field in ÜTS is mandatory and that the barcode allocated for the relevant device by the UDI Issuing Entity is entered in this field. Production information such as lot and serial number (UDI-PI) is not written into this field.

Changes That Require a New UDI-DI

This is the most commonly misunderstood subject on the market: not every change to a device requires a new UDI-DI, but certain changes certainly do. The seventh sub-item of subparagraph (b) of paragraph 2 of Article 27 of the Guide sets the general criterion: when there is a change that could lead to incorrect identification of the device and/or ambiguity in its traceability, a new UDI-DI Number must be allocated for the resulting new device. The same sub-item states that, in particular, if there is a change in the following elements, a new UDI-DI Number is required according to the standard of the relevant UDI Issuing Entity.

  • Change of device name or trade name: A change of name requires a new UDI-DI.

  • Change of device version/model: A change of the version or model code requires a new UDI-DI.

  • Change related to whether it is single-use: A change in the device's single-use status requires a new UDI-DI.

  • Change related to whether it is packaged sterile: A change in sterility status requires a new UDI-DI.

  • Change related to whether sterilisation is required before use: A change in this requirement requires a new UDI-DI.

  • Change in the quantity of devices in the package/box (number of products in the contents): A change in the content quantity requires a new UDI-DI.

  • Changes related to critical warnings or contraindications: The Guide gives as examples changes in the status of containing latex, DEHP and CMR/endocrine-disrupting substances.

On the IVDR side the same list is in the eighth sub-item of subparagraph (b) of paragraph 2 of Article 30 of the Guide, and its six items are the same; the last item is written there without the latex and DEHP examples.

Even a Translation of the Trade Name Requires a New UDI-DI

A translation is also a name change. The second sub-item of subparagraph (g) of paragraph 2 of Article 27 of the Guide states that any change in trade names resulting from translation into the languages of the EU countries where the device is placed on the market will cause the affected device to be placed on the market with a new UDI-DI; the IVDR counterpart is the second sub-item of subparagraph (g) of paragraph 2 of Article 30. This should not be confused with the "Additional trade names of the product (if any)" field in ÜTS: that field is used when the device is already supplied under other trade names.

A New UDI-DI If the SIP Content Changes

For systems and procedure packs the trigger is the content itself. The sixth sub-item of subparagraph (b) of paragraph 4 of Article 28 of the Guide states that when there is a change that could lead to incorrect identification of the SIP and/or ambiguity in its traceability, or in cases such as removal of a device from the SIP content or addition of a new device to the SIP content, a new UDI-DI Number must be allocated for the resulting new SIP. In practice this means that a SIP manufacturer that revises the pack content cannot carry on with the same barcode.

What Is the Basic UDI-DI and What Does It Link?

The Basic UDI-DI identifies not a single product but a device family. The definition in Article 4 of the Guide describes the Basic UDI-DI as the identifier code assigned at the level of the device unit of use, serving as the main key in the database and in the relevant documentation (for example EU certificates, the EU declaration of conformity, technical documentation and the summary of safety and clinical performance) to link devices with the same intended purpose, risk class and essential design and manufacturing characteristics.

The second sub-item of subparagraph (c) of paragraph 5 of Article 27 of the Guide describes the same function in ÜTS terms: the Basic UDI-DI is the main key in EUDAMED and in ÜTS and in the relevant documents for linking devices of the same manufacturer with the same intended purpose, risk class and essential design and manufacturing characteristics. The first sub-item of the same subparagraph states that selecting this field is mandatory; the IVDR counterpart is subparagraph (c) of paragraph 5 of Article 30.

Separating the concepts from one another ensures the registration is built correctly.

  • Basic UDI-DI: The top-level code linking the device family. It is not on the label, it is selected in the Product Documents block in ÜTS and it appears in the EU declaration of conformity.

  • UDI-DI: The code specific to a single device model. In MDR and IVDR records it is entered in the Identifying Information block and is found within the UDI carrier on the label.

  • UDI-PI: Identifies the production unit (such as lot, serial number, expiry date). It has no separate field in the ÜTS device record.

  • Primary Product Number: The field that takes the place of the UDI-DI in old-regulation records; the registration is made with this number.

  • Secondary Product Number: A field completed only in old-regulation records, if the device has a barcode from a second standard.

At Most 25 Characters and a Check Digit

The format of the Basic UDI-DI is also bound by rules. The tenth sub-item of subparagraph (c) of paragraph 5 of Article 27 of the Guide states that, under the Basic UDI-DI allocation rules, the Basic UDI-DI code value that issuing entities may allocate consists of at most 25 characters. The eleventh sub-item states that, based on the algorithm determined by the issuing entities, a check digit/character must be part of the Basic UDI-DI, and that this algorithm is provided by the issuing entities to the Commission and to manufacturers. On the IVDR side the same two sub-items are in subparagraph (c) of paragraph 5 of Article 30.

The eighth sub-item states that the Basic UDI-DI issuing entities and standards authorised under the MDR are GS1, HIBCC, ICCBBA and IFA; that is, the Basic UDI-DI is allocated by the same organisations as the UDI-DI.

The Basic UDI-DI Is Not on the Label

This is one of the rules most often misunderstood in the field. The seventh sub-item of subparagraph (c) of paragraph 5 of Article 27 of the Guide expressly states that the Basic UDI-DI is not on the device's market placement label and/or sales package. On the IVDR side the same subparagraph of Article 30, and for MDR SIP records subparagraph (c) of paragraph 8 of Article 28, repeat the provision. Looking for the Basic UDI-DI on the label is therefore pointless; this code lives on the document side, in the EU declaration of conformity and in certain EU certificates.

If the Basic UDI-DI Cannot Be Selected

The most common reason for the field remaining empty is not technical but a sequencing error. The third sub-item of subparagraph (c) of paragraph 5 of Article 27 of the Guide states that, before making a selection on the "Select Basic UDI-DI" screen, it is mandatory to select, in the Documents field, the documents (EU Declaration of Conformity, EU Certificate) related to the relevant device and to the Basic UDI-DI of the device. The fourth sub-item states that only the Basic UDI-DI numbers associated with the selected EU Declaration of Conformity will be listed on this screen and that more than one selection cannot be made. If no Basic UDI-DI appears on the screen, first check whether the EU Declaration of Conformity is registered in ÜTS and whether the Basic UDI-DI is present in the declaration record.

In Which Certificates Is the Basic UDI-DI Mandatory?

The Basic UDI-DI is not required in all EU certificates; it varies by certificate type. The fifth sub-item of subparagraph (c) of paragraph 5 of Article 27 of the Guide makes this distinction expressly and refers to subparagraph (h) of paragraph 2 of Article 7 of the Guide.

  • EU Technical Documentation Assessment Certificate: The Basic UDI-DI information of the device must be present.

  • EU Type-Examination Certificate: The Basic UDI-DI information of the device must be present.

  • EU Product Verification Certificate: The Basic UDI-DI information of the device must be present.

  • EU Quality Management System Certificate: There is no obligation for the Basic UDI-DI information to be present.

  • EU Production Quality Assurance Certificate: There is no obligation for the Basic UDI-DI information to be present.

The first sub-item of subparagraph (h) of paragraph 2 of Article 7 of the Guide shows the reason: EU technical documentation assessment, EU type-examination and EU product verification certificates contain a clear identification of the device, including name, model and type, the intended purpose, the risk class and the Basic UDI-DI. The second sub-item lists, for EU quality management system and EU production quality assurance certificates, the identification of the devices or device groups, the risk class and, for Class IIb devices, the intended purpose information; the Basic UDI-DI is not in this list.

On the declaration of conformity side there is no exception. The sixth sub-item of subparagraph (c) of paragraph 5 of Article 27 of the Guide states that the presence of the Basic UDI-DI information in the EU Declaration of Conformity of the device is mandatory, and refers to subparagraph (d) of paragraph 2 of Article 11; that subparagraph lists the Basic UDI-DI among the information that must be present in a declaration of conformity under the new regulations.

Same Barcode, Different Brand: It Cannot Be Registered

The barcode identifies the device; the brand depends on the barcode. The sixth sub-item of subparagraph (d) of paragraph 2 of Article 25 of the Guide states that devices with the same product number (barcode) cannot be registered in the system under different brand names. On the MDR side the sixth sub-item of subparagraph (e) of paragraph 2 of Article 27, and on the IVDR side the sixth sub-item of subparagraph (e) of paragraph 2 of Article 30, repeat the same provision through the UDI-DI Number.

Action is taken if it is detected. The same sub-items state that if it is determined that the same device has been registered in ÜTS by different companies under different brand names, action will be taken on the non-conforming ÜTS records as a result of the assessment to be made by the Agency. Registering the same barcode under a different brand therefore leads to the record being corrected afterwards, even if it gets the application through in the short term.

What Does the "Products with the Same Barcode" Screen Show?

This field is for checking, not for data entry. Subparagraph (d) of paragraph 2 of Article 27 of the Guide states that in this field the list of records of devices previously registered in ÜTS by other companies with the same UDI-DI Number can be viewed; when the link screen in the field is entered, the "Other Products with the Same Barcode" screen that appears lists the product records of other companies registered with the same number. The IVDR counterpart is subparagraph (d) of paragraph 2 of Article 30, and the CMD counterpart is subparagraph (c) of paragraph 10 of Article 29.

If this screen is not empty, the next step is clear. Paragraph 1 of Article 43 of the Guide states that where records of different companies for a device registered in ÜTS with the same barcode exist and there are data differences between these records, the relevant product parameters must be made identical and consistent in ÜTS before the first device application to be made under Article 40 for the device concerned. This harmonisation is done through an imported product data change request.

The "UTS-" Code for Custom-Made Devices Without a Barcode

Most custom-made devices have no number allocated by a barcode organisation. The fifth sub-item of subparagraph (a) of paragraph 10 of Article 29 of the Guide states that if no primary product number has been allocated from one of the barcode organisations authorised for the CMD concerned, the "UTS" option will be selected in the relevant field; in this case the primary product number for the CMD will be generated automatically by ÜTS with the "UTS-" prefix, and gives an example: UTS-12345.

The company cannot change the generated code. The third sub-item of subparagraph (b) of the same paragraph states that if "UTS" is selected in the barcode organisation field, the Primary Product Number field is generated automatically by ÜTS and this code cannot be changed by the company. If the CMD has a real barcode, the fourth and fifth sub-items of the same subparagraph state that the barcode will be entered exactly as it is and that the application will end negatively if it is not entered as it appears in its technical documents (CMD Declaration and, if any, EU certificate).

Barcode Change in the MDR/IVDR Transition

If the barcode of your device changed when moving to the MDR, you need to establish the link between the two records in the system. Subparagraph (c) of paragraph 2 of Article 27 of the Guide states that the field "Did it transition to the MDR with a different product number?" is mandatory in ÜTS; "Yes" is selected if the device was previously registered in ÜTS under the MDD or AIMDD with a different barcode, and "No" otherwise. If "Yes" is selected, the "Product Number under 93/42/EEC or 90/385/EEC" field in subparagraph (ç) appears and making a selection becomes mandatory.

The selection is made from among the old records. The second sub-item of the same subparagraph (ç) states that the relevant primary product number is selected, using the list on the "Select Medical Device" screen, from among devices previously registered under the MDD or AIMDD, and that the query can be made with the fields "Primary Product Number", "Brand Name", "Product Name" and "Version/Model". Under the third sub-item, only a single barcode can be selected in this field.

On the IVD side the structure is the same; the directive referred to changes. Subparagraph (c) of paragraph 2 of Article 30 of the Guide defines the field "Did it transition to the IVDR with a different product number?" and subparagraph (ç) defines the "Product Number under 98/79/EC" field, and requires a single barcode to be selected from among the old IVDD records.

The UDI Carrier and Its Counterpart on the Label

The UDI-DI and UDI-PI are placed on the label within a structure called the "UDI carrier". Paragraph 4 of Article 27 of the Medical Device Regulation states that UDI carriers are placed on the label of the device and on all higher levels of packaging; the higher levels of packaging do not include shipping containers. Subparagraph (a) of paragraph 3 of the same article states that before placing a device on the market, the manufacturer applies the UDI, created in accordance with the rules of an assigned issuing entity, to the device and, where applicable, to all higher levels of packaging.

The expiry date can be part of this structure. The fourth sub-item of subparagraph (m) of paragraph 7 of Article 27 of the Guide states that for devices with a shelf life, an expiry date on the original label, the sales package and/or the UDI carrier is mandatory. The third sub-item of the same subparagraph states that, if an expiry date is included in labels bearing a UDI carrier, it will be part of the UDI-PI, and that if a manufacturing date is separately present on the label there is no need to include it in the UDI-PI. The IVDR counterpart is subparagraph (ı) of paragraph 7 of Article 30.

GTIN Number for Non-Medical-Device Products Within a SIP

A system or procedure pack may also contain products that are not medical devices. These products are added in ÜTS with a separate logic. Subparagraph (a) of paragraph 14 of Article 28 of the Guide makes the field "Does the SIP content include products outside the scope of Medical Devices?" mandatory; if "Yes" is selected, the "List of Non-Medical-Device Products" field in subparagraph (b) appears and adding the products to the system becomes mandatory.

Five items of information are requested for adding. The second sub-item of the same subparagraph states that if the product to be selected is not in the list, the "Barcode Organisation", "GTIN No", "Manufacturing Institution/Company", "Brand Name" and "Product Name" of the relevant product can be entered on the "Add Non-Medical Device" screen so that the product is saved to the list and can then be selected from it. The third sub-item states that the selected products will be listed with their "GTIN No", "Manufacturing Company", "Brand Name", "Product Name" and "Quantity" information and that the quantities must be entered correctly.

Barcode Checklist: Five Checks Before Registration

Barcode errors are among the fastest reasons for an application to be returned, and almost all of them can be prevented by a short check before registration. The list below sets out the five checks that emerge from the provisions cited above.

  • Are the barcodes on the label, the declaration of conformity and the certificate the same? Under the fourth sub-item of subparagraph (b) of paragraph 2 of Article 25 of the Guide, if the barcode is not entered as it appears in the technical documents, the application ends negatively.

  • Is the registration made with the barcode of the smallest package? Under the sixth sub-item of the same subparagraph, the registration is made with the unit or single package barcode; multi-package barcodes are added to the "Market Placement Information" field after registration.

  • Was the correct organisation selected? GS1, HIBCC and ICCBBA under the old regulations; under the MDR and IVDR, IFA can be selected in addition.

  • If HIBCC, is the reference number consistent with the barcode? Under the fifth sub-item of the same subparagraph, the consistency takes the form +XXXXreferencecodeXX.

  • Is there another record with the same barcode? The "Products with the Same Barcode" screen is checked; if there are data differences, harmonisation is carried out before the first application under paragraph 1 of Article 43.

Most errors on the barcode and UDI side come down to a single character, but the result affects the whole application. Companies can also carry out this check and the registration by opening user authorisation for a consultant from their own ÜTS company pages; the consultant fills in the barcode, UDI-DI and Basic UDI-DI fields with the "Medical Device Registration Officer" authorisation and approves the record, while the e-signature stays with the company's signatory and responsibility for the accuracy of the data rests with the company.

The screen-by-screen flow of the registration is covered on our ÜTS Product (Medical Device) Registration page, the exact list of mandatory fields on our ÜTS Device Registration Mandatory Fields page, and post-registration updates on our ÜTS Post-Registration Obligations page. All reasons for rejection are on our Why Is a ÜTS Application Rejected page, and the details of SIP and custom-made device registration are on our SIP and Custom-Made Medical Device (CMD) ÜTS Registration page. To verify the last digit of a barcode before registration you can use our GTIN Check Digit Calculation tool.

You can find the place of the same subject in EU legislation in our English article titled Basic UDI-DI.

Ü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