3 ms·
Its not just YOUR product though - its the entire suite of products that medical institutions use. Be it the EHR, the patient management, the radiology, the car
by lvspiff 7y ago
Its not just YOUR product though - its the entire suite of products that medical institutions use. Be it the EHR, the patient management, the radiology, the cardiology system - each one deals in IE11 instead of a more modern tech stack. So if you end up being the outlier your product is more than likely going to end up being cut in preference for something with fewer features even.
- WorldMaker 7y agoIt's certainly not an easy bootstrap problem (by way of a mexican standoff). It's possible many of those projects individually are just waiting for the first to take the first risk and move forward so the rest can just claim to be following someone else's lead. To badly mix metaphors: a rising tide floats all boats, it's just sometimes you have to be the first to remove your finger from the dyke to raise the tide. Like I said, it's always going to be a calculated risk, and I mentioned that losing customers is certainly a risk involved. Sometimes a small loss of customers is an acceptable risk. There are mitigations for such risks such as making sure that "fewer features" alternative is your own (at the right maintenance costs), but also including taking things to standards/regulatory boards. Using out-of-date software is a HIPAA risk and an ethics risk. There are ways to convince HIPAA enforcement auditors and/or groups like the AMA that it is too much of a risk, or too unethical a risk and that some sort of upgrade horizon should be spread across the industry. That's not easy either, but it's not impossible, and it's probably a good idea in general in the long run (the regularity with which Day-0 vulnerabilities are disclosed would give a lot of weight to the risks of falling behind on software upgrades, for instance).