Stream: cql
Topic: Supplemental Data
Jill Doty (Mar 29 2021 at 15:51):
The FHIR Measure resource has a supplementalData field for specifying what additional data to return. However, the FHIR MeasureReport is less clear where the calculated supplemental data should go. The guidance here (http://hl7.org/fhir/clinicalreasoning-quality-reporting.html) specifies using an observation for individuals and adding it to evaluatedResources, but it is unclear how one would differentiate that observation from the the rest.
It additionally does not specify how to store these for a group of patients - this example is provided (http://hl7.org/fhir/measurereport-cms146-cat3-example.html) but I'm not sure how the example including a supplemental data section conforms to the MeasureResult profile.
I've reviewed the https://github.com/DBCG/cqf-ruler implementation of supplemental data and see that supplemental data is always added as an observation resource, both within the evaluatedResources field and within the generic contained field on DomainResource.
Finally, my questions:
- Is there additional guidance for supplemental data that I've missed? I've looked in the cqfmeasure IG as well as davinci-deqm IG without luck.
- Is there a plan for more concrete supplemental data guidance in the future?
Bryn Rhodes (Mar 30 2021 at 19:18):
Hi @Jill Doty , yes, there are a couple resolved trackers related to this that are in the process of being applied to improve the documentation of supplemental data handling. We'll also be adding more examples to help illustrate the expected behavior.
Bryn Rhodes (Mar 30 2021 at 19:19):
Specifically, this tracker: https://jira.hl7.org/browse/FHIR-29807
Richard Stanley (May 31 2021 at 00:36):
In the example at: https://www.hl7.org/fhir/measurereport-cms146-cat1-example.html, supplemental data is returned inline as values. But, my tests show that it is returned as an inline contained Observation (and the path to it doesn't resolve). Might I ask for a helpful hint on how to get the returned values? My use case is to define in CQL define "Hello, World!": 'Hello, World!'
, and then call it in supplemental data with:
"supplementalData": [
{
"code": {
"text": "supplemental-data-example-define"
},
"criteria": {
"language": "text/cql",
"expression": "Hello, World!"
}
}
]
An example MeasureReport is at: https://pastebin.com/aRmhMSft
Edit: I do see it evaluated correctly in the HAPI logs, just not in the MeasureReport, e.g.:
HIVSimpleGender.33:25-33:39(28): Hello, World!
HIVSimpleGender.33:1-33:39(29): Hello, World!
Bryn Rhodes (Jun 10 2021 at 20:32):
Hmmm, the value of that expression is supposed to be included in the value element of the observation for that supplemental data element. Is this still behaving this way on the latest ruler?
JP (Jun 11 2021 at 02:52):
Current ruler only supports codes. Strings are not supported.
Last updated: Apr 12 2022 at 19:14 UTC