340B ESP is implementing an entity access check for claims submissions. With this update, users will only be able to submit claims for 340B IDs they are authorized to access in 340B ESP.
Before this functionality becomes available, users should review their current 340B ID access and confirm that the appropriate members of their organization have access to the entities they submit claims for.
What’s changing?
Once this update is live, users will only be able to submit claims for entities where they are registered to the specific 340B ID in 340B ESP.
During the submission process, claims associated with 340B IDs the user does not have access to will be excluded from the Selected Row count in the Submission Summary and will not be included in the submission.
This helps ensure claims can only be submitted by users with appropriate access to the associated covered entity.
How to prepare
Before this update, review your organization's existing access in 340B ESP.
From the Entity Profile, you can:
Review your 340B ID access and confirm that all entities you submit claims for are visible.
Review your team's access to confirm the appropriate users are associated with each 340B ID.
Invite new users to an entity using the Invite New User functionality when additional team members need access.
Learn: To learn how to give additional team members access to an entity, see How to Invite a User to Your Covered Entity.
If your organization uses a Third-Party Administrator (TPA) to submit claims, also review your TPA permissions under Settings. Confirm that the TPA has the appropriate access code and permissions to submit claims for the applicable entity.
Taking these steps in advance can help prevent claims from being excluded from future submissions because of missing 340B ID access.
Learn: For more information about reviewing and managing TPA permissions, see Partners & TPA Permissions.
Need access to an additional 340B ID?
If you are an authorized user for a 340B ID that is not currently visible in your Entity Profile, select Enroll New Entity to begin registering the entity in 340B ESP.
If the 340B ID is not available for enrollment, it is likely that the entity has already been registered in 340B ESP. In this case, you must request access from an Admin currently registered to that entity.
Learn: If you need access to an additional 340B ID that has not yet been enrolled in 340B ESP, see How to Enroll Additional Entities in 340B ESP.
What’s next?
We recommend reviewing your Entity Profile, your team's access, and any applicable TPA permissions before the update becomes available.
Continue to check What's New for the latest release information, and visit the 340B ESP Support Calendar to register for upcoming events and live learning opportunities.
Still have questions?
If you have questions or need additional help, our team is here for you — please feel free to reach out using any of the contact options below:
Chat: Available via in-app messenger
Email: [email protected]