Triage management system, triage management method and program
The triage management system improves situational awareness by creating electronic medical records and outputting categorized lists, addressing the challenge of managing triage efficiently during emergencies.
Patent Information
- Application Number
- JP2023216308
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-12-21
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2043-12-21
AI Technical Summary
Existing triage management systems struggle to effectively grasp the on-site situation during emergencies, making it difficult to manage triage efficiently.
A triage management system that utilizes location information from tags, creates electronic medical records based on triage tags and symptoms, and outputs categorized lists to facilitate comprehensive understanding of the situation.
Enables appropriate grasp of the emergency situation by providing categorized lists and maps, enhancing the management and allocation of resources.
Smart Images

Figure 0007586543000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to techniques that are useful in managing triage situations. [Background technology]
[0002] When a disaster occurs or an emergency response is carried out, triage is carried out. When triage is carried out, it is necessary to properly register information about the injured. Therefore, a system is known that registers information on injured people and triage tags in a database and outputs them as necessary (see Patent Document 1). [Prior art documents] [Patent documents]
[0003] [Patent Document 1] Patent Publication No. 2022-191702 Summary of the Invention [Problem to be solved by the invention]
[0004] However, while the invention described in Patent Document 1 makes it possible to grasp the condition of each individual injured person, it is difficult to adequately grasp the situation at the scene. Therefore, a method for adequately grasping the situation at the scene is required.
[0005] The present invention aims to provide a triage management system, a triage management method, and a program that are capable of appropriately grasping the situation on site. [Means for solving the problem]
[0006] The present invention provides a triage management system for managing triage situations, to a location information acquisition unit that acquires location information of the person in need of rescue from a location information transmission tag attached to the reage tag; a creation unit that creates an electronic medical record based on the classification of the triage tag attached to the person requiring rescue, the symptoms of the person requiring rescue, and location information of the person requiring rescue; Changes in the person needing rescue The classification of the triage tag or the edited content of the symptom of the person in need of rescue entered according to the A reception unit that receives Changes in the person in need of rescue Editing content according to In response to the above, the electronic medical record the classification of the triage tag or the symptoms of the person in need of rescue In addition, the electronic medical record is edited according to the location information of the person in need of rescue. Location information of the person in need of rescue The editorial department edits the articles one by one. a category list output unit that outputs the created electronic medical record as a category list by category; The present invention provides a triage management system comprising:
[0007] According to the present invention, by outputting electronic medical records collectively for each triage tag category, it becomes possible to properly grasp the condition of the injured person.
[0008] Although the present invention is in the category of a system, the same functions and effects can be obtained with a method and a program. Effect of the Invention
[0009] According to the present invention, it is possible to appropriately grasp the situation at the site. [Brief description of the drawings]
[0010] [Figure 1] FIG. 1 is a diagram for explaining an overview of a triage management system 1. [Diagram 2] FIG. 2 is a diagram illustrating a functional configuration of the triage management system 1. [Diagram 3] 1 is a flowchart showing an electronic medical record creation process executed by a computer 10. FIG. [Figure 4] 1 is a diagram showing a schematic example of a blank electronic medical record output by a computer 10. FIG. [Diagram 5] 1 is a diagram showing a schematic example of an electronic medical record when a computer 10 receives input. [Figure 6]1 is a flowchart showing an electronic medical record editing process executed by the computer 10. FIG. [Figure 7] FIG. 13 is a flowchart showing a category-based list output process executed by the computer 10. [Figure 8] FIG. 2 is a diagram showing an example of a category list output by the computer 10. [Figure 9] 13 is a flowchart showing a summary list output process executed by the computer 10. FIG. [Figure 10] 1 is a diagram showing a schematic example of a summary list output by a computer 10. FIG. [Figure 11] FIG. 11 is a flowchart showing a map output process executed by the computer 10. [Figure 12] FIG. 2 is a diagram illustrating an example of a map output by a computer 10. [Figure 13] 1 is a diagram showing a flowchart of a process for acquiring the number of available hospital beds executed by the computer 10. FIG. [Figure 14] 13 is a flowchart showing an acceptance / rejection list output process executed by the computer 10. FIG. [Figure 15] 10 is a diagram showing an example of an acceptance / rejection list output by the computer 10. FIG. [Figure 16] FIG. 13 is a flowchart showing a medical facility allocation process executed by the computer 10. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] Hereinafter, a detailed description will be given of an embodiment of the present invention with reference to the accompanying drawings. In the following drawings, the same elements are designated by the same numbers or symbols throughout the description of the embodiment.
[0012] [Overview of Triage Management System 1] Fig. 1 is a schematic diagram for explaining an overview of the triage management system 1. Components of the triage management system 1 will be explained based on Fig. 1. The triage management system 1 is a system for managing the triage situation, which is composed of at least a computer 10 having a server function. In this embodiment, in addition to the computer 10, the system includes a rescuer terminal 2 carried by a rescuer who performs rescue activities at the scene, and an administrator terminal 3 carried by an administrator who manages the rescuers. The computer 10 has a server function and may be realized, for example, by a single computer, or may be realized by a plurality of computers, such as a cloud computer. In this specification, a cloud computer may refer to either a scalable use of any computer to perform a specific function, or a computer that includes multiple functional modules to realize a system, the functions of which can be freely combined. The rescuer terminal 2 is, for example, a terminal device such as a mobile phone, a smartphone, a tablet terminal, a laptop computer, or a personal computer, or a wearable terminal such as a smart watch, smart glasses, or a head mounted display (HMD). The number of rescuer terminals 2 is not particularly limited and can be designed as appropriate. The administrator terminal 3 is, for example, a terminal device such as a mobile phone, a smartphone, a tablet terminal, a laptop computer, or a personal computer, or a wearable terminal such as a smart watch, smart glasses, or an HMD. The number of administrator terminals 3 is not particularly limited and can be designed as appropriate. In addition to the rescuer terminal 2, administrator terminal 3, and computer 10 described above, the triage management system 1 may also include other terminals and devices such as medical facility terminals (terminal devices such as mobile phones, smartphones, tablet terminals, laptop computers, personal computers, etc.) used in medical facilities, and the number, types, and functions of these are not particularly limited and can be designed as appropriate.
[0013] An overview of the processing steps performed by the triage management system 1 when managing the triage situation will be described.
[0014] The computer 10 creates an electronic medical record based on the classification of the triage tag attached to the patient and the symptoms of the patient (step S1). The rescuer terminal 2 reads the identification code attached to the triage tag attached to the person in need of rescue using a predetermined application, and requests the computer 10 to transmit the electronic medical record linked to the identification code. The computer 10 transmits a blank electronic medical chart to the rescuer terminal 2 in response to the request. The rescuer terminal 2 displays the received blank electronic medical record on its display unit and accepts input of the triage tag category of the rescuer and the patient's symptoms in the predetermined fields of the electronic medical record. The rescuer terminal 2 transmits the accepted input contents to the computer 10. The computer 10 receives the input and, based on the received input, creates an electronic medical record based on the classification of the triage tag attached to the patient and the symptoms of the patient.
[0015] The computer 10 outputs the created electronic medical record as a category-specific list by category (step S2). The computer 10 classifies the created electronic medical records according to the triage tag categories, and creates a category-by-category list that compiles the electronic medical records of rescue recipients by category. The manager terminal 3 uses a predetermined application to request transmission of the category list. In response to a request, the computer 10 transmits the created category list to the administrator terminal 3. The manager terminal 3 receives the category list and displays it on its own display unit. The computer 10 outputs the created electronic medical record as a category-specific list by displaying the category-specific list on the manager terminal 3.
[0016] The above is an overview of the triage management system 1. According to the present triage management system 1, it becomes possible to properly grasp the situation on-site.
[0017] [Device configuration] 2 is a block diagram showing the configuration of the triage management system 1. The device configuration of the triage management system 1 will be described with reference to FIG. The triage management system 1 is a system for managing a triage situation, and is configured with at least a computer 10. In this embodiment, the triage management system 1 is configured with a rescuer terminal 2 and an administrator terminal 3 in addition to the computer 10. The triage management system 1 is a system in which a computer 10 is connected to a rescuer terminal 2 and an administrator terminal 3 so as to be capable of data communication via a network 8 such as a public line network. In the triage management system 1, the number of rescuer terminals 2 and manager terminals 3 can be appropriately designed and is not particularly limited. In addition, the triage management system 1 may include, in addition to the rescuer terminal 2, the administrator terminal 3, and the computer 10, other terminals and devices such as medical facility terminals used in medical facilities, and the number, types, and functions of the other terminals and devices can be designed as appropriate.
[0018] The computer 10 has a server function and may be realized, for example, by a single computer, or may be realized by a plurality of computers, such as a cloud computer. The computer 10 has a control unit such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), a RAM (Random Access Memory), and a ROM (Read Only Memory), and has a communication unit such as a device for enabling communication with other terminals and devices, and a category list output unit that outputs the created electronic medical record as a category list by category. The computer 10 includes a data storage unit such as a hard disk, a semiconductor memory, a recording medium, or a memory card as a memory unit. The computer 10 includes, as a processing unit, various devices for executing various processes, a creation unit for creating an electronic medical record based on the classification of the triage tag attached to the patient and the symptoms of the patient, and the like.
[0019] In computer 10, the control unit loads a specified program and works in cooperation with the communication unit to realize an electronic medical record output module, an input reception module, a location information acquisition module, an editing reception module, a category list output module, a summary list output module, a map output module, a number of available beds acquisition module, an acceptance / non-acceptance list output module, and a medical facility output module. In addition, in the computer 10, the control unit reads a specific program and cooperates with the memory unit to realize an electronic medical record memory module and an available hospital bed number memory module. In addition, in computer 10, the control unit reads a specified program and cooperates with the processing unit to realize an electronic medical record creation module, an editing module, a category list creation module, a compilation module, a compilation list creation module, a location identification module, a category identification module, a map creation module, an acceptance / rejection list creation module, and a decision module.
[0020] The rescuer terminal 2 is a terminal device carried by the rescuer, and may be the above-mentioned terminal device, a wearable terminal, or the like. The rescuer terminal 2 includes a CPU, a GPU, a RAM, a ROM, and the like as a terminal control unit, and includes a device for enabling communication with other terminals, devices, and the like as a communication unit. The rescuer terminal 2 includes, as an input / output unit, various devices for receiving predetermined inputs and executing input / output of various data.
[0021] The manager terminal 3 is a terminal device carried by a manager who manages rescuers performing rescue activities at the scene, and is the above-mentioned terminal device, a wearable terminal, or the like. The administrator terminal 3 includes a CPU, GPU, RAM, ROM, etc. as a terminal control unit, and includes a device for enabling communication with other terminals, devices, etc. as a communication unit. The administrator terminal 3 includes, as an input / output unit, various devices for receiving predetermined inputs and executing input / output of various data.
[0022] Hereinafter, each process executed by the triage management system 1 will be described together with the process executed by each of the modules described above. In this specification, each module may execute its processing contents as its own function, or may execute its processing contents via a predetermined application.
[0023] [Electronic medical record creation process executed by computer 10] The electronic medical record creation process executed by the computer 10 will be described with reference to Fig. 3. The figure shows a flowchart of the electronic medical record creation process executed by the computer 10. This electronic medical record creation process is a detailed creation process (step S1) for creating an electronic medical record based on the classification of the triage tag attached to the rescue requester and the symptoms of the rescue requester.
[0024] The electronic medical chart output module outputs a blank electronic medical chart (step S10). The electronic medical chart output module outputs a blank electronic medical chart in response to a request from the rescuer terminal 2. A rescuer attaches a triage tag (such as a colored silicone band) to the hand, foot, or the like of a person requiring rescue according to the condition of the person requiring rescue (such as the urgency or severity of the injury or illness). The triage tags are classified into four categories, 0 to 3, according to the condition. 0 is an apnea group or a death group, 1 is a top-priority treatment group (severe injury group), 2 is an elective treatment group (moderate injury group), and 3 is a pending group (slight injury group). The triage tags are also color-coded according to the category, with 0 being black, 1 being red, 2 being yellow, and 3 being green. A location information transmission tag (such as a GPS (Global Positioning System) tag) is attached to the triage tag. Furthermore, a predetermined identification code (such as a two-dimensional code) is attached to the location information transmission tag. The rescuer terminal 2 accepts an input from the rescuer regarding the start of a predetermined application for reading the identification code (such as a tap on a predetermined icon arranged on the home screen of the rescuer terminal 2) and starts the corresponding application. The rescuer terminal 2 reads the identification code using a specific application, and requests the computer 10 to transmit a blank electronic medical record based on an access URL (Uniform Resource Locator) for the electronic medical record stored in the identification code, etc. The identification code has a one-to-one correspondence with the electronic medical record (one identification code is linked to only one electronic medical record), and if the identification code has been read in the past, the computer 10 and the rescuer terminal 2 execute an editing process described later. The electronic medical chart output module transmits a blank electronic medical chart to the rescuer terminal 2 in response to a request. The rescuer terminal 2 receives the blank electronic medical record and displays it on its own display unit (see FIG. 4). The electronic medical chart output module outputs a blank electronic medical chart by displaying the blank electronic medical chart on the rescuer terminal 2.
[0025] A blank electronic medical chart output by the electronic medical chart output module will be described with reference to Fig. 4. This figure is a schematic diagram showing a blank electronic medical chart output by the electronic medical chart output module. In this figure, an electronic medical chart 20 is shown. The electronic medical record 20 includes a triage tag field 21 in which a triage tag classification can be input, an image field 22 in which an image of the location where symptoms were determined, and at least one of images before and after first aid can be input, etc. Furthermore, the electronic medical record 20 has fields in which basic information of the person in need of rescue (name, age, sex, address, telephone number, date and time of triage implementation, name of triage implementer, name of transporting institution, name of accommodation institution, etc.) and symptoms (injury, illness, pathology, etc.) can be input, etc.
[0026] Returning to FIG. 3, the rest of the electronic medical record creation process will be explained. The input receiving module receives an input of rescue requester information related to a rescue requester (step S11). The rescuer terminal 2 accepts input from the rescuer into each field of the blank electronic medical record. The rescuer terminal 2 accepts input (tapping, etc.) from the rescuer into each field, accepts direct input of text, images, etc. into each field (input using a virtual keyboard, etc., input of images, etc.), selects an option suited to the person requiring rescue from multiple options set in advance (input using a drop-down list, etc.), etc., and accepts input of rescue requester information related to the person requiring rescue, such as basic information about the person requiring rescue, triage tag classification, images, symptoms, etc. (see FIG. 5). The rescuer terminal 2 transmits the received rescue requester information to the computer 10. The input receiving module receives information about a person in need of rescue, and receives input of the information about the person in need of rescue.
[0027] The rescue requester information inputted and received by the input receiving module will be described with reference to Fig. 5. The figure is a schematic diagram showing a state in which the rescuer terminal 2 receives input of the rescue requester information. In the figure, an electronic medical record 20 is shown. The triage tag field 21 is a field in which a rescuer can select and input a desired option from a plurality of options using a drop-down list or the like. The rescuer terminal 2 accepts input of the category of the triage tag of the rescuer in need of rescue in the triage tag field 21. When the rescuer terminal 2 accepts input (such as a tap) from the rescuer into the triage tag field 21, it displays a drop-down list and accepts the selection input of the category of the triage tag of the rescuer in need of rescue. When the rescuer terminal 2 accepts the selection input of the triage tag category from the rescuer, the background color of the triage tag field 21 is changed to a color (0 is black, 1 is red, 2 is yellow, and 3 is green) according to the category of the triage tag for which the selection input has been accepted. The triage tag field 21 may be a field in which text can be directly input. The image field 22 is a field in which an image can be input. The rescuer terminal 2 accepts input of at least one of an image of the location where the symptoms of the rescue requester were determined and images before and after first aid into the image field 22. When the rescuer terminal 2 accepts input (such as a tap) into the image field 22 from the rescuer, it accepts input of an image of the rescue requester captured by the rescuer terminal 2 or an image of the rescue requester captured by a capturing device communicably connected to the rescuer terminal 2. When the rescuer terminal 2 receives input (such as a tap) into each corresponding field in the electronic medical record 20 for the basic information and symptoms of the person in need of rescue, it also receives selection input from a drop-down list, etc., or direct input of text. When the rescuer terminal 2 receives input such as a transmission icon (an icon for transmitting the received input content to the computer 10) provided on the electronic medical record 20, the rescuer terminal 2 transmits the received input information on the rescuer to the computer 10. The input receiving module receives information about a person in need of rescue, and receives input of the information about the person in need of rescue.
[0028] Returning to FIG. 3, the rest of the electronic medical record creation process will be explained. The position information acquisition module acquires the position information of the rescue requester (step S12). The location information transmission tag attached to the triage tag determines its own location information based on GPS, and transmits the determined location information to the computer 10 as the location information of the person in need of rescue. At this time, the location information transmission tag also transmits its own identifier (management number, name, etc.). The location information transmission tag successively transmits the location information. The location information acquisition module receives the location information and the identifier of the location information transmitting tag, and acquires the location information of the person in need of rescue.
[0029] The electronic medical record creation module creates an electronic medical record based on the classification of the triage tag attached to the rescue requester and the symptoms of the rescue requester (step S13). The electronic medical record creation module creates an electronic medical record using the classification and color of the triage tag attached to the rescuer, the symptoms of the rescuer, an image, etc., based on the received information on the rescuer. The format of the electronic medical record created by the electronic medical record creation module is not particularly limited and can be designed as appropriate, and may be, for example, the format shown in Fig. 5. The electronic medical record creation module links the acquired location information of the rescuer and the identifier of the location information transmission tag to the created electronic medical record.
[0030] The process of step S13 described above may be performed by a predetermined generating AI (Artificial Intelligence) instead of the computer 10, and the computer 10 may acquire the processing result by the generating AI.
[0031] The electronic medical record storage module stores the created electronic medical record (step S14).
[0032] This completes the electronic medical record creation process.
[0033] [Electronic medical record editing process executed by computer 10] The electronic medical record editing process executed by the computer 10 will be described with reference to Fig. 6. The figure shows a flowchart of the electronic medical record editing process executed by the computer 10.
[0034] The electronic medical record output module outputs the electronic medical record of the rescue requester (step S20). In response to a request from the rescuer terminal 2, the electronic medical record output module outputs the electronic medical record created by the process of step S13 described above. When a change occurs in the person requiring rescue (a change in condition, symptoms, etc.), the rescuer terminal 2 accepts input from the rescuer (such as a tap on a specific icon located on the home screen, etc. of the rescuer terminal 2) to launch a specific application for reading the identification code attached to the triage tag attached to the person requiring rescue, and launches the corresponding application. The rescuer terminal 2 reads the identification code using a predetermined application, and requests the computer 10 to transmit the electronic medical record of the rescue requester based on a URL for accessing the electronic medical record stored in the identification code. The electronic medical record output module transmits the electronic medical record of the rescue requester to the rescuer terminal 2 in response to a request. The rescuer terminal 2 receives the electronic medical record and displays it on its own display unit. The electronic medical record output module outputs the electronic medical record of the rescue requester by displaying the electronic medical record of the rescue requester on the rescuer terminal 2. The electronic medical record of the person in need of rescue output by the electronic medical record output module is, for example, as shown in FIG.
[0035] The edit receiving module receives edits according to changes in the rescue requester (step S21). The rescuer terminal 2 accepts input from the rescuer into each field according to changes in the person in need of rescue. The rescuer terminal 2 accepts input (tapping, etc.) from the rescuer into each field, accepts direct input of text, images, etc. into each field (input using a virtual keyboard, etc., input of images, etc.), selects an option suited to the person in need of rescue from multiple options set in advance (input using a drop-down list, etc.), etc., and accepts editing of the information on the person in need of rescue, such as basic information, triage tag classification, images, symptoms, etc., according to changes in the person in need of rescue.
[0036] The editing module edits the electronic medical record in response to changes in the rescue requester (step S22). The editing module edits the content of the electronic medical record of the person in need of rescue based on the accepted editing content. For example, when the editing module accepts an edit of the triage tag category, it edits the triage tag category and edits the background color to a color corresponding to the edited category. Similarly, when editing each of the other fields, it edits the corresponding content of the corresponding field.
[0037] The process of step S22 described above may be configured such that a predetermined generation AI executes the process instead of the computer 10, and the computer 10 acquires the processing result by the generation AI.
[0038] The electronic medical record storage module stores the edited electronic medical record (step S23). The electronic medical record storage module updates the pre-edited electronic medical record to the edited electronic medical record.
[0039] This completes the electronic medical record editing process. In addition, since computer 10 sequentially receives location information transmitted from a location information transmission tag attached to a triage tag attached to the person in need of rescue, the location information of the person in need of rescue may be edited sequentially, may be edited at specified intervals, or may be edited during the electronic medical record editing process described above.
[0040] [Category-specific list output process executed by computer 10] The category-based list output process executed by the computer 10 will be described with reference to Fig. 7. This figure shows a flowchart of the category-based list output process executed by the computer 10. This category-based list output process is the details of the category-based list output process (step S2) that outputs the above-mentioned created electronic medical record as a category-based list by category.
[0041] The category-specific list creation module creates a category-specific list that organizes the created electronic medical records by category (step S30). The category is the category of the triage tag attached to each person in need of rescue. The category-based list creation module classifies rescue recipients into categories. The category-based list creation module groups rescue recipients by category and creates a category-based list that groups together the electronic medical records of the grouped rescue recipients. The category-based list creation module classifies people requiring rescue into the following groups: category 0, category 1, category 2, and category 3, compiles the electronic medical records of each person requiring rescue for each category, and creates a category-based list.
[0042] The process of step S30 described above may be configured such that a predetermined generation AI executes the process instead of the computer 10, and the computer 10 acquires the processing result by the generation AI.
[0043] The category-specific list output module outputs the created electronic medical record as a category-specific list by category (step S31). The category-based list output module outputs the created category-based list in response to a request from the manager terminal 3. The administrator terminal 3 accepts an input related to the launch of a predetermined application for displaying the categorized list (such as tapping on a predetermined icon arranged on the home screen of the administrator terminal 3) and launches the corresponding application. The administrator terminal 3 accepts an input related to the display of the categorized list (such as tapping on a predetermined icon in a predetermined UI (User Interface)) from this application, and requests the computer 10 to transmit a categorized list for the category desired by the administrator. In response to a request, the category-based list output module transmits to the manager terminal 3 a category-based list for the category desired by the manager. The manager terminal 3 receives the category list and displays it on its own display unit (see FIG. 8). The category-based list output module causes the manager terminal 3 to display a category-based list, thereby outputting the created electronic medical record by category as a category-based list.
[0044] The category list output by the category list output module will be described with reference to Fig. 8. This figure is a schematic diagram of a category list output by the category list output module. In this figure, a category list 30 is shown. The category list 30 is composed of a list of categories 31 desired by the administrator and electronic medical records 32 of each person in need of rescue. In the category 31, the number of the category desired by the administrator is shown, and the background color is a color corresponding to the number of the category. The electronic medical record 32 is an electronic medical record created in the electronic medical record creation process described above or edited in the electronic medical record editing process. The contents output as the electronic medical record 32 are not particularly limited, and the entire electronic medical record created or edited may be output, or only a part of it (symptoms, etc.) may be output. The category list output module outputs the category list 30 via a predetermined UI. The category list 30 has categories 31 at predetermined positions (such as the top or bottom of the category list 30), and the electronic medical records 32 of each person in need of rescue are arranged in a predetermined order (such as the earliest date and time of triage, by name, by age, etc.). The positions of the categories 31 and the order of the electronic medical records 32 can be designed as appropriate. Furthermore, when the administrator terminal 3 receives an input to switch the display to a category-specific list for another category (such as tapping on a specific icon in a specific UI), the administrator terminal 3 requests the computer 10 to transmit the category-specific list for the received category. The category-based list output module transmits a category-based list for the category desired by the administrator in response to a request. The manager terminal 3 receives the category-specific list for the category desired by the manager, and switches the display to the newly received category-specific list for the category desired by the manager.
[0045] The above is the process of outputting the list by category.
[0046] [Count list output process executed by computer 10] The summary list output process executed by the computer 10 will be described with reference to Fig. 9. The figure shows a flowchart of the summary list output process executed by the computer 10.
[0047] The counting module counts the number of people in need of rescue for each category (step S40). The counting module counts the number of people requiring rescue based on the triage tag classification in the electronic medical record of each person requiring rescue created by the above-mentioned electronic medical record creation process and the triage tag classification in the electronic medical record of each person requiring rescue edited by the electronic medical record editing process.
[0048] The tally list creation module creates a tally list of the number of people needing rescue by category based on the tally result (step S41). The tally list creation module creates a tally list that compiles the tally results of the rescue recipients by category.
[0049] The processes of steps S40 and S41 described above may be configured so that a predetermined generation AI executes the processes instead of the computer 10, and the computer 10 acquires the processing results by the generation AI.
[0050] The tally list output module outputs the tally results as a tally list (step S42). The tally list output module outputs the created tally list in response to a request from the manager terminal 3. The administrator terminal 3 accepts an input related to the launch of a predetermined application for displaying the tally list (such as tapping on a predetermined icon arranged on the home screen of the administrator terminal 3) and launches the corresponding application. The administrator terminal 3 accepts an input related to the display of the tally list (such as tapping on a predetermined icon in a predetermined UI) from this application, and requests the computer 10 to transmit the tally list. The tally list output module transmits the tally list to the manager terminal 3 in response to a request. The manager terminal 3 receives the tabulation list and displays it on its own display unit (see FIG. 10). The tally list output module outputs the tally results as a tally list by displaying the tally list on the manager terminal 3.
[0051] The summary list output by the summary list output module will be described with reference to Fig. 10. The figure is a schematic diagram of the summary list output by the summary list output module. In the figure, a summary list 40 is shown. The tally list 40 is composed of each category 41 of the triage tags attached to the rescue recipients and tally results 42 for each category 41. In category 41, numbers indicating each category of the triage tag are shown, and the background color is a color corresponding to the category number. The tally results 42 show the number of people requiring rescue in each category 41. The summary list 40 may further include some or all of the contents entered in the electronic medical records, such as basic information and symptoms of rescue recipients in each category 41. For example, the list may include common symptoms and common ages in each category 41, or conversely, rare symptoms and rare ages. In addition, the tally list output module can also be configured to accept input of the category of the triage tag of the person in need of rescue from an administrator (selection from a drop-down list, direct input using a virtual keyboard, etc.) and change the appearance (blinking, highlighting, adding an icon, etc.) of the category 41 and tally result 42 linked to the category of the triage tag of the person in need of rescue that has been accepted.
[0052] This completes the summary list output process.
[0053] [Map output process executed by computer 10] The map output process executed by the computer 10 will be described with reference to Fig. 11. The figure shows a flowchart of the map output process executed by the computer 10.
[0054] The location information acquisition module acquires location information of the person in need of rescue from a location information transmission tag attached to the triage tag (step S50). The location information acquisition module receives location information successively transmitted by the location information transmission tag, and acquires the location information of the person in need of rescue from the location information transmission tag attached to the triage tag. The location information acquisition module also receives the identifier (management number, name, etc.) of the location information transmission tag, and acquires the identifier (management number, name, etc.) of the location information transmission tag.
[0055] The position identification module identifies the position of the person in need of rescue based on the position information (step S51). The location identification module identifies the location of the person in need of rescue wearing the triage tag to which the location information transmission tag is attached, based on the location information transmitted from each location information transmission tag. The location identification module identifies the location of the person in need of rescue on a predetermined map, for example.
[0056] The category identification module identifies the category of the triage tag attached to the person in need of rescue (step S52). The category identification module identifies the electronic medical record of the rescue requester whose location has been identified based on the identifier of the location information transmission tag transmitted by each location information transmission tag and the identifier of the location information transmission tag linked to the electronic medical record created and edited by the electronic medical record creation process and the electronic medical record editing process described above. The category identification module identifies the category of the triage tag attached to the rescue requester based on the category of the triage tag entered in the electronic medical record of the identified rescue requester.
[0057] The map creation module creates a map that reflects the location of the identified person in need of rescue (step S53). The map creation module creates an icon linked to the electronic medical record of the identified rescuer. The map creation module may create this icon in a manner corresponding to the classification of the triage tag of the identified rescuer (e.g., color-coded in a color corresponding to the classification of the triage tag), or in a different manner, or may create all of the icons in the same manner. The map creation module places the created icons at the positions of the identified rescue recipients on a predetermined map, and creates a map that reflects the positions of the identified rescue recipients.
[0058] The map creation module may also create a map that reflects only the locations of rescue recipients in a section desired by the administrator. This case will be described. The administrator terminal 3 accepts input related to the launch of a predetermined application for displaying a map (such as tapping on a predetermined icon arranged on a home screen or the like on the administrator terminal 3), and launches the corresponding application. The administrator terminal 3 accepts input related to the display of a map for this application (such as tapping on a predetermined icon on a predetermined UI), and further accepts input of a desired category (selection input from a drop-down list, direct input from a virtual keyboard, etc.), and transmits the accepted category to the computer 10. The computer 10 receives this category, and creates an icon linked to the electronic medical record of the person in need of rescue in this category. The map creation module places the created icons at the positions of the rescue requesters on a predetermined map, and creates a map that reflects the positions of the rescue requesters in the division desired by the administrator.
[0059] The above-mentioned processes in steps S51 to S53 may be performed by a predetermined generation AI instead of the computer 10, and the computer 10 may acquire the processing results by the generation AI.
[0060] The map output module outputs a map reflecting the position of the person in need of rescue based on the acquired position information (step S54). The map output module outputs the created map in response to a request from the manager terminal 3. The administrator terminal 3 accepts an input related to the launch of a predetermined application for displaying a map (such as tapping on a predetermined icon arranged on a home screen or the like on the administrator terminal 3), and launches the corresponding application. The administrator terminal 3 accepts an input related to the display of a map (such as tapping on a predetermined icon on a predetermined UI) from this application, and requests the computer 10 to transmit the map. The map output module transmits the map to the administrator terminal 3 upon request. The manager terminal 3 receives the map and displays it on its own display unit (see FIG. 12). The map output module outputs a map reflecting the position of the person in need of rescue based on the acquired position information by displaying the map on the manager terminal 3.
[0061] The map output by the map output module will be described with reference to Fig. 12. This figure is a schematic diagram showing a map reflecting the position of a person in need of rescue based on the acquired position information output by the map output module. In this figure, a map 50 is shown. The map 50 has icons 51 arranged thereon, each of which is associated with a person in need of rescue who is wearing a triage tag to which a location information transmission tag is attached. An icon 51 is placed at the location of each person needing rescue on the map 50. The icon 51 is colored according to the category of the triage tag of the person needing rescue. Incidentally, the icon 51 is not limited to a predetermined mark, but may be something related to the person in need of rescue, such as basic information about the person in need of rescue, an image of the person in need of rescue, or something else, such as a symbol. The icon 51 can also be configured to accept input (such as a tap) from the administrator and display the electronic medical record of the person in need of rescue linked to the accepted icon 51 near the icon 51 or as a pop-up display. The map output module can also be configured to accept input of the triage tag category of the person in need of rescue from an administrator (selection input from a drop-down list, direct input using a virtual keyboard, etc.) and change the appearance of the icon 51 linked to the accepted triage tag category of the person in need of rescue (flashing, highlighting, adding an icon, etc.). The map output module can also be configured to accept input of basic information about the person in need of rescue from an administrator (such as direct input using a virtual keyboard) and change the appearance of the icon 51 linked to the accepted basic information (such as blinking, highlighting, adding an icon, etc.). In addition, when the administrator terminal 3 receives input (such as tapping on a specific icon in a specific UI or direct input using a virtual keyboard) to switch the display to a map that reflects the location of rescue recipients in the category desired by the administrator, it requests the computer 10 to send a map that satisfies the received input. In response to the request, the computer 10 executes a process similar to the process in step S53 described above, and when creating a map, creates a map that reflects the positions of rescue recipients in the section desired by the administrator. The map output module transmits the map created in response to the request to the manager terminal 3. The administrator terminal 3 receives the map reflecting the positions of rescue recipients in the administrator's desired category and displays it on its own display unit. At this time, if a map that does not specify a category or a map reflecting the positions of rescue recipients in another category is already displayed, the display is switched to the newly received map reflecting the positions of rescue recipients in the administrator's desired category. In addition, the map output module can also be configured to change the manner of the icon associated with the rescue requester in the category desired by the administrator on the original map (by flashing, highlighting, adding an icon, etc.), rather than switching the map.
[0062] This completes the map output process.
[0063] [Processing for obtaining the number of available hospital beds executed by computer 10] The process of acquiring the number of available hospital beds executed by the computer 10 will be described with reference to Fig. 13. The figure shows a flowchart of the process of acquiring the number of available hospital beds executed by the computer 10.
[0064] The vacant bed number acquisition module acquires the number of vacant beds for each medical facility (step S60). The vacant bed number acquisition module acquires the number of vacant beds for each medical facility from medical facility terminals (terminal devices such as mobile phones, smartphones, tablet terminals, laptop computers, personal computers, etc.) managed by each medical facility. A medical facility terminal managed by each medical facility (disaster base hospital, etc.) capable of accepting rescue recipients transmits the current number of available hospital beds that can accept rescue recipients at its own facility to computer 10. In addition to the number of available hospital beds, the medical facility terminal also transmits medical facility information related to its own facility, such as the medical facility identifier (name, etc.), location, medical department, doctor identifier (name, etc.), etc. The vacant bed number acquisition module receives the number of vacant beds and medical facility information, and acquires the number of vacant beds for each medical facility.
[0065] The vacant bed number storage module stores the acquired vacant bed number (step S61). The vacant bed number storage module stores the acquired number of vacant beds in association with medical facility information.
[0066] This completes the process for obtaining the number of available hospital beds. The computer 10 executes the process of acquiring the number of available hospital beds as needed, and stores the number of available hospital beds in the medical facility as needed, while updating the number of available hospital beds already stored according to the newly acquired number of available hospital beds.
[0067] [Acceptance / rejection list output process executed by computer 10] The acceptance / rejection list output process executed by the computer 10 will be described with reference to Fig. 14. Fig. 14 is a flowchart showing the acceptance / rejection list output process executed by the computer 10.
[0068] The acceptance / rejection list creation module creates an acceptance / rejection list of rescue requesters based on the number of available hospital beds (step S70). The acceptance / rejection list creation module creates an acceptance / rejection list that summarizes the triage tag categories and symptoms of rescue recipients that can be accepted and the number of rescue recipients for each medical facility based on the acquired number of available beds for each medical facility and medical facility information. When creating the acceptance / rejection list of rescue recipients, the acceptance / rejection list creation module may arrange the medical facilities in order of the number of available beds, the number of categories that can be handled, the number of symptoms that can be handled, the order of the names of the medical facilities, the reverse, or another method. The contents of the acceptance / rejection list created by the acceptance / rejection list creation module are updated as needed by the above-mentioned vacant bed number acquisition process.
[0069] In addition, the acceptance / rejection list creation module may create an acceptance / rejection list of only medical facilities that meet the conditions desired by the administrator (medical facility identifier, location, treatment category, treatable symptoms, and number of available beds). This case will be described. The administrator terminal 3 accepts an input for starting a predetermined application for displaying the acceptance / rejection list (such as tapping a predetermined icon arranged on the home screen of the administrator terminal 3) and starts the corresponding application. The administrator terminal 3 accepts an input for displaying the acceptance / rejection list for this application (such as tapping a predetermined icon in a predetermined UI), and further accepts an input of desired conditions (such as selection input from a drop-down list or direct input from a virtual keyboard), and transmits the accepted conditions to the computer 10. The computer 10 receives the conditions and creates an acceptance / rejection list of rescue recipients for only medical facilities that meet the conditions.
[0070] The process of step S70 described above may be configured such that a predetermined generation AI executes the process instead of the computer 10, and the computer 10 acquires the processing result by the generation AI.
[0071] The acceptance / rejection list output module outputs the acceptance / rejection list indicating whether the rescue requester can be accepted or not based on the acquired number of available hospital beds (step S71). The acceptance / rejection list output module outputs the created acceptance / rejection list in response to a request from the manager terminal 3. The administrator terminal 3 accepts an input regarding the launch of a predetermined application for displaying the acceptance / rejection list (such as tapping on a predetermined icon arranged on the home screen of the administrator terminal 3) and launches the corresponding application. The administrator terminal 3 accepts an input regarding the display of the acceptance / rejection list (such as tapping on a predetermined icon in a predetermined UI) from this application, and requests the computer 10 to transmit the acceptance / rejection list. The acceptance / rejection list output module transmits the acceptance / rejection list to the manager terminal 3 in response to a request. The manager terminal 3 receives the acceptance / rejection list and displays it on its own display unit (see FIG. 15). The acceptance / rejection list output module causes the manager terminal 3 to display the acceptance / rejection list, and outputs the acceptance / rejection list indicating whether or not the rescue requester can be accepted based on the acquired number of available hospital beds.
[0072] The acceptance / non-acceptance list output by the acceptance / non-acceptance list output module will be described with reference to Fig. 15. This figure is a schematic diagram showing the acceptance / non-acceptance list output by the acceptance / non-acceptance list output module. In this figure, an acceptance / non-acceptance list 60 is shown. The admission availability list 60 is composed of medical facilities 61, treatment categories 62, treatable symptoms 63, and number of available hospital beds 64. The medical facility 61 shows the name of the medical facility based on the acquired medical facility information. The response category 62 indicates the category of triage tag that the medical facility can respond to. The response category 62 may or may not have a background color that corresponds to the category of the triage tag. The symptoms of the rescuer that can be treated by the medical facility are shown in the treatable symptoms 63. The treatable symptoms 63 may describe all symptoms of the rescuer that can be treated, or may describe only a part of the symptoms (such as representative symptoms). The number of available hospital beds, 64, indicates the number of available hospital beds in medical facilities. The admission availability list 60 may be composed of only the medical facilities 61 and the number of available hospital beds 64, or may include other items than those mentioned above. In addition, when the administrator terminal 3 receives input (such as tapping on a specified icon in a specified UI or direct input using a virtual keyboard) to switch the display to an acceptance / rejection list of only medical facilities that meet the conditions desired by the administrator (medical facility identifier, location, treatment category, treatable symptoms, number of available beds), it requests the computer 10 to transmit a list of acceptance / rejection of the person in need of rescue that covers only medical facilities that meet the received input. In response to the request, the computer 10 executes processing similar to that of step S70 described above, and when creating a list of medical facilities that can accept or reject rescue recipients, creates a list of medical facilities that can accept or reject rescue recipients that is limited to only medical facilities that meet the conditions desired by the administrator. The acceptance / rejection list output module transmits the acceptance / rejection list created in response to the request to the manager terminal 3. The administrator terminal 3 receives the acceptance / rejection list that satisfies the conditions desired by the administrator and displays it on its own display unit. At this time, if an acceptance / rejection list that does not specify conditions or an acceptance / rejection list that satisfies other conditions is already displayed, the display is switched to the newly received acceptance / rejection list that satisfies the conditions desired by the administrator. In addition, the acceptance / rejection list output module can also be configured to change the behavior of medical facilities that meet the conditions desired by the administrator in the original acceptance / rejection list (by flashing, highlighting, adding an icon, etc.), rather than switching the acceptance / rejection list.
[0073] This completes the acceptance / rejection list output process.
[0074] [Medical facility allocation process executed by computer 10] The medical facility allocation process executed by the computer 10 will be described with reference to Fig. 16. The figure shows a flowchart of the medical facility allocation process executed by the computer 10.
[0075] The determination module determines which medical facility to assign the rescue requester to, depending on the symptoms of the rescue requester (step S80). The decision module decides which medical facility to assign the rescue requester to based on the category and symptoms of the triage tag attached to the rescue requester and the acceptance / rejection list created by the above-mentioned acceptance / rejection list output process. The determination module identifies a medical facility corresponding to the category of the triage tag and symptoms of each rescue requester, and determines whether the identified medical facility has available beds. If there are no available beds, the determination module reidentifies a medical facility other than the identified medical facility. On the other hand, if there are available beds, the determination module determines the identified medical facility as the destination of the rescue requester. Here, if the determination module identifies multiple medical facilities as destinations of the rescue requester, the determination module determines the medical facility with the largest number of available beds as the destination of the rescue requester. Alternatively, the determination module may determine the medical facility closest to the current location of the rescue requester as the destination of the rescue requester, or may determine the medical facility to which the rescue requester is assigned by other methods.
[0076] The process of step S80 described above may be configured such that a predetermined generation AI executes the process instead of the computer 10, and the computer 10 acquires the processing result by the generation AI.
[0077] In addition, in the processing of step S80 described above, the computer 10 determines the medical facility to which the rescue requester is assigned, but it is also possible to configure this processing to be performed mainly by the administrator terminal 3 rather than the computer 10. This case will be described. The manager terminal 3 accepts input to a medical facility for the acceptance admissibility list displayed by the above-mentioned acceptance admissibility list output process (tap on medical facility 61, number of available hospital beds 64, etc.), and transmits allocation destination information indicating that the accepted medical facility is to be the allocation destination to the computer 10. The computer 10 receives the allocation destination information. The determination module determines a medical facility in the allocation information as a medical facility to which the rescue requester is to be allocated.
[0078] The medical facility output module outputs the electronic medical record to the determined medical facility (step S81). The medical facility output module sends a notification that rescue recipients have been assigned (such as a message indicating the number of rescue recipients, the date and time, etc.) to the medical facility terminal managed by the medical facility that assigned the rescue recipients. The medical facility terminal receives this notification and displays it on its own display unit. The medical facility terminal accepts an input for starting a specific application for displaying the electronic medical record (such as tapping a specific icon arranged on a home screen of the medical facility terminal) and starts the corresponding application. The medical facility terminal accepts an input for displaying the electronic medical record (such as tapping a specific icon on a specific UI) for this application and requests the computer 10 to transmit the electronic medical record. The medical facility output module transmits, upon request, the electronic medical records of the rescue recipients assigned to this medical facility to the medical facility terminal. The medical facility terminal receives the electronic medical record and displays it on its own display unit. The medical facility terminal output module outputs the electronic medical record of the rescue requester assigned to the medical facility to the determined medical facility by displaying the electronic medical record on the medical facility terminal.
[0079] The above is the medical facility allocation process.
[0080] Although each of the above processes is described as a separate process, the computer 10 can be configured to execute a combination of some or all of the above processes. Also, the computer 10 can be configured to execute each process at a timing other than the timing described. Furthermore, although each of the above-mentioned processes is described as a process executed by the computer 10, it is also possible to configure a configuration in which some or all of the processes are executed directly by the rescuer terminal 2 or the manager terminal 3, rather than by the computer 10. In this case, for example, the rescuer terminal 2 executes an electronic medical record creation process and an electronic medical record editing process, outputs the processing results to the manager terminal 3, and stores the electronic medical record. The manager terminal 3 executes a category list output process, a summary list output process, a map output process, a vacant hospital bed number acquisition process, an acceptance / rejection list output process, and a medical facility allocation process.
[0081] The above-mentioned means and functions are realized by a computer (including a CPU, an information processing device, and various terminals) reading and executing a predetermined program. The program may be provided, for example, from a computer via a network (Software as a Service (SaaS)) or as a cloud service. The program may also be provided in a form recorded on a computer-readable recording medium. In this case, the computer reads the program from the recording medium, transfers it to an internal or external recording device, records it, and executes it. The program may also be recorded in advance on a recording device (recording medium) and provided from the recording device to the computer via a communication line.
[0082] Although the embodiments of the present invention have been described above, the present invention is not limited to the above-mentioned embodiments. Furthermore, the effects described in the embodiments of the present invention are merely a list of the most preferable effects resulting from the present invention, and the effects of the present invention are not limited to those described in the embodiments of the present invention.
[0083] A first aspect disclosed in this embodiment is a triage management system that manages a triage situation, a creating unit that creates an electronic medical record based on the classification of the triage tag attached to the patient and the symptoms of the patient; a category list output unit that outputs the created electronic medical record as a category list by category; The present invention provides a triage management system comprising:
[0084] A second aspect disclosed in this embodiment includes a counting unit that counts the number of patients by the category; an tally list output unit that outputs the tally results as an tally list; The triage management system according to the first aspect further comprises:
[0085] A third aspect disclosed in this embodiment is that the electronic medical record includes at least one of an image of a portion where symptoms were judged and an image before and after first aid, According to a first aspect, there is provided a triage management system.
[0086] A fourth aspect disclosed in this embodiment includes an editing unit that edits the electronic medical record in response to a change in a symptom of the patient; The triage management system according to the first aspect further comprises:
[0087] A fifth aspect disclosed in this embodiment includes a location information acquisition unit that acquires location information of the patient from a location information transmission tag attached to the triage tag; a map output unit that outputs a map reflecting the position of the patient based on the acquired position information; The triage management system according to the first aspect further comprises:
[0088] A sixth aspect disclosed in this embodiment includes an empty bed number acquisition unit that acquires the number of empty beds for each medical facility; an acceptance / rejection list output unit that outputs the acceptance / rejection list of the patient based on the acquired number of vacant hospital beds; The triage management system according to the first aspect further comprises:
[0089] A seventh aspect disclosed in this embodiment includes a determining unit that determines an allocation destination of the patient to a medical facility according to a symptom of the patient; a medical facility output unit that outputs the electronic medical record to the determined medical facility; The triage management system according to the first aspect further comprises: [Explanation of symbols]
[0090] 1. Triage Management System 2 Rescuer terminal 3. Administrator terminal 10. Computers 20 Electronic Medical Records 21 Triage Tag Column 22 Image column 30 List by category 31 categories 32 Electronic Medical Records 40 Count List 41 division 42 Counting Results 50 Maps 51 Icons 60 Acceptance / Rejection List 61 Medical Facilities 62 Available categories 63 Symptoms that can be treated 64 Number of vacant beds
Claims
1. A triage management system for managing triage situations, a location information acquisition unit that acquires location information of a person in need of rescue from a location information transmission tag attached to the triage tag; A creating unit that creates an electronic medical record based on the classification of the triage tag attached to the rescue requester, the symptoms of the rescue requester, and location information of the rescue requester; A reception unit that receives edited content for the classification of the triage tag or the symptom of the rescue requester input in accordance with a change in the rescue requester; An editing unit that edits the classification of the triage tag in the electronic medical record or the symptoms of the rescue requester according to the editing content corresponding to the change of the rescue requester received, and sequentially edits the location information of the rescue requester in the electronic medical record according to the location information of the rescue requester that is acquired; a category list output unit that outputs the created electronic medical record as a category list by category; A triage management system equipped with
2. A counting unit that counts the number of people requiring rescue by category based on the category of triage tags in the electronic medical record and the category of triage tags in the edited electronic medical record; an tally list output unit that outputs the tally results as an tally list; The triage management system of claim 1 further comprising:
3. The summary list output unit outputs the summary list including a part or all of the contents of the electronic medical record. The triage management system of claim 2 .
4. The electronic medical record includes at least one of an image of a portion where symptoms were judged and an image before and after first aid. The triage management system of claim 1 .
5. a map output unit that outputs a map reflecting the position of the rescue requester based on the acquired position information; The triage management system of claim 1 further comprising:
6. The map output unit receives a predetermined input for the output map, and outputs the created electronic medical record of the rescue requester on the map. The triage management system of claim 5 .
7. the map output unit places an icon associated with the person requiring rescue at a position of the person requiring rescue on the map, and when receiving input of basic information of the person requiring rescue, changes a state of the icon associated with the person requiring rescue. The triage management system of claim 5 .
8. An available bed number acquisition unit that acquires the number of available beds for each medical facility; an acceptance / rejection list output unit that outputs the acceptance / rejection of the rescue requester as an acceptance / rejection list based on the acquired number of vacant hospital beds; The triage management system of claim 1 further comprising:
9. A determination unit that determines a medical facility to which the rescue requester is assigned according to a symptom of the rescue requester; a medical facility output unit that outputs the electronic medical record to the determined medical facility; The triage management system of claim 1 further comprising:
10. A triage management method executed by a computer that manages a triage situation, comprising: A step of acquiring location information of a person in need of rescue from a location information transmission tag attached to the triage tag; creating an electronic medical record based on the classification of the triage tag attached to the person requiring rescue, the symptoms of the person requiring rescue, and location information of the person requiring rescue; A step of accepting edited content for the classification of the triage tag or the symptom of the rescue requester input in accordance with a change in the rescue requester; According to the received edit content corresponding to the change in the person requiring rescue, edit the classification of the triage tag in the electronic medical record or the symptoms of the person requiring rescue, and according to the acquired location information of the person requiring rescue, edit the location information of the person requiring rescue in the electronic medical record sequentially. outputting the created electronic medical record as a list by category; A triage management method to perform.
11. The computer that manages the triage situation A step of acquiring location information of the person in need of rescue from a location information transmission tag attached to the triage tag; creating an electronic medical record based on the classification of the triage tag attached to the person requiring rescue, the symptoms of the person requiring rescue, and location information of the person requiring rescue; A step of accepting edited content regarding the classification of the triage tag or the symptoms of the rescue requester input in response to a change in the rescue requester; A step of editing the classification of the triage tag in the electronic medical record or the symptoms of the rescue requester in accordance with the received editing content corresponding to the change in the rescue requester, and sequentially editing the location information of the rescue requester in the electronic medical record in accordance with the acquired location information of the rescue requester; A step of outputting the created electronic medical record as a category-specific list by category; A computer readable program for executing the program.
Citation Information
Patent Citations
Power generating device for diesel vehicle, emergency medical support electronic chart system and control system
JP2009281331A
Complementing device, complementing method and complementing program for electronic triage tag
JP2019192029A
Triage system, information terminal, and system management server
JP2022191702A
