| Course | HI570 Legal and Ethical Issues in Health Information |
|---|---|
| Unit | Unit 4 |
| Paper type | E-discovery memo |
| Length | About 880 words, 6 pages double-spaced |
| Format | APA 7 student paper |
| School | Purdue University Global |
| Program | MS in Health Informatics |
| Updated | October 2026 |
Free sample paper for HI570 Unit 4
The Duty Began Before the Letter: A Unit 4 E-Discovery Memo on Preserving Alarm, Audit and Messaging Data After a Surgical Floor Death
[Student Name]
Purdue University Global
HI570: Legal and Ethical Issues in Health Information
Unit 4 E-Discovery Memo
[Instructor Name]
[Date]
Larchmere Health, the patient, every system setting and every date are composite; the rule commentary and sources cited are real.
Memorandum
To: General Counsel
From: Director of Health Information Management
Date: May 19
Re: Preservation and production of electronic information, surgical floor death of April 8
Summary
The duty to preserve likely began on April 8 or 11, not on May 19 when the letter arrived. Alarm events from the patient's final shift were deleted on May 8 by the alarm middleware's rolling thirty-day purge, after the duty arose. The hold should issue today across six systems. Replacement evidence exists for much of what was lost, and nothing suggests anyone intended to destroy it.
Timeline
April 8, night: the patient died on the surgical floor; the charge nurse filed a serious safety event report that night. April 11: the family met with the unit manager and asked why alarms had not brought a nurse sooner. May 8: thirty days after April 8, the middleware purged that night's alarm events. May 19: a preservation letter arrived from the family's attorney.
When the Duty Began
Preservation obligations attach once a claim can reasonably be foreseen, which is often well before any demand is written. A serious safety event involving a death, followed three days later by family questions about alarm response, would lead a reasonable organization to anticipate a claim. The commentary on electronic discovery treats exactly these signals, an internal incident review and complaints from the people affected, as triggers that can precede any formal demand (The Sedona Conference, 2018). The safer reading for Larchmere is that the duty began by April 11.
Systems the Hold Must Cover
1. Electronic health record: retention indefinite; custodian HIM; action: flag the record and suspend any purge of draft notes.
2. Record audit log: retention seven years; custodian information security; action: export the patient's access and edit events from March 1 forward.
3. Alarm middleware: retention thirty days; custodian clinical engineering; action: suspend the rolling purge for the unit now and export what remains.
4. Secure messaging: retention ninety days; custodian information technology; action: suspend deletion for the unit's staff and the physicians who messaged about the patient.
5. Nurse call system: retention sixty days; custodian facilities; action: export call events for the room from April 1 to 9 before they purge on June 7.
6. Staffing system: retention three years; custodian nursing administration; action: preserve assignments and break records for the April 8 shifts.
Two of the six systems will delete relevant data on their own within three weeks unless someone changes a setting today.
What Is Lost and What Can Replace It
The alarm events for April 8 were purged on May 8. Under the federal rule on failure to preserve electronically stored information, a court may act only if the information should have been preserved, was lost because reasonable steps were not taken, and cannot be restored or replaced through other discovery; the most severe measures require a finding of intent to deprive the other party of the information (Fed. R. Civ. P. 37, 2015). Nothing suggests intent: the purge was an automatic setting no one changed.
Replacement sources may reduce any prejudice. Vital signs charted by nursing record what the monitor showed at intervals. The bedside monitor stores its own events for several days, and clinical engineering should check whether the unit's monitor has been reassigned. The middleware vendor keeps backups for disaster recovery and should be asked in writing whether the April 8 data survive. The safety event review, which used alarm screenshots on April 9, may contain images of the relevant events.
Production of the Health Record
The production should distinguish the legal health record, which is produced as the business record, from source system data, which is produced on specific request. For the record, a certified copy in its native electronic format with metadata, or a paginated image set with a load file, should be offered. Audit log data should be produced as a spreadsheet with field definitions. Federal rules allow the requesting party to specify the form of production, and a meet and confer on form is recommended before anything is sent (The Sedona Conference, 2018).
Recommendations
1. Issue a written hold today to the six custodians named above, with the settings to change.
2. Ask the alarm middleware vendor in writing about backups.
3. Change the unit's alarm purge setting so that any serious safety event involving a death automatically suspends deletion for that unit.
4. Document every step taken from today, so the record shows reasonable efforts once the duty was recognized.
Limits of This Memo
This memo describes health information practice and the systems involved. It is not legal advice, and counsel should decide how to describe the loss of the alarm data if asked. Record retention schedules for the middleware and messaging systems should also be reviewed against the hospital's policy, since both are shorter than the period during which claims are commonly brought (Oachs & Watters, 2020).
References
Fed. R. Civ. P. 37 (2015). https://www.law.cornell.edu/rules/frcp/rule_37
Oachs, P. K., & Watters, A. L. (Eds.). (2020). Health information management: Concepts, principles, and practice (6th ed.). AHIMA Press.
The Sedona Conference. (2018). The Sedona Principles, third edition: Best practices, recommendations and principles for addressing electronic document production. The Sedona Conference Journal, 19, 1-207.
What the HI570 Unit 4 assignment asks for
Unit 4 typically asks you to advise counsel or leadership on preserving and producing electronic health information after a potential claim. Expect a memo with a timeline, an analysis of when the duty to preserve began, a list of systems and custodians, a discussion of any lost data and a plan for production. Five pages is a common length. Answer the timing question early, since it determines whether anything was lost after the duty arose. List each relevant system with its retention period and the setting that must change. Apply the federal rule on failure to preserve electronic information carefully, including its replacement and intent elements. Separate the legal health record from source system data in the production plan.
Inside the HI570 Unit 4 example
The memo opens with a summary of when the duty began, what was lost and what to do today. A timeline marks the death, the safety event report, the family meeting, the automatic purge and the letter. The timing section argues that the duty arose by day three, drawing on Sedona Conference commentary. Six numbered systems follow with retention, custodian and action, and the highlighted sentence warns that two will delete data within weeks. A section applies the federal rule to the lost alarm data and lists replacement sources, from charted vital signs to vendor backups. Production guidance separates the legal health record from audit and source data. Four recommendations and a note on the memo's limits close it.
Where the points sit in the HI570 Unit 4 rubric
E-discovery memos are generally graded on accuracy of the legal analysis, completeness of the preservation plan, practical usefulness and professional writing. Legal accuracy weighs heavily: graders look for a correct statement of when the duty arises and of the federal rule's elements. Completeness is judged on whether all relevant systems are identified with retention and custodians. Practical usefulness earns credit when the memo tells the reader exactly what to do and by when. Candor about lost data and replacement sources is rewarded. Production guidance should distinguish the business record from source data. Memo format and correct citations complete the rubric. Memos that treat the letter as the trigger, or list systems without actions, tend to lose points.
HI570 Unit 4 help: mistakes that cost points
Graders most often send this memo back because the writer counted the duty from the day the letter came. Another is listing only the electronic record and forgetting alarm, messaging and audit systems. Some students state the federal rule loosely, skipping the replacement or intent elements. Others hide the loss of data rather than addressing it. Production plans often omit the form of production. Infusion pump logs, telemetry archives and badge readers all behave differently on retention; list the systems in your scenario and the hold table will be written for those.
Get an HI570 Unit 4 example written to your instructions
Litigation scenarios differ mainly in their dates and systems, so include whatever your Unit 4 prompt gives for both, along with the memo format and rubric. A first memo carries no charge and arrives within 24-48h, dating the duty to preserve, scoping the hold system by system and stating what production would contain. The paper above is an original model document written by our desk, not a submitted student paper and not an official Purdue University Global document.
More HI570 papers and MS in Health Informatics samples
- HI570 Unit 1: Discussion Board Argument
- HI570 Unit 2: Case Brief
- HI570 Unit 3: Release of Information Decision
- HI570 Unit 5: Ethical Dilemma Analysis
- HI570 Unit 6: Secondary Use Evaluation
- HI570 Unit 7: Liability Risk Analysis
- HI570 Unit 8: Seminar Reflection
- HI570 Unit 9: Policy Revision
- HI570 Unit 10: Legal and Ethical Position Paper
- HI560 Unit 4: Data Quality Assessment
- HI555 Unit 4: Charge Capture Review
- HI550 Unit 4: Staffing and Workload Plan
- HI501 Unit 4: Decision Support Rule Design
HI570 Unit 4 questions, answered
Does the federal rule apply if the lawsuit is in state court?
Not directly. The Federal Rules of Civil Procedure govern federal cases, and state courts apply their own rules, though many states have adopted provisions modeled on the 2015 federal amendments. A memo for class can use the federal rule as the framework and note that the governing state rule should be confirmed, which is what the example does.
Is the audit trail part of the legal health record?
Usually not by default. Many organizations define the legal health record to exclude audit logs, but courts often find audit trails discoverable when timing or alteration of entries is disputed. The memo should state the organization's own definition, then treat the audit trail as a separate source that the hold must still preserve.
Is this memo legal advice?
No. It is coursework on a composite case, reflecting federal rules as they stood in 2026. Real preservation decisions belong to the organization's counsel and records custodian. The example shows how a health information professional frames the systems, dates and retention settings counsel needs, which is the part HIM leaders are expected to know well.
Where can I find a free HI570 Unit 4 sample paper?
The full Unit 4 memo appears here, with its timeline, six-system hold list, analysis of the lost alarm data and production plan.
When does a hospital's duty to preserve electronic data begin?
Once a claim is reasonably foreseeable, often long before anything arrives in writing, for example after a serious safety event and family questions about what happened.