Clinical engineering
Calls to bridge the gap between EBME and IT
Earlier this year, clinical engineers came together at EBME Expo to discuss the intelligent hospital and the challenges this presents for medical devices management. Insights from a workshop of clinical engineers were gathered to inform the EBME Expo Leaders Network, who seek to collaborate on achieving key objectives in the field of EBME. Louise Frampton reports.
Chairing the thought leadership workshop at EBME Expo, Iain Threlkeld, Head of Clinical Engineering at Leeds Teaching Hospitals NHS Trust, posed a challenging question: how can healthcare organisations manage the introduction of new technology, along with device integration and interoperability, as this becomes central to the future of the intelligent hospital? Furthermore, as the intelligent hospital will
require greater co-operation between clinical engineering, ICT, and procurement, who should be leading on this, and how can we bridge the gaps between the various stakeholders?
Technologies and ‘grey areas’ of responsibility A hot topic of discussion included the challenges around siloed working across Clinical Engineering, IT, Estates, and Procurement. It was clear that no single team has clear ownership of complex healthcare technologies and this had the potential to lead to patient safety risks. One clinical engineer shared that he had
developed a list of complex technologies – such as RO units for renal, electronic prescribing systems, middleware and digital-based medical devices – that occupy “a grey area”, as there is uncertainty over who should take ownership. “We need a completely different approach
to managing healthcare technology,” he commented, adding that a lack of interoperability between systems is a major issue. He pointed out that many in the UK are using the E-Quip system (an asset management software for medical devices), while others are using a Computer-Aided Facility Management (CAFM) system (a type of software that automates critical aspects of facility management, such as maintenance, operations and workflows.) “None of the systems can talk to each other, so how can we manage an asset when so many
Iain Threlkeld chaired the discussion
interested parties are managing different components or aspects of it?” he questioned. He warned that “we have a long way to go”
to solving this challenge: “Estates may manage the water supply, clinical engineering the daily testing, and digital teams the middleware, monitoring systems and cybersecurity. We can lobby for support and encourage suppliers to provide a genuinely integrated system that allows each team to do their part, but in the short term, we must make best use of existing guidance and policies, working across these areas wherever possible, to support modern healthcare technology,” he advised. The thought leadership group agreed that
clinical engineers bring a wealth of experience to the table but there was concern over whether they were best placed to lead: “The digital teams are just learning what software as a medical device looks like, what AI looks like, how to record it, how to administer it, and how to buy it. We need to work together on this,” one of the delegates suggested. “Lots of people believe that clinical engineering should lead the way, but I don’t
think that’s quite right. We’re not as expert as IT. We can provide support, but it must be a collaborative effort. In the long term, this may mean clinical engineering moves forward more with the digital teams, with estates forming ‘digital estate teams,’” he continued. One of the attendees shared that they had
cross-referenced various guidance with a view to create a “maturity assessment framework” across all components of digital healthcare technology – covering clinical engineering, training, application, procurement, and cyber security.
“If we can’t describe what ‘good’ looks like and
the varying degrees of that, then we don’t have anything to work towards,” he exclaimed. “There must be a hybrid document, drawing on all of the different pieces of legislation, regulation, and guidance that says, ‘this is what good looks like’, the levels of maturity, and what you should aspire to,” he pointed out. A member of the group cited the example
of increasingly complex and digitally advanced pharmaceutical administration and prescribing systems. Their advancement has prompted debate over whether they fall within the remit of IT and digital teams or clinical engineering, and whether they should be classified as medical devices. These blurred boundaries create uncertainty over who is responsible for their management. “We need to adapt and work together on
these technologies because there are so many ‘grey areas’,” one of the delegates asserted. Another example was given of a new
ultrasound technology that appeared to fit the category of ‘software as a medical device’. “It’s basically a handheld wireless-connected probe, which you download an app to,” the delegate explained. “It could be a personal phone or a Trust-issued phone. The question is, how do we manage that, if the probe stops working? It’s a conundrum – will IT deal with this or is there a
November 2026 I
www.clinicalservicesjournal.com 35
t
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