Inbound ADT Interface / Vocera Data Requirements |
Vocera uses ADT events to derive patient visit information. Vocera relies on being able to uniquely identify patients to properly identify a single inpatient visit/admission/encounter.
An inpatient visit/admission/encounter is comprised of a single admission data followed by a single discharge date. Same day admissions must also be captured.
Improper identification of patient visits will result in number of admissions/visits in Vocera not correlating closely to actual number of admissions/visits across the health system. It will also result in Vocera showing incorrect admission duration (i.e., the duration between admit date and discharge date) for a given visit.
Patient visits will be derived from related chronological patient events (or ADT events) for a given unique patient. A patient visit will start with a patient admit event (or equivalent) and end with a patient discharge event (or equivalent). For example, the most simple scenario will consists of A01 (Admit/Visit Notification) event chronologically followed by A03 (Discharge/End Visit) event for a unique patient.
A health system’s use of ADT event types for representing physical patient event is often idiosyncratic and requires close collaboration between Experia Health and the health system for proper identification of patient visits.