EMR systems
Every major EMR audits differently
The right discovery request depends on the system. These guides cover each EMR/EHR platform's audit-trail and access-log reporting, what to demand in discovery, and the production gaps that hide late entries and alterations.
Epic
Epic stores far more about how a chart was created than the printed record reveals. The access logs, audit trail, and note revision history live in the back end — and are routinely left out of a standard records production.
Discovery guideOracle Health (Cerner)
Cerner, Cerner Millennium
Oracle Health (formerly Cerner) splits its audit data across tools — privacy/access auditing is handled differently from clinical-change history, and a production limited to one leaves the other invisible.
Discovery guideMEDITECH
MEDITECH MAGIC, Client/Server, Expanse
MEDITECH's audit detail depends heavily on which generation of the platform a facility runs — and the version itself is often the first thing a production fails to disclose.
Discovery guideathenahealth
athenaOne, athenaClinicals
Because athenahealth is cloud-hosted, the practice does not hold the servers — but the audit history still exists, centrally, and 'we don't control it' is not the end of the inquiry.
Discovery guideeClinicalWorks
eCW
eClinicalWorks distinguishes between locked notes, addenda, and edits — and whether a note was changed after it was finalized is exactly the question its audit log is positioned to answer.
Discovery guideVeradigm (Allscripts)
Allscripts, TouchWorks, Professional EHR, Sunrise
Allscripts — now Veradigm — is not one product but a family of them, and each line audits differently. The decisive first question is which product the provider actually runs.
Discovery guideNextGen Healthcare
NextGen Enterprise, NextGen Office
NextGen's ambulatory documentation leans heavily on templates and copy-forward — making cloned and carried-forward content one of the integrity questions its audit data is most useful for.
Discovery guide