Automate 340B drug purchasing through a wholesaler API connection to submit 340B-eligible purchase orders generated by the TPA replenishment system

Verified steps

1. Establish a 340B purchasing account with a wholesale distributor (e.g., AmerisourceBergen's 340B program, McKesson's ClaritasMD, or Cardinal Health's 340B management platform); confirm the account is designated as a 340B account and not a GPO account in the wholesaler's system
2. Integrate the TPA's replenishment output with the wholesaler's ordering API or EDI order interface (typically EDI X12 850 Purchase Order or wholesaler-specific API); map replenishment-generated drug NDC, quantity, and ship-to location fields to the wholesaler's order format
3. Transmit 340B purchase orders to the wholesaler; receive EDI X12 855 Purchase Order Acknowledgment or API order confirmation; validate that the order was accepted as a 340B-priced order (not WAC or GPO pricing)
4. Receive the EDI X12 856 Advance Ship Notice (ASN) and 810 Invoice from the wholesaler; reconcile the invoice pricing against the HRSA-published 340B ceiling prices for the purchased NDCs (available at 340bpricing.hrsa.gov for covered entity users)
5. If any invoice price exceeds the 340B ceiling price, dispute the overcharge with the wholesaler and, if unresolved, submit a 340B pricing complaint to HRSA via the OPA complaint process
6. Maintain purchase records (NDC, quantity, 340B price paid, wholesaler invoice number) for a minimum of 3 years; these records are required for HRSA audits and internal 340B compliance audits