Re: Risk Management
"If your MRI scanner, for instance, relies on a no-longer maintained piece of XP-only software do you simply put your hand in your pocket for a few million to replace it, commission a rewrite and take the risk that it may fail in some respect to emulate the existing product or do you keep using XP?"
I'm bored with this BS.
How much do you think an MRI scanner costs vs the cost of a replacement computer and replacement software, when amortised across a countrywide fleet of MRI scanners.
What if such systems had been based on open standards for device control, document interchange, etc? NB open standards .ne. open source so no religious arguments please. The replacement of any component subsystem could have been a near-transparent upgrade. In fact, do the relevant open standards already exist for healthcare imaging? HL7? DICOM? Etc. It's a long time since I looked.
Separately, judging by the number of Scanning as a Service HGV trailers I see parked outside hospitals and elsewhere, many organisations have outsourced imaging services of that nature to commercial 3rd party organisations, so the 3rd parties (not the trusts) would be the ones doing the necessary upgrade work. Joe Public would still pay in the end.
"These sorts of issues are not easily solved. Of course they only exist in the real world so please feel free to keep helping with your advice."
O'Really? I think a far more common situation is that the issue is *already* solved technically (open standards or whatever) but vested interests don't want to go that way, for whatever reason.