html5-img
1 / 14

Data Access Framework All Hands Community Meeting

Data Access Framework All Hands Community Meeting. July 23, 2014. 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

barr
Download Presentation

Data Access Framework All Hands Community Meeting

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Data Access Framework All Hands Community Meeting July 23, 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. From S&I Framework to Participants: Hi everyone: remember to keep your phone on mute  NOTE: This meeting is being recorded and will be posted on the DAF Wikipage, under “Materials” “Past Meetings”

  3. Agenda

  4. Notional Project Timeline S&I Lifecycle (Discovery  Pilot & Evaluation) July2014 August September Today 7/23 October November December DAF/IHE White Paper Published Data Element IG Consensus Document IG Consensus Implementation (DAF/IHE Community) IHE Activities WP Comment Period IHE Trial Implementation Meeting DAF IHE/ S&I Joint Work Group Implementation (S&I Community) Pilots & Testing TWG 1: Document Metadata based access for LDAF & TDAF Create IGbased on existing standards Creating Operation Plan for Pilot Testing Pilots and Testing Balloting Activities Implementation (S&I Community) Pilots & Testing Candidate Standards Analysis Finalize Actors + Transactions + Technology Stacks and Standards Create IG Creating Operation Plan for Pilot Testing Pilots and Testing TWG 2: Data Element based access for LDAF & TDAF Balloting Activities

  5. DAF Data ElementsStandards Selection • The DAF standards comparison spreadsheet is posted to the Harmonization section of the DAF wikipage • Please visit the following link to submit your comments: http://wiki.siframework.org/DAF+Standards+Harmonization+and+Implementation#Comment

  6. Candidate Standards Discussed … • All standards identified by the community have been discussed • FHIR • QUICK • QED • HL7v2.x • HQMFv2 • Need to start narrowing down to a single standard from the existing set of candidates. • Standards selected may still need to be enhanced to satisfy DAF requirements • Profiles may be required to create an implementable IG

  7. HQMF v2 • Early decision to not pursue further analysis of HQMFv2 due to • Its focus on quality measures • Complexity of creating queries • Document Paradigm • Not completely computable • Results are to be obtained using other types of documents such as QRDA Category I, QRDA Category III, C-CDA etc.

  8. QED - SWOT RESTful QED looking at FHIR as an option to adopt

  9. QUICK • Quality Improvement Clinical and Knowledge model • QUICK = Harmonization of vMR and QDM with mappings to FHIR • Objective is to use the model in clinical quality artifacts • In expressions and criteria for eMeasures, CDS artifacts • Hence, the model is tuned for that purpose • Objectives of Mapping to FHIR • Interoperability • Gain physical format, API • CQL • complements FHIR and does not replace it. (Enables complex queries) • This expression is used in knowledge artifacts. • The execution of this artifact may leverage FHIR to obtain the data for use within the reasoning engine. • S&I CQF is going to leverage FHIR to implement QUICK/CQL

  10. HL7v2.x • Query Specification Formats • Query by Simple Parameters • Query by Example Variant • Query by Using the QSC Variant • Query profiles will be required to be created similar to the Immunization profile

  11. Discussion to Narrow Down the Standards • FHIR seems to be emerging as a leading candidate • QED/QUICK adopting FHIR in the near future or as part of the roadmap • Is the emerging standard backed by industry support • Is in sync with FACA guidance to embrace RESTful approaches • HL7v2.x seems to be the other alternative to puruse Strawman Poll: • Pursue FHIR for Simple DAF Data Element Queries using existing DSTU and create profile and IG as needed • Monitor CQL and how it evolves as a Query syntax for complex queries instead of developing a parallel query syntax

  12. Questions

  13. Data Access Framework Resources • DAF Wiki Homepage • http://wiki.siframework.org/Data+Access+Framework+Homepage • Become a Community Member • http://wiki.siframework.org/Data+Access+Framework+Join+the+Initiative • DAF Charter • http://wiki.siframework.org/Data+Access+Framework+Charter+and+Members • DAF Standards, Harmonization and Implementation Activities • http://wiki.siframework.org/DAF+Standards+Harmonization+and+Implementation • Standards and Interoperability(S&I) Framework • http://wiki.siframework.org/Introduction+and+Overview • S & I Calendar of Events • http://wiki.siframework.org/Calendar

  14. Initiative Support Leads • For questions, please feel free to contact your support leads: • Initiative Coordinator: John Feikema john.feikema@siframework.org • ONC Sponsors: Mera Choi mera.choi@hhs.gov • Support Team: • Project Management: • GayathriJayawardenagayathri.jayawardena@esacinc.com • Technical Support: • Dragon (Nagesh) Bashyam nagesh.bashyam@drajer.com • Standards SME: • Ed Larsen ed_larsen@comcast.net • Standards Support: • Angelique Cortez angelique.j.cortez@accenture.com • Vocabulary and Terminology Subject Matter Expert: • Mark Roche, MD mrochemd@gmail.com

More Related