The HQMF standard defines timing relationships to operate on effectiveTime. However, attributes (which may have timing elements of their own) are often referenced in eCQM logic. In these situations, what is the currently expected behavior of QDM-based HQMF? Particularly:

• If the QDM attribute is a time element other than effectiveTime (e.g. facility location arrival datetime), does the timing relationship still operate on the effectiveTime of the "base" QDM element?
• If the QDM attribute is not a time element, but has associated time elements (e.g. facility location), does the timing relationship operate on the associated time elements (e.g. facility location arrival/departure datetimes) or the effectiveTime of the "base" QDM element?

I understand there are efforts under way to enhance the flexibility of timing relationship source and target datetimes, however I am specifically interested in the expected behavior of QDM-based HQMF in the existing and published eCQMs (i.e., QDM 4.0/4.1 and HQMF R1).