Continue the testing and use of the Data Exchange for Quality Measures (DEQM IG) for gaps in care reporting use cases using FHIR-based eCQMs
The Gaps in Care/Member Attribution Track will be combined with the Clinical Reasoning Track in this Connectathon.
Gaps in Care/Member Attribution Track orientation: 12/3/2020 2pm ET (see here for meeting information)
To find us at the Connectathon - please go to the Clinical Reasoning Track through Whova.
Testing an Implementation Guide
Submitting Work Group/Project/Accelerator/Affiliate/Implementer Group
Yan Heras (firstname.lastname@example.org), Rob Reynolds (email@example.com)
Specification(s) this track uses
Artifacts of focus
Clinical input requested (if any)
Clinical review of the input parameters for generating the Care Gaps report and expected results in the payload.
Patient input requested (if any)
Da Vinci Gaps in Care Track stream under connectathon mgmt
Clinical Reasoning Track Zoom Link
Track Orientation Date
December 3rd, 2020
Track Orientation Details
Gaps in Care/Member Attribution Track Orientation 12/3/2020 (2pm ET), click here for GotoMeeting details
See the 2021-01 Clinical Reasoning Track page for information about the Clinical Reasoning Track Orientation.
System Roles (Gaps in Care)
Systems capable of playing these roles should implement the exchange and reporting scenarios as described in the Data Exchange for Quality Measures implementation guide.
The CQF Ruler, a reference implementation of FHIR Clinical Reasoning based on the HAPI FHIR Server is available to either play the Consumer or Receiver, or to help guide and test implementations in preparation for the track.
A test instance of the CQF Ruler is available here: https://gic-sandbox.alphora.com. This testing instance is subject to change throughout the event.
Scenario: End-to-End Gaps in Care Reporting
Action: A Client calls the $care-gaps operation using the Colorectal Cancer Screening measure and receives the gaps in care report from the Server. The Client uses the $collect-data or $submit-data operation to gather data-of-interest that would close the open gap and submit to the Server. The Client then calls the $care-gaps operation again for the Colorectal Cancer Screening measure using the same set of in parameters. The Client uses the $submit-data operation to send the summary measure report
Precondition: The Server knows the patient and has appropriate measure data for the patient to produce gaps in care report. The Server supports measure calculations for the measure of interest and is able to generate summary report
Success Criteria: The end to end is successful
Bonus point: Run for additional measure(s)
Scenario: Test the updated GIC profiles/operation incorporating changes applied from the DEQM IG September 2020 ballot reconciliation
Action: A Client calls the $care-gaps operation to request a gaps in care report from the Server, using various combinations of the $care-gaps in parameters
Precondition: The Server knows the patient and has appropriate measure data for the patient to produce gaps in care report.
Success Criteria: The Client receives the gaps in care report as expected based on the in parameters provided to the $care-gaps operation and successfully processes the data
Scenario: Test the use of ATR IG to attribute members when create a gaps in care report
Action: A Client calls the $care-gaps operation for a specific Group from the Server. The Server gets a pre-configured Group. The Server returns gaps in care report for the Group, which shows open and/or closed gaps for each patient in the Group for the Colorectal Cancer Screening measure.
Precondition: Group is pre-configured on both Gaps in Care Server and Member Attribution Server.
Success Criteria: The gaps in care Client receives gaps in care report for the Group
Bonus point: Using Bulk data to test the scenario
TestScript(s): All testing materials can be accessed from the DA Vinci Gaps in care GitHub Repository: https://github.com/dbcg/davinci-gic. These testing materials are subject to change throughout the event.
Security and Privacy Considerations: The scenarios and reference implementations here run using open (i.e. unsecured) connections. Systems SHALL NOT use PHI in any form, or data derived directly from PHI.