1. Data Access Framework All Hands Community Meeting March 26, 2014

2. Meeting Etiquette Remember: If you are not speaking, keep your phone on mute Do not put your phone on hold – if you need to take a call, hang up and dial in again when finished with your other call – Hold = Elevator Music = very frustrated speakers and participants This meeting, like all of our meeting is being recorded – Another reason to keep your phone on mute when not speaking Feel free to use the “Chat” feature for questions, comments or any items you would like the moderator or participants to know. NOTE: This meeting is being recorded and will be posted on the Wikipage, under “Past Meetings” after the meeting From S&I Framework to Participants: Hi everyone: remember to keep your phone on mute 2

3. Agenda TopicEstimated Time Standards Analysis Recap15 minutes Brief Recap of Last Week’s Direct Standards Discussion15 minutes Continue Candidate Standards Analysis20 minutes Next Steps/Questions5 minutes 3

4. Notional Project Timeline S&I Lifecycle (Discovery  Pilot & Evaluation) Today 3/26 February May Signifies milestone or deliverable March AprilJune Define Use Case & Functional Requirements Define Use Case & Functional Requirements Discovery (Use Case 2) UC 2 Consensus (2/5) Draft DAF/IHE White Paper Complete (2/28) DAF/IHE White Paper Published January 2014 UC 2: Targeted Data Access: Inter- Organizational Query Implementation (DAF/IHE Community) DAF IHE/ S&I Joint Work Group IHE Activities Publish DAF/IHE White Paper IG Consensus Implementation (S&I Community) Candidate Standards Analysis TWG 1: Document Metadata based access for LDAF & TDAF Finalize Actors + Transactions + Technology Stacks and Standards Create IG’s based on existing standards Create SWG to modify/add standards as necessary Update IG’s based on SWG output Candidate Standards Analysis Finalize Actors + Transactions + Technology Stacks and Standards Create SWG to profile standards for data element access TWG 2: Data Element based access for LDAF & TDAF White Paper Comment Period

5. DAF Candidate Standards Analysis Standards Analysis Process Recap – Examine the various standards and fill out the Candidate Standards Spreadsheet – Select and finalize standards that can be leveraged for the various DAF use cases – Focus on Modularity / Substitutability of standards across the various layers of transport, security, query structure and query results. Process Steps: – Identify technical requirements based on use cases – Identification and Analysis of the various candidate Query stacks (SOAP, RESTful, SMTP etc) – Finalization of the candidate standards spreadsheet – Identification of Gaps and Technical Solutions – Finalizing the standards based technical solution for current use cases – Creation of IG 5

6. 6 Transactions/Queries Required for DAF Find Document(s) based on Patient Identifiers Find Document(s) based on Patient Demographics Get Document(s) based on Document Identifiers Get Document(s) based on Patient Identifiers Get Document(s) based on Patient Demographics Get Document(s) for Multiple Patients based on Patient Ids * Supply and Consume User Assertions Capture and Supply Patient Consent Find Patient Identifiers based on Patient Demographics Find Patient Demographics based on Patient Id DAF Technical Requirements from use cases * - Only in the context of LDAF and is not applicable for TDAF

7. 7 DAF Candidate Query Stacks DAF Query Stacks for Document Metadata based access – SOAP Stack (SOAP over HTTP, SAML, XDS, XCA and other related IHE profiles) – SMTP Stack (SMTP, S/MIME, Content structured using SOAP Content profiles of RESTful resources) – RESTful Stack (HTTP, OAuth, RESTful Resources)

8. 8 SOAP Stack Analysis SOAP Stack Detailed Analysis is present in the IHE PCC DAF White Paper – Examines Transport, Security, Content Models – Addresses Substitutability and modularity concepts

9. 9 SMTP Stack Analysis - Recap Organized a dedicate SMTP Stack Discussion last week along with members from the Direct Community – A very good robust discussion on the applicability of Direct as a standard for Queries – Since Direct is primarily a transport standard, agnostic to content the community indicated that it would be best to leverage the existing XDS metadata and related models to structure the queries and results – Some members felt that we should wait to determine if Direct is a candidate until the Data Element based access WG is started.

10. 10 SMTP Stack Analysis – Recap Cont’d The following were some of the advantages that were presented by the community in using Direct – Leverage existing MU2 capabilities that is available since Direct is a mandatory transport standard for ToC / VDT use cases – Leverage security layers of Direct – Leverage the discovery mechanisms of Direct Some of the areas where Direct has to be enhanced to meet any query capabilities are – Request / Response correlation has to implemented at the edges – Is an asynchronous protocol by nature, so work flow implications have to be addressed (No specific use cases currently for asynchronous workflows) – Create bindings of existing Content models such as FHIR or XDS for Direct – Additional burden on vendors to implement Direct for queries – Home for the Direct Query stack Implementation Guides were not very clear (Many proposed IHE as an option)

11. 11 SMTP Stack Analysis – Recap Cont’d Proposed Path Forward: – DAF will encourage the community members to pursue defining the SMTP stack based on Direct for Queries if there is significant interest. Specifically the DAF support team will provide the necessary resources to schedule any sub work-group calls and setup any wiki/collaboration resources required – The sub-work group can define the necessary artifacts and present to the DAF Technical WG periodically – If there is enough community support around the WG, the WG can also move towards creating an IG and propose to an SDO such as IHE DAF Support team will continue to focus on flushing out details on the SOAP and RESTful query stacks – Continue to identify gaps in the existing SOAP and RESTful stacks and address the gaps » (For e.g a single query vs multiple queries for retrieving documents based on demographics, retrieving documents for multiple patients etc)

12. 12 RESTful Query Stack Analysis Current Status: – IHE MHD Profile and its capabilities – FHIR Document Reference, Document Manifest, Bundles and Compositions – Issues to consider IHE Currently working on aligning MHD with FHIR Detail discussions and analysis are in progress DAF is determining the best way to leverage the work that is being performed and participate in these discussions

13. 13 Pending Analysis Activities Analysis of the Security profiles for RESTful Query stack – Use of IHE ATNA / IUA and/or FHIR Labels etc. – For the SOAP stack, ATNA and XUA is the currently adopted profile and it is described in the IHE white paper. Try to leverage implementation experiences to collect feedback about the XUA profiles. Analysis of Consent/Segmentation Related profiles and their usage with SOAP and/or RESTful stacks – BPPC, CDA Consent Directive and DS4P

14. DAF Candidate Standards Analysis Standards Analysis Process Recap – Examine the various standards and fill out the Candidate Standards Spreadsheet – Select and finalize standards that can be leveraged for the various DAF use cases – Focus on Modularity / Substitutability of standards across the various layers of transport, security, query structure and query results. Process Steps: – Identify technical requirements based on use cases – Identification and Analysis of the various candidate Query stacks (SOAP, RESTful, SMTP etc) – Finalization of the candidate standards spreadsheet – Identification of Gaps and Technical Solutions – Finalizing the standards based technical solution for current use cases – Creation of IG 14

15. 15 IHE IUA profile Describes Authorization profile for RESTful resources or services Based on OAuth2.0 Framework JWT Token with defined extensions SAML Token, using the XUA extensions Detailed Documentation

16. Questions 16

17. Data Access Framework Resources DAF Wiki Homepage – http://wiki.siframework.org/Data+Access+Framework+Homepage http://wiki.siframework.org/Data+Access+Framework+Homepage Become a Community Member – http://wiki.siframework.org/Data+Access+Framework+Join+the+Initiativ e http://wiki.siframework.org/Data+Access+Framework+Join+the+Initiativ e DAF Charter – http://wiki.siframework.org/Data+Access+Framework+Charter+and+Me mbers http://wiki.siframework.org/Data+Access+Framework+Charter+and+Me mbers DAF Standards, Harmonization and Implementation Activities – http://wiki.siframework.org/DAF+Standards+Harmonization+and+Imple mentation http://wiki.siframework.org/DAF+Standards+Harmonization+and+Imple mentation Standards and Interoperability(S&I) Framework – http://wiki.siframework.org/Introduction+and+Overview http://wiki.siframework.org/Introduction+and+Overview S & I Calendar of Events – http://wiki.siframework.org/Calendar http://wiki.siframework.org/Calendar 17

18. Initiative Support Leads For questions, please feel free to contact your support leads: – Initiative Coordinator: John Feikema john.feikema@siframework.orgjohn.feikema@siframework.org – ONC Sponsors: Mera Choi mera.choi@hhs.govmera.choi@hhs.gov – Support Team: Project Management: – Gayathri Jayawardena gayathri.jayawardena@esacinc.comgayathri.jayawardena@esacinc.com Technical Support: – Dragon (Nagesh) Bashyam nagesh.bashyam@drajer.comnagesh.bashyam@drajer.com Use Case Development: – Presha Patel presha.patel@accenture.compresha.patel@accenture.com – Hema Patel hema.patel@accenture.comhema.patel@accenture.com Standards Support: – Angelique Cortez angelique.j.cortez@accenture.comangelique.j.cortez@accenture.com Vocabulary and Terminology Subject Matter Expert: – Mark Roche mrochemd@gmail.commrochemd@gmail.com 18