Presentation on theme: "Connected Health Framework"— Presentation transcript:
1 Connected Health Framework A Stable Foundation for Agile HealthcareAn Architecture & Design BlueprintIn-depth Architectural Guidance- from Requirements to Solutions
2 VisionDefine an overarching framework for Health Industry ArchitectureBest practices for service oriented health information integration and collaboration architecturesEnterprise-, state-, province- and country-wide projectsFaster ROIBased on open standards and protocolsDevelop ecosystem of CHF-enabled solutionsFaster ROI for customersBenchmark for partners solutions
3 Connected Health Framework Focus is on major issues specific to Connected Health solutionsProvides:A Business Pattern for HealthcareA Reference Technical Architecture for HealthcareBased on real worldwide experienceCreated, reviewed and approved byMicrosoft architects, engineering teams and consultantsandMicrosoft Partners and Customers
4 Guiding Principles Achieve Application Integration, through A Stable Foundation and Agile ImplementationsManaged Multiplicity of Platform and LocationFlexible Application Configuration and Process EngineeringConsistent, available, understandable Data SourcesLegacy Rejuvenation and ReuseExpressed as:A Business Pattern for HealthcareAchieve Technical Interoperability, throughOpen StandardsBest Practice GuidelinesState of the Art technical capabilitiesSecure, manageable, efficient infrastructuresA Reference Architecture for Connected Health
6 CHF Business Framework The CHF Business Framework uses a service oriented approach toDefine business components and major subject areasOffer a range of services that can be “orchestrated” to enable and support business processesLeverage existing sources of functionality and informationIt provides a Business Pattern for HealthcareThe 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 ComponentProfessional Access History ComponentPatients’ Events ComponentPatient Consents ComponentHealth Subject ComponentCare Pathways ComponentAppointments ComponentGP & Hospital Systems Access ComponentClinical Processes ComponentGroups & Teams ComponentProfessionals ComponentPermissions ComponentThis 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 systemsManagement of patient and clinician identityIntegration across multiple systemsFlexibility and agilitySecurityScalability, Performance and AvailabilityIt 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 ServicesPrivacy and Security ServicesPresentation and Point of Access ServicesService Publication and Location ServicesElectronic Health Record (EHR) ServicesHealth Domain ServicesHealth Registry ServicesIntegration ServicesData ServicesSystem Management ServicesCommunication ServicesThese are described in detail in Part3 of the CHF Architecture and Design Blueprint
10 Key Architectural Principles 3/25/2017Key Architectural PrinciplesService oriented architectureAllows for modular and flexible approachBased on open standardsFocus on the basics, add additional services laterDiscoverability of servicesData networkUI is an additional serviceFederated or centralized dataFocus on subset of Critical Care InformationData ownership is preservedFederated securityCentralized security management extremely complexTrustworthyReliable, fault tolerant…10
11 Support for Both Centralized and Federated Deployment Models
Your consent to our cookies if you continue to use this website.