Medical management systems, servers, and programs

Abstract

Efficiently manage information on multiple patients and multiple healthcare professionals. [Solution] A medical management system 1 is provided, which includes a server 12 for managing the linking of multiple patients with multiple medical professionals, and which performs the following processes: acquiring or setting first basic information including identification information of multiple patients; acquiring or setting second basic information including identification information of multiple medical professionals; displaying a setting screen 1800 for setting the linking of multiple patients with multiple medical professionals based on the first basic information of multiple patients and the second basic information of multiple medical professionals; and setting a setting process for setting the linking of multiple patients with multiple medical professionals based on input operations on the setting screen 1800.

Description

Technical Field

[0001] The present disclosure relates to a medical management system, a server, and a program.

Background Art

[0002] In medical institutions such as hospitals, biological information such as a patient's heart rate and respiratory rate is measured using measuring devices such as bedside monitors, and the patient's condition is managed. Medical staff such as doctors and nurses determine the treatment content and treatment plan for each patient based on the measured biological information of each patient. At this time, since a plurality of medical staff are involved in the treatment of each patient, a medical system that can share information on each patient among the plurality of medical staff is used.

[0003] For example, Patent Document 1 discloses a medical system in which a plurality of bedside monitors for measuring biological information of a subject and a central monitor for centrally managing the states of a plurality of subjects are communicably connected to each other. In the medical system of Patent Document 1, a history of biological parameters measured for a subject and a prediction input screen for allowing a user to input prediction information regarding future prediction of the subject's biological parameters are displayed on a display unit of the central monitor.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] Incidentally, in recent years, the importance of RRS (Rapid Response System) for quickly responding to sudden changes in a patient's condition has been increasing in medical institutions. In order to properly implement this RRS, it is desirable that medical institutions be able to share and confirm patient information in real time not only on a central monitor but also on mobile devices carried by each medical professional. However, the medical system described in Patent Document 1 above does not disclose anything about sharing patient information on the mobile devices of each medical professional.

[0006] Furthermore, in order to properly implement the above RRS, it is desirable that the medical system's server and central monitor manage information on a large number of patients, while each healthcare professional's mobile terminal extracts and outputs information on only a portion of the patients they are responsible for. Otherwise, it would be difficult for each healthcare professional to quickly check and respond to sudden changes in the condition of their assigned patients among a large number of patients, or to focus on understanding the risks for their assigned patients. Thus, in order to implement RRS, it is desirable to efficiently manage information on multiple patients and multiple healthcare professionals by using a combination of centralized management, where a large number of healthcare professionals manage information on a large number of patients using a server, and distributed management, where each healthcare professional manages information on only the patients they are responsible for using their mobile terminal.

[0007] Therefore, this disclosure aims to provide a medical management system, server, and program that can efficiently manage information on multiple patients and multiple healthcare professionals. [Means for solving the problem]

[0008] To solve the above problems, according to this disclosure, A medical management system equipped with a server that manages the linking of multiple patients with multiple healthcare professionals, A process for acquiring or setting first basic information including identification information of the aforementioned multiple patients, A process for acquiring or setting second basic information, which includes the identification information of the aforementioned multiple medical professionals, A display process that displays a settings screen for setting up the association between the multiple patients and the multiple healthcare professionals based on the first basic information of the multiple patients and the second basic information of the multiple healthcare professionals, A setting process that sets up the association between the multiple patients and the multiple healthcare professionals based on the input operation on the setting screen, A medical management system is provided to perform this task. [Effects of the Invention]

[0009] This disclosure makes it possible to efficiently manage information on multiple patients and multiple healthcare professionals. [Brief explanation of the drawing]

[0010] [Figure 1] Figure 1 is a block diagram showing the configuration of a medical management system according to an embodiment of this disclosure. [Figure 2] Figure 2 is a block diagram showing the configuration of the medical management system according to this embodiment. [Figure 3] Figure 3 is a sequence diagram illustrating the acquisition of vital signs using a bedside monitor according to this embodiment. [Figure 4] Figure 4 is a sequence diagram illustrating the acquisition and notification of scores by the bedside monitor according to this embodiment. [Figure 5] Figure 5 shows an example of a score notification screen displayed on a mobile device. [Figure 6] Figure 6 is an explanatory diagram showing an example of the basic screen displayed when the mobile terminal according to this embodiment is operating in nurse mode. [Figure 7] Figure 7 is an explanatory diagram showing specific examples of corresponding statuses. [Figure 8] Figure 8 is an explanatory diagram showing an example of a detailed screen displayed when the mobile terminal according to this embodiment is operating in nurse mode. [Figure 9] Figure 9 is a sequence diagram showing an example of the display process for the basic screen and detail screen of a mobile terminal according to this embodiment. [Figure 10] FIG. 10 is a diagram for explaining an example of an RRS call screen displayed when an input operation is performed on a call icon. [Figure 11] FIG. 11 is a diagram for explaining an example of a pull-down menu screen displayed when an input operation is performed on an input area for reasons for a request. [Figure 12] FIG. 12 is a sequence diagram showing an example of an operation when an input operation is performed on a call execution icon 640. [Figure 13] FIG. 13 is a diagram showing an example of a proxy request screen according to the present embodiment. [Figure 14] FIG. 14 is a diagram showing an example of a proxy request notification screen according to the present embodiment. [Figure 15] FIG. 15 is a sequence diagram for explaining the flow of proxy requests according to the present embodiment. [Figure 16] FIG. 16 is a sequence diagram for explaining the flow when proxy is not available for a proxy request notification according to the present embodiment. [Figure 17] FIG. 17 is a sequence diagram for explaining the flow of spot checks according to the present embodiment. [Figure 18] FIG. 18 is a diagram showing an example of a basic screen displayed when a mobile terminal according to the present embodiment operates in the RRT mode. [Figure 19] FIG. 19 is a diagram showing an example of a detailed screen displayed when a mobile terminal according to the present embodiment operates as the RRT mode. [Figure 20] FIG. 20 is a diagram showing an example of a doctor call screen displayed when an input operation is performed on a doctor call icon. [Figure 21] FIG. 21 is a diagram showing an example of a waveform display screen displayed on a mobile terminal according to the present embodiment. [Figure 22] FIG. 22 is a diagram showing an example of a trend screen according to the present embodiment. [Figure 23] FIG. 23 is a diagram showing an example of a status screen according to the present embodiment. [Figure 24]Figure 24 shows an example of a memo screen according to this embodiment. [Figure 25] Figure 25 illustrates the recording of various types of information by the server according to this embodiment and the creation of reports using the recorded information. [Figure 26] Figure 26 is a sequence diagram illustrating the flow of report creation according to this embodiment. [Figure 27] Figure 27 shows an example of a settings screen for configuring the link between patients and healthcare professionals according to this embodiment. [Figure 28] Figure 28 shows an example of a table that links the mobile terminal according to this embodiment, the medical professional who possesses the mobile terminal, and the operating mode of the mobile terminal. [Figure 29] Figure 29 shows an example of the settings screen for a support application in a mobile terminal according to this embodiment. [Figure 30] Figure 30 shows an example of a patient notification settings screen in a mobile terminal according to this embodiment. [Modes for carrying out the invention]

[0011] Embodiments of this disclosure will be described in detail below with reference to the attached drawings. The specific dimensions, materials, numerical values, etc., shown in these embodiments are merely illustrative to facilitate understanding of the invention and do not limit this disclosure unless otherwise specified. In this specification and drawings, elements having substantially the same function or configuration are denoted by the same reference numerals to avoid redundant explanations, and elements not directly related to this disclosure are omitted from the illustrations.

[0012] [1. Overview of RRS] First, we will describe the Rapid Response System (RRS) implemented using the medical management system according to the embodiment of this disclosure. The RRS is a mechanism for medical institutions such as hospitals to identify patients showing signs of worsening condition early and to respond to those patients. The RRS is an in-hospital response system that focuses on the fact that many sudden changes in a patient's condition (e.g., rapid deterioration of condition, cardiac arrest, etc.) are preceded by signs related to the patient's biological information (e.g., abnormal vital signs). If the RRS is properly established within a hospital, medical professionals such as doctors and nurses will be able to recognize changes in the patient's condition early and respond to the appropriate treatment early. In order to correctly detect and respond to the patient's condition with the RRS, clear objective criteria using scores that indicate the patient's condition are necessary. Furthermore, it is preferable to also use subjective criteria that complement these objective criteria (e.g., the subjective judgment of the medical professional who examined the patient).

[0013] In the RRS (Rapid Rating Scale), a score representing the patient's condition is calculated for each patient based on their vital signs. For example, the patient's condition may include their risk status. Vital signs are basic information about a patient's life and are also called vital signs. As a score using vital signs, for example, the Early Warning Score (EWS) can be used. The EWS is an index that quantifies the patient's condition. The EWS is a diagnostic support index that helps predict sudden changes in the patient's condition and is also used as an activation criterion for the RRS. For example, the EWS is calculated by scoring the measured values ​​of multiple vital signs of the patient, as well as the patient's level of consciousness, whether or not oxygen is being administered, etc. Vital signs preferably include at least one of the following, for example, respiratory rate, oxygen saturation (SpO2), body temperature, blood pressure, and pulse rate, but are not limited to these and may include various other information about the patient's body.

[0014] In this embodiment, we describe an example using a general-purpose score called EWS or NEWS (National Early Warning Score) as an early warning score representing the patient's condition, but the scores disclosed herein are not limited to such examples. For example, a Modified Early Warning Score (MEWS) may be used, which is a combination of multiple types of vital sign parameters customized and uniquely by each hospital.

[0015] Nurses and other healthcare professionals can refer to a patient's Emergency Health System (EWS) and, if they determine that the patient is showing signs of worsening condition, they can request assistance from a Rapid Response Team (RRT). An RRT is a team formed specifically to manage patients showing signs of worsening condition and includes multiple healthcare professionals with advanced life support training. Preferably, an RRT includes at least one person from a profession such as a nurse and a doctor, but it is not limited to this and may include people from various professions involved in healthcare.

[0016] In the following explanation, for the sake of clarity, the term "activation" of the RRS may be used to refer to the RRT responding to a patient who is judged to be showing signs of worsening condition. Furthermore, the act of requesting the RRT to activate the RRS may be referred to as an "RRS call." Finally, a patient to whom the RRS has been "activated" may be referred to as an "RRS patient."

[0017] When RRS is activated, each member of the RRT gathers at the location of the RRS patient and provides treatment to the patient according to their symptoms and condition. In this way, RRS enables a rapid response to patients showing signs of worsening symptoms.

[0018] [2. Configuration of the medical management system] Next, the overall configuration of the medical management system 1 according to this embodiment will be described with reference to Figures 1 and 2. Figures 1 and 2 are block diagrams showing the configuration of the medical management system 1 according to this embodiment.

[0019] As shown in Figures 1 and 2, the medical management system 1 comprises a plurality of mobile terminals 10, at least one server 12, at least one client PC 14 (Personal Computer) 14, at least one electronic medical record server 16, a plurality of bedside monitors 18, at least one central monitor 20, a plurality of spot check devices 22, and at least one vital signs server 24. Figure 1 shows an example of the components of the medical management system 1, specifically the plurality of mobile terminals 10, the server 12, the client PCs 14, and the electronic medical record server 16. Figure 2 shows an example of the components of the medical management system 1, specifically the plurality of bedside monitors 18, the central monitor 20, the plurality of spot check devices 22, and the vital signs server 24.

[0020] Medical Management System 1 is an information processing system used in medical institutions such as hospitals for healthcare professionals to manage medical care for patients. Medical Management System 1 is installed, for example, within a hospital and used to manage various types of medical information, such as patient information of patients hospitalized in the hospital. In order to protect patients' personal information and the hospital's trade secrets, it is preferable that Medical Management System 1 be a secure system limited to use within the hospital. For this reason, Medical Management System 1 may be constructed as an internal system that can only be used by healthcare professionals belonging to the hospital, utilizing the hospital's internal local network, and may be constructed in isolation from systems outside the hospital. However, this disclosure is not limited to such examples, and for example, Medical Management System 1 may be a system that links the internal system of a medical institution such as a hospital with external systems of the medical institution (for example, systems of other medical institutions, PCs and smartphones of home-care patients, systems of public institutions, etc.) via a public network.

[0021] The mobile terminals 10, server 12, client PCs 14, electronic medical record server 16, bedside monitors 18, central monitor 20, spot check devices 22, vital signs server 24, and other components of the medical management system 1 are connected to each other via a wireless or wired network (for example, the internal network of the hospital mentioned above) so that they can communicate with one another. The configuration of each device in the medical management system 1 is described below.

[0022] [2.1. Mobile Devices] The mobile device 10 is, for example, a portable computer such as a smartphone or a tablet PC. For example, each of the multiple mobile devices 10 is associated with a healthcare professional on a one-to-one basis. The association between the mobile device 10 and the healthcare professional is managed by the server 12. Each of the multiple mobile devices 10 is carried and possessed by the associated healthcare professional. The multiple mobile devices 10 may include mobile devices 10 carried by nurses and physicians who are members of the RRT, or they may include mobile devices 10 carried by nurses and physicians who are not members of the RRT.

[0023] In the medical management system 1, it is preferable that one mobile terminal is exclusively used by one healthcare professional, but one mobile terminal 10 may be shared by multiple healthcare professionals on a rotating basis. If one mobile terminal 10 is shared by multiple healthcare professionals on a rotating basis, it is preferable to update the association between the mobile terminal 10 and the healthcare professional each time the healthcare professional carrying the mobile terminal 10 changes.

[0024] As shown in Figure 1, the mobile terminal 10 includes a communication device 30, an input device 32, an output device 34, storage 36, one or more processors 38, and one or more memories 40 connected to the processor 38.

[0025] The communication device 30 is a device for communicating with external devices connected to the mobile terminal 10 by wire or wireless connection. For example, the communication device 30 can communicate wirelessly with the server 12 and the vital server 24.

[0026] The input device 32 can accept input operations from a medical professional carrying the mobile terminal 10, i.e., the user of the mobile terminal 10. The output device 34 can present various types of information to the user of the mobile terminal 10. For example, the output device 34 may include a display device such as a liquid crystal display (LCD) capable of displaying various screens, information, etc., or it may include an audio output device. The input device 32 may include physical input devices such as buttons and switches, a touch panel located on the front of the display device, an audio input device such as a microphone, etc.

[0027] The storage 36 is a non-volatile storage device, such as flash memory. The storage 36 stores various information used by the mobile terminal 10, as well as programs that control the operation of the mobile terminal 10. For example, the storage 36 stores the support application 50 and the vital application 52. In other words, in the medical management system 1, the support application 50 and the vital application 52 are installed on the mobile terminal 10.

[0028] The support application 50 is an application installed on the mobile terminal 10 to support RRS. The support application 50 includes a program that describes various processes related to RRS. The support application 50 is executed by the processor 38 to present information about RRS to healthcare workers and support their RRS activities.

[0029] The vital signs application 52 is an application installed on the mobile terminal 10 to enable real-time monitoring of the patient's vital signs measured by a bedside monitor 18 or a spot check device 22. The vital signs application 52 includes a program that describes the process of displaying the changes in the patient's vital signs measured in real time. The vital signs application 52 is executed by the processor 38 to display waveforms of the patient's various vital signs on the display device of the mobile terminal 10.

[0030] The processor 38 is a processing unit installed in a computer. The processor is composed of, for example, a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit), but may also be composed of other microprocessors. The processor 38 performs various processes in the mobile terminal 10 by executing programs stored in the memory 40, storage 36, or other storage media. A program is a computer program that includes instructions to be executed by the computer. By installing a program in the mobile terminal 10, the mobile terminal 10 becomes capable of realizing various functions defined by the program.

[0031] Memory 40 is a storage medium for storing programs and various other data. Memory 40 includes, for example, RAM (Random Access Memory) and ROM (Read Only Memory). ROM is a non-volatile memory that stores programs used by the processor 38 and data necessary to run those programs. RAM is a volatile memory that temporarily stores data such as variables, arithmetic parameters, and calculation results used in processes executed by the processor. Programs stored in ROM and storage 36 are read into RAM and executed by the processor 38, such as the CPU.

[0032] For example, the processor 38 may load the support application 50 stored in the storage 36 into the RAM of the memory 40 and execute the support application 50 deployed in the memory 40. Alternatively, the processor 38 may load the vital application 52 stored in the storage 36 into the RAM of the memory 40 and execute the vital application 52 deployed in the memory 40. Furthermore, while the support application 50 is being executed, the processor 38 may load the vital application 52 from the support application 50 and execute the vital application 52 in parallel. The processes executed by the processor 38 of the mobile terminal 10 will be described in detail later.

[0033] [2.2. Server] Server 12 is a computer that processes requests in response to requests from other computers, such as mobile terminals 10 and client PCs 14. Server 12 manages various types of information, including patient information for multiple patients and information on the history of interactions between healthcare professionals and patients.

[0034] As shown in Figure 1, the server 12 includes a communication device 60, an input device 62, an output device 64, storage 66, one or more processors 68, and one or more memories 70 connected to the processors 68.

[0035] The communication device 60 is a device for communicating with external devices connected to the server 12 by wire or wireless connection. The communication device 60 can communicate with the mobile terminal 10, client PC 14, electronic medical record server 16, central monitor 20, and spot check device 22.

[0036] The input device 62 can accept various input operations from the user. The output device 64 can present various information to the user. For example, the output device 64 may include a display device such as a liquid crystal display capable of displaying various screens, information, etc., or it may include an audio output device. The input device 62 may include physical input devices such as a keyboard and mouse, a touch panel placed on the front of the display device, an audio input device such as a microphone, etc.

[0037] Storage 66 is a non-volatile storage device such as a hard disk drive, solid-state drive, or flash memory. Storage 66 stores various information used by server 12, as well as programs that control the operation of server 12.

[0038] The processor 68 is a processing unit installed in the computer. The processor 68 is composed of, for example, a CPU or GPU, but may also be composed of other microprocessors. The processor 68 performs various processes in the server 12 by executing programs stored in memory 70, storage 36, or other storage media. A program is a computer program that includes instructions executed by the computer.

[0039] Memory 70 is a storage medium for storing programs and various other data. Memory 70 includes, for example, RAM and ROM. ROM is a non-volatile memory that stores programs used by the processor 68 and data necessary to run those programs. RAM is a volatile memory that temporarily stores data such as variables, arithmetic parameters, and calculation results used in processes executed by the processor 68. Programs stored in ROM and storage 66 are read into RAM and executed by the processor 68, such as the CPU.

[0040] [2.3. Client PCs] The client PC 14 is a computer such as a tablet PC, laptop PC, or desktop PC. The client PC 14 may be used not only by medical professionals such as doctors and nurses, but also by personnel in charge of various hospital operations such as medical administration, general affairs, accounting, public relations, general affairs, and information system management. For example, a general affairs staff member at a hospital may use the client PC 14 to create reports on RRS activity history. The client PC 14 connects to the server 12 via communication, requests processing from the server 12, and receives a response from the server 12. The client PC 14 receives various information stored in the server 12 from the server 12, processes the information, and presents it to the user.

[0041] As shown in Figure 1, the client PC 14 has a communication device 90, an input device 92, an output device 94, storage 96, one or more processors 98, and one or more memories 100 connected to the processors 98. The communication device 90, input device 92, output device 94, storage 96, processor 98, and memory 100 of the client PC 14 have similar functions and configurations to the communication device 60, input device 62, output device 64, storage 66, processor 68, and memory 70 of the server 12 described above, so a detailed explanation of them will be omitted.

[0042] [2.4. Electronic Medical Record Server] The electronic medical record server 16 is a computer that processes requests from other computers, such as server 12. The electronic medical record server 16 records and manages electronic medical records 120 for multiple patients. The electronic medical record 120 is electronic data representing the patient's medical record, including their condition, treatment, and progress. The electronic medical record 120 may include various types of information, such as basic patient information, information on treatment provided to the patient, and information on the history of interactions between medical professionals and the patient. The electronic medical record server 16 provides the server 12 with various types of information recorded in the electronic medical record 120 in response to requests from server 12.

[0043] Although not shown in the diagram, the electronic medical record server 16 may include communication devices, input devices, output devices, storage, processors, memory, etc., similar to the server 12 described above.

[0044] [2.5. Bedside Monitor] A bedside monitor 18 is an example of a measuring device for measuring a patient's vital signs. The bedside monitor 18 is an electronic device installed near the patient's bed in a hospital room, measuring, monitoring, and displaying the patient's condition. The bedside monitor 18 is used, for example, for critically ill patients whose vital signs need to be constantly monitored. For instance, the bedside monitor 18 is associated with a patient on a one-to-one basis. The association between the bedside monitor 18 and the patient is managed by a central monitor 20.

[0045] As shown in Figure 2, the bedside monitor 18 includes a communication device 150, an input device 152, an output device 154, storage 156, one or more processors 158, and one or more memories 160 and measuring instruments 162 connected to the processor 158. The communication device 150, input device 152, output device 154, storage 156, processor 158, and memory 160 of the bedside monitor 18 have similar functions and configurations to the communication device 60, input device 62, output device 64, storage 66, processor 68, and memory 70 of the server 12 described above, so a detailed explanation of them is omitted.

[0046] The measuring device 162 of the bedside monitor 18 is attached to the vital sign measurement site of the patient associated with the bedside monitor 18. The measuring device 162 continuously measures various vital signs of the patient. For example, the measuring device 162 preferably measures at least one of the following: respiratory rate, oxygen saturation (SpO2), body temperature, blood pressure, and pulse rate, but is not limited to these, and may measure various vital signs of the patient.

[0047] The processor 158 of the bedside monitor 18 transmits the patient's vital signs measured by the measuring instrument 162 to the central monitor 20 in real time via the communication device 150. The processor 158 of the bedside monitor 18 may also calculate the total score and individual scores, described later, based on the patient's vital signs measured by the measuring instrument 162, and transmit these to the central monitor 20.

[0048] [2.6. Central Monitor] The central monitor 20 is a computer for managing patient information, such as vital signs, for multiple patients. The central monitor 20 is installed in a management room, such as a nurses' station, and is used by multiple healthcare professionals. The central monitor 20 is communicatively connected to multiple bedside monitors 18 installed in each patient room, multiple spot check devices 22, and a server 12. The central monitor 20 acquires the vital signs of multiple patients measured by each bedside monitor 18 and each spot check device 22, and records, manages, and displays the vital signs of those patients.

[0049] As shown in Figure 2, the central monitor 20 has a communication device 180, an input device 182, an output device 184, storage 186, one or more processors 188, and one or more memories 190 connected to the processors 188. The communication device 180, input device 182, output device 184, storage 186, processor 188, and memory 190 of the central monitor 20 have similar functions and configurations to the communication device 60, input device 62, output device 64, storage 66, processor 68, and memory 70 of the server 12 described above, so a detailed explanation of them is omitted.

[0050] The processor 188 of the central monitor 20 receives vital signs from multiple patients in real time from multiple bedside monitors 18 and spot check devices 22. The processor 188 of the central monitor 20 stores the received vital signs in storage 186. The processor 188 of the central monitor 20 can also provide the received vital signs to the vital signs server 24 in real time. The processor 188 of the central monitor 20 can also periodically provide the received vital signs to the server 12. The processor 188 of the central monitor 20 may also calculate a total score and individual scores, as described later, based on the vital signs of multiple patients received from the bedside monitors 18 and spot check devices 22.

[0051] [2.7. Spot Check Device] The Spot Check Device 22 is an example of a measuring device for measuring a patient's vital signs. The Spot Check Device 22 is an electronic device capable of measuring a patient's vital signs on a spot basis. The Spot Check Device 22 is used, for example, for patients with mild to moderate illnesses who do not need to have their vital signs constantly monitored but need to be checked periodically as needed. The Spot Check Device 22 is designed to be portable and can be used, for example, by nurses making rounds to patient rooms. The nurse carries the Spot Check Device 22 when visiting a patient's room, attaches the measuring device 222 of the Spot Check Device 22 to the patient's measurement site, and measures the vital signs.

[0052] As shown in Figure 2, the spot check device 22 includes a communication device 210, an input device 212, an output device 214, storage 216, one or more processors 218, one or more memories 220 connected to the processors 218, and a measuring instrument 222. The communication device 210, input device 212, output device 214, storage 216, processor 218, and memory 220 of the spot check device 22 have similar functions and configurations to the communication device 30, input device 32, output device 34, storage 36, processor 38, and memory 40 of the mobile terminal 10 described above, so a detailed explanation of them is omitted.

[0053] The measuring instrument 222 of the spot check device 22 is operated, for example, by a nurse, to measure various vital signs of the patient. For example, the measuring instrument 222 preferably measures at least one of the following: respiratory rate, oxygen saturation (SpO2), body temperature, blood pressure, and pulse rate, but is not limited to these, and may measure various vital signs of the patient.

[0054] The processor 218 of the spot check device 22 associates the patient's vital signs measured by the measuring instrument 222 with patient information and transmits it to the central monitor 20 or server 12 via the communication device 210. The processor 218 of the spot check device 22 may also calculate a total score and individual scores, as described later, based on the patient's vital signs measured by the measuring instrument 222, and transmit these to the central monitor 20 or server 12.

[0055] Furthermore, the spot check device 22 may also include a function for medical professionals, such as nurses, to input notes about patients. These notes may include, for example, notes from medical professionals, such as nurses, regarding whether or not they have made any "observations" about the patient. The spot check device 22 may also allow medical professionals to select and input "yes" or "no" for "observations" on the display screen of the spot check device 22 when they are attending to a patient. The spot check device 22 may transmit the notes entered by medical professionals, along with the total score and individual scores, to the central monitor 20 or server 12. The notes entered in this way via the spot check device 22 may be displayed, for example, on the memo screen 1600 (see Figure 24) of the mobile terminal 10, depending on the communication between the server 12 and the mobile terminal 10.

[0056] [2.8. Vitals Server] The vital server 24 is a computer that processes requests in response to requests from the mobile terminal 10 running the vital application 52. The vital server 24 records and manages data and information regarding the vital signs of multiple patients. The vital server 24 can acquire the vital signs of multiple patients in real time from the bedside monitor 18 or spot check device 22 via the central monitor 20. The vital server 24 can provide the mobile terminal 10 running the vital application 52 with data representing the waveforms of the patients' vital signs in real time.

[0057] As shown in Figure 2, the vital server 24 has a communication device 240, an input device 242, an output device 244, storage 246, one or more processors 248, and one or more memories 250 connected to the processor 248. The communication device 240, input device 242, output device 244, storage 246, processor 248, and memory 250 of the vital server 24 have similar functions and configurations to the communication device 60, input device 62, output device 64, storage 66, processor 68, and memory 70 of the server 12 described above, so a detailed explanation of them is omitted.

[0058] [3. Processing related to bedside monitors] [3.1. Obtaining vital signs using a bedside monitor] Next, referring to Figure 3, the processing related to the bedside monitor 18 according to this embodiment will be described. Figure 3 is a sequence diagram illustrating the acquisition of vital signs by the bedside monitor 18 according to this embodiment.

[0059] As shown in Figure 3, the measuring instrument 162 of the bedside monitor 18 measures various vital signs of the patient associated with the bedside monitor 18 in real time (S10). The processor 158 of the bedside monitor 18 records the acquired vital signs in the storage 156 each time the patient's vital signs are measured by the measuring instrument 162 (S11). At the same time, the processor 158 of the bedside monitor 18 transmits the acquired vital signs and identification information that identifies the patient for whom the vital signs are being acquired to the central monitor 20 (S12).

[0060] When the central monitor 20 receives the patient's vital signs and identification information from the bedside monitor, it associates the acquired vital signs and identification information and records them in the storage 186 (S13).

[0061] In this way, the storage 186 of the central monitor 20 stores the patient's vital signs measured by the bedside monitor 18 in real time.

[0062] The processor 188 of the central monitor 20 sequentially determines whether a predetermined transmission condition for vital signs has been met (S20). For example, the central monitor 20 may determine that a predetermined transmission condition has been met when a predetermined time has elapsed since the previous transmission. This ensures that the transmission condition is met each time the predetermined time has elapsed. The predetermined time may be, for example, 15 minutes, but is not limited to this example; it may be other time intervals such as a few seconds, a few minutes, 30 minutes, or an hour. The central monitor 20 may also determine that a predetermined transmission condition has been met when vital signs have accumulated a predetermined number of samples or more since the previous transmission.

[0063] If the central monitor 20 determines that the predetermined transmission conditions are not met (NO in S20), it waits until the predetermined transmission conditions are met. If the central monitor 20 determines that the predetermined transmission conditions are met (YES in S20), it transmits the patient's vital signs and identification information recorded in the storage 186 to the server 12 via the communication device 180 (S21). At this time, the central monitor 20 transmits the vital signs that were acquired since the previous transmission from among the vital signs recorded in the storage 186.

[0064] When server 12 receives patient vital signs and identification information from central monitor 20, it associates the acquired vital signs and identification information and records them in storage 66 (S22).

[0065] In this manner, the central monitor 20 transmits patient vital signs and identification information to the server 12 in batch processing. The server 12's storage periodically stores patient vital signs measured by the bedside monitor 18 via the central monitor 20.

[0066] [3.2. Obtaining scores using bedside monitors] Figure 4 is a sequence diagram illustrating the acquisition and notification of scores by the bedside monitor 18 according to this embodiment.

[0067] As shown in Figure 4, the bedside monitor 18 determines whether the score update condition has been met (S30). For example, the bedside monitor 18 may determine that the score update condition has been met when a predetermined time has elapsed since the last update. This means that the score update condition will be met each time the predetermined time has elapsed. The predetermined time may be, for example, 8 hours, but is not limited to this example; it may be other time intervals such as several hours, 12 hours, or 24 hours. The bedside monitor 18 may also determine that the score update condition has been met when vital signs have accumulated a predetermined number of samples or more since the last update.

[0068] If the score update condition is not met (NO in S30), the bedside monitor 18 waits until the score update condition is met. If the score update condition is met (YES in S30), the bedside monitor 18 calculates the patient's vital signs score based on the latest values ​​of the patient's vital signs recorded in the storage 156. For example, the bedside monitor 18 may calculate an individual score and a total score as the score.

[0069] An individual score is a score calculated from one type of vital sign of a patient. An individual score may be a separate EWS for each type of vital sign. For example, suppose the vital signs measured are respiratory rate, oxygen saturation (SpO2), body temperature, blood pressure, and pulse. In this case, individual scores for respiratory rate, oxygen saturation (SpO2), body temperature, blood pressure, and pulse may be calculated. Individual scores are expressed as a step-by-step numerical value, for example, in four stages: "0," "1," "2," and "3," but are not limited to this example and may be expressed in any step-by-step manner. A higher individual score indicates a worse state of the patient's vital signs.

[0070] The total score is calculated from multiple types of vital signs of the same patient. The total score may be an EWS (Emergency Health System) that combines multiple individual scores (e.g., individual scores for respiratory rate, oxygen saturation (SpO2), body temperature, blood pressure, and pulse). For example, the total score may be calculated by adding up multiple individual scores. The total score is expressed as a step-by-step numerical value. For example, if there are seven types of individual scores, the total score will be expressed in 21 steps from "0" to "20 (18 (3 x 6) + 2 (2 x 1))", but it is not limited to this example and may be expressed in any step-by-step manner. For example, the total score may be calculated by adding up multiple types of individual scores of the same patient, or by weighting and adding those multiple types of individual scores. Alternatively, the total score may be calculated directly from multiple types of vital signs of the same patient without going through individual scores. A higher total score indicates that the patient's overall condition is worse and that there is a greater need for emergency response using the RRS (Rapid Risk Assessment System).

[0071] Furthermore, the total score may be calculated from all pre-set individual scores (or all vital signs) (e.g., 7 types), or from some of the individual scores (or some of the vital signs) (e.g., 6 types) out of all types. For example, if only some of the individual scores (e.g., 6 types) out of all types (e.g., 7 types) can be measured from a single patient, the sum of those individual scores may be used as the total score. If the total score calculated from all individual scores is the same as the total score calculated from some individual scores, it means that the total score calculated from some individual scores indicates a higher need for emergency response.

[0072] The bedside monitor 18 records the calculated patient score (more specifically, the individual score and the total score) in the storage 156 (S32). The bedside monitor 18 associates the calculated patient score (more specifically, the individual score and the total score) with the patient's identification information and transmits it to the central monitor 20 (S33).

[0073] When the central monitor 20 receives the patient's score and identification information from the bedside monitor 18, it associates the received patient's score and identification information and records it in the storage 186 (S34). At the same time, the central monitor 20 transmits the received patient's score and identification information to the server 12 (S35).

[0074] When server 12 receives patient scores and identification information from central monitor 20, it associates the received patient scores and identification information and records them in storage 66 (S36).

[0075] In this way, the server 12 stores patient scores (more specifically, individual scores and total scores) associated with the bedside monitor 18.

[0076] [3.3. Score notification regarding bedside monitor] As shown in Figure 4, the server 12 receives the patient's score from the central monitor 20 and records it in the storage 66 (S36). Then, based on the total score and / or individual scores, the server 12 determines whether the score notification condition has been met (S40). For example, the server 12 may determine that the score notification condition has been met if the total score is above a predetermined threshold. Alternatively, the server 12 may determine that the score notification condition has been met if the individual scores are above a predetermined threshold.

[0077] The score notification informs a specific healthcare professional's mobile device 10 that the patient's score is a value that suggests signs of worsening condition. The server 12's storage 66 may pre-record information associating the patient with the recipient of the score notification. The recipient of the score notification may be, for example, the patient's nurse or doctor.

[0078] If it is determined that the score notification conditions are not met (NO in S40), server 12 will not send the score notification.

[0079] If it is determined that the score notification conditions have been met (YES in S40), the server 12 selects the healthcare professionals to whom the score notification will be sent, based on the identification information of the patient for whom the score notification conditions have been met (S41). The healthcare professionals selected to receive the notification may be, for example, the nurse in charge of the patient for whom the score notification conditions have been met, the patient's attending physician, the RRT nurse, the RRT physician, or the head nurse, among other healthcare professionals belonging to the hospital.

[0080] Server 12 sends score notifications only to the mobile terminals 10 of selected healthcare professionals who are designated as recipients of the notification (S42). For example, Server 12 sends score notifications to the mobile terminals 10 of the assigned nurse or other healthcare professional selected as a recipient of the score notification, but does not send score notifications to the mobile terminals 10 of other healthcare professionals (other than the recipients). This allows only a select group of healthcare professionals in the hospital who are responsible for a particular patient to be notified that a patient's score has changed and that the patient requires attention. Therefore, each healthcare professional can quickly and accurately grasp changes in the condition of the patient they are responsible for among multiple patients. After sending the score notification, Server 12 records a response history in the storage 66 indicating that the score notification was sent (S43). The response history may include various information related to the score notification, such as the recipient and time of notification, in addition to the fact that the score notification was sent.

[0081] When a mobile terminal 10 of a healthcare professional selected as a notification recipient receives a score notification, it displays the score notification screen on the display device (S44).

[0082] Figure 5 shows an example of a score notification screen 300 displayed on a mobile device 10. As shown in Figure 5, the score notification screen 300 displays a message area 302 that shows the content of the score notification, such as "Tokyo Taro's score has exceeded the standard." The score notification screen 300 also displays an input area 304 labeled "Display" and an input area 306 labeled "Proxy Request."

[0083] The nurse in charge of receiving the score notification can see the message in message area 302 to confirm that they have received the score notification and to identify the patient to whom the notification is sent. This allows the nurse to recognize changes in the patient's condition in real time and to consider whether or not to intervene. The information displayed in message area 302 may include not only the patient's name as shown in Figure 5, but also various other patient information, such as the patient's ward and room number.

[0084] When a nurse is notified of a patient via score notification, they can perform an input operation on the input area 304 labeled "Display". When an input operation is performed on the input area 304 labeled "Display", the mobile terminal 10 displays various information about the notified patient on the display device.

[0085] If the assigned nurse is unable to immediately attend to a patient notified by the score notification, for example, due to being busy with other duties, they can request another nurse to attend to the notified patient by entering information in the input area 306 labeled "Proxy Request." This allows the nurse who receives the proxy request to quickly decide whether or not to attend to the patient. Therefore, even if the assigned nurse is unable to attend to a patient requiring emergency attention, another nurse can quickly attend to that patient.

[0086] [4. Basic screen of the mobile device (nurse mode)] Next, with reference to Figure 6, the basic screen displayed on the display device of the mobile terminal 10 when the mobile terminal 10 according to this embodiment runs the support application 50 will be described. Figure 6 is an explanatory diagram showing an example of the basic screen 400 displayed when the mobile terminal 10 according to this embodiment operates in nurse mode.

[0087] When the mobile terminal 10 runs the support application 50, it operates in either nurse mode or RRT mode, depending on the role of the healthcare professional associated with the mobile terminal 10. For example, if the healthcare professional associated with the mobile terminal 10 is a nurse who is not a member of the RRT, the mobile terminal 10 operates in nurse mode. On the other hand, if the healthcare professional associated with the mobile terminal 10 is a member of the RRT, the mobile terminal 10 operates in RRT mode. First, the nurse mode will be explained, and the RRT mode will be described later.

[0088] As shown in Figure 6, the basic screen 400 when operating in nurse mode may include a mark 410 that indicates the mobile terminal 10 is in nurse mode. The basic screen 400 may also include a display of the name 412 of the healthcare professional associated with the mobile terminal 10, such as "Shizuoka Chacha". The basic screen 400 may also include a display of icons 414 that allow various settings of the support application 50 to be configured.

[0089] The basic screen 400 may include a list display image 420 in which patient information, including identification information, individual scores, and total scores associated with each patient, is displayed in a list. More specifically, the list display image 420 includes the display of the patient's name as patient identification information, an individual score for one type of vital sign of the patient, and a total score which is the sum of multiple types of individual scores of the patient. The list display image 420 may also include the display of the measurement date and time of the vital signs that form the basis of the individual scores and total score. The list display image 420 includes patient information for at least one patient.

[0090] In list display image 420, the total score enclosed in parentheses "( )" is the total score calculated from some of the individual scores (or some of the vital signs) among all the individual scores that are subject to the calculation of the total score. On the other hand, the total score without parentheses in list display image 420 is the total score calculated from all of the individual scores (or all of the vital signs) that are subject to the calculation of the total score. If the total score with parentheses and the total score without parentheses are the same value, the total score with parentheses may be displayed higher than the total score without parentheses in list display image 420.

[0091] For example, in the example in Figure 6, the individual score for patient "Tokyo Taro" is "3" for "systolic blood pressure," the "total score" is "10," and the measurement date and time is "today" at "11:00," all of which are displayed together. Furthermore, the display range of the list image 420 can be freely changed by input operations such as swiping on the main screen 400.

[0092] For the total score in the list display image 420, for each patient, a latest value image 430 representing the most recent total score and a previous value image 432 representing the previous total score may be included. The latest value image 430 of the total score may be displayed relatively larger than the previous value image 432.

[0093] On the main screen 400, not only the latest image 430 of the total score but also the previous image 432 is displayed, so nurses carrying a mobile device 10 can easily keep track of changes in the patient's total score.

[0094] Regarding the individual scores in the list display image 420, one of several individual scores corresponding to multiple types of vital signs may be displayed. For example, the list display image 420 may selectively display the individual score of the vital sign with the highest numerical value (score value) among the patient's multiple types of vital signs.

[0095] Individual scores may display different types of individual scores for each patient. In the example in Figure 6, since the individual score for "systolic blood pressure" among the vital signs of patient "Tokyo Taro" is the highest, "systolic blood pressure" and "3" are displayed for patient "Tokyo Taro". Similarly, since the individual score for "respiratory rate" among the vital signs of patient "Shinagawa Hanako" is the highest, "respiratory rate" and "3" are displayed for patient "Shinagawa Hanako". This allows healthcare professionals to be presented with the individual score that requires the most careful monitoring among the multiple types of individual scores for each patient. Therefore, healthcare professionals can easily grasp the important individual scores for each patient displayed and respond quickly to changes in the patient's condition.

[0096] Furthermore, if there are multiple individual scores with the highest numerical value (score value), the list display image 420 may display at least one individual score selected from among the multiple individual scores based on a pre-set display priority for individual scores.

[0097] The display priority of individual scores may be set in the following order, from highest to lowest priority: "systolic blood pressure," "pulse rate," "body temperature," "oxygen saturation (SpO2)," and "respiratory rate." Note that the display priority of individual scores is not limited to the example given; it may be set in various other orders.

[0098] The basic screen 400 displays not only the total score for each patient but also their individual score, making it easier for nurses to infer each patient's condition.

[0099] Furthermore, the basic screen 400 displays only the single highest-priority individual score among multiple types of individual scores, thus preventing the basic screen 400 from becoming cluttered and difficult to read.

[0100] The list display image 420 of the basic screen 400 may include a response status image 440 that represents the response status. The response status is one of the patient information items and represents the status of the patient's response by healthcare professionals. The response status is associated with the patient's identification information, the patient's individual score, and the patient's total score, and is displayed as a response status image 440. In the example in Figure 6, a response status image 440 with a response status of "Alarm Notification" is displayed in the field below the patient name "Tokyo Taro".

[0101] An "alarm notification" alerts healthcare professionals when one or more of a patient's vital signs are at a value different from the normal value. For example, an "alarm notification" may be sent to a healthcare professional's mobile device 10 when one or more of a patient's vital signs, measured by a bedside monitor 18 or the like, exceed a pre-set threshold. The occurrence of an "alarm notification," i.e., a response status of "alarm notification," is an example of an abnormality in a patient's vital signs. The types of response statuses will be described later.

[0102] The main screen 400 displays the status of each patient's response, allowing nurses carrying a mobile device 10 to check the main screen 400, understand the status of each patient's response, and identify patients who require the highest priority.

[0103] The basic screen 400 may include a memo icon 450 that allows for the display and entry of notes about a patient. The memo icon 450 is associated with a patient. If a memo about a patient has already been created and it was created within a predetermined time, the memo icon 450 is displayed in the patient's display area. On the other hand, if no memo about a patient has been created, or if the created memo was created before the predetermined time, the display of the memo icon 450 in the patient's display area may be omitted. For example, when a healthcare professional carrying a mobile terminal 10 performs an input operation on the memo icon 450 displayed on the basic screen 400, a memo screen (not shown) is displayed on the display device of the mobile terminal 10. The memo screen displays notes such as the patient's condition, treatment details, and response status that have been written by the healthcare professional. The healthcare professional can use the memo screen to check previously written memos or write new memos. This makes it possible for multiple healthcare professionals to share notes about the patient's condition, treatment details, and response status.

[0104] The mobile terminal 10 can receive multiple notifications (for example, the score notifications mentioned above) related to multiple patients associated with the healthcare professional who possesses the mobile terminal 10. Therefore, in order to easily identify whether the healthcare professional has confirmed multiple notifications related to multiple patients, the basic screen 400 of the mobile terminal 10 may include highlight images 460 that represent the confirmation status of notifications related to each patient. The highlight images 460 of patients are images used to highlight the patient information of some of the multiple patients listed in the list display image 420 of the basic screen 400. These some patients may be patients for whom notifications have not yet been confirmed by the healthcare professional who possesses the mobile terminal 10. For example, as shown in Figure 6, the highlight image 460 is a frame image that surrounds the display area of ​​the patient information of patients for whom notifications have not yet been confirmed by the healthcare professional in the list display image 420 of the basic screen 400. Furthermore, the highlighted image 460 is not limited to the frame image example shown above. For example, the background color of the display area for patient information of patients who have received unconfirmed notifications from healthcare professionals may be different from the background color of the display area for other patient information.

[0105] On the basic screen 400 of the mobile device 10, a highlighted image 460 is displayed for patient information with unconfirmed notifications, allowing nurses carrying the mobile device 10 to easily and quickly recognize if there are unconfirmed notifications for their assigned patients.

[0106] The main screen 400 may include list icons 470 labeled "Assigned List" and "Overall List." For example, when an input operation is performed on the list icon 470 labeled "Overall List," patient information for all patients in the hospital is sorted according to a specific priority and displayed on the main screen 400 as a list display image 420.

[0107] Furthermore, for example, when an input operation is performed on the list icon 470 labeled "Assigned Patients List," patient information for a subset of patients assigned to the healthcare worker is extracted from all patients in the hospital. The extracted patient information is then sorted according to a specific priority and displayed on the main screen 400 as a list display image 420. In this case, patient information for patients other than those assigned to the healthcare worker is not displayed in the list display image 420. Therefore, healthcare workers can efficiently check patient information only for the patients they are assigned to by viewing the list display image 420. In addition, when an input operation is performed on the list icon 470, the main screen 400 may display a list display image 420 that includes both patients assigned to the healthcare worker and patients for whom the healthcare worker has received notifications.

[0108] The specific priority order for sorting the above patient information may include, for example, a first priority (highest priority), a second priority (next priority after the first priority), and a third priority (next priority after the second priority).

[0109] The first priority may be, for example, the priority regarding whether or not the notification has been confirmed. For example, in the list display image 420, patient information of patients with unconfirmed notifications, i.e., patient information for which the highlighted image 460 is displayed, may be displayed with higher priority than patient information of patients without unconfirmed notifications. In other words, in the list display image 420, patient information may be sorted and displayed so that patient information with unconfirmed notifications is displayed relatively higher (in a higher position). This makes it easy for healthcare professionals carrying the mobile terminal 10 to recognize if there are unconfirmed notifications for patients under their care or for patients who have received notifications.

[0110] The second priority may be, for example, a priority for multiple types of response statuses. For example, a priority for multiple types of response statuses may be set in advance, and in the list display image 420, patient information may be sorted and displayed so that patient information with a high priority for the current response status is displayed relatively higher (upper position). This allows healthcare workers carrying the mobile terminal 10 to refer to the response status of their own patients or patients handled by other healthcare workers and appropriately identify patients who should be given priority. An example of a priority for response statuses will be described later.

[0111] The third priority may be, for example, a priority based on the total score. For example, in the list display image 420, patient information may be sorted and displayed so that patient information with a high current total score is displayed relatively higher (in a higher position). The higher a patient's total score, the more severe the patient's symptoms are and the higher the likelihood that the patient requires urgent attention. Therefore, by displaying patient information in order of highest total score in the list display image 420, healthcare workers carrying the mobile device 10 can appropriately recognize patients with high total scores among their own patients or patients under the care of other healthcare workers as patients who should be given priority attention.

[0112] [5. Example of response status] Next, with reference to Figure 7, specific examples of the multiple types of corresponding statuses according to this embodiment will be described. Figure 7 is an explanatory diagram showing specific examples of corresponding statuses.

[0113] As shown in Figure 7, the response status is information that classifies the state of how healthcare professionals are responding to a patient. In other words, the response status is status information that represents the state of the healthcare professionals' response actions toward the patient.

[0114] Specifically, the response statuses according to this embodiment include, for example, "No score notification," "Score notification," "Proxy request," "Activation," "RRS call," "Contact doctor," "Doctor call," "Patient confirmation," "Monitoring," "Arrival at scene," "Treatment completed," "Interruption," "Proxy response unavailable," and "Alarm notification."

[0115] Thus, the response status is, (1) The response status caused by the score (for example, "No score notification", "Score notification"), (2) Response status resulting from the actions of healthcare workers (e.g., "Request for proxy," "Activation," "RRS call," "Contact doctor," "Doctor call," "Patient confirmation," "Observe," "Arrival at scene," "Procedure completed," "Interrupted") (3) Support status due to system settings (e.g., "Cannot be handled by proxy", "Alarm notification"), Includes.

[0116] (1) The response status based on the score is a status that is automatically changed depending on whether or not a notification is issued regarding the score calculated from the patient's vital signs (the total score or individual score mentioned above). By setting this response status based on the score, the response status of the patient can be automatically changed in accordance with changes in the patient's score. Therefore, the patient's response status can be appropriately and automatically changed regardless of whether or not a response action is taken by a healthcare professional.

[0117] (2) The response status resulting from the healthcare worker's response is a status that can be manually changed by the response actions taken by the healthcare worker towards the patient (e.g., observation, treatment, therapy, notification to other healthcare workers). By setting this response status resulting from the healthcare worker's response, the response status of the patient can be manually changed when a response action is taken by the healthcare worker.

[0118] (3) The response status due to system settings is a status that is automatically changed according to predetermined change conditions set in the medical management system 1. By setting this response status due to system settings, the response status of the patient can be automatically changed according to various conditions desired by the medical professional. Therefore, regardless of the response actions of the medical professional, the patient's response status can be freely and automatically changed when the desired conditions are met. For example, if the conditions for triggering an "alarm notification" are met and an "alarm notification" is issued, the response status of the patient for whom the alarm notification was issued may be automatically changed to "alarm notification".

[0119] When any of the above response statuses are changed automatically or manually, information regarding the changed response status is transmitted from the mobile terminal 10, bedside monitor 18, central monitor 20, etc. to the server 12 and recorded in the server 12. The server 12 collects and stores the response statuses for multiple patients and provides them to the mobile terminal 10, central monitor 20, etc. This allows healthcare professionals to view and confirm the response statuses of multiple patients in real time using the mobile terminal 10, central monitor 20, etc., and take appropriate next steps for the patients as needed.

[0120] As mentioned above, the specific priority for sorting and displaying patient information on the basic screen 400 (see Figure 6) may be the priority of the response status. For example, the priority of the response status may be set in the following order from highest to lowest: "Doctor Call," "RRS Call," "Proxy Request," "Proxy Response Unavailable," "Alarm Notification," "Score Notification," and "Other." Note that "Other" refers to response statuses other than "Doctor Call," "RRS Call," "Proxy Request," "Proxy Response Unavailable," "Alarm Notification," and "Score Notification" among the response statuses in Figure 7, and may be in any order. Thus, "Doctor Call," "RRS Call," "Proxy Request," "Proxy Response Unavailable," "Alarm Notification," and "Score Notification" are response statuses with high urgency. Therefore, it is preferable to sort and display the patient information of patients with such high urgency response statuses at the top of the basic screen 400 of the mobile terminal 10. This allows each healthcare professional to easily and quickly recognize the response status of patients requiring emergency response.

[0121] [6. Mobile device details screen (Nurse mode)] Next, with reference to Figure 8, a detailed screen displayed on the display device of the mobile terminal 10 when the mobile terminal 10 according to this embodiment runs the support application 50 will be described. Figure 8 is an explanatory diagram showing an example of a detailed screen 500 displayed when the mobile terminal 10 according to this embodiment operates in nurse mode.

[0122] The details screen 500 is a separate screen for each patient, displaying various information about a designated patient. A nurse holding the mobile terminal 10 can input information in the area of ​​the basic screen 400 in nurse mode where the patient information of the patient whose details they wish to check is displayed. When this input operation is performed, the mobile terminal 10 switches its display screen to the details screen 500 of the patient specified by that input operation.

[0123] Furthermore, the mobile terminal 10 may also display the patient details screen 500 for which the score notification is to be sent when an input operation is performed on the input area 304 labeled "Display" in the score notification screen 300 of Figure 5 described above.

[0124] The detail screen 500 may include the patient's name 510 as identifying information for the patient to be displayed, and the ward information (e.g., ward, floor, room number, etc.) in which the patient is hospitalized. The detail screen 500 may also include a back icon 512 for returning from the detail screen 500 to the basic screen 400.

[0125] The detail screen 500 may include a list display image 520 that shows a list of multiple types of vital signs, the patient's vital sign measurements, the date and time of vital sign measurement, and the patient's individual score based on the vital signs. The vital signs displayed on the detail screen 500 may include at least one of the following, for example: "systolic blood pressure," "pulse rate," "body temperature," "oxygen saturation (SpO2)," "respiratory rate," and "presence or absence of oxygen administration." The vital signs displayed on the detail screen 500 are not limited to those exemplified in Figure 8, but may include at least various vital signs measured by the bedside monitor 18. If all types of individual scores cannot be displayed at once in the list display image 520, healthcare professionals can view the desired individual scores by scrolling the list display image 520 vertically on the screen.

[0126] The list view image 520 of the details screen 500 may include a mark 530 that indicates the change in the latest value of an individual score relative to the previous value. For example, if the latest value has increased relative to the previous value, the mark 530 may be displayed as an upward-convex triangle. If the latest value has decreased relative to the previous value, the mark 530 may be displayed as a downward-convex triangle. If the latest value is the same as the previous value, the mark 530 may be displayed as a horizontally convex triangle. Healthcare professionals can easily recognize changes in a patient's individual score using such marks 530.

[0127] The details screen 500 may include a call icon 540 labeled "RRS Call". When a healthcare professional performs an input operation on the call icon 540, they can make an RRS call, that is, request the activation of RRS. As a result, the patient's response status is updated to "RRS Call". The updated response status is sent from the mobile terminal 10 to the server 12 and recorded. RRS calls will be explained later.

[0128] The details screen 500 may include an icon 542 labeled "Wait and See." When an input operation is performed on the icon 542 labeled "Wait and See," the patient's response status on the details screen 500 is updated to "Wait and See." The updated response status is sent from the mobile terminal 10 to the server 12 and recorded.

[0129] The details screen 500 may include an icon 544 labeled "Proxy Request". By performing an input operation on the icon 544 labeled "Proxy Request", a healthcare worker can request another nurse to attend to the patient on the details screen 500. As a result, the patient's attendance status is updated to "Proxy Request". The updated attendance status is sent from the mobile device 10 to the server 12 and recorded.

[0130] As described above, the score notification is an example of a notification sent to the mobile device of at least one healthcare professional associated with the patient. The details screen 500 is also displayed when an input operation is performed on the input area 304 labeled "Display" on the score notification screen 300. Upon receiving the score notification, the healthcare professional can check the patient's status on the patient's details screen 500, and in some cases, may actually check the patient's status.

[0131] If a healthcare professional determines that a patient's condition has suddenly changed, they may input "RRS Call," an example of a response status, to the call icon 540. Alternatively, if a healthcare professional determines that the patient's condition should be monitored, they may input "Wait and See," another example of a response status, to the icon 542, which is labeled "Wait and See." In other words, the details screen 500 is an example of an input screen (first input screen) for inputting a response status on the healthcare professional's mobile terminal 10 after responding to a patient in response to a notification. The mobile terminal 10 performs a first input process to display the details screen 500 (first input screen) in response to a notification. The mobile terminal 10 then transmits the response status, such as "RRS Call" or "Wait and See," entered by the healthcare professional on the details screen 500, from the mobile terminal 10 to the server 12 (first transmission process). The server 12 associates the response status, notification information, patient identification information, and the time of the healthcare professional's response and records it in the storage 66 as response history information.

[0132] In this way, the response status of each healthcare professional is sequentially accumulated on server 12, which reduces the burden on healthcare professionals while allowing for proper management of the healthcare professionals' response history to patients.

[0133] The details screen 500 may include a details icon 550 labeled "Details." Healthcare professionals can view more detailed information about the patient on the details screen 500 by performing input operations on the details icon 550.

[0134] The details screen 500 may include a trend icon 552 labeled "Trend". Healthcare professionals can view an overview of the patient's vital sign history on the details screen 500 by performing input operations on the trend icon 552.

[0135] The details screen 500 may include a status icon 554 labeled "Status". Healthcare professionals can check the history of patient status on the details screen 500 and input the status of the patient by performing input operations on the status icon 554.

[0136] The detail screen 500 may include a waveform display icon 556 labeled "Waveform Display". Healthcare professionals can view the waveforms of the patient's vital signs on the detail screen 500 in real time by performing input operations on the waveform display icon 556.

[0137] The details screen 500 may include a memo icon 558 labeled "Memo". Healthcare professionals can view and add notes about the patient on the details screen 500 by performing an input operation on the memo icon 558.

[0138] Furthermore, if the mobile terminal 10 receives alarm information regarding a patient on the detailed screen 500 from the central monitor 20 via the server 12, it may display a history of the received alarm information at the bottom of the list display image 520.

[0139] [7. Screen display sequence of mobile devices] Next, with reference to Figure 9, the display processing of the basic screen 400 and detail screen 500 of the mobile terminal 10 according to this embodiment will be described. Figure 9 is a sequence diagram showing an example of the display processing of the basic screen 400 and detail screen 500 of the mobile terminal 10 according to this embodiment.

[0140] First, the display of the basic screen 400 (see Figure 6) will be explained. As shown in Figure 9, the mobile terminal 10 receives a display instruction for the basic screen 400 (S50). The display instruction for the basic screen 400 may be generated, for example, in response to the launch of the support application 50. Alternatively, the display instruction for the basic screen 400 may be generated by an input operation by a medical professional on the back icon 512 of the detail screen 500. Alternatively, the display instruction for the basic screen 400 may be generated by an input operation by a medical professional on the list icon 470 of the basic screen 400.

[0141] In response to receiving a command to display the basic screen 400, the mobile terminal 10 sends request information to the server requesting patient information to display the basic screen 400 (S51).

[0142] In response to receiving the request information, Server 12 refers to the patient information recorded in Storage 66 and extracts the patient information to be transmitted (S52). At this time, Server 12 may extract one individual score from among multiple individual scores to be transmitted as patient information. Server 12 transmits the extracted patient information to the mobile terminal 10 (S53). The transmitted patient information includes the patient's identification information, the patient's individual score, the patient's total score, and the patient's response status.

[0143] When the mobile terminal 10 receives patient information from the server 12, it displays the basic screen 400 (see Figure 6) on the display device based on the received patient information (S54).

[0144] Next, the display of the details screen 500 (see Figure 8) will be described. As shown in Figure 9, the mobile terminal 10 receives a display instruction for the details screen 500 (S60). The display instruction for the details screen 500 may be generated, for example, by an input operation by a healthcare professional on the display area of ​​the desired patient information on the basic screen 400. Alternatively, the display instruction for the details screen 500 may be generated by an input operation by a healthcare professional on the input area 304 labeled "Display" on the score notification screen 300.

[0145] In response to receiving a command to display the details screen 500, the mobile terminal 10 sends request information to the server 12 requesting detailed information for displaying the details screen 500 (S61). The request information may include patient identification information for the details screen 500.

[0146] In response to receiving the request information, Server 12 refers to Storage 66 and extracts detailed information about the patient from the received identification information (S62). Server 12 sends the extracted detailed information to the mobile terminal 10 (S63). The transmitted detailed information includes the patient's identification information, detailed individual scores for the patient, and the patient's total score.

[0147] When the mobile terminal 10 receives detailed information from the server 12, it displays a detailed screen 500 (see Figure 8) on the display device based on the received detailed information (S64).

[0148] [8. RRS Call] Next, we will explain what happens when an input operation is performed on the call icon 540 labeled "RRS Call" in Figure 8 above. Figure 10 is a diagram illustrating an example of the RRS call screen 600 that is displayed when an input operation is performed on the call icon 540.

[0149] An RRS call is an example of a call notification, a call notification to request emergency response for a patient from members of the RRT (Rapid Response Team). A call notification is a notification from one of several healthcare professionals associated with a patient to another healthcare professional (the second healthcare professional) to request that the patient be attended to. When the first healthcare professional (the source of the call notification) inputs the call notification into their mobile terminal 10, the call notification is sent from the first healthcare professional's mobile terminal 10 to the second healthcare professional's (the recipient of the call notification) mobile terminal 10 via the server 12. The first healthcare professional, such as the assigned nurse, can notify the RRS call using, for example, an RRS call screen 600 as shown in Figure 8.

[0150] As shown in Figure 10, the RRS call screen 600 may include a delete icon 610 labeled "×". If an input operation is performed on the delete icon 610, the user can return from the RRS call screen 600 to the details screen 500 shown in Figure 8.

[0151] The RRS call screen 600 may include an input area 620 for entering the reason for the RRS call. Healthcare workers can, for example, select the reason for the call using a pull-down menu. The input area 620 may have pre-set reasons for the call entered as initial values.

[0152] Figure 11 illustrates an example of a pull-down menu screen 700 that appears when an input operation is performed in the input area 620 for the reason for the request. Note that the pull-down menu screen 700 is an example of a "second input screen for entering the reason for the call notification on the mobile terminal 10 of the first medical professional (the source of the call notification request)."

[0153] As shown in Figure 11, the pull-down menu screen 700 may include a delete icon 710 labeled "×". If an input operation is performed on the delete icon 710, the contents of the input area 620 are not changed, the pull-down menu screen 700 is cleared, and the user returns to the RRS call screen 600.

[0154] The pull-down menu screen 700 includes the display of the pull-down menu 720. The pull-down menu 720 is an example of a selection tool for healthcare professionals to choose a reason for requesting an RRS call. The pull-down menu 720 includes multiple options that can be selected as reasons for requesting an RRS call. For example, the pull-down menu 720 may include "increased EWS score," "tachypnea," "bradypnea," "new dyspnea," "decreased SpO2," "hypotension," "tachycardia," "bradycardia," and "chest pain." Note that the pull-down menu 720 may include a variety of reasons that could be considered as candidates for requesting an RRS call, not limited to the examples given.

[0155] When an input operation is performed on the pull-down menu 720, the pull-down menu screen 700 is cleared, and the request reason selected by the input operation is entered into the input area 620 of the RRS call screen 600.

[0156] On the mobile device 10, the reason for requesting an RRS call can be selected via a pull-down menu, allowing healthcare professionals who initiated (notified) the RRS call to easily, quickly, and accurately input the reason for the RRS call.

[0157] As shown in Figure 10, the RRS call screen 600 may include a notification candidate image 630 that lists the possible recipients of the RRS call. For example, the notification candidate image 630 illustrated in Figure 10 includes the name of the medical professional who is a candidate recipient of the RRS call and the role information of that medical professional. Note that the notification candidate image 630 only needs to include the name of the medical professional who is a candidate recipient, and the role information of the medical professional may be omitted. The notification candidate displayed in the notification candidate image 630 is managed by the server 12.

[0158] The RRS call screen 600 may include checkboxes 632 corresponding to the candidate recipients in the candidate notification recipient image 630. The healthcare professional who initiated the RRS call (notification source) can check or uncheck the checkboxes 632. The candidate recipients corresponding to the checked checkboxes 632 are set as the healthcare professionals to whom the RRS call will be notified.

[0159] As described above, the RRS call screen 600 (second input screen) displays the candidate notification destinations set in the server 12. Specifically, the server 12 has pre-registered configuration information linking patients with healthcare professionals involved with those patients. Based on this configuration information, the server 12 displays on the mobile terminal 10's RRS call screen 600 (second input screen) the names of multiple second healthcare professionals who are candidates for RRS call notification destinations (sending destinations), and a selection tool for selecting a healthcare professional to send the RRS call to from among these second healthcare professionals. The checkbox 632 in the RRS call screen 600 shown in Figure 10 is an example of this selection tool. The first healthcare professional who initiated the RRS call can easily and appropriately select a second healthcare professional to send the RRS call to using the names of multiple second healthcare professionals displayed on the RRS call screen 600 and the checkbox 632.

[0160] The RRS call screen 600 may also include a call execution icon 640 labeled "Call". When a healthcare professional who initiated (notified) the RRS call makes an input operation on the call execution icon 640, the mobile terminal 10 sends the RRS call information via the server 12 to the mobile terminal 10 of the healthcare professional to whom the notification is received, corresponding to the checked checkbox.

[0161] Figure 12 is a sequence diagram showing an example of the operation when an input operation is performed on the call execution icon 640. In Figure 12, it is assumed that the user of the first mobile terminal is the assigned nurse, the user of the second mobile terminal is a member of the RRT, and the user of the third mobile terminal is a doctor.

[0162] The first mobile terminal of the assigned nurse (first medical professional) displays a detailed screen 500 (first input screen) where the response status can be entered (first input process). As shown in Figure 12, the first mobile terminal of the assigned nurse (first medical professional) accepts an input operation indicating the start of execution of an RRS call for the call execution icon 640 (S70). The process of displaying the RRS call screen 600 (an example of a second input screen) on the first mobile terminal of the first medical professional who requested (notified) the RRS call, and the process of accepting an input operation from the said first medical professional (S70), is an example of a "second input process that displays a second input screen".

[0163] When the first mobile terminal receives an input operation for the call execution icon 640, it sends identification information of the patient to be called and activation information indicating the start of the RRS call to the server 12 (S71). The activation information may also include information on the reason for the request and information on the recipient, which are set on the RRS call screen 600. This transmission process in S71 is an example of a "second transmission process in which the reason for the request entered by the first medical professional on the second input screen (RRS call screen 600) is sent from the first medical professional's first mobile terminal to the server 12."

[0164] When server 12 receives patient identification information and activation information from the first mobile terminal, it associates the patient identification information and activation information and records them in storage 66 (S72). Furthermore, server 12 refers to the notification destination information contained in the received activation information and selects the second medical professional to whom the RRS call will be notified (S73).

[0165] Server 12 transmits patient identification information and RRS call information indicating the RRS call notification to the mobile terminal of the selected second healthcare worker (S74). Note that this transmission process in S74 is an example of "notification processing in which Server 12 transmits the call notification and the reason for the request to the mobile terminal 10 of the second healthcare worker."

[0166] In the example shown in Figure 12, server 12 transmits patient identification information and RRS call information to the second and third mobile terminals of the second healthcare professional (e.g., an RRT member and a physician) selected as the recipient of the RRS call notification. Note that RRS call information is not transmitted to the mobile terminal 10 of healthcare professionals who have not been selected as recipients of the RRS call notification. This prevents unnecessary notifications of RRS calls to healthcare professionals who are not involved with the patient in question, and allows for efficient notification of RRS calls only to the necessary healthcare professionals.

[0167] Subsequently, server 12 records the history of sending RRS call information in storage 66 (S75).

[0168] When the second mobile terminal receives patient identification information and RRS call information, it displays an RRS call notification screen on the display device (S76). Similarly, when the third mobile terminal receives patient identification information and RRS call information, it displays an RRS call notification screen on the display device (S77). The RRS call notification screen includes a display indicating that an RRS call has occurred and a display identifying the patient to whom the RRS call is directed.

[0169] [9. Request for proxy] Next, the proxy request according to this embodiment will be described with reference to Figures 13 to 16. Figure 13 is a diagram showing an example of the proxy request screen 800 according to this embodiment.

[0170] A proxy request is a request made by a first healthcare professional, who has received a notification regarding a patient (e.g., a score notification, a call notification, etc.), to another second healthcare professional to take over the patient's care. When the first healthcare professional (the source of the proxy request notification) inputs the proxy request into their mobile terminal 10, a proxy request notification is sent from the first healthcare professional's mobile terminal 10 to the second healthcare professional's mobile terminal 10 (the recipient of the proxy request notification) via the server 12. The proxy request notification is a notification from the first healthcare professional who has received the above notification (e.g., a score notification, a call notification, etc.) to the other second healthcare professionals to request that they take over the patient's care. The first healthcare professional can send a proxy request using, for example, a proxy request screen 800 as shown in Figure 13.

[0171] For example, if an input operation is performed on the input area 306 labeled "Proxy Request" on the score notification screen 300 in Figure 5 above, the proxy request screen 800 shown in Figure 13 will be displayed on the display device of the mobile terminal 10. Similarly, if an input operation is performed on the icon 544 labeled "Proxy Request" on the detail screen 500 in Figure 8 above, the proxy request screen 800 shown in Figure 13 will also be displayed on the display device of the mobile terminal 10.

[0172] As shown in Figure 13, the proxy request screen 800 may include a delete icon 810 labeled "×". If an input operation is performed on the delete icon 810, the user can return to the screen that was displayed immediately before the proxy request screen 800.

[0173] The proxy request screen 800 may include a list of candidate recipient images 820 for the proxy request notification (request recipient). For example, the candidate recipient image 820 illustrated in Figure 13 includes the names of the medical professionals who are candidates for the proxy request notification. The candidate recipient image 820 may also include role information of the medical professionals who are candidates for the proxy request notification. The candidate recipients displayed in the candidate recipient image 820 are managed by the server 12.

[0174] The proxy request screen 800 may include checkboxes 822 corresponding to the candidate recipients of the proxy request in the candidate recipient image 820. The first medical professional who is the source of the proxy request (notification source) can add or remove checks to the checkboxes 822. The candidate recipients of the notification corresponding to the checked checkboxes 822 are set as the second medical professional who will be notified (requested) for the proxy request. The recipients of the proxy request are not limited to one person, but may be multiple people. In the proxy request screen 800, the checkboxes 822 of the pre-configured recipients may be temporarily checked as initial values. Note that checkboxes 822 are an example of a selection tool for selecting the recipients of the proxy request.

[0175] Although not shown in the diagram, the proxy request screen 800 may include an input area where a message can be entered. The user of the mobile terminal 10 can freely enter a message to the person to be notified when a proxy request is made by performing a message input operation in the input area.

[0176] The proxy request screen 800 may include an icon 840 labeled "Proxy Request". When an input operation is performed on the icon 840 labeled "Proxy Request", a proxy request notification is sent to the selected mobile terminal 10.

[0177] When the mobile terminal 10 of the second medical professional (the recipient of the proxy request notification) receives the proxy request notification from the mobile terminal 10 of the first medical professional (the source of the proxy request notification), it displays the proxy request notification screen described below.

[0178] Figure 14 shows an example of the proxy request notification screen 900 according to this embodiment. The mobile terminal 10 that receives the proxy request notification displays the proxy request notification screen 900 shown in Figure 14 on its display device.

[0179] The proxy request notification screen 900 displays a message area 910 that shows the details of the proxy request, such as, "Ms. Gifu Hashima has requested that Mr. Tokyo Taro handle the matter." The proxy request notification screen 900 also displays an input area 912 labeled "Display" and an input area 914 labeled "Proxy Not Possible."

[0180] The user of the mobile terminal 10 who receives the proxy request notification can view the message in the message area 910 to confirm that they have received the proxy request, the patient to be handled by the proxy, and the sender of the proxy request.

[0181] Furthermore, the content displayed in the message area 910 is not limited to examples of content where the selected patient (e.g., Taro Tokyo) and medical professional (e.g., Hashima Gifu) are applied to a standard template for proxy requests, as shown in Figure 14. For example, at least a portion of the message entered in the input area of ​​the proxy request screen 800 may be displayed in the message area 910 of the proxy request notification screen 900, along with the standard template for proxy request notifications.

[0182] When a user of the mobile terminal 10 accepts the assignment of a proxy in response to a proxy request notification, they can perform an input operation on the input area 912 labeled "Display". When an input operation is performed on the input area 912 labeled "Display", the mobile terminal 10 may, for example, display the details screen 500 of the patient for whom the proxy action is being taken.

[0183] If a user of mobile device 10 is unable to act as a proxy in response to a proxy request notification, they can enter information into the input area 914 labeled "Proxy Unavailable" to inform the sender of the proxy request notification that they are unable to act as a proxy.

[0184] Figure 15 is a sequence diagram illustrating the flow of a proxy request according to this embodiment. In the example in Figure 15, the user of the first mobile terminal among the multiple mobile terminals 10 is the nurse (first medical professional) who made the proxy request, and the user of the second mobile terminal is the nurse (second medical professional) who is the recipient (notification recipient) of the proxy request.

[0185] As shown in Figure 15, the first mobile terminal receives an input operation indicating the start of execution of a proxy request for the icon 840 labeled "Proxy Request" on the proxy request screen 800 (see Figure 13) (S80). Upon receiving the input operation for the icon 840 labeled "Proxy Request", the first mobile terminal sends the identification information of the patient to be handled by the proxy and proxy request information representing the proxy request to the server 12 (S81). The proxy request information may also include the identification information of the medical professional to be notified and message information set on the proxy request screen 800.

[0186] When server 12 receives patient identification information and proxy request information from the first mobile terminal, it refers to the identification information of the healthcare professional to be notified included in the proxy request information and selects the nurse (second healthcare professional) to whom the proxy request notification will be sent (S82). Server 12 sends the patient identification information and proxy request notification information representing the proxy request notification to the second mobile terminal of the selected nurse (S83). Server 12 records the history of sending proxy request notification information in storage 66 (S84).

[0187] When the second mobile terminal receives patient identification information and proxy request notification information, it displays the proxy request notification screen 900 (see Figure 14) on the display device (S85).

[0188] A nurse (second medical professional) possessing a second mobile terminal can accept a proxy request by performing an input operation on the input area 912 labeled "Display" on the displayed proxy request notification screen 900. The second mobile terminal accepts the input operation indicating "Proxy Accepted" on the input area 912 labeled "Display" (S86). Upon receiving this input operation, the second mobile terminal displays the details screen 500 of the target patient identified by the identification information on its display screen (S87). This allows the nurse with the second mobile terminal to check the patient's condition and take appropriate action.

[0189] Furthermore, when the second mobile terminal receives an input operation indicating "Proxy Allowed" for the input area 912 (S86), it transmits the patient's identification information and proxy allowance information to the server 12 (S88). The proxy allowance information may also include the identification information of the nurse (first medical professional) who made the proxy request.

[0190] When server 12 receives patient identification information and proxy information from the second mobile terminal, it records the received patient identification information and proxy information in storage 66 (S89).

[0191] Figure 16 is a sequence diagram illustrating the process when proxy requests are not accepted in accordance with this embodiment. In the example of Figure 16, similar to Figure 15, the user of the first mobile terminal among the multiple mobile terminals 10 is the nurse (first medical professional) who made the request for proxy assistance, and the user of the second mobile terminal is the nurse (second medical professional) who received the request for proxy assistance (notification).

[0192] The nurse (second medical professional) on the second mobile terminal can refuse the proxy request by making an input operation on the input area 914 labeled "Proxy Not Allowed" on the displayed proxy request notification screen 900. As shown in Figure 16, the second mobile terminal accepts the input operation indicating "Proxy Not Allowed" on the input area 914 labeled "Proxy Not Allowed" (S90). Upon accepting the input operation, the second mobile terminal sends the patient's identification information and the proxy not allowed information to the server 12 (S91). The proxy not allowed information may also include the identification information of the nurse (first medical professional) who made the proxy request.

[0193] When server 12 receives patient identification information and non-proxy information from the second mobile terminal, it refers to the identification information of the requesting nurse included in the non-proxy information and selects the nurse (first medical professional) to whom the non-proxy information should be sent (S92). Server 12 transmits the patient identification information and non-proxy information to the first mobile terminal of the selected recipient nurse (S93). Server 12 records the history of the transmission of non-proxy information in storage 66 (S94).

[0194] When the first mobile terminal receives patient identification information and non-representation information, it displays a screen indicating that representation is not possible on its display device (S95). This allows the nurse on the first mobile terminal to recognize that the representation request was unsuccessful. In this case, the nurse on the first mobile terminal may change the recipient of the representation request (notification recipient), the medical professional (third medical professional), and make the representation request again.

[0195] [10. Spot check] Next, with reference to Figure 17, a spot check according to this embodiment will be described. A spot check means measuring the patient's vital signs using the spot check device 22. Figure 17 is a sequence diagram illustrating the flow of a spot check according to this embodiment.

[0196] The measuring instrument 222 of the spot check device 22 is attached by a nurse to the patient's vital sign measurement site. The nurse performs an input operation to instruct the spot check device 22 to start the measurement. As shown in Figure 17, the spot check device 22 accepts the input operation to instruct the start of the measurement (S100). Then, the measuring instrument 222 of the spot check device 22 performs the measurement of the patient's vital signs (S101). Once the measurement of the patient's vital signs is complete, the spot check device 22 records the measurement results in the storage 216 (S102).

[0197] The spot check device 22 calculates individual scores and a total score from the vital signs measured using a predetermined table or calculation algorithm (S103). The spot check device 22 records the calculated individual scores and total score in the storage 216 (S104).

[0198] The spot check device 22 transmits patient identification information, vital signs measured, calculated individual scores, and total scores to the server 12 (S105).

[0199] When the server 12 receives patient identification information, vital signs from the measurement results, calculated individual scores, and total scores from the spot check device 22, it records them in the storage 66 (S106).

[0200] Server 12 records the individual scores and total scores received from the spot check device 22 in storage 66, and then determines whether the score notification conditions have been met (S107). For example, Server 12 may determine that the score notification conditions have been met if the received total score is equal to or greater than a predetermined threshold. Alternatively, Server 12 may determine that the score notification conditions have been met if the received individual scores are equal to or greater than a predetermined threshold. If Server 12 receives multiple types of individual scores, it may determine that the score notification conditions have been met if at least one type of individual score is equal to or greater than a predetermined threshold.

[0201] If it is determined that the score notification conditions are not met (NO in S107), the server 12 will not send a score notification to the mobile terminal 10.

[0202] If it is determined that the score notification conditions have been met (YES in S107), the server 12 selects the healthcare professionals to whom the score notification will be sent based on the identification information of the patient for whom the score notification conditions have been met (S108).

[0203] Server 12 sends the score notification only to the mobile terminal 10 of the selected healthcare professional(s) who are the recipients of the notification (S109). For example, Server 12 sends the score notification to the mobile terminal 10 of the nurse who has been selected as the recipient of the score notification, but does not send the score notification to any other mobile terminals 10 (other than the recipients). After sending the score notification, Server 12 records in storage 66 that the score notification has been sent (S110).

[0204] When a mobile terminal 10 of a healthcare professional selected as a notification recipient receives a score notification, it displays the score notification screen 300, as illustrated in Figure 5 above, on its display device (S111). This allows for quick and efficient notification to the nurse or other healthcare professional assigned to the patient, selected from among multiple healthcare professionals, that the patient's score has changed and that the assigned nurse needs to take action, in the event that the patient's score has increased.

[0205] [11. Basic screen of the mobile device (RRT mode)] Figure 6 above shows an example of the basic screen 400 displayed when the mobile terminal 10 is operating in nurse mode. As described above, if the healthcare professional associated with the mobile terminal 10 is a member of the RRT (e.g., RRT nurse, RRT doctor, etc.), the mobile terminal 10 operates in RRT mode. Below, with reference to Figure 18, the basic screen displayed when the mobile terminal 10 according to this embodiment operates in RRT mode will be described in comparison with the basic screen 400 in nurse mode shown in Figure 6. Figure 18 shows an example of the basic screen 1000 displayed when the mobile terminal 10 according to this embodiment operates in RRT mode. In the basic screen 1000 of Figure 18, the same reference numerals are used to simplify the explanation of display items that are the same as those in the basic screen 400 in nurse mode shown in Figure 6.

[0206] As shown in Figure 18, the basic screen 1000 when operating in RRT mode may include a mark 1010 that indicates the mobile terminal 10 is in RRT mode. The basic screen 1000 may also include a display of the name 1012 of the healthcare professional (more specifically, a member of the RRT) associated with the mobile terminal 10, such as "Hanako Fukuda".

[0207] The basic screen 1000 for RRT mode may include a list display image 420 that shows a list of patient information, such as identification information, individual scores, and total scores associated with each patient, similar to the basic screen 400 for nurse mode.

[0208] Furthermore, the total score in the list display image 420 of the basic screen 1000 in RRT mode may include, for each patient, a latest value image 430 representing the latest total score and a previous value image 432 representing the previous total score, similar to the basic screen 400 of Nurse mode.

[0209] Furthermore, regarding the individual scores in the list display image 420 of the basic screen 1000 of RRT mode, at least one of several types of individual scores corresponding to several types of vital signs may be displayed, similar to the basic screen 400 of Nurse mode.

[0210] Furthermore, the list display image 420 of the basic screen 1000 in RRT mode may include a corresponding status image 440 that represents the corresponding status, similar to the basic screen 400 of Nurse mode.

[0211] Furthermore, the list display image 420 of the basic screen 1000 in RRT mode may include a memo icon 450 that allows for the display of memos, similar to the basic screen 400 in Nurse mode. In addition to the function of displaying memos, the memo icon 450 in RRT mode may also include a function for writing memos.

[0212] Furthermore, the list display image 420 of the basic screen 1000 in RRT mode may include a highlighted image 460 that can identify patient information for which there is a notification that has not yet been confirmed by the healthcare professional who is the user of the mobile terminal 10, similar to the basic screen 400 of the nurse mode.

[0213] Furthermore, the basic screen 1000 for RRT mode may also include the display of icons 414 that allow various settings of the support application 50, similar to the basic screen 400 for nurse mode.

[0214] Furthermore, the list view image 420 of the basic screen 1000 in RRT mode displays multiple patient information sorted according to a specific priority, similar to the basic screen 400 in Nurse mode.

[0215] The basic screen 1000 of RRT mode does not necessarily have to include the list icons 470 labeled "Assigned List" and "Overall List" in the basic screen 400 of Nurse mode (see Figure 6).

[0216] The basic screen 1000 in RRT mode may include checkboxes 1020 instead of list icons 470 to filter and display patient information that meets predetermined conditions from among multiple patient information (for example, patient information for all patients in the hospital). Multiple checkboxes 1020 may be provided, for example, corresponding to the stages of the total score. There may be more than one checkbox 1020.

[0217] For example, if checkbox 1020 labeled "4-0" is checked, only patient information with a total score between "0" and "4" will be displayed in list image 420. If checkbox 1020 labeled "6-5" is checked, only patient information with a total score between "5" and "6" will be displayed in list image 420. If checkbox 1020 labeled "7 or more" is checked, only patient information with a total score of "7" or higher will be displayed in list image 420.

[0218] Nurses who are not RRT members are typically responsible for a subset of the many patients in the hospital. Therefore, in the basic screen 400 of Nurse Mode (see Figure 6), a list icon 470 labeled "Assigned Patients List" allows nurses to filter and display only the patient information of the patients they are responsible for.

[0219] On the other hand, RRT members typically do not assign themselves to a specific group of patients, but rather deal with a wide range of patients showing signs of worsening condition. Therefore, the basic screen 1000 of RRT mode provides checkboxes 1020 instead of filtering the display of patient information by assigned patients. The basic screen 1000 of RRT mode then allows the display of patient information to be filtered according to the level of the total score using the checkboxes 1020. This allows the RRT member to appropriately filter the patient information according to their needs.

[0220] [12. Mobile device details screen (RRT mode)] Figure 8 above shows an example of the detailed screen 500 displayed when the mobile terminal 10 is operating in nurse mode. In contrast, the detailed screen displayed when the mobile terminal 10 according to this embodiment is operating in RRT mode will be described below with reference to Figure 19, comparing it with the detailed screen 500 of nurse mode in Figure 8. Figure 19 is a diagram showing an example of the detailed screen 1100 displayed when the mobile terminal 10 according to this embodiment is operating in RRT mode. In Figure 19, the same reference numerals are used for display items that are the same as those in the detailed screen 500 of nurse mode in Figure 8, and the explanation will be simplified.

[0221] As shown in Figure 19, the RRT mode detail screen 1100 may include, similar to the nurse mode detail screen 500, the patient's name 510 as identification information for the patient to be displayed, the ward information in which the patient is hospitalized (e.g., ward, floor, room number, etc.), and a back icon 512 to return to the basic screen 1000.

[0222] Furthermore, the RRT mode detail screen 1100, like the nurse mode detail screen 500, may include a list display image 520 that shows a list of multiple types of vital signs, the patient's vital sign measurements, the date and time of vital sign measurement, and the patient's individual score based on the vital signs. If all types of individual scores cannot be displayed at once in the list display image 520, healthcare professionals can view the desired individual scores by scrolling the list display image 520 vertically on the screen.

[0223] Furthermore, the list display image 520 of the RRT mode details screen 1100 may include marks 530 that indicate the change in the latest value of individual scores relative to the previous value, similar to the nurse mode details screen 500.

[0224] Furthermore, the RRT mode detail screen 1100 may include detail icons 550, trend icons 552, status icons 554, waveform display icons 556, and memo icons 558, similar to the nurse mode detail screen 500. When the mobile terminal 10 receives patient-related alarm information for the detail screen 1100 from the central monitor 20 via the server 12, it may display a history of the received alarm information at the bottom of the list display image 520.

[0225] The RRT mode detail screen 1100 may include an icon 542 labeled "Wait and See" and an icon 544 labeled "Request Proxy," similar to the nurse mode detail screen 500. On the other hand, the RRT mode detail screen 1100 does not need to include the call icon 540 labeled "RRS Call" in the nurse mode detail screen 500 (see Figure 8).

[0226] As mentioned above, nurses who are not RRT members are usually responsible for only a limited number of patients, making them more likely to notice changes in the condition of their assigned patients. Therefore, in the detailed screen 500 of the nurse mode (see Figure 8), a call icon 540 allows nurses to make RRS calls regarding their assigned patients.

[0227] On the other hand, RRT members are not assigned to specific patients, so in practice, they do not perform RRS calls. Therefore, it is not a problem if the call icon 540 is not included in the RRT mode details screen 1100.

[0228] The RRT mode detail screen 1100 may include a doctor call icon 1110 labeled "Doctor Call" instead of the call icon 540 (see Figure 8). When an RRT member is attending to a patient with RRS activated, they may sometimes need the assistance of a doctor. In such cases, the RRT member can call a designated doctor, i.e., make a doctor call, by performing an input operation on the doctor call icon 1110.

[0229] [13. Doctor Call] Next, the doctor call according to this embodiment will be described with reference to Figure 20. Figure 20 is a diagram showing an example of the doctor call screen 1200 that is displayed when an input operation is performed on the doctor call icon 1110.

[0230] A doctor call is an example of a call notification, a call notification that requests a doctor to attend to a patient. A call notification is a notification from one of several healthcare professionals associated with a patient, requesting another healthcare professional (the second healthcare professional) to attend to the patient. When the first healthcare professional (the source of the call notification) inputs a call notification into their mobile terminal 10, the call notification is sent from the first healthcare professional's mobile terminal 10 to the second healthcare professional's (the recipient of the call notification) mobile terminal 10 via the server 12. First healthcare professionals, such as nurses and RRT members, can send doctor calls using, for example, a doctor call screen 1200 as shown in Figure 20.

[0231] As shown in Figure 20, the doctor call screen 1200 may include a delete icon 1210 labeled "×". If an input operation is performed on the delete icon 1210, the user can return to the screen that was displayed immediately before the doctor call screen 1200.

[0232] The doctor call screen 1200 may include a notification candidate image 1220 that displays a list of potential recipients for the doctor call. For example, the notification candidate image 1220 illustrated in Figure 20 includes the names of the medical professionals who are candidates for the doctor call notification. The notification candidate image 1220 may also include role information of the medical professionals who are candidates for the doctor call notification. The notification candidates displayed in the notification candidate image 1220 are managed by the server 12.

[0233] The doctor call screen 1200 may include checkboxes 1222 corresponding to the candidate recipients of the doctor call in the candidate notification recipient image 1220. The requesting nurse or other healthcare professional (first healthcare professional) can add or remove checks to the checkboxes 1222. The candidate recipients corresponding to the checked checkboxes 1222 are set as the doctors (second healthcare professionals) to whom the doctor call will be notified. The recipients of the doctor call, i.e., the doctors who wish to be called by the doctor call, are not limited to one person but may be multiple people. In the doctor call screen 1200, the checkboxes 1222 of the pre-configured recipients may be initially checked. Note that checkboxes 1222 are an example of a selection tool for selecting the recipients of the doctor call.

[0234] The doctor call screen 1200 may include an input area 1230 where a message can be entered. The user of the mobile device 10 can freely write a message to contact the doctor who will be notified via the doctor call by performing an input operation on the input area 1230.

[0235] The doctor call screen 1200 may include an icon 1240 labeled "Doctor Call". When an input operation is performed on the icon 1240 labeled "Doctor Call", a doctor call notification is sent to the selected mobile terminal 10.

[0236] [14. Vitals Application] Next, we will explain what happens when an input operation is performed on the waveform display icon 556 in the detailed screen 500 of the nurse mode in Figure 8, or on the waveform display icon 556 in the detailed screen 1100 of the RRT mode in Figure 19. Figure 21 is a diagram showing an example of the waveform display screen 1300 displayed on the mobile terminal 10 of this embodiment.

[0237] When an input operation is performed on the waveform display icon 556 on the details screen 500 or details screen 1100, the mobile terminal 10 links the vital application 52 to the support application 50. The mobile terminal 10 then launches the vital application 52 from the support application 50 and displays the waveform display screen 1300 from the vital application 52 on the display device while the support application 50 is running. At this time, the mobile terminal 10 displays the waveform display screen 1300 for the patient identified on the details screen 500 or details screen 1100 of the support application 50.

[0238] As shown in Figure 21, the waveform display screen 1300 may include the display of the patient name 1310 and bed number as identification information for the patient being displayed. The waveform display screen 1300 may also include a back icon 1312 for returning from the vital signs screen to the support application details screen 500 or details screen 1100.

[0239] The waveform display screen 1300 includes waveform images 1320 that show real-time time-series changes in various vital signs.

[0240] The vital application 52 communicates with the vital server 24 in real time and acquires the vital signs of the patient to be displayed on the waveform display screen 1300 from the vital server 24 in real time. Based on the vital signs acquired in real time, the vital application 52 generates a waveform image 1320 and displays the generated waveform image 1320 on the vital screen.

[0241] The mobile terminal 10 can display the vital signs screen of the vital signs application from the detailed screen 500 or detailed screen 1100 of the support application. Therefore, healthcare professionals carrying the mobile terminal 10 can instantly check the real-time waveform of a specific patient's vital signs and understand the patient's condition.

[0242] [15. Trends screen] Next, the trend screen 1400 according to this embodiment will be described with reference to Figure 22. Figure 22 is a diagram showing an example of the trend screen 1400 according to this embodiment.

[0243] When an input operation is performed on the trend icon 552 on the details screen 500 (see Figure 8), the trend screen 1400 shown in Figure 22 is displayed on the display device of the mobile terminal 10. Similarly, when an input operation is performed on the trend icon 552 on the details screen 1100 (see Figure 19), the same trend screen 1400 is displayed as when an input operation is performed on the trend icon 552 on the details screen 500 (see Figure 8).

[0244] As shown in Figure 22, the trend screen 1400 includes a time-series image 1420 that illustrates the measurement results of a patient's vital signs over time, instead of the list display image 520 in the detail screen 500. The time-series image 1420 of the trend screen 1400 shows the time-series changes of multiple types of vital signs for a specific patient in graph format.

[0245] Furthermore, the trend screen 1400 may include multiple checkboxes 1422 that allow switching the display of multiple types of vital signs in the time-series image 1420. A checkbox 1422 is provided for each vital sign and is associated with each vital sign. Healthcare professionals can input checks or removes for each checkbox 1422. For example, in the time-series image 1420, the measurement results of one or more vital signs for which a checkbox 1422 is checked are displayed. On the other hand, vital signs for which a checkbox 1422 is not checked are not shown in the time-series image 1420.

[0246] For example, in time-series image 1420 and checkbox 1422, "blood pressure" may be associated with a solid line graph, "pulse rate" with a dashed line graph, "body temperature" with a dotted line graph, and "respiratory rate" with a double-dotted line graph. In the example in Figure 22, the graphs for "pulse rate," "body temperature," and "respiratory rate," for which checkbox 1422 is checked, are displayed as time-series image 1420. On the other hand, "blood pressure," for which checkbox 1422 is not checked, is not displayed in time-series image 1420.

[0247] In the initial state of the trend screen 1400, checkboxes 1422 may be checked for vital signs whose individual scores are above a predetermined threshold. Also, in the initial state of the trend screen 1400, pre-configured vital signs may be preferentially displayed as time-series images 1420. Since the vital signs to be displayed differ depending on the patient's disease, the vital signs displayed in the initial state may be set individually for each patient.

[0248] Furthermore, the trend screen 1400 may include multiple checkboxes 1424 that allow switching the time axis scale of the time series image 1420. For example, checking multiple checkboxes 1424 is mutually exclusive. The time series image 1420 is displayed at the scale selected by the checkboxes 1424.

[0249] In the time-series image 1420 of Figure 22, the display of vital sign measurements corresponding to the vertical axis is omitted. However, the time-series image 1420 may include the display of vital sign measurements in addition to the vital sign graph.

[0250] Healthcare professionals can comprehensively and intuitively grasp the time-series changes of multiple types of vital signs for a specific patient by checking the trend screen 1400 displayed on their mobile device 10. Furthermore, if the time-series image 1420 includes vital sign measurements, healthcare professionals can grasp the time-series changes of vital signs for a specific patient more accurately.

[0251] [16. Status Screen] Next, the status screen 1500 according to this embodiment will be described with reference to Figure 23. Figure 23 is a diagram showing an example of the status screen 1500 according to this embodiment.

[0252] When an input operation is performed on the status icon 554 of the details screen 500 (see Figure 8), the status screen 1500 shown in Figure 23 will be displayed on the display device of the mobile terminal 10. Similarly, when an input operation is performed on the status icon 554 of the details screen 1100 (see Figure 19), the same status screen 1500 will be displayed as when an input operation is performed on the status icon 554 of the details screen 500 (see Figure 8).

[0253] As shown in Figure 23, the status screen 1500 includes a history image 1520 that shows one or more response statuses for the patient in chronological order, instead of the list display image 520 in the details screen 500. As described above, the patient's response status changes sequentially each time a healthcare professional takes a response action for the patient (see Figure 7). The history image 1520 shown in Figure 23 is an image that clearly displays the history of changes in the patient's response status by such healthcare professionals in chronological order.

[0254] The history image 1520 includes, for example, response status images 1530 that represent response statuses that have occurred in the past for the patient being displayed. The response status images 1530 are displayed in the history image 1520 in the order in which the response statuses occurred, from top to bottom. The response status image 1530 is, for example, an example of an image representing a response status that shows the state of the patient's response by a healthcare professional in response to the various notifications mentioned above.

[0255] Furthermore, the history image 1520 may also include the display of the name 1540 of the healthcare professional represented in the response status image 1530, and the date and time when the response status occurred. The name 1540 of the healthcare professional is the name of the healthcare professional who caused the response status, or the name of the healthcare professional to whom the response status was notified. The name 1540 of the healthcare professional displayed in the history image 1520 is an example of the identification information of the healthcare professional who performed the response action related to each response status. The date and time when the response status occurred, displayed in the history image 1520, is an example of the time when the healthcare professional responded to the patient. In the example of the history image 1520 in Figure 23, the history of a "score notification" is shown by the response status image 1530 labeled "score notification," and the history of the recipient of the "score notification" is shown by the name 1540 of the healthcare professional labeled "Shizuoka Chacha."

[0256] Furthermore, the history image 1520 may include an input area 1550 where the latest response status for the patient can be entered. Also, the status screen 1500 shown in Figure 23 may include icons for entering the response status, such as a call icon 540, an icon labeled "wait and see" 542, and an icon labeled "request proxy" 544. Healthcare workers can enter the response status of the healthcare worker who responded to the patient by performing an input operation on the input area 1550 or on the icons. In other words, the status screen 1500 shown in Figure 23 is an example of an input screen (first input screen) for entering the response status. The mobile terminal 10 may perform a first input process to display the status screen 1500 (first input screen) in response to a notification. The mobile terminal 10 sends the response status entered by the healthcare worker on the input area 1550 or on the icons to the server 12 (first transmission process). Thus, when a healthcare professional enters the latest response status into the mobile terminal 10, the entered response status may be transmitted to the server 12 in association with the patient's identification information and recorded in the server 12's storage 66.

[0257] By checking the history image 1520 on the status screen 1500, healthcare professionals can easily and accurately understand the patient's treatment history, including the treatment status, the name of the healthcare professional who provided the treatment, and the time of the treatment. Therefore, each healthcare professional treating a patient can refer to the past treatment status history in the history image 1520 to take the next appropriate action for the patient.

[0258] [17. Memo screen] Next, the memo screen 1600 according to this embodiment will be described with reference to Figure 24. Figure 24 is a diagram showing an example of the memo screen 1600 according to this embodiment.

[0259] The memo screen 1600 is displayed when an input operation is performed on the memo icon 558 of the detailed screen 500 (see FIG. 8). When an input operation is performed on the memo icon 558 of the detailed screen 1100 (see FIG. 19), a memo screen 1600 substantially the same as when an input operation is performed on the memo icon 558 of the detailed screen 500 (see FIG. 8) is also displayed.

[0260] As shown in FIG. 24, the memo screen 1600 includes a memo list image 1620 that lists memos entered by medical staff about a patient, instead of the list display image 520 on the detailed screen 500. The memo list image 1620 includes a plurality of display blocks 1622 in which the content of the memo, the identification information of the medical staff who entered the memo (for example, the name of the medical staff), and the date and time when the memo was entered are associated and displayed. The display blocks 1622 are arranged in order from top to bottom in the memo list image 1620 in the order of the date and time when the memos were written.

[0261] The memo screen 1600 may include a memo input area 1630 where an input operation for creating a memo is possible, and a posting icon 1632 where the created memo can be posted to the memo list image 1620. By performing an input operation on the memo input area 1630, a medical staff can enter a new memo for the target patient. By performing an input operation on the posting icon 1632, a medical staff can post the memo created in the memo input area 1630 to the memo list image 1620. The new memo posted to the memo list image 1620 may be transmitted to the server 12 and recorded in the storage 66 of the server 12.

[0262] Thus, in this embodiment, the memo screen 1600 displayed on the mobile terminal 10 of each medical staff member enables easy input of memos regarding the patient's condition and response details by multiple medical staff members, and sharing of the memo history among multiple medical staff members. For this purpose, in this embodiment, when a medical staff member who has dealt with a patient enters a memo on the memo screen 1600 of the mobile terminal 10 of that medical staff member, the mobile terminal 10 transmits memo information including the entered memo, the memo entry time (e.g., entry date and time), and the identification information of the medical staff member who entered the memo to the server 12. Then, the server 12 records the memo information received from the mobile terminal 10 as patient information in the storage 66. Thereafter, when each medical staff member uses the mobile terminal 10 to check patient information, the server 12 causes the mobile terminal 10 to display the memo list image 1620 of the memo screen 1600 based on the above-mentioned memo information included in the patient information recorded in the storage 66. As shown in FIG. 24, this memo list image 1620 is an image that lists a plurality of memos entered by a plurality of medical staff members corresponding to a patient in chronological order for each patient.

[0263] Medical staff members can collectively check the memos individually entered by a plurality of medical staff members for the target patient through the memo list image 1620 on the memo screen 1600 displayed on the mobile terminal 10. In addition, medical staff members can also check the content of the memos entered by other medical staff members, the names of the memo enterers, and the entry dates and times through the memo list image 1620. Thereby, a plurality of medical staff members can appropriately and smoothly share information to be shared and convey matters to be postponed for the target patient by looking at the memo screen 1600.

[0264] [18. Recording of Information and Creation of Report] Next, referring to FIG. 25, the recording of various information by the server 12 according to this embodiment and the creation of a report using the recorded various information will be described. FIG. 25 is a diagram for explaining the recording of various information by the server 12 according to this embodiment and the creation of a report 1700 using the recorded various information.

[0265] Healthcare workers operate a mobile terminal 10 running a support application 50 at various points in time when performing various actions related to patients. The mobile terminal 10 communicates with the server 12 as appropriate in response to the various operations performed by the healthcare workers. In this way, the server 12 can obtain various information about the patient from, for example, multiple mobile terminals 10. The server 12 can also obtain various information about the patient and healthcare workers from, for example, a client PC 14, an electronic medical record server 16, a bedside monitor 18, a central monitor 20, a spot check device 22, a vital signs server 24, etc. The server 12 records the various patient information obtained from each device, such as the mobile terminals 10, in storage 66 and manages it for each patient.

[0266] Here, various patient information includes, for example, the basic patient information mentioned above (e.g., patient's name, ID, ward information, etc.), information on the measurement and score of the patient's vital signs, response history information regarding the patient's response status by healthcare professionals, information on notes written by healthcare professionals, and configuration information that sets up the link between the patient and healthcare professionals. Response history information includes notification information (e.g., information on call notifications such as RRS calls, doctor calls, and proxy requests, score notifications, system notifications, etc.).

[0267] For example, as shown in Figure 25, when a healthcare professional (e.g., a nurse) uses the mobile terminal 10 to input information to the call execution icon 640 on the RRS call screen 600, the server 12 records notification information representing the history of RRS call notifications as response history information. Also, as shown in Figure 25, when a healthcare professional uses the mobile terminal 10 to input information to the pull-down menu screen 700 and selects a reason for requesting an RRS call, the server 12 records information representing the reason for requesting an RRS call selected by the pull-down menu screen 700, along with the notification information for the RRS call notification, as response history information.

[0268] Furthermore, as shown in Figure 25, when a healthcare professional enters a response status regarding a patient on the status screen 1500, the server 12 records the response history information related to that response status. Also, for example, when a healthcare professional enters a memo about a patient on the memo screen 1600, the server 12 records that memo information.

[0269] Furthermore, the information recorded by server 12 may include not only the information exemplified above, but also various other types of information concerning patients and healthcare workers.

[0270] As described above, each time a healthcare professional interacts with a patient, the server 12 records the history of the healthcare professional's interaction with the patient in the storage 66. More specifically, the server 12 records the following in the storage 66 as interaction history information: notification information regarding the notification requesting a healthcare professional to interact with the patient, the time the notification was sent, the interaction status representing the interaction with the patient by the healthcare professional who responded to the notification, and the time of the healthcare professional's interaction (e.g., interaction date and time).

[0271] Here, notifications may include, for example, score notifications, RRS call notifications, doctor calls, proxy request notifications, proxy unavailable notifications, alarm notifications, etc. The response status may include the response status resulting from these various notifications (see Figure 7). The response status may also include, for example, waiting, RRS call, proxy request, etc. (see Figure 7).

[0272] Medical professionals and other hospital staff, such as administrative staff, may prepare various reports 1700 (see Figure 25) concerning patients. These reports 1700 may be prepared, for example, using a client PC 14.

[0273] The client PC 14 may output information arranged chronologically for each patient, including notification information for multiple notifications and response statuses for multiple response actions, in the format of a report of the response history of multiple healthcare professionals to a patient. In other words, the report 1700 may be a document containing a list of notification information and response statuses arranged chronologically for each patient.

[0274] Furthermore, the client PC 14 is not limited to outputting information in a report format such as report 1700, which is written in a prescribed format set by the hospital. In other words, the client PC 14 may output information in various display formats other than the report format, which is a chronological arrangement of multiple notification information and multiple response statuses for each patient, based on the response history information recorded in the server 12's storage 66.

[0275] In this way, according to this embodiment, information (for example, report 1700) is output in which multiple notification information and multiple response statuses are arranged chronologically for each patient. As a result, healthcare professionals, healthcare managers, hospital administrators, and public institution personnel can easily and appropriately grasp the history and status of responses to each patient by checking the output information.

[0276] Figure 26 is a sequence diagram illustrating the flow of creating the report 1700 according to this embodiment. As shown in Figure 26, the client PC 14 selects a patient to be included in the report 1700 (S120). The client PC 14 sends the identification information of the selected patient and request information requesting response history information for that patient to the server 12 (S121). The request information requesting response history information may include, for example, information requesting multiple notification information, the time the notification was sent, multiple response statuses, and the time the medical professional responded, as response history information.

[0277] When server 12 receives patient identification information and request information from client PC 14, it refers to the patient identification information and selects the response history information to send from the response history information recorded in storage 66 (S122). Server 12 sends the selected response history information to client PC 14 (S123). The response history information sent to client PC 14 includes multiple notification information, the time the notification was sent, multiple response statuses, and the time the medical professional responded.

[0278] When client PC 14 receives response history information, which includes multiple notification information, the time the notification was sent, multiple response statuses, and the time the medical professional responded, it creates a report 1700 based on the received response history information (S124). Client PC 14 records the created report 1700 in storage 96 (S125). In this way, report 1700 can be created.

[0279] Thus, according to the medical management system 1 of this embodiment, the response history information recorded on the server 12 is used to generate information (for example, a report 1700) in which multiple notification information and multiple response statuses are arranged chronologically for each patient. This response history information is information accumulated through centralized management in which information for many patients is managed by many medical professionals using the server 12. On the other hand, by performing distributed management using the mobile terminals 10 of some medical professionals in charge of each patient, various information such as notification information and response statuses that form the basis of the above-mentioned response history information are efficiently and accurately collected from multiple mobile terminals 10 to the server 12.

[0280] As described above, according to the medical management system 1 according to this embodiment, in order to realize RRS, a centralized management in which the server 12 is used to manage the information of a large number of patients by a large number of medical staff, and a decentralized management in which only the information of each assigned patient is managed using the mobile terminal 10 of each medical staff are used in combination, and the information of a plurality of patients can be efficiently managed. Therefore, it is possible to reduce the processing load of the medical management system 1 required for creating information (for example, the report 1700) summarizing the response history of each patient, and the labor of hospital medical staff, clerks, and the like.

[0281] [19. Linking between Information] [19.1. Settings in Server] Next, referring to FIG. 27, the setting of the linking between patients and medical staff according to this embodiment will be described. FIG. 27 is a diagram showing an example of a setting screen 1800 for setting the linking between patients and medical staff according to this embodiment.

[0282] The server 12 manages the linking between a plurality of patients admitted to the hospital and a plurality of medical staff belonging to the hospital. The setting screen 1800 is a screen for setting the linking between patients and medical staff. In this embodiment, for example, the setting screen 1800 is displayed on the display device of the server 12, and an example of setting the linking between patients and medical staff by the server 12 will be described. However, it is not limited to such an example. For example, the setting screen 1800 may be displayed on a display device such as the mobile terminal 10, the client PC 14, or the central monitor 20 to set the linking between patients and medical staff.

[0283] As shown in Figure 27, the settings screen 1800 includes a list display image 1810 that displays a list of identification information for multiple patients (e.g., patient names) and identification information for multiple healthcare professionals (e.g., healthcare professional names). The list display image 1810 is displayed such that the identification information for multiple patients is arranged in a first direction (e.g., the vertical direction of the settings screen 1800), and the identification information for multiple healthcare professionals is arranged in a second direction that intersects with the first direction (e.g., the horizontal direction of the settings screen 1800). In other words, in the list display image 1810, the identification information for multiple patients and the identification information for multiple healthcare professionals are arranged in a matrix and displayed in a list.

[0284] The list display image 1810 includes multiple checkboxes 1812 positioned at the intersection of the display fields for each patient's identification information and the display fields for each healthcare worker's identification information. The checkboxes 1812 are also arranged in a matrix.

[0285] In the settings screen 1800, patients and healthcare professionals corresponding to checkboxes 1812 that have a check mark are linked in the list display image 1810. On the other hand, patients and healthcare professionals corresponding to checkboxes 1812 that do not have a check mark are not linked.

[0286] The person setting up the patient-healthcare worker link can add or remove a checkbox 1812 by performing an input operation on it. In other words, the person setting up the link can add a checkbox 1812 at the intersection of the patient's identification information and the healthcare worker's identification information. This input operation sets up the patient-healthcare worker link. By adding a check to the desired checkbox 1812, the person setting up the link can easily and accurately set up the patient-healthcare worker link.

[0287] The list display image 1810 of the settings screen 1800 may include a highlight image 1814 that highlights the identification information of a patient who is not associated with any healthcare professional.

[0288] The highlighting image 1814 displays the identification information of patients not associated with any healthcare professional (hereinafter sometimes referred to as "associated patients") in a manner that is visually distinguishable from the identification information of patients already associated with one or more healthcare professionals. For example, the highlighting image 1814 may highlight the frame surrounding the identification information of the associated patients. Alternatively, the highlighting image 1814 may highlight the display area of ​​the identification information of the associated patients. Furthermore, the highlighting image 1814 may highlight the font of the identification information of the associated patients.

[0289] Furthermore, as the highlighted image 1814, not only the identification information of the linked patient but also the multiple checkboxes 1812 corresponding to the identification information of the linked patient may be highlighted.

[0290] By viewing the enhanced image 1814, the administrator can quickly and easily identify patients who are not linked to any healthcare professional. As a result, the server 12 can suppress the occurrence of linking errors, and even if linking errors occur, it can recover from them quickly.

[0291] Furthermore, in the list display image 1810, patient identification information that is not linked to any healthcare professional may be displayed in a higher position than patient identification information that is already linked to one or more healthcare professionals.

[0292] By displaying the identification information of patients not linked to any healthcare professional at a higher position, it becomes easier for the person setting up the system to identify patients who should be linked to a healthcare professional.

[0293] Furthermore, if a new patient is added, the server 12 may perform a default setting process to associate at least one medical professional belonging to the ward where the newly added patient is hospitalized with the newly added patient, based on the ward information where the newly added patient is hospitalized and the ward information where the medical professionals belong.

[0294] The default configuration process may be performed when a new patient is added to the list of patients monitored for RRS due to a new patient's admission. In the default configuration process, the healthcare professionals associated with the newly added patient may be set as the default notification recipients for that patient. Alternatively, for example, the default configuration process may associate multiple healthcare professionals and all RRT members who are responsible for the same ward as the newly admitted patient with that patient.

[0295] The default configuration process effectively avoids a situation where newly added patients are not linked to any healthcare professionals, and therefore, the risk status of those patients is not notified to any healthcare professionals.

[0296] The list view image 1810 may include a first scroll bar 1820 and a second scroll bar 1822. The first scroll bar 1820 is displayed when the patient identification information for the first direction cannot be fully displayed within the list view image 1810. By operating the first scroll bar 1820, the user can move the display range for the first direction to the first direction. The second scroll bar 1822 is displayed when the medical professional identification information for the second direction cannot be fully displayed within the list view image 1810. By operating the second scroll bar 1822, the user can move the display range for the second direction to the second direction.

[0297] The settings screen 1800 may display, for patients, patient identification information as well as information about the ward in which the patient is hospitalized (e.g., ward name, ward floor). The settings screen 1800 may also display, for healthcare professionals, healthcare professional identification information as well as information about the ward to which the healthcare professional belongs (e.g., ward name, ward floor). This allows the user to efficiently and appropriately link patients and healthcare professionals by referring to the ward information.

[0298] The settings screen 1800 may have a filtering function that narrows down the patient identification information to be displayed in the list image 1810 from among all patients in the hospital, based on the patient's ward information.

[0299] More specifically, the settings screen 1800 may include a patient selection image 1830 that can accept input from the user to narrow down the patient's identification information. The patient selection image 1830 includes the patient's ward information. The patient selection image 1830 may also include multiple checkboxes 1832 corresponding to the ward information.

[0300] The user can input whether to check or remove checkboxes 1832 in the patient selection image 1830. On the settings screen 1800, patients in wards corresponding to checkboxes 1832 that have been checked are displayed as list display image 1810. On the other hand, on the settings screen 1800, patients in wards corresponding to checkboxes 1832 that have not been checked are not displayed in list display image 1810. In other words, by inputting information on checkboxes 1832 in the patient selection image 1830, the user can narrow down the list display image 1810 to show only patients in the desired wards.

[0301] Furthermore, patient selection image 1830 may include an image that highlights ward information containing patients who are not associated with any healthcare professional, for each ward information corresponding to checkbox 1832.

[0302] The settings screen 1800 may have a filtering function that narrows down the identification information of medical personnel to be displayed as a list image 1810 from among all medical personnel belonging to the hospital, based on the medical personnel's ward information.

[0303] More specifically, the settings screen 1800 may include a healthcare professional selection image 1840 that can accept input from the user to narrow down the identification information of healthcare professionals. The healthcare professional selection image 1840 includes the healthcare professional's ward information. The healthcare professional selection image 1840 may also include a pull-down menu containing the healthcare professional's ward information.

[0304] The user can input information into the pull-down menu on the healthcare professional selection image 1840. On the settings screen 1800, healthcare professionals who meet the criteria selected by the pull-down menu are displayed as a list image 1810. On the other hand, healthcare professionals who do not meet the criteria selected by the pull-down menu are not displayed in the list image 1810. In other words, by inputting information into the pull-down menu on the healthcare professional selection image 1840, the user can narrow down the list of healthcare professionals in the desired ward and display them in the list image 1810.

[0305] Furthermore, the settings screen 1800 may have a filtering function that narrows down the identification information of healthcare workers to be displayed as a list image 1810 from among all healthcare workers belonging to the hospital, based on the role information of the healthcare workers. The role information of healthcare workers may include, for example, occupational information such as nurses and doctors, or it may include role information such as assigned nurses who are not members of the RRT, and nurses who are members of the RRT.

[0306] More specifically, the healthcare professional selection image 1840 may include information about the healthcare professional's role. The healthcare professional selection image 1840 may also include a pull-down menu containing information about the healthcare professional's role. By performing input operations on the pull-down menu in the healthcare professional selection image 1840, the user can narrow down the list of healthcare professionals with the desired role and display them in the list display image 1810.

[0307] In this way, the system administrator can smoothly and efficiently link desired patients with desired healthcare professionals by using a filtering function that narrows down the identification information of patients and healthcare professionals.

[0308] [19.2. Linking mobile devices to healthcare workers] Next, with reference to Figure 28, the linking of the mobile terminal 10 with the medical professional who possesses the mobile terminal 10 will be described. Figure 28 is a diagram showing an example of a table 1900 that links the mobile terminal 10 with the medical professional who possesses the mobile terminal 10 and the operating mode of the mobile terminal 10 according to this embodiment. The table 1900 illustrated in Figure 28 is recorded as information about the medical professional, for example, in the storage 66 of the server 12.

[0309] As shown in Figure 28, multiple mobile terminals 10 are associated with each other by their respective identification information (e.g., mobile terminal ID), the identification information of the healthcare professional who possesses the mobile terminal 10 (e.g., the healthcare professional's name), the healthcare professional's role, and the operating mode of the mobile terminal 10. The healthcare professional's role may be categorized into, for example, nurses other than RRTs, RRTs, and doctors. In Figure 28, nurses other than RRTs are simply referred to as nurses. The operating modes of the mobile terminals 10 are classified into nurse mode and RRT mode. Table 1900 may also include the ward information of the healthcare professional who possesses the mobile terminal 10.

[0310] For example, in the example in Table 1900 of Figure 28, mobile device "A" is owned by "Fukuda Hanako," a nurse who is not an RRT, and is set to nurse mode. Mobile device "B" is owned by "Shizuoka Chacha," a nurse who is not an RRT, and is set to nurse mode. Mobile device "C" is owned by "Fuji Ayako," an RRT, and is set to RRT mode. Mobile device "D" is owned by "Odawara Futoshi," a doctor, and is set to RRT mode.

[0311] By referring to table 1900, server 12 can identify the healthcare professional who possesses a mobile terminal 10 from the identification information of the mobile terminal 10, and can also identify the mobile terminal 10 possessed by that healthcare professional from the identification information of the healthcare professional. Therefore, server 12 can identify the mobile terminal 10 of the healthcare professional to whom notifications such as score notifications and RRS call notifications are received. Furthermore, when server 12 receives a notification such as a score notification or RRS call notification from a mobile terminal 10, it can also identify the healthcare professional who sent the notification from the identification information of the mobile terminal 10.

[0312] [19.3. Settings on mobile devices] Next, the confirmation of settings in the mobile terminal 10 will be described with reference to Figures 29 and 30. Figure 29 is a diagram showing an example of the settings screen 2000 of the support application 50 in the mobile terminal 10 according to this embodiment. The settings screen 2000 may be displayed on the display device of the mobile terminal 10 in response to input operations on icons 414 on the basic screen 400 or basic screen 1000, for example.

[0313] As shown in Figure 29, the settings screen 2000 may include a delete icon 2010 labeled "×". If an input operation is performed on the delete icon 2010, the user can return to the screen immediately preceding the settings screen 2000.

[0314] The settings screen 2000 may include the display of various settings items 2020. Furthermore, the settings screen 2000 may include icons 2022 that allow transition to a screen where detailed settings for the settings items 2020 can be configured.

[0315] The multiple settings items 2020 may include, for example, an item labeled "User Settings" that allows setting the association between the mobile device 10 and its user (owner). In the example in Figure 29, "Shizuoka Chacha," a healthcare worker, is set as the user (owner) of the mobile device 10. If multiple healthcare workers share one mobile device 10 in turns, the user may be selected in "User Settings," and the selected user's password may be entered to set the association between the selected user and the mobile device 10.

[0316] Furthermore, the multiple setting items 2020 may include, for example, an item labeled "Patient Notification Settings" that allows for the setting of a link between the mobile device 10 and the patient (in other words, a link between the healthcare worker possessing the mobile device 10 and the patient).

[0317] Next, with reference to Figure 30, the patient notification setting screen 2100 according to this embodiment will be described. Figure 30 is a diagram showing an example of the patient notification setting screen 2100 in the mobile terminal 10 according to this embodiment. When an input operation is performed on the icon 2022 corresponding to "Patient Notification Settings" on the setting screen 2000 (see Figure 29), the patient notification setting screen 2100 shown in Figure 30 is displayed. The patient notification setting screen 2100 is a screen for healthcare workers to set at least one patient under their care.

[0318] As shown in Figure 30, the patient notification settings screen 2100 may include a back icon 2110 for returning to the settings screen 2000.

[0319] The patient notification settings screen 2100 may include an input area 2120 where the settings related to patient notification settings can be selected. The input area 2120 may be selectable via a pull-down menu. In the example in Figure 30, "Current 담당" (current 담당) is selected as the setting.

[0320] The patient notification settings screen 2100 may include a display area 2130 that displays the settings target according to the settings selected in the input area 2120. In the example in Figure 30, the setting "Current Assignment" is selected in the input area 2120. In this case, the display area 2130 may display a list of patient names currently assigned to the healthcare worker who possesses the mobile terminal 10.

[0321] The display area 2130 may include a checkbox 2140 for each setting target (i.e., for each patient displayed in the display area 2130). The settings targets and checks of the checkboxes 2140 displayed in the display area 2130 may be displayed as initial values ​​pre-configured in the server 12. Healthcare workers possessing a mobile terminal 10 can add or remove checks to the checkboxes 2140 by performing input operations on the checkboxes 2140 for each setting target.

[0322] On the patient notification settings screen 2100, patients with a checkbox 2140 checked are set as patients assigned to the healthcare worker who possesses the mobile device 10. This allows the mobile device 10 to receive notifications about patients who have been assigned to that patient.

[0323] The patient notification settings screen 2100 may include, for example, an icon 2150 labeled "Select All". When an input operation is performed on the icon 2150, all checkboxes 2140 in the display area 2130 can be checked.

[0324] The patient notification settings screen 2100 may include a setting execution icon 2160 labeled "Confirm". When an input operation is performed on the setting execution icon 2160, the patient notification settings on the patient notification settings screen 2100 are sent to the server 12, and the patient notification settings are updated.

[0325] In this way, healthcare professionals can set up and confirm the link between healthcare professionals and patients (in other words, the link between the mobile device 10 and the patient) by performing setting operations on the patient notification setting screen 2100 of the mobile device 10. This increases the flexibility of the linking, so that the linking of patients and healthcare professionals in the medical management system 1 can be flexibly operated according to the situation of each hospital, and RRS compliance can be effectively supported.

[0326] [20. Summary] As described above, according to the medical management system 1 of this embodiment, in order to appropriately realize the above RRS, the server 12 collects and stores information on a large number of patients and a large number of medical professionals from various devices such as each medical professional's mobile terminal 10, electronic medical record server 16, bedside monitor 18, central monitor 20, spot check device 22, and manages them centrally. As a result, the server 12 can efficiently manage information on multiple patients and multiple medical professionals (for example, basic information on medical professionals, basic information on patients, setting information linking medical professionals and patients, measurement data of patients' vital signs, score information on patients' vital signs, notification information between medical professionals, response status information by medical professionals, memo information by medical professionals, etc.).

[0327] On the other hand, each healthcare worker's mobile device 10 can extract and display only information about a subset of patients under their care (for example, basic information about the patient, vital sign measurement data for the patient, vital sign score information for the patient, notification information between healthcare workers, status information of the healthcare worker's response, and memo information from the healthcare worker), and present this information to each healthcare worker efficiently and appropriately. Therefore, each healthcare worker can quickly check and respond to sudden changes in the condition of their assigned patients among a large number of patients, and can focus on understanding the risks to their assigned patients and respond quickly.

[0328] Thus, according to this embodiment, by using a combination of centralized management, in which a server 12 is used to manage information on a large number of patients by a large number of medical professionals, and distributed management, in which each medical professional uses their mobile terminal 10 to manage information on only the patients they are responsible for, it is possible to efficiently manage information on multiple patients and multiple medical professionals. Therefore, it is possible to support a rapid response to changes in each patient's condition, and thus a RRS can be suitably implemented within a medical institution such as a hospital.

[0329] [20.1. Summary of the first aspect of this disclosure] According to the first aspect of this disclosure, the following configuration can be provided:

[0330] (1) A medical management system comprising a server for managing patient information relating to multiple patients and a mobile terminal for medical professionals, The recording process includes recording the patient identification information, a total score calculated from multiple types of vital signs of the patient, and at least one individual score calculated from one type of vital sign of the patient on the server. Based on the patient information recorded on the server, a display process is performed to associate the identification information relating to at least one patient with the total score and the individual score, and to display it on the mobile terminal. A medical management system that performs this task.

[0331] (2) The recording process includes recording the response status, which represents the response status of the patient by the medical professional, as patient information. The medical management system according to (1), wherein the display process associates the patient's identification information, total score, and individual score with the patient's corresponding status and displays them on the mobile terminal.

[0332] (3) When the patient's vital signs are abnormal, or when the patient's total score or individual score is updated, the change in the patient's response status is recorded on the server, and the change in the response status is notified to the mobile terminal of the healthcare worker associated with the patient. (2) The medical management system described above, which displays the changed response status on the mobile terminal in response to notification of a change in the response status.

[0333] (4) When the medical professional who provided care to the patient enters the care status into the medical professional's mobile terminal, the entered care status is recorded on the server. The medical management system according to (2) or (3), which notifies the mobile terminal of the medical professional associated with the patient of the change in the response status and displays the changed response status on the mobile terminal.

[0334] (5) In the display process, a list image of patient information, in which the corresponding status, identification information, total score, and individual score for multiple patients are associated with each patient, is displayed on the mobile terminal. The medical management system according to any one of (2) to (4), wherein the patient information of the multiple patients is sorted and displayed in the list display image based on the priority of the corresponding status.

[0335] (6) In the display process, a list image of patient information, in which the identification information, total score, and individual score for each of the multiple patients are associated with each patient, is displayed on the mobile terminal. The medical management system according to any one of (1) to (5), wherein the mobile terminal of the medical professional displays the patient information of the patient associated with the medical professional from among the multiple patients whose patient information is recorded on the server, and does not display the patient information of the patient not associated with the medical professional.

[0336] (7) The medical management system according to (6), wherein in the list display image, the patient information of the patient associated with the medical professional is sorted and displayed such that, among multiple notifications relating to the patient associated with the medical professional, the patient information including notifications not yet confirmed by the medical professional is displayed at the top.

[0337] (8) The medical management system according to (6) or (7), wherein the list display image is sorted and displayed in descending order of the total score of the patients associated with the medical professionals.

[0338] (9) The medical management system according to any one of (6) to (8), wherein in the list display image, the identification information for the multiple patients, the latest value of the total score, the previous value of the total score, and the individual score for each patient are associated with each patient.

[0339] (10) The mobile terminal has a function to narrow down the patients to be displayed in the list display image, The medical management system described in any one of items (6) to (9), wherein the function for narrowing down the patients to be displayed varies depending on the role of the medical professional who possesses the mobile terminal.

[0340] (11) The medical management system according to any one of items (1) to (10), wherein the display process displays the individual score with the highest score value among the multiple types of individual scores.

[0341] (12) The medical management system according to (11), wherein in the display process, if there are multiple individual scores with the highest score value, at least one of the multiple individual scores is displayed based on a pre-set display priority for individual scores.

[0342] (13) When a memo concerning the patient is written on the medical professional's mobile device by the medical professional who attended to the patient, the written memo and the time the memo was written are recorded on the server as patient information. A medical management system according to any one of (1) to (12), wherein, based on the patient information recorded on the server, the mobile terminal displays a list of multiple memos written by multiple medical professionals, arranged chronologically for each patient.

[0343] (14) The mobile terminal is A vital signs application that displays the patient's vital signs, A support application to assist in the care of the aforementioned patient,

[0344] Equipped with, A medical management system according to any one of (1) to (13), wherein, in response to an input operation by a medical professional on the mobile terminal to the support application, the support application and the vital application are linked, and an image showing the time-series changes of the vital signs generated by the vital application is displayed on the mobile terminal.

[0345] (15) A portable terminal for healthcare workers configured to communicate with a server that manages patient information for multiple patients, A receiving process that receives from the server the following patient information from the aforementioned patient information: at least one patient identification information, a total score calculated from multiple types of vital signs of the patient, and at least one individual score calculated from one type of vital sign of the patient. A display process that associates the identification information relating to the patient with the total score and the individual score, A mobile device that performs [some action].

[0346] (16) A mobile terminal for healthcare workers configured to communicate with a server that manages patient information for multiple patients, A receiving process that receives from the server the following patient information from the aforementioned patient information: at least one patient identification information, a total score calculated from multiple types of vital signs of the patient, and at least one individual score calculated from one type of vital sign of the patient. A display process that associates the identification information relating to the patient with the total score and the individual score, A program to execute.

[0347] [20.2. Summary of the second perspective of this disclosure] According to the second aspect of this disclosure, the following configuration can be provided:

[0348] (1) A medical management system equipped with a server for managing patient care history information by medical professionals, The aforementioned response history information includes a recording process that records, in association with the patient's identification information, notification information relating to a notification requesting the medical professional to respond to the patient, the time the notification was sent, a response status representing the status of the medical professional's response to the patient in response to the notification, and the time the medical professional responded. Based on the correspondence history information recorded on the server, an output process is performed to output multiple notification information and multiple correspondence statuses arranged chronologically for each patient. A medical management system that performs this task.

[0349] (2) The medical management system is The aforementioned mobile terminal for medical personnel Furthermore, The server performs a notification process that sends the notification to the mobile terminal of the medical professional associated with the patient, In response to the notification, the mobile terminal of the healthcare worker corresponding to the patient displays a first input screen for entering the corresponding status; The mobile terminal performs a first transmission process in which it transmits the corresponding status entered on the first input screen by the medical professional to the server, The medical management system described in (1) further implements the following.

[0350] (3) The medical management system is The aforementioned mobile terminal for medical personnel Furthermore, The notification includes a call notification in which one of the multiple healthcare professionals associated with the patient requests another healthcare professional to attend to the patient. The first input process involves the mobile terminal of the first medical professional displaying a first input screen for inputting the corresponding status, The first medical professional's mobile terminal displays a second input screen for inputting the reason for the call notification, and The first medical professional's mobile terminal performs a second transmission process which transmits to the server the response status representing the call notification entered by the first medical professional on the first input screen, and the reason for the request entered on the second input screen. The server performs a notification process to send the call notification and the reason for the request to the mobile terminal of the second medical professional,

[0351] Further execution, The medical management system according to (1) or (2), wherein the recording process includes recording the notification information, the reason for the request, and the transmission time related to the call notification in association with the patient's identification information on the server as correspondence history information, and recording the response status and response time of the second medical professional who responded to the patient in response to the call notification in association with the patient's identification information on the server.

[0352] (4) The server has recorded configuration information that links the patient and the medical professional, The medical management system according to (3), wherein, based on the setting information, the second input screen displays identification information of the second medical professional who is a candidate to whom the call notification will be sent, and a selection tool for selecting the medical professional to whom the call notification will be sent from among the second medical professionals.

[0353] (5) The server sequentially receives from the mobile terminals of multiple healthcare workers corresponding to the patient in response to each of the multiple notifications a plurality of response statuses representing the response status of the patient by each of the multiple healthcare workers.

[0354] Further execution, The medical management system according to any one of (2) to (4), wherein the recording process records the notification information and transmission time for multiple notifications in association with the patient's identification information on the server, and records the response status and response time for multiple notifications in association with the patient's identification information on the server.

[0355] (6) The medical management system according to (5), wherein the output processing outputs information arranged chronologically for each patient, consisting of the notification information relating to the multiple notifications and the multiple response statuses, in the form of a report of the response history of the multiple medical professionals to the patient.

[0356] (7) In the recording process, the identification information of the medical professional corresponding to the patient in response to the notification is recorded on the server in association with the patient's identification information. The medical management system according to any one of (1) to (6), wherein the output processing outputs the notification information relating to multiple notifications, the corresponding statuses, and the identification information of the medical professional corresponding to the multiple notifications, arranged in chronological order for each patient.

[0357] (8) Recording process that records, as patient response history information by medical personnel, notification information relating to a notification requesting medical personnel to respond to the patient, the time the notification was sent, a response status indicating the response status of the medical personnel who responded to the patient in response to the notification, and the time the medical personnel responded, in association with the patient's identification information. Based on the aforementioned correspondence history information, an output process is performed to output multiple notification information and multiple correspondence statuses arranged chronologically for each patient. A server that executes this process.

[0358] (9) To the server, Recording process that records, as patient care history information by healthcare professionals, notification information regarding a notification requesting care from the healthcare professional to the patient, the time the notification was sent, the response status representing the healthcare professional's response to the patient in response to the notification, and the time the healthcare professional responded, all associated with the patient's identification information. Based on the aforementioned correspondence history information, an output process is performed to output multiple notification information and multiple correspondence statuses arranged chronologically for each patient. A program to execute.

[0359] (10) A portable terminal for healthcare workers configured to communicate with a server that manages patient care history information by healthcare workers, The process of receiving a notification from the server requesting the medical professional to take action regarding the patient, A first input process that displays a first input screen for inputting a response status representing the response status of the patient by the medical professional in response to the notification, A first transmission process that transmits the corresponding status entered by the medical professional on the first input screen to the server, A display process that displays multiple response statuses for the patient in chronological order based on the response history information recorded on the server, A mobile device that performs [some action].

[0360] (11) A mobile terminal for healthcare workers that is configured to communicate with a server that manages patient care history information by healthcare workers, The process of receiving a notification from the server requesting the medical professional to take action regarding the patient, A first input process that displays a first input screen for inputting a response status representing the response status of the patient by the medical professional in response to the notification, A first transmission process that transmits the corresponding status entered by the medical professional on the first input screen to the server, A display process that displays multiple response statuses for the patient in chronological order based on the response history information recorded on the server, A program to execute.

[0361] [20.3. Summary of the third perspective of this disclosure] According to a third aspect of this disclosure, the following configuration can be provided:

[0362] (1) A medical management system equipped with a server that manages the linking of multiple patients with multiple healthcare professionals, A process for acquiring or setting first basic information including identification information of the aforementioned multiple patients, A process for acquiring or setting second basic information, which includes the identification information of the aforementioned multiple medical professionals, A display process that displays a settings screen for setting up the association between the multiple patients and the multiple healthcare professionals based on the first basic information of the multiple patients and the second basic information of the multiple healthcare professionals, A setting process that sets up the association between the multiple patients and the multiple healthcare professionals based on the input operation on the setting screen, A medical management system that performs this task.

[0363] (2) The first basic information of the patient further includes information about the ward in which the patient is hospitalized, The aforementioned second basic information of the medical professional further includes information about the ward to which the medical professional belongs. The medical management system according to (1), wherein the display process displays the patient's identification information and ward information, and the medical personnel's identification information and ward information on the settings screen.

[0364] (3) The medical management system according to (2), wherein the settings screen has a filtering function that narrows down the identification information of the patient and the medical personnel displayed on the settings screen based on the ward information of the patient and the medical personnel.

[0365] (4) The second basic information of the healthcare worker further includes the role information of the healthcare worker, The medical management system according to any one of (1) to (3), wherein the settings screen has a filtering function that narrows down the identification information of the medical professional displayed on the settings screen based on the role information of the medical professional.

[0366] (5) The medical management system according to any one of (1) to (4), wherein in the display process, the patient identification information that has not yet been associated with the medical professional is highlighted on the settings screen so that it can be distinguished from the patient identification information that has already been associated with the medical professional.

[0367] (6) The medical management system according to any one of (1) to (5), wherein in the display process, the patient identification information that has not yet been associated with the medical professional is displayed in a higher position on the settings screen than the patient identification information that has already been associated with the medical professional.

[0368] (7) The first basic information of the patient further includes information about the ward in which the patient is hospitalized, The aforementioned second basic information of the medical professional further includes information about the ward to which the medical professional belongs. Based on the ward information in which the newly added patient is hospitalized and the ward information to which the medical professional belongs, a default setting process is performed to associate at least one of the medical professionals belonging to the ward in which the newly added patient is hospitalized with the newly added patient. A medical management system described in any one of items (1) to (6) further implements the above.

[0369] (8) The medical management system according to any one of (1) to (7), wherein in the display process, the identification information of the plurality of patients and the identification information of the plurality of medical personnel are arranged in a matrix and displayed in a list on the setting screen such that the identification information of the plurality of patients is arranged in a first direction and the identification information of the plurality of medical personnel is arranged in a second direction intersecting the first direction.

[0370] (9) In the display process, on the settings screen, a checkbox is placed at the position where the display field for each patient's identification information and the display field for each medical professional's identification information intersect in the matrix-like list display. The medical management system according to (8), wherein the setting process sets up the association between the patient and the medical professional by inputting into the checkbox.

[0371] (10) The medical management system is The system further comprises multiple mobile devices associated with each of the aforementioned multiple medical professionals, A medical management system according to any one of (1) to (9), wherein a list display image showing a list of the patient identification information associated with each medical professional is displayed on the mobile terminal associated with each medical professional.

[0372] (11) Recording process for recording on the server the response status representing the response status of the patient by the medical professional, When the patient's status changes, a notification process is performed to send a notification to the mobile device of the healthcare worker associated with the patient among the multiple healthcare workers requesting the healthcare worker to attend to the patient. A medical management system described in any one of items (1) to (10) further implements the above.

[0373] (12) A proxy request notification process in which, among the medical professionals associated with the patient, the first medical professional who received the notification sends a proxy request notification from the first medical professional's mobile terminal to the second medical professional's mobile terminal to request the second medical professional to take on the responsibility of treating the patient on their behalf. A medical management system as described in (11) further implements the above.

[0374] (13) A server that manages the linking of multiple patients with multiple healthcare professionals, A process for acquiring or setting first basic information including identification information of the aforementioned multiple patients, A process for acquiring or setting second basic information, which includes the identification information of the aforementioned multiple medical professionals, A display process that displays a settings screen for setting up the association between the multiple patients and the multiple healthcare professionals based on the first basic information of the multiple patients and the second basic information of the multiple healthcare professionals, A setting process that sets up the association between the multiple patients and the multiple healthcare professionals based on the input operation on the setting screen, A server that executes this process.

[0375] (14) To the server, A process for acquiring or setting first basic information, which includes identification information for multiple patients, A process for acquiring or setting second basic information, which includes the identification information of multiple healthcare professionals, A display process that displays a settings screen for setting up the association between the multiple patients and the multiple healthcare professionals based on the first basic information of the multiple patients and the second basic information of the multiple healthcare professionals, Based on the input operation on the settings screen, a setting process is performed to set up the association between the multiple patients and the multiple healthcare professionals. A program to execute.

[0376] While embodiments of this disclosure have been described above with reference to the attached drawings, it goes without saying that this disclosure is not limited to such embodiments. It will be obvious to those skilled in the art that various modifications or alterations can be conceived within the scope of the claims, and these will naturally also fall within the technical scope of this disclosure.

[0377] Furthermore, the processes described herein do not necessarily have to be performed chronologically in the order shown in the sequence diagram; they may include parallel processing or processing by subroutines.

[0378] The series of processes performed by each device of the medical management system 1 according to this embodiment (e.g., mobile terminal, server, client PC, electronic medical record server, central monitor, bedside monitor, spot check device, vital sign server, etc.) may be implemented using software, hardware, or a combination of software and hardware. The program constituting the software is pre-stored in a non-temporary storage medium provided inside or outside each device. The program is then read from a non-temporary storage medium (e.g., ROM) to a temporary storage medium (e.g., RAM) and executed by a processor such as a CPU.

[0379] It is possible to create programs to implement each of the above-mentioned devices and install them on the computers of each device. The processor executes the programs stored in memory, thereby carrying out the processing of each of the above-mentioned functions. At this time, the program may be divided and executed by multiple processors, or it may be executed by a single processor. Alternatively, each of the above-mentioned devices may be implemented through cloud computing, which uses multiple computers interconnected by a communication network.

[0380] The program may be provided to and installed on each device's computer via a communication network from an external device. Alternatively, the program may be stored on a non-transitory computer-readable medium and provided to and installed on each device's computer via that medium.

[0381] Furthermore, this disclosure can provide a program for executing the processing of each function of each of the above-mentioned devices. In addition, it can also provide a computer-readable non-temporary recording medium on which the program is stored. The non-temporary recording medium may be, for example, a disk-type recording medium such as an optical disk or a magnetic disk, or a semiconductor memory such as a flash memory or a USB memory.

[0382] Furthermore, in the medical management system 1 according to the embodiment described above, the support application 50 is stored in the storage 36 of a mobile terminal 10 such as a smartphone, and the processor 38 of the mobile terminal 10 executes the support application 50. However, at least a portion of the support application 50 may be stored in the storage 216 of the spot check device 22, and the processor 218 of the spot check device 22 may execute at least a portion of the support application 50. Thus, the spot check device 22 may function as an example of a mobile terminal of this disclosure, similar to the mobile terminal 10. In other words, the mobile terminal of this disclosure is not limited to the mobile terminal 10, but may also include the spot check device 22. [Explanation of symbols]

[0383] 1. Medical Management System 10 Mobile devices 12 servers 14 Client PCs 18. Bedside monitor 22 Spot Check Device 50 support applications 52 Vital Applications

Claims

1. A medical management system equipped with a server that manages the linking of multiple patients with multiple healthcare professionals, A process for acquiring or setting first basic information including identification information of the aforementioned multiple patients, A process for acquiring or setting second basic information, which includes the identification information of the aforementioned multiple medical professionals, A display process that displays a settings screen for setting up the association between the multiple patients and the multiple healthcare professionals based on the first basic information of the multiple patients and the second basic information of the multiple healthcare professionals, A setting process that sets up the association between the multiple patients and the multiple healthcare professionals based on the input operation on the setting screen, A medical management system that performs this task.

2. The first basic information of the patient further includes information about the ward in which the patient is hospitalized. The aforementioned second basic information of the medical professional further includes information about the ward to which the medical professional belongs. The medical management system according to claim 1, wherein the display process displays the patient's identification information and ward information, and the medical personnel's identification information and ward information on the settings screen.

3. The medical management system according to claim 2, wherein the settings screen has at least one of a first filtering function that narrows down the patients displayed on the settings screen based on the patient's ward information, or a second filtering function that narrows down the medical personnel displayed on the settings screen based on the medical personnel's ward information.

4. The aforementioned second basic information of the healthcare professional further includes the healthcare professional's role information, The medical management system according to claim 1, wherein the settings screen has a filtering function that narrows down the identification information of the medical professional displayed on the settings screen based on the role information of the medical professional.

5. The medical management system according to claim 1, wherein in the display process, the patient identification information that has not yet been associated with the medical professional is highlighted on the settings screen so that it can be easily distinguished from the patient identification information that has already been associated with the medical professional.

6. The medical management system according to claim 1, wherein in the display process, the patient identification information that has not yet been associated with the medical professional is displayed in a higher position on the settings screen than the patient identification information that has already been associated with the medical professional.

7. The first basic information of the patient further includes information about the ward in which the patient is hospitalized. The aforementioned second basic information of the medical professional further includes information about the ward to which the medical professional belongs. Based on the ward information in which the newly added patient is hospitalized and the ward information to which the medical professional belongs, a default setting process is performed to associate at least one of the medical professionals belonging to the ward in which the newly added patient is hospitalized with the newly added patient. A medical management system according to claim 1, further comprising the following steps.

8. The medical management system according to claim 1, wherein in the display process, the identification information of the plurality of patients and the identification information of the plurality of medical personnel are arranged in a matrix and displayed in a list on the setting screen such that the identification information of the plurality of patients is arranged in a first direction and the identification information of the plurality of medical personnel is arranged in a second direction intersecting the first direction.

9. In the aforementioned display process, on the settings screen, checkboxes are placed at the intersection of the display fields for each patient's identification information and the display fields for each healthcare worker's identification information in the matrix-like list display. The medical management system according to claim 8, wherein in the setting process, the link between the patient and the medical professional is set by an input operation on the checkbox.

10. The aforementioned medical management system is The system further comprises multiple mobile devices associated with each of the aforementioned multiple medical professionals, The medical management system according to claim 1, wherein a list display image showing a list of the patient identification information associated with each medical professional is displayed on the mobile terminal associated with each medical professional.

11. A recording process that records the response status, which represents the response status of the patient by the medical professional, on the server, When the patient's status changes, a notification process is performed to send a notification to the mobile device of the healthcare worker associated with the patient among the multiple healthcare workers requesting the healthcare worker to attend to the patient. A medical management system according to claim 1, further comprising the following steps.

12. The proxy request notification process involves the first medical professional, who has received the notification, sending a proxy request notification from the first medical professional's mobile device to the second medical professional's mobile device, requesting the second medical professional to take over the care of the patient. A medical management system according to claim 11, further comprising the following steps.

13. A server that manages the linking of multiple patients with multiple healthcare professionals, A process for acquiring or setting first basic information including identification information of the aforementioned multiple patients, A process for acquiring or setting second basic information, which includes the identification information of the aforementioned multiple medical professionals, A display process that displays a settings screen for setting up the association between the multiple patients and the multiple healthcare professionals based on the first basic information of the multiple patients and the second basic information of the multiple healthcare professionals, A setting process that sets up the association between the multiple patients and the multiple healthcare professionals based on the input operation on the setting screen, A server that executes this process.

14. On the server, A process for acquiring or setting first basic information, which includes identification information for multiple patients, A process for acquiring or setting second basic information, which includes the identification information of multiple healthcare professionals, A display process that displays a settings screen for setting up the association between the multiple patients and the multiple healthcare professionals based on the first basic information of the multiple patients and the second basic information of the multiple healthcare professionals, Based on the input operation on the settings screen, a setting process is performed to set up the association between the multiple patients and the multiple healthcare professionals. A program to execute.

Images