Difference between revisions of "MeasureReport FHIR Resource Proposal"
Bryn rhodes (talk | contribs) |
Bryn rhodes (talk | contribs) |
||
| (5 intermediate revisions by 2 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:Pending FHIR Resource Proposal| | + | This page documents a [[:category:Pending FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] |
</div> | </div> | ||
</div> | </div> | ||
[[Category:FHIR Resource Proposal]] | [[Category:FHIR Resource Proposal]] | ||
| − | [[Category: | + | [[Category:Approved FHIR Resource Proposal]] |
| Line 14: | Line 14: | ||
=MeasureReport= | =MeasureReport= | ||
| + | |||
| + | The MeasureReport resource represents the results of calculating a clinical quality measure. The _evaluate_ operation of the Measure resource is defined to return a MeasureReport. The resource is capable of representing three different levels of report: patient-level, patient-list, and summary. | ||
| + | |||
| + | The resource is based on the [http://www.hl7.org/implement/standards/product_brief.cfm?product_id=35 HL7 CDA R2 Implementation Guide: Quality Reporting Document Architecture - Category 1 (QRDA I) DSTU Release 3 (US Realm)] and the [http://www.hl7.org/implement/standards/product_brief.cfm?product_id=286 HL7 Implementation Guide for CDA Release 2: Quality Reporting Document Architecture - Category III (QRDA III), DSTU Release 1] implementation guides. | ||
| + | |||
| + | The resource is differentiated from a general purpose query result because it communicates specific information related to quality measurement evaluation that would be difficult to convey generally without imposing some other structure on top of the general results. A more generic result container would certainly be useful, and perhaps the MeasureReport could be a profile of that more general resource? | ||
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
| Line 34: | Line 40: | ||
==Committee Approval Date:== | ==Committee Approval Date:== | ||
| − | + | ||
| + | * The resource proposal was approved on 2016-03-18 [http://www.hl7.org/Special/committees/_common/documentProperties.cfm?wg_document_id=17246&returnHREF=%2FSpecial%2Fcommittees%2Fcqi%2Fminutes%2Ecfm%3F minutes]. | ||
| + | * STU3 Ballot Submission: 2016-08-05 | ||
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
| Line 56: | Line 64: | ||
As a rule, resources should encompass all of these aspects. | As a rule, resources should encompass all of these aspects. | ||
--> | --> | ||
| + | |||
| + | The MeasureReport resource represents the results of calculating a Measure. It may be specific to a patient, or it may be a patient-listing or population-level report. As with the Measure resource, the structure is flexible enough to be used to capture a broad range of clinical quality measurement reporting scenarios and can be used to report in any discipline and locale. | ||
| + | |||
| + | The resource is intended to be used by quality measurement reporting agencies and healthcare delivery systems to facilitate the communication of quality measurement results. | ||
==RIM scope== | ==RIM scope== | ||
<!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | <!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | ||
| + | |||
| + | <!-- I believe this maps to Document in the RIM. --> | ||
==Resource appropriateness== | ==Resource appropriateness== | ||
| Line 75: | Line 89: | ||
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | * Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | ||
--> | --> | ||
| + | |||
| + | The Quality Reporting Document Architecture specifications define a standard mechanism for communicating the results of quality measurement calculation for HL7 V3 standards. Enabling those results to be represented as a FHIR resource will extend the reach of quality measurement reporting. In addition, defining the content as a FHIR resource will allow implementers to use the FHIR stack and all its associated tooling and specifications to facilitate quality reporting, effectively enabling another potential role of a FHIR server as a Quality Reporting Service. | ||
==Expected implementations== | ==Expected 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. --> | <!--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. --> | ||
| + | |||
| + | In addition to general interest from the Quality Measurement community, several vendors have expressed interest in using the Measure and MeasureReport resources to enable various quality measurement and quality reporting scenarios. | ||
==Content sources== | ==Content sources== | ||
| Line 107: | Line 125: | ||
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | ||
--> | --> | ||
| + | |||
| + | The MeasureReport resource will reference the [http://hl7.org/fhir/2016May/measure.html Measure] resource to identify the measure being reported. | ||
==Timelines== | ==Timelines== | ||
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | <!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | ||
| + | |||
| + | May 2016 Ballot Cycle in support of the [http://hl7.org/fhir/2016May/cqif/cqif.html CQF IG]. | ||
==gForge Users== | ==gForge Users== | ||
<!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | <!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | ||
| − | + | brynrhodes | |
| − | |||
| − | |||
Latest revision as of 15:05, 21 August 2017
This page documents a Approved FHIR Resource Proposal
Contents
- 1 MeasureReport
- 1.1 Owning committee name
- 1.2 Committee Approval Date:
- 1.3 Contributing or Reviewing Work Groups
- 1.4 FHIR Resource Development Project Insight ID
- 1.5 Scope of coverage
- 1.6 RIM scope
- 1.7 Resource appropriateness
- 1.8 Expected implementations
- 1.9 Content sources
- 1.10 Example Scenarios
- 1.11 Resource Relationships
- 1.12 Timelines
- 1.13 gForge Users
MeasureReport
The MeasureReport resource represents the results of calculating a clinical quality measure. The _evaluate_ operation of the Measure resource is defined to return a MeasureReport. The resource is capable of representing three different levels of report: patient-level, patient-list, and summary.
The resource is based on the HL7 CDA R2 Implementation Guide: Quality Reporting Document Architecture - Category 1 (QRDA I) DSTU Release 3 (US Realm) and the HL7 Implementation Guide for CDA Release 2: Quality Reporting Document Architecture - Category III (QRDA III), DSTU Release 1 implementation guides.
The resource is differentiated from a general purpose query result because it communicates specific information related to quality measurement evaluation that would be difficult to convey generally without imposing some other structure on top of the general results. A more generic result container would certainly be useful, and perhaps the MeasureReport could be a profile of that more general resource?
Owning committee name
Clinical Quality Information Work Group
Committee Approval Date:
- The resource proposal was approved on 2016-03-18 minutes.
- STU3 Ballot Submission: 2016-08-05
Contributing or Reviewing Work Groups
FHIR Resource Development Project Insight ID
1234: FHIR-Based Clinical Quality Framework (CQF-on-FHIR)
Scope of coverage
The MeasureReport resource represents the results of calculating a Measure. It may be specific to a patient, or it may be a patient-listing or population-level report. As with the Measure resource, the structure is flexible enough to be used to capture a broad range of clinical quality measurement reporting scenarios and can be used to report in any discipline and locale.
The resource is intended to be used by quality measurement reporting agencies and healthcare delivery systems to facilitate the communication of quality measurement results.
RIM scope
Resource appropriateness
The Quality Reporting Document Architecture specifications define a standard mechanism for communicating the results of quality measurement calculation for HL7 V3 standards. Enabling those results to be represented as a FHIR resource will extend the reach of quality measurement reporting. In addition, defining the content as a FHIR resource will allow implementers to use the FHIR stack and all its associated tooling and specifications to facilitate quality reporting, effectively enabling another potential role of a FHIR server as a Quality Reporting Service.
Expected implementations
In addition to general interest from the Quality Measurement community, several vendors have expressed interest in using the Measure and MeasureReport resources to enable various quality measurement and quality reporting scenarios.
Content sources
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? -->
- Clinical Quality Common Metadata Conceptual Model
- Clinical Decision Support Knowledge Artifact Specification
- Health Quality Measure Format
- QRDA Category I
- QRDA Category III
Example Scenarios
Resource Relationships
The MeasureReport resource will reference the Measure resource to identify the measure being reported.
Timelines
May 2016 Ballot Cycle in support of the CQF IG.
gForge Users
brynrhodes
