Updated 2026-10-11 · 3 min read
qb-ambulancejob: EMS and hospital lifecycle
The official qb-ambulancejob manages hospital beds, death/last-stand state, injuries, EMS duty and recovery. This reference is pinned to commit 19bb190. It is not a complete patient-records database or arbitrary injury creation service.
Installation
- Install
qb-core,oxmysqland thePolyZonemodules used in the manifest. Confirmqb-inventoryand job/dispatch dependencies on your server. - Keep
qb-ambulancejob'sclient/,server/,html/and locales intact. - Check that
ambulanceis an actual job in QBCore shared jobs and that hospital locations exist in the config. - Test injuries, last stand, hospital transport, EMS interaction, bandages, first aid and reconnect on staging.
The upstream tree contains no packaged SQL file creating player_meds or medical_records. These were fabricated in the previous QBCore.net page; do not add them for a standard installation.
Configuration
The current config.lua includes:
| Key | Function |
|---|---|
Config.UseTarget | Interaction behavior based on UseTarget convar |
Config.MinimalDoctors / DocCooldown | Availability and cooldown for medical services |
Config.WipeInventoryOnRespawn | Inventory handling on respawn |
Config.RespawnAtNearestHospital | Hospital selection behavior |
Config.BillCost | Medical service charge |
Config.DeathTime / ReviveInterval / MinimumRevive | Death/respawn timing |
Config.HealthDamage / ArmorDamage | Wound severity thresholds |
Config.Locations | Hospitals, duty/spawn positions and other points |
Config.AuthorizedVehicles | Allowed EMS vehicle list |
The file also contains wound, bleeding and damage-related settings. Do not use Config.MedicalSupplies, Config.InjuryTypes or Config.AmbulanceSpawns as if they were defined by this upstream revision.
Real server export
The server implementation exposes one server export:
local onDutyDoctors = exports['qb-ambulancejob']:GetDoctorCount()
print(('On-duty doctors: %d'):format(onDutyDoctors))This is a doctor count, not a client-callable RevivePlayer export. The resource does not register AddInjury, HealPlayer, TreatPatient or GetMedicalRecord as server exports.
Hospital events and callbacks
Internal server network events are named under hospital:server:, including SendToBed, RespawnAtHospital, SetDeathStatus, SetLaststandStatus, TreatWounds, RevivePlayer and UseFirstAid. These are not qb-ambulancejob:server:playerDied or billPatient.
Callbacks registered with QBCore include hospital:GetDoctors, hospital:GetPlayerStatus and hospital:GetPlayerBleeding.
The server also registers EMS commands such as 911e and admin/medical commands including revive, heal and aheal. Check the installed QBCore ACE configuration before exposing privileged commands.
Authorization warning: Internal network events that heal, revive or change a player's death state can be dangerous if clients can trigger them without server-side proof of EMS/admin permission and allowed target. Do not treat existing client UI checks as an authorization boundary.
Troubleshooting
| Symptom | First check |
|---|---|
| EMS duty count wrong | Real GetDoctorCount export and active ambulance job |
| Cannot revive a player | Correct event side, EMS permission and target status |
| Bleeding/injury effect persists | Last-stand, injury sync and death metadata |
| Player respawns at wrong hospital | RespawnAtNearestHospital and Config.Locations |
| Medic gear unusable | QBCore shared items, usable-item handlers, qb-inventory |
No such export RevivePlayer | Upstream exports only GetDoctorCount |
Update checklist
- Verify installed
qb-ambulancejob,qb-core,qb-inventoryand police/hospital dependencies. - Test death/respawn on disconnected and reconnected test clients.
- Audit revive/heal/admin operations against real ACE/job permissions.
- Never import unrelated patient-record SQL without verifying its real owner.
Sources
Repository · Server export/events · Configuration · Manifest
Related: qb-policejob, server authority.
Found an issue in this guide?
Send the page URL, the affected example, and a source or reproduction to the site maintainer. For a server or resource problem, use the support guide.
