Clinical

Captures the total dollar amount paid toward a visit's balance, including insurance reimbursements and patient payments. Used in revenue cycle management to reconcile claims, track outstanding balances, and report on payment performance across payers and service lines.

Records the date on which payment was received or posted for a clinical visit, whether from an insurance payer or the patient. Used in revenue cycle management to calculate reimbursement timelines, measure days in accounts receivable, and reconcile claim adjudication records.

Reference identifier linking a child encounter record to its parent encounter in hierarchical EHR and care management data models, such as associating a lab visit to a primary office visit. Data engineers use this field to build encounter relationship hierarchies and support episode-of-care grouping logic in analytic datasets.

Calculated ratio value in healthcare analytics and claims systems expressing a visit-related metric as a proportion of a total, such as percentage of visits resulting in admission or telehealth visit share. Data engineers use this field in performance dashboards, utilization reporting, and population health measurement pipelines.

Defined time span in EHR, claims, and utilization management systems representing the duration or reporting window associated with a patient encounter, such as an inpatient stay or a measurement period for chronic care visits. Data engineers use this field for episode grouping, length-of-stay calculations, and time-bounded cohort analysis.

Telephone contact number associated with a patient encounter in EHR and scheduling systems, representing the location phone, provider direct line, or patient callback number for the visit. Data engineers use this field for care coordination integrations, contact verification workflows, and provider directory data quality checks.

Stores the patient's preferred name or chosen display name as provided during visit registration. Supports person-centered care by ensuring clinical and administrative staff address patients by their preferred identifier, aligned with gender-affirming care and patient experience standards.

Represents the billed or estimated charge for services rendered during a clinical visit before insurance adjustments or patient discounts are applied. Used in revenue cycle and price transparency workflows to calculate patient liability, negotiate payer contracts, and report gross charges.

A flag designating whether a visit record represents the primary encounter within a group of related visits, such as the principal inpatient admission versus associated outpatient contacts. Used in episode-of-care grouping, claims adjudication, and clinical reporting to distinguish primary from ancillary encounters.

Ranked importance classification assigned to a patient encounter in EHR scheduling and triage systems, indicating urgency levels such as emergent, urgent, or routine. Data engineers use this field to support capacity planning analytics, triage workflow reporting, and visit prioritization logic in care management data pipelines.

Records the date on which a clinical procedure or treatment was performed during or associated with a patient encounter. Used in claims processing, surgical scheduling, and outcomes reporting to align procedure codes with service dates for accurate billing and longitudinal care tracking.

Captures the patient's heart rate in beats per minute as recorded during the clinical encounter. This vital sign is used to assess cardiovascular status, monitor treatment response, and support clinical decision support alerts for conditions such as tachycardia, bradycardia, or hemodynamic instability.

Numeric count representing the volume of visits, units of service, or encounter occurrences in EHR, claims, and utilization reporting systems within a defined population or time period. Data engineers aggregate this field for utilization metrics, provider productivity reporting, and member-level visit frequency analysis in healthcare data warehouses.

Records the patient's self-reported racial identity as collected during visit registration or intake. Used in population health analytics, health equity reporting, and disparity monitoring to identify gaps in care access and outcomes across racial groups in compliance with federal reporting requirements.

Defined minimum and maximum boundaries for visit-related values in EHR analytics and claims systems, such as acceptable visit count ranges for quality measures or reimbursement thresholds. Data engineers use this field to implement data validation rules, flag outliers, and enforce business logic in healthcare data quality frameworks.

Monetary or utilization rate value associated with a patient encounter in claims, PBM, and fee schedule systems, representing the reimbursement amount or service unit cost per visit. Data engineers use this field for cost analysis, contract rate validation, provider fee schedule comparisons, and claims adjudication reconciliation workflows.

Captures a scored assessment of the visit, which may reflect patient satisfaction survey results, clinician quality scores, or acuity ratings assigned during triage. Used in quality improvement programs, value-based care reporting, and patient experience benchmarking across clinical settings.

Represents a calculated proportional value derived from visit-level data, such as the ratio of completed to scheduled visits, follow-up rate, or resource utilization per encounter. Used in operational analytics and population health dashboards to measure care delivery efficiency and access patterns.

Free-text or coded explanation documenting why a patient sought care during an encounter. Captured in EHR scheduling and encounter modules, maps to chief complaint fields, and supports clinical documentation, utilization review, and population health analytics in claims and EHR systems.

Records the date on which a visit-related document, referral, or claim was received by the processing entity, such as a health plan or clinical facility. Used in claims adjudication, referral management, and prior authorization workflows to calculate turnaround times and compliance with regulatory timelines.