3 ms·
The problem is Epic's mentality of "do it our way Or Else" which seems to be across the entire software package. I once asked my former hospital IT team why we
by kotaKat 5y ago
The problem is Epic's mentality of "do it our way Or Else" which seems to be across the entire software package.
I once asked my former hospital IT team why we didn't get Epic ourselves and it was described to me as "You don't get to buy Epic, they reach out and 'offer' to sell it to you". You then buy what they tell you to buy, hire who they tell you to hire, train what and who they tell you to train. If you do any bit of it wrong it eats into your support costs because of a "quality of install" score that either raises or lowers your annual support fees.
- nradov 5y agoThat's a reasonable position for Epic to take. Most failed EHR implementations have been caused by excessive customization. Hospital staff often wanted to make the new software fit their existing idiosyncratic processes and forms. But in reality there was no valid business or clinic reason for most of those differences between hospitals. It's better in the long run to reengineer hospital operations to match industry best practices and the selected EHR, regardless of whether that EHR is Epic or one of their competitors. As a local hospital IT director told me, "Vanilla is the best flavor." By that she meant that if they purchased a piece of software they were going to use it as-is and not get sucked into a black hole of customization.