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

1

Glen F. Marshall, Glen F. Marshall, Co Co-

• chair, IHE IT Infrastructure Planning

chair, IHE IT Infrastructure Planning

IHE: A Proven Process IHE: A Proven Process for HL7 Standards for HL7 Standards Implementation Implementation

2

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 implementations for specific use-

• cases.

cases. This This presentation will focus on: presentation will focus on:

• 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

3

Standards Development View Standards Development View

Use Use Cases Cases Refine Refine Scoping Scoping Criteria Criteria Scoped Scoped Use Use Cases Cases Abstract Abstract Domain Domain Models Models Abstracted Abstracted Use Use 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.

4

Standards Development View Standards Development View

Abstracted Abstracted Use Use Cases Cases Define Define Solution Solution

Knowledge Knowledge

Solved Solved Use Use Cases Cases Author Author Publishing Publishing Criteria Criteria Standard Standard 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. Balloting Balloting

5

Profile Development View Profile Development View

Use Use Cases Cases Refine Refine Scoping Scoping Criteria Criteria Essential Essential Use Use Cases Cases Realize Realize Usage Usage Scenarios Scenarios Use Use Case Case Scenarios 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 Realization identifies use case scenarios – – actors actors and transactions within clinical workflows. and transactions within clinical workflows.

6

Profile Development View Profile Development View

Use Use Case Case Scenarios Scenarios Define Define Solution Solution

Standards Standards

Solved Solved Use Use Cases Cases Author Author Publishing Publishing Criteria Criteria Profile Profile 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 Profile authorship yields documents -

• solutions in detail.

solutions in detail. Balloting gains refinement and consensus. Balloting gains refinement and consensus. Balloting Balloting

7

Comparison Comparison

Standards

Are problem-based

Solve classes of use

cases

Exist within a domain

knowledge constraint

Provide options to be

applied for specific solution implementations

Are collaborative Reference other standards

Profiles

Are standards-based

Solve specific usage

scenarios

May draw from many

domains’ knowledge

Specify choices among the

• ptions for specific solution

implementations

Are collaborative Reference other profiles

8

Technical Requirements View Technical Requirements View

Business Business Problem Problem Define Define Solution Solution Profile Profile Solution Solution Proposal Proposal Author Author Business Business Rules Rules RFP RFP 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 Vendors can respond to such well-

• defined integration

defined integration requirements via requirements via IHE Integration Statements IHE Integration Statements

9

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.)

10

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

11

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.

12

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

13

Where are HL7 Standards? Where are HL7 Standards?

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

14

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

15

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

16

IHE Web site: IHE Web site: www.IHE .net www.IHE .net

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

17