Existing Wording: If the CQL is malformed (is not syntactically correct) in any way, the app's execution engine SHALL not attempt any execution, and the user SHALL be notified with an appropriate on screen error message.

Comment:

This worst case scenario describes a pretty lousy user experience for a clinician. During ordering, a clinician receives an interruptive prompt to open an app, the app opens, spins for a bit as it download a CQL library and then displays an appropriate error informing the clinician that the "Payer CQL is malformed". What should the clinician do with that information? Is that an example of an appropriate error? It would be better for the app link card to have never appeared to the user if the app wasn't usuable. Why is the error message a SHALL, but logging errors a SHOULD?

Summary:

Error message: the payer's CQL is malformed?