Hacker News new | ask | show | jobs
by ShirtlessRod 2338 days ago
I fundamentally disagree with the idea that the system can somehow overcome poor implementation; guardrails can only do so much. At the end of the day you can set up almost any piece of software in a way that hinders rather than helps a user. At some point the organization needs to take some responsibility for that.

At any rate, this all started with a glib "garbage software" comment, so I suppose I should happy that you acknowledge that the implementation requirements set by the organization have at least something to do with overall user satisfaction.

2 comments

I used to work in IT where I worked with sizeable Epic installations... and now I’m a clinician amongst other things.

I’m going to agree with the garbage software sentiment.

I will say that Epic implementations tend to be liked better than alternatives... but when it replaced some piece of shit Meditech implementation nursed from 1980 that’s not really high praise dude.

> I fundamentally disagree with the idea that the system can somehow overcome poor implementation

If very large amounts of 'implementation' have to be done on top of the software, then that's also a sign of bad design. It should be handling more of the implementation and making it more streamlined.

You’ve just described Jira, or really any other heavily customisable tool that can fit multiple complex workflows.
Having used a dozen EMR systems and Jira, I'd say Jira is much better at its job than most EMRs are at theirs. In fact, now that you mention it: you could easily model each patient as an epic, assignments to various people on various teams (ICU, pharmacy, lab, etc), to-do/in-progress/done. Holy cricky, you may have just cracked the EMR nut.
Just make sure you don't move the epic to "Done" status.
I'll take 5% as an innovators fee please and thank you.
They already have an option like that. The problem is a lot of organizations still want to do their own thing or have their own requirements they want to impose on their users, which is where the large amounts of "implementation" comes from.