Clinical

The date on which a patient transfer record was initially created in the EHR, ADT, or claims system, distinct from the actual transfer event date. Data engineers use this field to track record latency, support audit logging, and identify data pipeline delays in inter-facility patient movement documentation workflows.

The exact timestamp when the patient transfer record was first entered into the clinical system. Used to establish the administrative timeline of a transfer event, supporting audit logs, workflow tracking, and distinguishing record creation from the actual clinical transfer occurrence.

The serum creatinine laboratory value recorded at the time of a patient transfer between units or facilities. Used as a key indicator of renal function to ensure continuity of care, inform receiving clinicians of kidney status, and support clinical decision-making during handoffs.

The calendar date on which a patient physically moved between healthcare facilities, recorded in ADT, inpatient EHR, and claims systems. Data engineers rely on this field for calculating inter-facility care timelines, aligning claims with clinical events, and validating continuity of care in population health and utilization reporting.

The combined date and time value recording the exact moment a patient transfer between facilities was initiated or completed, captured in ADT HL7 messages and EHR systems. Data engineers use this precise timestamp for sequencing care events, calculating transfer response times, and ensuring accurate temporal joins in clinical data pipelines.

The Drug Enforcement Administration registration number associated with a patient transfer, typically linked to the prescribing clinician authorizing controlled substance orders during or following the transfer. Required for regulatory compliance when controlled substances accompany a transferred patient.

The recorded date of patient death occurring in the context of an inter-facility transfer event, captured in ADT, inpatient EHR, and vital statistics systems. Data engineers use this field to close patient records accurately, support mortality analytics, and ensure claims and enrollment data reflect correct member status following transfer-related deaths.

The calendar date on which a patient transfer record was marked as deleted or voided within the clinical system. Used to maintain a soft-delete audit trail, allowing administrators to track when and why transfer records were removed without permanently destroying historical data.

A flag denoting that a patient transfer record has been voided or logically removed from active use in the clinical system. Records marked with this indicator are excluded from standard operational reporting while remaining accessible for audit, compliance, and historical review purposes.

A textual explanation providing context about the nature, reason, or outcome of a patient transfer between healthcare facilities, stored in EHR and ADT systems. Data engineers use this field during ETL to categorize transfer events, populate care coordination platforms, and support clinical narrative reporting when structured codes are insufficient.

Granular clinical and administrative data captured for inter-facility patient movements in EHR and ADT systems, including sending/receiving facility codes, transport mode, clinical handoff notes, and transfer reason codes used for continuity of care tracking.

The date a patient is formally discharged from a sending facility during an inter-facility transfer, recorded in ADT and claims systems. Critical for calculating inpatient LOS, coordinating benefit periods, and avoiding duplicate billing across facilities in UB-04 claims processing.

The target or scheduled date by which a patient transfer between units or facilities is expected to be completed. Used in care coordination workflows to track pending transfers, prioritize bed management activities, and ensure timely patient movement within or between healthcare facilities.

The total elapsed time from the initiation to the completion of a patient transfer between units or facilities. Used in operational reporting to assess transport efficiency, identify delays in patient movement, and benchmark performance against care coordination and throughput standards.

The electronic mail address associated with the receiving provider, care coordinator, or facility contact for an inter-facility patient transfer. Stored in EHR and care management platforms to facilitate secure clinical communication and transfer documentation routing between organizations.

A flag identifying whether a patient transfer between units or facilities was initiated on an emergency or unplanned basis. Used to distinguish urgent transfers requiring immediate coordination and resource mobilization from scheduled or elective transfers in clinical and operational workflows.

The date marking completion of an inter-facility patient transfer episode in EHR and ADT systems, signaling when transfer-related care coordination responsibilities conclude. Used by data engineers to calculate transfer duration, trigger downstream workflows, and close open transfer records in care management platforms.

The timestamp recording when a patient transfer between units or facilities was fully completed and the patient was accepted at the receiving location. Used to calculate transfer duration, measure handoff efficiency, and support bed management and throughput analytics.

The identifier of the staff member who manually entered the patient transfer record into the clinical or administrative system, which may differ from the clinician who ordered the transfer. Used for data quality auditing and accountability tracking in inpatient transfer workflows.

The self-reported or recorded ethnicity of the patient at the time of transfer between units or facilities. Captured to support health equity reporting, population health analytics, and compliance with federal requirements for demographic data collection during inpatient care transitions.