Clinical engineering
about professional status that has persisted for decades. The expansion of digital healthcare could present an opportunity to redefine the role. Job descriptions for clinical engineers have not been updated since 2004/2005 and do not reflect the digital and integration responsibilities now expected. Professional registration was raised as a mechanism to establish parity with IT colleagues. One participant recommended that clinical engineers obtain medical equipment networking qualifications to gain credibility and access with IT departments: “We should get at least one person in the team on a medical equipment networking course – such as the one at Eastwood Park. I’ve completed one recently. You need to get that qualification! “That allowed me to go back into my hospital,
to my IT department, put my certificate on their desk and say, ‘I now require elevated admin rights, so that I can make some changes on the network.’ In the past, we were lucky if we could turn up the volume on our PCs, at work! “Sometimes, I need to change my IP address on the laptop to connect to medical devices. I want to run command prompts. I want to ping IP addresses. I want to be able to do these things,” they commented, adding that this had helped to improve the relationship with IT: “They respect that you’ve gone out and made some effort to learn some of their language,” they commented. Another delegate cited the example of a
Trust where the clinical engineering department reports into the director of IT: “IT tend to have a much easier link into the senior executive team and are listened to; and they have much better access to funding. As clinical engineers, we have allowed ourselves to be the poor relations and we are now recognising that we need to look at how we are heard at the top table,” they asserted. “Our hospital put on an event especially for healthcare scientists and even my superiors did not know that clinical engineering was under
this title. I nominated two of our engineers to ensure that they were visible and part of it. But when the signage appeared this year, they were completely missed off again,” one of the thought leaders shared. It was noted that clinical engineering is
often the “poor relation” regardless of whether it sits under estates, IT, or medical physics. So, some suggested that clinical engineering should be a standalone department – a separate entity in its own right. The group emphasised professional
registration, recognition and visibility are key. One of the delegates questioned why IT has historically been elevated over clinical engineering: “What is professional registration like with our IT colleagues? What qualifications do they have to wield the power that they have over medical device management? This is what we need to fight for as a profession,” they asserted. “We have a huge workforce, with control
and power over medical devices, who are passionate and well managed. And yet they [IT] are dictating what we can and can’t do. We need to gain their respect, but shouldn’t they be gaining our respect too? Ultimately, someone has to make the first move. Let it be us.”
New hospital programme and early involvement The new hospital programme was highlighted as an opportunity for clinical engineering to get involved at the earliest stages of hospital design, including working with architects and project teams. It was noted that funding is available within capital projects that could support asset management system improvements and training. However, participants acknowledged that clinical engineering teams are frequently excluded from planning processes. One of the delegates urged the group: “For
those waiting to get involved; just pull up a chair and don’t wait to be invited.”
Proposed solutions and next steps As the discussion reached its conclusion, the group identified a number of potential steps forward: l Development of a digital healthcare technology maturity framework spanning estates, clinical engineering, procurement, clinical training, and digital teams.
l Updated job profiles for clinical engineering roles to reflect modern digital responsibilities.
l A joint healthcare technology policy with clearly defined roles and responsibilities across all relevant teams.
l The MDSO should sit within the quality and governance team.
l Updating MHRA guidance from “Managing Medical Devices” to “Managing Healthcare Technology” to encompass software, AI, and digital systems, and to apply equally to estates, digital, and clinical engineering
l Identify good pockets of practice and share this across Trusts. There is an opportunity for a white paper to exchange this knowledge, so individual teams do not have to ‘reinvent the wheel’.
Ultimately, the discussions during EBME Expo showed that the future of healthcare technology will depend not only on innovation, but on collaboration, professional competence, and strong implementation. The Clinical Services Journal will share the findings of the EBME Expo Leaders Network in the next editions, as a select gathering of influential leaders meet in Birmingham to reflect on the topics and challenges raised at EBME Expo.
For details of EBME Expo 2027, visit:
https://www.ebme-expo.com/
November 2026 I
www.clinicalservicesjournal.com 39
CSJ
AKACHA -
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