1 DRAFT October 22, 2008 Ed Larsen Framework Review Working Group Plan

2 HITSP – enabling healthcare interoperability Today’s Agenda  Introductions  Discussion of Scope, Priorities and Scheduling –The Board Approved TOR –Scope –Priorities/Major Tasks –Scheduling /Meeting Logistics  How do we proceed with our work  Action Items from the Meeting

3 HITSP – enabling healthcare interoperability Introduction and Organization  Leadership –John Quinn, HL7 –Elliot Sloane, IHE –Dave Riley, FHA  Volunteers –Insure key representations √IHE, √HL7, √FHA, X12, NCPDP Who else?  Staff –Ed Larsen, Jack Corley, Bob Yencha, Gene Ginther and Eric Pupo

4 HITSP – enabling healthcare interoperability MOTION – Approve Establishment of Framework Review Working Group  The HITSP Board approved the establishment of the Framework Review Working Group under the Foundations Committee to evaluate and if necessary, present a proposal to revise the HITSP Framework. –Membership, leadership and staff support are open to all –Confirm drivers to change current HITSP Harmonization Framework  Evaluate adoption issues/challenges (HIEs, ONC, NHIN, CCHIT)  Address known challenges in utilizing current framework –Consider leveraging of HL7 work and harmonizing with all SDOs –TC co-chairs will be solicited for input during the evaluation and proposal process –Provide preliminary findings by November 15 and final recommendations by December 31  APPROVED – No Objections  Next steps – A call for committee participation will be announced the HITSP membership.  The HITSP Board advised the Foundations Committee to continue forward with their defined terms of reference and to continue to report to the Board on a yearly basis.

5 HITSP – enabling healthcare interoperability Priorities / Major Tasks 1.Defining the scope of the problems to address in the Framework Review. –Task 1 – Agree today√ 2.Understand the Services Aware Enterprise Architecture Framework (SAEAF) that HL7 is developing –Task 2 - Presentation by HL7 ArB – Next meeting 3.Based on our HITSP expertise, evaluate how SAEAF can be applied (assuming it can). –Task 3 - HITSP experts evaluate SAEFE and any alternatives – Next Following 4.Issue a report of the above with expected directions (November 15) –Task 4 - Staff draft for WG review 5.Redesign the Framework as necessary to support services, interoperability service contracts and avoid any rip and replace 6.Develop an implementation and transition plan to present to TC Leadership by December 31

6 HITSP – enabling healthcare interoperability 1. Defining the scope of the problems to address  Identified Problems –Implementers coming in sideways to reuse constructs in non-conformant manner –Current framework does not incorporate services Cannot harmonize NHIN work for HIEs Cannot support CCHIT network certification –Defining conformance at different levels of “the stack” –Producing 2009 extension and gap fillers is too cumbersome using current framework –Current framework requires changes across many documents when one is changed  Other Challenges to Consider –Alignment with HITSP current framework, templates and concepts and relationships Includes concepts of stakeholders, business actors, technical actors, IERs, DRs, and SDEs –Parallel work groups/IRT? –Transition and migration from existing framework and documents

7 HITSP – enabling healthcare interoperability 2. Gather information on options  Gain in-depth understand the Services Aware Enterprise Architecture Framework (SAEAF) that HL7 is developing –Presentation of SAEAF by HL7 ArB experts (NEXT MEETING)  Identify and gather information on any other approaches to consider –Who wants to work on this? –FHA perspective – Craig Miller/Dave Riley  Solicit input from HITSP standards organizations –Probably present to SDO Summit on November 14

8 HITSP – enabling healthcare interoperability 3. Evaluate how SAEAF and/or other options can be applied  Use our expertise in current HITSP Interoperability Specifications and constructs, templates, processes including RDSS, and the 2009 work items as base –Who wants to represent current Framework and Templates?  Comparative Analysis versus Problems –Current framework –Services aware framework –Other options  Who wants to evaluate?

9 HITSP – enabling healthcare interoperability 4. Interim Report  Issue a report on the above steps with expected directions (November 15) to Program Team and TC Leadership –Ongoing drafting by Staff –Final draft by November 12 – working approval by COB November 14  Outline –Scope and objectives (TOR) –Problems –Preliminary Evaluation of SAEFE /Other –Proposed Go Forward Plan for December 31 Deliverable

10 HITSP – enabling healthcare interoperability 5. Redesign the Framework  Redesign as necessary to support services, interoperability service contracts and avoid any rip and replace –Modify current framework and adopt services formalisms as indicated –Start with optional service wrappers? –Run parallel frameworks for existing IS  Work to be completed after November 15 Interim report and feedback

11 HITSP – enabling healthcare interoperability 6. Publish Implementation and Transition Plan  Develop an implementation and transition plan to present to TC Leadership by December 31 for acceptance  Make necessary changes to plan based on consensus  Make required changes to processes and templates for 2009

12 HITSP – enabling healthcare interoperability Scheduling/ Meeting Logistics  Meetings –Call schedule Only 3 Full Weeks to November 15 Delivery Twice a week for an hour or extended call once a week? –F2F? Around HL7 Harmonization/SDO Summit (Nov 12 – 14) Around HITSP Panel (December 18)  Insure outreach to all SDOs, IHE and FHA  Coordination with IRT, Foundations Information Interchange and TC Leadership  Any plan must include migration/transition plan

13 HITSP – enabling healthcare interoperability