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

Dependent Library references in main Library different from measure bundle entries #47

Open
elsaperelli opened this issue Jan 9, 2024 · 1 comment

Comments

@elsaperelli
Copy link

Hello! I noticed some inconsistencies in the dependent Libraries in measure bundles in the measure directory (bundle/measure) and was wondering if they were intentional. It seems like the resource field for relatedArtifacts for the main Library in these measure bundles are different from the url of the dependent Libraries in the measure bundle. For example, in CesareanBirthFHIR-bundle.json, the main library, CesareanBirthFHIR, has Libraries in its relatedArtifacts array. Library CQMCommon is referenced in this array with the following resource attribute: http://ecqi.healthit.gov/ecqms/Library/CQMCommon%7C2.0.000. However, the Library CQMCommon entry in the measure bundle has the following url: https://madie.cms.gov/Library/CQMCommon. Is there a reason why these are different? Thanks!

@hossenlopp
Copy link

Just wanted to bump this issue thread as this was still an issue with the bundles in bundles/measure for the September 2024 Connectathon. The Library resources all use https://madie.cms.gov/Library for their urls while they reference other libraries with http://ecqi.healthit.gov/ecqms/Library URLs. This causes an issue for systems that rely on these canonical url references to be correct.

Additionally, the FHIR (http://fhir.org/guides/cqf/common/Library/FHIR-ModelInfo) and QICore (http://hl7.org/fhir/Library/QICore-ModelInfo) model information libraries are referenced by the measures and libraries but are not included in the bundles. While these are not hard to find and upload to a system that might want them to exist when resolving dependencies for an operation, it may be helpful for them to be included in the packages.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants