4 ms·
> In most implementations, neither Cerner not Epic encourage structured data recording except for billing codes. > The software is designed to be sold to admin
by whatl3y 7y ago
> In most implementations, neither Cerner not Epic encourage structured data recording except for billing codes.
> The software is designed to be sold to administrators and, as currently designed is unquestionably leading to worse outcomes for patients.
disclaimer: I’m a former Epic employee who worked on their inpatient app.
Do you have data or literature to support these statements for a typical Epic implementation or is this just anecdotal and biased?
Although there were ALWAYS some sort of issues and pushback from clinicians during implementation and go live, Epic software and data flow literally revolves around patient care and not billing. I don’t recall exactly which apps came first when Epic was born in the 1970s, but I believe their billing and admin apps came much later than many of the clinical apps. It’s actually why they still use a backend on top of mumps and cache, because the way data is stored and flows in these systems can do so literally around the core patient data structure, which should theoretically make a clinicians job easier to review a complete patient record (not make it easier for billing).
- AzzieElbab 7y agoI worked in healthit for a few years. I have not seen a single piece of software or spec that wasn't up for a major revamp. Well, maybe snomed
- whatevershesaid 7y agoGenerally agree with your sentiments, with one correction: Scheduling/Revenue apps came first (Cadence was the first app to go live in 1983) with clinical apps launching in the 90s (Ambulatory in 1992 and Inpatient in 1998). Source: staff meetings (former Epic IS) and this old article: https://isthmus.com/news/cover-story/epic-systems-an-epic-timeline/ https://isthmus.com/news/cover-story/epic-systems-an-epic-ti...