A road accident victim's golden hour is now a statutory 60-minute window with a national reimbursement scheme attached. Here is what AIS-125 crew standards and PM RAHAT's cashless claims actually require from the system running your ambulance fleet and your emergency department together.
Most tier-2/3 hospitals in India sit alongside, not inside, the government emergency ambulance system. The 108 service — pioneered by EMRI in Andhra Pradesh in 2005 and now operating in more than 20 states and union territories — handles trauma, cardiac, and general medical emergencies through a public-private partnership model. The 102 service, run separately in many states under the Janani Shishu Suraksha Karyakram, is dedicated to maternal and child transport, known locally by names like Janani Express in Madhya Pradesh and Odisha or Mamta Vahan in Jharkhand. Both operate under National Health Mission guidelines and are, for the patient, free.
A private hospital's own ambulance fleet is a different animal entirely: it exists to bring patients specifically to that hospital, to move patients between facilities in a group, and increasingly to compete on response quality in cities well served by 108. None of the public network's dispatch software helps a private hospital manage its own fleet, crew certification, or handover documentation — that's a gap the hospital's own systems have to close, and it's routinely the most manually run part of an otherwise digitised hospital.
This gap is easy to underestimate precisely because the public network is genuinely good in most cities — a hospital administrator can point to 108's coverage and reasonably ask why the hospital needs its own dispatch software at all. The answer is that a hospital's own ambulance serves purposes 108 doesn't: scheduled inter-facility transfers for a multi-location group, non-emergency patient pickups for elective admissions, and the specific cases where a hospital wants direct control over which crew and which vehicle responds, rather than whichever unit the public dispatch system assigns. None of those use cases are edge cases for a hospital running its own fleet — they're the majority of what that fleet actually does day to day, with true emergency response being the minority case that gets the most attention.
There's a reputational dimension too, separate from the operational one. In competitive tier-2/3 markets, response time and handover quality are genuinely visible to patients and their families in a way most other hospital operations aren't — someone remembers exactly how quickly an ambulance arrived and how organised the crew was, in a way they don't remember billing turnaround or lab report timing. A hospital that can actually demonstrate its response-time performance, backed by real timestamp data rather than an anecdotal claim, is making a specific, differentiated case to the community it serves — and that case is only as credible as the data behind it.
The Automotive Industry Standard 125 was approved in June 2014 after an expert committee under the Ministry of Road Transport and Highways studied the state of Indian ambulances and found, bluntly, that most vehicles called ambulances were transport vehicles with a stretcher bolted in, not purpose-built emergency vehicles. The Ministry notified it as mandatory via G.S.R. 868(E) dated 8 September 2016, requiring compliance for Category L and M road ambulances manufactured on or after 1 April 2018. AIS-125 defines four ambulance categories and sets staffing expectations for each:
| Category | Purpose | Minimum staffing |
|---|---|---|
| First responder | Rapid arrival, no patient transport capability | Trained first responder |
| Patient transport | Non-emergency, stable patient movement | Driver, attendant |
| Basic Life Support (BLS) | Non-invasive care, basic monitoring | Trained Emergency Medical Technician (EMT) |
| Advanced Life Support (ALS) | Critical care, invasive intervention capability | Critical care nurse or doctor, plus EMT |
Part 1 of the standard covers vehicle design and construction — stretcher anchoring, electrical systems, occupant safety in the patient compartment (research cited in the standard's own drafting found ambulance occupants, particularly those unrestrained in the patient bay, were more likely to be injured in a collision than fire truck or police car occupants). Part 2 covers the medical equipment and devices each category must carry. As of 2026, the Ministry has draft amendments under consideration that would add a dedicated Neonatal Road Ambulance category, reflecting demand that the original 2014 categories didn't anticipate. The full AIS-125 Part 1 standard is published by the Automotive Research Association of India for anyone specifying or auditing a fleet against the actual constructional requirements rather than a summary.
For hospital software, the practical implication is straightforward: every ambulance in your fleet has a category, and that category determines both the minimum crew certification the dispatch system should be checking before assigning a vehicle to a call, and the equipment checklist that should be verified before the vehicle goes into service each shift. A hospital that owns both BLS and ALS vehicles but dispatches whichever is physically closest, without checking whether the case actually needs ALS-level crew, is running a fleet that technically exists but isn't functionally delivering the care level its own vehicle categories promise.
Section 2(12-A) of the Motor Vehicles Act, 1988 defines the "golden hour" as the critical one-hour period following a traumatic injury during which timely medical intervention significantly reduces the probability of death. The Law Commission of India's estimate, cited in support of cashless-treatment policy, put the potential reduction in road accident fatalities from timely golden-hour care as high as 50%.
Section 162 of the Motor Vehicles (Amendment) Act, 2019 legally obligates the creation of a nationwide cashless treatment framework for road accident victims, funded through a Motor Vehicle Accident Fund. That statutory mandate has moved through a phased rollout — a pilot launched in Chandigarh in March 2024, expansion to several more states and union territories through 2024, and a nationwide scheme announced under the name PM RAHAT (Road Accident Victim Hospitalisation and Assured Treatment). Under the current framework, eligible victims receive cashless treatment up to ₹1.5 lakh per person for up to seven days from the accident date, provided police are informed within 24 hours; hit-and-run cases carry a separate ₹2 lakh provision for the families of the deceased. All India Radio's official news service carries the government's own announcement of the scheme's launch and terms. The National Health Authority — the same agency that runs PMJAY — is the implementing agency, operating through a platform that integrates the Ministry's eDAR (e-Detailed Accident Report) system with NHA's Transaction Management System.
The rollout history is worth being precise about, since several summaries compress it into a single date when it was genuinely phased: a pilot began in Chandigarh in March 2024, expanded to several more states and union territories including Punjab, Haryana, Assam, and Puducherry through 2024, and only reached its current nationwide, PM RAHAT-branded form afterward. A hospital reading an older article about "the cashless treatment pilot" and a newer one about "PM RAHAT" is reading about the same statutory scheme at different points in its rollout, not two different programmes.
A separate Good Samaritan scheme offers a ₹5,000 reward to bystanders who get a victim to a hospital or trauma centre within the golden hour, which is itself a small but real driver of more road-accident patients arriving by whatever transport is fastest — not necessarily an ambulance — rather than waiting for one to arrive, which is itself a useful reminder that a hospital's own dispatch record needs to accommodate patients who never went through a formal dispatch at all. A detailed policy explainer covering eligibility and funding mechanics is available for anyone drafting an internal SOP around how the ED should triage and document these arrivals.
For a hospital, none of this is background policy. If your emergency department treats a road accident victim, whether they arrived by your own ambulance, the public 108 service, or a bystander's car, claiming reimbursement under this scheme depends on producing accurate, timely admission and treatment data in a format the eDAR/TMS platform recognises. A hospital whose ambulance dispatch and ED admission systems don't talk to each other — or worse, aren't digitised at all — is the hospital most likely to lose a legitimate claim to a documentation gap rather than a clinical one.
A hospital group running more than one facility, each with its own ambulance or two, faces a scaled-up version of the same dispatch problem: a facility whose own vehicle is out on a call needs to know instantly whether a sister facility's ambulance is closer and free, rather than defaulting to "we have none available" when the group as a whole does. This is the same local-speed-versus-group-visibility architecture we describe for bed management and OT scheduling in multi-location hospital ERP for chains and groups, applied to a fleet instead of a building. The stakes are comparable to the OT and ICU cases covered elsewhere on this site: a transfer or dispatch decision delayed by poor cross-site visibility is exactly the kind of delay the golden hour framework exists to prevent.
Road traffic accidents are one of the most common triggers for a Medico-Legal Case designation, and an ambulance-transported trauma patient often needs MLC documentation started at the point of hospital arrival, not after triage has finished. We've covered MLC register requirements and the documentation obligations that follow in our note on MLC register software for hospitals — the practical connection here is that an ambulance handover record and an MLC record are describing the same arrival event from two angles, and software that treats them as unrelated forces staff to re-enter the same facts twice under time pressure.
There's a documentation-order problem specific to ambulance-transported trauma worth naming directly: MLC intake traditionally happens after a patient is triaged and stabilised, but the ambulance crew already captured much of what an MLC record needs — scene description, time of injury, condition on pickup — before the patient ever reaches the emergency department. A system that discards the ambulance record once handover is complete forces the ED to reconstruct information that already existed thirty minutes earlier, from a crew that has since moved on to the next call. This same pattern applies to the ABHA linkage covered in our note on ABDM and ABHA integration: if the patient's ABHA ID can be captured or looked up during transport rather than only at ED registration, the entire admission record starts life already linked, instead of being linked as an afterthought once the immediate emergency has been managed.
Time the call was received, time a vehicle was assigned, time it departed — each a separate timestamp, not a single "dispatched" entry logged after the fact.
An ALS-classified vehicle requires a critical care nurse or doctor aboard per AIS-125; the dispatch system should be able to verify that pairing before confirming an assignment, not rely on the dispatcher's memory.
Whatever monitoring and care happens in transit needs to be logged against the same case timeline the hospital record continues — not written on a paper form that gets handed over and then filed separately from the patient's chart.
For a hospital marketing response-time performance, or simply trying to improve it, actual GPS-timestamped data beats a dispatcher's estimate every time.
The crew's en-route documentation should populate directly into the emergency department's admission record, not require a nurse to transcribe a paper handover sheet while also managing an incoming trauma patient.
OneCity's own Ambulance Dispatch module handles call logging, dispatch, and trip records as part of the same connected patient record every other module feeds into — so an ambulance-transported patient's pre-hospital data is already sitting in the chart by the time they reach a bed, not waiting to be typed in separately.
Where this matters most is the handoff moment itself. An ED nurse receiving a trauma patient from an ambulance crew is, in the same sixty seconds, assessing the patient, listening to a verbal handover, and trying to remember details to write down later. Every piece of information that already exists in a structured digital record — vitals trend during transport, medications given, mechanism of injury as reported at the scene — is one less thing that nurse has to capture from memory under pressure. This is not a minor workflow convenience; it is the specific place where information gets lost between pre-hospital and in-hospital care, and it is entirely preventable with a shared record rather than a paper handover sheet.
An ambulance trip record tied to a road accident is exactly the kind of document likely to be requested in an insurance claim, a PM RAHAT reimbursement audit, or a legal proceeding years after the fact. It follows the same statutory retention logic we've covered for the rest of the hospital record set in our guide to medical records retention rules for Indian hospitals, and access to it needs the same audit trail described in role-based access control under the DPDP Rules. This applies with particular force to ambulance GPS and timestamp data, which is precisely the kind of granular location information that a PM RAHAT audit or an insurance dispute is most likely to scrutinise, and precisely the kind of data a paper-based dispatch log cannot produce with any confidence months after the fact.
A single "call handled" entry can't reconstruct response-time performance or defend a delayed-response complaint.
If an ALS vehicle can be dispatched without the required critical care staff aboard, the system isn't actually enforcing the standard, just recording that a vehicle was sent.
Separate systems mean re-entry under time pressure, which is exactly when transcription errors happen.
If your hospital treats road accident victims, ask specifically whether admission and treatment data can be exported in a form that supports an eDAR/TMS-linked reimbursement claim, not just a general PDF summary.
See our guide to NABH accreditation software for how emergency and transport documentation fits the wider accreditation picture, and implementation and migration services for realistic rollout sequencing.
AIS-125 is the Automotive Industry Standard governing ambulance construction, equipment, and (indirectly, through category definitions) staffing in India. Approved in June 2014 and made mandatory via G.S.R. 868(E) dated 8 September 2016, it applies to Category L and M road ambulances manufactured from 1 April 2018 onward, and defines four categories: first responder, patient transport, Basic Life Support (BLS), and Advanced Life Support (ALS).
A critical care nurse or doctor, plus an Emergency Medical Technician (EMT), as a minimum. A BLS ambulance requires a trained EMT. These staffing levels correspond to the clinical capability each category is certified to provide.
Section 2(12-A) of the Motor Vehicles Act, 1988 defines the golden hour as the critical one-hour period after a traumatic injury during which timely medical care significantly reduces the probability of death. The Law Commission of India has estimated that timely care in this window could prevent up to 50% of road accident fatalities.
PM RAHAT (Road Accident Victim Hospitalisation and Assured Treatment) is the nationwide cashless treatment scheme for road accident victims, providing coverage up to ₹1.5 lakh per person for up to seven days from the accident, provided police are informed within 24 hours. It is implemented by the National Health Authority through a platform integrating the Ministry of Road Transport's eDAR system with NHA's Transaction Management System, and its statutory basis is Section 162 of the Motor Vehicles (Amendment) Act, 2019.
108 is India's general emergency ambulance number, pioneered by EMRI in Andhra Pradesh in 2005 and now operating in over 20 states and union territories, handling trauma, cardiac, and general medical emergencies. 102 is dedicated to maternal and child transport under the Janani Shishu Suraksha Karyakram, known by different local names across states such as Janani Express (Madhya Pradesh, Odisha) and Mamta Vahan (Jharkhand).
For claiming reimbursement under the PM RAHAT cashless treatment scheme, yes in effect — the claim depends on producing accurate admission and treatment data in a form the eDAR/TMS platform recognises. A hospital whose ambulance dispatch and ED admission systems aren't connected is more likely to lose a legitimate claim to a documentation gap than a clinical one.
Road traffic accidents are among the most common MLC triggers, and the ambulance handover record and the MLC record typically describe the same arrival event. Software that treats them as unrelated forces staff to re-enter the same facts twice, usually under time pressure in the emergency department.
The same statutory retention logic that applies to the rest of the hospital record set applies here, since a trip record tied to a road accident is a likely candidate for an insurance claim, a PM RAHAT audit, or legal proceedings well after the event. See our full guide to medical records retention rules for the complete statutory picture.
Want your ambulance's en-route record already sitting in the ED chart before the patient arrives?
Book a demo