Compared to other developed nations, the delivery of safe and high-quality healthcare in the U.S. has reached a crisis in terms of comparative personal loss due to preventable morbidity and mortality, excessive/uncontrolled costs, and poor care coordination across the continuum of care delivered by trans-domain networks of independently managed/operated heterogeneous systems. From the point of view of a systems engineer, it is clear that healthcare, as it exists in the U.S. today, is neither a force multiplier-enhanced “system” nor a “System of Systems” (SoS), and continues to rely on a fragmented delivery model that is highly dependent on the immediate findings and expertise of an individual provider. Most patients receive services that are poorly integrated with complementary services and relevant information resources. Consequently, unlike our military operations, healthcare operations generally lack Situational Awareness (SA) and therefore are not effectively “preemptive” (e.g. effective preventive care), and/or capable of delivering highly precise/coordinated/timely care. Moreover, inconsistent component capabilities and lack of coordinated repeatable processes towards common objectives limit the capacity for continuous improvement.
It is asserted that what is missing in the national healthcare industry is an overarching “systems of systems engineering” (SoSE) foundation, heavily used by the DoD, that applies sound, proven systems engineering tools to the identification, understanding, and optimization of interrelated legacy and evolving constituent care delivery systems processes as a collective SoS .
The foundational tools of any SoS engineering process includes:
- Definition of the measurable objectives/capabilities or goals of the SoS
- Elaboration of the interdependencies/interfaces between and among system components (e.g. constituent systems)
- Clarification of the roles of the constituent systems necessary to achieve system of systems level capability/performance (e.g. decomposed functional/performance/operational SoS level requirements allocated to component systems)
Healthcare as a whole is not managed as a set of well-defined interrelated processes driven by end-to-end SoS goals that have been decomposed and allocated to component systems, but instead performance requirements and interdependencies between component systems (in-patient care, ambulatory care, specialty care, EMRs, patient portals, medical devices, etc.) are loosely defined at best. Government incentives/penalties designed to reward/encourage value based care and information exchanges using “standards” have been unable to shift the existing fee-for-service environment and overcome the barriers to SA bred by the proliferation of proprietary, information intensive healthcare systems that were not initially developed for an integrated SoS mission.
The growing role of information intensive systems in clinical practice SoS (composed of clinicians/providers, information systems and institutional equipment devices used across the care continuum) provides the opportunity for positive digital technology force multiplicative transformation of care delivery. However today’s U.S. healthcare lacks a clear definition of overall objectives or goals at the SoS level, lacks clarity on the interdependencies between component systems (including critical human factored man-machine and interoperable machine-machine interfaces), and most importantly fails to allocate critical care requirements to these components necessary to achieve overall system of system goals.
Without these most basic formative systems engineering underpinnings, our emerging digitally supported healthcare system will continue to fail to meet force multiplicative performance expectations and instead deliver care that, at best, represents the suboptimal sum of constituent systems, and at worse, reflects new technology use challenges for safety and quality.
 Charles B. Keating, Polinpapilinho F. Katina (2011) “Systems of systems engineering: Prospects and challenges for the emerging field,” International Journal of System of Systems Engineering, 2(2/3), 234–256. http://doi.org/10.1504/IJSSE.2011.040556