IHE: A Proven Process IHE: A Proven Process for HL7 Standards for - PowerPoint PPT Presentation

IHE: A Proven Process IHE: A Proven Process for HL7 Standards for HL7 Standards Implementation Implementation Glen F. Marshall, Glen F. Marshall, Co- -chair, IHE IT Infrastructure Planning chair, IHE IT Infrastructure Planning Co 1

What This Talk Is About What This Talk Is About The IHE methodology specifies, tests, and The IHE methodology specifies, tests, and verifies interoperable standards verifies interoperable standards implementations for specific use- -cases. cases. implementations for specific use This presentation will focus on: presentation will focus on: This � HL7 standards implemented by � HL7 standards implemented by IHE IHE � How they have been used in the HIMSS 2006 � How they have been used in the HIMSS 2006 Interoperability Showcase Interoperability Showcase � IHE plans for new profiles that incorporate HL7 � IHE plans for new profiles that incorporate HL7 Standards Standards 2

Standards Development View Standards Development View Scoping Domain Scoping Domain Criteria Models Criteria Models Scoped Abstracted Scoped Abstracted Use Use Refine Use Abstract Use Refine Use Abstract Use Cases Cases Cases Cases Cases Cases Standardization begins with use cases. Standardization begins with use cases. Refinement scopes the use cases. Refinement scopes the use cases. Abstraction identifies common use case elements. Abstraction identifies common use case elements. 3

Standards Development View Standards Development View Publishing Publishing Knowledge Knowledge Criteria Criteria Solved Abstracted Solved Abstracted Define Define Use Author Standard Use Use Author Standard Use Solution Solution Cases Cases Cases Cases Balloting Balloting Knowledge defines solutions to abstract use cases. Knowledge defines solutions to abstract use cases. Standards authorship documents repeatable solutions. Standards authorship documents repeatable solutions. Balloting gains refinement and consensus. Balloting gains refinement and consensus. 4

Profile Development View Profile Development View Scoping Usage Scoping Usage Criteria Scenarios Criteria Scenarios Essential Use Essential Use Use Use Refine Use Realize Case Refine Use Realize Case Cases Cases Cases Scenarios Cases Scenarios Profiling begin with use cases. Profiling begin with use cases. Refinement identifies essential use case elements. Refinement identifies essential use case elements. Realization identifies use case scenarios – – actors actors Realization identifies use case scenarios and transactions within clinical workflows. and transactions within clinical workflows. 5

Profile Development View Profile Development View Publishing Publishing Standards Standards Criteria Criteria Solved Use Solved Use Define Define Use Author Profile Case Use Author Profile Case Solution Solution Cases Scenarios Cases Scenarios Balloting Balloting Standards provide solutions to use case scenarios and Standards provide solutions to use case scenarios and help identify the need for additional elements to fill gaps help identify the need for additional elements to fill gaps Profile authorship yields documents - - solutions in detail. solutions in detail. Profile authorship yields documents Balloting gains refinement and consensus. Balloting gains refinement and consensus. 6

Comparison Comparison Standards Profiles � Are problem-based � Are standards-based � Solve classes of use � Solve specific usage cases scenarios � Exist within a domain � May draw from many knowledge constraint domains’ knowledge � Provide options to be � Specify choices among the applied for specific options for specific solution solution implementations implementations � Are collaborative � Are collaborative � Reference other standards � Reference other profiles 7

Technical Requirements View Technical Requirements View Business Business Profile Profile Rules Rules Define Solution Business Define Solution Business Author RFP Author RFP Solution Proposal Problem Solution Proposal Problem Profiles inform solution definitions and proposals Profiles inform solution definitions and proposals Authorship converts solution proposals to RFPs. Authorship converts solution proposals to RFPs. Vendors can respond to such well- -defined integration defined integration Vendors can respond to such well requirements via IHE Integration Statements IHE Integration Statements requirements via 8

IHE Integration Statements IHE Integration Statements Documents published by vendors to describe the conformance of their products with the IHE profiles: Contents: � Vendor Name � Product Name and version � Publication date and revision designation � List of IHE integration profiles, actors, and options supported � Reference information, e.g., URLs, for verification. The referenced IHE profiles document the details (and avoid meaningless “boilerplate” responses.) 9

IHE Adoption IHE Adoption VA/DoD � Requires IHE Conformance in RFPs ONC NHIN Award – IBM � Implements IHE profiles for prototype Canada � CHI Requires IHE Conformance for Radiology Italy � Live implementation of XDS in Padua region France � Live implementation of XDS in summer ’06 … and more to come this year 10

What IHE Does With HL7 What IHE Does With HL7 IHE draws upon HL7’s standards. IHE solves specific use scenarios. IHE makes choices among options. IHE seeks consensus among stakeholders that profiles are complete and correct. IHE tests profiles in Connectathons. IHE references many standards in addition to HL7: DICOM, IETF, W3, OASIS, etc. 11

What HL7 Standards? What HL7 Standards? HL7 v2 � Latest version for new profiles � 2.3.1 for some legacy cases HL7 CDA � Structured clinical documents � Metadata wrapper for non-structured documents HL7 CCOW � User Context � Patient Context 12

Where are HL7 Standards? Where are HL7 Standards? Profiles HL7 v2 CDA CCOW Non-HL7 XDS X OASIS XDS-MS X OASIS RID X IETF PIX X PDQ X Radiology X DICOM PSA Patient EUA User Kerberos PAM X 13

What Does IHE Plan Next? What Does IHE Plan Next? IT Infrastructure � Cross-Enterprise Document Interchange � Scanned Documents � PIX and PDQ - HL7 v3 Transactions � XDS Stored Query � Request Form for Display � Cross-Enterprise User Authentication � White Papers: • XDS Federation for RHIO-to-RHIO document sharing • Security Risk Evaluation and Management New XDS Document Content Profiles � CDA for persistent clinical documents � CDA wrappers for unstructured documents � CCD, when HL7+ASTM collaboration work is complete 14

What about HL7 v3? What about HL7 v3? HL7 CDA is based on v3 � XDS in the Interoperability Showcase now � XDS-MS uses CDA/CRS Revision of PIX and PDQ � Authored by IHE Canada to meet their needs Roadmap for the future � V3 equivalents to existing v2 transactions � Novel uses cases that v2 does not address 15

IHE Web site: www.IHE .net www.IHE .net IHE Web site: Frequently Asked Questions Frequently Asked Questions Integration Profiles in Technical Frameworks: Integration Profiles in Technical Frameworks: � Cardiology � Cardiology � IT Infrastructure � IT Infrastructure � Laboratory � Laboratory � Patient Care Coordination � Patient Care Coordination � Radiology � Radiology Connectathon Results Connectathon Results Vendor Products Integration Statements Vendor Products Integration Statements Participation in Committees & Connectathons Participation in Committees & Connectathons 16

17