4 ms·

> Meanwhile, over here in healthcare, I'm currently carefully evaluating whether to update some software packages from their 2011-release version to their 2015-

by midev 5y ago

> Meanwhile, over here in healthcare, I'm currently carefully evaluating whether to update some software packages from their 2011-release version to their 2015-release version This could partially explain why healthcare IT is some of the worst in the world. Can't imagine the number of vulnerabilities you have from using such outdated tech. From EHR systems, to basic appointment scheduling, to billing and insurance, everything is so poorly built and tedious for the users. Not to mention, healthcare is always falling victim to ransomware, shutting down entire hospital systems. I know you'll say you need to move slow, lives are at risk, etc. But what healthcare IT is doing now certainly doesn't work. So maybe push on the gas a little bit.

stan_rogers 5y ago
Bullshit. When your "minor issue" becomes something that kills people, you test the living bejesus out of it before you think of deploying. When even the slightest change in UI becomes a deadly operator error, you make damned good and sure that those errors won't happen. There are more things that there is no "undo" (or antidote) for than you can imagine. Having things not isolated is the only real problem.
- midev 5y ago
  > Bullshit. When your "minor issue" becomes something that kills people, you test the living bejesus out of it before you think of deploying. At no point did I say not to test before rollouts. > When even the slightest change in UI becomes a deadly operator error Stop being dramatic, because it's part of the problem. Yes, UI's are critical, and these UI's are absolute garbage. You need to improve rapidly, not agonize over bullshit changes in Microsoft Office. https://www.thedoctors.com/articles/electronic-health-records-continue-to-lead-to-medical-malpractice-suits/ https://www.thedoctors.com/articles/electronic-health-record... https://ehrintelligence.com/news/diagnostic-medication-errors-rank-among-most-common-ehr-related-issues https://ehrintelligence.com/news/diagnostic-medication-error... EHR's are killing people because they are so poorly built. To reiterate, what you're doing is not working. > you make damned good and sure that those errors won't happen You're not making sure those errors are not happening, is the point.

by midev 5y ago

stan_rogers 5y ago

Bullshit. When your "minor issue" becomes something that kills people, you test the living bejesus out of it before you think of deploying. When even the slightest change in UI becomes a deadly operator error, you make damned good and sure that those errors won't happen. There are more things that there is no "undo" (or antidote) for than you can imagine. Having things not isolated is the only real problem.

midev 5y ago
> Bullshit. When your "minor issue" becomes something that kills people, you test the living bejesus out of it before you think of deploying. At no point did I say not to test before rollouts. > When even the slightest change in UI becomes a deadly operator error Stop being dramatic, because it's part of the problem. Yes, UI's are critical, and these UI's are absolute garbage. You need to improve rapidly, not agonize over bullshit changes in Microsoft Office. https://www.thedoctors.com/articles/electronic-health-records-continue-to-lead-to-medical-malpractice-suits/ https://www.thedoctors.com/articles/electronic-health-record... https://ehrintelligence.com/news/diagnostic-medication-errors-rank-among-most-common-ehr-related-issues https://ehrintelligence.com/news/diagnostic-medication-error... EHR's are killing people because they are so poorly built. To reiterate, what you're doing is not working. > you make damned good and sure that those errors won't happen You're not making sure those errors are not happening, is the point.