Clinical

A human-readable display name or title assigned to a clinical record for identification and navigation purposes within health information systems. Used to distinguish record types, episodes of care, or document categories in patient charts and clinical data repositories.

The calendar date on which a clinical procedure documented within a healthcare record was performed. Used for chronological sequencing of care events, claims adjudication alignment, and retrospective auditing of procedural timelines within patient medical records.

Defines the allowable or observed span of values within a healthcare document or result record, such as reference ranges for lab results or valid date windows. Stored as rec_rng in EHR and LIS systems, this field supports data validation rules, anomaly detection, and range-based filtering in clinical data engineering pipelines.

The clinical outcome or measured value captured within a healthcare information document, such as a diagnostic finding, test result, or assessment score. Stored as rec_rslt in EHR and LIS systems, this field is central to clinical analytics, quality measure calculation, and result normalization across heterogeneous source data pipelines.

The calendar date on which a surgical procedure referenced in a clinical record was performed. Critical for operative documentation integrity, surgical outcomes tracking, post-operative care scheduling, and aligning medical record content with corresponding inpatient or outpatient claims data.

A binary flag indicating whether a patient referral from one provider to another is currently active and valid for use. Determines whether the referral can be applied to authorize specialist visits, drives worklist visibility in care coordination systems, and supports managed care authorization workflows.

A categorical status value describing the current activity state of a provider-initiated patient referral, such as open, pending, completed, or expired. Used in care coordination and utilization management systems to track referral lifecycle and ensure timely specialist follow-through.

The date a patient was admitted to a facility in connection with a specialist referral, stored as ref_admn_dt in EHR and care coordination systems. Data engineers use this field to link referral authorizations to inpatient encounters, validate payer authorization timelines, and support referral-to-admission latency analysis in population health pipelines.

Stores the communication details of the referring provider, specialist, or care coordinator associated with a specialist referral request in EHR and care management systems. Used to support provider directory integration, referral notification workflows, and contact validation processes within healthcare data engineering pipelines.

The date a patient was discharged from a facility associated with a specialist referral encounter, stored as ref_dsch_dt in EHR and care management systems. Used by data engineers to calculate referral episode length, close open referral records, and reconcile specialist encounter dates against authorization windows in claims data pipelines.

A flag designating that a provider-to-provider patient referral was initiated under emergency circumstances, bypassing standard prior authorization requirements. Triggers expedited processing workflows, affects payer authorization rules, and is used in utilization management reporting for emergency referral volumes.

A narrative field containing the referring provider's description of the patient's current condition and symptom history at the time a referral is generated. Communicates clinical context to the receiving specialist, supporting informed evaluation and continuity of care across provider transitions.

Free-text or coded guidance provided by the referring provider as part of a specialist referral request, stored as ref_instr in EHR and care coordination systems. Data engineers must handle this field as unstructured or semi-structured text, often requiring NLP processing to extract actionable clinical directives for downstream care management workflows.

A descriptive display name assigned to a patient referral record for identification within care coordination and referral management systems. Typically reflects the referral type, specialty destination, or clinical purpose, enabling staff to quickly locate and distinguish referrals within patient workflows.

Clinical annotation or commentary attached to a specialist referral request, stored as ref_nt in EHR and care coordination platforms. This field contains provider-authored narrative context such as clinical history or urgency rationale. Data engineers process referral notes as unstructured text requiring NLP parsing for analytics and care gap identification workflows.

The anticipated or actual date on which a procedure associated with a patient referral is scheduled or performed. Used in referral tracking systems to monitor care delivery timelines, measure referral-to-procedure lag times, and ensure specialist appointments are completed within authorization windows.

Defines the allowable value span or date window associated with a specialist referral, such as authorized visit counts or valid service date ranges. Stored as ref_rng in EHR and utilization management systems, this field is used by data engineers to enforce authorization boundary logic and detect out-of-range referral utilization in claims pipelines.

The clinical outcome or specialist finding returned following a referral service request, stored as ref_rslt in EHR and care coordination systems. Data engineers use this field to close referral loops, measure specialist response rates, support quality reporting on referral completion, and link outcomes back to originating primary care encounters in analytics pipelines.

The scheduled or actual date of a surgical procedure tied to a patient referral. Used in surgical referral management to coordinate pre-operative clearance, track authorization validity periods, and measure time elapsed between referral initiation and operative care delivery.

The date a patient was admitted to a facility in the context of a prescription refill event, stored as rfll_admn_dt in pharmacy and EHR systems. Data engineers use this field to correlate inpatient admissions with medication refill activity, supporting medication adherence analysis, polypharmacy reviews, and drug utilization reporting across PBM and EHR data pipelines.