HCIS 352 Week 3 Healthcare Information System Maintenance Example

Upgrading the EHR Without Stopping Care: A Maintenance Plan for Patches, Version Upgrades and Planned Downtime in a Two-Hospital System

[Student Name]

University of Phoenix

HCIS/352: Foundations of it in the Health Care Environment

Week 3 Assignment

[Instructor Name]

[Date]

The health system, its schedule and its figures are composites written for a model paper; research findings and guidance come from the sources listed.

A two-hospital health system with 520 beds runs its EHR around the clock. Nurses give medications at 3 a.m., the emergency department never closes and laboratory results post every few minutes. Yet the system must be maintained: security patches arrive monthly, the vendor releases updates quarterly and, once every year or two, a major version upgrade requires the EHR to go offline. This paper plans maintenance that keeps the system current without stopping care.

Three Kinds of Maintenance

Routine patches for servers and workstations are applied monthly using rolling methods that keep the EHR available, updating one server in a cluster at a time. Quarterly vendor updates, which change features or fix defects, are applied in a two-hour window between 1 a.m. and 3 a.m., during which the EHR runs in a read-only mode. The major upgrade, planned for this spring, changes the database structure and requires about four hours with the EHR fully offline.

Change Management and Testing

Every change goes through the change advisory board, which reviews the risk, the test results, the back-out plan if the change fails and the schedule. The health system keeps separate test and training environments that mirror the live system. For the major upgrade, analysts will test for six weeks: every order set, interface, report and device connection, with clinical superusers running real workflows. A dress rehearsal on a copy of live data will time each technical step.

Why Downtime Needs Clinical Planning

Downtime is a clinical event. Larsen et al. (2018) analyzed patient safety event reports from a large database and identified 76 reports explicitly tied to EHR downtime. The reports involved laboratory, medication, imaging and registration processes, patient handoffs, documentation, access to patient history and delayed procedures, and they examined whether downtime procedures were in place and followed. The lesson for planners is that the riskiest part of an upgrade is not the software installation but the hours when clinicians must work without the tools they rely on, so the plan must be written for them.

Federal Guidance for Contingency Planning

Federal health IT officials publish the SAFER Guides, self-assessments that help organizations evaluate the safety of their EHR use; one focuses on contingency planning and recommends measures such as read-only backup access to key patient information, downtime procedures and forms, practice drills and communication plans (Office of the National Coordinator for Health Information Technology, 2016). The health system scored itself against the guide and closed two gaps before scheduling the upgrade.

Communication

Staff will hear about the upgrade six weeks ahead through managers, three weeks ahead by email and posted notices, the week before in huddles and the night of the event by overhead page and badge phone. Each unit will receive a one-page checklist. Physicians' offices and outside laboratories will be told that results may be delayed.

The Night of the Upgrade

The upgrade begins at midnight on a Sunday, the lowest-census night. A command center staffed by IT, the vendor, nursing leadership, pharmacy, laboratory and a physician lead opens at 11 p.m. Thirty minutes before shutdown, each unit prints a downtime report of current patients, medications due in the next eight hours and recent results. The system then goes offline.

Working on Paper

During the four hours, nurses document medication administration on paper records printed from the downtime report. New orders are written on paper and walked or tubed to pharmacy, laboratory and imaging. The laboratory phones critical results and delivers printed results by runner. Registration uses paper forms and assigns numbers from a pre-allocated block. A downtime coordinator on each unit collects paper for later entry.

Other Systems During the Outage

The EHR is not the only system affected. The laboratory information system keeps running and holds results until the interface returns. The pharmacy system can verify orders entered directly by pharmacists. The image archive stays available, so radiologists can read studies and phone results. Bed management switches to a whiteboard in the house supervisor's office. Each departmental system owner confirms, during the dress rehearsal, exactly which functions work without the EHR and which do not, so no unit discovers a gap at 1 a.m.

A Back-Out Plan

If the upgrade fails partway, the team must be able to return to the old version. The back-out plan sets a decision point at the two-hour mark: if key tests have not passed, the command center restores the previous version from the backup taken at shutdown, extending downtime by about two hours rather than risking an unstable system. The vendor and the chief information officer jointly make the call.

Recovery and Back-Entry

When the upgraded system returns, technical staff verify interfaces and run test transactions before clinicians log in. Units then enter orders, medication administrations and results from the downtime period in a set order, with pharmacy reviewing all medication entries. Registration merges any temporary records.

Review Afterward

Within a week, the command center team reviews what worked and what did not, including safety reports filed during the event, and updates the downtime procedures.

Routine Maintenance Lessons

The same principles apply at smaller scale: test every change, tell people before it happens, protect access to critical information and review problems afterward. Maintenance also carries costs that belong in any honest account of electronic systems, including staff time, vendor fees and the disruption of each change (Menachemi & Collum, 2011).

Measures

Measures include unplanned downtime hours per quarter, the share of changes that required a back-out, the number of safety reports linked to downtime, the time to complete back-entry after planned events and staff ratings of downtime readiness from drills.

Conclusion

Maintaining health care information systems means keeping them current without stopping care. Separate approaches for patches, updates and major upgrades, strict change control and testing, federal contingency guidance, careful communication and detailed clinical downtime procedures let a two-hospital system upgrade its EHR while patients continue to receive care safely.

References

Larsen, E., Fong, A., Wernz, C., & Ratwani, R. M. (2018). Implications of electronic health record downtime: An analysis of patient safety event reports. Journal of the American Medical Informatics Association, 25(2), 187-191. https://doi.org/10.1093/jamia/ocx057

Menachemi, N., & Collum, T. H. (2011). Benefits and drawbacks of electronic health record systems. Risk Management and Healthcare Policy, 4, 47-55. https://doi.org/10.2147/RMHP.S12985

Office of the National Coordinator for Health Information Technology. (2016). SAFER guides: Contingency planning. HealthIT.gov. https://www.healthit.gov/topic/safety/safer-guides