Hi,

The quarterly registration period closed earlier this month— did your entity add new contract pharmacies? If so, SectyrHub 340B is here to help you manage your Pharmacy Services Agreements (PSAs). 

Learn how to import your newly registered contract pharmacies from OPAIS, add new PSAs and revise existing ones within SectyrHub 340B. Ditch the static Excel sheets and hectic Shared Drives for SectyrHub’s logic-specific workflows and transform how you keep your 340B Program up to date. 

Did you know...

“Discrepancies” occur when the information in OPAIS is updated and no longer matches the information in SectyrHub 340B. There are two scenarios: 

• When new contract pharmacies are added, the discrepancy will read “Pharmacy Missing” and display the name of the newly added contract pharmacy. Once the new pharmacy is brought into SectyrHub 340B, it will pop-up as needing coverage within a contract pharmacy agreement. 

• When an existing contract pharmacy is updated, the discrepancy will read “Pharmacy Value Changed” and will display the old and new values for you to review. When a new value is confirmed and pulled into SectyrHub 340B, it will overwrite the old value— prompting users to add amendments as needed. 

Within the PSA workscreens, users can indicate which contract pharmacies are covered within the agreement by selecting them from a pre-populated dropdown list. SectyrHub 340B’s built-in logic finds which contract pharmacies have not been associated with an agreement and lists them out for the entity to review.  

As new contract pharmacies are added via the OPAIS import, they are added to the list of pharmacies needing coverage— providing another check and balance so that no pharmacy is left uncovered. 

Organization Oversight - The System Perspective 

System Users (those with access to all covered entities within SectyrHub 340B) can maintain a high level of oversight over the OPAIS discrepancies and Pharmacy Services Agreements status and drill down to the entities requiring attention. 

On the System Dashboard, the OPAIS tile displays how many OPAIS discrepancies and follow-ups exist throughout the system. Clicking the tile will display all entities with discrepancies and follow-ups and shows the number of each in red. Clicking the red numbers will take you directly to the discrepancies listing page for the given entity. Seeing a lot of discrepancies and follow-ups at your orgnaziation?  

Also on the System Dashboard, the Requirement Status Tile for PSAs displays the number of covered entities that fall into each compliance status.  

• Red represents entities that have failed to provide any documentation related to the requirement;  

• Yellow represents entities that have one or more deficiencies related to the requirement;  

• Green represents entities that have no recognized deficiencies related to the requirement.  

Click each number to see a listing of which entities fall into the given status. Where are the covered entities at your organization falling? 

Compliance Insight -

Per HRSA, PSAs must include language for child-sites. Your entity may choose to: 

1. List all pharmacy sites locations by name and address. If so, the names and addresses for each site must match between OPAIS and the agreement. 
   
   or

2. Incorporate an all-inclusive statement that demonstrates that all child-sites listed in the OPAIS database under the parent-site are covered by the agreement. The pro of an all-inclusive statement? No need to add amendments when changes are made to child-sites or new ones are added!