This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "DataExchangeforQualityMeasures FHIR IG Proposal"

From HL7Wiki
Jump to navigation Jump to search
Line 145: Line 145:
  
 
This IG outlines three methods for the data exchange: subscription, query/request, and push.  In each case below, the [id] is the profile for a specific measure.
 
This IG outlines three methods for the data exchange: subscription, query/request, and push.  In each case below, the [id] is the profile for a specific measure.
* In the subscription method, an aggregator system subscribes to a specific measure on a provider system. When measure data is generated on the provider system, the provider system performs a POST Measure/[id]/$submit-data operation on an aggregator system
+
* In the subscription method, an aggregator system subscribes to a specific measure on a provider system. When measure data is generated on the provider system, the provider system will notify the aggregator via the subscription callback, and the aggregator will then query the provider system using the query/request method.
* In the query/request method, an aggregator system queries a Measure/[id]/$collect-data operation and passes parameters for the query. The provider system returns an operation response with the applicable FHIR resources.
+
* In the query/request method, an aggregator system will invoke the Measure/[id]/$collect-data operation and passes parameters for the query. The provider system returns an operation response with the applicable FHIR resources.
 
* In the push method, after measure data is generated, the provider system performs a POST Measure/[id]/$submit-data operation to send data to an aggregator system.  
 
* In the push method, after measure data is generated, the provider system performs a POST Measure/[id]/$submit-data operation to send data to an aggregator system.  
  

Revision as of 19:36, 6 July 2018



Data Exchange for Quality Measures

==




Data Exchange for Quality Measures

Owning work group name

Clinical Quality Information

Committee Approval Date:

TODOPlease enter the date that the committee approved this IGproposal

Contributing or Reviewing Work Groups

FHIR Development Project Insight ID

1429

Scope of coverage

This IG is specific to the US Human exchange of data for quality measures across al healthcare disciplines. Its purpose is inpatient; outpatient; and primary, secondary and tertiary care settings. The content is developed by stakeholders including clinical care provider, EHR vendor, and payor representatives.

IG Purpose

As the US Healthcare system transitions from a fee-for-service payment model to a value-based-care (VBC) model, the authoring, collection and reporting of quality measures is essential to this new model. Currently, disparate methods, both propriety and non-proprietary, are used to collect, aggregate and report quality measures data. This implementation guide leverages the interoperability of FHIR to create a framework for the timely and standardized method for exchanging this data. By shortening the feedback loop of quality measures data, the framework can support activities such as closing gaps in care. Main IG will address the general framework for data exchange of quality measures. The framework will be exemplified in the specific use case of “30-Day Medication Reconciliation Post-Discharge,” for which the guide will implementation details including profiles and operations.

Content location

https://github.com/HL7/data-exchange-for-quality-measures

Proposed IG realm and code

us/davinci-deqm

Maintenance Plan

This specification will be maintained by the CQI work group once the Da Vinci project has completed initial development.

Short Description

Provides a mechanism for healthcare providers and data aggregators to exchange quality measure information using subscription, query, and push methods.

Long Description

The Data Exchange for Quality Measures Implementation Guide (IG) will provide guidance to implementers who wish to request and report clinical and administrative data using FHIR resources and operations in support of quality measure reporting. The main IG will detail the base and profiled FHIR resources and operations for three methods of exchanging data. Additionally, the specific use case of 30-Day Medication Reconciliation Post-Discharge will demonstrate how one of the three methods can be implemented to exchange measure data. Through the framework of this base implementation guide, stakeholders will have a consistent approach to creating FHIR profiles and utilizing FHIR operations to exchange quality measures data. This IG will be based on FHIR R4 with additional guidance for backward compatibility with STU3.

Involved parties

This implementation guide has been developed by U.S. EHR and Payor organizations as part of the Da Vinci project.


Expected implementations

In addition to a pilot reference implementation and testing at the Sept. 2018 and Jan. 2019 WGMs, several EHR and Payor organizations are expected to implement this implementation guide prior to the end of 2019 .

Content sources

Requirements are drawn from payor and provider organizations as part of the Da Vinci initiative. Additional guidance come from quality measure authors.

Example Scenarios

This IG outlines three methods for the data exchange: subscription, query/request, and push. In each case below, the [id] is the profile for a specific measure.

  • In the subscription method, an aggregator system subscribes to a specific measure on a provider system. When measure data is generated on the provider system, the provider system will notify the aggregator via the subscription callback, and the aggregator will then query the provider system using the query/request method.
  • In the query/request method, an aggregator system will invoke the Measure/[id]/$collect-data operation and passes parameters for the query. The provider system returns an operation response with the applicable FHIR resources.
  • In the push method, after measure data is generated, the provider system performs a POST Measure/[id]/$submit-data operation to send data to an aggregator system.


IG Relationships

This implementation guide will be "aligned" with US Core and will eventually be derived from US Core once that IG has been updated to align with FHIR R4.

Timelines

The intention is to perform initial balloting of the IG in the Sept. 20.

When IG Proposal Is Complete

When you have completed your proposal, please send an email to FMGcontact@HL7.org

FMG Notes