1. Da Vinci Connectathon Clinical Reasoning Track Orientation
Wednesday, May 29th & Thursday, May 30th, 2019
Jacksonville, FL
Track Leads: Nikolai Schwertner, Michael O’Keefe

2. Connectathon Overview
FHIR Connectathon Objectives
Track Selection/Registration
Timeline
Participant Opportunities
Clinical Reasoning Track Overview
How to get your questions answered

3. What’s to be gained by attending a FHIR Connectathon?
Join a community of FHIR users
Develop and test your system
Refine Da Vinci Specifications and Use Cases
Demonstrate what’s possible

4. Registration and Track Selection
Add contact details/scenario interests and roles to the Connectathon Confluence page
Connect with your track lead(s) in advance
We recommend participating fully in only one track

5. Timeline of Activities
One Month Prior: Registration
1-3 weeks prior: Track Orientation Meeting
On-Site
Wednesday
8:30-9:00 AM: Registration
9:00 AM-5:00 PM: Connectathon activities
Thursday
9:00 AM-11:00 AM: Connectathon activities
11:00 AM-12:00 PM: Wrap-up/demos

6. Participant Opportunities
Join in the community
Bring Questions and share your challenges
Help others by sharing your knowledge
Bring your development system ready to go
Have your application installed
Have your environment configured
Raise questions that identify hot topics
Record your Results
What happens at Connectathon stays at Connectathon.
It’s OK to fail.

7. Location of Reference Materials
FHIR Specifications:
R4 final:
STU3 final:
Track Definition
Connectathon Manager (Conman)
FHIR Chat:

8. How to Get your Questions Answered
FHIR Chat:
mgmt/topic/Clinical.20Reasoning.20Track
Track Leads:
Michael O’Keefe
Nikolai Schwertner
On Site Issues: Sandy Vance

9. Intro to Clinical Reasoning Track
Track Definition
List of participating systems in the track
References to the servers & clients for the track
Goals for this track

10. Track Definition Quality Data Model -> QI-Core Mapping
Colorectal Cancer Screening
Venous Thromboembolism (VTE) Prophylaxis

11. QDM -> QI-Core
Test quality reporting submission using the FHIR MeasureReport resource for a focused set of program measures and based on the Cypress tooling
Support evaluation of CMS program measures in a FHIR environment using:
Translation of QDM-based CQL measures to QI Core-based CQL

12. CQF Measures http://hl7.org/fhir/us/cqfmeasures/2019May/
Balloted Quality Measure Implementation Guide
Contains Example Screening Measures
Breast Cancer Screening (EXM125)
Cervical Cancer Screening (EXM124)
Colorectal Cancer Screening (EXM130)
Venous Thromboembolism Prophylaxis (VTE-1)
Will use the May2018 ValueSets (not the addendum)
Based on the published CMS Program Measures
Test data, Measure definitions, and upload scripts are posted here:

13. Track Resources Quality Measure Evaluation Server:
Apelon Terminology Server:
(cc to request credentials
Interopion (HSPC Sandboxes)
MITRE (TestScripts)

14. MITRE TestScripts Exploring what a FHIR-based Cypress looks like
Focusing on Reporting and Submission
$data-requirements, $submit-data, $collect-data
$evaluate-measure (individual, patient-list, population)

15. Track Goals
Primary:
Validate quality reporting results using a FHIR MeasureReport resource
Demonstrate evaluation of a QI Core-based VTE measure against a FHIR server
Secondary:
Demonstrate submission of 30-day medication reconciliation data in response to a medication reconciliation occurring
Demonstrate submission of a set of Colorectal Cancer screening results

16. Discussion & Questions

17. Next Steps

18. Action Items Finish Ensuring measure evaluation (DCG/MITRE)
Operations to Test
ValueSet/$cache
Library/$cache-terminology
Measure/$cache-terminology