Difference between revisions of "DataExchangeforQualityMeasures FHIR IG Proposal"
VietNguyen (talk | contribs) (Created page with "{{subst::Template:FHIR IG Proposal}}") |
|||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 3: | Line 3: | ||
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | ||
<div style="background:#F0F0F0"> | <div style="background:#F0F0F0"> | ||
| − | This page documents a [[:category: | + | This page documents a [[:category:Approved FHIR IGProposal|Approved]] [[:category:FHIR IG Proposal|FHIR IG Proposal]] |
</div> | </div> | ||
</div> | </div> | ||
[[Category:FHIR IG Proposal]] | [[Category:FHIR IG Proposal]] | ||
| − | [[Category: | + | [[Category:Approved FHIR IG Proposal]] |
| Line 13: | Line 13: | ||
| − | = | + | =Data Exchange for Quality Measures= |
| + | |||
| + | <!-- Resource names should meet the following characteristics: | ||
| + | * Title Case | ||
| + | * U.S. English | ||
| + | * Domain-friendly | ||
| + | * Short | ||
| + | * Clear | ||
| + | * Unique | ||
| + | * Avoid non-universal abbreviations (e.g. URL would be ok) | ||
| + | * Be consistent with other similar IGs | ||
| + | --> | ||
| + | |||
| + | =Data Exchange for Quality Measures= | ||
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
| Line 29: | Line 42: | ||
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the IG. --> | <!-- The name of the committee that is proposed to have responsibility for developing and maintaining the IG. --> | ||
| − | [[ | + | [[Clinical Quality Information]] |
==Committee Approval Date:== | ==Committee Approval Date:== | ||
| − | <i>Please enter the date that the committee approved this IGproposal</i> | + | <i><b>TODO</b>Please enter the date that the committee approved this IGproposal</i> |
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
<!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the IG (optional) --> | <!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the IG (optional) --> | ||
| − | * | + | * [[Clinical Decision Support]] |
| − | |||
| − | |||
==FHIR Development Project Insight ID== | ==FHIR Development Project Insight ID== | ||
| − | + | 1429 | |
<!-- Please specify the id of your work group’s PSS for doing FHIR work that covers the development and maintenance of this IG. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | <!-- Please specify the id of your work group’s PSS for doing FHIR work that covers the development and maintenance of this IG. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | ||
==Scope of coverage== | ==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. | ||
<!-- Define the full scope of coverage for the IG. The scope must be clearly delineated such that it does not overlap with any other existing or expected HL7 Int'l-maintained IG. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | <!-- Define the full scope of coverage for the IG. The scope must be clearly delineated such that it does not overlap with any other existing or expected HL7 Int'l-maintained IG. The scope will be used to govern "what is the set of potential applications to consider when evaluating what elements are 'core' – i.e. in the 80%" | ||
| Line 58: | Line 70: | ||
==IG Purpose== | ==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. | ||
<!-- Why is this IG necessary? --> | <!-- Why is this IG necessary? --> | ||
==Content location== | ==Content location== | ||
| + | https://github.com/HL7/data-exchange-for-quality-measures | ||
<!-- What is the path within the HL7 github repository (i.e. https://github.com/HL7/xxx) or what is the Simplifier project name? --> | <!-- What is the path within the HL7 github repository (i.e. https://github.com/HL7/xxx) or what is the Simplifier project name? --> | ||
| − | |||
==Proposed IG realm and code== | ==Proposed IG realm and code== | ||
| + | us/davinci-deqm | ||
<!-- What is the realm code (2-character country code or 'uv') and IG code to use for the path when the IG is published under http://hl7.org/fhir? E.g. us/ccda --> | <!-- What is the realm code (2-character country code or 'uv') and IG code to use for the path when the IG is published under http://hl7.org/fhir? E.g. us/ccda --> | ||
==Maintenance Plan== | ==Maintenance Plan== | ||
| + | This specification will be maintained by the CQI work group once the Da Vinci project has completed initial development. | ||
<!-- What commitment does the WG have to maintaining this IG as the FHIR core specification continues to evolve - particularly if the initial project sponsors are no longer providing resources --> | <!-- What commitment does the WG have to maintaining this IG as the FHIR core specification continues to evolve - particularly if the initial project sponsors are no longer providing resources --> | ||
==Short Description== | ==Short Description== | ||
| + | Provides a mechanism for healthcare providers and data aggregators to exchange quality measure information using subscription, query, and push methods. | ||
<!-- 1-2 sentences describing the purpose/scope of the IG for inclusion in the registry --> | <!-- 1-2 sentences describing the purpose/scope of the IG for inclusion in the registry --> | ||
| − | |||
==Long Description== | ==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 which provides a framework to enable the Exchange of Quality Measure Data between Data "Aggregators" (organizations that want to evaluate quality measures) and Providers (organizations that deliver care to patients). This guide describes three methods of exchanging data quality and the specific use case of 30-Day Medication Reconciliation Post-Discharge will demonstrate how one of these method can be implemented to exchange the MRP measure data. This IG will span both FHIR STU3 and R4 with additional guidance for backward compatibility with STU3. A future release of this guide will include all the R4 artifacts when then US Core and QI Core profiles and the DEQM Profiles derived from them have been defined. | ||
<!-- 1 paragraph describing the purpose/scope of the IG in more detail for inclusion in the version history --> | <!-- 1 paragraph describing the purpose/scope of the IG in more detail for inclusion in the version history --> | ||
| − | |||
==Involved parties== | ==Involved parties== | ||
| + | This implementation guide has been developed by U.S. EHR and Payor organizations as part of the Da Vinci project. | ||
<!-- 1 paragraph describing who is sponsoring or involved in creating the IG for inclusion in the version history --> | <!-- 1 paragraph describing who is sponsoring or involved in creating the IG for inclusion in the version history --> | ||
| Line 90: | Line 106: | ||
==Expected implementations== | ==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 . | ||
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | <!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | ||
==Content sources== | ==Content sources== | ||
| + | Requirements are drawn from payor and provider organizations as part of the Da Vinci initiative. Additional guidance come from quality measure authors. | ||
<!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult | <!-- List all of the specifications (beyond those in the "standard" (FHIR_Design_Requirements_Sources) list of source specifications) that you’re planning to consult | ||
| Line 99: | Line 117: | ||
==Example Scenarios== | ==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. | ||
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this IG. They should demonstrate the full scope of the IG and allow exercising of the IG's capabilities (all profiles, different types of applications, etc.) --> | <!-- Provide a listing of the types of scenarios to be represented in the examples produced for this IG. They should demonstrate the full scope of the IG and allow exercising of the IG's capabilities (all profiles, different types of applications, etc.) --> | ||
| Line 104: | Line 127: | ||
==IG Relationships== | ==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. | ||
<!-- Are there any IGs this resource depends on or that depend on this IG? --> | <!-- Are there any IGs this resource depends on or that depend on this IG? --> | ||
==Timelines== | ==Timelines== | ||
| + | The intention is to perform initial balloting of the IG in the Sept. 20. | ||
<!-- Indicate the target date for having the IGcomplete from a committee perspective and ready for vetting and voting --> | <!-- Indicate the target date for having the IGcomplete from a committee perspective and ready for vetting and voting --> | ||
| Line 114: | Line 139: | ||
==FMG Notes== | ==FMG Notes== | ||
| + | Approved 2018-07-11 | ||
Latest revision as of 08:29, 18 August 2018
This page documents a Approved FHIR IG Proposal
Contents
- 1 Data Exchange for Quality Measures
- 2 Data Exchange for Quality Measures
- 2.1 Owning work group name
- 2.2 Committee Approval Date:
- 2.3 Contributing or Reviewing Work Groups
- 2.4 FHIR Development Project Insight ID
- 2.5 Scope of coverage
- 2.6 IG Purpose
- 2.7 Content location
- 2.8 Proposed IG realm and code
- 2.9 Maintenance Plan
- 2.10 Short Description
- 2.11 Long Description
- 2.12 Involved parties
- 2.13 Expected implementations
- 2.14 Content sources
- 2.15 Example Scenarios
- 2.16 IG Relationships
- 2.17 Timelines
- 2.18 When IG Proposal Is Complete
- 2.19 FMG Notes
Data Exchange for Quality Measures
Data Exchange for Quality Measures
Owning work group name
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 which provides a framework to enable the Exchange of Quality Measure Data between Data "Aggregators" (organizations that want to evaluate quality measures) and Providers (organizations that deliver care to patients). This guide describes three methods of exchanging data quality and the specific use case of 30-Day Medication Reconciliation Post-Discharge will demonstrate how one of these method can be implemented to exchange the MRP measure data. This IG will span both FHIR STU3 and R4 with additional guidance for backward compatibility with STU3. A future release of this guide will include all the R4 artifacts when then US Core and QI Core profiles and the DEQM Profiles derived from them have been defined.
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
Approved 2018-07-11
