This discussion references short-circuiting and indicates that rule authors should use it to build performant rule logic. Totally agree with the intent, but there is a potential for misunderstanding here, given that since CQL is a query language, not a programming language, this type of short-circuiting will not occur within single expressions like it will with imperative programming languages such as Java, JavaScript, and C#.

In particular, if the tests for `patient is female` and `patient is pregnant` occur within the same expression, implementations will not necessarily short-circuit the evaluation. Reference the discussion on short-circuiting in the CQL specification here: https://cql.hl7.org/02-authorsguide.html#logical-operators

I would recommend expanding this example to provide explicit CQL that will exhibit the desired behavior, as opposed to CQL that would not necessarily short-circuit.