Clinical

The identifier of the clinician, administrator, or system user who authorized or approved the patient visit record within the clinical or administrative workflow. Used for audit trail purposes in care management, utilization review, and scheduling systems to establish accountability for visit authorization decisions.

The recorded timestamp indicating when the patient physically arrived at the clinical facility for a scheduled or unscheduled visit. Used in operational reporting to measure wait times, patient throughput, and scheduling efficiency, and to support regulatory compliance reporting for emergency and ambulatory settings.

The calendar date on which the patient arrived at the clinical facility for a scheduled or unscheduled encounter. Used in conjunction with arrival time to establish the encounter timeline, support operational analytics, and reconcile scheduled versus actual visit dates in scheduling and billing systems.

The clinician's documented evaluation of the patient's condition recorded during the encounter, typically capturing diagnoses, clinical impressions, and interpretation of findings. Forms a core component of the SOAP note structure and supports medical decision-making documentation required for accurate coding and claims submission.

Remaining unpaid amount on a patient encounter after insurance payments, adjustments, and prior patient payments have been applied, stored in practice management and revenue cycle systems. Used in accounts receivable aging analysis, patient financial services workflows, and bad debt reporting within healthcare financial data warehouses and billing platforms.

The total gross charges submitted by the provider to the payer for services rendered during a patient visit, prior to any contractual adjustments, denials, or payment reductions. Used in claims processing, revenue cycle management, and financial reporting to track billed versus allowed versus paid amounts.

Patient date of birth captured at the visit level in EHR and claims systems. Used by data engineers to validate patient identity across encounters, support age-based eligibility logic, and reconcile demographic discrepancies between ADT feeds and enrollment records.

The systolic and diastolic arterial blood pressure measurement recorded as a vital sign during the patient encounter, typically expressed in millimeters of mercury. Used in clinical documentation, chronic disease management workflows, and quality measure reporting for conditions such as hypertension and cardiovascular risk assessment.

The calendar date on which a scheduled patient visit was formally cancelled by the patient, provider, or administrative staff. Used in scheduling analytics to track cancellation rates, measure no-show patterns, support appointment utilization reporting, and trigger follow-up workflows for rescheduling or care gap outreach.

Classification grouping assigned to a patient encounter in EHR and claims systems, such as inpatient, outpatient, or emergency. Data engineers use this field to segment encounter datasets, apply category-specific business rules, and drive downstream utilization reporting pipelines.

The primary symptom or reason for care documented by clinical staff at the start of a patient encounter. Captured in EHR visit records to guide triage, clinical decision-making, and coding. Used in population health analytics to identify patterns in patient-reported presenting conditions.

Subordinate encounter record linked to a parent visit in hierarchical EHR data models, representing associated services or sub-encounters. Data engineers use this relationship to build encounter hierarchies, resolve billing dependencies, and accurately aggregate claim line-level data.

The city where the clinical service location is situated for a specific patient encounter. Used in EHR and claims data to identify geographic service areas, support regional utilization reporting, and verify facility addresses for billing and credentialing purposes.

Classification tier assigned to a patient encounter in EHR and hospital systems, such as inpatient, observation, or ambulatory. Critical for data engineers applying reimbursement logic, filtering encounter cohorts, and aligning visit data with payer-specific claims adjudication rules.

Standardized alphanumeric code representing the type or nature of a patient encounter in EHR, claims, and revenue cycle systems. Data engineers use this field for encounter classification, mapping to code sets like UBREV or CPT, and driving procedure-level analytics pipelines.

Free-text notation field attached to a patient encounter record in EHR and scheduling systems, capturing clinical or administrative notes. Data engineers must handle this unstructured field carefully during ETL, applying NLP parsing or exclusion logic to avoid downstream processing errors.

The calendar date on which all clinical services and documentation associated with a patient encounter were finalized. Used in EHR workflows to trigger downstream billing processes, measure visit closure timelines, and support audit and compliance reporting.

A binary flag indicating that a patient encounter contains sensitive clinical information subject to heightened privacy protections, such as behavioral health, substance use, or reproductive care. Controls access restrictions in EHR systems to comply with 42 CFR Part 2 and HIPAA requirements.

Communication reference associated with a patient encounter in EHR and scheduling systems, including phone, address, or responsible party details. Data engineers use this field for patient outreach analytics, care gap identification, and linking encounter data to member contact records.

Numeric tally of patient encounters within a defined period in EHR, claims, and utilization management systems. Data engineers use this metric to measure care utilization, flag high-frequency users, build risk stratification models, and support population health reporting dashboards.