You administer an influenza vaccine. Depending on how the patient is covered, that single act produces one of two entirely different claims, on two different standards, paid on two different timelines, and judged against two different rulebooks.
The pharmacy rail you already run in your sleep. The medical rail is where money goes missing, and it goes missing quietly, because the failure mode is not a rejection at the register. It is a claim nobody ever built.
Two standards, not one
The NCPDP Telecommunication Standard (version D.0 is the currently adopted HIPAA standard) is a conversation. You send BIN, PCN, group, cardholder ID, NDC, quantity, days supply, DAW, prescriber NPI, your NPI as service provider, usual and customary. Two seconds later you have an answer and a patient responsibility amount, and the patient is still at the counter.
An ASC X12N 837 Professional claim is a letter. The current version is 005010X222A1. You send it to a clearinghouse in a batch, you get a 277CA acknowledgment telling you whether it was even accepted for adjudication, and then, days or weeks later, an 835 remittance advice tells you what happened.
The vocabulary changes completely:
- CPT and HCPCS Level II for the service and the product, with units
- ICD-10-CM for why you did it
- Place of service (01 is Pharmacy)
- Modifiers where the payer wants them
- A billing provider, and usually a separately identified rendering provider
Eligibility is its own transaction (270 out, 271 back). Claim status is another (276 out, 277 back). Denials arrive as CARC and RARC codes on the 835 and do not map onto anything you know from NCPDP.
The same flu shot, two ways
Quadrivalent influenza vaccine, 0.5 mL, intramuscular, adult patient.
| Pharmacy rail (NCPDP) | Medical rail (837P) | |
|---|---|---|
| Product identified by | 11-digit NDC | CPT product code, e.g. 90686 |
| Quantity | 0.5 metric decimal, 1 day supply | 1 unit |
| Administration | Bundled, or paid through a professional service fee field | Its own line. 90471 for the first injectable vaccine, +90472 for each additional. For Medicare Part B, G0008 |
| Diagnosis | Not required | Required. Z23 |
| Place of service | Implied by your NPI | POS 01 |
| Outcome known | Seconds | Days to weeks |
| Money collected | At the counter | When the 835 posts |
| Denial language | Reject code 70 | CARC 16, 96, 109, 197 |
For a Medicare patient, the routing is statutory, not a preference. Part B covers influenza, pneumococcal, COVID-19, and hepatitis B for beneficiaries at medium or high risk, along with their administration. Everything else commercially available and reasonable and necessary, including shingles, Tdap and hepatitis B for low-risk patients, sits under Part D. Since 1 January 2023 the Inflation Reduction Act has required Part D plans to cover ACIP-recommended vaccines at zero cost sharing, which removed the copay conversation but did not move a single vaccine between benefits.
Commercial plans vary genuinely: some pay everything through the PBM, some carve vaccines to medical, and some split the product and the administration across the two.
Where the money goes
Reject 70 reads as final. “Not covered on the drug benefit” and “not covered” are different statements. If the plan pays the vaccine on medical, that reject is a routing instruction. A technician trained only on NCPDP reads it as the end of the conversation and the patient walks.
Nobody owns receivables. Your operation is built around same-day reconciliation. Medical claims create an aging bucket that has to be worked: acknowledgments checked, denials categorised, corrected claims resubmitted, secondaries filed after the primary posts. Unassigned, that bucket becomes a write-off bucket.
Timely filing expires in silence. Medicare fee-for-service is 12 months from the date of service, with no appeal on the deadline itself. Commercial windows are frequently shorter. Unbuilt claims from October are worthless by the following autumn, and nothing in your dispensing system will raise a hand.
No diagnosis in the workflow. Dispensing never needed an ICD-10 code, so nothing captures one. If Z23 is not recorded at the moment of service, someone is reconstructing it later from an immunisation log.
The rendering provider is not enrolled. Many payers require a rendering individual and will only pay if that individual is enrolled and contracted with them specifically. A clean claim from a pharmacy with only a type 2 NPI still denies.
Units and edits. CPT units are not NDC quantities. Some payers additionally require the NDC and drug quantity on the professional line, carried in the drug identification and drug quantity segments of the 2410 loop. And the National Correct Coding Initiative medically unlikely edits will deny 90472 when more than five units appear on a single claim line, which catches multi-vaccine encounters coded lazily.
Decide the rail before the vial leaves the fridge
Two steps, and both are cheapest before administration.
- Check both benefits. A 270/271 against the medical plan tells you whether the patient is active and what the vaccine benefit looks like. A test claim on the pharmacy rail tells you what the PBM will do. Most dispensing systems can do the second and not the first, which is why this ends up as a portal login and a phone call.
- Know the benefit category for that payer. The Part B versus Part D split is fixed and belongs on a card at the immunisation station. For commercial plans it is a per-contract fact you look up once and then need somewhere durable to keep.
The minimum infrastructure
If you are running meaningful vaccine volume, or moving into point-of-care testing, contraception or travel health, the medical rail stops being optional. You need:
- A clearinghouse relationship with 837P submission and 835 retrieval
- ERA and EFT enrolment with each payer, so remittances arrive electronically rather than as paper you have to key
- Capture of the ICD-10 code, the rendering pharmacist and the consent at the point of service, not afterwards
- One named person working denials weekly, with a written escalation path
- A record of which payer routes which product to which benefit
None of it is exotic. It is the ordinary equipment of a medical practice applied to a business that has never needed it, and the gap between the two is where the leakage lives. Attergo Billing sits on that gap, reading the dispensing event through Attergo Integrations as it happens and flagging fills that should have produced a medical claim and did not.