EBME Forums Forums Management Modernisation (Formerly, Controls Assurance) Medical Device IT Integration Strategy

Hi All,

I've been given a short piece of work to draft formulate an integration strategy for our organisation. Feel free to email yours if you have such a thing so I can use it as benchmark/guidance as it might break the back of it somewhat.

Obviously I've googled already but I'm looking for something along the lines of:

- 5 year strategy
- Prioritisation based on ROI (Time/Money), Initial Outlay, Appropriateness of the device
- Common sense, we are not going to integrate everything
- Perhaps some clues into who/how this will be realised operationally, i.e. is this is a new post in IT or Medical Devices etc

I've got an idea of what might go in, but I'd be keen to learn from someone who had already followed this route in the form of a formal strategy (to create a joint strategy with IT)

Thanks in advance (if your quick enough!)

Cheers
Joe

Hello Joe,
Medical Device Interoperability and Integration is a pretty lengthy process. It requires someone working full-time on this particular project. This is no fish that can be underhandedly dealt with.
So be prepared to face the challenges and frustrations that you will encounter not only with the IT department but with the medical device manufacturers as well.
There is a lot you have to think about since this is a new field that is still in turmoil and changes are being made as we move forward.
This is a huge topic and needs thorough discuss at each step of the project.
E-mail me and we can chat on it.
Cheers
Tim

Good luck dealing with IT, try to find a BME with IT knowledge as you may find it more difficult to find an IT with medical equipment knowledge.

Do you have HIS/RIS Cardiac PACS to begin with?

Neil

As I may have mentioned before:- in a rational world, all Technical Services in any hospital should come under one umbrella anyway!

In other words, I believe it's about time that IT versus biomed "turf wars" became a thing of the past.

Not having a turf war, just that our IT doesn't understand medical equipment. It comes down to the recruitment policy. I have advocated that IT should be split into 2 sections 1)Office Automation 2) Health Informatics. IT should be part of Operations and maintenance, especially the Health Informatics. We are hoping that the powers that be will endorse this as there was a recent operations audit in the hospital and this idea was mooted.

Neil

I hear what you're saying there, Neil.

In fact I was thinking of posting something similar. Along the lines of:- how come any "unhelpful" hospital IT staff don't get weeded out during the hiring process?

IMHO, everyone (all hospital staff) needs to be focused on patient care ... and any that don't sign up to that ideal should seek employment somewhere (else) where they might be more happy. In short, it needs to be a team effort.

On your other point:- yes; hospitals should be streamlined into five divisions (or "services"):-

1) Medical
2) Nursing
3) Technical (to include "estates", biomed, IT etc.)
4) Logistics (catering, stores, CSD, laundry etc.)
5) Admin

Can't wait for the first installment of "Breaking Biomeds" turf wars between the Crips of IT and the Biomed Boyz!!!

On a more serious note here in Italy it's a constant uphill struggle.....

Extract from the first chapter of "Breaking Biomeds" (sub-titled:- "Pump Boys versus the IT Mafia"):-

The technical support of biomedical equipment involves the application of certain specialised operational, workshop and repair techniques. These practical hands-on methods are constantly being developed or evolving.

The range of medical equipment found in a general hospital and serviced by medical engineering technicians (often known as "biomeds") typically embraces the following types of technology:-

1) Electrical (suction pumps, laboratory equipment)
2) Electronic (monitoring equipment, laboratory instruments, diagnostic systems)
3) Fibre-optics (lasers, endoscopes etc.)
4) Fine instruments (surgical tools, dental handpieces)
5) Gas controlling systems (anaesthesia machines, ventilators)
6) High voltage systems (radiographic equipment)
7) Hydraulics (operating tables, dental chairs)
8) Mechanical machines (some ventilators, pumps, beds, trolleys)
9) Microcomputer based systems (x-ray control systems, patient monitoring systems, microcomputers)
10) Optics (ophthalmic instruments, microscopes, laboratory instruments)
11) Pneumatics/fluidics (dental units, some ventilators)
12) Precision pumps (infusion pumps, dialysis machines, laboratory analyzers)
13) Refrigeration (refrigerators, laboratory instruments)
14) Steam (autoclaves, washers, cleaners)
15) Plumbing (washers, laboratory equipment)
16) Radio (ambulatory patient telemetry)

The scope of all this technology has traditionally been one of the main reasons that "techie" types are attracted to biomed work in the first place. The other reason usually being the desire to "do a bit of good" by applying technical skills within an healthcare environment (rather than - often more lucrative - employment in some other "electronics" discipline ... "defence", for example).

In recent times designers of medical equipment (like just about everything else, it seems) have felt the need to have equipment talk to each other, other devices, computers or networks (the internet for example), and such like.

The "true biomed" has, however, taken such progress in his (her) stride, generally recognising that "data" is just another "connection" to be dealt with (rather like electrical power, water, gases ... and what-have-you). In other words, nothing to fear; but rather a new challenge to be met, understood, and overcome.

In short, the "true biomed" (the proficient and dedicated medical engineering technician) needs to be, and remain, a multi-skilled and enthusiastic all-rounder.

The next edition of "Breaking Biomeds" (sub-titled:- "Pump Boys versus the IT Mafia") will include:-

17) Data (equipment interfacing and networks)

IT technicians response to the BME and Electrical technicians when shown where the data cable must run, "looks like hard work"