Health Care Facilities · Definitive Healthcare
Definitive Healthcare Hospital, IDN and Post-Acute Facility Intelligence
Datadory delivers definitive healthcare hospital idn and post acute facility intelligence data covering more than 9,000 hospital and IDN profiles, 100K+ post-acute organizations, 22K+ imaging centers and 14K+ surgery centers, each carrying affiliations, Medicare claims by DRG, technology installs and named executive contacts. Delivered as an API, files, or straight into your warehouse.
API, files, or your warehouse. Daily, weekly, or hourly.
- Where it covers
- United States across hospitals/IDNs, post-acute, imaging, ASC, clinic/FQHC, physician group and ACO/HIE/payer universes; claims products add prescription detail
- How far back
- Maintained current-state profiles rather than an archived time series; universe counts observed at the August 2026 review
- How fine
- One profile per facility or organization, with network/member/episode-level elements beneath for episodic care
What is the Definitive Healthcare Hospital, IDN and Post-Acute Facility Intelligence dataset?
It is the broadest single view of the US care continuum in this catalog, and the only one pairing claims depth with named human beings. Eight universes share one keyed structure: more than 9,000 hospital and health system profiles through HospitalView, 100K+ post-acute organizations (nursing, assisted living, home health, hospice) through LongTermCareView, 22K+ imaging centers, 14K+ ambulatory surgery centers, 60K+ clinics and FQHCs, 130K+ physician groups, 4.5K+ ACOs, HIEs and payers, with billions of de-identified all-payor claims underneath.
Hospital profiles span nine institution types - short-term acute care, long-term acute care, critical access, VA, pediatric, Department of Defense, psychiatric, rehabilitation and religious non-medical - and carry the org chart and the operating reality on the same record: affiliations and parent/child system structure, financial performance, staffing, physicians, quality metrics, technologies installed by category, vendor and product, purchasing information, referrals, episodes of care, study activity, population data, Medicare-certified bed counts and operating room square footage. Medicare claims ride along broken out by DRG, diagnoses, procedures, revenue centers, cost and readmission measures, and claim origination/destination.
Two things separate this from a directory. Claims enrichment turns each facility into measurable volume, and every profile names its executives - department, title, email, phone, LinkedIn - scored for likelihood of technology investment. Universe counts drift between marketing pages (9,000+ versus 9,300+ hospitals); figures here were read at the August 2026 review. Get a sample of this dataset cut to the segments you sell into.
What do sample records look like?
Shapes first, cells second. The vendor publishes no public sample profiles, and Datadory does not print numbers it cannot stand behind - so below is the documented anatomy every record carries, with placeholders that resolve when your sample is cut:
# hospital / IDN profile -- one row per facility or health system
facility_profile_id : <atlas profile identifier>
affiliations_and_partnerships : <system components; parent/child
relationships across the network>
medicare_certified_bed_count : <certified beds on the profile>
operating_room_square_footage : <OR square footage>
technology_installations : <category > vendor > product>
drg_claims_volume : <inpatient Medicare claims, split by
DRG, diagnoses and procedures>
quality_metrics : <quality measures on the profile>
predicted_buyer_score : <likelihood-of-investment score>
# executive_contacts -- carried on the same profile
<name> | <department> | <title> | <position level>
<email> | <phone number> | <linkedin profile>Read it as two joined layers. The profile layer answers scale and structure: how many certified beds, how much operating room square footage, which system owns whom, which technologies sit installed at vendor and product level, and how much inpatient Medicare volume flows through each DRG. The executive layer answers the human question: who runs the place, at what level, reachable where.
Multiply the pair across 9,000-plus hospitals, 100K-plus post-acute organizations and the adjacent universes, and the same file works as a prospecting panel, a referral-network map or a market-sizing denominator - the grouping key decides.
What fields does the dataset include?
Nine attribute groups define the core profile. Definitions below are reconstructed from the platform's own feature documentation rather than transcribed from a published schema document - the vendor ships no public data dictionary - so treat them as verified structure carrying inferred labels until a sample confirms cell-level typing.
Everything deeper folds under additional fields on request rather than being promised blind: the financial, staffing and physician detail on each profile, the Medicare revenue-center, readmission and origination/destination splits beneath the DRG breakouts, purchasing and news activity, population context, study activity, and the six adjacent universes from post-acute to physician groups. Name the attributes you benchmark against when you request the sample and the extract arrives carrying exactly those columns.
What geography, time span, and granularity does it cover?
Geography - United States throughout, across every tracked universe: hospitals and IDNs, post-acute organizations, imaging centers, ambulatory surgery centers, clinics and FQHCs, physician groupes and ACO/HIE/payer profiles. Claims products extend the footprint into prescription detail.
Temporal - maintained current-state profiles rather than an archived time series. Each record describes the facility as the platform holds it at delivery, with no deep backfile of earlier profile states. Universe counts quoted anywhere should carry an observation date; the figures on this page were read at the August 2026 review.
Granularity - one profile per facility or organization at the top, with network, member and episode-level elements beneath for episodic care. The analysis unit is therefore configurable: roll profiles up through parent/child affiliations to read a whole IDN or system, or drill to episode elements for care-utilization questions.
How is the data delivered?
API, files, or your warehouse. Daily, weekly, or hourly.
You pick the channel and set the cadence, and change either without re-integrating. Every delivery ships typed rows keyed so profiles join cleanly to their executive records, the full field dictionary attached, and sample rows for validation before anything recurring starts. Name the universes, the geography and the profile attributes you need when you request the sample, and the first cut arrives already filtered to them.
Who uses this data, and for what?
- Provider prospecting and lead enrichment - sales teams build account lists across hospitals, IDNs, post-acute organizations and surgery centers with named executives attached, then carve territories on system affiliation rather than raw address. See lead enrichment use cases and the sales growth teams use cases page.
- Market sizing for market-entry work - researchers size the post-acute, imaging-center and ASC landscape from documented universes (100K+ post-acute orgs, 22K+ imaging centers, 14K+ ASCs) instead of estimating them. Worked examples live on our market sizing use case page.
- Referral network mapping - discharge flows become mappable once the post-acute universe is keyed: 100K-plus organizations and 14K-plus surgery centers give the destination layer behind every discharging hospital.
- Private-market diligence on provider rollups - investors map an operator's facilities, affiliations and executive bench before pricing a deal; see investors and quants use cases.
- Competitive install tracking - watch which systems rivals partner with by following technology installations and affiliation changes across their footprints; see competitor tracking use cases.
- Provider master-data enrichment - claims-enriched profiles serve as a reference layer for entity resolution and internal CRM hygiene; see data scientists use cases.
Which personas get the most value?
Sales and growth teams and market researchers and consultants rate it maximum relevance - three out of three, the top of this industry's eight tagged personas. One group monetizes the executive records and affiliation maps directly; the other leans on the documented universe counts as defensible denominators.
Investors and quant researchers and competitive intelligence and product teams rate it two: diligence mapping on provider rollups, and tracking rival facilities' technology installs and partnerships - see competitive intel product teams use cases.
Data scientists and ML engineers and journalists, academics and students rate it one - a reference layer for provider master data, and background context rather than a citable primary figure. Developers and data-product builders carry no strong tag on this slice: the payoff lands after delivery, when typed profile rows power CRM enrichment and internal tools - see developers builders use cases.
What should I know before requesting a sample?
Four things, stated upfront.
First, the dictionary is reconstructed, not published. The vendor releases no public data dictionary, so the nine core definitions come from its own feature documentation and stay labeled inferred until a sample confirms cell-level typing.
Second, universe counts move. The hospital figure reads 9,000+ on some pages and 9,300+ on others; every count on this page was read at the August 2026 review, and your sample states its own totals.
Third, this is a current-state view, not an archive. Profiles describe facilities as held at delivery, so longitudinal designs need successive captures - precisely what a scheduled cadence builds from day one.
Fourth, Datadory scores it 5/10 against a 7.81 catalog average: docked for undocumented fields and absent public sample rows, credited for breadth nothing else in this industry matches - eight universes, DRG-level claims and named executives under one keyed roof.
Field dictionary - the nine core attribute groups on every facility profile (full dictionary with examples ships with your sample)
| Field | Type | Definition | Example |
|---|---|---|---|
| facility_profile_id | string | Identifier for each hospital, IDN or facility profile within the platform; the join key tying profile, claims and executive layers together. | <returned in your sample> |
| affiliations_and_partnerships | text | System components and parent/child relationships describing organizational structure - which IDN or system a facility belongs to. | <membership chain for the profile> |
| medicare_certified_bed_count | integer | Medicare-certified bed count carried as account-level detail for sizing and segmentation. | <certified beds for the facility> |
| operating_room_square_footage | number | Facility operating room square footage, used for surgical-service sizing and prospect qualification. | <square footage on the profile> |
| technology_installations | text | Installed technology tracked at category, vendor and product level - the EHR, imaging and IT stack in place. | <category > vendor > product entries> |
| drg_claims_volume | integer | Inpatient Medicare claims volumes broken out by DRG, diagnoses and procedures. | <claims count per DRG> |
| quality_metrics | text | Quality performance measures shown on hospital profiles and market-level views. | <measures attached to the profile> |
| executive_contacts | text | Executive name, department, title, email, position level, phone number and LinkedIn profile. | <named contacts per profile> |
| predicted_buyer_score | number | Score predicting likelihood of technology investment, used to rank likely buyers. | <score per account> |
Coverage chips
| Dimension | Coverage |
|---|---|
| Geography | United States across every tracked universe - hospitals/IDNs, post-acute, imaging centers, ASCs, clinics/FQHCs, physician groups, ACO/HIE/payer profiles; claims products add prescription detail |
| Temporal | Maintained current-state profiles rather than an archived time series; universe counts observed at the August 2026 review |
| Granularity | One profile per facility or organization, with network/member/episode-level elements beneath for episodic care |
| Record families | Facility profiles plus nested executive records; six adjacent universes delivered under the same keyed structure |
Additional fields available on request
| Field group | Notes |
|---|---|
| Financial performance, staffing and physicians | Profile-level economics and workforce detail, plus physician rosters attached to each facility. |
| Claims extensions | Medicare revenue centers, cost and readmission measures, and claim origination/destination pairs beneath the DRG breakouts; all-payor and prescription claims products extend the layer further. |
| Purchasing, news and population context | Purchasing information, news activity, population data and study activity tied to the profile. |
| Adjacent universes | Long-term care, imaging center, surgery center, clinic/FQHC, physician group and ACO/HIE/payer files delivered under the same keyed structure. |
What teams do with it
- Provider prospecting and lead enrichment Account lists across hospitals, IDNs, post-acute organizations and surgery centers with named executives attached, carved into territories on system affiliation.
- Market sizing for market-entry work Documented universes - 100K+ post-acute orgs, 22K+ imaging centers, 14K+ ASCs - as defensible denominators for entry decks and TAM models.
- Referral network mapping The keyed post-acute and ASC universes supply the destination layer behind every discharging hospital.
- Private-market diligence on provider rollups Map an operator's facilities, affiliations and executive bench before pricing a deal.
- Competitive install tracking Follow technology installations and affiliation changes across rival footprints to see which systems competitors partner with.
- Provider master-data enrichment Claims-enriched profiles as a reference layer for entity resolution and CRM hygiene.
Questions buyers ask
What fields does the Definitive Healthcare hospital and IDN dataset include?
Nine core attribute groups: a facility profile identifier, affiliations and partnerships with parent/child system structure, Medicare-certified bed counts, operating room square footage, technology installations by category, vendor and product, DRG-level Medicare claims volumes, quality metrics, executive contact records, and a predicted buyer score. Financial performance, staffing, referrals, episodes of care and study activity arrive under additional fields on request.
How many hospitals and post-acute facilities does the dataset cover?
More than 9,000 hospital and health system profiles, 100,000-plus post-acute organizations, 22,000-plus imaging centers, 14,000-plus ambulatory surgery centers, 60,000-plus clinics and FQHCs, 130,000-plus physician groups and 4,500-plus ACO, HIE and payer profiles, with billions of claims underneath. Counts were read at the August 2026 review; the hospital figure itself appears as both 9,000+ and 9,300+ on different pages.
Which facility types are profiled besides short-term acute care hospitals?
Long-term acute care, critical access, VA, pediatric, Department of Defense, psychiatric, rehabilitation and religious non-medical institutions all carry profiles, alongside the post-acute universe of nursing, assisted living, home health and hospice organizations. Each profile carries bed counts, operating room square footage, affiliations and claims volume regardless of type.
Do records include individual executives and their contact details?
Yes. Executive records carry name, department, title, email address, position level, phone number and LinkedIn profile, plus a score predicting likelihood of technology investment. That combination turns a facility profile into a workable account: the org chart and the outreach route ship on the same record.
How current is the facility data?
Profiles are maintained current-state views rather than an archived time series: each record describes the facility as held at delivery, with no deep backfile of earlier profile states. Any universe count you quote should carry an observation date - the figures on this page were read at the August 2026 review, and your sample states its own.
Who uses hospital, IDN and post-acute facility data?
Sales and growth teams and market researchers rate it maximum relevance: prospecting hospitals and post-acute networks with named executives, and sizing the post-acute, imaging and ASC landscape for market-entry work. Investors map referral networks during rollup diligence, competitive teams track rivals' technology installs, and analysts use it as a claims-enriched reference layer.
Datasets that pair with this one
- NPPES NPI Registry - National Provider & Facility Identifier Search The public identity spine: resolve every facility to its NPI and join these profiles to federal provider records.
- American Hospital Directory - Advanced Search hospital profiles Medicare claims and cost-report profiles rebuilt quarterly for 7,000-plus hospitals - the independent cross-check layer.
- American Hospital Association Organizational Hub & Data Insights System membership and organizational data that pairs with the affiliation fields for whole-market hospital structure.
- HealthData.gov - COVID-19 Hospital Capacity by Facility (Historical Time Series) Facility-week utilization history for roughly 6,000 hospitals - the time-series counterweight to a current-state profile view.
- HRSA Health Center Program Uniform Data System (UDS) Data 2025 The standardized annual filing for the community-health-center side of the continuum, complementing hospital and post-acute coverage.
- how sales growth teams use health care facilities data The worked workflow: turning affiliation maps and executive records into territories that convert.
- best health care facilities datasets Where this universe ranks among the thirteen primary facilities datasets we catalog.
See the rows before you pay anything.
Name this dataset and we send real records from it — scoped to the fields you asked for.