Pharmacy contracting in a health system is unusually fragmented. Group purchasing agreements are managed by supply chain, wholesaler agreements by pharmacy operations, contract pharmacy arrangements by the 340B program office, and payer terms by managed care. Each function keeps its own records, and each set of records is complete from that function’s perspective. What almost never exists is a single view of which agreements apply to which entity and location.
That matters because 340B program compliance turns on exactly those relationships. The prohibition on group purchasing organization arrangements for covered outpatient drugs applies to specific covered entity types, which means the applicable purchasing route depends on entity classification. Contract pharmacy arrangements must be documented. Child sites must be registered and their eligibility maintained. Every one of these is a records question before it is a policy question.
This article covers where contract records sit in a health system pharmacy program, which obligations need active tracking, what auditors ask for, and how a system can consolidate the records without reorganizing the functions that own them.
The agreements that make up the picture
A single covered entity operates under several overlapping agreement types, each with a different owner and a different lifecycle. The compliance question usually requires two or three of them at once.
- Group purchasing agreements, membership and participation terms, committed volume tiers and the product categories in scope, which determine where the prohibition is relevant
- Wholesaler and distributor agreements, account structure, pricing accounts and the mechanics that separate purchasing routes at the ordering level
- Contract pharmacy agreements, the documented arrangement with each contract pharmacy, including service scope, fees, data flow and audit rights
- Manufacturer and specialty agreements, limited distribution terms, product-specific conditions and any restrictions relevant to program participation
- Payer and PBM agreements, reimbursement and network terms that interact with dispensing arrangements and with duplicate discount controls
These agreements are negotiated on different cycles by different teams, and none of them is wrong on its own. The gap is relational. Nobody can produce, for a given entity and location on a given date, the set of agreements that governed purchasing and dispensing. That is precisely the question an audit asks, and reconstructing the answer from four systems is slow and rarely complete. The reconstruction also has to be repeated the next time the question is asked, because nothing about the first effort is retained in a form the next reviewer can use.
Health systems add, close and reclassify locations continuously through acquisition, service line change and site relocation. Contract applicability follows entity and location, so a contract record that is not linked to a maintained location list becomes inaccurate without anyone editing the contract. Linking agreements to entity and site records is what keeps applicability current.
Obligations that need active tracking
Beyond eligibility, pharmacy agreements create ongoing obligations that are frequently treated as background terms rather than monitored commitments.
- Contract pharmacy data and reporting. Agreements typically define what dispensing data flows back, in what format and on what cadence, and that data underpins the covered entity’s own oversight
- Audit and access rights. The covered entity retains responsibility for compliance at contract pharmacies, so audit rights need to be exercisable and actually exercised on a defined cycle
- Fee structures and true-up. Administrative and dispensing fee terms often include periodic reconciliation, which goes unclaimed when nobody owns the calculation
- Notification of location or status change. Changes in entity status, site registration or pharmacy participation should trigger contract review, which requires the trigger to be wired rather than assumed
- Record retention. Program records must be retrievable for the applicable retention period, and contract pharmacy records held by a third party need a contractual retention commitment
A five-step consolidation sequence
Step 1, Build the entity and location register
Start with the authoritative list of covered entities, registered child sites and their classifications. Contract applicability is meaningless without it, and in most systems it exists in the program office rather than in the contract system.
Step 2, Link agreements to entities and sites
Attach each agreement to the entities and locations it governs, with effective and end dates. This is the step that lets a system answer which agreements applied where on a given date, which is the form the audit question actually takes.
Step 3, Extract the obligations that carry audit exposure
Pull data reporting cadences, audit rights, fee reconciliation terms, retention periods and notification duties from contract pharmacy and wholesaler agreements into monitored records with owners.
Step 4, Wire change triggers between functions
Make site registration changes, entity reclassification and pharmacy participation changes generate a contract review task. Most compliance drift in this area originates in an operational change that never reached the contract owner, so the trigger is worth building even where the review it starts is short.
Step 5, Rehearse the audit request
Select an entity, a location and a date, and try to assemble the governing agreements, the contract pharmacy arrangement and the supporting obligation evidence. The elapsed time is the honest measure of readiness, and repeating the exercise quarterly is cheaper than discovering the answer during an actual review.
See pharmacy agreements linked to entities and sites
Walk through agreement applicability, obligation tracking and audit evidence on a health system portfolio.
Why this is a records problem rather than a policy problem
Health system compliance teams generally know the rules. Policies are documented, training is delivered, and the program office understands the requirements in detail. What breaks is the connection between the policy and the operational records that evidence it. A covered entity can have a correct policy on group purchasing and still be unable to demonstrate which purchasing account a specific location used in a specific month, because the account structure sits in the wholesaler system and the entity classification sits in the program office. The remedy is not more policy. It is making the contract record carry the entity and location linkage, the applicable dates and the obligations, so that the evidence is a query rather than an investigation. The same structural point applies across health system contracting generally, including payer agreements where amendment history and effective dating determine reimbursement, as covered in payer and provider contract automation.
Agreement types, owners and audit exposure
The table summarizes the main agreement types in a health system pharmacy program, their typical owner and the exposure created when records are incomplete.
| Agreement | Typical owner | Key records | Exposure if incomplete |
|---|---|---|---|
| Group purchasing agreement | Supply chain | Entities in scope, categories | Cannot evidence purchasing route |
| Wholesaler agreement | Pharmacy operations | Account structure by site | Ambiguous purchasing attribution |
| Contract pharmacy agreement | Program office | Scope, fees, data, audit rights | Undocumented arrangement finding |
| Manufacturer or specialty terms | Pharmacy and supply chain | Product conditions and limits | Unrecognized distribution limits |
| Payer and PBM agreement | Managed care | Network and reimbursement terms | Duplicate discount control gaps |
Pharmacy program compliance is examined through records, and health systems generally hold those records in the systems where they were created rather than in the structure the question requires. Building an entity and location register, linking agreements to it with dates, and extracting the obligations that carry audit exposure converts a multi-team reconstruction into a query. The functional ownership does not need to change for that to work, only the linkage between what each function already maintains. That is usually the argument that gets the project approved, because it asks supply chain, pharmacy and the program office to connect their records rather than to surrender them.
For related guidance, see GPO and medical device contract control for health systems, GPO and supply contract price accuracy for health systems and GPO and supply contract price compliance tracking.
