For rural health & RHTP
New capability for new geography.
All 50 states received Rural Health Transformation Program awards — $50 billion over five years, averaging $200M per state. Year-1 funds must be obligated by September 30, 2026. The hard part isn't the money. It's the targeting.
$50B
RHTP program total
Sept 30, 2026
Year-1 obligation deadline
50–100
allocation questions per state
~6 wks
per question, custom GIS — or ~10 seconds
Three realities, one missing layer.
Reality 1 — distance
Demand hides in the miles
- A single rural service area can span whole counties.
- Need concentrates in places no windshield survey can find — and clinical systems don't look.
Reality 2 — the mandate
Program dollars must build, not backfill
- RHTP and TEAM funds carry anti-supplanting rules: they must add capability that didn't exist before.
- The documentation matters as much as the delivery.
Reality 3 — the gap
Nothing in the stack sees the field
- EHRs end at the clinic door.
- The geography your teams drive every day has no data layer — until you add one.
New capability, documented as new capability.
The engine answers where rural demand is concentrating — precision maps from 200+ federal health variables — plans next week's staffing and today's coverage across real distances, and produces the evidence trail program reporting requires: versioned weights, data vintages, and an audit log of every human and machine decision. An addition to your stack, not a replacement for anything in it.
“The records see the clinic. The map sees the field. Same tool, opposite result — the only thing that changed is who was holding the map.”
Read “Who Holds the Map” — on rural hospitals, home care, and 180 closures since 2010 →
For the program office.
For state RHTP leads
Allocation logic that survives audit
- “Show me tracts where diabetes prevalence >80th percentile AND 65+ >75th percentile AND no hospital within 15 miles” — one question, ~10 seconds, with the receipt attached.
- Every allocation memo reproducible: dataset vintages, engine version, weight-set hash.SYNTHETIC EXAMPLE
For your auditors
Anti-supplanting, provable
- Documentation of new capability, generated as a byproduct of using it — not assembled after the fact.
- Actor-level audit trail: what the engine proposed, what a human approved, when, and on what evidence.
For procurement
Buying us is boring (by design)
- Security questionnaire answers, BAA details, and architecture docs in writing — no sales layer. Procurement pack →