The jurisdictional context
The Washington, DC framework.
Use these topics to frame a discussion with counsel about the electronic record. The EMR discovery guide connects that discussion with requests for the underlying data.
- 01
Expert-evidence standard
In Motorola Inc. v. Murray, the D.C. Court of Appeals adopted the Rule 702/Daubert reliability standard in place of Dyas/Frye. Expert qualifications, reliable methods, and their application to the particular evidence require scrutiny; admissibility remains a decision for the court.
Motorola Inc. v. Murray, 147 A.3d 751 (D.C. 2016) (en banc)
- 02
Merit & pre-suit requirements
Before filing a medical-malpractice action in D.C. Superior Court, the person bringing suit generally must give the intended defendant notice at least 90 days before filing. The notice must explain the claim's legal basis and the injuries and losses; the court may excuse a timing failure upon a showing of a good-faith effort to give notice. A technical EMR review does not replace counsel's compliance with this process.
D.C. Code §§ 16-2801, 16-2802, 16-2803 · At least 90 days before filing; conditional limitations extension
- 03
Statute of limitations
D.C. Code § 12-301(8) provides a 3-year period from accrual for claims without another specifically prescribed limitation. Counsel must assess accrual, tolling, and any claim-specific deadline. If the required pre-suit notice is served within 90 days of the applicable period's expiration, § 16-2803 extends the filing time to 90 days from notice service; it does not automatically add 90 days to every claim.
D.C. Code §§ 12-301(8), 16-2803
- 04
Record retention
The District's hospital regulation, 22-B DCMR § 2030.7, requires patient medical records to be kept for at least 10 years after discharge, or for minors until 3 years after attaining majority. This is a hospital medical-record rule, not a guarantee that every audit event, note version, or backup is retained for the same period. Confirm the facility's system configuration and separate log-retention policies, and address preservation early.
- 05
Spoliation & concealment
D.C. Superior Court Civil Rule 37(e) addresses electronically stored information that should have been preserved for litigation but was lost through a failure to take reasonable steps and cannot be restored or replaced. Upon prejudice, the court may order measures limited to curing it. An adverse presumption or instruction, dismissal, or default under Rule 37(e)(2) requires a finding of intent to deprive another party of the information's use; a missing export alone does not establish those conditions.
A medical-record retention rule does not, by itself, establish how long every audit log or revision history is retained. Confirm the available data and preservation needs with the producing organization.
From production to findings
How an EMR review fits a Washington, DC case.
- 01
Examine the record's completeness.
Compare the chart with available activity and revision history. Independent audit-trail analysis helps identify discrepancies and questions for the producing organization.
- 02
Go deeper than the chart.
EMR metadata analysis examines timestamps, identifiers, and revision data behind the printed record. Pair that work with the guide to the EMR system used in your matter.
- 03
Prepare findings for counsel's review.
A documented methodology supports deposition preparation and expert-witness work. The findings identify their sources, limits, and the next questions to resolve.
The work product
What you receive.
The scope is agreed for each engagement. Available work includes:
Audit trail & metadata findings
Entry-timing reconstruction, edit and deletion history, copy-forward detection, and user attribution — what changed, by whom, and when.
Revision-history reconstruction
Where a note exists in multiple states, the full sequence is rebuilt from the logs, separating a disclosed addendum from a silent alteration.
Discovery support & model RFP language
Request-for-production language tuned to the specific EMR, so you ask for what the system can actually produce — not an ambiguous label that invites objection.
Deposition prep & expert consulting
Outlines to question records custodians and IT witnesses, plain-language translation of the findings, and consulting or testifying expert support.
Completeness review
An access log shows who viewed the chart; an audit trail shows what changed. A focused review of what was produced, what's missing, and what to demand next.
Related reading: signs of medical-record alteration in EMR metadata — patterns to investigate in the underlying system history.
Common questions
EMR review in Washington, DC.
Do you support EMR cases in Washington, DC?
Yes. EMRCheck provides independent forensic analysis of produced EMR/EHR audit trails and metadata for plaintiff attorneys handling District of Columbia matters. A paid engagement can examine entry timing, revisions, authorship, and production gaps within the available evidence, with scope and fees agreed before review begins.
How does the District's expert-evidence standard affect an EMR review?
Motorola Inc. v. Murray adopted the Rule 702/Daubert reliability framework. An EMR review should document the source data, timestamp definitions, method, and limits of each conclusion so counsel can assess the proposed expert opinion. The court decides admissibility; a system-generated log is not automatically admissible merely because it came from an EMR.
Does a technical EMR review satisfy D.C.'s pre-suit notice requirement?
No. D.C. Code § 16-2802 generally requires notice to the intended defendant at least 90 days before a medical-malpractice action is filed in Superior Court. Section 16-2803 provides a conditional extension when notice is served within 90 days of the applicable limitations deadline. Counsel must calculate and satisfy those requirements; an EMR analysis may inform the record questions but does not provide notice or determine the filing deadline.
Does the hospital's 10-year record rule mean its audit trail will still exist?
No. The hospital retention rule in 22-B DCMR § 2030.7 concerns patient medical records. It does not by itself establish the retention or completeness of audit logs, revision histories, or backups. Ask about the actual system, purge schedules, export filters, and preservation steps. If electronic information has been lost, counsel must evaluate the specific requirements of Superior Court Civil Rule 37(e) before seeking a remedy.
Go to the source
Primary references.
Starting points for the authorities discussed in this guide. Counsel should check the current text, applicable exceptions, and the law governing the particular matter.
- Motorola Inc. v. Murray · Rule 702/Daubert adoption, en banc opinion
- D.C. Code § 16-2801 · Superior Court and healthcare-provider definitions
- D.C. Code § 16-2802 · Notice of intention to file suit
- D.C. Code § 16-2803 · Conditional extension of limitations
- D.C. Code § 12-301 · Limitations periods
- DC Health hospital regulations · 22-B DCMR § 2030.7, retention
- D.C. Superior Court Civil Rule 37(e) · Lost electronic information
This page is educational information, not legal advice. EMR Check provides consulting and analysis services, not legal representation, and using this site does not create an attorney–client relationship.