["Encounter, Performed": "Non-Elective Inpatient Encounter"]
Data Element Scope: This value set may use the Quality Data Model (QDM) category related to Encounter. The intent of this data element is to identify non-elective inpatient encounters.
Inclusion Criteria: Includes only relevant concepts associated with SNOMED CT codes representing non-elective inpatient encounters.
Exclusion Criteria: No exclusions.
Constrained to codes in the Encounter, Performed: Non-Elective Inpatient Encounter value set (2.16.840.1.113883.3.117.1.7.1.424)
"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.
A QDM Known Issue has been identified related to this datatype. To see this QDM known Issue, please click here.
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.
diagnoses
Coded diagnoses/problems addressed during the encounter. The diagnoses attribute has three components:
- diagnosis (code)
- presentOnAdmissionIndicator (code)
- rank (positive integer)
To reference an encounter diagnosis, the expression must include the diagnosis code component. The other components are optional. The expression should only include the presentOnAdmissionIndicator if it is necessary to reference present on admission and should only include the rank if it is necessary to reference principal diagnosis.
The "Encounter, Performed" diagnosis attribute is intended to capture ALL diagnoses, including the principal diagnosis, i.e., all diagnoses addressed during the encounter represented by the diagnosis (code) used in the expression.The presentOnAdmissionIndicator (code) allows the eCQM developer to include criteria about whether each specific "Encounter, Performed" diagnosis was present at the time of admission (an indicator used to evaluate patient safety and adverse events). See presentOnAdmissionIndicator attribute definition for information about using the "Encounter, Performed" diagnosis attribute.
The "Encounter, Performed" diagnosis (rank) replaces the principal diagnosis attribute. To reference a principal diagnosis, eCQM developers should express the "Encounter, Performed" diagnosis with a diagnosis (code) and a rank of 1. See definition of rank attribute.
With an "Encounter, Performed" diagnosis, there is no dependency on the timing of the diagnosis in relation to the encounter.
- Use of the "Encounter, Performed": diagnoses attribute component and the "Diagnosis" datatype is redundant for relating the diagnosis to the "Encounter, Performed". The "Encounter, Performed": diagnoses component syntax is preferred.
- Referencing the same diagnosis using "Encounter, Performed" (diagnoses attribute) and "Diagnosis" (datatype) should only occur if the measure must define a specified length of a prevalencePeriod, e.g.,
- The measure must assure that the diagnoses
- have been present for at least some defined time period before the encounter, and
- were addressed during the "Encounter, Performed"
- The measure must assure that the diagnoses
dischargeDisposition
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