We have received questions regarding "starts after" and what exact time ranges it effects. The issue is that an event that starts concurrently with another (i.e. within the same minute) will not be included, but often times measure developers need to represent this logic. This can be captured in the current QDM but requires multiple statements of logic. A "starts after or concurrent" temporal operator is recommended, to succinctly provide this capability and clarify logic for future measures going forward.

The following example shows the current way of expressing that one event starts after or concurrent with another:

OR:  X starts after Y
OR:  X starts concurrent with Y

Using the "starts after or concurrent with" operator, this can be expressed more succinctly:

X starts after or concurrent with Y