JP7383385B2 - Transport plan generation device, transport plan generation system, and transport plan generation method - Google Patents

Description

Embodiments of the present invention relate to a transport plan generation device, a transport plan generation system, and a transport plan generation method.

In response to a call from a caller, a communication center that accepts 119 calls requests emergency services to be dispatched to the scene of a person in need of rescue (person in need of rescue). When the emergency team arrives at the scene, they determine the symptoms and condition of the person in need of rescue, and then search for a hospital to accept the person in need of rescue. However, after emergency teams arrive at the scene, it is not possible to decide on a hospital to receive the patient, which can lead to delays in transporting people in need of rescue. Delays in transportation can be life-threatening, so countermeasures are necessary.

JP2017-213951A International Publication No. 2013/065113 JP 2017-210078 Publication JP2009-075952A

The problem to be solved by the present invention is to prevent delays in transporting a person in need of rescue.

The transport plan generation device according to the embodiment includes an information acquisition unit that acquires rescue recipient information regarding at least one of the location of the scene where the rescue recipient is located and the rescue recipient; a hospital information acquisition unit that acquires hospital information including information; and a hospital information acquisition unit that acquires hospital information including information on the person in need of rescue based on the information on the person in need of rescue acquired by the information acquisition unit, and the hospital information acquired by the hospital information acquisition unit. The present invention includes a search unit that searches for a hospital that accepts patients, and a provision unit that provides transport plan information corresponding to the hospital searched by the search unit to an emergency team.

FIG. 1 is a diagram for explaining an overview of a transportation plan generation system according to a first embodiment. FIG. 2 is a diagram showing the configuration of the transport plan generation system shown in FIG. 1. FIG. 3 is a diagram showing the configuration of the transport plan generation device shown in FIG. 2. FIG. 4 is a diagram showing the configuration of the emergency team information table shown in FIG. 3. FIG. 5 is a diagram showing the configuration of the hospital information table shown in FIG. 3. FIG. 6 is a flowchart showing the procedure of dispatch request processing executed by the transport plan generation device shown in FIG. 2. FIG. 7 is a diagram showing the configuration of a rescue-required person information table generated in the dispatch request process shown in FIG. 6. FIG. 8 is a diagram showing an example in which the emergency team information table shown in FIG. 4 has been updated. FIG. 9 is a flowchart showing the processing procedure until the hospital information table shown in FIG. 5 is updated. FIG. 10 is a flowchart showing the procedure of the receiving destination determination process executed by the transport plan generation device shown in FIG. FIG. 11 is a diagram showing the structure of the rescue recipient information table generated in the acceptance destination determination process shown in FIG. 10. FIG. 12 is a diagram showing the structure of a hospital information table generated in the acceptance destination determination process shown in FIG. 10. FIG. 13 is a diagram showing processing up to the time when the hospital information table is updated in a procedure different from the procedure shown in FIG. FIG. 14 is a flowchart illustrating the procedure of a process for acquiring information on a person in need of rescue, which is executed by the transport plan generation device according to the second embodiment.

Hereinafter, embodiments of a transport plan generation device, a transport plan generation system, and a transport plan generation method will be described in detail with reference to the accompanying drawings.

(First embodiment)
As shown in Figure 1, the transport plan generation system 1 effectively utilizes the time between when an emergency team is requested to be dispatched to a scene where there is a person who requires rescue (person in need of rescue) and when the emergency team arrives. During this time, the system determines which hospital will accept the person in need of rescue.

As shown in FIG. 2, the transportation plan generation system 1 includes a transportation plan generation device 100 installed at the fire department's reporting center, an ambulance terminal 200 owned by the emergency team, and a hospital terminal 300 installed at the hospital. Equipped with

The transport plan generation device 100 determines which emergency team should be dispatched to the scene in response to a report from the scene where there is a person in need of rescue. For example, the transport plan generation device 100 identifies the emergency squad closest to the scene from among the waiting ambulance crews based on the location information of the scene acquired when a caller makes a report, and sends the identified ambulance Request dispatch to the scene. Note that "near" here may include a temporal element in addition to a distance element. In other words, in addition to the concept of being close in a straight line distance, it includes the concept of being close in terms of road traffic (early in terms of time). Further, although FIG. 2 shows an example in which the person in need of rescue and the informer are different, the person in need of rescue and the informer may be the same person. Further, the location of the person in need of rescue may be either indoors or outdoors.

The transport plan generation device 100 also determines a hospital that will receive the person in need of rescue, and provides the determined hospital to the emergency team. For example, the transport plan generation device 100 specifies the hospital closest to the scene as the receiving destination from among the hospitals that can accept the person in need of rescue. Note that "near" here may include a temporal element in addition to a distance element. In other words, in addition to the concept of being close in a straight line distance, it includes the concept of being close in terms of road traffic (early in terms of time). The transport plan generation device 100 notifies the emergency team of the specified hospital, and also makes a reservation for the receiving hospital by notifying the specified hospital that the person in need of rescue will be transported.

The configuration of the transport plan generation device 100 will be described with reference to FIG. 3. The transport plan generation device 100 includes an input interface 110, a display 120, a communication interface 130, a storage circuit 140, and a processing circuit 150.

The input interface 110 is composed of input devices such as a mouse and a keyboard. The input interface 110 accepts various operations by the operator, and supplies electrical signals corresponding to the operator's operations to the processing circuit 150.

The display 120 is composed of a display device such as an organic electro-luminescence (OEL) display or a liquid crystal display (LCD). The display 120 displays various image data under the control of the processing circuit 150.

The communication interface 130 is composed of a communication device such as a NIC (Network Interface Card). The communication interface 130 communicates with the emergency team terminal 200, the hospital terminal 300, and the mobile terminal 400 under the control of the processing circuit 150.

The memory circuit 140 is composed of, for example, a semiconductor memory element such as a RAM (Random Access Memory) or a flash memory, or a storage device such as a hard disk or an optical disk. Further, the storage circuit 140 stores an ambulance information table 141, a hospital information table 142, and a control program 143.

The emergency squad information table 141 has a list of emergency squads. For example, if there is one fire station in a city, a list of emergency services in the city and neighboring cities is managed.

As shown in FIG. 4, the emergency team information table 141 includes emergency team identification information, communication destination information, current position information, situation information, etc. for each emergency team.

The emergency team identification information is unique information that uniquely identifies an emergency team. “E1” to “En” shown in FIG. 4 are unique IDs of emergency teams. The ambulance identification information is updated based on communication between the transport plan generation device 100 and the ambulance terminal 200.

The communication destination information is information for communicating with the emergency team terminal 200, and includes, for example, an IP (Internet Protocol) address and a MAC (Media Access Control) address. “E1A” to “EnA” shown in FIG. 4 are communication destination information for communicating with the emergency team terminal 200, respectively. Communication destination information is updated based on communication performed between transport plan generation device 100 and emergency team terminal 200.

The current location information is information representing the current location of the ambulance terminal 200, and is obtained, for example, by the GPS (Global Positioning System), Wi-Fi (Wireless Fidelity) function, etc. provided in the ambulance terminal 200. “E1L” to “EnL” shown in FIG. 4 each represent the current position of the emergency team terminal 200. The current location information is updated based on communication performed between the transport plan generation device 100 and the emergency team terminal 200.

The situation information is information representing the situation of the emergency team, and includes "on standby", "moving to the scene", "on the spot", "moving to the hospital", and the like. The situation information is changed, for example, by an operation of the emergency team using the emergency team terminal 200. The situation information is updated based on communication performed between the transport plan generation device 100 and the emergency team terminal 200.

The hospital information table 142 shown in FIG. 3 has a list of hospitals. For example, if there is one fire station in a city, a list of hospitals in the city and neighboring cities is managed.

As shown in FIG. 5, the hospital information table 142 includes hospital identification information, communication destination information, remaining acceptance information, location information, jurisdiction area information, clinical department information, etc. for each hospital.

Hospital identification information is unique information that uniquely identifies a hospital. “H1” to “Hm” shown in FIG. 5 are unique IDs of hospitals, respectively. The hospital identification information is updated based on communication performed between the transport plan generation device 100 and the hospital terminal 300.

The communication destination information is information for communicating with the hospital terminal 300, and includes, for example, an IP address and a MAC address. “H1” to “Hm” shown in FIG. 5 each represent a communication destination for communicating with the hospital terminal 300. The communication destination information is updated based on communication performed between the transport plan generation device 100 and the hospital terminal 300.

The remaining acceptability information is information representing the remaining number of patients that the hospital can accept and the remaining resources. The remaining acceptability information is updated based on communication performed between the transport plan generation device 100 and the hospital terminal 300. For example, "8 people (10%)" shown in FIG. 4 represents the remaining number of patients and remaining resources that the hospital "H1" can accept.

The location information is information representing the location of the hospital, and includes, for example, an address. “H1L” to “HmL” shown in FIG. 5 each represent the address of the hospital. The position information is updated based on communication performed between the transport plan generation device 100 and the hospital terminal 300.

Jurisdiction area information is information representing an area under the jurisdiction of a fire department. For example, hospitals "H1", "H2", and "Hm" belong to the jurisdictional area "HJ12", and hospitals "H3" and "H4" belong to the jurisdictional area "HJ34".

The clinical department information is information representing the medical department of the hospital. Medical departments include internal medicine, surgery, orthopedics, radiology, obstetrics and gynecology, etc.

The control program 143 shown in FIG. 3 is a program executed by the processing circuit 150.

The processing circuit 150 controls the transport plan generating device 100 as a whole by controlling each component of the transport plan generating device 100. The processing circuit 150 functions as an information acquisition function 151, a hospital information acquisition function 152, a search function 153, and a provision function 154 by executing the control program 143 stored in the storage circuit 140. Note that the processing circuit 150 may include a plurality of independent processors, and each processor executes the control program 143 to perform an information acquisition function 151, a hospital information acquisition function 152, a search function 153, and a provision function 154. may be realized.

Note that the word "processor" refers to, for example, a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an Application Specific Integrated Circuit (ASIC), a programmable logic device (for example, a simple programmable logic Refers to circuits such as simple programmable logic devices (SPLDs), complex programmable logic devices (CPLDs), and field programmable gate arrays (FPGAs). A processor realizes its functions by reading and executing a program stored in a memory circuit. Note that instead of storing the program in the storage circuit, the program may be directly incorporated into the circuit of the processor. In this case, the processor realizes its functions by reading and executing a program built into the circuit. Note that the processors of each embodiment are not limited to being configured as a single circuit for each processor, but may be configured as a single processor by combining multiple independent circuits to realize its functions. .

The processing operations performed by the transport plan generation device 100 configured as above will be explained. The processing carried out by the transport plan generation device 100 is a dispatch request process in which an emergency team is requested to be dispatched to the scene where a person in need of rescue is present, and a hospital that will accept the person in need of rescue is provided to the emergency team that has requested dispatch. It can be broadly divided into the acceptance destination determination process.

The dispatch request process will be explained with reference to FIG. For example, when a person in need of rescue has some kind of seizure, the person in need of rescue uses the mobile terminal 400 to report to the transport plan generation device 100 of the notification center (step S101).

The information acquisition function 151 of the transport plan generation device 100 acquires rescue recipient information (step S102). The information on the person in need of rescue includes the address (location) of the scene, the name of the informer, contact information, time of report, etc. Specifically, the information acquisition function 151 uses voice recognition to extract and acquire the address (location) of the scene, the name of the informer, contact information, etc. from the conversation between the operator of the reporting center and the informer. The information acquisition function 151 also acquires the time when the report was received at the report center (report time). Note that the site address may be acquired based on information (base station information) representing the calling location of the mobile terminal 400 instead of being extracted from the conversation between the operator and the informer.

The information acquisition function 151 associates the person in need of rescue information acquired in step S102 with the notification ID to generate the person in need of rescue information table 144 (step S103). For example, as shown in FIG. 7, the information acquisition function 151 includes the report ID "1405", the location of the scene "XX-chome, XXX-city, XXX-city, XXX-prefecture, XXX-Apartment XXX", and the name of the informer "A". A rescue person information table 144 having information such as , informer contact information "090-*****-****" and reporting time "16:00" is generated.

In step S104, the information acquisition function 151 selects an ambulance closest to the scene from among the waiting ambulances based on the rescue-required person information table 144 and the ambulance information table 141 stored in the storage circuit 140. Identify. Specifically, among the emergency teams included in the emergency team information table 141 shown in FIG. Identify. Note that "close" here includes the concept of being close in a straight line distance as well as being close in terms of road traffic (early in terms of time). The information acquisition function 151 identifies the nearest ambulance in terms of distance or the closest (earliest in time) in terms of road traffic, according to a search method set in advance or selected by the user. The information acquisition function 151 transmits a message requesting dispatch to the scene (hereinafter referred to as a dispatch request message) to the communication destination "E4A" of the identified emergency squad "E4". The dispatch request message includes the rescue recipient information included in the rescue recipient information table 144. In this case, the emergency squad terminal 200 of the emergency squad "E4" receives a dispatch request message, and the emergency squad "E4" receives the location of the scene included in the rescue person information (here, "XX prefecture, XX city, XX"). ○-chome, ○○, ○○ apartment, ○○'') and start moving to the site.

At this time, the ambulance team "E4" uses the ambulance terminal 200 to change the status information included in its own ambulance information from "on standby" to "moving to the scene" and also changes the current location information. and transmits the changed emergency team information to the transport plan generation device 100. Then, the information acquisition function 151 of the transport plan generation device 100 that has received the changed emergency team information updates the emergency team information table 141, as shown in FIG. 8.
With the above steps, the dispatch request process ends.

Next, the acceptance destination determination process will be explained. The hospital information acquisition function 152 of the transport plan generation device 100 updates the hospital information table 142 based on communication performed with the hospital terminal 300. For example, as shown in FIG. 9, the hospital terminal 300 corresponding to each of the plurality of hospitals (“H1” to “Hm”) transmits hospital information including its own remaining acceptance information to the transport plan generation device 100 ( Step S201). The hospital information acquisition function 152 receives hospital information transmitted from each of the plurality of hospital terminals 300, and updates the hospital information table 142 (step S202). Note that the communication with the hospital terminal 30 may be performed either periodically or at the timing when hospital information is changed in the hospital terminal 300. As a result, the transport plan generation device 100 manages the remaining acceptance information of the hospital.

As shown in FIG. 10, the search function 153 of the transport plan generation device 100 searches for a hospital that accepts the person in need of rescue based on the person in need of rescue information table 144 and the hospital information table 142 stored in the storage circuit 140. is determined (step S301). Specifically, by referring to the remaining acceptance information and location information included in the hospital information table 142 shown in FIG. Search for. For example, if the location information "H4L" of the hospital "H4" is the closest to the site location and can accept at the moment (one person can be accepted), then the hospital "H4" is determined as the acceptance destination. Note that "close" here includes the concept of being close in a straight line distance as well as being close in terms of road traffic (early in terms of time). The information acquisition function 151 specifies the closest hospital in terms of distance or the closest hospital in terms of road traffic (earliest in time) according to a search method set in advance or selected by the user.

The providing function 154 generates transport plan information by including the hospital information of the hospital determined in step S301 (here, "H4") in the rescue-required person table 144 generated in the dispatch request process (step S302). ). In this case, the rescue recipient table 144 shown in FIG. 7 is updated as shown in FIG. 11.

Then, the providing function 154 notifies the determined receiving hospital by transmitting the generated transportation plan information to the emergency team that requested dispatch to the scene in the dispatch request process (step S303). Specifically, the provision function 154 sends a message (hereinafter referred to as a reception reservation) to the communication destination "E4A" of the emergency team "E4" specified in the dispatch request process, notifying the hospital "H4" that accepts the person in need of rescue. Message). The destination reservation message includes transportation plan information. In this case, the ambulance terminal 200 of the ambulance team "E4" receives the reception reservation message, and the ambulance team "E4" can refer to the information of the reception hospital "H4".

Further, the providing function 154 communicates with the hospital terminal 300 of the determined hospital "H4" and transmits a reservation message including the ambulance information of the emergency squad "E4" to the hospital terminal 300. Upon receiving the reservation message, the hospital terminal 300 performs reservation processing based on the ambulance information included in the reservation message. As a result, the hospital "H4" can refer to the information of the ambulance team "E4" and learn the information about the ambulance team "E4" that will arrive soon. Note that if this reservation process is performed normally (if the reservation is made), the remaining acceptance information at the hospital "H4" is changed (decreased by one person). Further, in this case, the hospital information table 142 shown in FIG. 5 is also updated as shown in FIG. 12.

Further, the hospital terminal 300 of the hospital “H4” may transmit a reservation completion message to the transport plan generation device 100. In this case, the provision function 154 of the transport plan generation device 100 transmits a message that the reservation for acceptance at the hospital "H4" has been completed to the ambulance terminal 200 of the ambulance team "E4". In this case, the reservation completion message is received on the ambulance terminal 200 of the ambulance team "E4", and it can be confirmed that the reservation has been completed. Note that the providing function 154 may notify the ambulance terminal 200 of the transport plan information after the reservation completion message is received.
With the above steps, the acceptance destination determination process ends.

As described above, according to the first embodiment, based on the location of the scene obtained by the report from the informer, the emergency team near the scene is requested to dispatch, and the hospital that can accept the emergency team near the scene information can be provided to emergency services. Since it is possible to determine and make reservations for the hospital that will receive the person in need of rescue before the emergency team arrives at the scene, it is possible to prevent the person in need of rescue from being shuffled around and to prevent delays in transporting the person in need of rescue.

In the above embodiment, an example was explained in which the transport plan generation device 100 makes a hospital reservation by communicating with the hospital terminal 300. The terminal 200 may communicate with the hospital terminal 300 to make a hospital reservation.

Further, in the embodiment described above, the search function 153 of the transport plan generation device 100 is capable of accepting a person in need of rescue by considering the location of the scene and the location (address) of the hospital recorded in the hospital information table 142. The search is for hospitals such as, but not limited to. For example, the search function 153 may further consider the jurisdiction area recorded in the hospital information table 142 to search for a hospital that can accept the person in need of rescue.

(First modification)
In the first embodiment, the search function 153 of the transport plan generation device 100 determines the hospital "H4" closest to the site among the hospitals that can accept the patient as the receiving hospital, but the invention is not limited to this. For example, as shown in FIG. 13, the search function 153 of the transport plan generation device 100 inquires about a predetermined number of hospitals that are close to the site among hospitals that can accept patients (step S211), and receives hospital information (step S211). S212), a predetermined number of hospitals may be searched as candidates for receiving the patient, and this may be provided to the emergency terminal 200 to allow the emergency team to select a hospital for receiving the patient.

Specifically, the search function 153 of the transport plan generation device 100 refers to the remaining acceptable information and position information included in the hospital information table 142 shown in FIG. Search for a predetermined number (for example, three) of hospitals near the location of the indicated site.

For example, if hospitals "H4", "H3", and "H2" are identified by the search function 153 in order of proximity to the location of the scene (step S301), the provision function 154 stores the request information generated in the dispatch request process. Transport plan information is generated by including hospital information of hospitals "H4", "H3", and "H2" in the rescuer table 144 (step S302).

The provision function 154 notifies the "candidate" receiving location (temporary reservation message) by transmitting the generated transportation plan information to the emergency terminal 20 of the emergency team (for example, "E4") that has requested dispatch to the scene. (Step S303). The transport plan information includes candidate hospitals "H4", "H3", and "H2" for acceptance, and the candidate hospitals are displayed on the emergency terminal 20.

In addition, the provision function 154 communicates with the hospital terminals 300 of the hospitals "H4", "H3", and "H2" that have been notified as "candidates" for the acceptance site, and includes information on the ambulance team "E4". Send a tentative reservation message. Upon receiving the provisional reservation message, each hospital terminal 300 performs provisional reservation processing based on the ambulance information included in the provisional reservation message. Note that if this provisional reservation process is performed normally (if a provisional reservation is made), the remaining acceptance information for hospitals "H4", "H3", and "H2" will be changed (decreased by one person). Further, in this case, the hospital information table 142 shown in FIG. 5 is also updated in the same way.

On the other hand, the ambulance team "E4" selects and determines a receiving hospital (for example, "H4") from among the receiving hospital candidates displayed on the ambulance terminal 200. When this decision is made, the unselected hospitals ("H3", "H2") are excluded from the hospital candidates ("H4", "H3", "H2") included in the transport plan information. Update transportation plan information.

Furthermore, the emergency terminal 200 transmits a main reservation message to the transport plan generation device 100 to notify that the receiving hospital has been determined. The provision function 154 of the transport plan generation device 100 updates the rescue recipient table 144 based on the main reservation message received from the emergency terminal 200. Furthermore, the emergency terminal 200 communicates with each hospital terminal 300 that has processed the provisional reservation based on the main reservation message, and performs the main reservation processing.

For example, the providing function 154 transmits a regular reservation message including the emergency squad information of the ambulance squad "E4" to the hospital terminal 300 of the hospital "H4" determined by the ambulance squad "E4". The hospital terminal 300 that has received the main reservation message performs the main reservation process based on the ambulance information included in the main reservation message. As a result, the hospital "H4" can refer to the information of the ambulance team "E4" and learn the information about the ambulance team "E4" that will arrive soon.

On the other hand, the provision function 154 sends a provisional reservation cancellation message to the hospital terminals 300 of hospitals "H3" and "H2" that were not selected by the emergency team "E4". The hospital terminal 300 that received the provisional reservation cancellation message returns the remaining acceptability information that was changed in the previous provisional reservation processing to its original state (increases by one person). As a result, the tentative reservation is canceled.

In this way, a predetermined number of hospitals that can accept the patient and are close to the site may be provided to the emergency terminal 200 as candidates for receiving the patient, and the emergency team may select a hospital for accepting the patient. In addition, in the above modification, an example was explained in which the hospital terminal 200 notifies the transport plan generation device 100 of the selected receiving hospital to perform the main reservation process and the temporary reservation cancellation process for the receiving hospital. The above-mentioned main reservation processing and provisional reservation may be canceled by the hospital terminal 200 communicating with the hospital terminal 300 of each hospital notified as a candidate for acceptance.

(Second modification)
In the first embodiment, an example has been described in which a hospital that can accept a person in need of rescue is specified based on the remaining acceptance information included in the hospital information table 142, but the present invention is not limited to this. When the information acquisition function 151 acquires the rescue recipient information, the hospital information acquisition function 152 of the transport plan generation device 100 may inquire whether or not the rescue recipient can be accepted, starting from the hospital terminal 300 of the hospital closest to the site. .

(Second embodiment)
In the first embodiment, an example was explained in which a hospital to accept a person in need of rescue is determined based on the location of the person in need of rescue, but in the second embodiment, the condition of the person in need of rescue (symptoms and Based on at least one of information that identifies the person in need of rescue (such as condition, etc.) and information that identifies the recipient of the person in need of rescue (name of the hospital/department (family hospital/department), chronic illness, past medical history, etc.) An example of determining an appropriate hospital to accept a person in need of rescue will be explained.

Specifically, the information acquisition function 151 of the transport plan generation device 100 transmits a message requesting dispatch to the scene (dispatch request message) to the emergency team closest to the scene, and then, as shown in FIG. 14, Information (URL, etc.) indicating the download destination of the application for obtaining information on persons in need of rescue is sent to the mobile terminal 400, which is the previously acquired contact information of the informant, with the notification ID included in the persons in need of rescue information table 144 (see FIG. 1405) and requests downloading of the application (step S401). Applications for acquiring information on people in need of rescue include, for example, programs that acquire information that identifies the condition of people in need of rescue (symptoms, condition, etc.), information that specifies where the person in need of rescue is accepted (name of the hospital they attend, etc.)・Contains format data for entering medical department (family hospital/department), chronic disease, past medical history, etc.

The informer operates the mobile terminal 400 to download an application for acquiring information on the person in need of rescue (step S402). Further, the informer executes the application downloaded to the mobile terminal 400 and obtains rescue recipient information (step S403).

For example, based on a program included in the executed application, the informer photographs the person in need of rescue using the mobile terminal 400. Note that the captured image may be either a moving image or a still image. Furthermore, in addition to or instead of the photographed image, the mobile terminal 400 may acquire biological information such as the pulse, blood pressure, and body temperature of the person in need of rescue. Furthermore, the mobile terminal 400 diagnoses the person in need of rescue based on the photographed image and biological information of the person in need of rescue, and outputs the results. The captured image, biological information, and diagnosis result thus obtained are information for identifying the condition of the person in need of rescue, and are also used as information on the person in need of rescue.

Further, for example, based on the format data included in the executed application, the informer may perform an operation to fill in the hospital/medical department where the person in need of rescue is attending, chronic illness/past history, etc. using the mobile terminal 400. I do. These pieces of information are information for identifying the receiving place of the person in need of rescue, and are also used as information on the person in need of rescue.

The mobile terminal 400 transmits the information on the person in need of rescue acquired in this way to the transport plan generation device 100 together with the report ID ("1405" shown in FIG. 7) notified with the application (step S404). .

The information acquisition function 151 of the transportation plan generation device 100 receives the rescuer information from the mobile terminal 400 (step S405), and includes the rescuer information in the rescuer information table 144, thereby generating the rescuer information. The table 144 is updated (step S406). In addition, the information acquisition function 151 requests information that identifies the condition (symptoms, condition, etc.) of the person in need of rescue and the place where the person in need of rescue is accepted, which is extracted by voice recognition from the conversation between the operator of the reporting center and the caller. The rescuer information may be included in the rescuer information table 144.

In the acceptance destination determination process, the search function 153 of the transport plan generation device 100 uses the rescue recipient information table 144 updated by the above process and the hospital information table 142 stored in the storage circuit 140 to Decide which hospital will accept the person in need of rescue. For example, the search function 153 searches the hospital information table 142 for a hospital that has a medical department that corresponds to the condition (symptoms and condition) of the person in need of rescue, and refers to the remaining acceptance information of the corresponding hospital. Decide which hospital will accept the patient. In addition, the search function 153 searches the hospital information table 142 for a hospital that corresponds to the acceptance destination of the person in need of rescue notified from the mobile terminal 400, and refers to the remaining acceptance information of the corresponding hospital. Decide on a hospital as the host.

After that, similarly to the first embodiment, the providing function 154 generates transportation plan information and updates the rescue recipient table 144. Further, the providing function 154 notifies the determined receiving hospital by transmitting the generated transportation plan information to the emergency team that has requested dispatch to the scene. Note that the providing function 154 may include information for identifying the condition of the person in need of rescue notified from the mobile terminal 400 (photographed image of the person in need of rescue, biometric information) in the transportation plan information. As a result, the emergency team can check and understand the condition of the person in need of rescue before arriving at the scene, and can efficiently treat the person in need of rescue after arriving at the scene.

Furthermore, the provision function 154 communicates with the hospital terminal 300 of the determined hospital and transmits to the hospital terminal 300 a reservation message containing the information of the emergency team requested to be dispatched to the scene. Upon receiving the reservation message, the hospital terminal 300 performs reservation processing based on the ambulance information included in the reservation message. As a result, the hospital that has been determined to receive the patient can refer to the information of the ambulance crew and learn about the ambulance crew that will arrive at the hospital in the future. Note that if this reservation process is performed normally (if the reservation is made), the remaining admission information at the hospital is changed (decreased by one person). Further, in this case, the hospital information table 142 shown in FIG. 5 is also updated as shown in FIG. 12.

As described above, according to the second embodiment, information that identifies the condition of the person in need of rescue and information that specifies the receiving location of the person in need of rescue is acquired before the emergency team arrives at the scene. Based on the information obtained, it is possible to determine and make reservations for the appropriate hospital to accept the person in need of rescue. Thereby, it is possible to prevent the person in need of rescue from being shuffled around and to prevent delays in transporting the person in need of rescue.

Note that if the application has already been downloaded to the mobile terminal 400 at the time of reporting in the above embodiment, the process of downloading the application described in the above embodiment may be omitted. In this case, the mobile terminal 400 executes the application according to the operation of the caller at the time of reporting, acquires information identifying the condition of the person in need of rescue and information identifying the place where the person in need of rescue is accepted, and combines the acquired information with , the address (position) of the scene, the name of the informant, the contact information, the time of the report, etc. are transmitted to the transport plan generation device 100 as rescue person information.

In addition, in the above embodiment, in order to determine the hospital that accepts the person in need of rescue, information that identifies the condition of the person in need of rescue and information that specifies the place where the person in need of rescue is accepted is obtained. After determining the receiving place of the person and sending a dispatch request message to the emergency team, information identifying the condition of the person in need of rescue and information specifying the receiving place of the person in need of rescue may be acquired. In this case, the providing function 154 transmits the acquired information as additional transportation plan information to the emergency team moving to the scene. As a result, the emergency team can check and understand the condition of the person in need of rescue before arriving at the scene, and can efficiently treat the person in need of rescue after arriving at the scene.

(Third embodiment)
In the first and second embodiments, the case where there is one person in need of rescue was explained, but in the third embodiment, there are multiple people in need of rescue (for example, three people), and the condition of each person in need of rescue is explained. Examples of cases where the symptoms and conditions are different will be explained.

In the dispatch request process shown in FIG. 6, the information acquisition function 151 of the transport plan generation device 100 acquires information on the person in need of rescue (step S102). For example, the information acquisition function 151 acquires the address (position) of the scene, the name of the informer, the contact information, the time of report, etc. as information on the person in need of rescue. The information acquisition function 151 acquires information based on the content of the conversation between the operator of the reporting center and the informer, and the communication performed with the mobile terminal 400. Specifically, the information acquisition function 151 extracts and acquires the address (location) of the scene, the name of the informer, contact information, etc. from the conversation between the operator of the reporting center and the informer using voice recognition. The information acquisition function 151 also acquires the time when the report was received at the report center (report time). Note that the site address may be acquired based on information (base station information) representing the transmission location of the mobile terminal 400 instead of being extracted from the conversation between the operator and the informer.

In addition, the information acquisition function 151 acquires information (symptoms, condition, etc.). For example, the informer uses the built-in camera of the mobile terminal 400 to photograph each of the plurality of persons in need of rescue, and obtains each photographed image. Furthermore, in addition to or in place of the photographed images, biological information such as the pulse, blood pressure, and body temperature of each person requiring rescue may be acquired. Furthermore, the mobile terminal 400 may diagnose the person in need of rescue based on the photographed image and biological information of the person in need of rescue, and output the results. The photographic images, biological information, and diagnostic results obtained for each of the plurality of persons in need of rescue in this way are information for identifying the condition of the person in need of rescue, and this is also used as information on the persons in need of rescue. Note that the information acquisition function 151 may use the condition (symptoms, condition, etc.) of the person in need of rescue, which is extracted from the conversation between the operator of the reporting center and the caller, as information on the person in need of rescue.

Furthermore, the information acquisition function 151 may assign a transport priority to each person in need of rescue based on information identifying the condition of each person in need of rescue, and use this as information on the person in need of rescue. For example, if there are three people in need of rescue, the condition (symptoms and condition) of each person in need of rescue is quantitatively identified and prioritized (1st to 3rd) in descending order of the condition of the person in need of rescue. may be used as information on the person in need of rescue.

Then, the information acquisition function 151 associates the acquired information on the person in need of rescue with the report ID and generates the person in need of rescue information table 144 (step S103).

In the acceptance destination determination process, the search function 153 of the transport plan generation device 100 determines which person requires rescue based on the rescue recipient information table 144 generated by the above process and the hospital information table 142 stored in the storage circuit 140. Decide which hospital will accept the patient. For example, the search function 153 determines and makes reservations for hospitals that accept rescue recipients in descending order of severity according to the priority order included in the rescue recipient information table 144. Note that the process described in the first or second embodiment may be performed to determine the hospital that will accept each person requiring rescue and to make a reservation.

Here, in the case where there are multiple people in need of rescue, if the hospitals serving as acceptance sites differ among the people in need of rescue, transportation efficiency will deteriorate. Therefore, when the search function 153 determines the hospital that will accept the person in need of rescue in step S301, it is better to preferentially select a hospital that can accept all the people in need of rescue (here, three people).

When the search function 153 determines that there is no hospital that can accept all rescue recipients, it searches for other hospitals that can accept rescue recipients whose reservations have not yet been completed. Furthermore, in this case, an additional emergency team may be requested that is on standby in addition to the emergency team currently moving to the scene. In this case, as described in the first embodiment, the information acquisition function 151 determines which rescuers are on standby based on the rescue recipient information table 144 and the rescue team information table 141 stored in the storage circuit 140. The emergency squad closest to the scene is identified from among the squads, and a dispatch request message is sent to the emergency squad terminal 200 of the identified ambulance squad.

After that, similarly to the first embodiment, the providing function 154 generates transportation plan information and updates the rescue recipient table 144. Further, the providing function 154 notifies the determined receiving hospital by transmitting transport plan information for each person requiring rescue to the emergency team that has requested dispatch to the scene. Note that the providing function 154 may include information for identifying the condition of each person requiring rescue (photographed image of the person requiring rescue, biometric information) and priority order notified from the mobile terminal 400 in the transportation plan information. This allows emergency teams to check and understand the condition of multiple people in need of rescue before arriving at the scene, allowing them to efficiently treat people in need of rescue after arriving at the scene. It is possible to prevent mistakes due to mix-ups. Furthermore, even if there are multiple people in need of rescue, by referring to the priority order, it is easy to determine which person should be treated first.

As described above, according to the third embodiment, even when there are multiple people in need of rescue, transport is carried out based on information identifying the condition of the people in need of rescue, which is obtained before the arrival of the rescue team at the scene. Priorities can be assigned, and based on the priorities, it is possible to decide and make a reservation for a hospital that will accept a person in need of rescue. In addition, since the transportation plan information includes information that identifies the condition of each of the multiple rescue recipients (photographed images of the rescue recipient, biological information), treatment for the rescue recipient after arriving at the scene is determined. In addition to efficiently carrying out rescue operations, it is possible to prevent mistakes in mistaking people in need of rescue. This prevents the person in need of rescue from being shuffled around and prevents delays in transporting the person in need of rescue.

(Fourth embodiment)
In the fourth embodiment, instead of the application for acquiring information on persons in need of rescue described in the second and third embodiments, an unmanned mobile object such as a drone is used to provide information on rescuers until the emergency team arrives at the scene. Next, an example will be described in which information identifying the condition of a person in need of rescue at a site is acquired by an unmanned mobile object.

As described in the first embodiment, in the dispatch request process shown in FIG. , sends a dispatch request message to the emergency squad terminal 200 of the specified emergency squad. At this time, the information acquisition function 151 also sets the address of the site for the unmanned mobile object, and moves the unmanned mobile object toward the site. Further, the information acquisition function 151 sets the report ID (“1405” shown in FIG. 7) included in the rescue person information table 144 to the unmanned mobile object.

When the unmanned vehicle arrives at the scene, it acquires information that identifies the condition (symptoms and condition) of the person in need of rescue. Here, the unmanned moving object has a configuration for acquiring the information, including a photographing unit (camera) that takes images, a biological information measuring unit that measures biological information such as pulse, blood pressure, and body temperature, and a photographed image of the person in need of rescue. The system is equipped with a diagnosis support unit that diagnoses the person in need of rescue based on biometric information and outputs the results. Photographed images acquired by the imaging unit, biological information acquired by the biological information measurement unit, and diagnosis results acquired by the diagnosis support unit are information that identifies the condition of the person in need of rescue, and are used as information on the person in need of rescue. used. The unmanned mobile object transmits the information on the person in need of rescue acquired in this way to the transportation plan generation device 100 together with the set notification ID ("1405" shown in FIG. 7) (step S404).

The information acquisition function 151 of the transport plan generation device 100 updates the rescuer information table 144 based on the rescuer information received from the unmanned moving object. After that, as explained in the second embodiment, the search function 153 determines the hospital that will accept the person in need of rescue, and the providing function 154 will send the emergency team that has requested dispatch to the scene to the hospital that will accept the person in need of rescue. Notify.

In addition, the unmanned vehicle may further include, for example, emergency supplies, a display device, and the like. Emergency supplies include AEDs (Automated External Defibrillators) and first aid kits. AEDs are used for rescuers who may be suffering from cardiopulmonary arrest. The first aid kit contains wrapping bags and gauze for first aid. The display device is a terminal that lectures the caller on how to use emergency supplies and first aid measures until the emergency team arrives at the scene. For example, the display terminal can output a video for explaining the operation of an AED, or a video for explaining a method for stopping bleeding, etc., by a simple operation by the informant.

As described above, according to the fourth embodiment, the unmanned moving object acquires information identifying the condition of the person in need of rescue before the emergency team arrives at the scene, and based on the acquired information, Determine and make reservations for appropriate hospitals to accept rescuers. Thereby, it is possible to prevent the person in need of rescue from being shuffled around and to prevent delays in transporting the person in need of rescue.

Note that the above embodiment can be implemented even when there are multiple rescuers as described in the third embodiment. In this case, the transportation plan generation device 100 is configured to generate a transport plan when the number of rescuers notified by the caller and the number of rescuers included in the photographed image are different (if the rescuer is the caller himself or If the caller is among the rescuers, the number of people in need of rescue included in the captured image does not satisfy the condition that the number of people in need of rescue is the same as the number of people in need of rescue notified by the caller. If the person in need of rescue is not the person making the call or the person in need of rescue is not included in the number of people in need of rescue, the number of people in need of rescue included in the captured image is one more than the number of people in need of rescue notified by the caller. (when the above conditions are not met), it is preferable to perform the acceptance destination determination processing described in the first to third embodiments based on the number of people in need of rescue included in the photographed image.

As described above, according to each embodiment, delays in transporting a person in need of rescue can be prevented.

Note that each component of each device illustrated in each embodiment is functionally conceptual, and does not necessarily need to be physically configured as illustrated. In other words, the specific form of distributing and integrating each device is not limited to what is shown in the diagram, and all or part of the devices can be functionally or physically distributed or integrated in arbitrary units depending on various loads and usage conditions. Can be integrated and configured. Furthermore, all or any part of each processing function performed by each device can be realized by a CPU and a program that is analyzed and executed by the CPU, or can be realized as hardware using wired logic.

Further, the methods described in each embodiment can be realized by executing a control program prepared in advance on a computer such as a personal computer or a workstation. This control program can be distributed via a network such as the Internet. Further, this control program is recorded on a computer-readable non-temporary recording medium such as a hard disk, flexible disk (FD), CD-ROM, MO, DVD, etc., and is executed by being read from the recording medium by the computer. You can also do that.

Although embodiments of the present invention have been described, the embodiments of the present invention are presented as examples and are not intended to limit the scope of the invention. The embodiments of the present invention can be implemented in various other forms, and various omissions, substitutions, and changes can be made without departing from the gist of the invention. The embodiments of the present invention and their modifications are included within the scope and gist of the invention as well as within the scope of the invention described in the claims and its equivalents.

100 Transport plan generation device 150 Processing circuit 151 Information acquisition function 152 Hospital information acquisition function 153 Search function 154 Providing function

Claims (15)

an information acquisition unit that acquires information on a person in need of rescue regarding at least one of the location of the person in need of rescue and the person in need of rescue;
a hospital information acquisition unit that acquires hospital information including acceptance information that identifies whether or not the patient can be admitted to the hospital;
a search unit that searches for a hospital that accepts the person in need of rescue based on the information on the person in need of rescue acquired by the information acquisition unit and the hospital information acquired by the hospital information acquisition unit;
a providing unit that provides transport plan information corresponding to the hospital searched by the search unit to an emergency team;
The information acquisition unit is configured to provide an application for acquiring information on the person requiring rescue to a caller at the scene before the emergency team arrives at the scene where the person in need of rescue is present , and execute the application to obtain the information on the person requiring rescue. obtaining the information on the person in need of rescue obtained through the operation of the informant;
Transport plan generation device. The information acquisition unit includes information on the person in need of rescue including information indicating the location of the scene where the person in need of rescue is located, information on the location of the emergency team, and information identifying whether or not the ambulance team can move to the scene. information on the emergency services, including information on the scene, and provides a dispatch request message requesting dispatch to the scene to the nearest emergency squad to the scene among those capable of moving to the scene;
The transport plan generation device according to claim 1. The information acquisition unit acquires the person in need of rescue information including information representing the location of the person in need of rescue,
The hospital information acquisition unit acquires the hospital information including information representing the location of the hospital along with the acceptance information,
The search unit searches for a hospital close to the scene from among hospitals that can accept the person based on the information on the person in need of rescue and the hospital information.
The transport plan generation device according to claim 1 or 2. The search unit searches for a hospital closest to the site from among the hospitals that can accept the hospital;
The provision unit performs a reservation process for the hospital searched by the search unit.
The transport plan generation device according to claim 3. The search unit searches for a plurality of hospitals from among the acceptable hospitals in order of proximity to the site,
The providing unit provides transport plan information corresponding to the plurality of hospitals searched by the search unit to an emergency team, and causes the emergency team to select a hospital that will receive the person in need of rescue.
The transport plan generation device according to claim 3. The provision unit performs a provisional reservation process for the plurality of hospitals searched by the search unit, and makes a permanent reservation for the receiving hospital selected from the plurality of hospitals by the emergency team. processing, and canceling the provisional reservation for a hospital that was not selected from the plurality of hospitals by the emergency team;
The transport plan generation device according to claim 5. The information acquisition unit acquires the rescue-required person information including at least one of information identifying the condition of the rescue-required person and information specifying a receiving place of the rescue-required person,
The hospital information acquisition unit acquires the hospital information including information representing the location of the hospital along with the acceptance information,
The search unit searches for a hospital that corresponds to at least one of the condition of the person in need of rescue and the place where the person in need of rescue is accepted, from among hospitals that can accept the person in need of rescue, based on the information on the person in need of rescue and the hospital information. do,
The transport plan generation device according to claim 1 or 2. The search unit searches for one hospital from among the acceptable hospitals;
The provision unit performs a reservation process for the one hospital searched by the search unit.
The transport plan generation device according to claim 7. The search unit searches for a plurality of hospitals from among the acceptable hospitals;
The providing unit provides transport plan information corresponding to the plurality of hospitals searched by the search unit to an emergency team, and causes the emergency team to select a hospital that will receive the person in need of rescue.
The transport plan generation device according to claim 7. The provision unit performs a provisional reservation process for the plurality of hospitals searched by the search unit, and makes a permanent reservation for the receiving hospital selected from the plurality of hospitals by the emergency team. processing, and canceling the provisional reservation for a hospital that was not selected from the plurality of hospitals by the emergency team;
The transport plan generation device according to claim 9. When there are a plurality of persons in need of rescue, the information acquisition unit acquires, for each of the plurality of persons in need of rescue, the person in need of rescue information including information identifying the condition of the person in need of rescue; Based on the condition of the person in need of rescue obtained for each person, assigning priority for transportation to each of the plurality of people in need of rescue,
The search unit searches for the receiving hospital from among the hospitals that can accept the patient based on the priority order.
The transport plan generation device according to claim 1 or 2. The information acquisition unit moves an unmanned mobile object that acquires the information on the person in need of rescue to a site, and acquires the information on the person in need of rescue obtained by the unmanned mobile object that has arrived at the site.
The transport plan generation device according to claim 1 or 2. The information acquisition unit is configured to acquire at least one of a photographed image of the person in need of rescue, biological information, and a diagnosis result based on at least one of the photographed image and the biological information, and information for identifying the condition of the person in need of rescue. Obtained as rescue person information,
The transport plan generation device according to claim 12. Emergency team terminal and
A transport plan generation device capable of communicating with the emergency team terminal,
The transport plan generation device includes an information acquisition unit that acquires information about the person in need of rescue regarding at least one of the location of the person in need of rescue and the person in need of rescue, and acceptance information that identifies whether or not the person can be admitted to the hospital. A hospital information acquisition unit that acquires hospital information; a reception place for the person in need of rescue based on the information on the person in need of rescue acquired by the information acquisition unit; and the hospital information acquired by the hospital information acquisition unit. a search unit that searches for a hospital, and a provision unit that provides an emergency team with transport plan information corresponding to the hospital searched by the search unit,
The information acquisition unit is configured to provide an application for acquiring information on the person requiring rescue to a caller at the scene before the emergency team arrives at the scene where the person in need of rescue is present , and execute the application to obtain the information on the person requiring rescue. obtaining the information on the person in need of rescue obtained through the operation of the informant;
Transport plan generation system. an information acquisition step of acquiring rescuer information regarding at least one of the location of the scene where the rescuer is located and the rescuer;
a hospital information acquisition step of acquiring hospital information including acceptance information for identifying acceptance into the hospital;
a search step of searching for a hospital that accepts the person in need of rescue based on the information on the person in need of rescue acquired in the information acquisition step and the hospital information acquired in the hospital information acquisition step;
a providing step of providing transport plan information corresponding to the hospital searched in the search step to an emergency team;
In the information acquisition step, before the emergency team arrives at the scene where the person in need of rescue is located, an application for acquiring information on the person in need of rescue is provided to the caller at the scene , and the caller executes the application to obtain the information on the person in need of rescue. obtaining the information on the person in need of rescue obtained through the operation of the informant;
A transport plan generation method executed by each function of a computer.

Images