Part A – Healthcare Interoperability Measures:- Cartesian Dilemma (Diagnosis)

Those in blue in the below content are reproduced from the referenced links.Slide06

Definition of Cartesian Dilemma; per Alexander Christopher

(what eyes sees and the mind sees are two different things)

Cartesian Dilemma


From above link

“””””Alexander has been inexorably led to the revolutionary necessity of revising our basic picture of the universe to include a conception of the personal nature of order and our belonging to the world in which the wholeness of space and the extent to which it is alive is perceived as rooted in the plenum behind the visible universe, “the luminous ground” that holds us all. This form of extended objective truth will ultimately resolve our Cartesian dilemma by teaching us a new view of order and a new cosmology in which objective reality “out there” and a personal reality “in here” are thoroughly connected and the bifurcation of nature healed.””””””

“”To Rene Descartes the “Method” (1638) was a convenient mental trick but its success has left us with a mindset that conceives of the universe as a machine without any intrinsic value: the realms of human experience and of feeling are simply absent from the Cartesian world. Whilst inspiring generations of architects and many others from all walks of life concerned with the fate of the earth, Alexander’s ultimately life changing work has understandably provoked powerful opposition from those invested within the establishment of the old paradigm. Social disorder, mental illness, ecological degradation, these and many other problems are due to a misunderstanding of the structure of matter and the nature of the universe and, until quite recently, there has been no coherent way of explaining the order that we respond to and love in nature.””


Affordability Care Act and HITECH Act lead into EHR Incentive Program. Based on the EHR Incentive Program CMS has already payed out 24+ Billions of dollars to Eligible Participants. Has it or will it drive the envisioned Healthcare Interoperability still remains a big question. Specifically will it be possible to mine the millions of records and discover opportunity for improvement? Without emphasis on clinical decision support will it be possible to achieve efficacy in the healthcare delivery, while also advancing the opportunities for “pay for performance” outcomes?

To advance EHR adoption in the Healthcare Ecosystem CMS proposed formation of Accountable Care Organization


From the above link

“”The Pioneer ACO Model is designed for health care organizations and providers that are already experienced in coordinating care for patients across care settings. It will allow these provider groups to move more rapidly from a shared savings payment model to a population-based payment model on a track consistent with, but separate from, the Medicare Shared Services Program. And it is designed to work in coordination with private payers by aligning provider incentives, which will improve quality and health outcomes for patients across the ACO, and achieve cost savings for Medicare, employers and patients.””

Importantly CMS proposed roadmap for EHR Adoption based on Meaningful Use (MU) 3 Stages, in the hope of advancing interoperability in the healthcare ecosystem ultimately achieving performance driven model, where the payment models shifts from “pay for service” towards “pay for performance”. Looking at the Healthcare ecosystem, one must take note that achieving efficiency is in the healthcare management; while achieving efficacy is in the healthcare delivery.

You will see in the end of the discussion that somehow efforts of the EHR Incentive Program lays more emphasis on the helathcare efficiency without paying required attention to clinical efficacy. This leads to the systemic entropic discontinuity that can be described by the Boltzmann constant.

This results into missed Line of Sight, where the established “objective”s at the IT / EHR level do not deliver all the required the “business capabilities” or the output and hence the desired “transformative outcomes” are not realized.


From the above link:-

“”In statistical mechanicsBoltzmann’s equation is a probability equation relating the entropy S of an ideal gas ( or consider healthcare ecosystem) to the quantity W, which is the number of microstates corresponding to a given macrostate.”””

Following are the EHR Adoption Meaningful Use Stages:-

MU Stage 1 :- Achieves electronic capture of the patient data (Data Capture and Sharing)

MU Stage 2 :- Achieves Health Information Exchanges (Advances co-ordinated clinical processes)

MU Stage 3:- Target Improved Outcomes ( achieved by moving the payment model from pay for service to pay for performance)

The eligible participants, physicians, hospitals and the ACOs have to demonstrate that they have met the MU criteria in stages. To demonstrate that they have met the requirements, first of all it is required to demonstrate that the data being captured adhere to a prescribed format. This is ascertained by MU attestation.

Additionally, the eligible participants are required to submit quality measures reports to CMS


From the above link

“””” Quality Measures and Performance Standards

Quality data reporting and collection support quality measurement, an important part of the Shared Savings Program. Before an ACO can share in any savings generated, it must demonstrate that it met the quality performance standard for that year. There are also interactions between ACO quality reporting and other CMS initiatives, particularly the Physician Quality Reporting System (PQRS) and meaningful use. The sections below provide resources related to the program’s 33 quality measures, which span four quality domains: Patient / Caregiver Experience, Care Coordination / Patient Safety, Preventive Health, and At-Risk Population. Of the 33 measures, 7 measures of patient / caregiver experience are collected via the CAHPS survey, 3 are calculated via claims, 1 is calculated from Medicare and Medicaid Electronic Health Record (EHR) Incentive Program data, and 22 are collected via the ACO Group Practice Reporting Option (GPRO) Web Interface.””””

https://www.cms.gov/Medicare/Quality-Initiatives-Patient-Assessment Instruments/QualityMeasures/index.htm/lredirect=/QUALITYMEASURES/

National Quality Forum (NQF) endorsed for CMS reports are :

  • The Hospital Inpatient Quality Reporting (IQR) Program,
  • The Hospital Outpatient Quality Reporting (OQR) Program,
  • The Physician Quality Reporting System (PQRS), and
  • Others as directed by CMS, such as long-term care settings and ambulatory care settings

The CMS quality reporting is based on the schematic derived from HL7, termed QRDA


From the above link

Overview of QRDA

“””The Health Level Seven International (HL7) QRDA is a standard document format for the exchange of electronic clinical quality measure (eCQM) data. QRDA reports contain data extracted from electronic health records (EHRs) and other information technology systems. QRDA reports are used for the exchange of eCQM data between systems for a variety of quality measurement and reporting initiatives, such as the Centers for Medicare & Medicaid Services (CMS) EHR Incentive Program: Meaningful Use Stage 2 (MU2).1

The Office of the National Coordinator for Health Information Technology (ONC) adopted QRDA as the standard to support both QRDA Category I (individual patient) and QRDA Category III (aggregate) data submission approaches for MU2 through final rulemaking in September 2012.2 CMS and ONC subsequently released an interim final rule in December 2012 that replaced the QRDA Category III standard adopted in the September 2012 final rule with an updated version of the standard.3 QRDA Category I and III implementation guides (IGs) are Draft Standards for Trial Use (DSTUs). DSTUs are issued at a point in the standards development life cycle when many, but not all, of the guiding requirements have been clarified. A DSTU is tested and then taken back through the HL7 ballot process to be formalized into an American National Standards Institute (ANSI)-accredited normative standard.

QRDA is a subset of CDA HL7 Standard; QRDA is a constraint on the HL7 Clinical Document Architecture (CDA), a document markup standard that specifies the structure and semantics of clinical documents for the purpose of exchange.4 To streamline implementations, QRDA makes use of CDA templates, which are business rules for representing clinical data consistently. Many QRDA templates are reused from the HL7 Consolidated CDA (C-CDA) standard5, which contains a library of commonly used templates that have been harmonized for MU2. Templates defined in the QRDA Category I and III IGs enable consistent representations of quality reporting data to streamline implementations and promote interoperability.”””

On the contrary we have Office Of National Coordinator (ONC) stipulate and regulate standards to achieve Healthcare Interoperability

ONC Roadmap Vision in the below link


From above link:-

Sadly, although Evidence based is discussed, data mining and concerns around algorithm development is missing.


Connecting Health and Care for the Nation: A Shared Nationwide Interoperability Roadmap version 1.0 (Roadmap) [PDF – 3.7 MB] supports the vision that ONC outlined in Connecting Health and Care for the Nation: A 10 Year Vision to Achieve An Interoperable Health IT Infrastructure [PDF – 607 KB]. The Roadmap, shaped by stakeholder input, lays out a clear path to catalyze the collaboration of stakeholders who are going to build and use the health IT infrastructure. The collaborative efforts of stakeholders is crucial to achieving the vision of a learning health system where individuals are at the center of their care; providers have a seamless ability to securely access and use health information from different sources; an individual’s health information is not limited to what is stored in electronic health records (EHRs), but includes information from many different sources and portrays a longitudinal picture of their health, not just episodes of care; and where public health agencies and researchers can rapidly learn, develop, and deliver cutting edge treatments.


http://www.healthit.gov/buzz-blog/from-the-onc-desk/oncinteroperability- roadmap-update/

There is no doubt that ONC aspires to achieve true Healthcare Interoperability, by bringing more clarity to the Health Information Exchange (HIE) as discussed in the below link.

Interoperability vs Health Information Exchange: Setting the Record Straight

ONC under its purview has Office of Standards and Technology, which drives the Interoperability Standards; and it acknowledges that there are numerous challenges in realizing the ONC roadmap; as discussed in the below link

Interoperability Standards – Shades of Gray

Also ONC specifies roadmap in achieving MU stages for physicians, hospitals and ACOs ( HIE)

Specifically for the Semantic Interoperability it recommends Consolidated – Clinical Document Architecture ( C-CDA).


CDA helps in representing a comprehensive view of the patient; complete birth-to-death view – Longitudinal Record.

Also ONC Interoperability Specification Address the Following three levels (Not adequate to achieve EBM driven CDSS):-

There are three levels of health information technology interoperability:  1) Foundational; 2) Structural; and 3) Semantic.

1 – “Foundational” interoperability allows data exchange from one information technology system to be received by another and does not require the ability for the receiving information technology system to interpret the data.

2 – “Structural” interoperability is an intermediate level that defines the structure or format of data exchange (i.e., the message format standards) where there is uniform movement of healthcare data from one system to another such that the clinical or operational purpose and meaning of the data is preserved and unaltered. Structural interoperability defines the syntax of the data exchange. It ensures that data exchanges between information technology systems can be interpreted at the data field level.

3 – “Semantic” interoperability provides interoperability at the highest level, which is the ability of two or more systems or elements to exchange information and to use the information that has been exchanged. Semantic interoperability takes advantage of both the structuring of the data exchange and the codification of the data including vocabulary so that the receiving information technology systems can interpret the data. This level of interoperability supports the electronic exchange of patient summary information among caregivers and other authorized parties via potentially disparate electronic health record (EHR) systems and other systems to improve quality, safety, efficiency, and efficacy of healthcare delivery.

Desired or Recommended 2nd Order Semantic Interoperability

Probabilistic Ontology Driven Knowledge Engineering

Ref:- http://www.ncbi.nlm.nih.gov/pubmed/22269224

Chronically ill patients are complex health care cases that require the coordinated interaction of multiple professionals. A correct intervention of these sort of patients entails the accurate analysis of the conditions of each concrete patient and the adaptation of evidence-based standard intervention plans to these conditions. There are some other clinical circumstances such as wrong diagnoses, unobserved comorbidities, missing information, unobserved related diseases or prevention, whose detection depends on the capacities of deduction of the professionals involved.

< diagnosis > < procedures > < outcomes > [triple store]


From the above points it must be noted that QRDA and C-CDA achieves different things. Unfortunately, against MU attestation and quality reports that are filed by the eligible participants (physicians, hospitals and ACOs) based on QRDA (especially PQRA), CMS runs the EHR incentives program. Whereas, in the MU2 stage ( as per ONC), it is also required by the participants to demonstrate that they have achieved interoperability within ACO, while implementing HIE, this requires C-CDA. This stage must demonstrate that coordinated clinical processes have been achieved.

Also, clinical decision support system (CDSS) has been established addressing at least 5 critical or clinical priority areas.  Unfortunately this particular capability does not seems to be addressed adequately by the ACOs; who only pursue to demonstrate quality measures have been achieved which necessarily does not mean clinical efficacy have been addressed. 

It seems an important architectural problem has been glossed over by the policy designers, who proposed quality measures model with the motivation for capturing the metrics that eventually demonstrate “pay for performance”; and somehow assumed that the proposed metrics based on QRDA also demonstrate that the clinical efficacies have been achieved. This leads into systemic entropic discontinuity, where the efforts at macro states that represents healthcare management leading into healthcare efficiency  is not necessarily a cumulative realization for the efforts at the micro states which represents gaining clinical efficacy. This entropic discountuinity between the macro state and the micro states is measured by Boltzmann Constant.

Link to more discussion on micro states and macro states within a complex system. Basically discusses for a given complex system, and for all the efforts towards the input; the entropy arrested and created loss, so the output is a actually created incurring loss. This means the systemic efficiency incurred losses and did not realize all the benefits arising out of the clinical efficacy. This is a model problem which inaccurately represents the “phenomenon of interest”.


To achieve Clinical Decision Support System capability which rather plays a very important role in enhancing clinical efficacy, developing data mining driven Evidence Based Medicine capability is imperative. This capability does not seem as being achieved because most HIE / ACO is being developed around QRDA; although discussed in the ONC Connecting Health and Care for the Nation: A Shared Nationwide Interoperability Roadmap version 1.0 (Roadmap) [PDF – 3.7 MB]; unless data mining related algorithmic challenges are addressed which means standards beyond mere capture of the required data fields, interoperability efforts will be in vain.

Role of EBM in achieving CDSS discussed on following sites

CMS Site


NIH Site


As such it must be noted clinical errors is one among the highest risk becoming the No 3 Killer in the US.


From above link

“””It’s a chilling reality – one often overlooked in annual mortality statistics: Preventable medical errors persist as the No. 3 killer in the U.S. – third only to heart disease and cancer – claiming the lives of some 400,000 people each year. At a Senate hearing Thursday, patient safety officials put their best ideas forward on how to solve the crisis, with IT often at the center of discussions. “””


Bioingine (www.bioingine.com); a Cognitive Computing Platform transforms the patient information (millions of records) created by the HIE into Ecosystem Knowledge Landscape that is inherently evidence based, allowing for study of the Tacit Knowledge, as discovered from the millions of patient records (large data sets) by mining and knowledge inference in an automated way. This is achieved employing AI, Machine Learning and such techniques. Thereby, creating Clinical Decision Support System.


In Lack of Theories – Planning will be along a Straight Line

Light bends in a gravitational field

Einstein's prediction (1907): Light bends in a gravitational field

Enterprise Architecture as a discipline promotes a framework of theories useful for planning the enterprise behavior. It might take years for verifying a theory; but in lack of it, manifold years will be needed to salvage the wrong done. In lack of theories the planning will be along a straight line, completely missing what mind should have uncovered and rather relying on what meets the eye. Furthermore, while acknowledging that planning is not moving along a straight line, it also must factor that random action exists that gives rise to unpredictability. This means detecting actions that leads into fragments and anticipating consequence due to them is very important both in structure and in behavior.

Most important among all other theories in the realm of EA is ‘Theory of Constraints’. Per ‘Programmed Cell Death’ A Constraint provides information about the current state and why it evolved into its present state from the past. Also, it provides inference into the possible future state. TOC also ties into system dynamics that can be explained by entropy. All these together has a consequence in terms of the behavior, especially with the probabilistic determinism at macroscopic level and indeterminism at microscopic level. The all encompassing behavior of the enterprise as an instrument with no beginning and end is explained by ‘implicate order’, which also accounts for generative transformations by unfoldments the DNA of which exists enfolded. All encompassing means an inclusive and a pluralistic architectural framework.

Checkout: Creative People At Work – Tribute to Einstein’s Thought Experiment – “Traveling On a Beam of Light”.


Emergence of Universe – Thought Experiment that traces the origin of Universe and where possibly it might go. This is study of generative transformation.


9 Billion Dollar Scientific Experiment – To verify the creation of world. Why do we need this? Keep asking this billion dollar question (that is 9 times manifold, 1000 times manifold – a million dollar question)

Case Study – Strategy & Enterprise Architecture

Strategy Game  

By Srinidhi Boray

Enterprise Engineering & few fundamentals to ponder about : –  


Definition of EA as a subject? (is it management, or economics, or sociology, or psychology, information technology, is it any one of these or all of them working together choreographed by chaos, or the management’s whim, or the market forces). What really is this dicey animal !?Where do the following elements fit in the larger EA space :


  • Structure
  • Behavior
  • Canonical View,
  • “Single Version of Truth”
  • Strategy
  • Capabilities
  • Vision
  • Mission
  • Goals
  • Objectives
  • Features
  •  Requirements
  • Specifications



There are many definitions for EA. Almost all  the attempts from the IT folks renders the boundary of the EA quite narrow and it tends to become IT centric. The original vision for EA was to encompass the broadest sense, while making the best attempt in capturing the descriptive details of an enterprise existing as a magnificent juggernaut. 


Try asking several who have worked at the same company for several years to describe the company they work for. Each one of them will come up with their own description as the picture conjured in their mind. None of them will have a common definition. In some abstraction they all are attempting to define the single truth. But when the description is broken down into details, then each will come up with a model that suits best to the picture that they carry in their mind. Is this wrong? And, should one attempt a ‘canonical’ view, a term quite favorite to IT folks. At the highest and the broadest sense, a single version of truth necessarily does not mean a canonical view. But when dealing with information engineering within the information architecture cross section, then canonical view is certainly a notion to work on to achieve a unified enterprise wide information framework. 


As an exercise, or for an excellent case study, you can read the document at the following link http://www.sec.gov/about/secstratplan0409.pdf) published by SEC. This is their 2004 to 2009 Strategic Plan.


Very good document to explore from EA perspective, although as an EA one might not find it to be structured accurately. That is the job of the EA anyway to ‘structure’, while understanding who has written this – Is it CEO, CIO or CTO. Obviosly it is not CTO or CIO. Also questions you will ask are: Does this document deal with the strategic plan or it is really dealing with tactical requirement? Then it could be ‘strategy’ in this document is a tautology issue. If not, then from management perspective what really is a ‘strategy’ and how is it different from ‘tactical’ efforts that improves the overall performance or the organizational effectiveness. Which disposes an enterprise uniquely, is it strategy or tactics? Refer Michael Porter on ‘what is strategy’. Structurally where does ‘strategy’ lie and where should ‘tactics’ exist. Is strategy from EA framework perspective, concept, context or logical? Can ‘tactic’ lie in the same space as ‘strategy’, if not then where should it be. What values are the thoughts like these adding to EA. 

“What is Strategy?”    


Michael E. Porter     Harvard Business Review, November-December 1996.Today’s dynamic markets and technologies have called into question the sustainability of competitive advantage. Under pressure to improve productivity, quality, and speed, managers have embraced tools such as TQM, benchmarking, and reengineering. Dramatic operational improvements have resulted, but rarely have these gains translated into sustainable profitability. And gradually, the tools have taken the place of strategy. As managers push to improve on all fronts, they move further away from viable competitive positions. Michael Porter argues that operational effectiveness, although necessary to superior performance, is not sufficient, because its techniques are easy to imitate. In contrast, the essence of strategy is choosing a unique and valuable position rooted in systems of activities that are much more difficult to match.Order article at Harvard Business Online


Ram Charan’s Lecture 


Why is it crucial to know how to link Strategy to Tactical Execution (Most Failures occur here)

And, render Governance via a ‘social system’ as a productive unit of work. 



Now after gaining some clarity on ‘strategy’ what are the thoughts running in the mind, presumed that it is wearing the EA hat . (its always piqued at its tip 🙂 ) I guess some like these :- The overall entropy. The overall system dynamics. What SEC does to secure stability in the market. The types of financial derivatives exists in the market. How market trade different products. What Fed does to ensure market stability. How policies are made and why? How are they operationalized.  How can the various behaviors be better described and understood. Why did the market fail despite all the systems in place. Why did ‘randomness’ or speculation become the dominant behavior. What is a Systemic Fault and how did it manifest. What role does EA play in understanding all these?