The relationship master for access. It doesn't just normalize codes; it models the real-world roles between payers, PBMs, plan sponsors, processors/TPAs, specialty networks, GPOs, and assistance programs — and makes that graph consumable at the right grain for both analytics and operational workflows.
AxsID ingests BIN/PCN/GROUP and medical plans from claims, processor lists, and multiple payer sources; resolves conflicts (one processor per BIN); and ships crosswalks to keep downstream systems stable.
Comprehensive coverage of all access relationship participants
Parent organizations and holding companies that own multiple payer entities
Legal entity with channel specification (Pharmacy vs Medical)
Benefit manager and switch/claims routing processor
Employer/group, government program, or association
Third-party administrator where applicable
Option/LOB, metal tier, benefit year specifications
Comprehensive relationship modeling for access complexity
Payer Parent → Payer
PBM/TPA → Plan Sponsor/Plan
Processor → Payer/PBM with effective dating
Payer/Plan ↔ Specialty Pharmacies
Plan Sponsor → Plan/Benefit Program
Assistance Program ↔ Payer/Plan rules context
Choose the right grain for the job
Processor + BIN (+ PCN/GROUP when applicable)
Canonical Payer ID (channel-specific) with effective-dated parent ownership
Payer + Plan/Benefit Program (+ LOB + Product + Year)
Plan Sponsor + Plan with PBM/TPA role links
Plan ↔ Specialty Pharmacy relationship (in/out-of-network)
Plan or Payer rules mapped to copay/PAP eligibility signals