Pharmacy

Stores a standardized code value identifying the type or status of a prescription refill transaction in PBM, pharmacy, and claims systems. Data engineers use this field for adjudication logic, refill categorization, NCPDP transaction mapping, and identifying authorized versus unauthorized refill attempts.

The portion of a prescription refill cost shared by the patient after the deductible is met, calculated as a percentage of the allowed amount under their pharmacy benefit plan. Used in member cost-sharing analysis and pharmacy claims adjudication reconciliation.

Contains free-text notations entered by pharmacists, prescribers, or PBM staff regarding a prescription refill event in pharmacy and EHR systems. Data engineers must handle this unstructured field carefully during ETL, applying text parsing or NLP techniques to extract actionable insights for clinical or operational reporting.

The date a prescription refill was fully dispensed and made available to the patient, marking the end of the pharmacy fulfillment workflow. Used to calculate fill cycle time, measure pharmacy operational efficiency, and support medication adherence monitoring.

A flag identifying whether a prescription refill record contains sensitive information requiring restricted access, such as medications for mental health, substance use disorder, HIV, or reproductive health. Governs data visibility controls in pharmacy and clinical systems under applicable privacy regulations.

Stores the communication point, such as phone number or contact name, associated with a prescription refill request in pharmacy and PBM systems. Data engineers use this field to support outreach workflows, link member contact records, and validate refill authorization communications in dispensing pipelines.

The fixed out-of-pocket dollar amount the patient is required to pay at the point of dispensing for a prescription refill, as defined by their pharmacy benefit plan tier. Used in pharmacy claims adjudication, member cost-sharing reporting, and adherence barrier analysis.

Records the total number of times a prescription has been refilled in PBM, pharmacy, and claims systems. Data engineers rely on this field to track medication adherence, validate fill limits against prescription authorizations, detect duplicate dispensing, and support medication possession ratio calculations in analytics pipelines.

The country associated with the dispensing pharmacy or patient address on a prescription refill record. Used to support international pharmacy fulfillment tracking, cross-border prescription data management, and regulatory compliance reporting for multinational health plan operations.

The unique identifier of the user, system, or role that initiated the prescription refill record in the pharmacy or clinical system, such as a pharmacist, prescriber, automated refill system, or patient portal. Used in audit trails and workflow accountability tracking.

Captures the timestamp when a prescription refill record was first generated in a PBM, pharmacy, or EHR system. Data engineers use this field to establish record lineage, support audit trails, calculate processing lag times, and sequence refill events accurately in longitudinal pharmacy claims data pipelines.

The timestamp recording when a prescription refill record was first entered into the pharmacy or clinical system. Used to establish the start of the refill fulfillment workflow, support audit logging, and calculate processing time from request initiation to dispensing completion.

The kidney function marker for a prescription renewal. Used in healthcare data management and clinical workflows. This field is commonly used in electronic health records (EHR), healthcare information systems (HIS), and clinical data warehouses for refill management and reporting.

Records the specific calendar date on which a prescription refill was dispensed or requested in pharmacy, PBM, and claims systems. Data engineers use this field to calculate days supply gaps, measure medication adherence intervals, sequence dispensing events, and reconcile refill dates against adjudication records.

Stores the combined date and time of a prescription refill event in pharmacy, PBM, and claims systems, providing precise temporal resolution for transaction tracking. Data engineers use this field to sequence same-day refill events, detect duplicate transactions, and support real-time dispensing audit pipelines.

The Drug Enforcement Administration registration number of the prescribing clinician authorized to prescribe controlled substances on a refill request. Required for Schedule II-V medication dispensing validation, regulatory compliance auditing, and controlled substance monitoring program reporting.

Records the date of death associated with a patient in the context of a prescription refill transaction in pharmacy and PBM systems. Data engineers use this field to suppress post-mortem refill activity, flag fraudulent dispensing events, and reconcile member enrollment termination dates against pharmacy claims records.

The dollar amount of a prescription refill cost applied toward the patient's annual pharmacy or medical deductible before insurance benefits begin paying. Used in pharmacy claims adjudication, member accumulator tracking, and benefit year cost-sharing analysis.

The date a prescription refill record was marked as deleted or voided in the pharmacy or clinical system, indicating the record was removed from active processing. Used in data governance audits, record lifecycle management, and identifying erroneously created refill transactions.

A flag denoting whether a prescription refill record has been logically deleted or voided from active pharmacy or clinical system workflows. Allows soft-deletion of erroneous refill records while preserving the data for audit trail purposes and historical reporting integrity.