Clinical engineering
I feel like I’m pushing companies hard to ‘toe the line’, when it comes to drug error reduction and software updates etc. They need to follow our processes. At the time that this happened, we didn’t even have access to the portal. I had to lobby to get support and access to the portal. Now we have gained firm control,” he reported.
MHRA and regulation of AI The delegates discussed the MHRA’s recommendations regarding the Regulation of AI in Healthcare. The document was eagerly anticipated at the time of the thought leadership workshop. In June this year, the MHRA announced a new regulatory sandbox to create a real-world environment to safely deploy AI-enabled medical devices, while generating additional evidence of benefit across NHS settings.
By bringing together regulators, healthcare
providers and innovators, the sandbox aims to provide a controlled environment so cutting- edge technologies can be safely and securely deployed. The programme will support delivery of the NHS 10-Year Health Plan by enabling faster adoption of technologies that improve patient outcomes, expand access to care, and reduce health inequalities. This was followed by the publication
of recommendations by MHRA’s National Commission into the Regulation of AI in Healthcare in September. These recommendations outline how we can ensure AI remains safe, keeps pace with innovation, and continues to earn people’s trust. “The MHRA guidance is not going as far as you would expect to be honest – and this is going to be the version of the guidance that will be in place for the next six or seven years,” said one of the delegates.
I don’t think you will get a clear definition stating that any product sits solely in your department or the IT department. You are just going to have to get used to multidisciplinary working. The group shared some of the challenges
they face around medical devices with AI software – especially around governance, registration and testing. “I don’t know how to test AI – that’s a whole
new thing,” commented one of the attendees. Another shared their frustration over blurred responsibilities with AI-enabled medical devices: “IT pick and choose what they want to get involved in,” they complained. At the same time, one attendee shared an example of when IT inadvertently corrupted the manufacturer’s technology during the integration of a patient monitoring system. The manufacturer complained that the Trust’s IT department should not be touching the software as it is ‘a medical device’. Arguments ensued over who was responsible and where the funding lay to fix the problem – IT or medical engineering. This scenario further highlighted some of the challenges and divisions between IT, clinical engineering and the manufacturers of AI-enabled healthcare technologies.
Bridging the gap One of the delegates suggested that they had found a way forward to this problem – they employed an IT person to sit within clinical engineering. “Their role was to interface between IT and medical devices. This helped to build dialogue between the two departments and overcome silo working. This is a significant problem within the NHS – and all of our budgets
are siloed as well, which acts as a barrier to partnership working…It’s about getting the right person in place.” Another Trust has implemented a digital
committee to bridge the gap between clinical engineering and IT. At the heart of this challenge is the need for effective governance, however: “From listening to all the stories around the room, it is clear that there are some really good pockets of good practice. However, it sounds like there is a need to get the governance right. You need guidelines to say who does what and replicate that because we have wildly different things happening across Trusts. I don’t think you will get a clear definition stating that any product sits solely in your department or the IT department. You are just going to have to get used to multidisciplinary working,” they asserted. Managing this change will require strong partnerships, another delegate confirmed: “Technology is changing and, as clinical engineers and leaders, we have to accept this is where it is heading and move into this space – we either own it or build that partnership. And partnership is absolutely key – not just with the IT team, but also with our vendors,” she commented. Citing the previously mentioned challenges
around software updates, she added: “We have a lot of connected systems and updating a medical device can affect the data that is going into EPIC. So, we need consistent dialogue, and we also need to encourage our teams to build that trust with vendors. It doesn’t matter whether it’s the senior engineer or a junior engineer, it’s about best practice. “We all talk about best practice and enforce that with our vendors and IT, and we continue to work together. From a system perspective, our asset management system sits in the same system as IT and facilities…Some of our applications that connect to medical devices are within the IT database, but we have access. However, to have access, you have to have an ITO licence and go through relevant training,” she explained.
Clinical engineering’s position and visibility Participants touched on the broader challenge of clinical engineering’s organisational position. Delegates shared a deep-seated frustration
38
www.clinicalservicesjournal.com I November 2026
3AI studio -
stock.adobe.com
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