I was in the ED the other day and noticed that they use a mix of Windows 7 and Windows 10. My question is two part.
- Do you know of hospitals using Linux?
- Besides legacy software and unwanted downtime, is there any reason why they wouldn’t use Linux?
Software for equipment and software for imaging etc. I work in healthcare. I’d love to use Linux but we’re stuck on software that is based on Java from 8 years ago, as the newer version is not compatible with some older equipment. Add to that, the newer version costs $500 per user to upgrade with no additional features, and this is just for one medical camera, that treats the camera like a webcam. The problem is how it stores images is in a custom database, through a server. Otherwise, the Java part should be easy enough.
Medical equipment is super expensive and they only make a few thousand of some of them. So, the software is super expensive too and not updated nor is there versions for Mac or Linux. Heck, most of them don’t officially support windows 10 or 11. It’s really frustrating too, as most are really a simple bridge that connects to the machine to give instructions or receive data. They are not usually drivers, but send data over the network. An open format would suit better for security too, as all this old software will be pretty leaky.
Did hospital IT work and 100% agree.
There’s a reason that stuff is ideally on its own separate vlan to isolate it as much as possible from the network too
Hahah yeah. 100% air gapped. About as secure as a paper door. Sometimes I feel like they just put it out in the field after they get their first successful test done and then forget about it forever.
GE imaging kit (certainly their CT scanners) do (or did for as long as I used them) run on Linux.
Helped my dad do tech support for a doc office. Even simple stuff like glucose meters barely worked on windows 7, and broke with windows 10. The web portal they used required a specific version of internet explorer to function. I think the biggest issue is always going to be how slowly these devices work in terms of drivers and software compatibility. For security and cost reasons, I’d guess.
It would be the same if they used Linux, they’d require something like Red Hat 6.0. 😄
The medical world is technically illiterate and handles a lot of money so the vendors take advantage of that to do heavy lock-in. Everything is tied down to super specific software versions, everything is proprietary, and you pay through the nose for any change.
Hell, poorer clinics use old versions of EMR/EHR software that they bought in '08 and host locally. Some of that shit barely supports Windows 7. Some of that software doesn’t support things like HL7 properly so getting the data out and into a newer one can be cost prohibitive in and of itself because you’ve got to pay someone to write a translator for a shitty database in a format that was purposefully confusing to keep vendor lock in for a vendor that went tits up a year later.
I mentioned before that I have a lot of certificates for a lot of those companies that no longer exist. If it wasn’t soul crushing I could probably make a decent living just moving people from those systems. But my soul is already a shriveled piece of garbage and I don’t want to purposely squeeze the last little bit of juice out just yet.
It’s really about the software.
Yeah, I had a feeling it would be.
I work IT at a hospital here in the US. The key issue is compatibility. Most of our vendor software flat-out does not support Linux at all, either on the client or server side. Shit, half of it barely even works on modern versions of Windows.
Designed for Windows 3.1
Upgrade if’n you dare
Shoot, that’s hardly an exaggeration - I was only recently able to deprecate the last of our Server 2003 instances, which was running a program originally designed for 2000 Server!
I know Linux has little to no penetration in health equipment firmware because a lot if not most of them have hard real-time requirements that Linux just doesn’t quite reach. QNX4 is a real-time Unix flavor that has been used in fancy graphical heartbeat/multi stat monitors. Its microkernel architecture allows for a watchdog to restart individual drivers so it’s more fault tolerant.
Microkernels for the win! Monolithic kernels can be built tiny though, so they are also pretty stable
There are hospitals running on SAP systems. Those servers will be 99% linux based. The rest are managed by crazy people.
None of the hospitals I’ve worked at (in the US) have used Linux, and I’m pretty surprised some do! Given that we used Internet Explorer up until the very last second before it was not supported, I don’t know if any change would be welcomed, unless a hospital somehow started out with Linux. But at the end of the day, it would be about to e electronic health record, if it was supported or not… I don’t know if Epic, Cerner, or AllScripts do!
The hospital I was seemed to still be using Internet Explorer….
I wonder how the various software needs of hospitals would be with Wine? My guess would be that it wouldn’t be stable enough for them.
Equipment firmware has rigid stability constraints. Office software, if IE is good enough, a tested and unchanging version of Wine is good enough.
they are all moving to sas… browser-based, browser agnostic systems. everyone is. people have actually learned from the IE mistake.
not there arent a few holdouts… nothing more painful than trying to bolt on new regulatory requirements to a 25 year old app. sigh
Compatibility, compliance and retraining,
I can give some guesses on 2.
- Familiarity. Most people are familiar using Windows. Nurses aren’t necessarily tech savvy, so an unfamiliar system might threw them off.
- Maintenance. It’s easier to recruit people who know how to maintain Windows systems. Linux is tricky because it comes in so many different distributions, and any maintainer must be aware of these differences.
- UI sucks big time on Linux. It’s so much easier and reliable to just do a winform.
- Communication with other equipment. I guess some computers are talking to other medical equipment, and those equipment might only have drivers written in Windows, because that’s what most are using.
- If it ain’t broken, don’t fix it. Why change to Linux when Windows is doing the job?
UI sucks big time on Linux. It’s so much easier and reliable to just do a winform.
I didn’t think about that. Makes sense though, especially when you combine the fact that most hardware will be designed with Windows in mind as you mentioned.
I wish I could say that the UI in EMRs *doesn’t * stick big time 😭
I really thought Allscripts was going to get their shit together a bit over a decade ago. We kept hearing from their reps that they were working on a much better UI.
It is still hot garbage.
Someone who works in hospital system posted about this in a comment earlier : https://lemmy.ml/comment/9989330
Ohh, I haven’t seen that yet. I’ll have a read through.
Hospitals have no IT budget and are the most insecure things around.
Additionally there staff are not exactly the most tech savvy
-
Our childrens hospital (besides the ICU that uses a phillips solution on windows, which integrates with the monitoring and anesthesia equipment) runs linux, however they do this in a virtual environment on windows, the reasoning I am not sure about, potentially to sandbox the electronic system they are using.
-
Its almost exclusively to do with the software they need, it often wont run on linux or will have limited support.
-
I worked for a device manufacturer that used Linux under the hood. It happens. Depends on what the staff knows and likes when designing.
I’ve seen some optometry equipment running RHEL
Hospital SysAdmin here.
Our infrastructure is roughly 95% windows and 5% Linux or Unix. Simply put: the requirements of the software/systems that the hospital requires to function properly is what dictates the OS.
We have a couple of major systems running on a handful of AIX Unix boxes and several dozen other systems that run RHEL, Cent, and Ubuntu. Not including hypervisors, the rest of our infrastructure is windows based and ALL of our workstations are windows.
Every app is unique, and annoyingly there is no consistency within all of a single companies applications. For example, I’m working on a GE Carescape upgrade which uses CentOS 7 but GE Time and Attendance uses Windows Server.
Guess open APIs are an unknown to medicine device vendors.
It’s cause Epic/McKesson has complete control over the EMR world so everything has to work with them to some degree.
GNU health is great but I haven’t seen where it could support the massive amount of legal and monetary hoops that Epic and co have to jump through as well.
For some reason there just isn’t a lot of volunteer efforts/space for open source development in the healthcare world.
