How health systems review vendor contracts at volume

In a health system, the vendor contract you are asked to review is usually not the whole deal. The same purchase can sit under a national GPO agreement someone else negotiated, a local agreement your system signed, an order form the department accepted, and a BAA if the vendor touches patient data. Those layers were signed by different people, in different years, and they do not always say the same thing.

That is the actual review problem: four documents from four negotiations pretending to be one deal.

And the volume is real. Industry research published by AHRMM found the average hospital carries more than 1,200 GPO and local contracts and activates pricing for over 40,000 new line items every six months. Nobody is re-reading that portfolio annually. The teams that keep up treat review as an alignment job: get the layers into one file, then check them against each other.

Why the layers disagree

A Wharton School survey done for the American Hospital Association found hospitals route a bit over half of purchases through their national GPO, with the rest split across regional and local GPOs, self-negotiated contracts, and off-contract buys. So on any given vendor, the pricing terms may have been negotiated by your GPO while the service terms were negotiated by your own team, on a different timeline, by people who never compared notes.

Then the vendor's order form shows up. Order forms and quotes tend to carry the vendor's standard terms on the back, and departments sign them to get equipment installed or a renewal processed. If nobody checks that paper against the agreement your system actually negotiated, the file now holds two versions of the deal and nobody knows it.

The BAA has the same problem in the other direction. It often gets signed once, early, from a template, and then nobody looks at it again while the services agreement underneath it gets amended two or three times.

What contract intake should capture

The fix starts at intake, not at review. When a vendor file comes in from a department, start by asking what else governs this vendor. A workable intake step captures three things: which GPO agreement covers the purchase if any, whether a local agreement already exists with this vendor, and whether patient data is involved so the BAA belongs in the file.

That takes minutes per file when it happens at intake. It takes hours when a dispute forces someone to reconstruct the stack two years later.

Running the first pass against a short playbook

Once the stack is assembled, the first-pass review is two checks, and they are different jobs.

The first check is the local agreement and order form against your playbook: the liability cap, the termination terms, the renewal mechanics, the data terms, whatever your short list of positions is. This is repetitive work across hundreds of files, which makes it the natural place to put an AI first pass on the review queue. Software will not tell you whether a deviation matters to this vendor relationship. What it can do is flag which files deviate from your positions, so your reviewers spend their time on those instead of paging through the ones that match.

The second check is document against document: does the order form contradict the negotiated agreement, does the amended services agreement still line up with the BAA, does the local deal undercut the GPO pricing tier you thought applied. This is the check that gets skipped under volume pressure, because it means opening files nobody sent you. It is the same failure mode that lets contract exhibits drift away from the approved terms, just spread across separate documents instead of separate attachments.

The one number worth watching

If you want a single measure of whether this is working, track how many active vendor files contain the complete stack: governing agreement, current order form, and BAA where one exists. A file with all the layers present can be reviewed in one sitting. One that is missing layers turns into a chase across inboxes, and the chase usually starts after something has already gone wrong.

Get that number up and reviews get faster on their own, because nobody has to go hunting for paper before the real work starts.

Try goHeather free and run a first pass on your own vendor stack. This is legal information, not legal advice; consult a lawyer for legal advice.