CQL Malformed specifics need defining - DTR #27

XMLWordPrintableJSON

    • Type: Change Request
    • Resolution: Persuasive with Modification
    • Priority: Medium
    • US Da Vinci DTR (FHIR)
    • STU3
    • Clinical Decision Support
    • (profiles) [deprecated]
    • Execution of CQL
    • Hide

      Add to gujide: We will use the standard that if the CQL cannot be executed by the CQL engine in the SMART on FHIR app or in the capable EMR then it is considered a CQL failure (the CQL author should be taking into account the capability of the CQL engine in desigining their CQL for execution).

      Show
      Add to gujide: We will use the standard that if the CQL cannot be executed by the CQL engine in the SMART on FHIR app or in the capable EMR then it is considered a CQL failure (the CQL author should be taking into account the capability of the CQL engine in desigining their CQL for execution).
    • Bob Dieterle / Rachael Foerster: 7-0-1
    • Clarification
    • Non-substantive

      Existing Wording: If the CQL is malformed (is not syntactically correct) in any way, the execution engine SHALL not attempt any execution, and the user SHALL be notified with an appropriate on screen error message. The application SHALL log failures and ensure the maintainer of the CQL/Questionnaire package is notified. To Commenters: The method of ensuring the maintainer is notified should probably be further specified.

      Comment:

      Define malformed, is there a specified set of rules? How will it be executed and against what rules, structure versus content?

      Summary:

      CQL Malformed specifics need defining

            Assignee:
            Unassigned
            Reporter:
            George Dixon
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: