Products/axsID

axsID

Unify

One version of payer truth. axsID is a next-gen payer mastering engine that resolves fragmented BPG signals into a single, consistent identity — linking claims, formulary, coverage, lives, and contract data across a 7-level ontology.

BPG Signal ResolutionaxsID
Incoming Fragment
BIN610011
PCN9999
GROUPFEDEX
PLANNULL
DRUGDupixent
Resolved Identity
Payer Identity
BPG String610011~9999~FEDEX
PBMOptumRx
PayerUnitedHealthcare
PlanFedEx Corp — Commercial
ChannelCommercial Rx
ConfidenceHigh · 97%
Ontology Position
L1 ChannelCommercial
L2 PBMOptumRx
L3 PayerUnitedHealthcare
L4 PlanFedEx Corp
L6 FormularyUHC Commercial Natl
Illustrative data — actual results vary by source configuration
One version of truth

Your single source of payer truth across contracting, analytics, reporting, and pull-through

Payer reporting across teams — market access, commercial analytics, patient services, hub operations — often yields conflicting answers. Each data source has its own payer and plan names at varying levels of granularity. Specialty pharmacy data use BPG codes with no translation key. You can't confirm whether a formulary win actually delivered ROI because nobody's speaking the same language.

axsID is your data-agnostic translator — a next-gen payer mastering engine that provides consistency across contracting, pull-through, analytics, reporting, and patient services by resolving the many-to-many mapping problem without complex business rules.

axsID
One truth
IQVIA LAAD
Symphony
Komodo
MMIT
Veeva
Specialty Rx
Hub / Intake
Contract Rebate
Enrollment
Next Generation

Everything legacy payer mastering does — and what comes next

Legacy payer spine solutions translate BPG codes to payer entities and link formulary and coverage data. axsID does all of that — and goes further with deeper ontology, real-time APIs, patient-level payer spine backfill, and operational delivery that legacy tools were never designed for.

Previous Generation
Map BPG to payer entity
Payer spine linking across data sources
Formulary + coverage + lives linking
Inferred card matching for patient backfill
Batch data warehouse delivery
Pre-deal analytics + pull-through reporting
Commercial analytics teams only
axs — Next Generation
Deep identity resolution with confidence scoring
7-level ontology — plan, GPO, formulary, contract
Specialty, contract, rebate + hub data linking
axsPatient payer spine backfill — not synthetic cards
Real-time API + batch delivery
Account management, pull-through + hub ops
Built for hubs, FRMs + HCP offices — not just analytics
Capabilities

What axsID resolves

Every BPG fragment carries hidden structure. axsID decodes it into a full payer identity — with confidence scores and ontology positioning.

BPG String Resolution
Takes BIN, PCN, and GROUP fragments from claims, hub intake, or pharmacy data and resolves them to a full payer identity with PBM, payer, plan, and channel.
7-Level Ontology
Maps every payer identity to a normalized hierarchy: Channel > PBM > Payer > Plan > GPO > Formulary > Contract. No more flat payer lists.
Real-Time API
Sub-200ms resolution via REST API. Built for operational systems — hub intake, specialty pharmacy onboarding, FRM routing — not just analytics.
Confidence Scoring
Every resolution includes a match confidence score — High, Medium, or Low — so downstream systems can triage and route appropriately.
Multi-Source Linking
Connects claims, formulary feeds, coverage files, specialty pharmacy, hub, and contract rebate data through a single common key — replacing manual crosswalks.
Batch + Streaming
Process historical files in batch or resolve signals in real-time as they arrive. Same resolution engine, two delivery modes.
Architecture

A 7-level payer ontology

Legacy payer mastering gives you flat lists. axsID gives you structure — from channel to contract, with every level connected and navigable.

L1ChannelCommercial Rx
L2PBMOptumRx
L3PayerUnitedHealthcare
L4PlanFedEx Corp
L5GPO
L6FormularyUHC Commercial Natl
L7ContractTier Specialty · PA Required
Relationship Intelligence

Relationship types captured

How access actually works. axsID doesn't just map entities to levels — it captures the relationships between them, so you can navigate the payer landscape the way it actually operates.

Payer ParentPayerParent
Ownership
Parent and subsidiary relationships between payers.
PBM / TPAPlan Sponsor
Administration
Which PBM or TPA manages benefits for a sponsor or plan.
Claims ProcessorPayerPBM
Claims processing
Who processes claims for each payer or PBM, with effective dates.
PlanPharmaciesSpecialtyNetworks
Networks
Contracted relationships between payers, plans, and specialty pharmacies.
SponsorsPlan / Benefit
Sponsorship
How sponsors connect to plans and benefit programs.
ProgramPayer / Plan
Assistance eligibility
How payer and plan rules determine copay or assistance eligibility.
Enhanced with axsPatient

Patient-level payer spine backfill — not synthetic cards

Legacy approaches use synthetic card finders and tokenized patient claims to backfill missing payer spine data. axsPatient takes this further — using real patient-level signals like benefit design, medication history, and diagnosis data to fill gaps in the payer identity and add granularity that payer data alone can't provide.

The result is a richer, more complete payer identity — where missing plan attributes are backfilled by patient-level evidence, and confidence scores improve through cross-validation across data sources.

axsIDPayer Identity — Resolved
PBMOptumRx
PayerUnitedHealthcare
PlanFedEx Corp — Commercial
Plan TypeUnknown
DeductibleUnknown
Confidence87%
+ axsPatient signals ↓
Gaps filled
axsID + axsPatientEnhanced Identity
PBMOptumRx
PayerUnitedHealthcare
PlanFedEx Corp — Commercial
Plan TypeHDHP ← Patient signal
Deductible$3,200 · Met ← Patient signal
Confidence97% ↑ Cross-validated
Workflow

From fragment to identity in one call

01
Ingest
A BPG signal arrives — from a claim, hub intake form, or specialty pharmacy fill. It carries a BIN, PCN, and GROUP.
02
Resolve
axsID matches the fragment against our multi-source ontology — cross-referencing claims, formulary, coverage, and lives data.
03
Enhance
axsPatient signals layer on — filling missing fields, adding plan-type detail, and cross-validating to boost confidence scores.
04
Deliver
The full enhanced payer identity — PBM, payer, plan, channel, formulary + patient context — is returned via API or batch file.
Developer-Ready

One API call.
Full payer context.

Integrate axsID into your existing workflows with a clean REST API. Send a BPG fragment, get back a full identity with ontology positioning.

// POST /v1/resolve
{
  "bin": "610011",
  "pcn": "9999",
  "group": "FEDEX"
}

// → Response
{
  "pbm": "OptumRx",
  "payer": "UnitedHealthcare",
  "plan": "FedEx Corp",
  "channel": "Commercial Rx",
  "formulary": "UHC Commercial Natl",
  "lives": 74202
}
Results

Measured accuracy

89%
Patient-to-Payer Mapping
Improved from 45% to 89% accuracy on patient-to-payer resolution through axsID + axsPatient integration.
Actual client engagement, 2026
<200ms
Resolution Time
Full payer identity resolution from BPG fragment to plan-level context in a single API call.
Production benchmark
7
Ontology Depth
Channel through contract — every payer identity is positioned in a navigable 7-level hierarchy.
Platform architecture
Get started

Send us one BPG signal.
See what resolves.

Start with your data. See axsID in action before you commit.