340B · CMS reporting for TPAs
Get your clients ready for CMS 340B reporting.
DevDocs helps TPAs build reporting workflows, onboard clients, and prepare for submission, starting with an audit of your claims data.
What CMS is changing, and where the DevDocs Audit fits
CMS's 340B claims repository accepts voluntary submissions starting October 1, 2026, and CMS has proposed required quarterly reporting for Part D 340B claims from covered entities that are Medicare providers and suppliers. Your platform is a practical starting point for reporting across your covered-entity clients. The audit identifies what can be handled centrally and what needs work with individual clients.
Target delivery schedule, subject to the audit and agreed scope.
- 1
DevDocs Audit
Oct to Nov 2026
- 2
DevDocs Sprint
Dec 2026
- 3
DevDocs Implementation
Jan to Mar 2027
- 4
DevDocs Hand-off
Apr to May 2027
- First required submission deadlineJun 30, 2027 (proposed)
Oct 1, 2026
Voluntary submissions open
Oct to Nov 2026
1. DevDocs Audit. Review the available claims data and reporting gaps.
Dec 2026
2. DevDocs Sprint. Plan the work identified by the audit.
Jan 1, 2027
Required reporting period begins (proposed)
Jan to Mar 2027
3. DevDocs Implementation. Carry out the agreed implementation work.
Apr to May 2027
4. DevDocs Hand-off. Review responsibilities with your team.
Jun 30, 2027
First required submission deadline (proposed)
Final rule expected with CMS's 2027 Physician Fee Schedule
The first required submission would cover January to March 2027 claims and be due Jun 30, 2027, if the proposal is finalized.
Starting this fall gives your team time to identify gaps and test the reporting process before the first proposed submission deadline.
See what the DevDocs Audit checks
Coverage across your clients
We map which covered entities, sites, and pharmacy relationships your data reaches, and where claims come from outside your platform, including in-house pharmacies, pharmacy networks, and specialty pharmacies.
Claim-level detail
We check whether your data carries the fields CMS requires, including the prescription or service reference number, fill number, NDC-11, and dispensing pharmacy NPI.
Roles and authority
CMS lets a TPA submit only with delegated authority to submit and certify, and each covered entity remains responsible for the accuracy of its data. We identify who reviews and certifies for each covered entity, and whether delegations to your platform are in writing.
What you get from the audit
A map of claims sources across your covered entities, a list of gaps, a plan for review and certification roles, and a clear scope for implementation, with recommended next steps.
Shared and client-specific work
We identify which changes can be made in your platform and which require work with individual covered entities.
How DevDocs solves it
DevDocs helps you bring claims data together, check the required fields, and prepare quarterly files for CMS reporting.
Sources
- TPA claims data
- In-house pharmacies
- Pharmacy networks
- Specialty pharmacies
DevDocs validation layer
- Brings claims data together
- Checks the required fields
- Removes duplicates
- Keeps an audit trail
CMS
Quarterly files prepared for CMS reporting
Implementation scope and submission responsibilities are agreed with your team.
What happens next
After the audit, we agree on an implementation and rollout plan with your team. The work can include building and testing the reporting workflow, onboarding clients, training your team, and supporting the first quarterly submission. We hand over runbooks your team can use to manage the process.
Two ways to work with us
For TPAs
Work with DevDocs to build CMS reporting into your platform, under your brand, for the covered entities you serve. We're looking for TPAs to run the first audits with us this fall.
For covered entities
Work with us alongside your TPA to prepare your claims data and reporting process. If your TPA isn't planning for CMS reporting yet, talk to us directly.
Submission support
We also offer a separate submission service for TPAs and covered entities. Under delegated authority, we format, validate, and file claims to CMS and archive the submitted files.
Who we are
DevDocs builds documentation systems and automation for enterprise teams. Michele Russell brings experience in 340B TPA sales and implementation, consulting, and audit services.
Talk to Michele
Questions about CMS 340B reporting or the DevDocs Audit? Call or email Michele directly.