Recommended update: Add two operators to streamline logic that identifies the events of interest in a measure.

The 2014 Stage 2 CQMs struggled to implement the concept of an event occurrence within the current QDM infrastructure. While helpful to specify requirements for measurement in some cases, inconsistent implementation of occurrences has occurred in the absence of a more specific means to convey if an event must satisfy all or any criteria. The “SATISIFIES ANY” and “SATISIFIES ALL” operators serve as an alternative to the current inconsistent usage of occurrences by providing a way to set a list of criteria that an event must meet. They specify a way to filter a given set of events to only the subset that is of interest at that point in the logic. This ability is present in the current QDM, but requires several redundant statements and use of occurrences to represent effectively. Consider the following QDM logic:

AND: Occurrence A of “Encounter X” starts before start of FIRST “Encounter Y”
AND: Occurrence A of “Encounter X” starts after start of “Encounter Z”
AND: Occurrence A of “Encounter X (length of stay <= 3 day(s))”

We see that “Occurrence A” exists to ensure the instances of “Encounter X” meet all the criteria. This can be simplified to the following measure logic:

AND: “Encounter X” SATISFIES ALL
	starts before start of FIRST “Encounter Y”
	starts after start of “Encounter Z”
	(length of stay <= 3 day(s))

These operators clearly show that the measure requires “Encounter X” events that match the given criteria.