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

CQL execution errors in an automated process should not require an end user to be notified

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci DTR (FHIR)
    • 1.1.0-ballot [deprecated]
    • Clinical Decision Support
    • Execution of CQL [deprecated]
    • 4.6.2.1, 4.6.2.2
    • Hide

      Current

      4.6.2.1 - "If the CQL is malformed (is not syntactically correct) in any way, the app’s execution engine SHALL NOT attempt any execution of the malformed CQL, the app SHALL log the error, and the user SHALL be notified with an appropriate on-screen message indicating that population did not occur and they SHALL be allowed to enter the information manually either now or at a later time."

      Change to:

      4.6.2.1 - "If the CQL is malformed (is not syntactically correct) in any way, the app’s execution engine SHALL NOT attempt any execution of the malformed CQL, the app SHALL log the error, and the user SHALL be notified with an appropriate message indicating that population did not occur and they SHALL be allowed to enter the information manually either now or at a later time."

      Show
      Current 4.6.2.1 - "If the CQL is malformed (is not syntactically correct) in any way, the app’s execution engine SHALL NOT attempt any execution of the malformed CQL, the app SHALL log the error, and the user SHALL be notified with an appropriate on-screen message indicating that population did not occur and they SHALL be allowed to enter the information manually either now or at a later time." Change to: 4.6.2.1 - "If the CQL is malformed (is not syntactically correct) in any way, the app’s execution engine SHALL NOT attempt any execution of the malformed CQL, the app SHALL log the error, and the user SHALL be notified with an appropriate message indicating that population did not occur and they SHALL be allowed to enter the information manually either now or at a later time."
    • Bob Dieterle / Isaac Vetter : 11-0-0
    • Correction
    • Compatible, substantive

    Description

      4.6.2.1 - "If the CQL is malformed (is not syntactically correct) in any way, the app’s execution engine SHALL NOT attempt any execution of the malformed CQL, the app SHALL log the error, and the user SHALL be notified with an appropriate on-screen message indicating that population did not occur and they SHALL be allowed to enter the information manually either now or at a later time."

      4.6.2.2 - "If any errors are encountered during execution, the app’s engine SHALL NOT attempt any further execution, and the user SHALL be notified with an appropriate on-screen error message."

       

      These sections should include considerations to facilitate automation. Currently they require DTR to always be run in an user-facing workflow by mandating that users SHALL be notified when errors occur.

      Instead, we should note that CQL execution is likely to occur as part of a background process without user intervention. If errors occur in this process they should be logged by the system so that follow-up can performed later.

      Of course, if DTR is actively executing in an end-user workflow, then we should still inform the user of any CQL execution errors.

      Attachments

        Activity

          People

            Unassigned Unassigned
            fswitzer Fred Switzer
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: