Table 2

The 49 measures to implement risk management, including the priority and complexity of each measure

SubgroupMeasurePriorityComplexity
OrganisationExternal laws and regulations must be taken into account*Embedded ImageEmbedded Image
The users must learn the network functions of the medical device*Embedded ImageEmbedded Image
Information technology (IT) standards and frameworks [Control Objectives for Information and Related Technologies (COBIT), Information Technology Infrastructure Library (ITIL), etc] must be integrated*Embedded ImageEmbedded Image
A professionally qualified risk manager must be appointed*Embedded ImageEmbedded Image
Roles and tasks of the risk manager must be clearly defined*Embedded ImageEmbedded Image
Roles and tasks of the manufacturers must be clarified*Embedded ImageEmbedded Image
Roles and tasks of users must be defined*Embedded ImageEmbedded Image
Responsible leadership must be appointed*Embedded ImageEmbedded Image
Possible stakeholders must be identified and informed*Embedded ImageEmbedded Image
Scopes must be defined*Embedded ImageEmbedded Image
Risk management processes must be developed and implemented*Embedded ImageEmbedded Image
Risk management activities must be evaluated regularly and improved if necessaryEmbedded ImageEmbedded Image
Interface between medical technology and IT department must be ensured*Embedded ImageEmbedded Image
A coordinated procurement process for medical devices must be established*Embedded ImageEmbedded Image
Reporting to the responsible management must be implemented*Embedded ImageEmbedded Image
A risk management file must be created*Embedded ImageEmbedded Image
All networked medical devices/systems must be recorded and documented*Embedded ImageEmbedded Image
A complete network description and documentation must be kept*Embedded ImageEmbedded Image
Document guidance must be introduced*Embedded ImageEmbedded Image
Risk identificationAsk manufacturers about possible cyber risks of their medical device*Embedded ImageEmbedded Image
Ask users what impact a medical device failure has*Embedded ImageEmbedded Image
Ask the IT department about general IT threatsEmbedded ImageEmbedded Image
Identify the purpose of the connection to the IT network and derive risk situations*Embedded ImageEmbedded Image
Identify critical clinical areas and automatically assume critical networking there*Embedded ImageEmbedded Image
Identify data flows completely and derive possible errors and effectsEmbedded ImageEmbedded Image
Create or adapt hazard catalogue*Embedded ImageEmbedded Image
Risk analysisDefine risk matrix*Embedded ImageEmbedded Image
Define probabilities of occurrence*Embedded ImageEmbedded Image
Define implications for data and information security*Embedded ImageEmbedded Image
Define impact for process effectiveness*Embedded ImageEmbedded Image
Define implications for patient safety*Embedded ImageEmbedded Image
Assess risks for each potential hazard*Embedded ImageEmbedded Image
Document risk analyses and evaluations*Embedded ImageEmbedded Image
Risk minimisationThe medical IT network must be constantly monitored*Embedded ImageEmbedded Image
Basic general IT security (eg, ISO 2700x) must be ensured*Embedded ImageEmbedded Image
Incident and event management must be developed and implementedEmbedded ImageEmbedded Image
Implement network segmentations based on risk analysisEmbedded ImageEmbedded Image
Interface and communication standards (eg, HL7, DICOM) must always be applied*Embedded ImageEmbedded Image
The technical infrastructure must be continuously kept at state of the art*Embedded ImageEmbedded Image
Manual data processing procedures should be identified as possible workarounds*Embedded ImageEmbedded Image
Risk-minimising measures must be regularly reviewed and documentedEmbedded ImageEmbedded Image
Catalogue for risk-minimising measures must be created and implementedEmbedded ImageEmbedded Image
Residual risksResidual risks must be systematically assessed and justifiedEmbedded ImageEmbedded Image
Residual risks must be documented in an understandable mannerEmbedded ImageEmbedded Image
Residual risks must always be accepted by top management*Embedded ImageEmbedded Image
Change managementSystematic change and configuration processes must be developedEmbedded ImageEmbedded Image
All changes and configurations must be approved by IT risk management*Embedded ImageEmbedded Image
Frequent changes should be defined as standard processes (routine)Embedded ImageEmbedded Image
Significant changes or new installations should be organised as a project*Embedded ImageEmbedded Image
  • *Measures implemented in the case study.