State RHT offices
Rural residents need care as close to home as possible. Your grantees run home health visits and patient transport to make that happen. DispatchCare routes each referral to the right program and tracks it to done. Your office then gets the same fields from every county.
Statewide roll-up · this quarter
Coordination infrastructure moves each RHT referral to a service that can take it. Your state office can then compare grantees without rework.
State RHT office
Grantees and subrecipients
Referrals into DispatchCare
EHR, web app, or mobile app
Services
Completion status back to the grantee
Reporting up to the state
Closes the loop, back to 01
The RHT statute asks each state plan to improve access for rural residents. It also asks for care "as close to a patient's home as is possible." Coordination is how a referral turns into that visit.
Today, many subrecipients track referrals in their own spreadsheets. Each sheet uses different fields. A referring clinic often cannot tell if the patient got the service. The state program office cannot add the sheets up.
A shared layer fixes the data at the source. The grantee does its normal work in DispatchCare. The report comes from that work. Staff do not re-key the same visit into a second system, so the administrative load on small rural teams stays low.
DispatchCare
Coordination layer
Care and transport
Services at home
Illustrative example. Not real patient data.
Patient: R.M., discharged 10/2.
Illustrative example. Not real patient data.
Patient: R.M., discharged 10/2.
Flagged to care coordinator · 10/7, 9:40 a.m.
DispatchCare sends a request to a program by territory and skill. The program accepts it. You can see this flow on the broadcast page and the provider network page.
State plans often name transportation as a barrier to rural care.
One referral path across community paramedicine and MIH visits, non-emergency transport and home health means fewer handoffs on paper.
DispatchCare is not 911 CAD. It does not replace the ePCR. The ePCR stays the clinical record of the visit.
Compare grantees on events, not on narrative reports. Each row below comes from a timestamp the grantee already records in daily work.
Illustrative
Same field set
State view
One state view from the same fields
Illustrative. Measures and sources are examples for planning. They are not results from any program.
Referral to first visit (median hours)
Where the data comes from
Referral received time and visit start time
Same field in every county?
Yes, if every grantee uses the shared layer
Missions completed
Where the data comes from
Mission status "complete"
Same field in every county?
Yes
Referrals declined or not placed
Where the data comes from
Mission status and decline reason
Same field in every county?
Yes
Transport requests filled
Where the data comes from
Ride request and assignment status
Same field in every county?
Yes
Residents and towns served
Where the data comes from
Patient and address fields on completed missions
Same field in every county?
Yes
ED return within 30 days
Where the data comes from
Hospital or payer data, matched after the visit
Same field in every county?
No. It depends on a data-sharing agreement with each source.
Program reports also ask for qualitative notes and for barriers to implementation. Those stay with the grantee. The shared data shows where to ask.
See the reporting requirements page for what subrecipients must keep. See CP metrics that satisfy state reporting for more measure ideas.
Your office sets the shared measures and status values before any grantee starts. Match them to the milestones in each subaward.
Start with a small group. They test the referral flow with real work.
Requests can start in the EHR, or in the DispatchCare web or mobile app. A grantee does not need an EHR connection to begin. Referrals can come from the hospital chart.
Grantees find missing fields while the fix is still small.
Your office pulls one statewide view from the same fields. Use it in your report to CMS.
Rollout: shared fields first, then a small group, EHR connections, a weekly report, and a quarterly state view.
See integrations for the current list. Epic is listed on the Epic Showroom. Oracle Health, MEDITECH, athenahealth, CPSI / TruBridge, eClinicalWorks, NextGen and Veradigm are available via SoFaaS.
Your grants office still decides how each grantee buys software. Procurement rules in 2 CFR Part 200 apply.
Reporting tells you what happened last quarter. The intelligence layer reads the same shared data during the quarter. It flags referrals that wait too long. It shows counties where requests go unfilled. It does not make clinical decisions. Clinicians and program leads decide what to do.
No. VectorCare is a vendor or subcontractor to subrecipients. We do not administer RHT funds. We do not decide what is allowable. Your state plan, CMS rules and your grants office decide that. Some states also use their own managing vendors to run onboarding and funding. We work alongside that structure. For budget lines, read the budget kit. For the supplanting question, read the non-supplantation guide.
Community care coordination touches all five. Below is how program leads typically describe the mapping in a plan narrative.
| Goal | Title | How coordination infrastructure contributes |
|---|---|---|
| RHT Goal 1 | Make rural America healthy again | Prevention and chronic disease follow-up delivered in the home, with measured reach into the cohort. |
| RHT Goal 2 | Sustainable access | Lets rural providers share and coordinate operations, so EMS and home-based capacity can take scheduled care. |
| RHT Goal 3 | Workforce | Extends the existing paramedic workforce into new roles without new licensure categories. |
| RHT Goal 4 | Innovative care | Treat-in-place, hospital-at-home bridging and remote-supported visits with a shared record. |
| RHT Goal 5 | Tech innovation | Shared referral and status data across grantees, with one record per mission. |
Grantees run their own programs. Your office gets a dataset it can compare.
A new subrecipient joins a working layer. It does not build its own tracker.
Row-level exports carry timestamps.
Security and HIPAA detail: security page. Reporting views: reporting.
Quarterly Report #1 is due Mon Nov 30, 2026. Each grantee captures the same mission fields, so your office can count missions across grantees. See how states prepare Quarterly Report #1.
It depends on your state's approved RHT plan; the full answer and where to check are in the RHT budget kit at dispatchcare.com/rural-health-transformation/budget-kit.
Non-supplantation asks whether the cost would have been paid anyway. For many states, scheduled preventive community paramedicine visits are not an existing billable service, so coordination and evaluation for a new or newly expanded program are new costs attached to new activity. Say that plainly, and keep emergency response and existing billing on existing funding. DispatchCare is positioned as new program infrastructure plus evaluation — not a replacement for ePCR, CAD, or an existing billable service.
Retention is configurable per customer contract. The federal rule for RHT records is 2 CFR 200.334: recipients and subrecipients keep federal award records for three years from the date they submit the final financial report, and longer if litigation, a claim or an audit starts before the three years end.
A 15-minute walkthrough with a coordinator view, a CP program view and the dashboard your sponsor will read.
