Clinical engineering
contract? If it’s the latter, how do we deal with that contract? Furthermore, is the contract for the app or is it for the probe? At the moment, we don’t know how to deal with it,” they continued.
Silo challenges Another delegate warned that confusion over responsibilities could leave cybersecurity updates incomplete. She pointed out that siloed working creates significant challenges. One Trust has responded to this challenge by establishing a Medical Device IT Group with representatives from IT, engineering and clinical teams. “The foundations of this model are very strong. I discussed it with my own Trust, and the digital lead said, ‘This is exactly what we need,’” she reported.
“What we need is a system,” she continued.
“We need a method of governing new technologies that looks at the support actions we need for a device. From an IT perspective, we need someone who is going to manage the middleware system, the operating system,
check the life cycle against the patching, and so on. From a cyber perspective, what support does that device need? From a maintenance perspective, what does that need from a contract? “From an electrical perspective, hardwired
devices require support from estates, as do those connected to a water supply. Different devices therefore need different types of support, recorded in a classified maintenance system that does not yet exist. Clinical engineering often logs a device on its system and, as a result, becomes its de facto ‘owner’. I would like a system that records each technology, while allowing different teams to own the individual areas of responsibility,” she continued. One of the thought leaders observed that he had seen good technology “fail” because responsibility fell between the cracks. Software may come with middleware that no one maintains, data is not extracted, and too often there is no clear owner.
“Too many responsibilities are assumed – or simply left unassigned. We need aligned standards and legislation, supported by systems that make ownership clear,” he asserted. Another shared that they had collaborated with their Trust’s cyber team and, as a result, some concerning issues had come to light. For example, a device needed a software update but a specialist nurse, who used it, objected “because it might not work” afterwards. “The end user may have had a bad experience in the past, but I pointed out that if you don’t update the software, you are not maintaining the device – therefore, if anything goes wrong, you can be held personally responsible – that changed things. I said to the cyber team: ‘how often does this happen for you?’, and they said a number of times. They had escalated it up to the IT manager, but nothing had happened. They said that I was the first person who had ‘actually shown an interest’. I advised that if they are finding this resistance at a local level and maintenance is not happening, they need to highlight this to the medical device safety group, so they can support them with the issue,” he commented.
Too many responsibilities are assumed – or simply left unassigned. We need aligned standards and legislation, supported by systems that make ownership clear.
36
www.clinicalservicesjournal.com I November 2026
Software updates and modifications Another delegate shared that that software updates and modifications are logged on to a ‘modifications register’ at their Trust: “We’ve incorporated all of the software related modifications. Field safety notices and corrective actions often result in a software change. We need to be able to track and manage that through the modification register, as well as have a function for escalation.” He explained that when an asset comes in for a service, the system ensures the device is quarantined until it has had the necessary software updates, as this is a safety critical issue.
“It’s the same principle as if you are fixing a
bracket, or a power supply issue, that’s been flagged by the manufacturer. We apply that same model across everything that we do with our devices,” he explained.
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71