Clinical

The unique identifier of the staff member who manually keyed encounter data into the EHR or clinical information system. Used in audit logs to establish data entry accountability, support error correction workflows, and distinguish system-generated records from those created through manual registration processes.

The patient-reported ethnic identity documented at the time of a clinical encounter, following OMB classification standards. Captured in EHR systems to support health equity reporting, identify disparities in care access and outcomes, and meet federal and state demographic data collection requirements.

Date after which a patient encounter authorization or record validity lapses in EHR and utilization management systems. Data engineers use this field to enforce referral and prior authorization expiration logic, filter stale encounter records, and align visit data with payer contract effective periods.

A reference identifier assigned by an external system, such as a health information exchange, payer, or referring organization, that maps to an encounter record within the internal EHR. Used to support cross-system data reconciliation, care coordination, and interoperability between disparate clinical platforms.

The facsimile telephone number associated with the clinical service location or ordering provider for a specific patient encounter. Used in EHR and referral management systems to route clinical documents, lab results, and prior authorization communications to the appropriate receiving facility or clinician.

The gross charge amount assigned to a patient encounter based on services rendered and applicable fee schedule rates. Captured in EHR and practice management systems as the starting point for claims adjudication, contractual adjustment calculations, patient balance determination, and revenue cycle reporting.

The patient's given name as recorded at the time of the clinical visit. Used in EHR and scheduling systems to personalize encounter documentation, verify patient identity, and ensure accurate matching of visit records to the correct individual's medical history.

Binary or categorical indicator applied to a patient encounter record in EHR and claims systems to denote special processing conditions, such as fraud risk, quality events, or data exceptions. Data engineers use these flags to route records through conditional ETL logic and exclusion workflows.

The scheduled recurrence interval for a patient's care visits, such as weekly therapy sessions or monthly chronic disease check-ins. Used in care management systems to coordinate treatment plans, authorize recurring services, and track adherence to prescribed visit schedules.

The patient's complete name, combining given, middle, and family name components, as documented at the time of the clinical encounter. Used in EHR systems for patient identity verification, legal documentation, and reconciliation of visit records across care settings.

The patient's gender identity or biological sex as recorded during the clinical visit. Used in EHR systems to inform clinically appropriate care decisions, ensure accurate demographic reporting, and support population health analytics segmented by gender across encounter data.

The blood glucose measurement recorded during a clinical encounter, typically captured as part of vitals or lab results. Used in chronic disease management for diabetes monitoring, inpatient care tracking, and identifying patients requiring immediate clinical intervention based on abnormal levels.

The health insurance group plan number associated with the patient's coverage at the time of the clinical visit. Used in billing and claims processing systems to link the encounter to the correct payer contract, verify eligibility, and ensure accurate adjudication of services rendered.

The hemoglobin concentration level measured during a clinical encounter, typically from a complete blood count or point-of-care test. Used in clinical documentation to assess anemia, monitor chronic conditions such as sickle cell disease, and guide transfusion or treatment decisions at the visit level.

The structured narrative describing the patient's chief complaint and current condition as documented by the clinician during the encounter. This HPI section is a core component of clinical notes used to capture symptom onset, duration, severity, and context for diagnosis and treatment planning.

Unique key assigned to a patient encounter record in EHR, claims, and ADT systems, serving as the primary join key across clinical and administrative datasets. Data engineers rely on this field for encounter deduplication, cross-system record linkage, and maintaining referential integrity in data warehouses.

Sequential numeric position assigned to a patient encounter within a series of related visits in EHR and care management systems. Used by data engineers to order longitudinal visit records, support time-series analysis, and maintain encounter sequencing in clinical data warehouses.

Boolean flag in EHR, claims, and scheduling systems that signals whether a specific encounter condition is true or false, such as flagging telehealth visits, preventive care, or billable encounters. Critical for data engineers filtering and segmenting visit populations in analytics pipelines.

Structured or free-text guidance documented in EHR and patient portal systems containing pre-visit preparation, post-visit care directives, or procedural requirements for a scheduled encounter. Data engineers use this field to support care coordination workflows and patient communication integrations.

The unique surrogate key assigned to a clinical visit record within the data warehouse or EHR system. Used as the primary join attribute for linking encounter-level data across clinical, billing, and operational tables to enable longitudinal patient care analysis and reporting.