Medical Device Software (MDSW): Classification under Annex VIII Rule 11, Software UDI and ÜTS Registration

SUMMARY
Medical device software is software designed by the manufacturer for one of the medical purposes in Article 3 of the Medical Device Regulation (Tıbbi Cihaz Yönetmeliği). The Regulation lists software separately in the definition of a medical device and, with Rule 11 in Annex VIII, sets a classification rule specific to software.
In this article we give the definitions, the word-for-word text of Rule 11, the general rules applied to software, the software UDI and the registration of software in ÜTS, quoting the Regulation and the TİTCK ÜTS Registration Guideline TCKKD-KLVZ-03.
For the ÜTS registration of your medical device software: Medical Device ÜTS Registration Consultancy
Contents
1. Where Does Software Appear in the Legislation?
The definition of a medical device (Medical Device Regulation Article 3, item eee) expressly lists software:
“instruments, apparatus, appliances, software, implants, reagents, materials or other articles intended by the manufacturer to be used, alone or in combination, for human beings for one or more of the medical purposes,”
The first two of the medical purposes in the definition:
“i) diagnosis, prevention, monitoring, prediction, prognosis, treatment or alleviation of disease,”
“ii) diagnosis, monitoring, treatment, alleviation of, or compensation for, an injury or disability,”
Under item (b) of the same article, the second sub-item of the definition of an active device is "Software". The ÜTS Registration Guideline also states this expressly:
“Software that is a medical device on its own is considered an active medical device.”
For whether software is considered a medical device, see our page on whether software is a medical device.
2. Classification Is Based on the Intended Purpose
The first of the implementing rules of Annex VIII:
“3.1. The application of the classification rules shall be governed by the intended purpose of the devices.”
The definition of intended purpose is in Article 3 of the Regulation:
“hh) Intended purpose: the use for which a device is intended according to the data supplied by the manufacturer on the label, in the instructions for use or in promotional or sales materials or statements, and as specified by the manufacturer in the clinical evaluation,”
According to the definition, the intended purpose is determined not only from the instructions for use but also from the label, promotional and sales materials and the information in the clinical evaluation. For misleading claims, see our article on misleading statements and label claims.
3. Software Driving a Device and Standalone Software
Annex VIII implementing rule 3.3:
“3.3. Software, which drives a device or influences the use of a device, shall fall within the same class as the device. If the software is independent of any other device, it shall be classified in its own right.”
The same provision is also in the third paragraph of Article 52 of the ÜTS Registration Guideline. Rule 3.2, for devices and accessories used together with another device:
“3.2. If the device in question is intended to be used in combination with another device, the classification rules shall apply separately to each of the devices. Accessories for a medical device shall be classified in their own right separately from the device with which they are used.”
For the concept of accessory, see our article on the medical device accessory.
4. Annex VIII Rule 11: The Software-Specific Rule
Medical Device Regulation Annex VIII, point 6.3:
“Software intended to provide information which is used to take decisions with diagnosis or therapeutic purposes is classified as class IIa. However, if such decisions:”
“- have an impact that may cause death or an irreversible deterioration of a person's state of health, such software is classified as class III,”
“- have an impact that may cause a serious deterioration of a person's state of health or a surgical intervention, such software is classified as class IIb.”
“Software intended to monitor physiological processes is classified as class IIa. However, if it is intended for monitoring of vital physiological parameters, where the nature of variations in those parameters is such that it could result in immediate danger to the patient, such software is classified as class IIb.”
“All other software is classified as class I.”
The rule gives four outcomes:
Software providing information for a diagnostic or therapeutic decision: class IIa; class III if the effect of the decision may be death or irreversible deterioration, class IIb if it may be serious deterioration or surgical intervention.
Software monitoring physiological processes: class IIa.
Software monitoring vital physiological parameters whose variations may result in immediate danger to the patient: class IIb.
All other software: class I.
The rule appears with the same text under the "Active Devices" category in Article 56 of the ÜTS Registration Guideline. For the other classification rules, see our article on MDR risk class.
5. If More Than One Rule Applies
“3.5. If several rules, or several sub-rules within the same rule, apply to the same device based on the intended purpose of the device, the strictest rule and sub-rule resulting in the higher classification shall apply.”
Active devices for diagnosis and monitoring are covered by Rule 10 in Annex VIII; if this rule also applies together with the software rule, the rule giving the highest class is taken as the basis. For the conformity assessment route according to class, see our article on selection of the conformity assessment procedure.
6. General Safety and Performance Requirements for Software
Point 17 of Annex I sets specific requirements for devices incorporating software and for software that are devices in themselves:
“17.2. In the case of devices that incorporate software or software that are devices in themselves, such software shall be developed and manufactured in accordance with the state of the art, taking into account the principles of development life cycle, information security, risk management, including verification and validation.”
“17.3. Software referred to in point 17 of this Annex that is intended to be used in combination with mobile computing platforms shall be designed and manufactured taking into account the specific features of the mobile platform (e.g. size and contrast ratio of the screen) and the external factors related to their use (varying environment as regards level of light or noise).”
“17.4. Manufacturers shall set out minimum requirements concerning hardware, information technology (IT) network characteristics and IT security measures, including protection against unauthorised access, necessary to run the software as intended.”
For the information security side, see our article on medical device cybersecurity. For IVD software, the same requirements are in point 16 of Annex I to the In Vitro Diagnostic Medical Device Regulation.
7. UDI for Software: When Is a New UDI-DI Required?
Annex VI Part C, point 6.5:
“The UDI shall be assigned at the system level of the software. Only software which is commercially available on its own and software which constitutes a device in itself shall be subject to this requirement.”
“The software identification shall be considered to be the manufacturing control mechanism and shall be displayed in the UDI-PI.”
“6.5.2. A new UDI-DI is required whenever there is a modification that changes:”
“a) the original performance;”
“b) the safety or the intended purpose of the software;”
“c) the interpretation of data.”
“6.5.3. Minor software revisions require a new UDI-PI and not a new UDI-DI.”
According to the same point, the UDI is provided on a screen easily accessible to the user, in an easily readable plain-text format such as an "about" file, or is included on the start-up screen; software without a user interface can transmit the UDI through an application programming interface (API). For the UDI structure, see our article on the UDI system, UDI-DI and Basic UDI-DI.
8. Software Provided Remotely: Information Society Services
Article 6 of the Medical Device Regulation:
“(1) A device offered to a natural or legal person by means of information society services shall comply with the provisions of this Regulation.”
“(3) Any natural or legal person who offers a device in accordance with the first paragraph or who provides a service in accordance with the second paragraph shall, upon request by the Authority, make available a copy of the EU declaration of conformity of the device concerned.”
The details of the article are in our article on information society services and remote service devices.
9. Software Registration in ÜTS
Software is registered in ÜTS under the MDR like other devices; the headings of the registration screen are in Article 27 of the ÜTS Registration Guideline. For product images, the sixth paragraph of the same article contains a provision specific to software:
“10) If the device is a standalone software, a screenshot from the software interface and the software identification may be uploaded to this field as a visual.”
For the Version/Model field, the second paragraph of the same article:
“2) If the version, model or model code of the device appears in the documents linked to the product and/or on the label, it is mandatory to enter this information in this field exactly as written in those documents and/or on the label.”
For product registration in general, see our articles on ÜTS product registration, and for the software product group, see our page on medical device software ÜTS registration.
10. Frequently Asked Questions
Which class is software that drives a device?
According to Annex VIII implementing rule 3.3, software that drives a device or influences the use of a device falls within the same class as the device. Software independent of a device is classified in its own right.
When does software become class III?
According to Rule 11, software is classified as class III if the diagnostic or therapeutic decisions taken with the information it provides may have an impact that may cause death or an irreversible deterioration of a person's state of health.
Is there software that stays in class I under Rule 11?
Yes. According to the last sentence of the rule, all other software that does not provide information for diagnostic or therapeutic decisions and does not monitor physiological processes is classified as class I.
Is a new UDI-DI required for a software update?
According to Annex VI Part C 6.5.2, a new UDI-DI is required for a modification that changes the original performance, the safety or the intended purpose of the software, or the interpretation of data. Minor revisions require only a new UDI-PI.
What is uploaded to ÜTS as the image of software?
According to Article 27 of the ÜTS Registration Guideline, if the device is a standalone software, a screenshot from the software interface and the software identification may be uploaded as the product image.
For the ÜTS registration of your medical device software: Medical Device ÜTS Registration Consultancy
Sources



