Health eDecisions RI/ Pilots Sub-Workgroup

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

2. Agenda • Announcements • Review of Goals • Review of RI/Pilot Sub-WG Timeline • Pilot project presentations • Wolters Kluwer • ZynxHealth • Medexter? • Questions and Answers • Review Action Items, Next Steps

3. Announcements • We will be continuing our work … • Next meeting March 11th, 2013 (plan for a 90 minute meeting) • We will wrap up presentation of Project Plans • The March 4th meeting is canceled due to HIMSS

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 • Harmonization: CemMangir: cmangir@deloitte.com • SDO Support: Anna Langhans: anna.langhans@accenture.com

6. HeD Pilots Goal • Goal • The goal of this initiative is to produce and consume 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.

7. Timeline We are Here

8. Materials for Project Plans: • Wiki Page: • http://wiki.siframework.org/Health+eDecisions+Pilots • Process: • Register as a “committed member” and attend Pilot Sub-WG calls. • Complete Pilot Project Documentation and present it to the Pilots Work Group • Think of this as “what do you intend to pilot” • See Pilots wiki for the document: • http://wiki.siframework.org/Health+eDecisions+Pilots • Pilot RI/ Pilot implementation – Development, Testing. • Provide feedback to ONC and HeD All Hands Community Meeting • Select a community member to represent our work at these meetings.

9. Pilot Project Schedule • As a reminder both NewMentor and OpenCDS presented their Pilot Project Plans to the team. (THANK YOU Julie and David) • Project plans are viewable on our wiki at: http://wiki.siframework.org/Health+eDecisions+Pilots • February 25th, 2013 • Zynx • Wolters Kluwer • Medexter (?) • Anyone, anyone, anyone…. • March 11th meeting will be focused around Vendor engagement and how to best utilize individual project plans with the Vendor community

10. Action Items & Next Steps • Continue developing the Pilots Work Plans • If you need help with this activity please contact: • Jamie Parker (jamie.parker@esacinc.com) • Christina Arenas:(christina.arenas@esacinc.com ) • Begin thinking about ways to connect Vendors, Content Producers and Content Supplier

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

12. 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

13. Appendix B • In Scope/Out of Scope

14. 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)

15. 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

16. 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)

17. 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