-
Notifications
You must be signed in to change notification settings - Fork 121
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
Contexts should have type specifiers #1273
Labels
cql
The issue relates to or requires a change or clarification on the CQL specification
Comments
@brynrhodes - This requires a change to the ELM spec, possible candidate for CQL 2.0 |
Funny, I was thinking about this just last week as well, wanted to started a discussion, until I realized we are probably just supposed to use Element's |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The context definition in a library does not have its TypeSpecifier (presumably a NamedTypeSpecifier) populated.
We need a qualified string here telling us that Patient is
{http:https://hl7.org/fhir}Patient
so we can differentiate it from other models that define a type calledPatient
in use in the same library.The text was updated successfully, but these errors were encountered: