120 likes | 232 Views
HITSP Project 2007 Work Plan and Schedule Contract HHSP23320054103EC. Chicago IL. March 5, 2007. 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.
E N D
HITSP Project 2007 Work Plan and Schedule Contract HHSP23320054103EC Chicago IL. March 5, 2007
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
Work Plan and Schedule Overview Standards Harmonization Work Plan Tasks PROCESS I Harmonization Request II RequirementsAnalysis III Identificationof CandidateStandards IV Gaps,Duplicationsand Overlaps Resolution V Standards Selection VI ConstructionofInteroperabilitySpecification VII InspectionTest VIIIInteroperabilitySpecificationReleaseandDissemination IXProgram Management Implementation Support and Testing Public and Panel Review and Input Requirements, Standards Selection, and Design Inspection Test, Public and Panel Comment Comment Resolution and Panel Approval Interoperability Specification Construct Development TASKS 3 weeks 3 months 4 weeks On-going 3 months 2 months Annual Updates as Required Requirements, Standards Selection, and Design Consolidated comments IS Docs V 1.0 Review Draft Summary of comment resolution Consolidated comments IS Docs V 1.0 Summary of comment resolution DOCUMENTATION
Key Activities and Milestones Work Plan and Schedule Overview • 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 HITSP 2007 Timeline 10/09/07 HITSP Board 04/23/07 HITSP Board 07/09/07 HITSP Board 02/05/07 HITSP Board 09/07/07 HITSP Panel 02/12/07 HITSP Panel 03/19/07 HITSP Panel 07/16/07 HITSP Panel 10/15/07 HITSP Panel 05/11/07 HITSP Panel JAN FEB MAR APR MAY JUN JUL AUG SEP OCT NOV DEC 6/18 – 6/20 TC Face to Face San Diego CA 5/08 – 5/10 TC Face to Face Arlington VA 09/04 – 09/06 TC Face to Face Arlington VA 03/06 – 03/08 TC Face to Face Chicago IL Activity 1 – Version 2.0 of Existing EHR, CE, BIO ISs EHR, CE and BIO v 2.0 On-going Support Implementation Support and Testing (includes minor document updates) Activity 2 – On-going Work for Existing EHR, CE, BIO ISs (e.g. Security and Privacy) Activity 3 – New Emergency Responder EHR Use Case S&P and EHR-ER v 1.0, EHR, CE, and BIO v M.m Implementation Support and Testing (with annual updates as required) Requirements, Standards Selection, and Design Public Input Inspect Test and Public Comment Comment Resolution and Panel Approval IS Construct Development 04/13 – 05/03 01/19 – 04/12 07/20 – 08/16 08/17 – 10/15 04/13 – 07/19 Activity 4 –New Use Cases from AHIC Detail Schedule to be Established Upon Review of the Use Cases
Version 2.0 of Existing EHR, BIO, CE ISs Release 2.0 Detailed Schedule
Key Points about the Release 2.0 Schedule Release 2.0 Detailed 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 Release 2.0 Detailed Schedule • 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 Release 2.0 Detailed Schedule
Version 1.0 of the Security and Privacy Constructs and Emergency Responder EHR IS ER-EHR and S&P Detailed Schedule Continued on next page…
Version 1.0 of the Security and Privacy Constructs and Emergency Responder EHR IS ER-EHR and S&P Detailed Schedule
Key Points about the Emergency Responder EHR and Security and Privacy Schedule ER-EHR and S&P Detailed 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 21stto disposition comment and republish the ISs for Panel approval by October 15th