1 / 18

Data Access Framework All Hands Community Meeting

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

radha
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 2, 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. General Announcements • DAF IHE/S&I Joint WG • This workgroup will be meeting every other week • Upcoming schedule: • Monday, July 7th at 10:00 am (EDT) • The week of July 21st will be the IHE Trial Implementation Meeting. Meeting details will be posted on the DAF wiki as soon as it is released • White Paper comment period ends tomorrow • White Paper: http://ihe.net/Public_Comment/#pcc • Comment Form: http://ihe.net/PCC_Public_Comments/

  5. Notional Project Timeline S&I Lifecycle (Discovery  Pilot & Evaluation) July2014 August September October November December Today 7/2 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 Pilots & Testing Implementation (S&I Community) 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

  6. Data ElementsComment Form • Take a moment to review the latest DAF data elements spreadsheet and submit your comments through the online comment form: http://wiki.siframework.org/DAF+Standards+Harmonization+and+Implementation

  7. Overview of QUICK CQF team discussion with DAF team 2nd July 2014

  8. QUICK • Quality Improvement Clinical and Knowledge model • QUICK = Harmonization of vMR and QDM with mappings to FHIR • Domain of QUICK is to model patient data • 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

  9. Timeline • Project formally initiated in Fall 2013 • QIDAM = Conceptual model • Ballot passed in May 2014 • Moving towards publication in August 2014 • QUICK = Logical model • Comment only ballot in September 2014 • FHIR mappings in Jan 2015

  10. Overview of class model in QIDAM • Walk through of UML model • Salient features • Core: Clinical Statement • Topic: Actions and Observables • Actions: Modality and Act

  11. What will QUICK class model add? • FHIR datatypes • Extension mechanism • Concrete statement types • E.g., ProcedureOrderOccurrence • The exact structure of how this statement is constructed in QUICK is being determined

  12. Mapping to FHIR • Objectives • Interoperability • Gain physical format, API • Initial analysis of QIDAM-FHIR mapping was performed • We expect that to create mappings to FHIR, we will • Create new FHIR resources, e.g., Prognosis • Profile existing resources, e.g., DiagnosticOrder • Tweak QUICK classes

  13. An example: QUICK and CQL Retrieve “Inpatient” encounters performed that have a condition of “Acute Pharyngitis” that began during the encounter and continues after it. Only include encounters with a duration of 120 days or more. For each encounter, return a tuple with the id and the length of stay. Order the results by the length of stay descending. CQL complements FHIR and does not replace it. 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.

  14. DAF perspective • Does it address the data elements that is part of the DAF data element spreadsheet (attached) • See responses in spreadsheet • Does QUICK have a query syntax as part of the specification? If so, how does it compare to FHIR’s query syntax ? • Yes, CQL + QUICK. But we rely on FHIR or other specs for implementation. • Does it have any specific transport requirements? • No. See FHIR • Does QUICK have any packaging specification ? (for e.g some kind of a XML container to package the elements) • No. See FHIR • How can the model be used to extract  data elements (For e.g., we would like to query for meds, problems , allergies etc) • See example, CQL + QUICK

  15. DAF perspective • What is the real world adoption of the standard ? • TBD. Based on QDM and vMR which have been adopted in their respective domains • What are the strengths of the model? • Tuned for reasoning about clinical concepts • Where do you see the model going in terms of next steps? • Balloting logical model and FHIR mapping • What is the level of support for security/provenance metadata ? • No security metadata – out of scope for QUICK • Some provenance metadata in ClinicalStatement

  16. Questions

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

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