Electronic Health Record (EHR)
The digital record of a patient's health information across providers — and the system clinicians spend most of their screen time inside.
An EHR holds a patient's longitudinal clinical record — history, medications, allergies, results, notes — and is designed to be shared across providers. An EMR is narrower, usually one practice's own record. The distinction matters commercially because interoperability obligations attach to the former, and it matters to design because a shared record means reconciling data entered by people with different conventions.
EHR interfaces are a well-documented source of clinician burnout, and the causes are consistent: documentation burden driven by billing rather than care, alert fatigue from warnings that fire constantly and are dismissed reflexively, and information density that buries the clinically relevant detail. Any product touching an EHR inherits this context — a new alert is not a neutral addition, it joins a stream clinicians have already learned to ignore.
Integration means HL7 FHIR
Most modern EHR integration runs through FHIR APIs, with access, scopes and vendor-specific behaviour that shape what a connected product can actually show.
In practice
A clinical decision tool added an alert for a drug interaction. Clinicians dismissed it in under a second at a 94% rate, because it joined about 60 daily alerts. Restricting it to the two highest-severity combinations cut firing by 80% and raised the rate at which it changed a prescribing decision from near zero to 12%.
Where teams get it wrong
- Adding alerts to a stream clinicians already dismiss reflexively.
- Designing for the administrator who buys rather than the clinician who uses.
- Treating documentation burden as a compliance constant rather than a design problem.
- Assuming EHR data is clean, structured and consistently coded.
- Ignoring that the record is shared, so conventions differ by contributing provider.
( Learn more )
Related terms
All terms- HL7 FHIRThe healthcare interoperability standard defining how clinical data is structured and exchanged over modern web APIs.
- Accessibility AuditA structured evaluation of a product against WCAG, producing a list of failures with severity, location and a route to fixing each one.
- Data TableA grid of rows and columns for scanning, comparing and acting on records — the screen most B2B users spend their day inside.
- AlertAn in-page message about something needing attention — persistent, placed where it applies, and gone only when the condition is.