Clinical engineering
MDSO: avoiding conflicts of interest It was suggested that issues around updates for safety critical software should be the remit of the Medical Device Safety Officer (MDSO), but one delegate pointed out that the MDSO role must be “in the right and appropriate place”. Rather than “sitting in clinical engineering”, it should be a corporate role across quality and governance. “Another aspect is the management of the
pre-acquisition questionnaire (PAQ), before the technology comes in. The PAQ looks at cleaning, maintenance, connectivity, training etc. But who should be signing off on that, before we invest in the technology? As the MDSOs are still sitting within clinical engineering, they find that they have the responsibility to pull all the silo working in. Those silo services should be reporting to the MDSO for governance to be signed,” commented one of the delegates. Another thought leader agreed but added that there are other key issues that must be addressed: “I’m the MDSO and I used to have a mix/match of a job two years ago. I’ve been a pure MDSO now, for the last year, for which I’m grateful. I sit in medical engineering…I understand why that role sits in medical engineering historically. I’m not saying it’s a bad thing, but if you have a problem in your medical engineering department, it is a big problem for an MDSO – because of the conflict of interest. “You have a duty to report safety issues to
the Trust. You need a clear line of reporting to the Trust governance policy team, as well as to your senior, if you sit within a subsidiary. But it is a complete and utter conflict of interest if your reporting role is to the head of service in engineering,” they exclaimed.
Remote access by manufacturers: the risks Another concern raised by the group was remote software updates by manufacturers: “They may let the department know that they’re doing it, if we’re lucky. They exclude IT and they exclude medical engineering. We had an issue that I was looking into, and I found a small can of worms,” one of the delegates shared. It was pointed out that an external
company shouldn’t be able to log onto a medical device connected to the Trust’s network because of the firewall, but in this instance, they were able to remotely access the MRI scanner. “They didn’t notify the team that there would be issues due to the remote update, and the hospital staff carried on scanning
patients. They should have been told. I’m not saying that this type of service should be excluded but they need to ensure stakeholders at the Trust are involved, so they know when it’s happening and can ensure staff are not scanning patients while they are doing this work,” she commented. “It’s not just the big items,” another attendee
shared. “We’ve had a scenario where staff were performing an ECG on a patient, just as the equipment was in the middle of the update. The clinician didn’t know that was what was happening and turned the equipment off halfway through the update – you can imagine how well it turned back on again!” Communication between manufacturers and
clinical engineering proved to be a contentious issue, with other delegates sharing similar experiences: “A large infusion pump company
has its middleware on one of our servers – and, as a matter of fact, decided to include me in on an email (among the many hundreds of emails that I get every day) to say that they were rolling out a firmware update on a particular day. “I found out that they had previously rolled out a number of firmware updates with new functionality without involving us. There was no change control or staged rollout plan. So, we got heavily involved and put a company process in place around future updates. We are now writing a standard operating procedure (SOP) for any updates undertaken remotely. “Previously, we hit problems where the
configuration had been upgraded but the firmware hadn’t, and vice versa. Sometimes the pumps locked out. I worry that this sort of thing is happening every day with companies. Vendors really should understand the implications.
TRUSTED RESULTS, WHERE IT MATTERS INTRODUCING SPINCHIP®
From just a single drop of blood.
Empowering decisions at the Point of Care for confident triage of patients in the Emergency Department.
SPINCHIP ®
®
hs-cTnl
The SPINCHIP hs-cTnI test provides rapid high-sensitivity cardiac troponin I results at the point of care, supporting faster assessment of patients with suspected acute myocardial infarction and enabling confident clinical decision-making closer to the patient.
PIONEERING DIAGNOSTICS
November 2026 I
www.clinicalservicesjournal.com 37
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