Actionable intelligence gathered from these informal workarounds reveals a significant need for software engineering fixes that prioritize the actual movement of clinical labor over data rigidity. The United States Department of Veterans Affairs is currently navigating a monumental shift in its technological landscape, moving away from the “VistA” platform that served as the primary digital heartbeat for federal medical facilities for many decades. This transition represents one of the most ambitious healthcare IT projects ever attempted, aiming to bridge the data gap between the VA and the Department of Defense through a unified commercial electronic health record (EHR). However, the implementation of this standardized software has encountered a stubborn obstacle: the human element of clinical practice. Rather than seamlessly adopting the rigid protocols of the new system, frontline providers have increasingly turned to a “culture of improvisation” to maintain the flow of patient care. This evolution from formal procedure to informal adaptation suggests that for a large portion of the workforce, the software’s intended workflows have become secondary to the immediate demands of the clinical environment.
The Mechanics of System Failure
Identifying Persistent Barriers: The Rise of Informal Solutions
The transition to a unified commercial EHR was expected to provide a streamlined, interoperable experience for clinicians, yet the reality observed at early implementation sites indicates a recurring disconnect between digital design and physical labor. A qualitative study published in the Journal of General Internal Medicine highlights that even several years into the deployment, clinicians continue to grapple with persistent operational impediments that extend far beyond simple learning curve frustrations. These barriers often involve complex navigation paths, redundant data entry requirements, and a lack of flexibility that fails to account for the unpredictable nature of emergency or high-volume care settings. In response to these friction points, medical staff have developed a sophisticated repertoire of workarounds. These informal pathways are not viewed by the staff as acts of technological rebellion, but rather as essential survival strategies designed to ensure that the primary mission—caring for veterans—is not compromised by the very tools meant to facilitate it.
These workarounds often manifest as clinicians documenting patient encounters in secondary applications or physical notes before transcribing them into the EHR at a later time, or finding “backdoor” methods to bypass mandatory fields that do not apply to specific scenarios. While these practitioners are acutely aware that such deviations can introduce risks to data integrity and patient safety, they often perceive these risks as the lesser of two evils when compared to the potential for care delays. The research suggests that these adaptations are not temporary fixes but have become foundational to the way care is delivered in the current environment. This reliance on improvisation points to a fundamental sociotechnical misalignment, where the software’s architecture assumes a level of linear predictability that rarely exists in a complex medical facility. By prioritizing rigid data capture over the fluidity of clinical movement, the system inadvertently forces users to operate outside of its formal guardrails to remain productive.
The Hardening of Unofficial Workflows: A Mask for Systemic Issues
One of the most concerning developments in the ongoing EHR modernization project is the “hardening” of these informal practices into what are effectively unauthorized standard operating procedures. When a workaround is used once to solve an immediate problem, it is a glitch; when it is used daily by an entire department to maintain throughput, it becomes the new baseline for operations. This normalization of deviance creates a significant blind spot for administrators and software developers. Because clinicians are finding ways to make the system “work” through underground methods, the official performance metrics may show that tasks are being completed and data is being entered, effectively masking the extreme level of effort and the potential safety hazards involved in those processes. This surface-level functionality provides a false sense of security, leading leadership to believe the implementation is stabilizing while the underlying structural flaws remain unaddressed and hidden by the manual labor of the workforce.
The institutionalization of these workarounds also complicates the training of new staff and the overall scalability of the EHR platform. When new clinicians enter the system, they are often taught the “official” way to use the software during orientation, only to be shown the “real” way by their peers once they arrive on the clinical floor. This creates a fragmented organizational culture where the digital record no longer serves as a single source of truth but rather as a distorted reflection of the actual medical work being performed. The long-term consequence of this hardening is a system that remains static and unresponsive to user needs, as the signals for necessary change are suppressed by the very people who need them most. To break this cycle, the focus must shift from simply documenting task completion to understanding the cognitive and physical load required to achieve it. Without this insight, the modernization effort risks building a permanent infrastructure of inefficiency that will plague federal healthcare for years to come.
Risks and Sociotechnical Consequences
Patient Safety Concerns: The Distortion of Medical Data
The proliferation of a workaround culture within a federal healthcare system introduces profound vulnerabilities, particularly concerning the automated safeguards that modern EHRs are designed to provide. Standardized systems typically include “hard stops” and decision-support tools that alert providers to dangerous drug-drug interactions, allergic reactions, or inconsistent clinical data. When clinicians develop habits of bypassing certain interfaces or delaying documentation to save time, they effectively neutralize these digital safety nets. This creates a precarious environment where the speed of care delivery is maintained at the cost of the systemic checks intended to protect vulnerable veterans. The risk is not merely theoretical; bypassing mandatory documentation fields or using informal notes can lead to critical information being omitted from the patient’s permanent record, which may result in medical errors when other providers access that incomplete data during future encounters.
Beyond the immediate physical risks to patients, the normalization of informal documentation leads to a phenomenon known as “data distortion.” In a modern, data-driven healthcare organization, the EHR serves as the primary source for quality metrics, research, and resource allocation. If the data entered into the system is the result of workarounds—such as back-dating entries or entering generic placeholders to satisfy mandatory fields—the resulting analytics will be inherently flawed. This lack of accurate, real-time information means that the healthcare system is essentially “flying blind,” unable to accurately monitor its own performance or identify emerging safety trends. When the gap between the medical record and the clinical reality becomes too wide, the integrity of the entire federal health database is compromised, undermining the very goal of the modernization effort which was to create a reliable, unified platform for longitudinal veteran care.
Sociotechnical Misalignment: The User Interface Gap
The struggle between clinicians and the new EHR system highlights a significant gap in sociotechnical alignment, specifically regarding how a standardized commercial product interacts with a specialized public health workforce. The previous “VistA” system, despite its age, was highly valued by clinicians because it was frequently customized at the local level to fit the specific workflows of individual departments. In contrast, the current commercial platform is designed for broad standardization, which often prioritizes billing and administrative data capture over the intuitive needs of a practicing physician or nurse. This shift from a flexible, user-centered tool to a rigid, data-centered platform has created a significant interface gap. Clinicians find themselves spending more time navigating menus and clicking through checkboxes than engaging with their patients, a reality that fuels burnout and drives the search for shortcuts that restore a sense of professional agency and efficiency.
Addressing this misalignment requires a deeper understanding of the “human-computer interaction” within the clinical workspace. The current system often fails to account for the cognitive load required to manage complex patient cases, forcing users to keep track of vital information mentally or on paper because the EHR interface is too cumbersome to update in real-time. This friction is not just a matter of convenience; it is a structural failure of the technology to integrate into the flow of medical work. To narrow this gap, the software must be viewed not as a static repository for data, but as a dynamic tool that supports the mental models of healthcare providers. This involves redesigning interfaces to reduce clicks, improving the visibility of critical patient data, and ensuring that the digital environment mimics the natural progression of a clinical encounter. Failure to address these sociotechnical discrepancies will ensure that workarounds remain the primary method of operation, regardless of how many training hours are mandated.
Challenges of Modernization and Future Policy
The Complexity of EHR Transitions: Utilizing Clinician Intelligence
The ongoing effort to modernize the VA’s digital infrastructure is complicated by the unique challenges of an EHR-to-EHR transition, which differs significantly from moving from paper to digital records. Clinicians are not just learning a new tool; they are unlearning a system that they have used for decades and which was deeply integrated into their professional identities. The persistence of workarounds years after the initial launch suggests that the “big bang” implementation strategy—where a system is rolled out rapidly with the promise of fixing bugs later—may be fundamentally ill-suited for a complex organization like the Department of Veterans Affairs. This approach often underestimates the emotional and professional friction caused by the loss of a familiar, highly customized tool, leading to a prolonged period of instability where the workforce remains in a state of perpetual adaptation rather than reaching a level of proficient, standardized use.
To navigate this complexity, the department must begin to treat clinician feedback and the workarounds themselves as “actionable intelligence.” Rather than viewing these deviations as misbehavior to be corrected through stricter enforcement or repetitive training, they should be analyzed as diagnostic clues that point directly to the system’s most critical failures. By employing frameworks such as the Sociotechnical Evaluation of Workarounds (SEWA), administrators can distinguish between training gaps that can be resolved through education and structural flaws that require fundamental software engineering changes. This proactive approach acknowledges that the frontline staff are the best-positioned experts to identify where the software fails to meet the needs of the veteran population. Integrating this clinician intelligence into the development cycle is the only way to move beyond a culture of improvisation and toward a system that truly supports the delivery of high-quality federal healthcare.
Strategic Integration: Frontline Feedback for Systemic Improvement
As the modernization project continues to expand across more sites, the strategic integration of frontline feedback will be the determining factor in its ultimate success or failure. The department has already faced several pauses in its rollout due to safety and performance concerns, and these moments of reflection should be used to build a more robust, iterative deployment model. This model must move away from the top-down imposition of software and toward a collaborative environment where the end-users—doctors, nurses, and technicians—have a direct seat at the table during the design and refinement phases. By creating formal mechanisms for reporting and analyzing workarounds, the VA can turn “underground” knowledge into transparent, data-driven improvements that benefit the entire network. This shift would allow for the creation of order sets and documentation templates that reflect actual clinical reality rather than idealized administrative workflows.
Furthermore, future policy must prioritize the reduction of “documentation burden” as a core metric of EHR success. If a system requires more time for data entry than for patient care, it is failing its primary mission regardless of its technical capabilities. The goal for the coming years should be to automate as much data capture as possible and to refine the user interface so that it acts as a silent partner in the clinical room, rather than a barrier between the provider and the veteran. Treating the EHR as a living, evolving organism that requires constant sociotechnical adjustment will allow the VA to bridge the current gap between design and delivery. Only by transforming informal, risky fixes into safe, formal system enhancements can the federal government ensure that its investment in modern technology results in a healthier future for those who have served.
Transforming Informal Intelligence into Structural Stability
The Department of Veterans Affairs faced a critical juncture as researchers determined that the transition to a modern EHR platform inadvertently institutionalized a culture of improvisation. It was observed that clinicians at early implementation sites relied on self-devised workarounds to bypass rigid software constraints, viewing these unofficial methods as necessary for maintaining patient care. This development indicated that the software design often prioritized data capture over the practical movements of medical labor, leading to a “hardening” of informal practices that masked systemic flaws from administrative oversight. Analysts pointed out that these workarounds, while functional in the short term, introduced significant risks to patient safety and data integrity by neutralizing built-in digital safeguards. The reliance on non-standard procedures created a distortion of medical records, which hindered the department’s ability to accurately monitor quality metrics and long-term veteran health outcomes.
Moving forward, the department established more robust feedback loops that treated these clinician workarounds as essential diagnostic data rather than disciplinary issues. By conducting detailed sociotechnical audits, administrators identified specific interface barriers and documentation burdens that required immediate engineering fixes. Technical teams worked to simplify navigation paths and automate redundant data entry tasks, directly addressing the friction points that drove clinicians “underground.” Policy shifts focused on reducing the cognitive load on healthcare providers, ensuring that the digital environment supported, rather than obstructed, the clinical mental model. These interventions allowed for a more iterative and user-centered approach to the nationwide rollout, turning the lessons learned from early friction into a more resilient and safe electronic health record system. The transition eventually moved toward a state where formal protocols aligned with clinical reality, ensuring that the modernization effort truly served its intended purpose.
