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

chore: expose constants as public #97

Closed
wants to merge 3 commits into from

Conversation

patburke234
Copy link
Contributor

At NCQA we need to be able to identify extension values that are useful for our measure processing. Specifically in this case, we need to be able to extract the CQL Default Value, CQL Default Value Type, and Type of the parameters using these constants.

@ewoutkramer
Copy link
Member

I'd rename this class from Constants to NcqaExtensionUrls or something, since that's what it is.

This:
public const string MeasureGroupCodeSystem = "https://ncqa.org/fhir/CodeSystem/measure-group"; sounds NCQA specific, so I wonder whether we should hard-code that into the exporter at all. @EvanMachusak what do you think?

I think that before we make these extension urls definitive (or even that codesystem url) - is this something that is simply missing form the current spec and we should urge HL7 to define these extensions in the HL7 space?

@EvanMachusak
Copy link
Collaborator

The group code (https://hl7.org/fhir/r4/measure-definitions.html#Measure.group.code) doesn't have a recommended binding so we invented a CodeSystem in our IG for this.

I agree with you that anything NCQA specific should be removed from the SDK. This is a custom step that we would inject into the packaging process to decorate the Measure resource with information.

@EvanMachusak
Copy link
Collaborator

I am going to close this as #100 supercedes it.

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

Successfully merging this pull request may close these issues.

4 participants