Member

Captures the assessed risk level associated with covering a specific health benefit, such as high-cost procedures or experimental treatments. Used in health plan underwriting and utilization management to flag benefits requiring prior authorization, clinical review, or additional cost controls before coverage approval.

Identifies the clinical administration pathway associated with a covered benefit, such as oral, intravenous, or subcutaneous delivery for pharmacy benefits. Used in pharmacy benefit management and medical policy systems to determine coverage eligibility based on how a drug or treatment is administered.

Calculated numeric rating (bnft_scr) derived from clinical, actuarial, or utilization metrics to assess the effectiveness, risk, or value of a covered benefit. Used in population health, care management, and analytics platforms to prioritize interventions and evaluate plan design performance.

Sequential ordering number (bnft_seq) assigned to a benefit record within a plan structure or adjudication workflow, ensuring benefits are processed in the correct order within EHR, claims, and PBM systems. Critical for COB logic, benefit stacking rules, and structured data extraction in downstream pipelines.

Classification value (bnft_sev) indicating the clinical seriousness or acuity level associated with a benefit or covered condition, used to trigger tiered coverage rules, prior authorization requirements, or case management escalation. Applied in utilization management and EHR systems to align resources with clinical need.

Specifies the biological sex eligibility restriction applied to a health plan benefit, such as mammography benefits limited to female members or prostate screenings limited to male members. Used in benefits configuration and claims adjudication to enforce gender-specific coverage rules defined in the plan contract.

Origin identifier (bnft_src) indicating the system, contract, regulatory mandate, or data feed from which a benefit configuration was derived. Used in EHR, enrollment, and claims platforms to support data lineage, audit compliance, and integration mapping across source systems in healthcare data pipelines.

Effective start date (bnft_start_dt) marking the beginning of a benefit's coverage period within member enrollment, claims, and EHR systems. Used to validate service eligibility, apply accumulator resets, and define plan-year boundaries for downstream adjudication and reporting workflows.

Records the precise time of day a health plan benefit becomes effective or was activated within a given coverage period. Used in benefits administration and real-time eligibility systems where time-stamped activation is required, such as same-day enrollment scenarios or intraday benefit changes.

Identifies the U.S. state or territory under whose regulatory jurisdiction a health plan benefit is offered or governed. Used in benefits configuration systems to enforce state-mandated coverage requirements, since benefit structures often vary by state due to differing insurance regulations and mandated benefit laws.

Lifecycle state indicator (bnft_sts) reflecting the current operational status of a benefit—such as active, suspended, terminated, or pending—within clinical, enrollment, and claims systems. Drives eligibility validation, adjudication routing, and reporting workflows across healthcare data integration pipelines.

Specifies the drug concentration or dosage strength associated with a pharmacy benefit, such as 10mg or 500mg formulations. Used in pharmacy benefit management systems to differentiate coverage tiers, apply formulary rules, and determine copay levels based on the specific strength of a covered medication.

Represents a partial financial sum for a subset of covered services within a health plan benefit category before final aggregation. Used in benefits cost calculation workflows and member Explanation of Benefits (EOB) reporting to display intermediate cost breakdowns across benefit groupings such as medical, pharmacy, or dental.

A unique system-generated key assigned to a specific benefit record within a health plan's benefits administration platform. Used to reference, link, and track individual benefit configurations across enrollment, claims adjudication, and reporting systems, ensuring consistent identification across integrated healthcare data environments.

Destination reference (bnft_tgt) identifying the intended recipient system, population segment, or coverage objective for a specific benefit configuration. Used in member enrollment, care management, and analytics platforms to route benefit data to downstream systems and align plan design with targeted member groups.

Stores the NUCC Health Care Provider Taxonomy Code associated with a benefit, identifying the specialty type eligible to render or prescribe covered services. Used in claims adjudication and benefits configuration to restrict certain benefits to specific clinical specialties such as behavioral health or physical therapy.

Records storage or transport temperature requirements associated with a covered benefit item, particularly for biologics, vaccines, or specialty drugs requiring cold chain management. Used in pharmacy benefit and specialty drug programs to ensure covered medications meet handling conditions required for clinical efficacy and coverage validity.

The calendar date on which a member's specific benefit coverage ends within EHR, claims, or enrollment systems. Used in eligibility verification, claims adjudication, and PBM processing to reject or deny services rendered after this date. Critical for downstream analytics and compliance reporting.

The specific time-of-day value associated with a covered healthcare service or item, captured in EHR, claims, and PBM systems. Used to sequence events, resolve duplicate claims, and support audit trails in real-time eligibility and prior authorization workflows.

The system-generated date and time value recorded when a benefit event is processed within compliance workflows in healthcare implementations. Captured in EHR, claims, and enrollment systems to support audit logging, regulatory reporting, integration sequencing, and downstream analytics pipelines.