Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Measure Resources should assume 'Boolean' based if not specified #536

Closed
Capt-Mac opened this issue Sep 27, 2024 · 0 comments · Fixed by #533
Closed

Measure Resources should assume 'Boolean' based if not specified #536

Capt-Mac opened this issue Sep 27, 2024 · 0 comments · Fixed by #533
Assignees
Labels
bug Something isn't working dQM

Comments

@Capt-Mac
Copy link
Contributor

Description

Measure resources have the ability to specify on what basis they will be evaluated as for population counts in a Measure Report.

Specification defined this with the following extension: http://hl7.org/fhir/us/cqfmeasures/StructureDefinition/cqfm-populationBasis

When this extension is specified on a Measure resource it communicates whether it is a "boolean" based measure or a resource based measure like "encounter".

Issue

When the Measure does not specify the populationBasis of the measure, the MeasureEvaluator.class assumes it is a "resource" based Measure. The default behavior should assume "boolean" based populations if the extension is not populated to communicate otherwise.

This could cause unforeseen behavior in population counts as a result, where resources are counted instead of subjects. Or cause exclusion logic to incorrectly remove counts from other populations.

@Capt-Mac Capt-Mac added bug Something isn't working dQM labels Sep 27, 2024
@Capt-Mac Capt-Mac self-assigned this Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working dQM
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant