Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-36378

Clarify CQL version expectations

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • US Da Vinci DTR (FHIR)
    • 1.0.0 [deprecated]
    • Clinical Decision Support
    • Technical Background and Underlying Technologies [deprecated]
    • Hide

      Document support of the current release of CQL.  If we wish to update the version, we will have to produce a new release of the IG.

      Show
      Document support of the current release of CQL.  If we wish to update the version, we will have to produce a new release of the IG.
    • Bob Dieterle / Ben Hamlin : 9-0-0
    • Correction
    • Non-compatible

    Description

      " Older versions of CQL such as STU 2 can be used provided they work with FHIR R4."

      Who can do that?  Presumably EHRs and SMART apps have to support the full capabilities of the current release, otherwise we won't have interoperability.  Are there any breaking changes between STU 2 or prior releases and the current one?  If so, what happens if someone uses and older version?  Do we understand how systems will determine what version of CQL they're seeing when it's embedded in an extension or found in a library?  We can't support multiple versions unless we know what version we're seeing - and supporting multiple versions add cost.  Is the cost justified?

      Attachments

        Activity

          People

            Unassigned Unassigned
            lloyd Lloyd McKenzie
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: