Medical Device Cybersecurity: Annex I 17.2, 17.4 and 18.8, IT Environment Risks, Instructions for Use, Software Updates and UDI, and ÜTS Record

SUMMARY
Medical device cybersecurity requirements are among the general safety and performance requirements in Annex I of the Medical Device Regulation. Annex I 17.2 requires software to be developed taking account of the information security principle, 17.4 requires the manufacturer to set out minimum requirements concerning IT security measures, including protection against unauthorised access, and 18.8 requires devices to be designed to be protected against unauthorised access.
In this article we give, with verbatim quotations (unofficial translation) from the Regulation and the TİTCK guidance, these items, the risks relating to the IT environment, the information to be given in the instructions for use, the equivalents in the IVD Regulation, software verification in the technical documentation, the UDI rule for software updates and its counterpart in the ÜTS record.
For the declaration of conformity and ÜTS registration of your devices incorporating software: Medical Device ÜTS Registration Consultancy
Contents
1. Annex I 17: Electronic Programmable Systems and Software
2. Annex I 17.4: Minimum IT Security Requirements
3. Annex I 18.8: Design Against Unauthorised Access
4. Annex I 14.2 (ç) and 14.5: IT Environment and Interoperability
5. IT Security Information in the Instructions for Use: Annex I 23.4 (y)
6. IVD Regulation Equivalents: Annex I 16
7. Technical Documentation and Classification
8. Software Updates and UDI: Annex VI 6.5
9. Counterpart in the ÜTS Record
10. Frequently Asked Questions
1. Annex I 17: Electronic Programmable Systems and Software
Item 17 of Annex I regulates devices that incorporate software and software that are devices in themselves:
“17.1. Devices that incorporate electronic programmable systems, including software, or software that are devices in themselves, shall be designed to ensure repeatability, reliability and performance in line with their intended use. In the event of a single fault condition, appropriate means shall be adopted to eliminate or reduce as far as possible consequent risks or impairment of performance.”
“17.2. For devices that incorporate software or for software that are devices in themselves, the 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, verification and validation.”
“17.3. Software referred to in item 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).”
In 17.2, information security is listed together with the development life cycle, risk management, and verification and validation, and the benchmark is the "state of the art".
2. Annex I 17.4: Minimum IT Security Requirements
“17.4. Manufacturers shall set out minimum requirements concerning hardware, IT network characteristics and IT security measures, including protection against unauthorised access, necessary to run the software as intended.”
The same provision in Annex I of MDR 2017/745 (official English text):
“17.4. Manufacturers shall set out minimum requirements concerning hardware, IT networks characteristics and IT security measures, including protection against unauthorised access, necessary to run the software as intended.”
The obligation to set out the minimum requirements rests with the manufacturer.
Scope: hardware, IT network characteristics and IT security measures.
IT security measures include protection against unauthorised access.
3. Annex I 18.8: Design Against Unauthorised Access
Item 18.8, under the heading on active devices and devices connected to them:
“18.8. Devices shall be designed and manufactured in such a way as to protect, as far as possible, against unauthorised access that could hamper the device from functioning as intended.”
“18.8. Devices shall be designed and manufactured in such a way as to protect, as far as possible, against unauthorised access that could hamper the device from functioning as intended.”
4. Annex I 14.2 (ç) and 14.5: IT Environment and Interoperability
Item 14, concerning the device's interaction with its environment, separately lists the risks between the software and the IT environment:
“14.2. Devices shall be designed and manufactured in such a way as to remove or reduce as far as possible the following risks:”
“ç) risks associated with the possible negative interaction between software and the information technology (IT) environment within which it operates and interacts,”
“14.5. Devices that are intended to be operated together with other devices or products shall be designed and manufactured in such a way that the interoperability and compatibility are reliable and safe.”
5. IT Security Information in the Instructions for Use: Annex I 23.4 (y)
The minimum requirements set out by the manufacturer under 17.4 are included in the instructions for use. Annex I 23.4 lists the information in the instructions for use; subparagraph (y):
“y) For devices that incorporate electronic programmable systems, including software, or software that are devices in themselves, minimum requirements concerning hardware, IT network characteristics and IT security measures, including protection against unauthorised access, necessary to run the software as intended.”
For the rules on instructions for use, see our article on Turkish label and instructions for use.
6. IVD Regulation Equivalents: Annex I 16
In Annex I of the In Vitro Diagnostic Medical Device Regulation, the same requirements are in item 16:
“16. Electronic programmable systems, devices that incorporate electronic programmable systems, and software that are devices in themselves”
“16.2. For devices that incorporate software or for software that are devices in themselves, the 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, verification and validation.”
“16.4. Manufacturers shall set out minimum requirements concerning hardware, IT network characteristics and IT security measures, including protection against unauthorised access, necessary to run the software as intended.”
7. Technical Documentation and Classification
Annex II requires software verification and validation information in the technical documentation:
“- Software verification and validation (Describes the software design and development process and presents evidence of software validation, as used in the finished device.”
There is no separate classification rule for cybersecurity in Annex VIII. For the class of software, Annex VIII implementing rule 3.3:
“3.3. Software, which drives a device or influences the use of a device, falls within the same class as the device.”
“If the software is independent of any other device, it is classified in its own right.”
For the class of standalone software, see our article on medical device software and Rule 11.
8. Software Updates and UDI: Annex VI 6.5
Annex VI determines whether a software modification requires a new UDI-DI:
“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) interpretation of data.”
“6.5.3. Minor software revisions require a new UDI-PI and not a new UDI-DI.”
“Minor software revisions are generally associated with bug fixes, usability enhancements that are not for safety purposes, security patches or operating efficiency.”
A modification that changes the safety of the software requires a new UDI-DI.
A security patch is counted as a minor software revision: a new UDI-PI, not a new UDI-DI.
For UDI-DI and UDI-PI, see our article on the UDI system.
9. Counterpart in the ÜTS Record
According to Article 17 of Guidance TCKKD-KLVZ-03, the obligation to upload instructions for use depends on the device class:
“1) For Class-III and Class-IIb devices, the instructions for use issued by the manufacturer,”
“(3) For device groups in other risk groups (Class-I Other, Class-Im, Class-Is, Class-Ir, Class A, Class A Sterile and IVD Other devices), uploading instructions for use is optional.”
For Class-IIa, under subparagraph 17/2-a-2, the instructions for use are uploaded if the manufacturer has issued them. For devices within the scope of the MDR, Article 27 has a software-specific rule for the "Product Images" field in the device record:
“10) If the device is software in itself, a screenshot from the software interface and the software identity may be uploaded to this field as a visual.”
For ÜTS product registration, see our article on ÜTS medical device product registration; for the declaration of conformity, see our page on preparing the MDR and IVDR declaration of conformity.
10. Frequently Asked Questions
Where is cybersecurity regulated in the Medical Device Regulation?
In the general safety and performance requirements of Annex I: 17.2 information security, 17.4 IT security measures, 18.8 design against unauthorised access, and 14.2 (ç) risks of interaction with the IT environment.
Who sets the minimum IT security requirements?
Under Annex I 17.4, the manufacturer. Under Annex I 23.4 (y), these requirements are included in the instructions for use.
Is there the same rule for IVD devices?
Yes. Annex I 16.2 and 16.4 of the In Vitro Diagnostic Medical Device Regulation contain the same wording.
Does a security patch require a new UDI-DI?
Under Annex VI 6.5.3, security patches are counted as minor software revisions; they require a new UDI-PI and not a new UDI-DI. A modification that changes the safety or intended purpose of the software requires a new UDI-DI under 6.5.2.
Which image is uploaded to ÜTS for standalone software?
Under Article 27 of TCKKD-KLVZ-03, a screenshot from the software interface and the software identity may be uploaded to the "Product Images" field.
For the declaration of conformity and ÜTS registration of your devices incorporating software: Medical Device ÜTS Registration Consultancy
Sources



