Ambulance Dispatch Android App for Hospitals with Crew Assignment

Ambulance dispatch for hospitals is the coordination work that sits between a hospital ward that needs a patient moved and the crew that moves the patient. When a ward contacts the control desk, the desk must decide which request goes first, which vehicle is free, which crew fits that job, and how long the wait will be. Without a board, those decisions live in phone calls, paper notes, and memory, so separate desks can promise the same vehicle, a routine transfer can quietly wait behind newer urgent jobs, and nobody can later explain why a unit was chosen. The ambulance dispatch app in this project replaces that chain with a shared live board: requests enter a ranked queue, every unit shows its current status, assignments are recorded with the reason behind them, and ETA estimates update from demo road distances. The result is a desk that can answer what is waiting, what is moving, and what is free.

A request begins when a hospital ward submits a transfer or emergency need through the hospital side of the app, and it ends when the assigned crew closes the job after handover at the destination. Between those two points, the system ranks the request, matches it to a unit, and keeps both sides informed. Ranking uses the published priority rule: urgency weight minus estimated travel minutes, with ties broken by earliest request time and then nearest unit. Matching considers only units marked Available, so an en-route or off-duty unit can never be double-booked by the board. The crew receives the job card, updates status at each stage, and the desk watches the same job move from assigned to en route to on scene to transporting to complete. Every stage change is written to the audit trail, so the full journey of a request can be replayed step by step in the report and the demonstration.

1. A ward submits a request with pickup location, destination, urgency level, and patient-handling notes such as stretcher or oxygen requirements.
2. The system computes the priority score as urgency weight minus estimated travel minutes, using Critical at 100 points, Urgent at 60 points, and Routine at 25 points, and inserts the request into the ranked queue.
3. The control desk opens the dispatch board, sees every unit with its crew and current status, and picks an Available unit for the highest-ranked request.
4. The assignment is recorded with the request, unit, crew, score at dispatch time, and ETA estimate, and the job card is pushed to the crew app.
5. The crew accepts the job, travels to the pickup point, and updates status through Arrived on scene and Start transport as the job progresses.
6. The desk tracks the job on the board through each status change, and reassigns the job from the board if the unit goes off duty mid-job.
7. On arrival at the destination, the crew closes the job after handover, the unit returns to Available, and the completed job stays in the audit trail for review.

Tech stack:

• Kotlin · Android Studio
• Jetpack Compose · Material 3
• Firebase Realtime Database · Authentication
• Google Maps SDK · demo GPS positions
• Room database · offline status queue
• Retrofit · REST endpoints for hospital requests
• WorkManager · background status sync
• JUnit · Espresso testing

The dispatch board is the heart of this build, and it works together with three supporting capabilities that make the board trustworthy rather than merely decorative. Live unit status shows every vehicle and crew as Available, En route, On scene, Transporting, or Off duty, so the desk never assigns a unit that is already committed. Transparent priority scoring ranks the request queue by a published rule instead of by gut feel, so any ranking can be audited after the fact. One-tap crew assignment turns a decision into an action and writes it to an audit trail with the score and ETA at dispatch time. ETA estimates from demo road distances give the ward a waiting time it can plan around, while the crew app keeps the crew in the same loop with job details, status updates, and navigation context.

• [Live dispatch board] A single control-desk view showing all units, their crews, their current status, and the open request queue, with unit positions plotted on a demo sector map.
• [Transparent priority scoring] Every request carries a visible score computed as urgency weight minus estimated travel time in minutes, so Critical requests outrank Routine ones and near-identical requests resolve by earliest request time, then nearest unit.
• [One-tap crew assignment] The desk assigns an available unit to a request from the board, and the assignment, the score at dispatch time, and the ETA estimate are recorded in an audit trail for later review.
• [Crew app with job cards] Crew members receive a job card with pickup ward, destination, demo distance, ETA estimate, and patient-handling notes, and update their status through Arrived on scene and Start transport actions.
• [ETA estimates from demo distances] Each request shows an ETA estimate derived from its demo road distance at a stated demo speed, labelled as a demo figure and never presented as a live traffic prediction.
• [Request queue with urgency filters] The queue filters by Critical, Urgent, and Routine urgency levels, so the desk can inspect one urgency class without losing sight of the rest of the queue.
• [Reassignment and off-duty handling] A job can be reassigned when a unit goes off duty, and off-duty units stay visible on the board instead of vanishing, so coverage gaps are obvious.
• [Assignment audit trail] Every dispatch decision keeps the request, unit, crew, score, and ETA estimate together, giving the report a concrete worked example of why each unit was chosen.

• Android app source code with the dispatch board, crew app views, and request queue
• Working demo build with fictional hospitals, units, crews, and requests for demonstration
• Priority-scoring module with the published urgency weights and tie-break rules
• Assignment audit trail with score and ETA estimate recorded at dispatch time
• Project report PDF covering problem, design, priority mechanism, testing, and limitations
• PPT presentation for review
• Viva Q&A preparation document covering dispatch logic, Android architecture, and data flow

To request this project on a quotation basis, message on WhatsApp with the scope needed: hospital dispatch board only, board plus crew app, or the full build with documentation. The quotation covers the agreed scope, the build is prepared to order, and delivery timing is discussed on WhatsApp once the scope and any customisation are confirmed. No fixed price is quoted on this page, and no delivery date is promised before that discussion.