What Is a Pharmacy Claim Switch?
Every time a pharmacist scans a prescription and submits it to insurance, a claim travels through an invisible piece of infrastructure called a pharmacy claim switch. Billions of transactions per year flow through these systems. If you're building pharmacy software, understanding switches is essential.
The air traffic controller of pharmacy claims
A pharmacy claim switch is a routing layer that sits between pharmacies and Pharmacy Benefit Managers (PBMs). Think of it like a network router — the pharmacy sends a claim to the switch, and the switch determines which PBM or insurance company should receive it based on the BIN (Bank Identification Number) and PCN (Processor Control Number) on the claim.
The switch then forwards the claim using the NCPDP Telecommunication Standard, waits for the PBM to adjudicate it (approve, reject, or return information), and routes the response back to the pharmacy. All of this happens in real time — typically under 2 seconds.
The major pharmacy switches
The US pharmacy claims ecosystem is dominated by a handful of switch vendors:
RelayHealth (McKesson)
One of the largest switches, deeply integrated with McKesson's pharmacy distribution and technology ecosystem.
Change Healthcare (Optum)
Massive healthcare technology company handling claims across pharmacy and medical. Now part of Optum/UnitedHealth.
Rx Linc
Pharmacy switch network with a focus on data intelligence and risk management alongside claims routing.
Emdeon / Inovalon
Legacy switch infrastructure that's been consolidated through various acquisitions.
How BIN/PCN routing works
Every insurance card has a BIN number and PCN. These two fields tell the switch where to route the claim:
- 1.Pharmacy submits claim with BIN + PCN to their switch
- 2.Switch looks up BIN in routing table to find the destination PBM
- 3.Switch forwards the NCPDP-encoded claim to the PBM
- 4.PBM adjudicates: checks formulary, applies copay, runs DUR
- 5.PBM sends response back through the switch to the pharmacy
What switches cost
Switches typically charge $0.05 to $0.07 per claim for pharmacy claims processing. For a pharmacy doing 3,000 prescriptions per month (running approximately 5,000 claims to account for rejections and resubmissions), the annual switch cost is roughly $3,000–$4,200.
Beyond the per-transaction fee, switches may have monthly minimums, setup fees, and implementation costs. These are typically negotiated based on volume and bundled with other services. Some pharmacy management systems (PMS) include switch fees in their software pricing, making the cost less visible to the pharmacy.
The problem for developers
If you're building pharmacy software and need to submit claims, you have a significant integration challenge:
- • You need a contract with a switch vendor — not a self-serve signup
- • You must implement the NCPDP Telecommunication binary protocol from scratch
- • You need NCPDP certification for production access
- • You must manage payer sheets — per-payer field requirements that change regularly
- • You need a pharmacy NPI and associated licensing
- • The entire process takes months from start to first production claim
This is the exact problem Starlight solves. Instead of negotiating switch contracts and implementing binary protocols, you make a JSON POST request and we handle everything else.
Skip the switch contract
Starlight gives you JSON REST access to the pharmacy claims network. No binary protocol. No certification. No NPI required with Instant Access.