340B claims data submission is the process of reporting individual, transaction-level prescription data to a manufacturer's platform within a fixed window, usually 45 days, to keep a claim's 340B pricing intact. In this episode of 340B Pulse, Jason Bilyj, PharmD, ACE, Director of Pharmacy at Third Street Family Health Services, an FQHC in north central Ohio, explains why that process breaks down across four mismatched TPA platforms, what it costs when it does — roughly $200,000 a year — and what changes for covered entities when the 340B rebate pilot moves to a per-claim vendor model in 2027. In this episode, Jason — Director of Pharmacy at Third Street Family Health Services, an FQHC in north central Ohio that opened its own in-house pharmacy in 2023 — walks host Muhammad Atif through what claims-level submission actually costs: roughly $200,000 a year lost to manufacturer restrictions and errors, a support system that won't even give him a ticket number when something breaks, and a rejected claim for a prescription a patient had already paid for and picked up, thirteen days after it was filled.He grounds all of it in the patients on the other end — about 30 percent with transportation issues, half without reliable internet access, and 12 percent who are homeless — including the story of a patient buying insulin off Craigslist because her copay was too high, until Jason found her a year of free medication instead. He closes on what changes for covered entities when the 340B rebate pilot moves to a per-claim vendor model in 2027, and his direct advice for FQHC pharmacy leaders preparing for it now. 00:00 Cold open: "just upload the claims-level data" 01:37 Welcome to 340B Pulse 02:48 Meet Jason Bilyj, Director of Pharmacy at Third Street 04:01 From Giant Eagle retail to FQHC pharmacy 06:30 Inheriting a 340B program and the staff turnover problem 08:26 Why Third Street opened its own pharmacy in 2023 08:34 Transportation, connectivity, and homelessness in the patient population 12:25 Retail habits Third Street deliberately left behind 14:26 The insulin black market story and patient assistance funds1 6:16 The $200,000-a-year cost of manufacturer restrictions 17:03 Becoming a data detective inside claims-level submission 17:28 Four TPAs, four different reports1 8:58 A claim rejected after the patient already paid 23:17 Manufacturer transparency claims versus the ESP and TRUSO reality 26:44 No ticket number: accountability on a support portal 33:16 Proving you acted on time when the delay wasn't yours 37:25 A fair claims transparency model and the road to 2027 38:47 The 2027 per-claim vendor model and the 10-day WAC risk 43:23 Where AI and automation could help small FQHC teams 47:15 Rapid fire round 48:46 Jason's advice for new FQHC pharmacy leaders 50:30 Closing thoughts and thank youWhy do rural and safety-net covered entities depend on multiple TPAs for 340B claims submission? Because different contract pharmacy networks and platforms each use their own identifiers and report formats, so a covered entity working across several networks ends up manually reconciling data from every TPA to satisfy manufacturer submission portals. Why would a covered entity lose 340B pricing on a claim it submitted correctly? Because the 45-day submission window starts at the date the prescription was dispensed, not the date the covered entity can act on it — patient pickup delays, wholesaler pricing corrections, and TPA processing time can all push a valid claim past the deadline. What does Jason Bilyj want FQHC pharmacy leaders to do before the 2027 rebate pilot takes effect? Confirm which manufacturers are actually participating, model the cash-flow impact of fronting full drug cost for roughly 10 days before a rebate check arrives, vet a claims-tracking vendor on more than price, and start tracking capture rate weekly now. #340BProgram #FQHC #PharmacyOperations #CoveredEntity
