16-04-2012, 12:37 PM
Ambulance Dispatch System
Design Specification.pdf (Size: 423.9 KB / Downloads: 90)
INTRODUCTION
PURPOSE
This design specification document describes the functions and design for this Ambulance Dispatch System (ADS). This dispatch system is needed to help ensure that the ambulance dispatching company meets all federal mandates about the speed at which an ambulance is dispatched. In order to make this possible, the system greatly decreases the amount of paperwork that must be filed. This system shall also help the company ensure that they are providing an adequate amount of ambulances for each of their service areas by enabling the management to track the status of each ambulance and a log of ambulance activity.
DEFINITIONS, ACRONYMS, AND ABBREVIATIONS
ADS – Ambulance Dispatch System
Dispatcher – The persons who decide what ambulance to dispatch. The dispatcher also contacts the ambulance drivers as well as updates the status of each ambulance.
GUI – Graphical User Interface, Screen visible to the user for inputting data and viewing output
Operator – The persons who receive the 911-incident calls and input the call information into the system. The operator also determines the uniqueness of each call.
ISSUES DIFFERING FROM REQUIREMENT SPECIFICATION DOCUMENT
From Requirement 1: Operator Input – We determined to not make the “Contact Phone Number” of caller a required data field.
From Requirement 2: Uniqueness of Call – Duplicate calls are not logged and the system displays a list of calls that matches 3 of the 4 required inputs as opposed to matching 3 of 5 required inputs.
From Requirement 5: Ambulance Status Update – Only currently active ambulances are displayed on the left, not currently active incidents.
From Requirement 8: Management Reports – Instead of the user choosing to display a report by day, week, year, or by ambulance, the user now simply enters two dates. One date is a starting date and the other is an ending date of when the average times should be calculated.
MANAGEMENT REPORTING
The Management Reporting Component’s purpose is to allow mangers and supervisors to see if the Ambulance Dispatch System is meeting current federal mandates. These mandates state that an ambulance must be dispatched within an average of three minutes of an incident call. The ambulance must then arrive at the scene of the incident within an average of eleven minutes.
PERSISTENT DATA MANAGEMENT
To achieve fast and reliable data access, the following database schema shall be implemented. The schema has three tables: CallInfo, AmbulanceStatus, and ResponseTimes (See Figure 3 below). The first table, CallInfo contains all the necessary attributes to store information pertaining to a 9-11 incident call. The first attribute is the IncidentNum which is unique number automatically assigned to each call inserted into the database. The system shall increment the number of the last IncidentNum in the database to acquire the next unique IncidentNum, and the first call inserted into the database shall be assigned an IncidentNum of 1.