Presentation is loading. Please wait.

Presentation is loading. Please wait.

0 Harmonization Process, Work Plan, and Schedule Chicago IL. March 5, 2007 HITSP Project 2007 Work Plan and Schedule Contract HHSP23320054103EC.

Similar presentations


Presentation on theme: "0 Harmonization Process, Work Plan, and Schedule Chicago IL. March 5, 2007 HITSP Project 2007 Work Plan and Schedule Contract HHSP23320054103EC."— Presentation transcript:

1 0 Harmonization Process, Work Plan, and Schedule Chicago IL. March 5, 2007 HITSP Project 2007 Work Plan and Schedule Contract HHSP23320054103EC

2 1 Harmonization Process, Work Plan, and Schedule 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

3 2 Harmonization Process, Work Plan, and Schedule Standards Harmonization Work Plan Tasks I Harmonization Request II Requirements Analysis III Identification of Candidate Standards IV Gaps, Duplications and Overlaps Resolution V Standards Selection VI Construction of Interoperability Specification VII Inspection Test VIII Interoperability Specification Release and Dissemination IX Program Management 3 months 3 weeks 3 months4 weeks 2 months Work Plan and Schedule Overview 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 Annual Updates as Required PROCESS TASKS DOCUMENTATION

4 3 Harmonization Process, Work Plan, and Schedule 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 Work Plan and Schedule Overview

5 4 Harmonization Process, Work Plan, and Schedule JANFEBMARAPRMAYJUNJULAUGSEPOCTNOVDEC HITSP 2007 Timeline 02/05/07 HITSP Board 04/23/07 HITSP Board 07/09/07 HITSP Board 10/09/07 HITSP Board 03/19/07 HITSP Panel 05/11/07 HITSP Panel 09/07/07 HITSP Panel 03/06 – 03/08 TC Face to Face Chicago IL 5/08 – 5/10 TC Face to Face Arlington VA 6/18 – 6/20 TC Face to Face San Diego CA 09/04 – 09/06 TC Face to Face Arlington VA Requirements, Standards Selection, and Design Public InputInspect 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/1608/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/07 HITSP Panel 07/16/07 HITSP Panel 02/12/07 HITSP Panel Activity 4 –New Use Cases from AHIC Detail Schedule to be Established Upon Review of the Use Cases Work Plan and Schedule Overview S&P and EHR-ER v 1.0, EHR, CE, and BIO v M.m

6 5 Harmonization Process, Work Plan, and Schedule Version 2.0 of Existing EHR, BIO, CE ISs Release 2.0 Detailed Schedule ActivityDate 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.0March 19 TC Construct Updates (with on-going correction request disposition and Panel input) March 9 – April 20 Project Team Editorial Review, Audit, and PublicationApril 23 – April 27 Release Summary of Updates 10 days in advance of Panel meetingApril 27 May 11 Panel Meeting to approve minor updates to CE, BIO, and EHR version 2.0 May 11

7 6 Harmonization Process, Work Plan, and Schedule Key Points about the Release 2.0 Schedule  The TC have until April 20 th 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 27 th for approval May 11 th. Release 2.0 Detailed Schedule

8 7 Harmonization Process, Work Plan, and Schedule 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. Release 2.0 Detailed Schedule

9 8 Harmonization Process, Work Plan, and Schedule Implementation Testing Results for Release 2.0 IHE ProfileHITSP Document ACEPACUO ALER T ALLS CRIPT S CAPM ED CAQH ECLIP SYS GEHXTIIBM INITIA TE MIE NEXT GEN U. WA TOTAL NA ISBIO-02 Biosurveillance Interoperability Specification 1 0 78 16 NA ISCE-03 Consumer Empowerment Interoperability Specification 1 5 10 6 XDSISTP-13 Manage Sharing of Documents1 0 11121 13 PIXIST-22 Patient ID Cross Referencing2 22 18110 17 PDQIST-23 Patient Demographics Query1 231 6 NAIST-24 Biosurveillance Pseudonymize1 01 1 NAIST-25 Anonymize Transaction0 2 2 XD-LabISC-37 Lab Report Document1 6 7 NAISC-39 Encounter Message 0 NAISC-47 Resource Utilization Message4 00 4 XDS-MSISC-48 Encounter Document30 35 11 XDS-IISTP-49 Radiology Report Document2 40 4 RFDISTP-50 Retrieve Form for Data Capture402 6 General Feedback22211 8 Total43012055002911 813101 Release 2.0 Detailed Schedule

10 9 Harmonization Process, Work Plan, and Schedule Version 1.0 of the Security and Privacy Constructs and Emergency Responder EHR IS ActivityDate Requirements and DesignNow – 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 progressMarch 19 TC approves RSSDApril 6 Project Team Editorial Review and PublicationApril 9 - 12 Public and Panel Review and Input on the RSSDApril 13 – May 3 TCs Construct Development and Comment DispositionApril 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 developmentJune 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

11 10 Harmonization Process, Work Plan, and Schedule ActivityDate Inspection Test and Public CommentJuly 20 – August 16 Comment Resolution and Re-publicationAugust 17 – October 8 TC Disposition Comments and Update DocumentsAugust 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 resolutionSeptember 7 Project Team Editorial Review, Audit, and Re-publicationSeptember 24 – October 5 Release 5 days in advance of Panel meetingOctober 8 October 15 Panel Meeting to Approve ISsOctober 15 Version 1.0 of the Security and Privacy Constructs and Emergency Responder EHR IS ER-EHR and S&P Detailed Schedule

12 11 Harmonization Process, Work Plan, and Schedule Key Points about the Emergency Responder EHR and Security and Privacy Schedule  The TC have until April 6 th 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 13 th to May 3 rd –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 21 st to disposition comment and republish the ISs for Panel approval by October 15 th ER-EHR and S&P Detailed Schedule


Download ppt "0 Harmonization Process, Work Plan, and Schedule Chicago IL. March 5, 2007 HITSP Project 2007 Work Plan and Schedule Contract HHSP23320054103EC."

Similar presentations


Ads by Google