Thought Leadership

Cracking the Code of BIN/PCN/Group Data for Faster Benefit Verification

September

25

2025

Key Insights

  • BIN/PCN/Group (BPG) data is a frequently overlooked set of pharmacy claim identifiers that can streamline claims bridging and early benefit verification.
  • Manual preliminary benefit verification can take patient support teams up to two days per patient, which can lead manufacturers to enroll patients who already have coverage. This can cause pharma companies to run out of funding for their patient support services (PSS) programs.
  • Mapping BPG data to plan-level coverage details and delivering it via API speeds verification without requiring third parties to collect personal health information (PHI).

This article was originally published in Drug Channels. 

As patient access grows more complex, manufacturers need tools that reduce friction throughout the care journey. One valuable but frequently overlooked dataset is known as BIN/PCN/Group (BPG) data, which refers to a trio of identifiers used in pharmacy claims processing.

Unlocking the power of BPG data can transform claims bridging and streamline early benefit verification, helping pharma companies provide support to more patients in need.

What Is BPG Data, and Why Is It Elusive? 

A patient’s drug benefit insurance card features their name, member ID, and plan group name—which is assigned by the payer, and does not necessarily correspond to PBM naming conventions. Three essential numbers are also encoded in the card’s magnetic strip:

  • Rx BIN (prescription Bank Identification Number): This six-digit number identifies the specific insurance company or PBM processing the claim.
  • Rx PCN (Processor Control Number): This alphanumeric code identifies the specific benefit package within a payer.
  • Rx Group Number: This identifier points to the plan benefit structure within the payer, which indicates the correct coverage and pricing. Typically, this number identifies an employer, but it can also be a contract number for Medicare and Medicaid patients. Neither of these identifiers are easy to find or map, as CMS does not publish its contract ID numbers.

While most patients think of their insurance card as simple proof of coverage, it’s actually a vital key to the entire ecosystem of pharmacy claims processing. Each of these data elements—BIN, PCN, Group, member ID, and even the plan group name—plays a critical role behind the scenes.

In order to route a pharmacy claim to the correct adjudication system, a pharmacy technician needs four pieces of information: the patient’s member ID plus their BPG numbers. When a patient presents their card at the pharmacy, the pharmacist will enter the BIN and PCN to determine their out-of-pocket cost versus what their insurer covers. The group number further refines which plan rules and pricing apply to the claim, tying the patient’s coverage to the right benefit structure. Together, these data enable accurate claims processing, routing and coverage identification.

As there is no master database of all BPG numbers, many duplicates exist among adjudication systems and PBMs, which means that the same Rx Group number can be associated with several different BIN/PCN combinations. This complicates the plan matching process—especially for manufacturers, hubs, and support teams working directly with patients.

The Need for Preliminary Benefit Verification

For complex and high-cost therapies, many pharma companies offer Patient Support Services (PSS) to help with education and access. When a potential patient reaches out, PSS first needs to know if their insurance will cover the drug. As full benefits verification requires processing a test claim, PSS teams often prefer to do a “dirty” or preliminary benefit verification, which costs much less and does not involve protected health information (PHI).

However, it does cost time—and lots of it. Many PSS teams spend up to two days per patient to find the correct coverage data. After a manual Google search to find the patient’s likely Rx BIN number, the PSS rep then contacts the patient’s PBM to determine the patient’s Rx PCN and Rx Group number. Unfortunately, the PBM may not be able to interpret the patient’s BPG data and plan name to arrive at the correct pharmacy coverage and pricing information—leaving the PSS team (and the patient) in the dark.

Given this unwieldy process, PSS teams are often unclear on which patients truly need their financial support. Many pharma companies run out of PSS funding much earlier than expected, because they end up enrolling patients who already have full or partial insurance coverage for their brand.

Mapping Claims Data to Coverage Details

As pharma knows all too well, the primary challenge of integrating claims data with other datasets is the difficulty of mapping non-standardized terminology, as payers use their own coding and naming systems. Typically, an analyst may be able to identify the payer associated with a particular claim, but not the exact plan: the patient could be a member of any one of hundreds of plans.

When claims data is augmented with unique BPG fields, however, that data can be linked to plan-level hierarchies within payer coverage data—enabling fast identification of a patient’s plan. For example, MMIT’s Bridging as a Service solution can map BPG data from various source IDs to our coverage and restriction data. Clients are provided with their own custom-built databases, crosswalk tables, and API services for more powerful analysis.

Using an API to Speed Benefit Verification

Once the power of BPG data is unlocked, a pharma company’s PSS team can verify coverage at a much faster rate, reducing call times. When a patient provides their member ID, the manufacturer can use its claims database to identify the correct BPG data for that patient.

The PSS team can then send that BPG data to a third-party vendor via an API, receiving the patient’s coverage details for the specific therapy in return. Importantly, the use of an API means that the vendor in this scenario does not have to collect PHI, as the member’s ID is only used to find the BPG data. This removes the regulatory risk of sharing PHI with a third party.

The pharma company now has the information it needs to verify coverage details and determine which patients are good candidates for its financial assistance program. BPG data helps manufacturers fully evaluate access hurdles for every potential patient—before they spend their precious PSS dollars.

Learn how MMIT can help you streamline benefit verification with BIN/PCN/Group Mapping.

Frequently Asked Questions

What is BIN/PCN/Group (BPG) data?

BPG data refers to three identifiers used in pharmacy claims processing: the Rx BIN, which identifies the insurer or PBM processing the claim; the Rx PCN, which identifies the benefit package within a payer; and the Rx Group number, which points to the plan benefit structure. Together with the member ID, these identifiers allow pharmacy claims to be routed to the correct adjudication system.

How is the information on an insurance card used in practice?

Knowing how to use the information on an insurance card can prevent delays and complications during treatment, whether at the pharmacy, doctor’s office, or hospital:

  • At the Pharmacy: When a patient presents their card at the pharmacy, the technician uses the BIN and PCN to route the prescription claim to the right insurance processor. The group number ensures that the correct plan benefits are applied, allowing for accurate copays and coverage decisions.
  • At Medical Offices and Hospitals: For doctor visits or hospital admissions, the member ID and group name are used to verify coverage. In some cases, an authorization number may also be required for pre-approved procedures.
  • In Emergencies: Having the insurance card on hand allows hospital staff to quickly access BPG data to expedite benefit verification and ensure that care is delivered without unnecessary delays.
Why is BPG data difficult to find and map?

There is no master database of BPG numbers, and many duplicates exist across adjudication systems and PBMs, so the same Rx Group number can be tied to several different BIN/PCN combinations. As CMS does not publish contract ID numbers, Medicare and Medicaid group identifiers are even harder to map.

Why is preliminary benefit verification so time-consuming for patient support teams?

Without BPG data, PSS reps often have to search for a patient’s likely Rx BIN and then contact the PBM to determine the PCN and Group number. This process can take up to two days per patient, and the PBM may still be unable to provide the correct coverage and pricing information.

How can BPG data speed up benefit verification?

When claims data is augmented with BPG fields, it can be linked to plan-level hierarchies within payer coverage data, enabling fast identification of a patient’s plan. PSS teams can then send BPG data to a third-party vendor via API and receive coverage details for the specific therapy in return.

Carolyn Zele

Carolyn Zele

As a solution consultant for MMIT, Carolyn Zele helps pharmaceutical manufacturers simplify market access and prepare for launch success. Prior to MMIT, Carolyn spent numerous years in the payer/PBM space managing formulary teams and technology across both regulated and non-regulated lines of business. She holds a Master of Science degree from Colorado State University.

Related Posts
How Copay Accumulators and Maximizers Affect Pharma PAPs
April 10

How Copay Accumulators and Maximizers Affect Pharma PAPs

Read More
Market Access Trends Impacting Your Patient Assistance Program
February 13

Market Access Trends Impacting Your Patient Assistance Program

Read More
Related Posts

Rebates Take the First Hit: How MFN Pricing Is Reshaping Payer Strategy

whats-shaping-coverage-under-medicare-drug-price-negotiation

Competition, Not Discounts: What’s Shaping Coverage Under Medicare Drug Price Negotiation

glp-1s-crossroads-access-innovation

GLP-1s at a Crossroads: Access and Innovation

How Copay Accumulators and Maximizers Affect Pharma PAPs

How Copay Accumulators and Maximizers Affect Pharma PAPs

Market Access Trends Impacting Your Patient Assistance Program

Market Access Trends Impacting Your Patient Assistance Program

Topics
Stay In Touch

Be the first to know about new arrivals and promotions

NEW RELEASE: The State of Patient Access 2026