Oracle Health (Cerner) Outage History: A Timeline of EHR Downtime Incidents and What They Mean for Your Organization
When your EHR goes down, clinical operations stop. From the CrowdStrike outage that forced 759 hospitals to paper charting, to Oracle engineers accidentally deleting critical hospital databases, the pattern is clear: EHR downtime is not a theoretical risk. This timeline tracks the major incidents, documents the operational fallout, and outlines what behavioral health organizations should demand from their vendors.
Key Incidents at a Glance
- 1759 hospitals affected by the CrowdStrike global outage (July 2024) — staff reverted to paper charting across EHR platforms
- 25-day Oracle Health outage (April 2025) — engineers accidentally deleted critical storage, downing 39-45 CHS hospitals
- 3VA EHR failures ongoing — disappearing notes, incorrect dosages, and widespread access loss reported through March 2025
- 4Island Health disruption (March 2025) — computer outage impacted hospital operations across the Canadian health authority
Why EHR outages matter
EHR downtime is not an IT inconvenience — it is a patient safety event. When clinicians lose access to electronic health records, they lose access to medication histories, allergy alerts, lab results, and treatment plans. The consequences cascade: paper charting introduces transcription errors, medication reconciliation becomes manual and error-prone, and diagnostic workflows slow to a fraction of their normal pace.
The incidents documented in this timeline span different root causes — accidental data deletion, third-party software failures, systemic implementation problems — but they share a common outcome: hospitals and health systems forced into degraded operations with direct risk to patient care.
Important context: This article focuses on documented incidents involving Oracle Health (Cerner) and related healthcare IT infrastructure. These events are not unique to any single vendor — EHR downtime is an industry-wide risk. The purpose of this timeline is to help healthcare organizations (including behavioral health providers) make informed decisions about vendor reliability and disaster preparedness.
Cybersecurity for the Clinician — Health Sector Coordinating Council
Visual timeline of major incidents
Healthcare EHR Outage Timeline (2020-2025)
VA begins Oracle Health (Cerner) EHR modernization at initial sites. Early reports of system instability, disappearing patient notes, and data anomalies emerge almost immediately.
Persistent reports of prescription dosage errors, clinician workflow disruptions, and system performance problems across VA sites running the new EHR. Multiple congressional hearings address the program's challenges.
759 US hospitals affected. Faulty CrowdStrike cybersecurity software update caused widespread IT failures. Hospitals running Epic, Cerner, and other EHR platforms were forced to revert to paper charting. Elective procedures canceled. Emergency departments operated on manual protocols.
Reports of widespread VA EHR access loss ahead of planned 2026 rollout expansion. Separately, Island Health (Canada) experienced a computer outage disrupting hospital operations across the health authority.
39-45 CHS hospitals down for 5 days. Oracle engineers conducting data center maintenance accidentally deleted critical storage connected to a key database. Hospitals activated downtime procedures and returned to paper-based records for nearly a week.
Oracle Health 5-day outage (April 2025)
On or around April 23, 2025, Oracle engineers conducting routine data center maintenance accidentally deleted critical storage connected to a key database supporting Community Health Systems (CHS) hospitals. The error caused a cascading failure that took down EHR access at between 39 and 45 hospitals — CHS itself reported 39 affected facilities, while external reporting placed the number at 45.
The outage lasted approximately five days, with hospitals not fully recovering until around April 28, 2025. During that period:
- Hospitals activated formal "downtime procedures" — standardized protocols for operating without electronic systems
- Clinical staff reverted to paper-based charting for all patient encounters
- Medication administration, lab ordering, and diagnostic workflows were conducted manually
- Upon system restoration, hospitals faced the additional burden of back-entering days of paper records into the EHR
The root cause — accidental deletion during maintenance — raises fundamental questions about Oracle's operational safeguards, change management processes, and data redundancy architecture. A single maintenance error should not be capable of producing a multi-day, multi-facility outage.
Oracle Health April 2025 Outage: By the Numbers
5
Days of downtime
39-45
CHS hospitals affected
1
Root cause: accidental deletion
Sources: CNBC (April 28, 2025), Fierce Healthcare
CrowdStrike global outage (July 2024)
On July 19, 2024, a faulty cybersecurity software update from CrowdStrike triggered one of the largest IT outages in recent history. The update caused widespread system crashes across organizations running CrowdStrike's Falcon endpoint protection, and healthcare was among the hardest-hit sectors.
Approximately 759 US hospitals were affected. Hospitals relying on major EHR platforms — including Epic and Cerner — lost access to electronic records and were forced to:
- Revert to paper charting across departments
- Cancel elective surgeries and procedures due to inability to verify patient histories and medication records
- Operate emergency departments on manual triage and documentation protocols
- Delay non-emergency diagnostic testing that required electronic ordering
While this was not an Oracle Health-specific failure, it exposed a critical vulnerability in healthcare IT: dependency on third-party infrastructure. Hospitals whose EHR access was mediated through systems running CrowdStrike experienced the same downtime regardless of which EHR vendor they used. This incident highlights that EHR reliability is not just about the EHR vendor — it encompasses the entire technology stack.
VA EHR modernization failures (2020-2025)
The Department of Veterans Affairs' Oracle Health (Cerner) EHR modernization program represents one of the most troubled large-scale EHR implementations in US history. Since the initial rollout began in 2020, the system has been plagued by persistent operational issues:
- Disappearing patient notes: Clinicians reported that clinical documentation would intermittently vanish from the system, creating gaps in the medical record
- Incorrect prescription dosages: The system displayed medication dosage information incorrectly in some instances, creating direct patient safety risks
- Data anomalies: Unexplained data inconsistencies raised clinician concerns about the integrity of the health record
- Widespread access loss: As recently as March 2025, reports surfaced of widespread EHR access failures across VA facilities
These are not minor usability complaints — they are systemic reliability and data integrity failures at a system serving millions of veterans. The VA's experience serves as a cautionary example for any organization evaluating Oracle Health (or any vendor) for a large-scale deployment: implementation quality and ongoing operational reliability matter as much as the software itself.
Island Health outage (March 2025)
In March 2025, Island Health — a regional health authority in British Columbia, Canada — experienced a computer outage that disrupted hospital operations across its facilities. While details on the specific EHR platform and root cause are more limited than the US incidents documented above, the event reinforces a global pattern: healthcare IT infrastructure remains fragile, and outage events are not confined to any single vendor or geography.
Downtime impact calculator
What does EHR downtime actually mean for a hospital's operations? While precise financial figures vary by facility size and geography, the operational impact of even a single day of EHR downtime is severe and well-documented. Here is what a 200-bed hospital can expect:
EHR Downtime Operational Impact: 200-Bed Hospital
Estimated effects per day of complete EHR unavailability
Paper charting across all departments
Every clinical encounter documented by hand. Nursing assessments, physician orders, medication administration records, and progress notes all revert to paper. Upon system restoration, every paper record must be manually back-entered — often taking longer than the original downtime.
Elevated medication error risk
Without electronic medication reconciliation, allergy alerts, drug interaction checks, and barcode scanning, the risk of medication errors increases significantly. Nurses must manually verify every dose against paper MAR records.
Delayed diagnoses and treatment decisions
Lab results, imaging reports, and historical clinical data become inaccessible. Physicians may delay non-urgent treatment decisions or order redundant tests because prior results cannot be retrieved. Critical results may not reach the ordering provider through normal electronic channels.
Staff overtime and operational strain
Clinical and administrative staff work extended hours managing manual workarounds. Additional personnel may be called in to handle paper-based processes. After restoration, data back-entry requires dedicated staff time that compounds the original downtime impact.
Canceled elective procedures and diverted admissions
Without access to patient histories, pre-operative records, and electronic ordering, many facilities cancel non-emergency procedures. Some hospitals divert incoming ambulances to other facilities during extended outages, reducing volume and revenue.
Multiply by 5 days for the Oracle Health April 2025 scenario. For the 39-45 CHS hospitals affected, every operational impact listed above persisted for nearly a full business week — with the additional recovery burden of back-entering five days of paper documentation into the restored EHR.
What this means for behavioral health
Most behavioral health organizations are not running hospital-scale Oracle Health deployments. But the incidents documented in this timeline carry direct lessons for any organization that depends on an EHR for clinical operations:
- Vendor reliability patterns are predictive. An EHR vendor's track record of outages, incident response, and transparency is the strongest indicator of future reliability. Organizations should research vendor outage history before signing contracts.
- Third-party dependencies create hidden risk. The CrowdStrike incident demonstrated that your EHR's uptime depends on the entire technology stack — not just the EHR vendor. Ask vendors about their infrastructure dependencies and how they manage third-party risk.
- Data integrity is as important as uptime. The VA's experience shows that an EHR can be "up" while still producing incorrect or incomplete data. Uptime SLAs alone are insufficient — behavioral health organizations should also evaluate data validation processes and clinical safety monitoring.
- Downtime procedures need rehearsal. Every organization, regardless of size, should have documented downtime procedures and should practice them regularly. A 50-clinician behavioral health practice that loses EHR access faces many of the same operational challenges as a hospital — just at a different scale.
Vendor reliability evaluation framework
Based on the patterns observed across these incidents, behavioral health organizations should evaluate EHR vendors on four key reliability dimensions:
| Dimension | What to ask | Minimum standard | Red flag |
|---|---|---|---|
| Uptime SLAs | What is the contractual uptime guarantee? What are the penalties for missing it? | 99.9% uptime with financial remedies | No published SLA or "best effort" language |
| Redundancy architecture | How is data replicated? Is there multi-region failover? What is the disaster recovery architecture? | Multi-region/multi-AZ with automated failover | Single data center, manual failover, or "we've never needed it" |
| Incident transparency | Is there a public status page? Are post-incident reports published? How are customers notified during outages? | Real-time status page + post-incident reports within 72 hours | No status page, no post-incident communication, or delayed acknowledgment |
| Recovery commitments | What are the defined RTO (Recovery Time Objective) and RPO (Recovery Point Objective)? | RTO under 4 hours, RPO under 1 hour for critical systems | No defined RTO/RPO, or targets exceeding 24 hours |
For behavioral health organizations evaluating EHR vendors, reliability should carry the same weight as clinical features and pricing in your selection criteria. A system with excellent documentation templates and a poor uptime record is a liability, not an asset.
If you are currently evaluating behavioral health EHR platforms, our vendor selection resources include detailed reviews of platforms purpose-built for behavioral health — including analysis of vendor infrastructure, support responsiveness, and reliability track records.
Frequently asked questions
What caused the Oracle Health outage in April 2025?
Oracle engineers conducting routine data center maintenance accidentally deleted critical storage connected to a key database. This caused a 5-day outage affecting 39-45 Community Health Systems (CHS) hospitals from approximately April 23 to April 28, 2025. Hospitals were forced to activate downtime procedures and revert to paper-based records.
How many hospitals were affected by the CrowdStrike outage in July 2024?
The CrowdStrike global IT outage on July 19, 2024 affected approximately 759 US hospitals. A faulty cybersecurity software update caused widespread system failures, forcing hospitals relying on major EHR systems including Epic and Cerner to revert to paper charting.
What happened with the VA EHR modernization outages?
The VA's Oracle Health (Cerner) EHR modernization program has experienced persistent system outages and data integrity issues since its initial rollout in 2020. Reported problems include disappearing patient notes, incorrect prescription dosages, data anomalies, and widespread EHR access loss as recently as March 2025.
How should behavioral health organizations evaluate EHR vendor reliability?
Behavioral health organizations should evaluate EHR vendors on four key reliability dimensions: contractual uptime SLAs (99.9% or higher), redundancy architecture (multi-region failover), incident response transparency (public status pages and post-incident reports), and recovery time commitments (defined RTO and RPO targets).
Editorial Standards
Last reviewed:
Methodology
- Reviewed published reporting from CNBC, Fierce Healthcare, Healthcare IT News, and Nurse.org on specific EHR outage incidents.
- Cross-referenced hospital counts and outage durations across multiple independent sources.
- Documented only incidents with published, verifiable reporting — no unconfirmed claims.
- Focused on operational impact rather than speculative financial estimates.