Health eDecisions RI/ Pilots Sub-Workgroup

1. Health eDecisionsRI/ Pilots Sub-Workgroup March 25th, 2013

2. Agenda • Announcements • Review and Revisit of Goals • Review of RI/Pilot Sub-WG Timeline • Pilot project presentations • Applied Pathways • Updates On IG • Review of Wiki tools • Discussion Board • Comment and Feedback form for Vocab and Terminology work • Updates on Vendor Activities • Updates on Licensing HeD Schema Framework Tool • Review Action Items, Next Steps

3. Announcements • We will be continuing our work … • Next meeting April 1st, 2013 (plan for a 90 minute meeting) • Continue to work on pilot activities • Begin Mapping/Harmonizing and translation activities • Determine support needs • Update timelines

4. Pilots

5. Support Team • Support Team: • Pilots Lead: Jamie Parker: jamie.parker@esacinc.com • Pilot Support: Christina Arenas: christina.arenas@esacinc.com • Subject Matter Expert: Aziz Boxwala: aziz.boxwala@meliorix.com • Subject Matter Expert: Bryn Rhodes: bryn@veracitysolutions.com • Use Case 1: Dave Shevlin: d.s.shevlin@accenturefederal.com • Implementation Guide: Lynette Elliot: lynettte.elliott@esacinc.com • SDO Support: Anna Langhans: anna.langhans@accenture.com

6. HeD Pilots Goal • Goal • The goal of this initiative is to produce, consume and where feasible, execute implementable CDS interventions. • Event Condition Action Rules (ECA Rules) • Order Sets • Documentation Templates • Pilot Scope • Health eDecisions will apply defined aspects of the Implementation Guide in a real-world setting. • Modify the Implementation Guide to ensure it is usable • The real-world pilots evaluate not only the technology, standards and model (VMR), but also provide a test bed to evaluate the interaction of technology, implementation support, and operational infrastructure required to meet Health eDecisions use case 1 objectives at the stakeholder or organization levels. • Demonstrate intent of artifact (specifically structures and semantics) are communicated either by direct execution or by translation to native format • Ensure Completeness and consumability of artifact

7. Timeline We are Here

8. Applied Pathways • Demo by: Paul Arnone

9. Update on IG • We have finished the draft IG • All ballot comments have been integrated • Schemas have been updated

10. Wiki Tools • General Monitored Discussion: • http://wiki.siframework.org/HeD+Pilot+Activities#HeD_Pilot_Discussion • Feedback on tools • Vocabulary and Terminology Work: http://wiki.siframework.org/HeD+Pilot+Tools • Discussion and Demo

11. Vendor Engagement Discussion • What we can do to help the vendors implement HeD Artifacts • What do the vendors need from us the support team? • What do the vendors need from the content suppliers? • Which content suppliers can meet this need? • Are we ready to start matching content suppliers to vendors?

12. Licensing –HeD Schema Framework Tool • We have requested an update/guidance on this issue. • There is some confusion if this should be licensed through ONC or HL7 • We will continue to monitor this and update you all as we get final word

13. Action Items & Next Steps • Begin pilot work!!!

14. Meeting Reminder • Pilots Work stream meets (next meeting: March April 1st, 2013) • Every Monday • 1-2:30 pm EDT See Wiki homepage for meeting details: http://wiki.siframework.org/Health+eDecisions+Homepage

15. Appendix A: Success Criteria • NOTE: This is a work –in-progress we will need to re-evaluate this after Pilot Project Plans • Discuss Pilot Success Criteria: • Individual Criteria • Initiative Criteria • EHR Involvement - DONE • Production (at least one of each artifact and consumption of those artifacts) • Addressed as part of the Pilot Project Plans (who will be doing which artifacts) • Successful implementation of artifacts • EHR involvement • Validate artifact – perhaps Pilots focuses on this ? • Execute the artifact • Cross initiative function • Potential Alignment with eDOC and esMD • SDC • Alignment with MU 3 objective • 10% knowledge based engine (align 402b) • ACTION ITEM: Review MU3 Criteria • Determine the delivery model we want to pilot • External (i.e. cloud service) • Assets are portable (can be run locally) • Discuss this with the group

16. Appendix B • In Scope/Out of Scope

17. Scope of Use Case 1 • This Use Case defines the requirements to build a standard for the contents of CDS Knowledge artifacts.  The use case focuses on the following artifact types: Event Condition Action (ECA) Rules, Order Sets, and Documentation Templates. To support this purpose the Use Case has one scenario:  A CDS Knowledge Artifact Supplier makes computable CDS Knowledge Artifact available to CDS Artifact Integrator (From HeD Use Case: CDS Artifact Sharing)

18. In Scope • Standards to structure medical knowledge in a shareable and executable format for use in CDS • In Scope Artifact Types (definitions for these artifact types can be found in Appendix A) • Event Condition Action Rules • Order Sets • Documentation Templates

19. Out of Scope • Tools: • Authoring tools, source “content” management. • Terminology server and mapping tools including management of concept coordination. • Semantic processing of text, including structured string processing and natural language processing. • System Functions • Messaging Layer • Means of sharing • Security • Authoring, creation and maintenance of clinical decision support knowledge • Knowledge Repository Design • Search and query mechanisms • Implementation in systems • User presentation, Transport layers • Market factors: regulatory incentive/mandate, liability shield, IP shield (patent/licensing litigation), certification body, marketplace design, test procedures, FDA rules • Clinical Decision Support Services (this will be covered in Use Case 2 CDS Guidance Services) • CDS Content Development Activities, including the distribution and sharing of artifacts • Context-Aware information retrieval (HL7 Information Button) – This will be covered in UC 2 (CDS Guidance)

20. Pre and Post Conditions • Pre-Conditions • CDS Artifact Supplier makes CDS artifacts available for search and consumption by CDS Artifact Integrators _ ACTION ITEMS (Clarify this –what is a precondition for this to be useful) • CDS Artifact integrator has the means to obtain the knowledge artifact from a CDS Repository (e.g. they have either browsed or queried the CDS Repository for available artifacts) • CDS Artifact Integrator Selects Artifacts of Interest to Use in their CDS System • Post Conditions • The CDS Knowledge Artifact Supplier has sent the CDS Knowledge Artifact to the requesting CDS Artifact Integrator • CDS Artifact has been received by CDS Integrator and is available for processing • CDS Artifact is available for mapping, structural transformations and local adaptation • Strategy Decision: In the pilot activities we will not directly address these as part of our pilot. We will focus the pilot activities on those tasks which occur between the pre and post condition