JP2013030046A - Emergency command system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To solve the problem that, when an emergency call of a fire or the like is received, a fire engine and an ambulance car are dispatched together and since the emergency call is to be received only once normally, if an emergency call is received, only one dispatch case relating to the dispatch is created but since it is necessary to separately manage a disaster case relating to the fire engine and a rescue case relating to the ambulance car because of statistics or the like, the office staff in the fire headquarter separates the dispatch cases into fire cases and rescue cases, so that work for the office staff in the fire headquarter may be increased or there is the risk of making input errors.SOLUTION: An emergency command system is provided in which, on the basis of a car type of a dispatched emergency vehicle stored in a dispatch case, a disaster case is created for each emergency call for a fire engine and a rescue case is created for each dispatched ambulance car for an ambulance car.

Description

  The present invention is an emergency command system in which a disaster case related to a fire engine is created for each emergency call and an emergency case related to an ambulance is created for each ambulance dispatched based on the type of emergency vehicle included in the dispatch case. is there.

  The Fire Department will accept emergency reports such as disasters such as fires and emergency services from the whistleblower. The staff of the fire department headquarters inputs information obtained from the whistleblower into the command board. A dispatch case is created based on the input information. A case number is assigned to the created dispatch case. A dispatch order is prepared based on the case. This dispatch command is transmitted to an ambulance in the case of emergency so that the emergency vehicle can quickly reach the disaster site, and is transmitted to both the fire engine and the ambulance in the event of a disaster such as a fire. Therefore, in the case of a disaster, the prepared dispatch case includes information on both the fire engine and the ambulance. (Patent Document 1)

JP 2008-262319 A

  In the case of ambulance, only the ambulance is dispatched, whereas when there is a victim due to a disaster such as a fire, both the fire engine and the ambulance are dispatched. After the disaster activity is over, the staff of the fire department headquarters prepares an end report, but if there are victims due to a disaster such as a fire, it is necessary to prepare a report on fire fighting and a report on first aid separately . This is because, for the operation of the fire fighting system, statistical data relating to fire fighting and first aid are separately compiled, and emergency cases are individually managed. Also, the method of preparation differs between disaster cases and emergency cases. A disaster case is created for each emergency call, while an emergency case is created for each ambulance dispatched. This is because ambulances carry victims to hospitals and the like, and the fire department headquarters manages the dynamics of each vehicle. In addition, disaster incidents and emergency incidents are created and managed separately, making it easier for staff at the fire department to grasp the number of incidents.

  For the above reasons, the staff at the Fire Department will prepare a disaster case and an emergency case separately. As the preparation procedure, each case was prepared by dividing into a disaster case related to fire fighting and an emergency case related to emergency depending on whether the emergency vehicle dispatched was a “fire engine” or “ambulance”. For example, if an ambulance is dispatched together with a fire engine at the time of a disaster, the data associated with the ambulance data is extracted, and a case number different from the case number of the original dispatch case is assigned to provide an emergency first aid. I was creating a case. As a result of the above work, there was a risk that the amount of work of the staff of the fire department headquarters would increase, or that input mistakes by the staff would occur.

  Therefore, the present invention sorts out whether the emergency vehicle included in the dispatch case created at the time of emergency call reception is a “fire truck” or “ambulance”, and the data of the fire truck is a disaster incident related to fire fighting, The purpose of the ambulance data is to divide the ambulance data into emergency cases and provide an emergency command system for creating each case.

  In order to achieve the above object, the emergency command system of the present invention creates an emergency case and an emergency case based on the vehicle type of the outgoing vehicle included in the outgoing case.

  According to such an emergency command system, the fire department headquarters staff manually input the emergency case and the disaster case based on the type of dispatch vehicle included in the dispatch case. This eliminates the need for staff and saves time and effort. In addition, it is possible to prevent human error such as an input error or an input omission of a fire department headquarters.

It is the schematic of the emergency command system of this invention. It is pre-division dispatch case data stored in the emergency command system of the present invention. It is the post-division dispatch case data stored in the emergency command system of the present invention. It is a block diagram of the emergency command system of this invention. It is a flowchart of the emergency command system of this invention. It is vehicle data memorize | stored in the emergency command system of this invention.

  The emergency command system of the present invention is created by dividing the case A into a disaster case A1 and an emergency case A2 based on the vehicle type as shown in FIG. The case of FIG. 1, FIG. 2 and FIG. 3 will be described below as examples, and after the emergency command system of the present invention has received an emergency call from the caller, a dispatch case is created, and then the disaster case and the emergency case are divided. The procedure until creation is described.

  The configuration of the emergency command system of the present invention will be described with reference to FIG. As shown in FIG. 4, the fire department headquarters includes an input means 1 for inputting the contents of an emergency call from the whistleblower to the command board, a case management means 2 for managing the contents of the case, and the case management means 2 The vehicle type selection means 3 for selecting emergency vehicles included in the case contents stored in the case, the case creation means 4 for making a case, and the control means 5 for controlling the above-mentioned parts.

  The input means 1 for inputting information is a device for a clerk of the firefighting headquarters to input the contents of an emergency call to a command board in the firefighting headquarters. For example, a mouse or a keyboard is applicable.

  The case management means 2 for managing the contents of the case, for each dispatched case created by the case creation means 4 based on the information input from the input means 1, the name of the whistleblower, the type of disaster and emergency such as fire, It is a device that stores information such as the location (address, latitude / longitude) of the report location, and the damage status against disasters. As shown in FIG. 2 and FIG. 3, “reception number”, “case number” and the like are given and stored in a state in which data is associated with each case. The case management means 2 does not store information on dispatch commands transmitted from the fire department to emergency vehicles such as fire engines and ambulances, but stores information required when creating an end report. To do.

  A plurality of data as shown in FIG. 2 and FIG. 6 are stored as the dispatch event data indicating the dispatch event. First, description will be made in order from the top of FIG. The “(1) History Incident Management Table” includes a “reception number” assigned when an emergency call is received, a “incident number” assigned for each incident, and a “incident status” indicating the current incident status. “Reception time” that is the time when the emergency call is received, “Disaster classification code”, “Disaster classification code”, “Disaster scale code”, and the like indicating the disaster type and scale. In the “(2) history incident reporter table”, “reporter name”, “reporter name”, and the like, which are names of reporters, are stored. In “(3) History Incident Patient Table”, the name of the injured person is stored. The “(4) history case vehicle table” stores “vehicle code” indicating the identification code of the emergency vehicle that has been dispatched. In the “(5) history event dynamic table”, “vehicle code”, “internal dynamic code” indicating the state of the emergency vehicle, and the like are stored. The “(6) managed vehicle dynamics table” stores “internal dynamics code”, “unscheduled availability”, etc., which are states of emergency vehicles, for each “vehicle code”. Further, as shown in FIG. 6, the “vehicle master table” stores “vehicle type code”, “vehicle name”, and “station code” of each vehicle.

  FIG. 3 is a diagram showing the dispatch case after the division. As described at the bottom of FIG. 3, “(7) History case division log table” includes “pre-division reception number”, “pre-division case number”, and information after division. A certain “division receipt number”, “division case number”, and the like are stored.

  The vehicle type selection means 3 for selecting the dispatched vehicle for each vehicle type such as a fire truck or an ambulance sorts the dispatched emergency vehicle stored in the case management means 2 according to the vehicle type such as a fire truck or an ambulance.

  The case creation means 4 for creating a case creates a dispatch case based on the emergency call input by the input means 1. Moreover, based on the prepared dispatch case, a disaster case related to a fire engine and an emergency case related to an ambulance are prepared.

  The control means 5 for controlling each means in the command board of the firefighting headquarters and transmitting information is like an HDD storing software for comprehensively controlling predetermined functions of the emergency command system of the present invention. A processing device such as a CPU and a microcomputer for executing processing by the software and its software is provided, and each part in the firefighting headquarters connected thereto is controlled.

  The emergency command system of the present invention has the above-described configurations. The dispatch case is created by the case creation means 4 based on the information input to the input means 1 (the name of the reporter, the disaster type, the report location, etc.). The case management means 2 stores the same information as the dispatch case created by the case creation means 4 as shown in FIG. The incident case data stored in the case management unit 2 is divided into the dispatch case data shown in FIG. 3 to create a disaster case and an emergency case.

  Next, a procedure for creating post-division dispatch event data in FIG. 3 from pre-division dispatch event data in FIG. 2 will be described based on the flowchart in FIG.

  In ST <b> 1, the vehicle type selection unit 3 acquires dispatch case data stored in the case management unit 2 via the control unit 5. After the vehicle type selection means 3 acquires the dispatch event data, the process proceeds to ST2.

  In ST2, the vehicle type selection means 3 uses the “vehicle code” shown in “(4) history case vehicle table” of the acquired dispatch case data in FIG. 2 and the “vehicle type code” in the “vehicle master table” in FIG. Compare the vehicle types of emergency vehicles that have been dispatched. After the vehicle type selection means 3 finishes selecting the vehicle type of the emergency vehicle using the “vehicle master table”, the process proceeds to ST3.

  In ST3, it is confirmed whether or not “6 (ambulance)” is included in the selected “car type code”. If there is no “6 (ambulance)”, the process of this flowchart is terminated (END). If there is "6 (ambulance)", the vehicle type selection means 3 outputs the acquired pre-division dispatch case data to the case creation means 4 and proceeds to ST4.

  In ST4, the case creation means 4 newly creates "reception number" and "case number" as shown in the data of "(1) history case management table" in FIG. The procedure to create a new one is shown below. Copy the data related to the “reception number” of “100100001” in the “(1) history event management table” of the acquired dispatch case data. In the copied “(1) History Incident Management Table”, change the “Receipt Number” from “100100001” to “100100002”, and change the “Case Number” from “1” to “2”. After saving in the “case management table”, the process proceeds to ST5.

  In ST5, the case creation means 4 sets the data regarding the victim to a new “reception number” as shown in the data of “(2) History Incident Reporter Table” and “(3) History Incident Patient Table” in FIG. "And" Case Number ". The creation procedure is shown below. The data related to the reception number “100100001” is copied from the “(2) history case reporter table” and “(3) history case victim table” of the acquired dispatch case data. Change the “Reception number” in the copied “(2) History Incident Table” and “(3) History Incident Table” from “100100001” to “100100002”. After saving in the “person table” and “(3) history case victim table”, the process proceeds to ST6.

  In ST6, the case creation means 4 sets the ambulance as shown in the data of “(4) History case vehicle table”, “(5) History case state table”, “(6) Management vehicle state table” in FIG. Change the related “reception number” and “case number”. The creation procedure is shown below. Of the acquired dispatch case data, “(4) History Case Vehicle Table”, “(5) History Case Dynamic Table”, “(6) Managed Vehicle Dynamic Table”, “Vehicle Code” is “6 (Ambulance)” Select one reception number related to "" and change the selected "reception number" to "100100002". As a result, the information related to the ambulance becomes an emergency case different from the dispatch case, and the information on the ambulance is deleted from the original case. After changing the “reception number”, the process proceeds to ST7.

  In ST7, the case creation means 4 leaves a history of changing the “reception number” and “case number” as shown in the data of “(7) History case division log table” in FIG. This “(7) history case division log table” is data for leaving a history of division of cases. This “(7) history case division log table” stores data such as “reception number” and “case number” before division, and “reception number” and “case number” after division. After creating the emergency case as a separate case, return to ST2.

  If there are a plurality of dispatch cases “6 (ambulance)”, one is selected from the plurality and the “reception number” and “case number” are changed to new numbers. Repeat this process to create an emergency case for each ambulance individually. If “6 (ambulance)” is single, “ambulance” is another case in the first operation, and the processing of this flowchart ends (END).

  As shown in “Vehicle code” in “(4) History incident vehicle table” to “(6) Managed vehicle dynamics table” in the pre-division dispatch event data in FIG. 2, there is one fire truck (vehicle code 4, vehicle type code). 2) The procedure for creating post-division dispatch event data shown in FIG. 3 from the pre-division dispatch case data shown in FIG. 2 is described below, assuming that one ambulance is dispatched (vehicle code 6, vehicle type code 6). Explained.

  As shown in the flowchart of FIG. 5, the process proceeds to ST3. This embodiment is composed of a fire truck (vehicle code 4, vehicle type code 2) and an ambulance (vehicle code 6, vehicle type code 6). The vehicle type selection means 3 selects an emergency vehicle whose “vehicle type code” is “6 (ambulance)” from “(4) history case vehicle table” of FIG. After the vehicle type selection means 3 finishes selecting “6 (ambulance)” from the “vehicle type code” in the “(4) history case vehicle table” of FIG. 2, the process proceeds to ST4.

  In ST4, the case creation means 4 creates “(1) history case management table” in FIG. 3 from “(1) history case management table” in FIG. Specifically, the data related to “100100001” in “reception number” of “(1) history incident management table” in FIG. 2 is copied, and the “reception number” of the copied data is changed from “100100001” to “100100002”. In addition, the “case number” is changed from “1” to “2” and stored in “(1) history case management table” of FIG. After saving, proceed to ST5.

  In ST5, the case creation means 4 changes the “(2) history case reporter table” and “(3) history case reporter table” and “(2) history case reporter table” and “(3 ) Create a “history case victim table”. Specifically, in “(2) History Incident Table” and “(3) History Incident Table” in FIG. 2, copy the data related to “Receipt Number” “100100001” “No.” is changed from “100100001” to “100100002” and stored in “(2) History Incident Table” and “(3) History Incident Table” in FIG. After saving, proceed to ST6.

  In ST6, the case creation means 4 performs "(4) history case vehicle table", "(5) history case dynamic table", "(6) management vehicle dynamic table" in FIG. “Vehicle table”, “(5) History event dynamic table” and “(6) Managed vehicle dynamic table” are created. Specifically, among “(4) History Case Vehicle Table”, “(5) History Case Movement Table”, and “(6) Managed Vehicle Movement Table”, “Vehicle Type Code” is related to “6 (Ambulance)” Select the data to be changed, change the “reception number” of the selected data from “100100001” to “100100002”, and select “(4) History Incident Vehicle Table” and “(5) History Incident Dynamic Table” in FIG. , “(6) Managed vehicle dynamics table” is stored. After saving, proceed to ST7.

  In ST7, the case creation means 4 creates “(7) history case division log table” of FIG. Specifically, “100100001” is input to “reception number before division” and “100100002” is input to “reception number after division” in “(7) History case division log table” of FIG. In addition, “1” is input to “pre-division case number”, and “2” is input to “post-division case number”. After the creation of “(7) history incident division log table”, the process returns to ST2.

  In ST2, the vehicle type of the emergency vehicle related to “100100001” as the “reception number” of the divided dispatch case data is selected. After selection, the process proceeds to ST3.

  In ST3, as shown in FIG. 3, there is no data in which the “vehicle code” is “6” in the dispatch event data related to “reception number” “100100001”. Therefore, the process of this flowchart is ended (END).

  By repeating the above work, the emergency command system of the present invention can divide and prepare a disaster case and an emergency case from a dispatch case. Therefore, it is not necessary for the staff of the fire department headquarters to manually create disaster incidents and emergency incidents, and the amount of work does not increase.

  It should be noted that the members on the emergency vehicle cannot recognize that the “case number” and the “reception number” have been changed. Therefore, the following measures are taken to ensure that data members cannot be found when a member of an emergency vehicle confirms the case contents.

  When there is a request for confirmation of the case contents from the emergency vehicle, the command board of the fire department headquarters refers to “(7) History case division log table” shown in FIG. This makes it possible to determine whether the emergency vehicle that has requested confirmation of the content of the case is an emergency vehicle in which the “case number” and the “reception number” have been changed. If the emergency vehicle has been changed, the contents of the case related to the changed “case number” and “reception number” are transmitted to the emergency vehicle. From the above, it is possible to easily respond to a request for confirmation of the contents of an emergency vehicle case.

DESCRIPTION OF SYMBOLS 1 Input means 2 Case management means 3 Vehicle type selection means 4 Case preparation means 5 Control means

Claims (2)

An emergency command system that accepts emergency calls, creates and manages dispatch cases according to the accepted emergency calls,
A case management means for managing the dispatch case;
Vehicle classification means for reading out the vehicle type of the emergency vehicle included in the dispatch case and determining whether the read emergency vehicle includes an ambulance;
If an ambulance is included in the emergency vehicle,
An emergency command system comprising: a case creation means for reading out data relating to an ambulance from the dispatch case and newly creating an emergency case. 2. The emergency command system according to claim 1, wherein the case creation unit creates an emergency case individually for all the ambulances sorted by the vehicle sorting unit.

Images