| Course | HIM FPX 3640 Managing Electronic Health Records Systems |
|---|---|
| Assessment | Assessment 2 |
| Paper type | EHR downtime plan |
| Length | About 1,130 words, 5 pages |
| Format | APA 7 student paper |
| School | Capella University |
| Program | BS in Health Information Management |
| Updated | September 2026 |
Free sample paper for HIM FPX 3640 Assessment 2
An Electronic Health Record Downtime Plan: Planned and Unplanned Outages, Paper at the Point of Care, and a Reconciliation That Proves Nothing Was Missed
Student Name
Capella University
HIM FPX 3640: Managing Electronic Health Records Systems
Instructor Name
Month Day, Year
Introduction
Hospitals now depend on their electronic health record for nearly every step of care, from registration and orders to medication administration and results. When the record is unavailable, care must continue safely and every action taken during the outage must be recorded afterward. Sittig and Singh (2012) argued that the safe use of electronic health records requires planning for their failure, including downtime procedures, because outages can create hazards such as missed results and medication errors. The federal SAFER guide on contingency planning offers recommended practices for preparing for and recovering from outages (Office of the National Coordinator for Health Information Technology, 2016). This paper sets out a downtime plan for a composite 200-bed hospital, here called Cedar Point Hospital.
Planned and Unplanned Separated
Planned and unplanned downtime differ in warning, duration, and preparation, so the plan treats them separately. Planned downtime occurs for upgrades and maintenance. It is scheduled at least two weeks ahead, usually between 1 a.m. and 5 a.m. on a weekday, when activity is lowest. Before it begins, the information technology department prints or saves downtime reports for every unit: a current patient census, active medication administration records for the next 12 hours, active orders, allergies, and recent results. Units are notified at 72 hours, 24 hours, and 1 hour before. A read-only copy of the record is available on dedicated computers during most planned downtimes. Unplanned downtime occurs without warning, because of hardware failure, network problems, power loss, or a cyberattack. Its length is unknown. The plan cannot rely on reports printed just before the outage, so a downtime computer on each unit, connected to a separate power source and printer, automatically receives updated census, medication, and order reports every hour. When an unplanned outage begins, the charge nurse prints the latest reports from this computer. If a cyberattack is suspected, the information technology department may also shut down the read-only copy and the downtime computers, so the plan must work with paper alone. Separating planned from unplanned downtime prevents a plan designed for scheduled maintenance from failing in an emergency.
Forms Held Where They Will Be Needed
Paper forms are useful only if they are available when the system fails. Each unit has a sealed downtime kit stored at the nurses' station, containing paper forms for physician orders, medication administration, nursing assessments, vital signs, intake and output, laboratory and imaging requisitions, and progress notes, enough for 24 hours for a full unit. The emergency department and operating rooms have kits tailored to their work, including registration forms and procedure records. The pharmacy, laboratory, and radiology have their own kits for receiving and reporting on paper. The health information management department checks every kit quarterly for completeness and replaces outdated forms.
Patients Identified Without the System
Registration normally creates a medical record number through the electronic system. During unplanned downtime, the emergency department and admitting office use pre-assigned downtime numbers, printed on sets of labels and wristbands kept in the downtime kits. Each downtime number is unique and is logged on a paper registration sheet with the patient's name, date of birth, and arrival time. After recovery, each downtime number is linked to the patient's existing medical record number, or a new one is created, and all documents are merged. Two identifiers, name and date of birth, continue to be required for every medication and procedure, as during normal operation.
Communication During Downtime
When an unplanned outage lasts more than 15 minutes, the house supervisor activates the downtime procedure, and the command center notifies all units by overhead page and text. Critical laboratory results are called to units by phone and written on a paper log. Pharmacy verifies orders from faxed or hand-carried order sheets. Updates on expected recovery time are sent every hour.
Recovery Sequenced by Role
When the system returns, back-entry of information recorded on paper must be sequenced by role, because some information must be entered before other work can proceed. First, the admitting office and emergency registration enter all patients registered with downtime numbers and link them to medical record numbers. No other entry can be attached to a patient until this is done. Second, pharmacists enter active medication orders so that the medication administration record is correct for the next doses. Third, nurses enter medication administrations given during downtime, with the actual times, so that the record shows what was given and duplicate doses are prevented. Fourth, laboratory and radiology staff enter results. Fifth, clinicians enter or scan remaining documentation, such as progress notes and assessments. Paper documents are then scanned into the record under the correct encounter and marked as downtime documentation.
A Check That Proves Nothing Was Missed
The final step is reconciliation, which proves that every action taken during downtime is in the record. For each unit, a nurse and a health information analyst compare the paper downtime logs, medication administration forms, and requisitions with the record. Every paper medication administration must match an entry in the record; every paper order must match an entry or a documented reason it was not entered; every downtime registration must be linked to a medical record number. Discrepancies are resolved and documented. The unit manager signs a reconciliation sheet, and the health information department keeps it with the downtime log. Reconciliation turns recovery from a belief that entries were made into a record showing that they were.
Roles During Downtime
Clear roles prevent confusion when the system fails. The house supervisor decides when to activate and end downtime procedures. The charge nurse on each unit prints reports, opens the downtime kit, and assigns a nurse to maintain the unit's paper medication log. The information technology on-call manager communicates the cause and expected duration. The health information management supervisor coordinates scanning and reconciliation after recovery. Each role has a one-page action card in the downtime kit, so that staff who have never experienced a long outage can follow the steps.
Testing the Plan
The plan is tested twice a year through an unannounced drill on one unit, in which staff work on paper for two hours while the record remains available to information technology staff for comparison. Drill results, including gaps in kits and delays in back-entry, are reviewed by the health information and nursing informatics committees.
Conclusion
Cedar Point's downtime plan separates planned from unplanned outages, keeps forms and patient identifiers where they are needed, sequences recovery by role, and ends with a reconciliation that proves every action taken on paper has been recorded.
References
Office of the National Coordinator for Health Information Technology. (2016). SAFER guides: Contingency planning. U.S. Department of Health and Human Services.
Sittig, D. F., & Singh, H. (2012). Electronic health records and national patient-safety goals. New England Journal of Medicine, 367(19), 1854-1860. https://doi.org/10.1056/nejmsb1205420
Reading the HIM-FPX3640 Assessment 2 instructions
The instructions ask you to create a downtime procedure plan for an electronic health record system. You define planned and unplanned downtime, describe preparation such as printed forms and read-only backup reports, explain how patients are identified and care is documented during an outage, set communication steps, sequence recovery and back-entry, and describe how the organization will confirm that all downtime documentation reached the record. Health information management has a central role in reconciliation. The ONC SAFER Guides on contingency planning and AHIMA guidance support the plan. The plan should be practical for staff working at three in the morning.
Inside the HIM FPX 3640 Assessment 2 example
The example is organized by the phases of an outage. It opens with scope, the systems covered and the definitions separating planned from unplanned and short from extended. The preparation section covers what exists before anything fails: printed packets held in the department, the read-only downtime copy, contact lists, and the schedule for testing all three. The response section runs from declaration through the first hour into sustained operation, and it is written by role, since registration, clinical staff and health information each do different things. The recovery section sequences reconciliation: what is entered, in what order, by whom, and what is scanned as an image instead. A completeness check follows. The plan closes with drills, review, and a review point after every real outage.
Reading the HIM FPX 3640 Assessment 2 scoring guide
The scoring guide rates the definitions, the preparation, the downtime procedures, the communication, the recovery and the reconciliation. Definitions reach Distinguished when planned and unplanned outages, and short and extended ones, are separated. Preparation scores higher when forms and backup reports are placed where staff will need them. Patient identification earns credit when a method works without the system, such as downtime medical record numbers. Recovery should be sequenced by role. The reconciliation criterion rewards a check that proves nothing was missed, such as matching a downtime log to scanned documents. Roles and training complete the plan, including drills so staff practice before a real outage.
HIM FPX 3640 Assessment 2 help: mistakes that cost marks
Students often write a plan that assumes the outage will be short and planned. Another common mistake is keeping forms in the HIM office, where no one can reach them on a night shift. Patient identification without the system is overlooked, which risks duplicate records. Communication is a single email that cannot be sent when systems are down. Recovery is described as entering the paper later without saying who does it and in what order. Reconciliation is missing, so documents are lost. A downtime log and a simple checklist for each unit are the most useful tools in the plan, and a drill twice a year keeps them in use.
Get a HIM FPX 3640 Assessment 2 example written to your instructions
Send the Assessment 2 instructions and the scoring guide from your HIM FPX 3640 courseroom, plus the setting and systems your plan has to cover. We write a custom example against those criteria, with response and recovery both worked through by role, and return it in 24 to 48 hours. The first custom sample is free. The paper above is an original model document written by our desk, not a submitted student paper and not an official Capella University document.
More HIM FPX 3640 papers and BS in Health Information Management samples
- HIM FPX 3640 Assessment 1: Documentation Integrity Audit
- HIM FPX 3640 Assessment 3: EHR Optimization Proposal
- HIM FPX 4630 Assessment 2: Data Presentation Report
- HIM FPX 3620 Assessment 2: Retention and Release Policy
- HIM FPX 4650 Assessment 2: Reporting and Dashboard Proposal
- HIM FPX 2670 Assessment 2: System Selection Analysis
HIM FPX 3640 Assessment 2 questions, answered
How long an outage should the plan assume?
Cover more than one duration. A short interruption is handled by waiting; an outage of several hours changes documentation and identification; an extended one exhausts the read-only copy and the paper packets. Saying which procedures apply at which duration shows the plan was thought through rather than written for a single imagined scenario.
What belongs in a downtime form packet?
The forms capturing what the system would have captured: registration and face sheet information, orders, medication administration, progress notes, vital signs and any consent the encounter requires. Add the downtime identification log and the reconciliation checklist. Name where the packet is stored and who checks that it is current, since an out-of-date packet fails the same way a missing one does.
Who declares downtime and recovery?
The plan has to name a position rather than leave it open. Usually an information technology authority declares the outage and a defined clinical or administrative leader confirms the move to downtime procedures, with recovery declared only after verification. Stating both the declaration and the notification path prevents half the organization working on paper while the other half waits.
Where can I find a free HIM FPX 3640 Assessment 2 sample paper?
This page holds the full EHR downtime plan, with planned and unplanned outages, forms at the point of care, patient identification, recovery by role and reconciliation. A model plan is available free.
Why does HIM lead reconciliation in HIM FPX 3640 Assessment 2?
Because health information management owns the completeness of the legal health record, it confirms that every paper document created during downtime was scanned or entered and matched to the right patient.