member identifier
mbr_idDefinition
ISO-11179 Definition
The member identifier (mbr_id) is the unique identifier assigned to an individual enrolled in a health plan, used to link that member's eligibility, enrollment, claims, pharmacy, laboratory, and care management records across all data systems. The member ID is assigned by the health plan and may differ from the subscriber ID when the covered person is a dependent rather than the primary policyholder. In HIPAA 837 transactions, the member ID appears in the NM109 element of the subscriber and patient NM1 segments.
Medicare beneficiaries have a Medicare Beneficiary Identifier (MBI) — an alphanumeric code that replaced the Social Security Number-based Health Insurance Claim Number (HICN) in 2019 as the primary Medicare member identifier. The member identifier is the primary key of the member dimension table and the most critical linkage key in a healthcare data warehouse. Every claim, pharmacy fill, lab result, care gap record, and care management touchpoint must link to a single member record to enable longitudinal member analytics — without reliable member ID linkage, population health management, care gap identification, and risk stratification are impossible.
Member ID management is complicated by the fact that members re-enroll after coverage gaps, switch between plans within the same organization, and may receive different IDs from different source systems (payer claims system, care management platform, pharmacy benefit manager). Healthcare data engineers store mbr_id as VARCHAR(50) to handle the full range of member identifier formats, which vary significantly across payers and government programs. When a member appears in multiple source systems with different identifiers, probabilistic matching on demographic attributes (last name, date of birth, sex, zip code) is used to link records to a single master member ID in the member master data management (MDM) layer.
Key data quality rules include: mbr_id must be non-null on all claim records, the member must have an active eligibility record on the date of service, and demographic data on the claim must match the eligibility record within defined tolerance thresholds. Enrollment gaps — periods where a member has no active coverage — must be explicitly modeled using effective and termination dates rather than a single status flag, enabling accurate member-months denominators for utilization and cost analytics.
Standard Abbreviation
mbr_id
Category
Production DDL — DIM_MEMBER
CREATE OR REPLACE TABLE DIM_MEMBER (
mbr_key INTEGER NOT NULL -- surrogate key,
mbr_id VARCHAR(50) NOT NULL -- member identifier,
mbr_first_nm VARCHAR(100) -- first name,
mbr_last_nm VARCHAR(100) -- last name,
mbr_birth_dt DATE -- date of birth,
mbr_gndr_cd CHAR(1) -- gender code M/F/U,
mbr_age SMALLINT -- age in years,
mbr_state_cd CHAR(2) -- state code,
mbr_zip_cd VARCHAR(10) -- zip code,
mbr_elig_ind BOOLEAN -- eligibility indicator,
mbr_enrl_dt DATE -- enrollment date,
mbr_term_dt DATE -- termination date,
mbr_plan_cd VARCHAR(20) -- plan code,
mbr_dual_elig_cd VARCHAR(10) -- dual eligibility code,
load_dt TIMESTAMP_NTZ NOT NULL -- load timestamp
);
Standard Snowflake DDL for the canonical member table. Convert to BigQuery or Databricks →
Why This Term Matters
Member and enrollment data governs who receives care and who pays for it — making it foundational to every downstream healthcare analytics workflow. Data engineers who understand member terminology build eligibility pipelines that prevent coverage gaps, correctly identify dual-eligible members, and support accurate risk adjustment submissions to CMS. Enrollment errors directly affect capitation payments and can trigger CMS corrective action plans.
Related Content
Related Definitions
Looking for more healthcare terms?
Browse our complete library of 100,000+ standardized healthcare data terms
Browse All Terms