0 harmonization process, work plan, and schedule chicago il. march 5, 2007 hitsp project 2007 work...

1Harmonization Process, Work Plan, and Schedule

Chicago IL. March 5, 2007

HITSP Project 2007 Work Plan and Schedule

Contract HHSP23320054103EC


Agenda

Work Plan and Schedule Overview

Release 2.0 Detail Schedule– Key Points

– Implementation Testing

Emergency Responder EHR and Security and Privacy Detail Schedule – Key Points


Standards Harmonization Work Plan Tasks

I

Harmonization Request

II

RequirementsAnalysis

III

Identificationof Candidate

Standards

IV

Gaps,Duplications

and Overlaps

Resolution

V

Standards Selection

VI

Constructionof

InteroperabilitySpecification

VII

InspectionTest

VIII

InteroperabilitySpecification

Releaseand

Dissemination

IXProgram Management

3 months

3 weeks

3 months 4 weeks 2 months


On-going

Requirements, Standards Selection, and Design

Public and Panel Review

and Input

Inspection Test, Public and Panel Comment

Implementation Support and

Testing

Comment Resolution and Panel Approval

Interoperability Specification Construct

Development

IS Docs V 1.0

Review Draft

Summary of comment resolution

IS Docs V 1.0

Summary of comment resolution

Requirements, Standards

Selection, and Design

Consolidated comments

Consolidated comments

Annual Updates as Required

PROCESS

TASKS

DOCUMENTATION


Key Activities and Milestones

Activity 1: Version 2.0 of Existing Use Cases– Minor updates to CE, BIO, and EHR based on implementation and other TC activities; includes

minor technical updates to CE ISC-32 for CCD

– Scheduled for release May 11, 2007

Activity 2: Ongoing work for Existing Use Cases (e.g. Security and Privacy)– Security and Privacy Work Group updates; along with other ongoing updates to CE, BIO, EHR

– Scheduled for release October 15, 2007

Activity 3: Emergency Responder EHR Use Case– New Emergency Responder EHR IS

– Scheduled for release October 15, 2007

Activity 4: New Use Cases Expected in March 2007– Detailed schedule to be determined upon review of use cases



JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC

HITSP 2007 Timeline

02/05/07HITSP Board

04/23/07HITSP Board

07/09/07HITSP Board

10/09/07HITSP Board

03/19/07HITSP Panel

05/11/07HITSP Panel

09/07/07HITSP Panel

03/06 – 03/08TC Face to Face

Chicago IL


Arlington VA


San Diego CA


Arlington VA

Requirements, Standards Selection, and Design

Public Input Inspect Test and Public Comment

Implementation Support and Testing

(with annual updates as required)

Comment Resolution and Panel Approval

01/19 – 04/12

04/13 – 05/03

IS Construct Development

04/13 – 07/19 07/20 – 08/16 08/17 – 10/15

Implementation Support and Testing(includes minor document updates)

EHR, CE and BIO v 2.0

Activity 1 – Version 2.0 of Existing EHR, CE, BIO ISs

Activity 2 – On-going Work for Existing EHR, CE, BIO ISs (e.g. Security and Privacy) Activity 3 – New Emergency Responder EHR Use Case

On-going Support

10/15/07HITSP Panel

07/16/07HITSP Panel

02/12/07HITSP Panel

Activity 4 –New Use Cases from AHIC

Detail Schedule to be Established Upon Review of the Use Cases


S&P and EHR-ER v 1.0, EHR, CE, and BIO v M.m


Version 2.0 of Existing EHR, BIO, CE ISs

Release 2.0 Detailed Schedule

Activity Date

Implementation Testing (via Connectathon and other activities) Now - April

TC Face to Face in Chicago to start to disposition correction requests

March 6 – 8

March 19 Panel Meeting to review progress on version 2.0 March 19

TC Construct Updates (with on-going correction request disposition and Panel input)

March 9 – April 20

Project Team Editorial Review, Audit, and Publication April 23 – April 27

Release Summary of Updates 10 days in advance of Panel meeting April 27

May 11 Panel Meeting to approve minor updates to CE, BIO, and EHR version 2.0

May 11


Key Points about the Release 2.0 Schedule

The TC have until April 20th to finalize Release 2.0. Prior to April 20th you need to…..

– Review and disposition any comments resulting from Implementation Testing. Determine what changes need to be made to the IS document based on comments and based on your 2007 SOWs

– Make the changes to the working version of the IS documents using TRACK changes (see Bob Yencha for location of the working version of these documents)

– Document a summary of the release 2.0 changes as the last section of each document (see Bob Yencha for an example of a change summary section and the appropriate level of detail).

– Coordinate changes to all XTC documents through Bob Yencha

There is NO formal comment period for release 2.0, therefore it is CRITICAL that each TC set up a schedule of meetings where members of the Panel can participate in the review and finalization of the release 2.0 changes.

Once you hand over the updated IS documents to the Project Team, we will conduct an editorial review and an audit of the changes against the comments. We will release to the Panel on April 27th for approval May 11th.



Implementation Testing for Release 2.0

The HITSP team leveraged the IHE Connectathon to identify vendors to support implementation testing of the existing HITSP interoperability specifications

– Prior to the IHE Connectathon, the HITSP/NIST team identified 14 vendors that were demonstrating the IHE profiles as part of the HIMSS Interoperability Showcase in February 2007.

– These vendors agreed to sign up as “HITSP vendors” to support the implementation testing of the IS documents associated with the relevant IHE profiles

Following the Connectathon, the HITSP worked with the vendors to gather their feedback

– The HITSP team provided each vendor with the HITSP IS documents relevant to their applications and requested from the vendors relevant documents, messages, acknowledgements and/or logs.

– Vendors were also asked to participate in facilitated feedback sessions led by Lori Reed-Fourquet from the HITSP Project Team.

As of March 2, 2007, 10 HITSP Connectathon vendors have provided feedback. In addition, one NHIN vendor has provided feedback and two other NHIN vendors have agreed to provide feedback in the near future.



Implementation Testing Results for Release 2.0

IHE Profile HITSP Document ACEP ACUOALER

T

ALLSCRIPT

S

CAPMED

CAQHECLIPSYS

GE HXTI IBMINITIA

TEMIE

NEXTGEN

U. WA TOTAL

NA ISBIO-02 Biosurveillance Interoperability Specification 1 0 7 8 16

NA ISCE-03 Consumer Empowerment Interoperability Specification 1 5 1 0 6

XDS ISTP-13 Manage Sharing of Documents 1 0 11 1 2 1 13

PIX IST-22 Patient ID Cross Referencing 2 2 2 1 8 1 1 0 17

PDQ IST-23 Patient Demographics Query 1 2 3 1 6

NA IST-24 Biosurveillance Pseudonymize 1 0 1 1

NA IST-25 Anonymize Transaction 0 2 2

XD-Lab ISC-37 Lab Report Document 1 6 7

NA ISC-39 Encounter Message 0

NA ISC-47 Resource Utilization Message 4 0 0 4

XDS-MS ISC-48 Encounter Document 3 0 3 5 11

XDS-I ISTP-49 Radiology Report Document 2 4 0 4

RFD ISTP-50 Retrieve Form for Data Capture 4 0 2 6

General Feedback 2 2 2 1 1 8

Total 4 3 0 12 0 5 5 0 0 29 11 11 8 13 101



Version 1.0 of the Security and Privacy Constructs and Emergency Responder EHR IS

Activity Date

Requirements and Design Now – April 12

TC Face to Face in Chicago to document Requirements, Standards Selection, and Design (RSSD)

March 6 – 8

March 19 Panel Meeting to review progress March 19

TC approves RSSD April 6

Project Team Editorial Review and Publication April 9 - 12

Public and Panel Review and Input on the RSSD April 13 – May 3

TCs Construct Development and Comment Disposition April 13 – July 19

TC Face to Face in Arlington to triage comments and continue IS development

May 8 - 10

May 11 Panel Meeting to review summary of comments received and status of IS development

May 11

TC Face to Face in San Diego to continue IS development June 18 - 20

July 16 Panel Meeting to review summary of comment disposition and draft IS docs

July 16

Continued on next page…

ER-EHR and S&P Detailed Schedule


Activity Date

Inspection Test and Public Comment July 20 – August 16

Comment Resolution and Re-publication August 17 – October 8

TC Disposition Comments and Update Documents August 17 – September 21

TC Face to Face in Arlington to complete comment resolution and update documents

September 4 - 6

September 7 Panel Meeting to review progress of comment resolution

September 7

Project Team Editorial Review, Audit, and Re-publication September 24 – October 5

Release 5 days in advance of Panel meeting October 8

October 15 Panel Meeting to Approve ISs October 15

Version 1.0 of the Security and Privacy Constructs and Emergency Responder EHR IS



Key Points about the Emergency Responder EHR and Security and Privacy Schedule

The TC have until April 6th to finalize the Requirements, Standards Selection and Design (RSSD) Document

– Please see Sarah Quaynor if you have any questions or comments on the RSSD template

Once you hand over the RSSD to the Project Team, we will conduct an editorial review and release for a public review and input period from April 13th to May 3rd

– The comments on the RSSD will feed into the Interoperability Specification

– You DO need to disposition all comment on the RSSD and document the dispositions but you DO NOT need to republish the RSSD

– So….after you hand over the RSSD, you may start working on the Interoperability Specifications – you do not need to wait!

The TCs will then have until mid-July to produce the Interoperability Specifications

The ISs will go through a 4 week period of inspection test and public comment

The TCS will then have from August 17 to September 21st to disposition comment and republish the ISs for Panel approval by October 15th
