HITSP Process to support TC Restructuring

1. HITSP Process to support TC Restructuring Includes Deliverables, Domain TC Terms of Reference, and Transition Plan

2. Restructuring Plan Care Management and Health RecordsTechnicalCommittee Infrastructure, Security and Privacy Technical Committee Administrative and Financial TechnicalCommittee Perspective Technical Committees Population Perspective TC Provider Perspective TC Consumer Perspective TC Use Case Use Case Use Case Use Case Use Case Use Case Use Case Use Case Use Case Use Case Use Case Use Case Security & Privacy Workflow and Process Terminology And Knowledge Representation Messaging and Datatypes Modeling Domain TCs Foundations Committee - TC Leadership Oversight - Communications function

3. Revised HITSP Process With IRB Review Points 3 Months 1.5 Month 1 Month 1 Month 3 Months Interoperability Specifications, System Integ Draft Use Case Analysis Preliminary Project Plan RDSS Inspection Test/ Public Comment Interoperability Constructs Draft Use Case Final Use Case RDSS Comments Implementors/SDO Feedback 2-3 Months Maintenance Panel Approval, Public Release Resolve and Disposition Comments Legend Domain TC Perspective TC IRB

4. Other work during transition • Provide comments on new use-cases – due Feb. 14 • Analyze draft use cases with 6 ad hoc groups with assigned co-chairs • Remote Monitoring – Steve H. • Consultation and Transfers of Care – Allen Hobbs • Patient Provider Secure Messaging – Mureen Allen • Personalized Healthcare – Scott Robertson • Public Health Case Reporting – Floyd/Steve S,/Peter • Immunizations & Response Management – Floyd/Steve S,/Peter • Internal deliverable – “Floyd Ranking” refined

5. Preliminary Use-Case Assignment to Perspective TCs • Provider Perspective TC – Steve Wagner, Steve Hufnagel, Alan Hobbs • Remote Monitoring • Consultation and Transfers of Care • Medication • ER-EHR • NHIN • Consumer Perspective TC – Charles Parisot, Scott Robertson, Mureen Allen • Patient Provider Secure Messaging • Personalized Healthcare • Consumer Empowerment • NHIN

6. Preliminary Use-Case Assignment to Perspective TCs • Population Health – Floyd Eisenberg, Peter Elkin, Steve Steindel • Public Health Case Reporting • Immunizations & Response Management • Quality • NHIN • Integration view • per IS – Perspective TC • Across ISs – TC Leadership, IRB, Domain TC • Across constructs – Domain TC

7. TC Restructuring Transition Plan Proposal (1 of 3) • TC Leadership at January face-to-face do provisional use-case allocation to Perspective TC • In February, organize restructuring transition • Transition of existing TCs to Perspective TCs • Retain co-chairs • Refine existing TC terms of reference to reflect existence of both Perspective and Domain TCs – by Feb 4 for Board approval • Establish process to do work plan/breakdown structure of use-case – TC Leadership and some expertise; look for consistency of process • Refine assignment of new use-cases – by HIMSS annual conf. • Finalize staff assignments to support TCs • Call for participation • For all Committees starting at Panel Meeting (Feb 20) and extending at HIMSS • Additional focused recruiting for each Perspective and Domain TC

8. TC Restructuring Transition Plan Proposal (2 of 3) • In February-early March, Establish Domain TCs • Two t-cons –Hold preliminary discussions, retain co-chairs for S&P • Define terms of reference for each Domain TC consistent with general Domain TC TOR by Feb 4 for Board approval • Gain approval of Board for each Domain TC term of reference • Allow facilitators or volunteer interim conveners to run Care Management and Admin domain TCs?

9. TC Restructuring Transition Plan Proposal (3 of 3) • Plan for training session for new members in mid-March, 2 web-exes, plan for session at March face-to-face • Complete organization transition by March 15 to support 6 use-cases and maintenance/development/support of existing HITSP constructs (7 ISs, constructs) • Identify how to convene Domain TC meetings at March face-to-face (conveners, staff, …?) • Do election for Care Management and Admin Domain TCs after March 24-26 TC face-to-face, hold election to establish co-chairs • Establish preliminary project plan for new use-cases at March face-to-face – finalize early April • March face-to-face under new structure • IS01 and IS02 V3 for HITSP panel approval and submission to AHIC • Interoperability Specs IS04-IS06 work complete pre-face-to-face • IS07 released for inspection testing

10. Revised HITSP Process Steps – Initial Planning

11. Revised HITSP Process Steps – RDSS Development

12. Revised HITSP Process Steps – IS Development

13. DOMAIN TC TERMS OF REFERENCE - General Strategy • Preferred approach - reuse or repurpose existing constructs to meet requests • Do reactively as new requests arrive • Do proactively as new constructs are developed – think reuse during development • If new construct needed, where possible, use and reference existing implementation guides or profiles provided by an SDO. • Wherever possible and appropriate, engage relevant SDO(s) that have or are willing to establish relevant work to attempt to minimize HITSP-developed construct content in favor of reference to standard(s). • Initiate as early as possible • To close gaps • Harmonize overlapping standards relevant to the construct(s)

14. DOMAIN TC TERMS OF REFERENCE - Working with HITSP Perspective TCs • Receive requests from the HITSP Perspective TCs for construct development or revision • Evaluate scope of effort • Define work-plan - scope statement, estimate of effort, schedule. • Collaborate with Perspective TC(s): • Refine work-plan • Do design work necessary to develop Requirements Design and Standards Selection (RDSS) and Interoperability Specification documents. • Assign and refine requirements to construct(s) to be developed.

15. DOMAIN TC TERMS OF REFERENCE - External Request Assigned to Domain TC • When an external request is to develop, change, or repurpose construct(s) • Domain TC establishes work-plan - scope statement, estimate of effort, schedule. • Collaborate with external requesting source • Refine work-plan • Identify requirements for construct(s) to be developed

16. DOMAIN TC TERMS OF REFERENCE – Construct Development and Maintenance • Assess impact on other scheduled deliverables. • If significant, negotiate schedule with all affected parties. • IRB will be the final arbiter when conflicts are not resolved. • Develop or revise HITSP constructs (transaction packages, transactions, components, Technical Notes) to meet requirements • Refine workplan as needed • Ensure HITSP constructs under Domain TC adequately support all Interoperability Specifications that reference those constructs • Ensure timely disposition of assigned public and testing comments • Establish a mechanism for coordinating activities with other HITSP TCs and workgroups • Maintain existing constructs • Monitor relevant base and composite standards for changes • Report planned changes to Perspective TCs and solicit feedback prior to updating constructs

17. DOMAIN TC TERMS OF REFERENCE –Some Comments • Need explicit feedback loop to ONC and AHIC • We must engage ONC and AHIC in dialogues to gain understanding of intent of use cases and their relative priority. Needed to plan. • Domain TCs must seek, attract, and engage appropriate experts in their work - done in collaboration with HITSP leadership and peer committees. • IRB role in settling schedule/priority conflicts must not lead to adding to a TC's workload without added resources to do the work.

18. Revised HITSP Process With IRB Review Points 3 Months 1.5 Month 1 Month 1 Month 3 Months Interoperability Specifications, System Integ Draft Use Case Analysis Preliminary Project Plan RDSS Inspection Test/ Public Comment Interoperability Constructs Draft Use Case Final Use Case RDSS Comments Implementors/SDO Feedback 2-3 Months Maintenance Panel Approval, Public Release Resolve and Disposition Comments Legend Domain TC Perspective TC IRB

19. To Maximize Reuse/Repurposing • Look at approach SPTC is developing

20. Domain TCs • Care Management and Health Records • Maintenance of existing constructs and harmonization with underlying standards • Summary • Lab • Medication/Immunization • NHIN • Infrastructure, Security and Privacy – (John Moehrke, Glen Marshall, Walter Suarez) • Maintenance of existing constructs and harmonization with underlying standards • Infrastructure • Security • Privacy • NHIN

21. Domain TCs • Administration and Finance - (new co-chairs) • Maintenance of existing constructs and harmonization with underlying standards • Quality • Response Management • Medication (Eligibility, Formulary, …) • NHIN • Data Element • Document Maintenance

22. Work On The Horizon • Develop 6 new use cases • Technology Transfer of existing IS • Technical Education material about existing approved HITSP IS and constructs • Respond to NHIN-2 and CCHIT questions on existing ISs and constructs • Maintenance and update of the first 6 use cases, especially completing the V3.0 of IS01 and IS02. • Complete work on IS07 and address selected gaps in IS04, IS03 (CACI use case)

23. Backup Material

24. Revised HITSP Process Steps – Initial Planning

25. Revised HITSP Process Steps – RDSS Development

26. Revised HITSP Process Steps – IS Development