Submit an NCPDP Telecom standard B1 claim transaction and process a B2 reversal for a pharmacy billing workflow

domain: ncpdp.org · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Build the NCPDP Telecom D.0 (or current version) B1 claim request: fixed-width or variable-length segments grouped into Transaction Header (Segment ID 'AM'), Insurance (Segment ID 'AM' group B1), Patient (Segment ID 'CA'), Claim (Segment ID '07'), Pricing (Segment ID '11'), and Prescriber (Segment ID '03') segments
  2. Populate mandatory claim fields: NCPDP Provider ID (Field 201-B1), Date of Service (401-D1 CCYYMMDD), RxNumber (402-D2), Drug NDC (407-D7 in 11-digit format), Quantity Dispensed (442-E7), Days Supply (405-D5), Compound Code (406-D6), DAW Code (408-D8), and the primary payer BIN/PCN/Group from the insurance card
  3. Submit the request to the PBM or payer switch via HTTPS or VPN-secured TCP; the response returns a header with Response Status (Field 501-F1): 'P' for paid, 'R' for rejected, 'D' for duplicate
  4. On a 'P' response, parse the Pricing segment response fields: Ingredient Cost Paid (506-F6), Dispensing Fee Paid (507-F7), Patient Pay Amount (505-F5), and Other Payer Amount Recognized (565-J4) for copay calculation and patient receipt
  5. For a B2 reversal, build a new transaction with Transaction Code 'B2': reuse the original claim's BIN/PCN, Service Provider ID, Date of Service, Rx Number, and Fill Number exactly; submit within the payer's reversal window (typically up to 30 days, but varies)
  6. Confirm reversal with response status 'P' on the B2 transaction; a 'R' reversal rejection with reject code '88' (DUR reject) or '14' (M/I Date of Service) indicates a field mismatch with the original claim

Known gotchas

Related routes

Submit an NCPDP Telecommunication D.0 B2 Claim Reversal to void a previously adjudicated pharmacy claim
ncpdp.org · 6 steps · unrated
Implement an NCPDP SCRIPT 2017071 RxFill transaction flow to receive dispense status confirmations back at the prescriber's EHR from the pharmacy
ncpdp.org · 6 steps · unrated
Handle an NCPDP SCRIPT RxChangeRequest to process a pharmacy change request
ncpdp.org · 6 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans