data access framework all hands community meeting
Download
Skip this Video
Download Presentation
Data Access Framework All Hands Community Meeting

Loading in 2 Seconds...

play fullscreen
1 / 14

Data Access Framework All Hands Community Meeting - PowerPoint PPT Presentation


  • 72 Views
  • Uploaded on

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

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' Data Access Framework All Hands Community Meeting ' - brendan-simpson


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
meeting etiquette
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”

notional project timeline
Notional Project Timeline

S&I Lifecycle

(Discovery  Pilot & Evaluation)

July2014

August

September

Today 7/16

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

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

candidate standards discussed
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
hqmf v2
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.
qed swot
QED - SWOT
  • RESTful QED looking at FHIR as an option to adopt
quick
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
hl7v2 x
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
discussion to narrow down the standards
Discussion to narrow down the standards
  • FHIR seems to be emerging as a leading candidate
    • QED/QUICK adopting FHIR in the near future
  • HL7v2.x seems to be the other alternative
data access framework resources
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
initiative support leads
Initiative Support Leads
ad