It looks like a VB app from the 90s. Text layout is poor, often overflowing boxes, it's not customizable.
Epic is where it is because hospitals are so fucking locked in.
It looks like a VB app from the 90s. Text layout is poor, often overflowing boxes, it's not customizable.
Epic is where it is because hospitals are so fucking locked in.
That said, lots of the problems with Epic is it is used so differently between hospitals/installs. It's less a EMR + scheduler + hospital management app than a toolkit used to construct those for big enough medical companies. That inevitably doesn't lead to nice software: see all enterprise software everywhere.
I’m rooting for something like this in the long term: https://github.com/openemr/openemr
I desperately want it to gain some real traction.
Working in the enterprise world, including the enterprise healthcare world... it's not "right", but as long as it exists as a PHP webapp...
I don't see that happening. No matter how good a PHP webapp it is.
I really want it to succeed. But there is so much further to go. For example, on the subject of backing up your EMR data, there is this:
> Disaster can strike at anytime. Backing up will mean the difference between a mild inconvenience and a major imbroglio.
> Choose a method according to the operating system from this webpage.
> Windows users are advised not to rely on the built-in utility once their file size becomes too large. The reasons are discussed in this Forum thread.
That's it?? That's the extent of your backup discussion for a business critical application storing PHI? Oof.
Any CIO remotely considering OpenEMR, even one hugely cost-constrained, is going to run for the hills.