Lecture 8: Interoperability Requirements

Week 8.
Enterprise IT Architecture
IT Management
School of Creative Industries
Overview
A definition of interoperability is "the ability to share information and services". Defining the degree to which the
information and services are to be shared is a very useful architectural requirement, especially in a complex
organization and/or extended enterprise.
• The determination of interoperability is present throughout the Architecture Development Method (ADM) as
follows:
• In the Architecture Vision (Phase A), the nature and security considerations of the information and service
exchanges are first revealed within the business scenarios
• In the Business Architecture (Phase B), the information and service exchanges are further defined in business
terms
• In the Data Architecture (Phase C), the content of the information exchanges is detailed using the corporate data
and/or information exchange model
• In the Application Architecture (Phase C), the way that the various applications are to share the information and
services is specified
• In the Technology Architecture (Phase D), the appropriate technical mechanisms to permit the information and
service exchanges are specified
• In Opportunities & Solutions (Phase E), the actual solutions (e.g., Commercial Off-The-Shelf (COTS) packages)
are selected
• In Migration Planning (Phase F), the interoperability is logically implemented
Defining Interoperability
There are many ways to define interoperability and the aim is to define one that is consistently
applied within the enterprise and extended enterprise. It is best that both the enterprise and the
extended enterprise use the same definitions.
Many organizations find it useful to categorize interoperability as follows:
• Operational or Business Interoperability defines how business processes are to be shared
• Information Interoperability defines how information is to be shared
• Technical Interoperability defines how technical services are to be shared or at least connect
to one another
From an IT perspective, it is also useful to consider interoperability in a similar vein to Enterprise
Application Integration (EAI); specifically:
• Presentation Integration/Interoperability is where a common look-and-feel approach through
a common portal-like solution guides the user to the underlying functionality of the set of systems
• Information Integration/Interoperability is where the corporate information is seamlessly
shared between the various corporate applications to achieve, for example, a common set of
client information
Defining Interoperability
Many organizations create their own interoperability models, such as illustrated in the example below from
the Canadian Government. They have a high-level definition of the three classes of interoperability and
identify the nature of the information and services that they wish to share. Interoperability is coined in terms
of e-enablers for e-Government. Their interoperability breakdown is as follows:
• Information Interoperability:
• Knowledge management
• Business intelligence
• Information management
• Trusted identity
• Business Interoperability:
• Delivery networks
• e-Democracy
• e-Business
• Enterprise resource management
• Relationship and case management
• Technical Interoperability:
• IT infrastructure
In certain architectural approaches, such as system of systems or a federated model, interoperability is a
strongly recommended best practice that will determine how the systems interact with each other. A key
consideration will be the enterprise's business operating model.
Enterprise Operating Model
Key to establishing interoperability is the determination of the corporate operating model, where
the operating model is "the necessary level of business process integration and standardization
for delivering goods and services to customers. An operating model describes how a company
wants to thrive and grow. By providing a more stable and actionable view of the company than
strategy, the operating model drives the design of the foundation for execution."
For example, if lines of business or business units only need to share documents, then the
Architecture and Solution Building Blocks (ABBs and SBBs) may be simpler than if there is a
need to share structured transaction data. Similarly, if the Architecture Vision includes a shared
services environment, then it is useful to define the level the services are to be shared.
The corporate operating model will normally indicate what type of interoperability approach will
be appropriate. This model should be determined in Phase A (Architecture Vision) if not in
Phase B (Business Architecture), and definitely by Phase E (Opportunities & Solutions).
Complex enterprises and/or extended enterprises (e.g., supply chain) may have more than one
type of operating model. For example, it is common for the internal operating model (and
supporting interoperability model) to differ from the one used for the extended enterprise.
Refining Interoperability
Implementing interoperability requires the creation, management, acceptance, and
enforcement of realistic standards that are SMART (Specific, Measurable, Actionable,
Realistic, and Time-bound). Clear measures of interoperability are key to success.
Architecture is the key for identifying standards and facilitated sessions (brainstorming) will
examine potential pragmatic ways (that fit within the current or emerging business culture) to
achieve the requisite degree of interoperability.
Interoperability should be refined so that it meets the needs of the enterprise and/or
extended enterprise in an unambiguous way. The refined interoperability measures
(degrees, types, and high-level targets) should be part of or referred to the Enterprise
Architecture strategic direction.
These measures are instantiated within a transformation strategy that should be embedded
within the Target Architecture definition and pragmatically implemented in the Transition
Architectures. Upon completion, also update the consolidated gap analysis results and
dependencies to ensure that all of the brainstorming nuggets are captured.
Determining Interoperability
Requirements
Co-existence between emerging and existing systems, especially during
transformation, will be a major challenge and brainstorming should attempt to
figure out what has to be done to reduce the pain. It is imperative to involve the
operations management staff and architects in this step as they will be
responsible for operating the portfolio deliverables.
For example, there might be a need for a "wrapper" application (an application
that acts as the interface [a.k.a. interpreter] between the legacy application and
the emerging infrastructure). Indeed, pragmatically, in the "if it works do not fix it"
world, the "wrapper" might become a permanent solution.
Regardless, using the gap analysis results and business scenarios as a
foundation, brainstorm the IT issues and work them through to ensure that all of
the gaps are clearly identified and addressed and verify that the organization-
specific requirements will be met.
Reconciling Interoperability
Requirements with Potential Solutions
The Enterprise Architect will have to ensure that there are no interoperability
conflicts, especially if there is an intention to re-use existing SBBs and/or
COTS.
The most significant issue to be addressed is in fact business interoperability.
Most SBBs or COTS will have their own business processes embedded.
Changing the embedded business processes will often require so much work
that the advantages of re-using solutions will be lost. There are numerous
examples of this in the past.
Furthermore, there is the workflow aspect between the various systems that
has to be taken into account. The Enterprise Architect will have to ensure that
any change to the business interoperability requirements is signed off by the
Business Architects and architecture sponsors in a revised Statement of
Architecture Work.
Semantic as a function of syntactic interoperability
• Syntactic interoperability, provided by for instance XML or
the SQL standards, is a pre-requisite to semantic. It involves a common
data format and common protocol to structure any data so that the manner
of processing the information will be interpretable from the structure. It also
allows detection of syntactic errors, thus allowing receiving systems to
request resending of any message that appears to be garbled or
incomplete. No semantic communication is possible if the syntax is garbled
or unable to represent the data. However, information represented in one
syntax may in some cases be accurately translated into a different syntax.
Where accurate translation of syntaxes is possible, systems using different
syntaxes may also interoperate accurately. In some cases, the ability to
accurately translate information among systems using different syntaxes
may be limited to one direction, when the formalisms used have different
levels of expressivity (ability to express information)
Interoperability in Cloud Solutions
Why Is Interoperability Important?
• Adaptability: Business systems that receive information can
quickly and automatically connect and share the information to the
relevant parties.
• Better Productivity: Businesses can operate more smoothly, as
necessary data is readily available and accessible to all relevant parties
and systems. This is a much more efficient process compared to
waiting for vital information required to achieve goals.
• Data Unity: Interoperability provides data unity, which is essential
for helping businesses to manage and access information from external
systems and vice versa.
Why Is Interoperability Important? Part 2
• Improved Data Protection: Data protection is a requirement for any business.
Fortunately, this process helps protect sensitive data. Companies can access
this via shared records offered through interoperability instead of manually
and repeatedly entering personal information.
• Fewer Errors: Information systems that are connected usually result in better
quality data and, thus, fewer errors. Indeed, this is a better option than systems
that are not connected and are more likely to contain duplicate and outdated
data.
• Lower Costs: Synchronized systems can send and receive information
automatically. In turn, this takes up fewer resources and costs compared to
non-inoperable systems that must request data manually from another system.
Use Case: Interoperability in Healthcare
• The well-known and influential organization, Healthcare Information and
Management Systems Society (HIMSS) has developed a
definition of interoperability, which is accepted and understood by most
healthcare stakeholders. They describe interoperability as “the ability of
different information technology systems and software applications to
communicate, exchange data, and use the information that has been
exchanged.”
Four Layers of Interoperability
• Foundational interoperability:
In this layer, interoperability lets the data transmitted by one HIT system be received by
another. I call this, ‘opening the pipes’ for the data to flow through. This was the focus of
Meaningful Use Stage 1, creating the ability to exchange data between systems.
• Structural/Syntactic interoperability:
The next layer, structural interoperability, defines the format of the data exchange that takes
place between systems. Also known as syntactic or technical interoperability, this layer
structures the data for exchange. One informaticist that I have worked with called this
“putting the words into sentences”, thus adding context to the data or “words” being
exchanged.
Four Layers of Interoperability
• Semantic interoperability
This level of interoperability adds a layer of understanding ensuring that the sending and receiving
systems are using the same language in that sentence that is being shared. In healthcare that means
that the structured message contains standardized, codified data. This capability aims to create a
common vocabulary that enables accurate and reliable, machine-to-machine communication, thus
ensuring reliable data and optimizing patient and organizational outcomes.
• Organizational Interoperability
This fourth level of interoperability is a relatively new add by the HIMSS organization and identifies
the importance of bringing all the levels together. This level includes governance, standard operating
procedures, policies, and social and legal considerations that are important to be able to ensure data
governance and data privacy across an organization.
Importance of Interoperability in Healthcare
• Interoperability speeds patient care
It is imperative that when a provider is first seeing a patient whether it be in a medical emergency, a natural disaster, or simply because the
patient is changing providers, they have access to the patient’s history, current conditions, treatments, and allergies. The data being presented at
the point of care must be optimized and reliable. It must be semantically interoperable, fully auditable, and managed with robust data
governance practices in place.

• Interoperability enables clinicians and patients to manage chronic conditions

According to the World Health Organization (WHO), 60% of all deaths worldwide can be attributed to chronic diseases. According to the
Centers for Disease Control (CDC),
90% of the nation’s annual healthcare spending is for people living with chronic and mental health conditions . They go on to say that there are
proven interventions that can be cost-effective and increase the quality and longevity of life for those suffering from chronic disease.

• Interoperability reduces physician burden

The burden to providers of documentation and provider-to-payer communication has been well documented and is a top priority for the
Department of Health and Human Services
End of Week 8 Lecture