Outcomes and reporting
Reporting as a by-product of the work.
A mission cannot close without the fields your sponsor will ask for. That turns the quarterly report from an archaeology project into an export.
Sponsor scorecard
- Referrals acceptedn/a
- Median referral to contactn/a
- Visits completedn/a
- Escalationsn/a
- Cohort ED revisitsn/a
What gets measured on every mission?
Reach
Referrals sent, accepted, declined and reason. Time from referral to first contact.
Delivery
Visits completed, exceptions by type, escalations to medical control, treat-in-place rate.
Follow-through
Medication reconciliation completed, teach-back done, follow-up appointment confirmed.
Utilization
ED revisits and readmissions in the enrolled cohort, joined to your own ADT data.
Equity
Rural/urban commuting area, distance travelled, language and interpretation used.
Cost
Avoided transports and avoided ED visits at your own local cost assumptions.
How a number gets from the field to a report
- 01
Field is required
Mission templates define which outcome fields a visit type must have before it can close.
- 02
Crew records it
The field is entered from the visit itself, on a phone or tablet, not reconstructed later from memory.
- 03
Mission closes
Closure timestamps the record and locks it into the mission's history.
- 04
Rolls into program view
Every closed mission adds a row to the program-level scorecard automatically.
- 05
Filtered by sponsor
A hospital, payer or state office sees only the cohort tied to their own referrals.
- 06
Exported
CSV plus a narrative summary, on whatever cadence the sponsor needs.
How the data holds up when someone asks a hard question
A sponsor scorecard is only useful if someone can defend it in a meeting. Every number in a DispatchCare export traces back to a specific mission, a specific timestamp and a specific field, not a spreadsheet formula someone built once and forgot. If a state auditor asks why the referral-to-contact time jumped in March, the answer is a filtered list of missions, not a guess.
That traceability matters most when the numbers are inconvenient. A rise in escalations, a dip in visits completed, a cluster of declined referrals in one county: these show up in the export the same way the good numbers do, because the mission record does not know in advance which quarter it will be summarized in.
What happens when a mission is missing a field
Mapping to Rural Health Transformation reporting
State RHT plans typically ask subrecipients for reach, utilization and outcome measures tied to a funded intervention, on a recurring cadence set by the state's award terms. Because DispatchCare's mission and outcome fields are structured the same way across every program in the network, a state office can roll individual program exports into its own RHT template without sending a separate data-collection request to each grantee every quarter.
This does not replace your state's reporting template or CMS's rules; it removes the step where a program coordinator has to reconstruct the numbers from a paper log or a personal spreadsheet before they can fill that template in.
Who audits the numbers, and what do they need?
Exports are row-level and timestamped, so a reviewer can trace a number back to a mission.
0%
Missions with outcome fields
Closure requires them.
0 export
Quarterly submission
CSV plus a narrative summary.
0
Separate data entry systems
Field crews work in one place.
Retention is configurable per customer contract.
Your data, your cohort definition
Getting started with reporting
If you already run a CP or MIH program, the fastest way to see this is to walk through your current sponsor report and compare it line by line to what closes automatically from a mission. Most programs find the structural fields, dates, referral source, protocol, escalation reason, already map cleanly, and the gap is usually the outcome and follow-through fields that today live in a coordinator's notebook.
If you are a hospital, payer or state office standing up reporting requirements for a new program, it is worth defining the required outcome fields before missions start flowing, since a field that is optional from day one is much harder to make mandatory later without leaving a reporting gap in your first quarter.
The reporting layer is shared with VectorCare Insights, the same analytics health systems already run against their patient logistics data.
Who sees which numbers
A single program can serve several sponsors at once, a hospital, a payer and a state office, without those sponsors seeing each other's data. Access to a scorecard is scoped to the referrals and cohort a sponsor actually sent in: a hospital sees its own discharge cohort, a payer sees its own member panel, and a state office sees the subrecipient-level roll-up its subaward calls for. Custom fields a sponsor adds to its own mission template, a state-specific data element, for example, do not leak into another sponsor's export.
This matters most when a program is trying to satisfy several reporting relationships at once: the same underlying mission produces different, correctly scoped views for each funder, instead of one spreadsheet a coordinator manually splits apart before every submission deadline.
Questions buyers ask
The hospital's own ADT and registration data is joined to enrolled cohorts in the BI layer. No HIE feed is required for a single-hospital view.
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.
No. The ePCR remains the record of care. DispatchCare captures the mission status and the sponsor-required outcome fields only.
Most sponsors want a quarterly narrative plus CSV, but the underlying export can run on any cadence: weekly for an internal program review, monthly for a payer, quarterly for a state RHT office. The data is the same; only the cut date and audience change.
The mission cannot move to Complete until the required outcome fields for that mission type are entered. If a field genuinely does not apply, it is marked not applicable with a reason, so it shows up as an explained gap in the export rather than a blank cell.
RHT award reporting asks for program-level reach, utilization and outcome measures tied to a funded intervention. DispatchCare's mission and outcome fields are structured so a state office can roll them up into its own RHT template without a separate data call to every subrecipient.
Yes, with an audit trail. Corrections are logged as a new row referencing the original mission ID and timestamp, so a reviewer can see what changed, when, and by whom, rather than a silently overwritten number.
Yes. Mission templates can include sponsor-specific fields alongside the standard reach, delivery, follow-through and utilization measures, so a state or payer requirement that isn't already covered can be added without a separate system.
Access is scoped to the sponsor's own referrals and cohort. A hospital, payer or state office sees the missions tied to what it sent in, not another sponsor's data on the same network.
See a mission go from the chart to the home and back.
A 15-minute walkthrough with a coordinator view, a CP program view and the dashboard your sponsor will read.