Every ambulance trip has two clocks. The event clock records what happened. The evidence clock records when the control room last knew it was true.
A useful system keeps both. A convincing map can hide the second one.
Takeaways
- Record event time and evidence freshness separately.
- Make stale location, delayed acknowledgement, and manual updates visible.
- Keep clinical priority and dispatch rules with authorised service owners.
- Reconcile both clocks at handover and after downtime.
This is a software-evaluation worksheet, not emergency medical, dispatch, fleet, legal, or clinical advice. Qualified service owners set protocols and conduct safe drills.
Build the event clock
Design a synthetic dispatch chain with explicit events:
REQUEST RECEIVED
-> location and callback checked
-> authorised priority recorded
-> suitable resource selected
-> dispatch sent
-> crew acknowledged
-> vehicle moving / arrived
-> destination set or changed
-> handover acknowledged
-> vehicle clearing
-> available, held, or out of service
Each state needs an event time, source, actor or device, and correction path. “Vehicle assigned” should not imply that the crew saw the request.
Delhi’s official Centralised Accident and Trauma Services specification describes computer-aided dispatch, vehicle-location, remote-viewer, and management components for that procurement. It offers useful evidence about one public-service design. It is not a national feature mandate or a promise about another system.
Add the evidence clock
For every displayed fact, ask for a last-confirmed time and source:
| Displayed fact | Evidence clock question |
|---|---|
| caller location | when and how was it confirmed? |
| vehicle availability | which owner or system last set it? |
| dispatch received | did the crew acknowledge, or was a message only sent? |
| vehicle position | how old is the location point and which device supplied it? |
| destination ready | which receiving role acknowledged the current destination? |
| vehicle clear | which readiness checks are still current? |
Do not turn missing evidence into a current state. Display uncertainty under the service’s approved design.
Make the clocks disagree
Use invented data and try these events:
- two callers report the same incident with different landmarks;
- the closest vehicle is marked available but lacks the required service capability;
- the selected crew does not acknowledge;
- a vehicle location is ten minutes old;
- the destination changes after departure;
- one vehicle goes out of service mid-assignment;
- the caller’s phone disconnects before the address is confirmed.
For each case, compare the event time with the time the control room learned about it. Ask what the dispatcher sees, which alert is audible or visible, who may reassign, and what history remains. Do not accept a hidden automatic state change for a safety-relevant event.
Read the age beside the location
Maps look exact even when the source is old or uncertain. The screen should show the last update time, source, confidence or status under local design, and loss-of-signal handling. Ask how the system distinguishes vehicle GPS, crew-device location, manually entered landmarks, and a caller’s description.
Limit collected data to the approved purpose and audience. India’s Digital Personal Data Protection Act, 2023 has phased commencement and needs date-specific legal review. Qualified owners should map active provisions and other duties to actual roles, notices, security, retention, vendors, and rights handling.
Put readiness on its own clock
A vehicle should not become selectable only because it returned to base. Test maintenance state, required equipment checks, crew assignment, fuel or charge state where applicable, and unresolved defects. The software may record those facts; responsible fleet and service owners decide availability.
Use one synthetic defect to place a vehicle out of service, prevent assignment, authorize repair evidence, and return it to availability. Try to bypass the hold. Record the actor and reason for any override.
The 2025 Indian Bank Hospital Management Solution RFP lists ambulance among many modules for that procurement. A module name alone does not establish dispatch depth.
Reconcile both clocks at handover
Send an invented trip to a synthetic hospital destination. Record only approved operational details. Change the destination once. Require the receiving team to acknowledge the updated handover and ensure the earlier destination no longer appears current. Compare departure, arrival, handover, and acknowledgement times without forcing them into one timestamp.
Keep transport status, clinical documentation, and billing as separate authorities. A completed trip can create a billing event under policy, but a charge should not rewrite dispatch history.
Lose both networks
Run a tabletop in which the crew data connection fails, followed by the control-room application. Use an approved alternate route, record every manual event, then restore the system. Reconcile timestamps, assignments, status, destination, handover, and vehicle availability. Detect a duplicate incident created during recovery.
Score event-history integrity, freshness visibility, owner clarity, override evidence, and reconciliation. A moving icon is not the outcome.
Patient Square does not publish a live ambulance-dispatch product. Do not infer GPS tracking, crew messaging, computer-aided dispatch, emergency records, fleet telemetry, or destination alerts from Hospital Copilot. If those functions matter, place the exact field workflow, devices, network assumptions, interfaces, service levels, and acceptance drills in the procurement record.