Clinical

The country where the clinical service location is situated for a specific patient encounter. Used in EHR and claims systems to support international patient billing, cross-border care coordination, and geographic reporting for facilities operating across national boundaries.

The unique identifier of the system user who initially generated the encounter record in the EHR or scheduling system. Used in audit trails to track data provenance, support compliance reviews, and identify workflows associated with appointment creation and registration activities.

Timestamp indicating when a patient encounter record was first written to the EHR or claims system database. Data engineers rely on this field for incremental data loads, audit trail reconstruction, identifying late-arriving records, and monitoring data pipeline latency across source systems.

The exact timestamp recording when an encounter record was first generated in the EHR or scheduling system. Used for audit logging, workflow performance measurement, and identifying the sequence of administrative events leading up to patient registration and clinical documentation.

The serum or urine creatinine laboratory value recorded during a specific patient encounter, used as a key indicator of kidney function. Captured in EHR clinical data to support chronic kidney disease monitoring, medication dosing decisions, and longitudinal renal health trending.

Calendar date on which a patient encounter occurred, present across EHR, claims, and scheduling systems. A foundational field for data engineers performing date-range filtering, encounter deduplication, care timeline construction, and aligning clinical events with eligibility periods.

Combined timestamp capturing both date and time of a patient encounter in EHR and ADT systems. Data engineers use this field for precise event sequencing, calculating encounter durations, resolving same-day visit conflicts, and supporting time-sensitive clinical quality measure calculations.

The Drug Enforcement Administration registration number associated with a prescribing clinician at the time of a patient encounter. Recorded in EHR and pharmacy systems to validate controlled substance prescribing authority, support DEA compliance audits, and maintain regulatory documentation.

Date of patient death recorded at the encounter level in EHR and mortality-linked claims datasets. Data engineers use this field to flag terminal encounters, suppress deceased members from outreach pipelines, and align clinical data with Social Security Death Index or payer mortality feeds.

The calendar date on which an encounter record was marked as deleted or voided within the EHR or clinical data system. Used in audit trails to track record lifecycle events, support data integrity reviews, and identify encounters removed due to administrative error or duplicate entry.

A binary flag designating that an encounter record has been voided or logically removed from active clinical and billing workflows. Used in EHR and data warehouse systems to exclude cancelled or erroneous visits from reporting while preserving the original record for audit and compliance purposes.

Textual explanation of the nature or purpose of a patient encounter in EHR and scheduling systems. Data engineers use this field during data profiling, encounter type classification, and as a fallback for mapping visits lacking structured codes to appropriate categories in analytics pipelines.

Granular encounter-level information stored in EHR and claims systems, capturing service specifics beyond the primary visit record. Data engineers join visit detail records to header-level encounter data to support line-item billing analysis, quality measurement, and clinical data completeness validation.

Date a patient was formally released from a facility following an inpatient or observation encounter in EHR, ADT, and UB-04 claims systems. Data engineers use this field to calculate length of stay, determine claim finalization timelines, and trigger post-discharge care management workflows.

The target date by which a scheduled or follow-up patient encounter is expected to occur, often set during care planning or at the close of a prior visit. Used in EHR and care management systems to drive outreach workflows, monitor care gaps, and support chronic disease management programs.

The total elapsed time between the start and end of a patient encounter, typically measured in minutes. Used in EHR systems and operational analytics to assess clinical productivity, support provider scheduling optimization, and benchmark encounter length by visit type and specialty.

Electronic mail address associated with a patient or contact at the encounter level in EHR and patient engagement systems. Data engineers use this field for patient communication analytics, deduplicating contact records across encounters, and supporting digital outreach integration with CRM platforms.

A binary flag designating that a patient encounter was classified as an emergency at the time of service. Used in EHR and claims systems to apply appropriate billing modifiers, trigger urgent care protocols, support case mix reporting, and distinguish emergency visits from scheduled encounters.

Date marking the conclusion of a patient encounter or service period in EHR, claims, and utilization management systems. Data engineers use this field alongside visit start dates to compute service durations, validate claim spans, and enforce date-range logic in encounter deduplication processes.

The exact timestamp marking the conclusion of direct clinical services for a patient encounter. Used in EHR operational data to calculate visit duration, measure provider throughput, support scheduling efficiency analysis, and generate accurate timekeeping records for billing and staffing purposes.