You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need a qualified string here telling us that Patient is {http://hl7.org/fhir}Patient so we can differentiate it from other models that define a type called Patient in use in the same library.
The text was updated successfully, but these errors were encountered:
EvanMachusak
changed the title
Contexts should have resultTypeSpecifiers
Contexts should have type specifiers
Nov 6, 2023
JPercival
added
the
cql
The issue relates to or requires a change or clarification on the CQL specification
label
Nov 6, 2023
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 resultTypeSpecifier for that. At least, that's what I have done now. Works for us, @EvanMachusak ;-)
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://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: