Embed Size (px)
DESCRIPTION
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 - PowerPoint PPT Presentation
Citation preview
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– 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 DAF Wikipage, under
“Materials” “Past Meetings”
NOTE: This meeting is being recorded and will be posted on the DAF Wikipage, under
“Materials” “Past Meetings”
From S&I Framework to Participants:Hi everyone: remember to keep your phone on mute
2
Agenda
Topic Estimated Time
Update from Joel on DAF Direct SWG 5 minutes
Data Element Standards Analysis 40 minutes
Next Steps/Questions 5 minutes
3
Create IG based on existing standards
Create IG based on existing standards
WP Comme
nt Period
WP Comme
nt Period
Notional Project Timeline S&I Lifecycle
(Discovery Pilot & Evaluation)Today
7/16August Novemb
erSeptember
October December
DAF/IHE White Paper Published
July2014
Implementation (DAF/IHE
Community)
Implementation (DAF/IHE
Community)
DAF IHE/ S&I Joint Work GroupIH
E A
cti
vit
ies
Document IG
Consensus
Implementation (S&I Community) Implementation (S&I Community)
Implementation (S&I Community) Implementation (S&I Community)
Candidate Standards Analysis
Candidate Standards Analysis
Finalize Actors + Transactions +
Technology Stacks and Standards
Finalize Actors + Transactions +
Technology Stacks and Standards
TW
G 2
: D
ata
Ele
men
t b
ased
access f
or
LD
AF &
TD
AF
Creating Operation Plan for Pilot Testing
Creating Operation Plan for Pilot Testing
Balloting Activities
Pilots and TestingPilots and Testing
Pilots & Testing Pilots & Testing
Create IGCreate IG Creating Operation Plan for Pilot Testing
Creating Operation Plan for Pilot Testing
Pilots & Testing Pilots & Testing
Pilots and Testing
Pilots and Testing
Balloting Activities
Data Element IG Consensus
IHE Trial Implemen
tation Meeting
IHE Trial Implemen
tation Meeting
TW
G 1
: D
ocu
men
t M
eta
data
based
access f
or
LD
AF
& T
DA
F
• 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
Candidate Standards Discussed …
5
• 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.
HQMF v2
6
QED - SWOT
StrengthsNearly same XML as CCD/IHE XPHRIdentical ConstraintsSupports Linkage to Document
WeaknessesNeeds update to Standard (based on DSTU)No Population Level Query SupportNo Pub/Sub Support
OpportunitiesSome limitations removed with StandardRESTful/FHIR Update
ThreatsFHIR Efforts More InterestingLimited Adoption
7
• RESTful QED looking at FHIR as an option to adopt
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
• 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
04/19/23 9
Discussion to narrow down the standards
10
• 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
Standards Selection Criteria
11
Criteria FHIR HL7v2.x HQMFv2 QUICK QED
Questions
12
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
13
Initiative Support Leads• For questions, please feel free to contact your support
leads:– Initiative Coordinator: John Feikema [email protected]– ONC Sponsors: Mera Choi [email protected]– Support Team:
• Project Management: – Gayathri Jayawardena [email protected]
• Technical Support: – Dragon (Nagesh) Bashyam [email protected]
• Standards SME:– Ed Larsen [email protected]
• Standards Support: – Angelique Cortez [email protected]
• Vocabulary and Terminology Subject Matter Expert: – Mark Roche, MD [email protected]
14
