Data Access Framework All Hands Community Meeting 1 May 4, 2016

2 If you are not speaking, please keep your phone on mute DO NOT place your phone on hold, if you need to take another call or step away, please hang up and dial in again Hold = Elevator Music = Frustrated Speakers and Participants Feel free to use the “Chat” feature for any questions, comments or any items you would like the moderator or participants to know Meeting Etiquette NOTE: This meeting is being recorded and will be archived on the DAF Wikipage, under “Materials”  “Past Meetings” From S&I Framework to Participants: Hi everyone: remember to keep your phone on mute

3 Agenda TopicEstimated Time General Announcements2 minutes SDO Updates5 minutes Pilot Updates30 minutes Next Steps & Questions2 minutes

4 General Announcements DAF All Hands Community Meeting Our next All Hands meeting will be on Wednesday, May 18, 2016 at 12:00 PM (ET). The meeting details can be accessed on the homepage: DAF Pilot Wikipage To track the latest Phase 3 pilot activities, please visit: Past Meeting Materials To access materials and meeting recordings from the All Hands meetings and technical WG calls, please visit:

5 SDO Updates HL7: DAF FHIR IG 1.1 HL7 May FHIR Connectathon 12 (Montreal, Canada) DAF will be testing as a track at the May FHIR Connectathon to include retrieval of laboratory results supporting both provider and patient access. This Connectathon will address the question whether accessing a patient’s laboratory results using the DAF Observation resource the DAF DiagnosticReport resource as the ‘entry’ point to the information. The purpose of this Connectathon is to provide the next steps for creating a simple FHIR client for accessing a patient. This track is a continuation of the first DAF Connectathon in January and will be reviewing resource types from the FHIR IG: Patient, Condition (Problem) MedicationStatement Allergies Results DiagnosticReport The subsequent step is extending to access patient lab data and investigating how whether the DAF DiagnositcReport Resource is needed for secondary access of lab data Read more on the DAF track at the May Connectathon here.here

6 C2: Standardize Metadata – Completed Draft structure of the C2 JSON resource – In Progress Review updates by team members to finalize C2 JSON C3: Standardize Query Distribution – Completed Draft structure of the C3 JSON resource Sample scenario walk through using proposed JSON and RESTful endpoints – In Progress Implementation pending resolution of issues raised at last review C4: Standardize Query Aggregate Results – Completed Draft structure of the C4 JSON resource Sample scenario walk through using proposed JSON and RESTful endpoints – In Progress Implementation pending resolution of issues raised at last review Next Steps – Resolve pending C4 issues at next group meeting – Begin implementation of C3 & C4 Phase 3-Pilot Update Lincoln Peak

7 Completed – Patient Mapping of Data Source to FHIR and FHIR to CDM for Patient Resource. Implementation of Data Quality checks and Data Standardization rules for Patient resource. Implementation of FHIR API on HAPI server for Patient resource which supports READ/Search operation. Generic FHIR/CDM connector implementation for invoking READ operation for Patient API. Implementation of FHIR/CDM convertor for transforming Patient API response to Demographic table elements and storing it in CDM. In Progress – Encounter Mapping of CDM to FHIR and Data Source to FHIR for Encounter. Data Quality and Data Standardization checks for Encounter resource. Implementation of FHIR API on HAPI server for Encounter resource which supports READ/Search. Generic FHIR/CDM connector for invoking READ operation for Encounter API. Implementation of FHIR/CDM convertor for transforming Encounter API response to CDM Encounter table elements and storing it in CDM data-mart. Phase 3-Pilot Update REACHnet

Questions 8

Upcoming Meetings Pilot TWG 2 (C2-C4): Monday, May 9, 2016 at 3:00 PM (ET) Pilot TWG 1 (C1): Wednesday, May 11, 2016 at 10:00 AM (ET) All Hands Community Call: Wednesday, May 18, 2016 at 12:00 PM (ET) 9 Next Steps

DAF Project Team  ONC Sponsor: Farrah Darbouze  S&I & DAF Initiative Coordinator: Johnathan Coleman  Support Team: Project Management: o Jamie Parker o Gayathri Jayawardena Project Support: o Nik Reineke o Swapna Bhatia Technical SME: o Nagesh (Dragon) Bashyam Standards SME: o Brett Marquard o Ed Larsen Software Developer: Douglas Harley Privacy and Security SME: o Glen Marshall Standards Development Support: o Angelique Cortez 10

Additional DAF Resources 11

Useful Links DAF Homepage – DAF Initiative Signup – DAF Charter – DAF Standards, Harmonization and Implementation Activities – tion tion DAF HL7 FHIR IG – DAF IHE White Paper – ev1.1_ pdf ev1.1_ pdf 12

13 SDO Updates DAF Publications  DAF FHIR IG DSTU (HL7) On September 23, 2015, Health Level Seven® International (HL7®) published Release 2 of the HL7 Fast Healthcare Interoperability Resources (FHIR®) Draft Standard for Trial Use (DSTU). Additionally, we are pleased to announce that the DAF FHIR Implementation Guide, a US-realm specific implementation guide, has also been published!! The DAF FHIR IG identifies and recommends standards for the interoperable representation and transmission of data using the notion of a Query Stack which modularizes the various layers of the Data Access Framework.DAF FHIR Implementation Guide  DAF Document Metadata Based Access IG (IHE) On September 24, 2015, the Integrating the Healthcare Enterprise (IHE) Patient Care Coordination (PCC) Technical Committee published The Data Access Framework (DAF) Document Metadata Based Access Implementation Guide. This US National Extension provides requirements and guidance on accessing clinical documents created during clinical workflows. The guide accomplishes this using RESTful resources based on HL7 FHIR® and the more traditional SOAP based IHE Profiles.The Data Access Framework (DAF) Document Metadata Based Access Implementation Guide