Microsoft Connected Health PlatformA Foundation for Service Oriented Health Industry Solutions
Dr Ilia FortunovIndustry Technology Strategist - EMEAMicrosoft Worldwide Health
Connected Health Framework 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• Leverage available assets to deliver more value faster• Based on open standards and protocols – platform-agnostic
– Develop ecosystem of CHF-enabled solutions• Deliver value for customers faster and at lower cost • Frame of reference for partners solutions• Easier integration across multiple solution areas
2Microsoft Connected Health Framework
Connected Health FrameworkBusiness 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 Health
3Microsoft Connected Health Framework
Microsoft Connected Health Framework 5
Business FrameworkCommunications
Operations Management
Security
Connected Health Services Hub
User Processes
Business Processes
Data Access Logic Components
Business Components
Service Interface Components
Patients
Care Pathways
Patient Events
Appointments
Healthcare Professionals
Professional Groups & Teams
Professional Permissions
Professional Access History
Patient Consents Health Subjects
GP & Hospital Systems Access
Clinical Processes
Databases
Connected Health FrameworkTechnical 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 Health
6Microsoft Connected Health Framework
Technical FrameworkCommunication
Operations Management
Security
Collaboration, Presentation and Point of Access, Identity Management, Privacy and
Security Services
Service Publication and Location, Shared Services
System Management Services
Communication Services
Data Services
Connected Health Services HubIntegration Services
Business ComponentsService Component Interface
7Microsoft Connected Health Framework
Connected Health Framework ArchitectureCommunication
Operations Management
Security
Collaboration Services
Presentation and Point of Access Services
Identity Management Services
Privacy and Security Services
Service Publication and Location
Shared Services
System Management Services
Communication Services
Data Services
User Processes
Business Processes
Connected Health Services HubIntegration Services
Business ComponentsService Component Interface
Data Access Logic ComponentsSTABLE
AGILE
Options For Storing Clinical Data
Mostly a matter of ownership and policy• Centralized model
– Central repository holds replica of full health record– Clinical Data Exchange (CDX) Gateway publishes full
health record and manages data synchronization• Federated model
– Central repository holds no personal data– CDX Gateway publishes registration events and caches
full record obtained from multiple sources• Hybrid model
– Central repository holds record summary– CDX Gateway publishes record summary and caches
full record– Could be multi-tier, with many data stores
9Microsoft Connected Health Framework
12
Communication
Operations Management
Security
Collaboration Services
Presentation and Point of Access Services
Identity Management Services
Privacy and Security Services
Service Publication and Location
Shared Services
System Management Services
Communication Services
Data Services
User Processes
Business Processes
Connected Health Services HubIntegration Services
Business ComponentsService Component Interface
Data Access Logic Components
CHF Ecosystem – Who does what?
Customer Specific(MS provides Guidelines,
Platform Products, Assistance)
ISV Provided (MS provides Business Pattern – Component and Service Definitions)
MS or SI Partner Provided
SI Partner Provided(MS provides Reference Architecture
and SDKs)
SI Partner Provided(MS provides Reference Architecture and SDKs)
ISV or SI Partner Provided (MS provides platform and guidance)
Microsoft Connected Health Framework 13
Building Solutions Using the CHF Blueprint
• Key scenarios depending on the role:– Customer - Formulating Requirements (RFP)– Vendor/Systems Integrator - Meeting Requirements
(Responding to an RFP) – Software Vendor - Aligning an ISV Application with the
CHF– Infrastructure provider - Establishing the Environment
• CHF (Part 4) provides guidance for each, e.g.:– Understanding Scope & Boundaries– Understanding the Required Features– Deriving the Architecture – Defining the Solution
Connected Health Framework: Levels and Components
• Connected Health Frameworkis Microsoft’s multi-year world-wide industry strategy, encompassing our industry solutions, partner strategy, platform offering and policy initiatives.
• Connected Health Framework – Architecture and Design Blueprintoffers a set of vendor-agnostic best practices and guidelines for
building the next generation of interoperable e-Health solutions based on a service-oriented architecture (SOA) and industry standards – ranging from within healthcare organizations to regional, national and cross-agency systems
• Microsoft Connected Health Platformis Microsoft technology offering and prescriptive architecture guidance for e-Health solutions built on the Microsoft platform
– Health Connection Engine (HCE)– Common User Interface (CUI)– … etc.Microsoft Connected Health Framework 14
Communication
Operations Management
Security
Collaboration Services
Presentation and Point of Access Services
Identity Management Services
Privacy and Security Services
Service Publication and Location
Shared Services
System Management Services
Communication Services
Data Services
User Processes
Business Processes
Connected Health Services HubIntegration Services
Business ComponentsService Component Interface
Data Access Logic Components
Microsoft’s Connected Health Platform
Office System
Visual Studio, .NET Framework
BizTalk Server, .NET Framework
Office System, LiveMeeting,Exchange,
Windows Server System
Operations Manager, System CenterSQL Server
Windows Mobile
Reference Implementations
• Health Connection Engine (HCE)– Community project on http://www.CodePlex.com/hce– Accelerates the development and deployment of connected solutions
• Adapters SDK• Standard set of Web Services
– Based on BizTalk, SQL Server and the .NET Framework• Microsoft Common Health User Interface (MSCUI)
– Available at http://www.mscui.net – Community project on http://www.CodePlex.com/mscui– Facilitates development of consistent and safe clinical user interfaces– Based on .NET Framework
• IHE Cross-Enterprise Document Sharing-b (XDS.b)– Community project on http://www.CodePlex.com/ihe– Implements standard IHE Integration Profile to facilitate sharing of clinical
and health documents– Based on .NET Framework and SQL Server
16Microsoft Connected Health Framework
Health Connection Engine (HCE)
• Community project on http://www.CodePlex.com/hce• Accelerates the development and deployment of
connected solutions– Adapters SDK– Standard set of Web Services
• Based on BizTalk, SQL Server and the .NET Framework
• First reference implementation in line with the Connected Health Framework – Architecture and Design Blueprint
• Developed in partnership with SIMPL Health (NZ)
Microsoft Connected Health Framework 17
Health Connection EngineCommunication
Operations Management
Security
Collaboration Services
Presentation and Point of Access Services
Identity Management Services
Privacy and Security Services
Service Publication and Location
Shared Services
System Management Services
Communication Services
Data Services
User Processes
Business Processes
Connected Health Services HubIntegration Services
Business ComponentsService Component Interface
Data Access Logic Components
HCE Services and Registries
Messaging Management Services
Adapters
Messaging Management Services
IHE/XDS Reference Implementation
Adapters
Adapters
Tools: Auditing - Reporting Access - Configuration
1. Sources post document packages to the Repository
2. Repository registers the documents metadata and pointer with the Registry
3. Consumers search for documents with specific information
4. Consumers retrieve documents from Repository(ies)
XDS Document (Metadata):TypePatientAuthorFacilityAuthenticator…
RepositoryOrigin of
Documents Package
Registry
Microsoft IHE XDS.b Reference Implementation
Operational considerations: smart-client…web-based…multi-device…Clinical User Interface Fundamentals
22Microsoft Connected Health Framework
Creating a SafeUseable Clinical UI
Fast and Effective User Interaction
Optimised for multiple styles of interaction e.g. keyboard, mouse, stylusAuto-populate to minimize data entryPresent relevant options at the right time
Fast and Effective User Interaction
Optimised for multiple styles of interaction e.g. keyboard, mouse, stylusAuto-populate to minimize data entryPresent relevant options at the right time
Consistent Navigation and Layout
Based on established norms and standardsDraws on generally accepted best practice designStrong familiarity between different applicationsReduces cognitive load on user
Consistent Navigation and Layout
Based on established norms and standardsDraws on generally accepted best practice designStrong familiarity between different applicationsReduces cognitive load on user
Leveraging Technology Developments
Intelligent systems behaviourBuilt-in decision and knowledge supportContext-sensitive information presentation
Leveraging Technology Developments
Intelligent systems behaviourBuilt-in decision and knowledge supportContext-sensitive information presentation
Compelling User InterfaceEasy and intuitive to userEasy to learnUser goal-driven workflow
Compelling User InterfaceEasy and intuitive to userEasy to learnUser goal-driven workflow
“Safe by Design”User-centred iterative design processBuilt in safety and hazard assessmentsEvidence based recommendations
“Safe by Design”User-centred iterative design processBuilt in safety and hazard assessmentsEvidence based recommendations
23Microsoft Connected Health Framework
Common User InterfaceCommunication
Operations Management
Security
Collaboration Services
Presentation and Point of Access Services
Identity Management Services
Privacy and Security Services
Service Publication and Location
Shared Services
System Management Services
Communication Services
Data Services
User Processes
Business Processes
Connected Health Services HubIntegration Services
Business ComponentsService Component Interface
Data Access Logic Components
Medical Research and Reference Services
User Interface Components
User Interface Components
Resources and Next Steps
• The Connected Health Framework – Architecture and Design Blueprint is available now– More details on http://msdn.microsoft.com/health– Contact your local Microsoft subsidiary or [email protected]
to engage– Provide feedback and discuss on http://SolShare.net
• Understand the Health Connection Engine– Submit bugs and feature requests– Contribute to the development
• Think service oriented business and technical architectures– Leverage Microsoft’s platform for security, collaboration,
management, integration…30Microsoft Connected Health Framework
© 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and
Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.