QBCore Frameworkqbcore.netCommunity docs
On this page

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

  1. Install qb-core, oxmysql and the PolyZone modules used in the manifest. Confirm qb-inventory and job/dispatch dependencies on your server.
  2. Keep qb-ambulancejob's client/, server/, html/ and locales intact.
  3. Check that ambulance is an actual job in QBCore shared jobs and that hospital locations exist in the config.
  4. 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:

KeyFunction
Config.UseTargetInteraction behavior based on UseTarget convar
Config.MinimalDoctors / DocCooldownAvailability and cooldown for medical services
Config.WipeInventoryOnRespawnInventory handling on respawn
Config.RespawnAtNearestHospitalHospital selection behavior
Config.BillCostMedical service charge
Config.DeathTime / ReviveInterval / MinimumReviveDeath/respawn timing
Config.HealthDamage / ArmorDamageWound severity thresholds
Config.LocationsHospitals, duty/spawn positions and other points
Config.AuthorizedVehiclesAllowed 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

SymptomFirst check
EMS duty count wrongReal GetDoctorCount export and active ambulance job
Cannot revive a playerCorrect event side, EMS permission and target status
Bleeding/injury effect persistsLast-stand, injury sync and death metadata
Player respawns at wrong hospitalRespawnAtNearestHospital and Config.Locations
Medic gear unusableQBCore shared items, usable-item handlers, qb-inventory
No such export RevivePlayerUpstream exports only GetDoctorCount

Update checklist

  1. Verify installed qb-ambulancejob, qb-core, qb-inventory and police/hospital dependencies.
  2. Test death/respawn on disconnected and reconnected test clients.
  3. Audit revive/heal/admin operations against real ACE/job permissions.
  4. 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.

On this page

Leonida RP server website built with RPWebsite
RPWebsite

Advertisement · RPWebsite

Want a website for your server?

Launch a site with live player status, rules, and a join button in minutes.

Build your website