Everyone hates the electronic medical record
Electronic medical records are widely seen as a double‑edged sword: they make data more accessible for patients and enable coordination across providers, yet impose heavy cognitive and administrative burdens on clinicians. Commenters describe EMR systems as bloated, badly designed enterprise software optimized for billing, compliance, and corporate control rather than usability or care quality, with regulatory complexity and market capture (e.g., Epic) reinforcing the status quo. Many argue that the core problems are sociotechnical—broken workflows, misaligned incentives, poor operations, and weak interoperability—so better interfaces alone won’t fix healthcare’s deeper structural issues.
Perceived Benefits for Patients
- Many patients report clear wins: unified access to labs and notes, easy prescription renewals, telehealth, rapid record export to new providers, and cross-clinic visibility (e.g., vacation care, multiple GPs).
- National or regional EHRs in some countries (Nordics, Estonia, parts of Europe, Israel, Australia) are described as highly convenient for patients, enabling seamless care across facilities.
- Patient-facing portals and Apple Health integrations are appreciated, but some warn that once data is in third‑party apps, HIPAA protections no longer apply; privacy then depends on app policies.
Clinician Burden and UX Problems
- Frontline staff overwhelmingly describe EMRs as slow, cluttered, and inconsistent; major contributor to burnout, with some systems reportedly cancelling critical orders or lagging during ICU care.
- Data entry and documentation work has shifted from dedicated clerical staff to clinicians, often with poor tools and minimal training.
- EMRs try to do “everything” (billing, scheduling, orders, notes, reporting), creating overloaded, hard‑to-learn interfaces; usability fixes are often deprioritized vs. revenue-cycle features.
Interoperability, Standards, and Patient Access
- In the US, corporate silos and variable implementations mean inter-hospital data sharing is unreliable, though the 21st Century Cures Act and FHIR APIs now allow patients to aggregate their own records.
- Standards like HL7, FHIR, and CCDA exist, but are so flexible that compliant systems can still be semantically incompatible; implementation guides and local conventions matter.
Operations, Regulation, and Sociotechnical Complexity
- Several argue EMR pain reflects deeper operational and regulatory complexity: liability tracking, billing codes, timing rules, and protocol enforcement all drive rigid workflows and extra clicks.
- Each hospital/clinic has evolved idiosyncratic processes; EMRs become massively configurable “ERPs for medicine,” entangling software design with messy, politicized local practices.
Vendors, Market Structure, and Public vs Private Efforts
- Large vendors (especially Epic, also Cerner/Oracle and others) dominate due to certification costs, compliance burden, and expensive, risky migrations, creating strong lock‑in and weak UX incentives.
- Reports from multiple countries describe troubled Epic deployments, though some sites and some patients find Epic workable or even good.
- Public or government EHR projects (e.g., UK NPfIT, some Scandinavian and US VA efforts) have had mixed to poor outcomes: huge costs, scope creep, political interference, and uneven clinician satisfaction.
- Open-source and modular alternatives (OpenMRS, OpenEMR, ClearHealth, personal health records) exist but face regulatory, integration, and market-entry barriers.
Security, Privacy, and Email
- Auto‑logout, complex passwords, and portal “you have a message” emails are often blamed on security/ HIPAA requirements; some note patients can legally opt into less secure channels but institutions remain risk‑averse.