As the 340B manufacturer policy landscape continues to evolve, covered entities are increasingly being asked to manage requirements across multiple platforms. One platform becoming more prominent is Truzo, a drug discount management platform used by certain manufacturers to administer contract pharmacy policies, pharmacy designations, and claims-level data submissions.
What Is Truzo?
Truzo connects covered entities and pharmaceutical manufacturers through a centralized platform. Depending on the individual manufacturer’s policy, covered entities may use Truzo to:
- Register their organization and authorized users
- Designate eligible contract pharmacies
- Submit claims data
Truzo is designed to support greater visibility across drug discount programs, identify potential duplicate discounts, and help manufacturers and covered entities manage policy requirements. However, the actions required of a covered entity depend on each participating manufacturer’s individual policy.
Truzo and 340B ESP: Similar Purpose, Different Experience
For many covered entities, claims submission is not a new responsibility. After several years of working with 340B ESP, users have become familiar with its submission process, dashboard, and manufacturer-specific requirements.
Truzo introduces a separate platform and a different workflow. Although both platforms may be used by manufacturers to collect claims data and address potential duplicate discounts, registration, pharmacy designations, and claims submissions completed through one platform do not carry over to the other.
Some of the key differences include:
- Separate manufacturer participation: Covered entities must identify which manufacturers use 340B ESP and which use Truzo so the correct requirements are completed through each platform.
- Different dashboard visibility: Users may find that 340B ESP provides more insight into submission balances, outstanding requirements, and pharmacies that may be at risk under manufacturer policies.
- TPA reporting capabilities are still developing: Many TPAs have established reporting processes for 340B ESP after several years of use. While some TPAs can already produce Truzo-ready files, others are still developing or refining this capability. When a report is not available, covered entities may need to manually build submission files by identifying and matching claims for applicable NDCs.
- Separate monitoring is required: Because the platforms operate independently, covered entities must monitor both systems for submission requirements, pharmacy designation issues, and manufacturer policy changes.
Covered entities should not approach Truzo as an extension of an existing 340B ESP account. It requires separate onboarding, ongoing monitoring, and clear internal ownership.
Managing Truzo Requirements
Several manufacturers currently use Truzo to administer their 340B contract pharmacy requirements, including Alkermes, Amphastar, Argenx, Gilead, Organon, and Puma Biotechnology.
Missing a deadline, failing to designate an eligible pharmacy, or submitting incomplete data may affect access to 340B pricing for applicable products.
Covered entities should confirm:
- Which manufacturers require action through Truzo
- Whether contract pharmacy designations are required
- Which claims and data fields must be submitted
- How frequently data should be submitted
- Whether their TPA(s) can produce a Truzo-ready report
- Who is responsible for monitoring the platform
- How manufacturer policy changes will be identified and addressed
Staying Ahead of Platform Requirements
Truzo is another example of the growing administrative complexity surrounding manufacturer contract pharmacy policies. Covered entities should avoid treating registration or initial setup as a one-time task. Participating manufacturers, pharmacy designation rules, covered products, data requirements, and submission timelines may change.
Establishing clear internal ownership and regularly reviewing each manufacturer’s current policy can help covered entities prevent missed requirements and potential disruptions to 340B pricing.
As Truzo requirements continue to evolve, ACI can help covered entities stay current, manage platform registrations and pharmacy designations, coordinate claims submissions, and address issues before they affect access to 340B pricing. Contact ACI to learn how we can support your organization’s ongoing manufacturer policy management.