cbiggs Given how much the human readable has changed since this ticket, I will set to yes and any new findings will result in a new ticket.

kimberlys we believe that this ticket can be closed (SRC = Yes) at this time.

We had 2 outstanding items we had wanted to fix (which, as Stan mentioned in a message below as nice to haves):

• Display in value set and code system elements - released in MADiE 2.1.3 on 2/4/2025
• Primary library should not contain data requirements from child libraries - released in MADiE 2.2.5 on 6/11/2025

If this ticket is complete could you please set SRC = Yes?  Thank you!

MADiE aligns with what is in QM IG STU 5 ballot 2 for mapping of value sets, direct reference codes, code systems and data requirements for measure's effective-data-requirements library.
The code and value sets in question would not meet the criteria for inclusion in data requirements for STU 5. Value sets and direct reference codes (DRCs) not used in retrieves would not appear in data requirements; they would appear in related artifacts or DRC extensions respectively, which map to the terminology section of human readable. That said, the code "AMB" is never referenced in the measure logic, so it would not be included in measure. The referenced value sets are present in the terminology section of the human readable, but the liquid scripts do not retrieve the value set names, though provided.

All of that said, there is an issue to fix for primary library's data requirements in that the primary library brings in the data requirements from the underlying libraries. This is not desirable and can be misleading, but it does not impact execution or what is viewable in human readable.

There would be some nice-to-have display content that could be added for following, but this does not impact human readable:

• value set related artifact entries in underlying library resources (not effective data requirements library)
• code system related artifact entries in underlying library resources (not effective data requirements library)
• value set references in data requirements

Hello Kim,

Bryn confirmed an update is needed to the US Quality Measures (FHIR) specifications. MADiE will incorporate the update in a future release. You can follow the ticket that was created for the specifications update here:

FHIR-40895

MADiE will incorporate the update documented in the ticket above in a future release-this update to MADiE is not dependent on the specifications update being completed. Timing information for this release will be communicated through community calls and the User Group meeting. We are closing this ticket. Let us know if you have any questions.

Thank you

Good morning Kim-

We are still pending a response from Bryn for this ticket. We will provide an update as soon as one is available.

Thank you

Hello Kim-

The team has reached out to Bryn to review your ticket. The team thinks the cause of this issue may be found in the standards. We will provide an update as soon as one is available. 

Thank you

Thank you for adding the export to all three tickets Kim!

See attached.

Hi Kim-

Please also attach the measure package you exported to this ticket so the team can review.

Thank you

Thank you for submitting your question/issue. We will assign this to a team member and respond in one business day. If your question/issue is related to a particular measure, please upload the corresponding measure package.