1. Connected Health Framework
A Stable Foundation for Agile Healthcare
An Architecture & Design Blueprint
In-depth Architectural Guidance
- from Requirements to Solutions

2. Vision
Define an overarching framework for Health Industry Architecture
Best practices for service oriented health information integration and collaboration architectures
Enterprise-, state-, province- and country-wide projects
Faster ROI
Based on open standards and protocols
Develop ecosystem of CHF-enabled solutions
Faster ROI for customers
Benchmark for partners solutions

3. Connected Health Framework
Focus is on major issues specific to Connected Health solutions
Provides:
A Business Pattern for Healthcare
A Reference Technical Architecture for Healthcare
Based on real worldwide experience
Created, reviewed and approved by
Microsoft architects, engineering teams and consultants
and
Microsoft Partners and Customers

4. Guiding Principles Achieve Application Integration, through
A Stable Foundation and Agile Implementations
Managed Multiplicity of Platform and Location
Flexible Application Configuration and Process Engineering
Consistent, available, understandable Data Sources
Legacy Rejuvenation and Reuse
Expressed as:
A Business Pattern for Healthcare
Achieve Technical Interoperability, through
Open Standards
Best Practice Guidelines
State of the Art technical capabilities
Secure, manageable, efficient infrastructures
A Reference Architecture for Connected Health

5. The Connected Health Framework in Context

6. CHF Business Framework
The CHF Business Framework uses a service oriented approach to
Define business components and major subject areas
Offer a range of services that can be “orchestrated” to enable and support business processes
Leverage existing sources of functionality and information
It provides a Business Pattern for Healthcare
The Connected Healthcare Framework is focused on the achievement of Application Integration and Technical Interoperability. It uses a Service-oriented Approach anfd offers a number of “Business Components” from which Healthcare solutions can be built.

7. CHF Business Framework
This diagram shows a Business Pattern for Healthcare as envisaged by the CHF Business Framework.
Patterns are useful things. A pattern describes a generic solution to a recurring problem, within a defined context. The basic premise of patterns is that, if something has been done successfully before, don’t reinvent the wheel. Developing and implementing a Service Oriented Architecture is amenable to a pattern-based approach. Patterns are available to address the business, integration and technical aspects of SOA.
There are two possible, but complementary, ways to look at this – the first is to say that other enterprises, operating is a similar business domain, probably have an inventory of business components and services similar to yours. The implementations will be different because the infrastructural environment will be different, but in terms on conceptual function and data, they will be similar. For Patient-centric Healthcare, we have defined of a number of business components and services.
These were derived from real-life and proof-of-concept projects and include:
Patient Component
Professional Access History Component
Patients’ Events Component
Patient Consents Component
Health Subject Component
Care Pathways Component
Appointments Component
GP & Hospital Systems Access Component
Clinical Processes Component
Groups & Teams Component
Professionals Component
Permissions Component
This list forms a basic inventory of components for a patient-centric care record system.
Specializing the above definition, a Business Pattern describes a re-usable approach to the solution of a particular business problem, usually scoped by a business process. It offers a solution based on previous success in defining solutions to the same, or similar, business problems. A business pattern may be described as an ‘Architectural template for a business solution’.
The components are platform and technology independent and each is also functionally independent and uniquely “owns” its data. Indicative contents (function and data) have been defined. The functionality and data is made available via defined services. These services have been identified. The component based approach provides a highly modular Integration Framework and, besides providing a development specification, provides means of evaluating the content, coverage and fit of 3rd party and legacy derived components.
Given an inventory of components and services such as this, we can foresee a potential service-oriented architecture for Healthcare as in this diagram.
The formation of this Business Pattern is described in detail in Part 2 of the CHF Architecture and Design Blueprint. The detailed structure and content of the Healthcare Business Components is described in Part 4.

8. CHF Technical Framework
The CHF Technical Framework addresses:
Multiplicity of services, sources of data and systems
Management of patient and clinician identity
Integration across multiple systems
Flexibility and agility
Security
Scalability, Performance and Availability
It provides a Reference Architecture for Service Oriented Healthcare Integration

9. CHF Technical Framework
This diagram shows a typical reference architecture, based on the Microsoft Connected Healthcare Framework (CHF), for implementing an e-Health integration solution.
The Reference Architecture is centered round the use of the Connected Health Services Hub which enables the provision of a number of services including:
Identity Management Services
Privacy and Security Services
Presentation and Point of Access Services
Service Publication and Location Services
Electronic Health Record (EHR) Services
Health Domain Services
Health Registry Services
Integration Services
Data Services
System Management Services
Communication Services
These are described in detail in Part3 of the CHF Architecture and Design Blueprint

10. Key Architectural Principles
3/25/2017
Key Architectural Principles
Service oriented architecture
Allows for modular and flexible approach
Based on open standards
Focus on the basics, add additional services later
Discoverability of services
Data network
UI is an additional service
Federated or centralized data
Focus on subset of Critical Care Information
Data ownership is preserved
Federated security
Centralized security management extremely complex
Trustworthy
Reliable, fault tolerant… 10

11. Support for Both Centralized and Federated Deployment Models

12. A Stable Foundation for Agile Healthcare

13. © 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.