Contexts should have type specifiers

[EvanMachusak]

The context definition in a library does not have its TypeSpecifier (presumably a NamedTypeSpecifier) populated.

"contexts": {
      "type": "Library$Contexts",
      "def": [
        {
          "type": "ContextDef",
          "locator": "7:1-7:15",
          "name": "Patient"
        },
        {
          "type": "ContextDef",
          "locator": "12:1-12:18",
          "name": "Unfiltered"
        }
      ]
    }

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.

[JPercival]

@brynrhodes - This requires a change to the ELM spec, possible candidate for CQL 2.0

[ewoutkramer]

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 ;-)