Where an IDN List Stops Working
You can buy an integrated delivery network database today, and most of them hand you the same thing: a row per health system, a parent name, a facility count, a bed number, an address. That is enough to build a territory. It is not enough to work one.
Because the row leaves out the part that decides your quarter:
- Which of the thirty hospitals under that parent share a procurement function, and which still buy on their own
- Whether the enterprise IT committee holds authority over your category, or only over the EHR
- Whether the three conversations you have open inside that system are unrelated, or the same evaluation surfacing in three places
An IDN list is a snapshot of structure. Selling into an IDN is a question about movement.
What Is an IDN in Healthcare?
An integrated delivery network (IDN) is a healthcare organisation that owns, manages or governs multiple care delivery assets under one structure: hospitals, outpatient clinics, physician groups, post-acute sites, and usually centralised IT and procurement.
The defining trait is not size. It is integration, meaning shared governance, shared financial accountability and shared standards. A large hospital group whose facilities still buy independently may look like an IDN on paper but behave very differently when you sell into it. A mid-sized system with one procurement committee is.
"Size tells you how big the account is. Integration tells you how the account decides."
The Role IDNs Actually Play
IDNs are usually described as big hospital groups. They behave more like conglomerates, and they shape what the hospitals and clinics beneath them are allowed to do in three ways:
1. Standardising Usage
- Set or influence the vendors and platforms facilities may use
- Decide what becomes the enterprise standard
- Strip out variation between sites
If the IDN has not standardised you, you have not really scaled.
2. Centralising Decisions
- Enterprise IT governance
- Central procurement and contracting
- Clinical protocol alignment
Local hospitals may evaluate. The IDN often decides what scales.
3. Translating Pressure
- Align operations with reimbursement models
- Implement value-based care mandates
- Reset cost structures across the network
Pressure arrives at the top and lands at the bedside.
How IDNs Connect to the Ecosystem
IDNs sit at the intersection of capital, policy, and care delivery. Tap the nodes to see connections.
The Enterprise Engine
Select a numbered node on the visualization to read exactly how IDNs execute strategy across that specific part of the ecosystem.
What IDNs Care About
An IDN evaluates through an enterprise lens, never a departmental one. Something that works in one hospital is interesting. Something that works across thirty is worth a contract.
Common Mistakes Sellers Make
- ✕ Believing that winning one hospital will pull the rest of the IDN along
- ✕ Reading local enthusiasm as enterprise approval
- ✕ Waiting for organic spread in a structure built to prevent it
Each of these ends the same way: a stalled rollout, a champion with no budget, and a forecast nobody trusts.
Telling Local Interest From Systemic Movement
This is the call that decides whether a rep spends a quarter well, and it is the one thing no facility list can answer.
One facility. One champion. Activity that repeats nowhere else in the system. It is real, and it is capped at the site budget. It expands only if somebody above your champion decides it should.
The same category surfacing across facilities that share governance, with activity gathering near the enterprise function rather than the floor. It looks like scattered noise until you know which sites report to the same committee.
The difference never shows up in a list, because a list has no hierarchy in it. It appears only when you can see which facilities answer to the same authority and watch them at the same time. Every hospital in the graph is a node that either confirms or contradicts what the others are showing.
What You Get
Intent.Health makes integrated delivery networks visible as decision centres rather than logos.
The rollup, mapped
How hospitals, clinics and post-acute assets roll up into each of 1,023 IDNs, so a facility is never just an address on a row.
Where the decision sits
The function that holds authority for your category inside that system. Not a generic org chart, and not the loudest title you can find on LinkedIn.
Signals read together
Intent detected across multiple facilities inside the same IDN and interpreted as one picture, instead of arriving in your CRM as four unrelated accounts.
The local-versus-systemic call
Whether interest is contained at one site or moving through the structure. This is the judgement a database cannot make for you.
Everything is sliceable by state, specialty and system, so you can pull a hospital IDN list by state for a territory and still see the enterprise layer sitting above it.
Common Questions
What is an integrated delivery network database?
A structured record of U.S. IDNs and the facilities beneath them, typically covering parent organisation, facility type, location and size. We provide that base layer across 1,023 IDNs, plus the decision structure and intent signals a static database leaves out.
What is the difference between an integrated delivery network and a health system?
The terms overlap in everyday use. Health system describes ownership of multiple facilities. IDN describes integration across them: shared governance, shared contracting, shared standards. Every IDN is a health system. Not every health system behaves like one when you sell into it.
Can I get a hospital IDN list by state?
Yes. Coverage slices by state, specialty and system, whether you are drawing territory boundaries or checking exposure across a region.
How is this different from a healthcare IDN list I could compile myself?
Facility names are assemblable from public sources if you have the patience. What is hard to assemble is the reporting structure between those facilities and the signals moving across them at the same time. That is the work this does.