TLDR
- A health system with 1,200 vendor contracts has 719,400 possible pairs to compare, which is far more than any team can review by hand.
- Overlapping agreements tend to come from four predictable places: mergers, decentralized contracting, vendor name changes and renewals that get entered as new records.
- Every overlap costs money, and many carry compliance risk when they involve physician services, referral sources or a missing BAA.
- Finding overlaps after the fact is cleanup. Ntracts flags a likely match before the second record is ever created.
The math nobody runs.
Every healthcare vendor consolidation project starts with the same goal of fewer vendors, better terms and cleaner spend. Almost every one also turns up something nobody planned for: two, three or even four active agreements with what turns out to be the same company. For procurement, that's leverage lost without anyone noticing. For legal, it's terms nobody ever reconciled. For IT, it's vendor master data that no longer tells the truth about who the organization does business with.
None of this means someone was careless. Picture a mid-sized health system with 1,200 vendor contracts, all stored in a centralized contract repository. Someone gets asked a simple question: do we have any overlaps? To answer it for sure, they'd have to hold each contract up against every other one, which comes out to 719,400 comparisons.
Say they're quick and spend just 30 seconds on each pair. That's still about 6,000 hours, or close to three years of full-time work, and by the time they finish, new contracts have come in. The hardest pairs aren't exact duplicates, either. They're near matches, like a slightly different legal name, a new billing address or a contract filed under a department instead of the parent company.
So, no one does the full review. Teams lean on memory, a search bar and whoever happens to recognize a vendor name, which catches the obvious matches but misses the ones that matter most.
Where overlapping contracts come from.
Overlaps aren't random. In healthcare they tend to come from the same four places.
1. Mergers and acquisitions.
When two organizations come together, their contract portfolios come with them. Both sides may already work with the same lab, staffing agency or software vendor on different terms, and after the deal closes those agreements land in one repository under slightly different names while both stay active. Integration teams are usually focused on bigger priorities in the first year, so contract consolidation tends to wait until renewal season forces the issue.
2. Decentralized contracting.
A hospital's pharmacy, radiology department and outpatient clinic can each sign with the same supplier without knowing the others already have. Each agreement looks reasonable on its own, but together they split your volume across three price points and leave negotiating leverage on the table. The more facilities and service lines a system adds, the more often this happens, which is one reason so many vendor rationalization efforts start here.
3. Vendor name and entity changes.
Vendors rebrand, get acquired and contract through subsidiaries, so "Midwest Imaging Partners" and "MIP Holdings LLC" may be the same counterparty even though a search for one won't surface the other. This is also where compliance risk tends to hide. Two separate agreements with the same physician group can add up to total compensation that no one ever reviewed for fair market value.
.png?width=685&height=315&name=image%20(5).png)
4. Renewals and migrations that become new records.
When a renewal gets entered as a new contract instead of an amendment, the same relationship ends up with two records. Moving off a legacy system or shared drive does the same thing at scale, leaving old and new versions both marked active while the obligations in each slowly drift apart. Over time, nobody is sure which version actually governs the relationship.
The cost goes well beyond spend. Overlapping agreements can carry conflicting terms, uneven indemnification and mismatched renewal dates. When one of them involves a referral source, it raises Stark and Anti-Kickback questions, and when one involves protected health information, it's easy to find a BAA on one record and assume it covers the other. If an auditor asks for every arrangement with a given physician or vendor, an incomplete answer becomes a problem of its own.
Finding isn't the model. Preventing is.
Most healthcare contract management tools treat overlap as a search problem. They build a dashboard that surfaces the exposure and then wait for someone to log in and look, which still leaves the 719,400 comparisons on a person's plate, just with a nicer screen to work from.
A dashboard assumes someone has the time to act on it. In most health systems, the people who would act on it are already stretched across renewals, audits and new requests, so the flagged items sit until the next consolidation project brings them back up.
Supplier rationalization projects follow the same pattern. Teams clean up the overlaps they can find, and new ones start forming the following week because nothing changed at the point of entry.
A better approach is to build prevention into contract lifecycle management itself and stop the second record before it exists. Ntracts uses AI to check each new party and contract as it's entered, and when something looks like a likely match for a record already in your repository, the system flags it right then, before a second record is created.
That shift changes who does the work and when. The person entering the contract sees the potential match in context and decides whether to amend the existing agreement, link the two or confirm they really are separate. There's no quarterly cleanup and no spreadsheet of suspected matches waiting for someone to get to it.
Consolidation will always turn something up. The goal isn't to run a bigger cleanup every few years. It's to catch the overlap the moment it tries to enter your system, so your next consolidation project starts from a clean repository and there's far less to find the next time around.
Wondering how many of your vendors show up more than once?