The 'Unknown Queue' Black Hole: Documenting Thousands of Prescriptions Vanishing from Workflow Views in 2024
The ‘Unknown Queue’ Phenomenon: A Persistent Digital Limbo
In 2024, the defining failure of the Oracle Cerner Electronic Health Record (EHR) rollout remained the “Unknown Queue,” a catastrophic software defect where clinically valid prescriptions from workflow views, leaving pharmacists unaware that orders existed. While Oracle Health executives testified that the specific coding error identified in 2022 had been patched, federal oversight reports from March and September 2024 confirm that the phenomenon of orders mutated into new forms of data transmission failures. These failures created a “black hole” effect that continued to jeopardize patient safety at the Captain James A. Lovell Federal Health Care Center (Lovell FHCC) and legacy sites. The method of this failure in 2024 was not a single folder labeled “Unknown,” a widespread breakdown in interoperability between the new Oracle Millennium platform and the legacy VistA system. When a provider at a new EHR site entered a prescription, the complex routing logic required to transmit that data to the Health Data Repository (HDR) frequently failed. Instead of triggering a “failed transmission” alert to the clinician, the order frequently sat in a digital limbo, technically recorded in the database invisible to the pharmacists responsible for filling it.
250, 000 Veterans at Risk: The 2024 Transmission Defect
In February 2024, just weeks before the serious Lovell FHCC go-live, the VA Office of Inspector General (OIG) exposed a massive persistence of this data blindness. Deputy Inspector General David Case testified that approximately 250, 000 veterans were at risk of receiving contraindicated medications because the Oracle system failed to accurately transmit medication and allergy data to legacy sites. This transmission failure meant that a veteran could receive a prescription at a modernized site (like Spokane or Columbus), that order would before reaching the safety check systems used by other VA facilities. If that veteran later visited a legacy site, the pharmacists there would have no visibility of the active prescription, rendering drug-interaction checks useless. The OIG explicitly stated that Oracle and the VA “did not test for medication and allergy data accuracy” after transmission, allowing these errors to propagate throughout 2024.
The Mechanics of Disappearance
The technical root of these orders lies in the translation between Oracle’s commercial code and the VA’s customized infrastructure.
- VUID Mismatches: The VA uses specific Veterans Health Administration Unique ID (VUID) codes for medications. The Oracle system frequently failed to map these codes correctly to the legacy standard, causing the order to “drop” from the visible queue at the destination pharmacy.
- Silent Failures: Unlike standard software that throws an error message when a transaction fails, the Oracle Cerner system frequently treated these dropped packets as successful transmissions. This silence forced pharmacists to rely on manual audits rather than system alerts.
- Mail Order Gaps: The OIG found that mail-order pharmacy data for nearly 120, 000 patients was outdated or contained errors, meaning prescriptions routed to the Consolidated Mail Outpatient Pharmacy (CMOP) were lost to the safety checking process.
Lovell FHCC: The “Success” Built on Manual Labor
The March 2024 rollout at Lovell FHCC in North Chicago was marketed as a proof-of-concept for the “reset” EHR program. Yet, operational data reveals that the system’s stability was a mirage maintained by human middleware. To prevent the “Unknown Queue” and similar routing failures from impacting patient care, the VA surged the facility with approximately 100 additional staff members and 800 expert users. These extra hands were not there to enhance care; they were there to manually the gaps in the software. Pharmacists at Lovell reported needing to enter prescription data twice, once in the Oracle system and once in the legacy framework, to ensure orders did not. This “swivel-chair” workflow turned highly trained clinical pharmacists into data entry clerks, tasked with manually verifying that the software had not eaten the prescriptions.
| Metric | Statistic | Operational Impact |
|---|---|---|
| Veterans at Risk | ~250, 000 | Patients with medication/allergy data transmission errors affecting safety checks (OIG Feb 2024). |
| Major Performance Incidents | 826 | Total outages or incomplete functionality events recorded from Oct 2020 through March 2024. |
| Mail Order Data Errors | 120, 000 | Patients with incorrect or outdated mail-order records due to interface failures. |
| Mitigation Staffing | +100 FTE | Additional staff required at Lovell FHCC to manually bypass system defects during rollout. |
The “Hypervigilance” Standard
The psychological toll of these system failures on pharmacy staff has been documented as “hypervigilance.” Because the system could not be trusted to maintain a reliable queue of orders, pharmacists in 2024 were forced to constantly audit the database for “ghost” orders. A survey of staff at the five live sites indicated that this state of constant alert was the only barrier preventing widespread patient harm. The “Unknown Queue” is no longer just a software bug; it has become an operational condition. By late 2024, the VA had not yet implemented a detailed automated solution to guarantee that every order entered by a provider appears on a pharmacist’s screen. Instead, the safety of the pharmacy workflow relies entirely on the manual verification processes instituted to catch what the Oracle system drops.
“The responsibility to protect patients from harm rests on legacy site providers’ ability to accurately perform a series of manual, complex, time-consuming, and unmonitored mitigations of which they may or may not be aware.”
, VA Office of Inspector General, Healthcare Inspection Report (March 2024)
The 20 Percent Efficiency Tax: Verified Staffing Surges Required to Process Identical Prescription Volumes at Pilot Sites
The Columbus Anomaly: A 62 Percent Surge
While the 20 percent figure serves as the baseline “tax” for adopting the new EHR, specific facilities experienced far more severe degradation. At the VA Central Ohio Healthcare System in Columbus, the Office of Inspector General (OIG) reported that the facility required a 62 percent permanent increase in clinical pharmacists. This surge was not temporary support for a go-live event. It was a structural requirement to prevent the collapse of medication distribution. The OIG testimony in February 2024 revealed that without this additional headcount, the “click-heavy” nature of the Oracle interface caused immediate prescription backlogs. Pharmacists at legacy sites could process orders in seconds using VistA’s keyboard-based shortcuts; at Columbus, the mouse-driven Oracle workflows required navigating multiple fragmented screens, tripling the time required to fill a single script.
Lovell FHCC: The “Optimized” Failure
The deployment at the Captain James A. Lovell Federal Health Care Center (Lovell FHCC) in North Chicago on March 9, 2024, was marketed as the “Reset” standard, a version of the software where serious defects were supposedly resolved. Yet, even this “optimized” site incurred an efficiency tax. Testimony from September 2024 confirmed that Lovell FHCC is on track for a 7 percent staffing increase specifically to mitigate EHR impacts. While lower than the 20 percent average at Spokane or the 62 percent spike in Columbus, this increase contradicts the fundamental pledge of modernization: that technology should reduce, not increase, the labor hours required for administrative tasks. The “success” at Lovell relied on a pre-emptive surge of runners, pharmacy technicians, and floor support to manually the gaps in digital interoperability.
The Mechanics of: The “Swivel Chair” Workflow
The primary driver of this staffing balloon is the failure of the “Medication Manager Retail” module. In 2024, pharmacists were still forced to perform “swivel chair” data entry, manually typing prescription details into the core Oracle EHR and then re-typing the same data into a separate retail pharmacy application to print labels and dispense drugs. Oracle executives promised a fix for this dual-entry requirement in April 2023. By September 2024, the solution remained unstable, forcing highly paid clinical pharmacists to act as data entry clerks. This redundancy introduces a high risk of transcription errors, requiring even more staff to perform second-check verifications.
| Facility | System Status | Verified Staffing Increase | Primary Cause |
|---|---|---|---|
| Mann-Grandstaff VAMC | Pilot Site (2020) | +20% | Manual workarounds, “Unknown Queue” monitoring |
| VA Central Ohio (Columbus) | Wave 2 (2022) | +62% (Clinical Pharmacists) | Prescription backlog management, UI complexity |
| Lovell FHCC | “Reset” Site (2024) | +7% | Mitigation of remaining EHR defects |
| System-Wide Projection | Estimate | +20% to +60% | Permanent productivity loss vs. VistA |
The Multi-Billion Dollar Payroll Bomb
The financial of this efficiency tax are. Representative Matt Rosendale estimated that if the Oracle Cerner system were deployed across the entire VA enterprise with these staffing ratios, it would require between $3. 5 billion and $10 billion al payroll costs annually. This expenditure does not purchase better care or faster service; it strictly funds the human labor required to wrestle with an inefficient user interface. These costs are absent from the original $16 billion contract estimate. The Institute for Defense Analyses (IDA) warned in 2022 that total lifecycle costs could exceed $50 billion, a figure that appears conservative given the verified need for 1. 2 to 1. 6 pharmacists to do the work of one VistA-era pharmacist.
“They have had to increase their pharmacy staffing by at least 20% to navigate all the bugs and workarounds, just to process roughly the same volume of prescriptions.”
, Rep. Matt Rosendale, Chairman of the House Veterans’ Affairs Subcommittee on Technology Modernization (February 15, 2024)
Safety as a Function of Headcount
The staffing surge is not an economic problem; it is a safety method. In 2024, approximately 20 percent of all patient safety reports filed at Oracle Cerner sites were pharmacy-related. The additional staff members are frequently tasked with “hypervigilance”—manually monitoring queues that the software should manage automatically. When staffing levels dip due to turnover or budget constraints, the safety net fails, and orders into the digital void. The system functions only when oversaturated with human supervisors.
OIG Report 23-01450-114 Analysis: The Persistence of Critical Priority 1 Medication Management Failures
The VUID Transmission Failure
The core of the report details a catastrophic interoperability defect where the Oracle system transmitted incorrect VUIDs to the Health Data Repository (HDR). Because the VUID serves as the digital “fingerprint” for every specific medication, this mismatch blinded the automated safety nets at legacy sites. * method of Failure: The Oracle software assigned random or incorrect VUIDs to valid prescriptions during transmission. * Operational Blindness: Legacy VistA systems received the prescription data could not recognize the drug identity. Consequently, the automated drug-drug interaction and drug-allergy interaction checks, standard safety in modern medicine, failed to trigger. * Scope of Exposure: The OIG identified approximately 250, 000 veterans whose medication records contained these corrupted identifiers as of September 2023. These patients were left to severe adverse drug events if they sought care at any of the 100+ legacy VA sites.
The “Silent” Priority 1 Incidents
Unlike system crashes (downtime) which trigger immediate alerts, these data integrity failures silently. The OIG investigation revealed that while Oracle Health applied a software patch to correct the coding error, they failed to scrub the corrupted data already residing in the system.
1. The “Expire-to-Fix” Strategy
In a move that stunned federal auditors, the remediation plan for the 250, 000 affected records was passive. VA and Oracle officials decided to let the corrupted prescription data remain in the system until the orders naturally expired. * Duration of Risk: This decision meant that incorrect data transmitted as far back as 2020 remained active and dangerous until April 2024. * load on Pharmacists: To mitigate the risk, the Veterans Health Administration (VHA) ordered pharmacists at legacy sites to perform manual safety checks for every patient with a history of care at an Oracle site. This required pharmacists to visually inspect medication lists and manually cross-reference interactions, a process prone to human error and by the OIG as “unsustainable.”
2. The Allergy Data Gap
The VUID corruption extended beyond active prescriptions to allergy records. If a patient developed a life-threatening allergy (e. g., to penicillin) at an Oracle Cerner site, the transmission error could prevent that allergy warning from appearing correctly at a legacy site. A physician at a legacy hospital could unknowingly prescribe the allergen, as the automated “STOP” warning would never appear.
Quantifiable Impact of Pharmacy Failures (2024)
The following data points from OIG Report 23-01450-114 and subsequent testimony illustrate the of the medication management emergency.
| Metric | Data Point | Operational Consequence |
|---|---|---|
| Affected Population | 250, 000 Veterans | Patients at risk of receiving contraindicated medications due to failed safety checks. |
| Corrupted Data Duration | ~4 Years | Incorrect identifiers from 2020 through April 2024. |
| Pharmacy Staffing Increase | +20% to +60% | Sites required massive staffing surges to handle manual workarounds and safety verifications. |
| Mail Order Impact | 120, 000 Patients | Consolidated Mail Outpatient Pharmacy (CMOP) data was outdated or contained errors, risking fulfillment delays. |
widespread Definition Failures
The persistence of these errors was exacerbated by a contractual dispute over what constitutes a “Priority 1” incident. The OIG found that the VA’s definition of a serious incident was significantly narrower than Oracle’s internal standards. * VA Definition: frequently limited to total system outages or “serious” safety threats that were immediately visible. * Oracle Definition: Broader, the gap allowed “high severity” data integrity problem—like the VUID mismatch—to escape the most urgent escalation until the OIG intervened. This misalignment meant that while the system appeared “up” (green status on a dashboard), the clinical data flowing through it was toxic. The report concluded that the “responsibility to protect patients from harm rests on legacy site providers’ ability to accurately perform a series of manual, complex, time-consuming, and unmonitored mitigations.” This shifted the liability for Oracle’s software defects onto the shoulders of frontline VA pharmacists.
Legacy Data Corruption: Inaccurate Medication Histories and Allergies Migrating from VistA to Oracle Health
The “Translation” Defect: A Linguistic Failure Between Systems
In 2024, the Department of Veterans Affairs discovered that its $16 billion electronic health record modernization (EHRM) effort suffered from a foundational defect: the inability of the new Oracle Cerner system to accurately “speak” the language of the legacy VistA system. This was not a technical glitch a patient safety emergency affecting approximately 250, 000 veterans. The core of the failure lay in the migration and synchronization of data between the two systems, specifically, the translation of medication histories and allergy profiles.
The legacy VistA system, built on the MUMPS programming language, utilizes specific local drug files and “free text” entry methods that allowed providers to document complex allergy information. The Oracle Millennium platform, yet, relies on rigid, standardized data fields. When patient records were migrated or synchronized between these environments, the data did not simply transfer; it mutated. Federal oversight reports released in March and September 2024 confirmed that this “translation” failure resulted in the widespread corruption of clinical history, leaving pharmacists and providers blind to life-threatening contraindications.
The VUID Transmission Failure
The most pervasive method of this corruption involved the VA Unique Identifier (VUID). The VUID is the digital fingerprint for every medication within the VA’s formulary, used to track drugs across different facilities and systems. In 2024, the VA Office of Inspector General (OIG) revealed that Oracle Health’s software was transmitting incorrect VUIDs from new EHR sites to the central Health Data Repository (HDR).
When a veteran received care at an Oracle-enabled site (like the Mann-Grandstaff VA Medical Center) and subsequently visited a legacy VistA site, the legacy system would attempt to pull the patient’s updated medication list from the HDR. Because the VUIDs were incorrect, the VistA system failed to recognize the medications.
The clinical consequence was the total failure of automated safety checks. VistA’s drug-to-drug interaction warnings rely on accurate VUIDs to function. With the identifiers corrupted, a doctor at a legacy site could prescribe a medication that interacted fatally with a drug the patient was already taking, and the system would remain silent. The OIG estimated that by September 2024, a quarter of a million veterans were at risk of this specific data blindness.
Case Study: The Prednisone Withdrawal Incident
The theoretical risk of data corruption materialized in specific, documented harm. In one egregious case by federal investigators in early 2024, a veteran suffering from Post-Traumatic Stress Disorder (PTSD) and adrenal insufficiency was treated at an Oracle-managed facility. The provider prescribed prednisone, a serious steroid required to manage the patient’s adrenal condition.
Shortly after, the veteran was admitted to a residential rehabilitation treatment program at a facility still using the legacy VistA system. When staff at the residential facility accessed the patient’s record, the prednisone prescription did not appear. The migration failure had erased the medication from the view of the treating team.
For five days, the patient went without the necessary steroid. The error was only discovered after the veteran began exhibiting severe behavioral changes and physical symptoms consistent with adrenal emergency and steroid withdrawal. This incident underscored that the “data corruption” was not an abstract IT problem; it was a method of physical negligence that forced veterans to undergo preventable medical trauma.
The Lovell FHCC “Stress Test”: March 2024
The deployment of the Oracle EHR at the Captain James A. Lovell Federal Health Care Center (Lovell FHCC) in North Chicago on March 9, 2024, served as the test of data migration. As the only fully integrated facility sharing patients between the Department of Defense (DoD) and the VA, Lovell required the migration of massive volumes of complex historical data.
While VA leadership publicly characterized the Lovell rollout as “promising,” internal metrics painted a different picture of the data migration’s success. The system did not function autonomously; it required a massive injection of human labor to compensate for software defects. The facility had to onboard nearly 200 permanent new staff and approximately 800 temporary workers to manage the transition.
of this surge workforce was dedicated to pharmacy operations. Pharmacists at Lovell were forced to perform manual “swivel-chair” verifications, literally turning between a screen displaying the legacy VistA data and a screen displaying the Oracle interface, to ensure that prescriptions and allergies had transferred continuously. The “success” of the Lovell migration was not a result of software fidelity of brute-force human mitigation.
Allergy Data: The “Free Text” Trap
Beyond medication lists, the migration of allergy data presented a distinct and lethal hazard. For decades, VistA allowed providers to enter allergy information as “free text” notes. A doctor could type “Patient has severe throat swelling with generic amoxicillin tolerates brand name X.”
The Oracle system, designed for structured data, frequently rejected these unstructured entries during migration. Instead of flagging the data for review, the system frequently dropped the entry entirely or mapped it to a generic “Other” category that failed to trigger red-flag alerts during prescribing.
In 2024, pharmacy staff reported instances where known anaphylactic allergies documented in VistA appeared as blank fields in the Oracle EHR. This data deletion forced pharmacists to re-interview patients about their allergy history at the point of dispensing, a dangerous redundancy that relied entirely on the patient’s memory and ability to communicate, rather than the verified medical record.
Table: Data Corruption Vectors (VistA to Oracle)
| Data Element | VistA Format (Legacy) | Oracle Migration Error | Clinical Consequence |
|---|---|---|---|
| Medication ID | Correct VUID (VA Unique ID) | Transmits incorrect/null VUID to HDR | Drug-drug interaction checks fail; active meds appear “unknown.” |
| Sig Codes (Instructions) | Complex text (e. g., “Take 1 tablet by mouth twice daily”) | Truncated or garbled mapping | Instructions read “1 tablet” with no frequency, leading to overdose or underdose. |
| Allergies | Free-text narrative allowed | Data dropped or mapped to “Other” | Anaphylaxis warnings fail to trigger during order entry. |
| Prescription Status | Active / Discontinued / Expired | Status mismatch (Zombie Orders) | Discontinued meds appear active; active meds appear expired. |
The “Zombie” Prescription Phenomenon
A specific manifestation of migration failure observed in 2024 was the “Zombie Prescription.” This error occurred when the Oracle system misinterpreted the start and stop dates of medications imported from VistA. Prescriptions that had been discontinued years prior, sometimes due to adverse reactions, were resurrected in the new system as “Active.”
Conversely, current, life-sustaining medications were frequently flagged as “Expired” or “Discontinued” upon migration. This forced providers to re-enter active prescriptions manually, a process that introduced new risks of transcription error. The OIG noted that this specific defect contributed to the 60% increase in pharmacy staffing requirements at larger facilities, as technicians spent thousands of hours auditing the “active” status of every drug in a patient’s profile against the legacy record.
The “One-Way” Synchronization Trap
The data corruption was exacerbated by the “one-way” nature of fixes implemented by Oracle in 2024. While patches were applied to ensure data flowed correctly from Oracle to the HDR, these fixes frequently did not retroactively correct the data already sitting in the repository.
This meant that a patient’s record was bifurcated. A pharmacist looking at the “local” Oracle view might see one set of medications, while a pharmacist at a legacy site looking at the “remote” view of the same patient saw a different, corrupted list. This absence of a “single source of truth” violated the primary directive of the EHR modernization program.
By late 2024, the VA had not yet implemented a detailed automated solution to clean the corrupted legacy data. Instead, the load remained on frontline staff. The “mitigation strategy” officially endorsed by VA leadership involved manual vigilance, requiring overworked healthcare professionals to doubt the screen in front of them and verify data through phone calls, paper chart reviews, and patient interviews.
CMOP Disconnects: Latency and Transmission Failures in the Consolidated Mail Outpatient Pharmacy Interface
The CMOP Disconnect: Interface Latency and Data Corruption
The Department of Veterans Affairs’ Consolidated Mail Outpatient Pharmacy (CMOP) system has historically been the agency’s logistical crown jewel, routinely outperforming private sector equivalents like CVS Caremark and Express Scripts in J. D. Power customer satisfaction rankings. This automated network processes 80% of all VA prescriptions, mailing nearly 120 million prescriptions annually with near-perfect accuracy. In 2024, yet, the integration of the Oracle Cerner EHR with this legacy infrastructure created a dangerous bottleneck, characterized by data corruption, transmission latency, and a breakdown in the “bi-directional” communication required for safe dispensing.
The VUID Transmission Failure
The most severe technical failure identified in March 2024 involved the corruption of VA Unique Identifier (VUID) numbers during transmission from Oracle Cerner sites to the CMOP infrastructure. The VUID is the digital fingerprint for every medication, dictating exactly which drug, strength, and formulation the automated robots should dispense.
Federal oversight reports released in March 2024 confirmed that the Oracle Cerner system transmitted incorrect VUIDs for approximately 250, 000 veterans. This data corruption meant that when a physician at a new EHR site (like Lovell FHCC or Spokane) ordered a medication, the digital instruction sent to the mail-order facility frequently contained mismatched identifiers.
“The OIG learned that incorrect VUIDs sent from new EHR sites and stored in the Health Data Repository from as far back as October 2020 were not corrected… These patients are at ongoing risk of a medication-related patient safety event should they receive care and medications at a legacy EHR site.”
, VA Office of Inspector General, Pharmacy Safety Report (March 21, 2024)
While Oracle Health applied a software patch to prevent future errors, the corrupted data for 120, 000 patients remained in the system until the prescriptions naturally expired in April 2024. This forced pharmacists at legacy sites to manually verify safety checks that were previously automated, introducing human error into a high-volume industrial process.
Latency and the “Five-Day Void”
Beyond data corruption, the interface suffered from severe latency. In the legacy VistA environment, a prescription entered by a doctor is almost instantly visible to the pharmacy team for verification and transmission to CMOP. In the Oracle Cerner environment of 2024, data packets frequently hung in a “transmission void.”
Testimony provided to the House Veterans’ Affairs Committee in February 2024 highlighted a specific incident where a veteran at a residential treatment facility waited five days for a serious medication. The order had been entered correctly in the Oracle Cerner system failed to the gap to the fulfillment center. The provider saw the order as “active,” while the pharmacy saw nothing. This latency forces site-level pharmacists to constantly toggle between “mail” and “window” dispensing, frequently manually filling prescriptions that should have been mailed, simply to ensure the patient receives them.
Lovell FHCC: The Manual Workaround emergency
The activation of the Captain James A. Lovell Federal Health Care Center in North Chicago in March 2024 provided a live stress test for the CMOP interface. Unlike smaller clinics in Spokane or Walla Walla, Lovell is a high-volume, complex facility shared with the Department of Defense.
Reports from September 2024 indicate that while Lovell avoided the total collapse seen in earlier rollouts, it did so only by throwing human bodies at software problems. The facility had to hire “several additional pharmacists” solely to manage the workarounds required to the gap between the provider’s ordering screen and the pharmacy’s fulfillment software. The systems were not in sync; a doctor could order a refill, the transmission logic would fail to trigger the CMOP release, requiring a pharmacist to manually intervene, cancel the digital order, and re-enter it locally.
Comparative Metrics: VistA vs. Oracle Cerner Interface
The following table contrasts the performance of the legacy VistA CMOP interface against the Oracle Cerner integration as of mid-2024. The data reflects the operational reality at sites like Mann-Grandstaff and Lovell FHCC.
| Metric | Legacy VistA System | Oracle Cerner EHR (2024) |
|---|---|---|
| Transmission Latency | Near Real-Time (<5 minutes) | Variable (Hours to Days) |
| Data Integrity (VUID) | > 99. 9% Accuracy | History of corruption (250k affected) |
| Safety Check Automation | Fully Automated | Requires Manual Verification |
| Staffing Requirement | Baseline | +20% to +60% Increase Required |
| Order Visibility | Bi-directional (Provider sees status) | Uni-directional (“Black Hole” effect) |
The Cost of Broken Automation
The failure of the CMOP interface is not a technical inconvenience; it is a financial. The VA’s mail-order system is designed to drive down costs by centralizing fulfillment. When the Oracle Cerner system fails to transmit an order to CMOP, that prescription must be filled locally at the medical center.
Local filling is significantly more expensive. It requires higher-paid clinical pharmacists to perform tasks that robots handle, consumes local inventory, and increases wait times for veterans physically present at the pharmacy window. In 2024, the “pharmacy freeze” and subsequent “reset” failed to fully resolve these transmission errors. Instead, the VA institutionalized the workarounds, accepting higher staffing costs and slower processing times as the price of keeping the Oracle system online.
also, the absence of reliable address validation in the Oracle system exacerbated these delays. The legacy system possessed rigid address checks to ensure mailability; the Oracle system frequently accepted non-standard address formats that the CMOP machines could not read, resulting in rejected orders that looped back to the site days later, further delaying therapy.
Critical Dosage Calculation Errors: Systemic Failures in Pediatric and Variable Dosing Algorithms
The Lovell Pediatric Stress Test: Algorithms vs. Biology
The March 9, 2024, activation of the Oracle Cerner EHR at the Captain James A. Lovell Federal Health Care Center (Lovell FHCC) in North Chicago represented a unique clinical danger: it was the time the system was deployed at a facility responsible for treating active-duty dependents, including children. Unlike standard VA medical centers that treat a predominantly adult population with standard dosing requirements, Lovell FHCC required the EHR to handle complex, weight-based pediatric calculations. Federal oversight reports from March 2024 confirm that the system failed to provide the necessary algorithmic safety nets for these patients, exposing a fundamental architectural flaw in the software’s ability to process variable dosing.
The core failure method identified in 2024 involved the system’s inability to distinguish between “standard” adult dosing and the non-linear, weight-dependent algorithms required for pediatric care. In verified instances, the Oracle Cerner system defaulted to adult-centric logic, forcing pharmacists to manually calculate dosages outside the system, a practice known as “breaking the loop” that bypasses automated safety checks for allergies and drug-drug interactions. This manual intervention was necessitated by the system’s rigidity; it frequently flagged clinically correct pediatric doses as “underdoses” based on adult metrics, contributing to alert fatigue that caused clinicians to ignore valid warnings.
The “Edit-Delete” Calculation Flaw
Beyond pediatric vulnerabilities, the most pervasive dosage error in 2024 was the “Pharmacy Modification” defect. This software bug, which through the “Block 10” update in February 2024, corrupted dosage instructions when a pharmacist attempted to modify a prescription’s administrative details. If a pharmacist edited a prescription to adjust the “days supply” or “quantity”, a routine administrative task, the system would frequently delete or revert the “Sig” (the dosage instructions) to a null value or a default setting.
For example, a tapering dose of Prednisone (e. g., “40mg for 3 days, then 20mg for 3 days”) requires a complex calculation of total tablets relative to the changing daily intake. When pharmacists attempted to correct the total quantity to match the taper, the Oracle Cerner system frequently stripped the tapering instructions entirely, leaving the patient with a bottle of high-dose steroids and no instructions on how to safely reduce the dosage. This forced pharmacists to adopt a “double entry” workaround, manually typing instructions into a separate text field that the EHR’s safety algorithms could not read or analyze for errors.
| Failure Vector | method of Error | Clinical Consequence | Status (As of Q3 2024) |
|---|---|---|---|
| Modification Corruption | Editing ‘Quantity’ or ‘Days Supply’ deletes dosage instructions (Sig). | Patients receive medication with blank or default instructions, risking overdose. | Unresolved; Workarounds required. |
| VUID Mismatch | System assigns incorrect Vaccine/Drug ID codes during transmission. | Safety algorithms check against the wrong drug, missing lethal interactions. | serious; 250, 000+ patients affected. |
| Pediatric Weight Logic | Algorithm applies adult standard dosing ranges to pediatric weight inputs. | False “Underdose” alerts cause alert fatigue; valid safety checks bypassed. | High Risk at Lovell FHCC. |
| Taper Flattening | Complex variable dosing (tapers) converts to static text strings. | Automated safety checks cannot calculate cumulative dose or toxicity risks. | Persistent defect. |
The VUID Contamination: 250, 000 Patients at Risk
The integrity of dosage calculations relies entirely on the accuracy of the underlying data. In March 2024, the VA Office of Inspector General (OIG) revealed a catastrophic data corruption problem involving “VUIDs” (VA Unique Identifier). The Oracle Cerner system transmitted incorrect medication identifiers to legacy VA sites, poisoning the clinical history of approximately 250, 000 veterans. This data corruption meant that when a veteran visited a legacy site, the safety algorithms used to calculate dosage adjustments for kidney function or drug interactions were running equations based on the wrong variables.
The OIG found that this “widespread transmission” of errors meant a patient prescribed a blood thinner in the Oracle system might appear to be on a different, benign medication in the legacy system. Consequently, the automated dosage calculators at legacy sites would fail to flag a dangerous duplication or interaction. even with Oracle Health executives claiming patches were applied, the OIG noted that the “cleanup” of historical data was incomplete, leaving a quarter-million veterans with digital medical records that contained latent calculation time bombs.
“The impact of these limitations continue at future deployment sites unless they are resolved. They also only become more pronounced at larger, more complex facilities that provide more services and care for more patients.”
, VA Office of Inspector General, Review of Lovell FHCC Deployment, March 2024.
Variable Dosing Algorithm Failures
The system’s inability to handle variable dosing extended to anticoagulation clinics, where precise, fluctuating dosages of Warfarin are life-sustaining. The Oracle Cerner “Anticoagulation Management Tool” failed to reliably calculate the cumulative weekly dose when a patient’s regimen involved alternating daily amounts (e. g., 5mg on Monday, 2. 5mg on Tuesday). In 2024, reports indicated that the system frequently flattened these alternating schedules into a single static value for the purpose of inventory deduction, creating a gap between the clinical order and the pharmacy’s inventory logic.
This “logic gap” forced pharmacists to manually override the inventory counts, a process that removed the electronic audit trail designed to prevent diversion and stockouts. More serious, the absence of algorithmic support for variable dosing meant that the EHR could not generate an accurate ” refill date.” Patients on tapering or alternating doses were frequently denied refills because the system calculated they should still have medication remaining, based on a flawed linear consumption model. This denial of service forced veterans to make emergency appeals to pharmacy staff to override the system’s math, delaying access to serious heart medication.
Pharmacist Attrition Metrics: Quantifying the Human Cost of Click-Heavy Workflows at Mann-Grandstaff and Roseburg
The ‘Hypervigilance’ Tax: Pharmacist Burnout and Attrition
By 2024, the operational reality for pharmacists at Mann-Grandstaff and Roseburg had devolved into a state of chronic “hypervigilance,” a clinical term reserved for PTSD patients applied to the daily workflow of VA pharmacy staff. This psychological was not a reaction to a difficult interface; it was a direct response to the Oracle Cerner system’s propensity to, alter, or misroute prescription data without warning.
Federal oversight data from March 2024 confirms that the “human cost” of the EHR rollout is quantifiable not just in dollars, in the exodus of highly trained clinical staff who could no longer ethically function within the system’s constraints.
Quantifying the: The 62% Staffing Surcharge
The most damning metric of the Oracle Cerner pharmacy module is not its downtime, the sheer volume of human labor required to mitigate its flaws. At the VA Central Ohio Healthcare System in Columbus, a site frequently used as a comparator for Mann-Grandstaff, the Office of Inspector General (OIG) documented a 62 percent increase in the hiring of clinical pharmacists post-implementation.
This surge did not represent an expansion of services for veterans. Instead, these nine additional full-time equivalents (FTEs) were hired primarily to manage the “prescription backlog” and execute manual workarounds necessitated by the software’s inability to process routine orders. For Mann-Grandstaff and Roseburg, this data point validates reports that the system requires nearly double the human effort to achieve the same output as the legacy VistA system.
| Metric | Legacy VistA System | Oracle Cerner EHR | Operational Impact |
|---|---|---|---|
| Processing Time per Order | ~30-60 seconds | 3-5 minutes (with workarounds) | 400% increase in time-on-task |
| Staffing Requirement | Baseline | +62% Clinical Pharmacists | Massive overhead to maintain safety |
| Safety Verification | Automated Checks | Manual “Eyeball” Audits | High risk of “alert fatigue” |
| User Sentiment | High Trust | “Hypervigilance” | Accelerated burnout and resignation |
The ‘Click-Heavy’ Workflow and Moral Injury
The term “click load” fails to capture the severity of the 2024 workflow collapse. Pharmacists at Roseburg reported that simple verification tasks, which previously required three to five keystrokes, demanded upwards of 40 clicks, traversing multiple fragmented screens to verify a single dosage. This mechanical compounded the “moral injury” faced by staff who knew that even with their best efforts, the system was prone to errors that could harm patients.
In May 2023 testimony that remained serious relevant throughout 2024, a Mann-Grandstaff pharmacist described the environment as a “constant state of hypervigilance to recognize and intervene on risks.” By 2024, this vigilance had hardened into a retention emergency. Exit interviews and union reports indicated that pharmacists were not leaving for better pay, to escape the professional liability of working in a system where 250, 000 veterans were flagged by the OIG as being at risk of medication errors due to interoperability failures.
Lovell FHCC: A Success Built on Manual Labor
The March 2024 rollout at the Captain James A. Lovell Federal Health Care Center was publicly touted as a stabilization of the program. Internal metrics tell a different story. To prevent the catastrophes seen in Spokane, the VA deployed a “swat team” method, flooding the North Chicago facility with additional pharmacists and support staff to manually the gaps between the DoD and VA instances of the software.
While this prevented a total collapse, it confirmed that the software itself remained defective. The “success” at Lovell was not a result of software engineering, of unsustainable human capital expenditure. The system still required pharmacists to perform manual double-checks on data transmissions that should have been automated, turning highly paid clinical doctors of pharmacy into data entry clerks.
“The definition of insanity is doing the same thing over and over again while expecting a different result. I have come to believe that continuing this effort… is insanity.”
, Rep. Matt Rosendale (R-Mont.), addressing the pharmacy system failures, February 2024.
The OIG’s ‘Unresolved’ Warning
In September 2024, the OIG issued a report reiterating that serious pharmacy problem identified as early as 2021 remained “unresolved.” This stagnation served as a final straw for senior pharmacists. The report highlighted that the “Unknown Queue” defect, while technically patched, had mutated into new forms of data loss where orders would sit in limbo, neither rejected nor processed.
For the pharmacy workforce, the message was clear: the system was not learning. The attrition rates at legacy sites like Mann-Grandstaff continued to outpace national averages, leaving the remaining staff to shoulder an ever-increasing load of manual safety checks, mandatory overtime, and the looming fear that the software update would be the one to let a fatal error slip through.
The 2024 Deployment Freeze: Operational Paralysis and Safety Risks at the Five Static Pilot Sites
The “VUID” Data Corruption: A New Silent Failure
In March 2024, the VA Office of Inspector General (OIG) exposed a massive data transmission failure that eclipsed previous “Unknown Queue” errors in. The defect involved the VA Unique Identifier (VUID), a digital tag attached to every medication order. When pharmacists at the five Oracle Cerner sites processed prescriptions, the system transmitted incorrect VUIDs to the central Health Data Repository (HDR). This corruption meant that when a veteran visited a non-Cerner VA facility (a “legacy” site), the local VistA system could not correctly identify the drugs the patient was already taking.
| Metric | Verified Data | Operational Consequence |
|---|---|---|
| Affected Veterans | ~250, 000 | Patients at risk of severe drug interactions due to invisible medication history. |
| Mail Order Impact | 120, 000 Patients | Consolidated Mail Outpatient Pharmacy (CMOP) received corrupted data, risking dispensing errors. |
| Duration of Error | 2020 , 2024 | The defect existed since the go-live was only fully characterized by OIG in 2024. |
| Detection Method | Legacy Site Staff | Discovered by VistA users, not by Oracle’s internal monitoring systems. |
This failure method was particularly insidious because it breached the “interoperability” pledge that justified the entire $16 billion program. Instead of connecting VA sites, the Oracle system was actively poisoning the data well for the entire network.
Site-Specific Operational Collapse
The “static” sites were not waiting for updates; they were actively degrading under the weight of a broken system. 2024 data reveals distinct patterns of failure at each location.
Columbus (Ohio): The Staffing Surge Workaround
The VA Central Ohio Healthcare System in Columbus, the largest of the pilot sites, became a case study in brute-force mitigation. Unable to rely on the software’s automation for safety checks, the facility was forced to manually double-check orders.
To maintain basic safety standards in 2024, Columbus had to increase its clinical pharmacy staffing by 62%. This was not a temporary surge a permanent “sustainment tax” required to operate the Oracle Cerner system. The OIG found that pharmacy leaders were forced to create “numerous workarounds” and “overwhelming” educational materials just to prevent the software from harming patients.
Roseburg and White City (Oregon): The Rural Exodus
At the Roseburg VA Health Care System, the software failures compounded an existing rural staffing emergency. By May 2024, reports indicated the facility was operating at approximately 48% of authorized staffing strength.
The Oracle Cerner system’s acted as a repellent for retention. Pharmacists and providers, already stretched thin, faced a “constant state of hyper-vigilance.” The system frequently blocked access to patient notes and failed to trigger serious suicide prevention alerts. Unlike Columbus, Roseburg did not have the labor pool to execute a 62% staffing increase, leaving remaining staff to manage the risk through exhaustion.
Mann-Grandstaff (Spokane): The Permanent Beta
Four years after becoming “Patient Zero,” Mann-Grandstaff remained the epicenter of dysfunction. In 2024, staff reported that the “Unknown Queue” had mutated. While the specific folder label was removed, orders continued to into data voids during inter-departmental transfers.
A specific 2024 incident involved the “Medication Manager Retail” application. Updates intended to fix physician ordering workflows inadvertently broke pharmacy dispensing screens, a phenomenon known as “regression defects.” Pharmacy staff reported that tickets filed for these serious safety problem frequently went months without resolution, as Oracle prioritized the “enterprise” rollout over fixing the “static” sites.
The Lovell Exception and the “Two-System” Risk
In March 2024, the VA proceeded with the go-live at the Captain James A. Lovell Federal Health Care Center (Lovell FHCC) in North Chicago. This was the only site to activate in 2024, justified by its unique joint status with the Department of Defense (DoD). While VA executives touted Lovell as a success, its activation deepened the isolation of the five pilot sites. * Resource Diversion: The “Reset” resources were heavily funneled to Lovell to ensure a political win, leaving the five pilot sites with a “sustainment” crew rather than a “fix” crew. * Data Fragmentation: The network was tri-furcated: The VistA majority, the Lovell “Gold Standard” instance (running a newer code block), and the five pilot sites stuck on an older, bug-ridden configuration.
Financial and Safety Metrics of Stasis
The cost of keeping these five sites in limbo ballooned in 2024. * Sustainment Costs: The VA paid Oracle millions monthly for “sustainment” of the pilot sites, even with the software failing to meet contractual uptime and error-free rate standards. * Patient Harm: By the end of 2024, the VA confirmed that the new EHR had been a contributing factor in at least six patient deaths since inception, with the underlying software flaws responsible for those deaths still present in the pilot site code base. * Alert Fatigue: A 2024 study of the pilot sites showed that providers were overriding over 80% of drug interaction alerts because the system flagged benign interactions as “serious,” training staff to ignore actual safety warnings.
“The situation we found in May of last year was dangerous and unsustainable, and it seems much the same today. Simply put, the medical centers using the Oracle Cerner EHR have been turned upside down.” , Rep. Matt Rosendale, February 2024 Hearing.
The 2024 freeze proved that the VA could not “pause” a disaster. For the veterans and staff at the five static sites, the freeze was an active state of harm, characterized by data corruption, staffing burnout, and a software vendor that was paid to sustain a failure.
Nuisance Alert Overload: Data Showing High Rates of Safety Warnings Ignored Due to System Noise
The “False Positive” Epidemic: 250, 000 Veterans at Risk
In 2024, the Oracle Cerner system’s primary failure method shifted from hidden orders to an overwhelming volume of inaccurate safety warnings. Federal oversight reports released in March 2024 confirmed that widespread interoperability defects created a “noise” loop that desensitized pharmacy staff to genuine threats. The Department of Veterans Affairs Office of Inspector General (OIG) revealed that approximately 250, 000 veterans were subjected to inaccurate medication data transmission between the new Oracle Health sites and legacy VistA facilities. This data corruption forced the system to generate thousands of erroneous Drug-Drug Interaction (DDI) and duplicate therapy alerts, requiring pharmacists to manually verify records that the software should have automated.
The volume of these “nuisance alerts” created a dangerous cognitive load known as alert fatigue. Because the system frequently flagged interactions based on duplicate or missing data, providers became conditioned to bypass warnings to maintain workflow speed. In one documented safety event detailed by the OIG in March 2024, a nurse practitioner overrode a system warning labeled “renewal of current therapy” because the patient’s active medication list was incomplete in the viewable interface. This override, driven by the system’s history of false flags, resulted in a failure to prescribe necessary corticosteroids, directly jeopardizing the patient’s stability.
Lovell FHCC: Operationalizing the Workaround
The activation of the Captain James A. Lovell Federal Health Care Center (Lovell FHCC) in North Chicago on March 9, 2024, demonstrated the operational cost of this software defect. Unlike a functioning modern EHR that streamlines verification, the Oracle Cerner system required a massive infusion of human labor to filter out system noise. Congressional testimony in September 2024 revealed that Lovell FHCC had to maintain 100 additional support staff and experts immediately post-go-live to prevent a collapse in pharmacy services. This mirrored the emergency at the Columbus VA, where pharmacy staffing had to be increased by 62 percent to manage the manual workarounds required by the system’s.
The table categorizes the specific alert failures identified by federal auditors in 2024, distinguishing between technical glitches and data integrity failures.
| Alert Category | Failure method | Operational Consequence |
|---|---|---|
| Interoperability DDI | System flags interactions based on “ghost” data from legacy sites that is duplicative or expired. | Pharmacists must exit the workflow to check JLV (Joint Legacy Viewer) manually, adding 5-10 minutes per order. |
| Duplicate Therapy | Active prescriptions from VistA appear as “new” orders in Oracle, triggering false duplication warnings. | High rate of “reflexive overrides” where staff ignore the warning, risking true double-dosing events. |
| Allergy Warnings | Allergy data fails to transmit or transmits with incorrect severity codes. | 250, 000 veterans left with chance gaps in allergy protection during cross-site visits. |
| Hard Stop Blocks | System locks workflow for non-clinical administrative data gaps (e. g., missing zip code). | Providers use “break-glass” emergency overrides for routine orders, degrading the audit trail. |
The “Check-Box” Safety Illusion
The persistence of these defects created a culture of “check-box” safety, where the act of overriding an alert became a muscle memory rather than a clinical decision. Deputy Inspector General David Case testified in February 2024 that the mitigations for these failures relied entirely on “staff vigilance.” This strategy proved fragile. At the Mann-Grandstaff VA Medical Center, staff reported keeping external spreadsheets to track patient needs because the system’s internal reminders and alerts were deemed unreliable. The OIG found that the system’s inability to reliably distinguish between a true contraindication and a data error forced clinicians to gamble on every override.
“The definition of insanity is doing the same thing over and over again while expecting a different outcome… I have come to believe that this continuing effort to transform the Oracle Cerner pharmacy software into something completely different is insanity.”
, Rep. Matt Rosendale (R-Mont.), House Veterans’ Affairs Subcommittee Hearing, February 15, 2024.
By late 2024, the “nuisance alert” problem had evolved from a software annoyance into a verified patient safety hazard. The OIG identified 48 safety events at Lovell FHCC alone between March and August 2024, a period where the system was supposedly “stable.” These events confirmed that the high noise-to-signal ratio in the Oracle Cerner pharmacy module was not slowing down care, actively obscuring life-threatening errors.
Unscheduled Downtime Logs: The Impact of 2024 Outages on Urgent Care Pharmacy Operations
Unscheduled Downtime Logs: The Impact of 2024 Outages on Urgent Care Pharmacy Operations
In 2024, the definition of “downtime” for the VA’s Oracle Cerner EHR evolved from simple system crashes to a more insidious state of “functional unavailability.” While the system remained technically online for portions of the year, pharmacy operations at the Captain James A. Lovell Federal Health Care Center (Lovell FHCC) and legacy sites like Mann-Grandstaff were frequently paralyzed by data transmission failures, “frozen” screens, and third-party dependencies. These incidents forced urgent care pharmacists to abandon digital workflows for manual paper contingencies, directly delaying acute medication delivery. The following log details the specific outage events and degraded states that defined the 2024 operational.
incident_log_2024: Major Pharmacy System Failures
| Date Range | Incident Type | Affected Sites | Operational Impact on Urgent Care |
|---|---|---|---|
| Feb 21 , Apr 02, 2024 | External Dependency Failure (Change Healthcare Cyberattack) |
Nationwide (inc. Lovell & Mann-Grandstaff) | Catastrophic. Military and VA pharmacies were forced to disconnect from the nation’s largest prescription processor. Pharmacists reverted to “offline” manual checks for drug interactions and insurance validation. Urgent care prescriptions faced severe dispensing delays as staff physically validated dosages without automated safety nets. |
| Mar 09 , Aug 31, 2024 | Post-Deployment Degradation (Lovell FHCC Go-Live) |
Lovell FHCC (North Chicago, IL) | Chronic. Following the March rollout, the facility logged 48 patient safety events directly linked to the EHR. even with a 7% staffing surge to handle the software’s, “acute medical” units struggled to return to baseline capacity. Pharmacists reported “suboptimal clinical workflows” where the system failed to sync provider orders with pharmacy fulfillment screens. |
| Jan 01 , Mar 25, 2024 | “Black Hole” Data Transmission (VUID Mismatch Error) |
All Oracle Cerner Sites & Legacy VistA Sites | serious Safety Risk. A coding error caused the widespread transmission of incorrect “VA Unique Identifier” (VUID) numbers. Approximately 250, 000 veterans had medication data that failed to transmit correctly between new and legacy sites. Urgent care doctors at legacy sites could not see active prescriptions from Oracle sites, creating a high risk of prescribing contraindicated medications during emergencies. |
| August 2024 | Update-Induced Lockout | Mann-Grandstaff VAMC | Acute Access Loss. A routine software update resulted in a multi-day lockout for case managers and clinicians. One documented case involved a case manager losing access to patient records for two full days, preventing the verification of urgent medication histories and delaying time-sensitive care coordination. |
The “Degraded State” Reality
Federal oversight reports from September 2024 confirm that “uptime” statistics provided by Oracle Health masked the reality of daily operations. The Office of Inspector General (OIG) identified a pattern of “performance degradations”, periods where the system was technically online too slow to be usable. In urgent care settings, where minutes matter, these degradations manifested as:
- Frozen Screens: Pharmacists at Lovell FHCC reported instances where the “Medication Manager Retail” module would freeze during order entry, requiring a full workstation reboot while patients waited.
- The “Unknown Queue” Mutation: While the original “Unknown Queue” bug was patched, 2024 saw a mutation of the problem where valid prescriptions into data “black holes” due to interoperability failures. This required pharmacists to manually hunt for orders that physicians insisted had been sent, turning a 30-second verification process into a 20-minute investigation.
- Latency Spikes: During peak urgent care hours, system latency frequently exceeded safety thresholds, delaying the “write-back” of filled prescriptions to the patient’s permanent record. This left subsequent providers blind to immediately preceding treatments.
Manual Workarounds as Standard Operating Procedure
By mid-2024, “downtime procedures” had become standard operating procedures. At Lovell FHCC, the only joint VA-DoD facility, the integration of two massive bureaucracies into one unstable EHR forced the adoption of permanent manual workarounds. Pharmacy staff were required to manually double-check data fields that the software should have automated, such as allergy cross-referencing. This “human middleware” method prevented total system collapse came at the cost of speed and sustainability. The 7% increase in pharmacy staffing at Lovell was not for expanded care capacity, solely to service the of the Oracle Cerner system.
The Billion-Dollar Beta Test: Cost Overruns Directly Linked to Pharmacy Workarounds and Manual Overrides
The Human Middleware Tax: 20% to 60% Staffing Surcharges
The most immediate cost driver in 2024 was not software licensing, the surge in human capital required to operate a defective system. Testimony and internal reports from the House Committee on Veterans’ Affairs revealed a metric: small to medium-sized facilities using the Oracle Cerner EHR were forced to increase pharmacy staffing by at least 20% to process the same volume of prescriptions as the legacy VistA system. For larger, complex medical centers, the VA projected this “staffing surcharge” would balloon to 60%. This increase was not for clinical improvements for “human middleware”, pharmacists and technicians hired solely to manually double-check data, monitor the “Unknown Queue,” and perform dual-entry tasks that the software failed to automate.
| Operational Metric | Legacy VistA System | Oracle Cerner EHR | Financial Impact |
|---|---|---|---|
| Staffing Baseline | Standard Ratios | +20% to +60% Required | Millions in unbudgeted salaries per site |
| Prescription Processing Time | Seconds | Minutes (due to dual entry) | 30-40% reduction in patient throughput |
| Error Rate (Safety Events) | Baseline | ~20% of all safety reports | High liability and remediation costs |
| System Uptime | 99. 9% | 826 Major Incidents (2020-2024) | 1, 909+ hours of lost productivity |
The Dual-Entry Deficit
A specific technical failure drove these costs: the inability of the Oracle Cerner core EHR to reliably communicate with the “Medication Manager Retail” module used for mail-order prescriptions. In 2024, pharmacists were frequently required to enter prescription data twice, once in the clinical record and again in the dispensing system, to ensure the order was not lost in the digital ether. This “swivel-chair interface” introduced a high risk of transcription errors and doubled the administrative time per order. A software patch intended to fix this interoperability failure was deployed in April 2023 was immediately rolled back due to “serious” errors that caused dosage instructions to. Throughout 2024, no permanent fix was implemented, leaving the costly manual workaround as the standard operating procedure.
Lovell FHCC: A “Success” Bought with Manpower
The March 2024 launch at the Captain James A. Lovell Federal Health Care Center (Lovell FHCC) was touted as a stabilization milestone. yet, the operational reality contradicted the “success” narrative. To prevent the “Unknown Queue” from endangering patients at this joint VA-DoD facility, the VA deployed a massive surge of support staff. Internal reports indicate that Lovell FHCC required significant “bolstering” of pharmacy personnel to manage the system’s. This deployment masked the software’s defects with human labor, creating a false sense of stability while inflating the daily operational cost of the facility. The “reset” period, intended to fix these bugs, instead solidified a model where the VA paid Oracle for the software and then paid its own staff overtime to bypass it.
The $50 Billion gap
The cumulative effect of these workarounds contributed to a widening chasm in lifecycle cost estimates. While the VA’s revised 2024 estimate pegged the program’s total cost at $37. 2 billion, an independent assessment by the Institute for Defense Analyses (IDA) warned the true figure was likely closer to $50 billion. This $13 billion gap is largely attributable to the “sustainment” costs, the long-term price of maintaining higher staffing levels, running parallel legacy systems, and funding the “tiger teams” required to monitor the Oracle Cerner deployment. By the end of 2024, the VA had spent over $9 billion on a system that, in the pharmacy sector, was less and more expensive to operate than the 40-year-old VistA platform it was meant to replace.
“We cannot keep writing a blank check that risks taxpayer money and slows down, or worse, endangers the delivery of veteran care.”
, Rep. Tom Barrett (R-Mich.), Chairman of the House Veterans’ Affairs Technology Modernization Subcommittee, December 2025.
The financial data from 2024 confirms that the Oracle Cerner system has shifted the cost load from technology to labor. Every “glitch” in the pharmacy module is a line item in the VA’s personnel budget, converting a one-time software purchase into a recurring annual deficit.
Contractual Non-Compliance: Oracle Health's Failure to Meet Pharmacy Performance Benchmarks in Fiscal Year 2024
The “Incident-Free” Fallacy: Redefining Failure in FY2024
By the close of Fiscal Year 2024, the Department of Veterans Affairs and Oracle Health operated under a renegotiated contract intended to impose strict accountability. The May 2023 modification, throughout 2024, introduced a new metric: “incident-free time.” This was designed to close a loophole where the system could be technically “online” (meeting uptime benchmarks) functionally useless due to lag or feature failures. even with these stricter terms, federal oversight in September 2024 revealed that the vendor continued to bypass performance standards through semantic definitions of stability.
While Oracle Health executives touted a system availability rate exceeding 99. 95% for most of 2024, the VA Office of Inspector General (OIG) exposed a different reality. Between the contract modification in May 2023 and March 2024, the EHR system experienced 193 major performance incidents. These were not minor glitches; they were severe degradations where pharmacy and clinical workflows stalled, ranging from one minute to over 18 hours in duration. The between Oracle’s “green light” dashboard and the clinicians’ “red light” reality demonstrates a persistent failure to meet the “incident-free” contractual obligation.
The Lovell “Success” Tax: Staffing Surges as a workaround
The deployment at the Captain James A. Lovell Federal Health Care Center (Lovell FHCC) in March 2024 was the primary test case for the “Reset” period. Oracle and VA leadership characterized this launch as a success, citing improved adoption rates compared to previous sites. yet, this stability was not achieved through software optimization through a massive, costly injection of human capital that violates the efficiency mandates of the original contract.
To maintain baseline pharmacy operations and prevent the patient safety risks seen in Spokane and Columbus, Lovell FHCC required a staffing increase of approximately 7%, amounting to over 100 additional employees. This “Lovell Tax” confirms that the Oracle Cerner pharmacy module, specifically the Medication Manager Retail (MMR), remains incapable of handling standard VA prescription volumes without excessive manual intervention. The contract originally promised a system that would; instead, the 2024 rollout necessitated a permanent surge in labor to the gap between the software’s capabilities and the facility’s needs.
| Performance Metric | Oracle Claim (FY2024) | OIG Verified Reality (Sept 2024 Report) |
|---|---|---|
| System Uptime | 99. 95%, 100% (10 of 16 months) | Irrelevant due to 1, 909 hours of “Major Performance Incidents” since go-live. |
| Incident Frequency | “Near zero interruptions” | 193 Major Incidents recorded between May 2023 and March 2024. |
| Pharmacy Throughput | “Consistent with legacy volumes” | Achieved only via 7% staffing increase and 100+ new hires at Lovell FHCC. |
Pharmacy Latency and Data Integrity Violations
In 2024, the definition of a “crash” evolved. For pharmacists at Lovell and legacy sites, the system frequently remained “up” exhibited severe latency that violated performance benchmarks. The OIG’s March 2024 reports highlighted that the MMR module struggled with data transmission speeds, creating dangerous lags between a physician entering an order and the pharmacy receiving it. This latency directly contravenes the “responsiveness” metrics outlined in the May 2023 contract renewal.
also, the “interoperability” requirement, a of the multi-billion dollar deal, failed during the Lovell rollout. The joint DoD-VA facility experienced synchronization errors where patient demographic data did not match between the scheduling and pharmacy modules. This forced pharmacists to perform manual identity checks, slowing the dispensing process and increasing the risk of handing controlled substances to the wrong patient. These errors even with Oracle’s assurance that the “Reset” period would resolve the code-level defects responsible for data corruption.
“The results of the VA and Oracle strategy to improve the EHR have been one step forward and one step backwards. We’re not gaining on this… I have come to believe that continuing this effort, to transform the Oracle Cerner pharmacy software into something completely different, is insanity.”
, Rep. Matt Rosendale (R-MT), House Veterans’ Affairs Committee Hearing, February 2024.
Financial Credits vs. Contract Renewal
The renegotiated contract included provisions for “monetary credits”, essentially fines, that Oracle must pay when performance metrics are missed. While the VA asserted that these credits would have been “30-fold higher” had the new terms been in place earlier, the agency’s actions in June 2024 suggest a reluctance to fully enforce these penalties. Instead of leveraging the documented failures to seek a termination for cause or a massive clawback of funds, the VA exercised an option to extend the contract for another 11 months.
This extension occurred even with the OIG’s finding that the VA and Oracle still absence “adequate controls” to prevent system changes from causing major outages. The decision to renew, rather than pause or cancel, indicates that the VA is currently trapped in a vendor lock-in scenario, where the cost of extracting the failed system is perceived as higher than the cost of paying for a non-compliant product. As of late 2024, the “credits” assessed against Oracle remain a fraction of the total program cost, which has ballooned from $10 billion to an estimated $50 billion over its lifecycle.
Regulatory Outlook: The “Reset” That Wasn’t
The “Reset” period officially ended with the Lovell deployment, yet the widespread defects identified in 2022 remain in the 2024 architecture. The OIG’s September 2024 audit confirmed that the root causes of pharmacy instability, specifically the code base’s inability to handle complex, variable-dose prescriptions without manual workarounds, have not been remediated. The “incident-free” metric has proven to be a paper tiger; Oracle continues to collect taxpayer funds for a system that requires a shadow workforce to function. As the VA looks toward a chance resumption of rollouts in 2025, the 2024 record stands as proof that the vendor is not meeting its contractual mandate to deliver a safe,, and autonomous pharmacy system.
