["Encounter, Performed": "Patient Provider Interaction"]
Data Element Scope: This value set may use a model element related to Encounter.
Inclusion Criteria: Includes concepts that represent an encounter in an office or care setting, as well as interactions that occur via virtual methods, such as telephone calls, emails, and letters.
Exclusion Criteria: No exclusions.
Constrained to codes in the Encounter, Performed: Patient Provider Interaction value set (2.16.840.1.113883.3.526.3.1012)
"Encounter, Performed"
Data elements that meet criteria using this datatype should document that the encounter indicated by the QDM category and its corresponding value set is in progress or has been completed.
The "Encounter, Performed" participant references the primary participant.
Previous versions of QDM included an attribute principal diagnosis, defined as the condition that, after study, was determined to be the principal cause of the admission. QDM version 5.5 addresses that concept using the diagnosis rank=1.
Timing:
- The relevantPeriod addresses:
- startTime - The time the encounter began (admission time).
- stopTime - The time the encounter ended (discharge time).
- author dateTime references the time the action was recorded.
- Refer to the eCQM expression to determine allowable timings to meet measure criteria.
Notes:
- negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatype-related actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod.
- The locationPeriod is an attribute of the attribute facility location that addresses:
- startTime - the time the patient arrived at the location. The time the encounter began (admission time).
- stopTime - the time the patient departed from the location.
relevantPeriod
Relevant Period addresses the time between the start of an action to the end of an action. Each datatype using relevant period defines specific definitions for the start and stop time for the action listed.
Note: negation rationale indicates a one-time documentation of a reason an activity is not performed. Negation of QDM datatyperelated actions for a reason always use the author dateTime attribute to reference timing and must not use relevantPeriod