v1.3.3

What's Changed

• Check if dataRequirement resourceType does not have patient search params by @elsaperelli in #289
• Not Equal and Not Equivalent clause coverage calculation handling by @elsaperelli in #291
• v1.3.3 by @hossenlopp in #292

Notice of Clause Coverage Percentage Changes

In this release, an issue with the coverage percentage calculation for Not Equivalent clauses was fixed. When a !~ (Not Equivalent) clause is translated from CQL to ELM, it results in separate Not and Equivalent clauses, each with their own localId. This caused coverage percentage calculation to only reach 100% if both of these pieces of logic evaluated to true. With this update, only the Not clause is factored into the coverage percentage calculation, allowing users to reach 100% without both equivalent and not-equivalent data in test cases.

With the current version of the cql-to-elm translator, this is not a problem for != Not Equal clauses. The Not and the Equal are still separated by the translator, but only the Not clause has a localId; therefore, the Equal clause is not factored into the coverage percentage calculation and users can reach 100%. The lack of a localId on the Equal clause will be fixed by the translator in a future update. We account for this upcoming fix by including handling for both of these cases.

This change only affects the coverage percentage calculation and does not change visual highlighting of coverage.

Reminder

Some aliases, unions and library references will show visually as uncovered. These are caused by quirks in the ELM annotation and do not affect the coverage percentage calculation.

Full Changelog: v1.3.2...v1.3.3