Domain
EHR, ICD-10, LOINC, SNOMED CT, patient care and clinical documentation
16,101 clinical terms
Sequential or externally assigned numeric identifier for a healthcare transaction used in claims, pharmacy, and clearinghouse systems. Data engineers rely on this field for deduplication, batch reconciliation, and tracing individual transactions through adjudication and remittance processing workflows.
Percentage value associated with a healthcare transaction, such as coinsurance rate or fee schedule percentage in claims and PBM systems. Data engineers use this field to calculate member cost-sharing, validate adjudication logic, and derive financial metrics in benefit design reporting pipelines.
Reference to the prior version or state of a healthcare transaction before an adjustment, reversal, or correction in claims or pharmacy systems. Data engineers use this field to trace claim lifecycle changes, build before-and-after audit comparisons, and support financial restatement processes.
Numeric value representing the count or volume of units associated with a healthcare transaction, such as days supply or units dispensed in NCPDP pharmacy claims. Data engineers validate this field against formulary rules, prior authorization limits, and utilization thresholds during adjudication pipeline processing.
Cross-system identifier or pointer linking a healthcare transaction to a related record such as a prior authorization, original claim, or remittance in EHR and payer platforms. Data engineers use this field to build relational joins, resolve adjustment chains, and maintain referential integrity across claim datasets.
Ordered numeric position of a transaction within a batch, claim set, or processing queue in EDI, claims, and pharmacy systems. Data engineers use this field to reconstruct processing order, detect missing records, and ensure correct application of adjustments and reversals in sequenced claim pipelines.
Current processing state of a healthcare transaction such as pending, adjudicated, denied, or reversed in claims, PBM, and eligibility systems. Data engineers use this field to filter active records, monitor pipeline completeness, and drive status-based logic in claims reporting and member-facing data products.
The precise date and time a transaction was initiated or recorded in healthcare claims, pharmacy, or EHR systems. Critical for data engineers performing audit trails, deduplication, and sequencing of eligibility transactions, claim submissions, and real-time adjudication events.
The aggregate monetary value of all line items within a single healthcare transaction, including claims, pharmacy dispensing, or remittance records. Used by data engineers to validate financial reconciliation across PBM, payer, and provider billing systems and detect payment discrepancies.
A categorical code distinguishing the nature of a healthcare data exchange, such as claim submission, reversal, adjustment, or eligibility inquiry. Present in EDI 837, 835, and 270/271 transactions; used by data engineers to segment, process, and route records through claims and enrollment pipelines.
A binary flag indicating whether a patient transfer event between care units, facilities, or levels of care is currently in progress or remains open in the clinical system. Used in inpatient workflow management to distinguish active transfers from completed, cancelled, or historical transfer records within the encounter.
A coded value representing the current workflow state of a patient transfer between units or facilities, such as pending, in transit, received, or closed. Provides more granular detail than a binary indicator, supporting real-time bed management, patient tracking, and handoff communication across care teams.
The hospital entry date recorded when a patient is admitted following transfer from another facility. Captured in ADT and inpatient EHR systems, this date is essential for data engineers calculating length of stay, continuity of care timelines, and inter-facility claims reconciliation in claims adjudication platforms.
The patient's age in years, months, or days at the time a transfer between units or facilities was initiated. Used in clinical decision support, acuity assessment, and transfer authorization workflows, particularly for distinguishing pediatric from adult transfer protocols and determining appropriate receiving unit criteria.
The maximum dollar amount a payer will reimburse for costs associated with a patient transfer between facilities or care levels, as determined by the applicable fee schedule or contract terms. Used in healthcare claims adjudication and financial reconciliation to calculate provider payment and member cost-sharing obligations.
The monetary value associated with a patient transfer event, such as financial liability moved between payers, facilities, or accounts during inter-facility patient movement. Used by data engineers in hospital billing and claims systems to reconcile cost-sharing obligations and validate payment accuracy across provider networks.
A coded value reflecting whether a patient transfer request has been authorized, denied, pended, or is awaiting clinical or administrative review. Tracks the authorization workflow state in utilization management systems, ensuring transfers comply with payer requirements and clinical criteria before patient movement occurs.
The identifier or name of the clinician, administrator, or payer representative who authorized a patient transfer between care settings. Captured for accountability, audit, and utilization management purposes, ensuring that transfers meet clinical necessity criteria and that an accountable decision-maker is documented in the patient record.
The recorded clock time at which a transferred patient physically arrived at the receiving unit, floor, or facility. Used to measure transfer duration, assess transport efficiency, support handoff documentation, and calculate time-sensitive quality metrics such as door-to-provider time in emergency or critical care settings.
The calendar date on which a transferred patient was received at the destination care unit or facility. Used alongside arrival time to establish the complete transfer timestamp, supporting length-of-stay calculations, transport documentation, continuity of care records, and regulatory reporting on inter-facility patient movement.