Skip to content
FonteumThe Graph

By use case

Exclusion & monitoring (self-serve)Free roster screen — no accountExclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligence

By buyer

Compliance & riskJournalists & newsroomsDevelopers & AI teams

By industry

HealthcareProviders & facilitiesSanctionsOFAC / EU / UK / UN / OIG / SAMFederal contractingSAM · USASpending · FAPIIS

The capability layer

APIREST + bulk accessFor AI agentsModel Context Protocol serverFHIR R4 APIBulk exportAudit packSigned report artifacts; source facts remain separately citedReconciliationSource-vs-source diffsAI answers with sourcesHow records link upHistoryRetained versions for named sources

The differentiator

Coverage & sourcesThe catalogFreshnessMethodologyCare CompareFacility qualityAI answers, comparedBrowse all datasets →
Research

The dev on-ramp

DocsAPI referenceConnect your AI agent (MCP)One-paste installFHIR sandboxLive API surfaceQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inFree roster screen →Get a signed certificate →

Solutions

Exclusion & monitoring (self-serve)Exclusion & sanctions screeningCredentialing & provider-data enrichmentAudit evidence & defensible programsProvider data for AI / RAGM&A & network diligenceCompliance & riskJournalists & newsroomsDevelopers & AI teamsHealthcareSanctionsFederal contracting

Platform

APIFor AI agentsFHIR R4 APIBulk exportAudit packReconciliationAI answers with sourcesHow records link upHistory

Data

Coverage & sourcesFreshnessMethodologyCare CompareAI answers, comparedBrowse all datasets →
Research

Developers

DocsAPI referenceConnect your AI agent (MCP)FHIR sandboxQuickstartStatusChangelogSDKs & integrations
Pricing
Sign inFree roster screen →Get a signed certificate →
Fonteum Care Compare · Kansas

Kansas hospices: 85 Medicare-certified, source-cited identity + ownership data.

Ownership type, certification date, and CMS region for every Medicare-certified hospice in Kansas. CAHPS Hospice experience-of-care measures live in a separate CMS dataset and are not included in this snapshot.

Cross-check at Medicare.gov →All states →
Snapshot May 7, 2026·85 Medicare-certified hospices in Kansas · 56.5% for-profit·CMS Care Compare — Hospice·Module overview →·Methodology →·Audit Pack →
Source-modified 2026-01-08 · CAHPS Hospice experience-of-care measures are a separate CMS dataset, not included in this snapshot

Editorial note: Kansas is a state where source-cited public-data coverage of hospice ownership is materially thinner than national averages — Fonteum prioritizes full provenance + state context here.

Ownership breakdown — Kansas

Hospice ownership concentration is the documented quality-of-care variable in policy literature; Fonteum surfaces the breakdown explicitly.

For-Profit
48
Other
15
Non-Profit
9
Unknown
6

Hospice quality measures — what this page can and cannot show

Unlike nursing homes or home health, the CMS Hospice General Information file that backs this page does notcarry star ratings or quality scores. Hospice quality is reported in the separate CAHPS Hospice Survey dataset, and CMS suppressed publicly reported hospice quality measures during the documented May 2026 → February 2028 transition to the new HOPE assessment.

Rather than fabricate a rating, Fonteum renders the fields that genuinely exist for every Kansas hospice: CMS-certified identity, ownership type, CMS region, and Medicare certification date. When the HOPE-based measures publish, they will land here traced to their source.

Hospices in Kansas

First 25 of 85 Medicare-certified hospices. The table is an unlinked state inventory.

FacilityCityOwnershipCertified
Harry hynes memorial hospiceWICHITAOther06/18/1986
Hospice and homecare of reno countyHUTCHINSONOther03/08/1989
Hospice the university of kansas health systemOLATHECombination Government & Non-Profit10/26/1989
Midland care hospiceTOPEKANon-Profit06/10/1991
Hospice of the prairieDODGE CITYOther10/29/1991
Saint luke’s hospice of leavenworth, llcLEAVENWORTHFor-Profit01/14/1992
Visiting nurses hospiceLAWRENCENon-Profit05/01/1992
Golden belt hospiceGREAT BENDNon-Profit06/03/1992
Hospice services incPHILLIPSBURGNon-Profit09/09/1992
Amberwell hospiceATCHISONFor-Profit09/11/1992
Good shepherd homecare & hospice incMANHATTANFor-Profit12/10/1992
Hand in hand hospiceEMPORIAGovernment01/08/1993
Hospice of jefferson countyOSKALOOSAGovernment04/23/1993
Meadowlark hospiceCLAY CENTERCombination Government & Non-Profit11/01/1993
Hospice of dickinson countyABILENEOther03/09/1994
Horizon hospiceCHANUTEGovernment05/03/1994
Heartland hospice (wichita)WICHITAOther05/09/1995
Hospice of ne ks multi-countyHORTONCombination Government & Non-Profit08/03/1995
St catherine hospiceGARDEN CITYFor-Profit12/20/1995
Hospice & palliative care at haysmedHAYSNon-Profit12/14/1995
Elara caringTOPEKAFor-Profit04/04/1997
Solomon valley hospiceBELOITGovernment05/05/1998
Catholic comm hospiceOVERLAND PARKNon-Profit04/24/1998
GentivaWICHITAOther05/04/1999
Holton community hosp home health & hospice agencyHOLTONNon-Profit11/28/2000

Kansas hospices — FAQ

How many Medicare-certified hospices are in Kansas?
85 Medicare-certified hospices operate in Kansas as of the CMS Hospice General Information snapshot (2026-05-07). 56.5% are for-profit — ownership concentration is the documented quality-of-care variable in the hospice policy literature.
Does Fonteum show hospice star ratings for Kansas?
No — and that is an honest data gap, not an omission. The CMS Hospice General Information file that backs this page carries identity, ownership, and certification only. Hospice quality lives in the separate CAHPS Hospice Survey dataset, and CMS suppressed publicly reported hospice quality measures during the May 2026 → February 2028 transition to the new HOPE assessment. Fonteum renders the fields that exist rather than fabricating a rating.
What can I learn from this hospice data today?
For every Kansas hospice you get its CMS-certified identity, ownership type, CMS region, and Medicare certification date — enough to map the ownership landscape and track when each provider entered the program. Each row reports those fields directly in the state inventory.
Where does this hospice data come from and how current is it?
The displayed fields come from the CMS Hospice General Information file, source-modified 2026-01-08. Fields can be absent; cross-check a consequential hospice record at Medicare.gov.

Compare other facility types

Supported Care Compare facility responses for Kansas and other states expose source-and-date fields where the module supplies them; individual fields may be absent or null.

Nursing homesHome healthDialysisAmbulatory surgical centersHospitalsAll modules

Compliance posture

Methodology · Corrections log · Editorial policy

What’s on file, by the numbers

Platform snapshot · 2026-07-15

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
—sources liveCrosswalk-resolved sources with a proved content transition in the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Built on the authoritative federal record

The primary sources, named on every page.

These are the federal agencies whose public datasets Fonteum ingests and attributes — the issuing authorities, not customers or partners. Every figure on the site links back to one of them.

  • CMS
  • HHS-OIG
  • HRSA
  • FDA
  • NLM
  • NUCC
  • Census
  • BLS
  • BEA

See the full source registry, with license and refresh cadence for each →

Reproducible by design

Published figures name their source and date.

Source and date

Published research identifies its government file and observation date. Source-file SHA-256 coverage is disclosed separately; facts do not currently link deterministically to signatures.

Reproducible SQL

Each study ships the exact query behind its figures, run against the same dated copy of the federal file we used. Re-run it yourself.

Daily observations

The platform records table row counts daily. Those observations detect local drift; they do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Fonteum
Platform
Platform overviewAPIFor AI agents (MCP)FHIR R4 APIBulk exportAudit packReconciliationAI answers with sourcesHow records link upHistory
Solutions
All solutionsExclusion & sanctions screeningCredentialing & enrichmentAudit evidenceProvider data for AI / RAGUse casesM&A & network diligenceCompliance & riskJournalists & newsroomsDevelopers & AI teams
Data & sources
Coverage & sourcesBrowse all datasetsState Medicaid exclusionsFreshnessMethodologyCare CompareNursing homesRecall recordsSanctions screeningOIG LEIE listOwnershipStaffingDeficienciesSpecial Focus Facilities
Federal contracting
OverviewAwards during active exclusionFederal debarment scorecardProcurement questionsContractor lookup8(a) certification guide
Developers
Developer hubDocsAPI referenceQuickstartStatusChangelogSDKs & integrationsWebhooks
Research & guides
Research hubLearnHow it worksGuidesHealthcare provider dataExclusion & sanctions screeningProvider credentialing dataHealthcare data for AIHospital margin gapProvider access gapsGlossaryComparisonsSourced data vs plain LLM answersCitationsManifestoWhy Fonteum
Company
AboutPressCustomersPricingContactEditorial policyCorrections
Trust & legal
TrustTrust markQualitySecurityPrivacy policyTerms of serviceAPI termsMedical disclaimer

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

© 2026 Fonteum LLC. All rights reserved.

·hello@fonteum.com

A public-records graph that exposes source and observation metadata where supplied.

Fonteum's provenance ledger contained 26.2M source-linked facts on July 12, 2026. All but 14 carried a source-file SHA-256; 0 linked deterministically to a signature. Inspect a supplied snapshot id at fonteum.com/verify · source-mark coverage and limitations.
Request access→