Presentation is loading. Please wait.

Presentation is loading. Please wait.

Slide 0 EHR SD RM - EHR Way Forward … Future State Reference Architecture HSSP Practitioners Guide Volume II Immunization and Adverse Event Reporting Prototype.

Similar presentations


Presentation on theme: "Slide 0 EHR SD RM - EHR Way Forward … Future State Reference Architecture HSSP Practitioners Guide Volume II Immunization and Adverse Event Reporting Prototype."— Presentation transcript:

1 Slide 0 EHR SD RM - EHR Way Forward … Future State Reference Architecture HSSP Practitioners Guide Volume II Immunization and Adverse Event Reporting Prototype From HL7 and HITSP Artifacts For presentation at HL7 Rio Workgroup Meeting, May 2010 Six Weeks to Rio, 19 March 2010 Minutes PHONE: Pass code # WEB: Details available at HL7 EHR SD RM Lead Project Editor GovProjects, EHR, PHER, HSSP co-sponsors

2 Slide 1 EHR SD RM - EHR Way Forward … Future State Reference Architecture Agenda ItemMax Time Roll Call and Introductions 3 min Overview Agenda 2 min Overview of HSSP Practitioners Guide Volume I 10 min Overview of Services Aware Interoperability Framework (SAIF) 10 min Overview of EHR System Design Reference Model (EHR SD RM) 10 min Overview of candidate HSSP Services for use in HSSP Practitioners Guide Volume II 10 min Overview of DRAFT Table of Contents for HSSP Practitioners Guide Volume II 13 min Wrap Up 2 min

3 Slide 2 EHR SD RM - EHR Way Forward … Future State Reference Architecture The Practical Guide for SOA in Health Care A real-world approach to planning, designing, and deploying SOA. Version 1.0, December 2008 An informative reference for leaders and decision-makers. Produced by the Healthcare Services Specification Project (HSSP): A collaborative effort between Health Level Seven (HL7) and the Object Management Group. The figure illustrates a macro-view of a SOA. It depicts five overlapping boundaries, each of which represents a context within the business and architecture: The Inter-organisational Boundar y (outermost) represents inter- organisational considerations, such as policies, sharing agreements, and business partners. The System Boundary represents the physical platforms on which software and systems run, including servers, networks, and so on. The Application Boundary represents the software running on those platforms, inclusive of applications and data. The Business Process / Orchestration Boundary manages the intersection between software and workflow, and would manage coordination among multiple software components that all must interact to satisfy business needs. Finally, the Service Implementation Boundary depicts the implementations themselves, interacting across a service bus, and realizing the architecture.

4 Slide 3 EHR SD RM - EHR Way Forward … Future State Reference Architecture The Practical Guide for SOA in Health Care Table 3. SampleHealth Business Function Map Healthcare-Unique ServicesBusiness SvcsSOA Infrastructure Svcs Business Line Order Entry Order Fulfill ment Patient Evaluat ion (DSS) Lab Data Retriev al Pharmacy Data Retrieval EHRAlert/ Event Mgmt Master Person Index Termi nology Service Demo grap hics Billin g Sched uling Auditi ng Service Except ion Mgmt Business Process Mgmt (BPM) Authe nticat ion Serv ices Dire ctor y Access Control PharmacyXXX XXXXXXX XXXX X LaboratoryXXXX XXXXXXXXXXX X Patient Administration XX XX XX XXX Order Entry/MgmtXX XXXXXXXXXXXXX Scheduling XX X XXXXXXX Registration XX XXXXXXX X Care ManagementXXXXXXXXXXXXXXXXXX Referrals/Referral MgmtXXXXXXXXXXXXXXXXXX NursingXXXXXXXXXXXXXXXXXX Emergency DepartmentXXXXXXXXXXXXXX XXX Patient Billing X XXXXXXX XXXX X Imaging/Radiology X XXXXXXXXXXXXX Clinical Decision Support XXXXXXX XX X X Facilities Management X XXX XXX Nutrition Mgmt (Dietetics) XX XXXXXXXXXXXXXXX

5 Slide 4 EHR SD RM - EHR Way Forward … Future State Reference Architecture The Practical Guide for SOA in Health Care

6 Slide 5 EHR SD RM - EHR Way Forward … Future State Reference Architecture Agenda Roll Call and Introductions 3 min Overview Agenda 2 min Overview of HSSP Practitioners Guide Volume I 10 min Services Aware Interoperability Framework (SAIF) 10 min Overview of EHR System Design Reference Model (EHR SD RM) 10 min Overview of candidate HSSP Services for use in HSSP Practitioners Guide Volume II 10 min Overview of DRAFT Table of Contents for HSSP Practitioners Guide Volume II 13 min Wrap Up 2 min

7 Slide 6 EHR SD RM - EHR Way Forward … Future State Reference Architecture The HL7 Services-Aware Interoperability Framework (SAIF) SAIF Contains: Enterprise Conformance and Compliance Framework (ECCF) is based on RM-ODP Behavioral Framework (BF) –Interoperability Scenarios supporting the RM-ODP Computational Viewpoint Governance Framework (GF) –Governance is the overarching policy structure and set of related processes by which a group exercises its authority and demonstrates accountability for accepted responsibilities within a particular jurisdiction. SAIF Principles: Applicable within each of HL7s three Interoperability Paradigms (IPs), –(i.e., messages, documents, and services). Provide support for measurable conformance and compliance. Define appropriate governance structures and processes. Provide support for directly implementable solutions. Address the growing disparity between the various solution sets emerging from HL7. Utilize existing V3/RIM artifacts and expertise to the maximum degree possible.

8 Slide 7 EHR SD RM - EHR Way Forward … Future State Reference Architecture HL7 SAIF Specification Stack Views Conformance and Compliance Framework (ECCF) Consistency Traceable ImplementationBehaviorContentPolicy Topic Specification Enterprise / Business View WHY Information View WHAT Computational View HOW Engineering View WHERE Conceptual Business Context, Reference Context Domain Analysis (Information) Model Collaboration Analysis, Functional Profile(s), Service Roles and Relationships Existing Platform capabilities Platform- Independent Business GovernanceProject-oriented Domain Information Model, Constrained Information Model, Localized Information Model, Hierarchical Message Definition Collaboration Types, Interface Specification and Functional Groups, Interaction Types and Collaboration Participations, Contracts Parts Existing Platform models, libraries, etc. Platform- Specific Rules, ProceduresLocalized Information Model, Transforms, Schema Collaboration scripts, Orchestrations, Realized Interfaces Execution Context, Platform Bindings, Deployment Model

9 Slide 8 EHR SD RM - EHR Way Forward … Future State Reference Architecture HL7 SAIF Responsibilities Conformance and Compliance Framework (ECCF) Consistency Traceable Implementation Where Behavior How Content What Policy Why

10 Slide 9 EHR SD RM - EHR Way Forward … Future State Reference Architecture HITSP Within HL7 SAIF ECCF Specification Stack Topic Specification Enterprise / Business View WHY Information View WHAT Computational View HOW Engineering View WHERE Conceptual Business Context, Reference Context Domain Analysis (Information) Model Collaboration Analysis, Functional Profile(s), Service Roles and Relationships Existing Platform capabilities Platform- Independent Business GovernanceProject-oriented Domain Information Model, Constrained Information Model, Localized Information Model, Hierarchical Message Definition Collaboration Types, Interface Specification and Functional Groups, Interaction Types and Collaboration Participations, Contracts Parts Existing Platform models, libraries, etc. Platform- Specific Rules, ProceduresLocalized Information Model, Transforms, Schema Collaboration scripts, Orchestrations, Realized Interfaces Execution Context, Platform Bindings, Deployment Model Consistency Traceable HITSP DA HITSP CAP Harmonization Requests/ Use Case HITSP CAP HITSP Transaction, Transaction Package and Service Collaboration HITSP Component HITSP IS ImplementationBehavior HITSP Harmonization Framework EHR-S FM is EHR System Functional Model EHR SD RM is EHR System Design Reference Model RIM is Reference Information Model FHIMS is Federal Health Information Model & Standards DA is Data Architecture 9 ContentPolicy

11 Slide 10 EHR SD RM - EHR Way Forward … Future State Reference Architecture HL7, HITSP, FHIMS and NHIN Within HL7 SAIF ECCF Specification Stack Topic Specification Enterprise / Business View WHY Information View WHAT Computational View HOW Engineering View WHERE Conceptual Business Context, Reference Context Domain Analysis (Information) Model Collaboration Analysis, Functional Profile(s), Service Roles and Relationships Existing Platform capabilities Platform- Independent Business GovernanceProject-oriented Domain Information Model, Constrained Information Model, Localized Information Model, Hierarchical Message Definition Collaboration Types, Interface Specification and Functional Groups, Interaction Types and Collaboration Participations, Contracts Parts Existing Platform models, libraries, etc. Platform- Specific Rules, ProceduresLocalized Information Model, Transforms, Schema Collaboration scripts, Orchestrations, Realized Interfaces Execution Context, Platform Bindings, Deployment Model Consistency Traceable HL7 RIM FHA FHIMS HITSP DA HITSP CAP Harmonization Requests/ Use Case HITSP Capability HITSP Transaction, Transaction Package and Service Collaboration HITSP Component HL7 EHR-S FM HITSP Harmonization Framework HL7 EHR SD RM HITSP IS EHR-S FM is EHR System Functional Model EHR SD RM is EHR System Design Reference Model RIM is Reference Information Model FHIMS is Federal Health Information Model & Standards DA is Data Architecture NHIN Connect Services Tomcat, JBoss, J2SE, Eclipse, GlassFish ESB, OpenSSO 10 ImplementationBehaviorContentPolicy

12 Slide 11 EHR SD RM - EHR Way Forward … Future State Reference Architecture Agenda Roll Call and Introductions 3 min Overview Agenda 2 min Overview of HSSP Practitioners Guide Volume I 10 min Overview of Services Aware Interoperability Framework (SAIF) 10 min EHR System Design Reference Model (EHR SD RM) 10 min Overview of candidate HSSP Services for use in HSSP Practitioners Guide Volume II 10 min Overview of DRAFT Table of Contents for HSSP Practitioners Guide Volume II 13 min Wrap Up 2 min

13 Slide 12 EHR SD RM - EHR Way Forward … Future State Reference Architecture Federal Enterprise Architecture (FEA) Performance Reference Model - The FEA PRM is a framework to measure the performance of major IT initiatives and their contribution to program performance. The PRM leverages performance measurement best practices from the public and private sectors, including the Balanced Scorecard, Baldrige Criteria, Value Measurement Methodology, program logic models, the value chain, and the theory of constraints. There is an increased emphasis placed on linkage of investment to agency program performance and the PRM will help agencies produce enhanced performance information. Furthermore, the PRM will assist in: improving the alignment of program goals and objectives with Mission Area goals and objectives; improving communication of program contributions such as technology (input) to outputs and outcomes; and in identifying improvement opportunities that span traditional organizational boundaries. Performance Reference Model Business Reference Model - The Business Reference Model (BRM) is a functional-driven framework for describing and organizing the day-to-day business operations of the Federal Government into Lines of Business (LOBs), independent of the agencies that perform the business operation. The BRM is the first layer of the Federal Enterprise Architecture and it is the organizing construct for the analysis of the other four reference models: performance, service components, data, and technology. Business Reference Model Service Component Reference Model - The Service Component Reference Model (SRM) is a functional framework to evaluate to identify government-wide opportunities to leverage IT investments and assets from a service perspective. This model helps understand the services delivered by the government and assess if there is an opportunity to group like services and create leverage opportunities, such as reuse or shared services. Service Component Reference Model Data Reference Model - The Data Reference Model (DRM) describes at an aggregate level, the data and information required to support the Lines of Business (LOBs). The three elements of data exchange that have been standardized include data description, data context, and data sharing. Establishing a common data model streamlines the information exchange process within and across the Federal Government and facilitates the ability to identify duplicative data resources. Data Reference Model Technical Reference Model - The Technical Reference Model (TRM) establishes a common technical framework for categorizing standards, specifications, and technologies that support and enable the delivery of services. This framework can be leveraged to support the development, delivery, and exchange of business and application components (Service Components) that may be leveraged in a Component-based or Service Oriented Architecture (SOA). Furthermore, it also serves as the foundation to advance the re-use of technology and best practices from each of the Service Components on a government-wide basis. Technical Reference ModelService Oriented Architecture

14 Slide 13 EHR SD RM - EHR Way Forward … Future State Reference Architecture Functional Analysis Object Analysis Requirements Analysis Interface Design Analysis Service Analysis EHR Future State Reference Architecture

15 Slide 14 EHR SD RM - EHR Way Forward … Future State Reference Architecture HL7 EHR System Functional Model (EHR-S) > 160 System Functions in 4 level categorization (separate spreadsheet available for full enumeration) NOTE : Other Category - The EHR-S model does NOT include Electronic Resource Planning (ERP) / Logistics and Financial components, which are needed for completeness of a Health IT Enterprise. Other O-1 Electronic Resource Planning (ERP) O-2 Finances O-3 Other System Functions EHR-S FM functions can be grouped into Service Components … aka Capabilities (e.g., Lab Order Capability, which does eligibility and authorization function as well as lab order function).

16 Slide 15 EHR SD RM - EHR Way Forward … Future State Reference Architecture Healthcare SOA Framework Based on HL7 EHR System Functional Model & Thomas Erls SOA Layers HL7 System Functions Direct CareSupportiveInformation Infrastructure Other Business Process Value Chains Composite Services Federated Composition (e.g., Choreograph or Orchestration) Within and Across Business Areas Core Business Services Functional Areas + Focal Classes Functional Areas + Focal Classes Functional Areas + Focal Classes Functional Areas + Focal Classes Entity Services Information Management Information Management Information Management Information Reporting and Management Agnostic Services C r o s s T e c h n I c a l Common S e r v I c e s (e.g., Security, Privacy, Auditing, Logging…) Application Services Ambulatory Care Systems, In Patient Care Systems Logistics Systems Financial Systems Decision Support Systems Data Marts Repositories Business Objects Implementation Profiles Integrated Healthcare Enterprise (IHE) Profiles Analysis ProfilesCommunications Profiles/Stacks Implementation Profiles 15

17 Slide 16 EHR SD RM - EHR Way Forward … Future State Reference Architecture HL7 RIM (Reference Information Model) Six Core Classes Defining a Semantic Framework which Maintains Clinical Data Context The HL7 RIM expresses the data content needed in a specific clinical or administrative context and provides an explicit representation of the semantic and lexical connections that exist between the information carried in the fields of HL7 messages. Role link Act relationship Participation The HL7 RIM supports EHR interoperability; an EHR may needs additional foundation classes (e.g., Responsibility) Language / communication ACT (aka ACTION) ROLEENTITY ACT – something that has happened or may happen Entity – a person, animal, organization, or thing Role – a responsibility of, or part played by, an Entity Participation – the involvement of a Role in an Act Act Relationship – a relationship between two Acts Role Link – a relationship between two Roles.

18 Slide 17 EHR SD RM - EHR Way Forward … Future State Reference Architecture HITSP Harmonization Framework IS Capability Service Collaboration Transaction, Transaction Package Components Addressing Business Needs Providing Infrastructure, Security, Privacy Data Architecture Available for Independent Implementation Defining Information Content IS = Interoperability Specification Base and Composite Standards

19 Slide 18 EHR SD RM - EHR Way Forward … Future State Reference Architecture Agenda Roll Call and Introductions 3 min Overview Agenda 2 min Overview of HSSP Practitioners Guide Volume I 10 min Overview of Services Aware Interoperability Framework (SAIF) 10 min Overview of EHR System Design Reference Model (EHR SD RM) 10 min Candidate HSSP Services for use in HSSP Practitioners Guide Volume II Overview of DRAFT Table of Contents for HSSP Practitioners Guide Volume II 13 min Wrap Up 2 min

20 Slide 19 EHR SD RM - EHR Way Forward … Future State Reference Architecture Candidate HSSP Services for use in HSSP Practitioners Guide Volume II CTS2 (Common Terminology Services 2) CTS 2 will be a commonly accepted standard for terminology services that enhances the capabilities of the initial CTS specification for sub-setting and mapping, and extends the specification into domains such as terminology distribution, versioning, and classification. CTS2 (Common Terminology Services 2) DSS (Decision Support Service) A commonly accepted standard for the DSS would make it more attractive for service consumers to invest in the infrastructure required for using the DSS to meet its patient evaluation needs, as they would be able to use the same interface to interact with multiple service vendors. DSS (Decision Support Service) HCPDS (Healthcare Provider and Services Directory Service) HCPDS is required to provide an online facility that will enable Practitioners, via a set of parameters, to locate other practitioners, to assist in the continuum of care. HCPDS (Healthcare Provider and Services Directory Service) IXS (Identity Cross-Reference Service, formerly known as Entity Identification Service) Normative In balloting to become a full HL7 standard. IXS (Identity Cross-Reference Service, formerly known as Entity Identification Service) Normative PASS (Privacy, Access and Security Services) The goal of PASS is to define a suite of services that will provide a simple interface for all privacy, access control, consent, identity management and other security services that are needed in a service-oriented health information architecture. PASS (Privacy, Access and Security Services) RLUS (Retrieve, Locate and Update Service) and EIS (Entity Identification Service) The HL7 SFM has been approved by the HL7 Board as an official DSTU. RLUS (Retrieve, Locate and Update Service) and EIS (Entity Identification Service)

21 Slide 20 EHR SD RM - EHR Way Forward … Future State Reference Architecture Agenda Roll Call and Introductions 3 min Overview Agenda 2 min Overview of HSSP Practitioners Guide Volume I 10 min Overview of Services Aware Interoperability Framework (SAIF) 10 min Overview of EHR System Design Reference Model (EHR SD RM) 10 min Overview of candidate HSSP Services for use in HSSP Practitioners Guide Volume II 10 min DRAFT Table of Contents for HSSP Practitioners Guide Volume II Wrap Up 2 min

22 Slide 21 EHR SD RM - EHR Way Forward … Future State Reference Architecture DRAFT Table of Contents for HSSP Practitioners Guide Volume II See HSSP Practitioners Guide Volume II May 2010 – DRAFT-A.Docx –Note that the version will change each week … A, B, C D, … till HL7 Rio Versions available at –Weekly Agenda/Minutes –Weekly Read Ahead Slides –Weekly updated HSSP Practitioners Guide Volume II May 2010 DRAFT-A.Docx

23 Slide 22 EHR SD RM - EHR Way Forward … Future State Reference Architecture We are inviting all interested to participate in the 11th International HL7 Interoperability Conference (IHIC-2010), to be held in Rio de Janeiro, Brazil on May This time will be the first for IHIC in South America. Following the success of previous IHIC venues in Kyoto(2009), Crete (2008), New Zealand (2007), Germany (2006), Taiwan (2005), Mexico (2004), IHIC2010 aims to serve as a meeting place for more than 30 HL7 affiliates around the world as well as individuals interested in interoperability and standards, to share their HL7 implementation experience and strengthen their shared vision. The paper submissions are invited to show to the international community successful experiences using HL7 V3 and CDA R2 interoperability between informatics applications using standards. Also, results and experiences from the collaborative use of standards are most welcome, especially if they are related to HL7 standards. Topics of interest include but are not limited to the following: HL7 implementation experience from regional, trans-regional, or national implementation: HL7 v2.x and 3.0 messages Clinical Document Architecture (CDA) Imaging Diagnostics and DICOM Standard Use of HL7 in IHE profiles Terminologies, Ontologies and Coding Systems: use of local and international standards Use of other standards in combination with HL7 standards: ASTM, ISO, CEN, etc. Business Models, regional & large scale deployment: Electronic Healthcare Record: from strategy to implementation Legal and regulatory issues. Epidemiology, disease surveillance and control Geographical information systems for population health Disaster medicine, emergency management and public health This year, along with the successful Show me your CDA! track, IHIC will also incorporate the "Send me your CDA!" HL7 CDA Interoperability Showcase to display basic interoperability of applications using a HL7 V3 and HL7 CDA R2 standards. All submitted papers will be reviewed based on their technical quality and merit by the technical committee and reviewers. Papers that describe research and experimentation are encouraged. All paper submissions will be handled electronically using IEEE format, and detailed instructions on submission procedure will be available on IHIC2010 web pages (http://www.ihic2010.hl7.org.ar/). Accepted papers will be published online. For other information, please contact IHIC2010, Important Dates: Call For papers : November 2, 2009 Deadline for submissions extended to February 15, 2010 Evaluation and notification, March 15, 2010 Camera-papers ready due : April 15, 2010 Call for Participation – HL7 in Rio

24 Slide 23 EHR SD RM - EHR Way Forward … Future State Reference Architecture Agenda Roll Call and Introductions 3 min Overview Agenda 2 min Overview of HSSP Practitioners Guide Volume I 10 min Overview of Services Aware Interoperability Framework (SAIF) 10 min Overview of EHR System Design Reference Model (EHR SD RM) 10 min Overview of candidate HSSP Services for use in HSSP Practitioners Guide Volume II 10 min Overview of DRAFT Table of Contents for HSSP Practitioners Guide Volume II 13 min Wrap Up 2 min

25 Slide 24 EHR SD RM - EHR Way Forward … Future State Reference Architecture Wrap Up Any new attendees? Agenda Time Metrics Volunteers to help prepare for next weeks meeting? –Do we need one-on-one working meetings? Suggestions for Improvement Next Meeting March 26, 2010 at 12:30 Eastern Time –PHONE: Pass code # –WEB:


Download ppt "Slide 0 EHR SD RM - EHR Way Forward … Future State Reference Architecture HSSP Practitioners Guide Volume II Immunization and Adverse Event Reporting Prototype."

Similar presentations


Ads by Google