Clinical

A coded or descriptive value indicating the time sensitivity of a therapist's intervention or referral for a patient. Used in care coordination workflows to prioritize therapy scheduling, ensuring patients with acute or deteriorating conditions receive timely physical, occupational, or behavioral health therapy services.

A discrete measured data point associated with a licensed therapy professional's assessment, outcome, or performance metric within EHR or quality reporting systems. Data engineers use this field to populate clinical scorecards, outcome registries, and value-based care performance dashboards across therapy program datasets.

A sequential number identifying the specific iteration of a therapist's record within the clinical data system. Supports record versioning and change history tracking, enabling downstream systems to identify whether they hold the most current therapist profile data, including licensure status and specialty credentials.

The five or nine digit postal code associated with a licensed therapist's primary practice or mailing address. Used in provider directory management, geographic access analysis, network adequacy reporting, and claims processing to validate service location and support member-to-therapist proximity matching.

The monetary value associated with a single financial transaction in healthcare claims, pharmacy PBM, or member billing systems. Data engineers use this field for claims payment reconciliation, adjudication auditing, and financial reporting pipelines, where accurate capture of gross charges or net paid amounts is critical.

A calculated metric representing the mean monetary or unit value across a set of healthcare financial transactions within claims, PBM, or billing systems. Used by data engineers to build cost benchmarking models, detect anomalous billing patterns, and produce utilization trend reports across payer and provider datasets.

The remaining financial amount owed or credited after payments, adjustments, and reversals are applied to a healthcare transaction in claims or member billing systems. Data engineers use this field to reconcile accounts receivable, track member cost-sharing liabilities, and validate payment posting accuracy in revenue cycle pipelines.

A classification code grouping healthcare financial transactions by type, such as medical claim, pharmacy claim, capitation payment, or member premium in payer and PBM systems. Data engineers use this field to partition financial datasets, apply business rules by transaction type, and support cross-domain cost attribution reporting.

A standardized identifier classifying the type of financial or clinical transaction in EHR, claims, and PBM systems. Used by data engineers to route, filter, and reconcile pharmacy claims, eligibility updates, and remittance records across payer and provider platforms.

Total number of discrete transactions processed within a defined period in claims, pharmacy, or enrollment systems. Used by data engineers for volume reconciliation, audit reporting, and batch validation to ensure completeness of EDI file loads and adjudication cycles.

Flag or record indicator identifying the most recent active version of a transaction in claims or PBM systems. Data engineers use this field to filter out superseded or reversed records when building current-state views of adjudicated claims or member eligibility data.

The calendar date on which a healthcare transaction was initiated, submitted, or processed in EHR, claims, or pharmacy systems. Data engineers rely on this field for temporal partitioning, run-out analysis, and reconciling service dates against adjudication timelines in EDI workflows.

Free-text or coded narrative explaining the nature of a healthcare transaction in claims, EHR, or PBM platforms. Used by data engineers to enrich transaction records, support audit trails, and populate human-readable fields in reporting layers for claim adjustments or pharmacy events.

Date or condition at which a healthcare transaction becomes invalid or inactive in eligibility, authorization, or PBM systems. Data engineers use this field to purge stale records, enforce referential integrity, and identify expired prior authorizations or benefit transactions during ETL processing.

Boolean or coded indicator marking a transaction with a specific attribute such as reversal, duplicate, or void in claims and pharmacy systems. Essential for data engineers filtering adjudicated claims pipelines, identifying NCPDP reversals, and excluding flagged records from financial aggregations.

Unique system-generated or EDI-assigned key that distinctly identifies a single healthcare transaction across claims, PBM, or enrollment platforms. Data engineers use this field as the primary join key for linking claim headers to detail lines, remittances, and audit logs.

Coded field denoting the nature or processing state of a healthcare transaction such as original, adjustment, or void in X12 and NCPDP systems. Data engineers reference this field to apply correct business logic when aggregating paid amounts and reconciling claim lifecycle states.

Upper threshold value associated with a healthcare transaction, such as maximum allowed reimbursement or benefit limit in claims or PBM adjudication systems. Data engineers use this field to enforce benefit cap rules, trigger alerts, and validate that adjudicated amounts do not exceed contractual ceilings.

Lower threshold value for a healthcare transaction, representing the minimum payable amount or quantity in claims or pharmacy adjudication. Data engineers apply this field in validation rules to flag zero-pay transactions, detect data quality issues, and enforce adjudication floor constraints.

Human-readable label assigned to a transaction type in EHR, claims, or PBM data systems, such as Claim Submission or Eligibility Inquiry. Data engineers use this field to populate reference tables, build reporting dimensions, and document ETL pipeline logic for transaction classification.