Device

Abstract

To provide a patient condition notification device or the like, capable of performing appropriate and rapid notification by switching a notification destination based on the condition of a patient.SOLUTION: A patient condition notification device stores ranges of a caution level and a warning level of a biological information value for each biological information, and performs notification of the condition of a patient to a terminal device of a first notification destination when an acquired biological information value of the biological information of the patient is included in the range of the caution level, and to a terminal device of a second notification destination when the biological information value is included in the range of the warning level.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to an apparatus and a method for controlling the apparatus.

Background Art

[0002] Conventionally, techniques for reporting to other terminal devices or the like and outputting an alarm have been known. For example, even in a situation where a plurality of monitoring devices of the same model are installed, an invention for easily and quickly identifying the output source of an alarm has been disclosed (see, for example, Patent Document 1).

[0003] In addition, an invention of a nurse call system that can easily call from a nurse call master unit to a mobile terminal of an assigned nurse and can also easily call to a specific plurality of patients has been disclosed (see, for example, Patent Document 2).

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0005] When used in a medical or nursing care site, there is a need to report to different reporting destinations depending on the patient's condition and the content of the report. However, conventionally, the reporting destination has been determined in advance, and it has not been possible to change the reporting destination according to the patient's condition or the like.

[0006] For example, in the aforementioned Patent Document 2, the system calls a designated nurse, which then notifies the appropriate medical professional. However, the recipient of the notification does not change depending on the patient's condition. Therefore, the recipient of the notification must assess the situation and, based on the content of the notification, either contact or search for the appropriate medical professional, which prevented a quick response.

[0007] In view of the above-mentioned problems, the object of the present invention is to provide a patient status notification device, etc., that can make appropriate and prompt notifications by switching the notification destination based on the patient's condition. [Means for solving the problem]

[0008] To solve the above-mentioned problems, the patient status notification device of the present invention is A patient status notification device to which multiple terminal devices can be connected, A storage means for storing the range of attention level and warning level for each biometric information value, A means for acquiring biometric information to obtain the patient's biometric information, A notification means that notifies a first notification terminal device of the patient's condition if the biological information value of the biological information acquired by the biological information acquisition means falls within the range of a caution level, and notifies a second notification terminal device of the patient's condition if the biological information value falls within the range of a warning level. It is characterized by having the following features.

[0009] The notification method of the present invention is, A notification method in a patient status notification device to which multiple terminal devices can be connected, A memory step that stores the range between the attention level and the warning level for each biometric value, A biometric information acquisition step to obtain the patient's biometric information, A notification step in which the patient's condition is notified to a first notification terminal device if the biological information value obtained in the biological information acquisition step falls within the range of a caution level, and to a second notification terminal device if the biological information value falls within the range of a warning level. A method for notifying a patient's condition in a patient status notification device, characterized by having the following features.

[0010] The program of the present invention, A computer that can connect to multiple terminal devices, A memory function that stores the range of attention level and warning level for each biometric value, A biometric information acquisition function that acquires the patient's vital signs, A notification function that notifies a first notification terminal device of the patient's condition if the biometric information value obtained by the biometric information acquisition function falls within the range of a caution level, and notifies a second notification terminal device of the patient's condition if the biometric information value falls within the range of a warning level. Its distinguishing feature is that it makes this a reality. [Effects of the Invention]

[0011] According to the present invention, the patient's biological information is acquired, and if the acquired biological information values ​​fall within the attention level, the patient's condition is reported to a first notification terminal device, and if the biological information values ​​fall within the warning level, the patient's condition is reported to a second notification terminal device. This makes it possible to report to the appropriate recipient based on the patient's condition. [Brief explanation of the drawing]

[0012] [Figure 1] This is a diagram illustrating the entire system in this embodiment. [Figure 2] This is a diagram illustrating the patient status display device in this embodiment. [Figure 3] This diagram illustrates the functional configuration of the display terminal and connection device in this embodiment. [Figure 4] This is a diagram illustrating the memory unit in this embodiment. [Figure 5] This is a diagram illustrating the continuous biological information in this embodiment. [Figure 6]This is a diagram for explaining the measured biological information in the present embodiment. [Figure 7] This is a diagram for explaining the alarm threshold table in the present embodiment. [Figure 8] This is a diagram for explaining the notification level table in the present embodiment. [Figure 9] This is a diagram showing an example of the notification destination in the present embodiment. [Figure 10] This is a diagram for explaining the entire notification system in the present embodiment. [Figure 11] This is a diagram for explaining the functional configuration of the electronic medical record server in the present embodiment. [Figure 12] This is a diagram for explaining the electronic medical record data in the present embodiment. [Figure 13] This is a diagram for explaining the overall flow in the present embodiment mainly focusing on the screen transition. [Figure 14] This is a diagram for explaining the operation flow of the main process in the present embodiment. [Figure 15] This is a diagram for explaining the operation flow of the alarm process in the present embodiment. [Figure 16] This is a diagram for explaining the operation flow of the patient status display process in the present embodiment. [Figure 17] This is a diagram for explaining the operation flow of the patient status identification display process in the present embodiment. [Figure 18] This is a diagram for explaining the operation of the patient status identification display in the present embodiment. [Figure 19] This is a diagram for explaining a screen example as an operation example in the present embodiment. [Figure 20] This is a diagram for explaining a screen example as an operation example in the present embodiment. [Figure 21] This is a diagram for explaining a screen example as an operation example in the present embodiment. [Figure 22] This is a diagram for explaining the operation flow of the electronic medical record registration process in the present embodiment. [Figure 23] This diagram illustrates an example screen showing the operation of this embodiment. [Figure 24] This diagram illustrates an example screen showing the operation of this embodiment. [Figure 25] This diagram illustrates an example screen showing the operation of this embodiment. [Figure 26] This diagram illustrates an example screen showing the operation of this embodiment. [Figure 27] This is a diagram illustrating an example of operation in this embodiment. [Figure 28] This diagram illustrates the operation flow of the first notification process in this embodiment. [Figure 29] This is a diagram illustrating an example of operation in this embodiment. [Figure 30] This is a diagram illustrating an example of operation in this embodiment. [Figure 31] This diagram illustrates the operation flow of the second notification process in this embodiment. [Figure 32] This diagram illustrates the operation flow of the third notification process in this embodiment. [Figure 33] This is a diagram illustrating an example of operation in this embodiment. [Modes for carrying out the invention]

[0013] The best mode for carrying out the present invention will be described below with reference to the drawings. The following embodiments are examples of the application of the patient status notification device of the present invention, and it goes without saying that the content of the invention is not limited to these embodiments.

[0014] [1. Entire System] First, the overall system in this embodiment will be described. Figure 1 is a diagram illustrating the entire patient status notification system 1 incorporating a patient status notification device. First, patient P is lying on their side on a mattress 5 placed on a bed 3. The bed is equipped with a status detection device 20.

[0015] The state detection device 20 is a device capable of continuously acquiring the patient's biological information, such as the patient's weight, body movement, blood pressure, and blood glucose level. As an example of the state detection device 20, it may be installed between the bed 3 and the mattress 5, as shown in Figure 1, or the state may be detected by attaching a sensor to the patient. Alternatively, it may be directly installed on the bed device (for example, by utilizing the load applied to the actuator). The state detection device 20 is connected to the patient state display device 10.

[0016] The patient status display device 10 has the function of a patient status notification device and is connected to the status detection device 20, the measurement device 60, or other server devices via a network. Furthermore, authentication processing (login processing) can be achieved by holding the authentication card 65 over the patient status display device 10.

[0017] The login process is performed by authorized personnel, such as staff (nurses, doctors, care staff). Logging in allows users to view biometric data and alarm details, and register information in electronic medical records. Furthermore, permissions can be set for each logged-in user, varying the scope of their actions.

[0018] The network is connected to, for example, a server 30, an electronic medical record server 40, a terminal device 50, and a mobile terminal device 55.

[0019] Server 30 is a server that provides various services and may be connected to the LAN within the hospital or facility, or it may be located externally via the internet.

[0020] The electronic medical record server 40 is a server that stores electronic medical record information about patients. It is usually connected to the network within the hospital or facility, but an external cloud server may also be used.

[0021] Terminal device 50 is a terminal device for connection in the nurse station or management room, making it possible to check the status of the patient status display device 10 even when remotely. In addition, portable terminal device 55 can be connected wirelessly to a LAN, for example, allowing nurses and care staff to easily check the information from the patient status display device 10.

[0022] Furthermore, as will be described later, the terminal device 50 and the mobile terminal device 55 are configured to receive notifications according to the patient's condition. Notifications may be made directly from the patient condition display device 10 or via the server 30.

[0023] The patient status display device 10 will be explained in detail using Figure 2. The patient status display device 10 consists of a display terminal 1000 and a connection device 2000. The display terminal 1000 is, for example, a tablet-type display terminal that displays various information and accepts input for various operations. The display terminal 1000 may be a dedicated terminal that constitutes the patient status display device 10, or it may be implemented by installing an application (program) on a general-purpose tablet terminal.

[0024] The connection device 2000 is a device for connecting the display terminal 1000 with various devices. In other words, it plays a hub role for various devices. For example, as shown in Figure 1, by connecting to the state detection device 20, it is possible to continuously acquire the patient's biological information, and it is also possible to receive biological information from the measuring device 60 (e.g., a thermometer) or from a device worn by the patient (e.g., a wristwatch-type wearable measuring device). Furthermore, by connecting the authentication card 65 to, for example, the communication unit 220, authentication processing (e.g., patient authentication or staff authentication) can also be realized. In this embodiment, NFC is used as an example of short-range wireless communication as an authentication method, but other methods such as barcodes, infrared, or IC tags may also be used for authentication.

[0025] Furthermore, a notification unit 260 is provided, which can notify, for example, in the event of an error. In addition, it can be connected to a server device, etc., via a LAN (the LAN may be either a wired LAN or a wireless LAN). The notification unit 260 may be configured to be invisible under normal circumstances and only light up (display) when a notification is to be issued. Alternatively, instead of a display, the notification may be made by sound, such as an alarm sound, warning sound, or voice, or by light.

[0026] In this embodiment, the display terminal 1000 is described as being used on top of the connection device 2000, but the display terminal 1000 and the connection device 2000 may be used separately. For example, the display terminal 1000 may be taken out and used in another location, or the connection device 2000 may be built into the bed device and the display terminal 1000 may be used separately.

[0027] [2. Functional Configuration] Next, the functional configuration of this embodiment will be explained using diagrams. Figure 3 is a diagram illustrating the functional configuration of the display terminal 1000 and the connection device 2000, which are part of the patient status display device 10.

[0028] [2.1 Display Terminal] First, the functional configuration of the display terminal 1000 will be described. The display terminal 1000 is composed of a control unit 100, a storage unit 110, a device communication unit 150, an operation unit 160, a display unit 170, and a LAN communication unit 180.

[0029] The control unit 100 is a functional unit for controlling the entire display terminal 1000. The control unit 100 realizes various functions by reading and executing various programs stored in the storage unit 110, and is composed of, for example, a CPU (Central Process Unit).

[0030] The storage unit 110 is a functional unit that stores various programs and data necessary for the operation of the display terminal 1000. The storage unit 110 is composed of, for example, semiconductor memory or an HDD (Hard Disk Drive).

[0031] Here, the configuration of the storage unit 110 will be explained using Figure 4. The storage unit 110 stores biological information 112, individual electronic medical record data 120, alarm threshold table 122, patient status identification information 124, and notification level table 126. It also stores the following programs: main program 132, alarm program 134, patient status display program 136, electronic medical record registration program 138, and notification program 140.

[0032] The biological information 112 stores continuous biological information 114, which is biological information continuously detected from the state detection device 20, and measured biological information 116, which is received from the measuring device 60 at any arbitrary timing. The measured biological information can also be manually entered or reused from the continuous biological information values ​​as needed.

[0033] Here, an example of the data structure of the continuous biological information 114 is shown in Figure 5. In this embodiment, the continuous biological information 114 stores biological information values ​​detected by the state detection device 20 and biological information values ​​whose state can be detected by other patients.

[0034] In other words, it is stored based on continuously detectable values. For example, the measurement date and time (e.g., "2015 / 05 / 16 20:00") and values ​​corresponding to the type of biological information, such as pulse rate (e.g., "126"), body temperature (e.g., "37.2"), respiratory rate (e.g., "15"), and SpO2 (e.g., "99"), are stored. That is, continuous biological information 114 can be obtained at any time from predetermined measurement values. Continuous biological information 114 can be obtained from the state detection device 20, from a detection device installed on the bed 3, or by attaching various sensors to the patient's body.

[0035] Furthermore, various acquired biometric data can be managed together as continuous biometric data. The values ​​of this biometric data vary depending on the items detected (for example, if only the body movement detection sensor is used, body movement status, sleep status, patient posture (getting out of bed, staying in bed, sitting up), pulse rate, and respiratory rate are detected as continuous biometric data).

[0036] The measured biological information 116 stores biological information received from external measuring devices such as thermometers, blood pressure monitors, and body fat analyzers. For example, as shown in Figure 6, the measured biological information 116 in this embodiment stores the reception date and time (e.g., "2015 / 05 / 16 20:00") and the value (e.g., "37.2") for each type of biological information (e.g., "body temperature"). In addition, for example, the systolic blood pressure (e.g., "159") and diastolic blood pressure (e.g., "98") are also stored.

[0037] Furthermore, the detected continuous biological information 114 and the measured biological information 116 may be stored for a predetermined period. For example, the storage period may be one day's worth of data or three days' worth of data. Alternatively, the continuous biological information 114 and the measured biological information 116 may be stored in the server 30.

[0038] Individual electronic medical record data 120 stores the electronic medical record data of each individual patient. This collection of individual patient electronic medical record data is stored in the electronic medical record server 40. The data structure of individual electronic medical record data 120 is the same as that stored in the electronic medical record server 40, so the details will be described later. In other words, in addition to patient information, continuous biological information at the time of registration, measured biological information, etc. are registered.

[0039] In this embodiment, the data is described as being stored in the storage unit 110, but it is also possible to use the data from the electronic medical record server 40 directly. In this case, it is not necessary to store the individual electronic medical record data 120 in the storage unit 110.

[0040] The alarm threshold table 122 stores alarm thresholds for various biological information values. When the measured (received) biological information value exceeds the alarm threshold, it triggers notification or error handling. These alarm thresholds may be pre-set or set arbitrarily.

[0041] Figure 7 shows an example of the alarm threshold table 122. As shown in Figure 7, alarm thresholds with upper and lower limits are stored for each biological information. In addition, multiple alarm thresholds can be stored depending on the type of alarm. Furthermore, in this embodiment, the alarm thresholds are stored in two stages: a range for attention levels and a range for warning levels.

[0042] For example, regarding "pulse rate," which is one of the pieces of biometric information, the threshold values ​​for pulse rate (the range that corresponds to attention level and warning level) are stored as biometric information values. The upper threshold is stored as "110" for the attention level and "130" for the warning level. The lower threshold is stored as "60" for the attention level and "30" for the warning level.

[0043] For example, a pulse rate of 130 or higher, or 30 or lower, can be considered to fall within the warning level range. Similarly, a pulse rate of "110 or higher but less than 130" or "greater than 30 but 60 or lower" can be considered to fall within the caution level range. It is also acceptable if the pulse rate exceeds the threshold (for example, if the pulse rate within the warning level range is greater than 130 or less than 30).

[0044] In this embodiment, for the sake of explanation, we have described the levels in two stages: caution level and warning level. However, it is of course possible to set a range greater than this.

[0045] Patient status identification information 124 is information for storing information about the patient's condition. The patient status identification information is used to perform the patient status identification display described later. In this embodiment, patient status identification information determined based on the patient's biometric information from logout to the present (interval patient status identification information) and patient status identification information determined based on the current patient's biometric information (current patient status identification information) are stored.

[0046] Here, the patient status identification information stores the states "Normal," "Caution," and "Warning." "Normal" means that the patient's biometric values ​​are within the alarm threshold range (a range that is neither a caution level nor a warning level). "Caution" means that some of the patient's biometric values ​​are within the threshold range for the caution level. Similarly, "Warning" means that some of the patient's biometric values ​​are within the threshold range for the warning level.

[0047] Furthermore, while the interval patient status identification information is determined based on the biometric data values ​​at the time of the previous logout in this embodiment, it could also be determined based on the biometric data values ​​at the time of the previous login, for example. In addition, another interval patient status identification information may be stored based on the biometric data values ​​between the logout before last and the time of the previous login.

[0048] In this embodiment, the patient status identification information changes if even one of the biological information values ​​is met. However, the patient status identification information may also be updated when multiple biological information values ​​reach an attention level or warning level. Furthermore, the patient status identification information may not be limited to one, but may be stored for each biological information or for each predetermined group. For example, the predetermined groups may be divided into continuous biological information and measured biological information, and patient status identification information may be determined and stored based on the patient's condition for each group.

[0049] The notification level table 126 is a table that stores how notifications are made for each patient, corresponding to the patient's condition and the type of vital signs. For example, as shown in Figure 8, the table stores the type (e.g., "respiration") and a notification setting (e.g., "caution") indicating whether or not to make a notification based on the vital signs, etc., corresponding to the patient number.

[0050] The notification settings can be set to "OFF" (no notification), or to indicate the level of notification: "Caution" (notifies when the alert level is reached), or "Warning" (notifies when the warning level is reached). In some cases, depending on the type of device, a simple "ON" or "OFF" setting may be available, such as whether the person is out of bed or not.

[0051] Furthermore, the recipients of notifications are predetermined according to the notification settings. For example, as shown in Figure 9, the first notification recipients are set to "assigned nurse" and "PC" located in the nurse station, etc. In addition, the second notification recipients are set to "assigned nurse," "PC," and "attending physician."

[0052] In this case, if the notification setting is "ON" or "Caution," the notification will be sent to the first notification destination. If the notification setting is "Warning," the notification will be sent to the second notification destination. In this embodiment, the "assigned nurse" and "attending physician" are extracted from the electronic medical record. Alternatively, this information may be set separately from the electronic medical record as notification destination information.

[0053] Here, we will explain the notification process using Figure 10. For example, let's consider a case where the patient's attending physician is Dr. A and the assigned nurse is Nurse B.

[0054] When the patient status display device 10 issues a warning level notification for the patient, a notification is sent to the terminal device 50 in the nurse's station and to the portable terminal device 55b. In this case, no notification is sent to Dr. A's portable terminal device 55a or Nurse C's portable terminal device 55c.

[0055] Furthermore, if a warning-level notification is issued regarding the patient in question, the notification will be sent to Dr. A's mobile terminal device 55a, in addition to terminal device 50 and mobile terminal device 55b. In this case, no notification will be sent to Nurse C's mobile terminal device 55c.

[0056] In this way, notifications are sent to pre-configured recipients with content corresponding to the notification settings. In this embodiment, notifications are set for each patient, but common recipients may also be set. For example, the Rapid Response Team may be set as the emergency notification recipient common to all patients. In this case, the setting may be such that a notification is sent to the emergency notification recipient if, for example, the patient's biometric values ​​exceed an emergency threshold or if multiple warning levels occur.

[0057] Furthermore, the notification settings are configured to notify when the biometric information reaches the attention level or warning level, but the setting is defined as "above" each level. For example, if it is set to the attention level, a notification will be sent to the first notification destination when the biometric information reaches the attention level, and then to the second notification destination when it reaches the warning level. In other words, the attention level includes the warning level. Note that it is also possible to configure the settings to only notify when the biometric information reaches the attention level.

[0058] Furthermore, the program stored in the memory unit 110 can be read by the control unit 100 to realize various functions. Specifically, the main function is realized by reading and executing the main program 132, the alarm function is realized by reading and executing the alarm program 134, the patient status display function is realized by reading and executing the patient status display program 136, the electronic medical record registration function is realized by reading and executing the electronic medical record registration program 138, and the notification function is realized by reading and executing the notification program 140.

[0059] The device communication unit 150 is a functional unit for communicating with the device communication unit 250, which will be described later. In this embodiment, it is explained that communication is performed by connecting via USB, for example, but other general-purpose connection methods or wireless connections (such as Bluetooth® or wireless LAN) may also be used. Alternatively, a dedicated connection interface may be provided for communication.

[0060] The operation unit 160 is a functional unit that receives operation input from the user, and may be, for example, a software key implemented via a touch panel, or an input device such as a keyboard or mouse. Voice input may also be used.

[0061] The display unit 170 is a functional unit that displays various information to the user and performs notification processing. For example, it is implemented by a liquid crystal display. Alternatively, it may be implemented by a touch panel in which the operation unit 160 and the display unit 170 are integrally formed.

[0062] The LAN communication unit 180 is an interface unit that can connect to a LAN. It is composed of a NIC for connecting to Ethernet (registered trademark). The LAN communication unit 180 may also be provided in the connection device 2000. In this case, the data to be transmitted is first sent to the connection device 2000 via the device communication unit 150 (250) before being transmitted to the network. The connection to the LAN may be made via a wired connection or a wireless connection.

[0063] [2.2 Connection Devices] Next, the functional configuration of the connection device 2000 will be described. The connection device 2000 is composed of a control unit 200, a storage unit 210, a communication unit 220, an interface unit 230, a device communication unit 250, and a notification unit 260.

[0064] The control unit 200 is a functional unit for controlling the entire connection device 2000. The control unit 200 realizes various functions by reading and executing various programs stored in the storage unit 210, and is composed of, for example, a CPU (Central Process Unit).

[0065] The storage unit 210 is a functional unit that stores various programs and data necessary for the operation of the connection device 2000. The storage unit 210 is composed of, for example, semiconductor memory or an HDD (Hard Disk Drive).

[0066] The communication unit 220 is a functional unit for communicating with other devices and authentication cards. For example, it can perform NFC (Near Field Communication) communication as a short-range wireless communication method. In the case of NFC communication, authentication processing is performed when the authentication card 65 is held over the device. Also, if the measuring device 60 has an NFC communication function, biometric information can be received via the connecting device 2000 by holding the measuring device 60 over the device. The measuring device 60 may be a device such as a smartphone or a wearable terminal device such as a watch.

[0067] Furthermore, the communication unit 220 may, of course, use any of the following methods: Bluetooth®, TransferJet®, ZigBee®, RFID, etc. Alternatively, a LAN (wireless LAN, wired LAN), etc., may also be used.

[0068] The interface unit 230 is a functional unit for communicating with other devices. For example, it is provided as a functional unit for connecting to the state detection device 20. The interface for connection may be a dedicated interface, or it may be a general-purpose interface such as USB or RS-232C.

[0069] The device communication unit 250 is a functional unit for communication between the display terminal 1000 and the connection device 2000 via the device communication unit 150 described above. For example, it may be connected using USB or via LAN. In this embodiment, for the sake of explanation, the configuration of the functions of each communication unit is described separately, but it may be configured as a single unit. That is, if all communication is performed by Bluetooth, the device communication unit 250, the communication unit 220, and the interface unit 230 are configured as a single functional unit.

[0070] The notification unit 260 is a functional unit that operates when the connecting device 2000 performs notification processing. For example, if an error is to be displayed, it will notify the system of that fact. Possible means of notification include sound, light, display, vibration, etc.

[0071] [2.3 Electronic Medical Record Server] Next, the functional configuration of the electronic medical record server 40 will be explained using Figure 11. The electronic medical record server 40 is composed of a control unit 400, a communication unit 410, and a storage unit 450.

[0072] The control unit 400 is a functional unit for controlling the entire electronic medical record server 40. The control unit 400 realizes various functions by reading and executing various programs stored in the storage unit 450, and is composed of, for example, a CPU (Central Process Unit).

[0073] The communication unit 410 is an interface unit for connecting to a network. For example, it is composed of a NIC that can connect to Ethernet. Communication with other devices can be performed via the communication unit 410.

[0074] The storage unit 450 is a functional unit that stores various programs and data necessary for the operation of the electronic medical record server 40. The storage unit 450 is composed of, for example, semiconductor memory or an HDD (Hard Disk Drive).

[0075] Furthermore, the memory unit 450 stores electronic medical record data 452. An example of electronic medical record data is shown in Figure 12. The electronic medical record data stores patient information, and for example, as shown in R100 in Figure 12, basic information such as patient number and name, medical information such as attending physician, and cautionary information (R102) indicating the patient's condition, pictograms, and measured biological information (biological information values) (R104) are stored for each patient.

[0076] Here, cautionary information refers to information used to alert healthcare workers, caregivers, and other specialists about the patient's condition. For example, cautionary information (such as "Do not blow your nose") and risk assessments such as pressure ulcer assessments and fall risk assessments are stored. This information may be managed using flags, or it may be managed using text, icons, pictures, etc.

[0077] Furthermore, to make it easier to understand, pictogram information may be memorized. Pictograms are based on information related to daily life. By displaying these pictograms, even passersby can show consideration for patients, thereby providing safety and security. Thus, pictogram information provides information about the patient's condition to a wide audience, while cautionary information conveys information about the patient's condition to professionals.

[0078] [3. Screen (State) Transition Diagram] Next, the overall system flow in this embodiment will be explained using the screen transition diagram (state transition diagram) in Figure 13.

[0079] First, when the system is started, it determines whether it is in an alarm state, that is, whether each biometric value exceeds (or falls below) the alarm threshold. Then, if necessary, the alarm screen (P100) is displayed. This alarm screen confirms that a problem has occurred, but the details of the error are not displayed until the user logs in. This prevents the display of error information that should not be shown to the patient or their family.

[0080] The alarm screen is displayed when the system starts up, such as when the power is turned on, but it may also be possible to check whether an alarm state is active at any given time. If an alarm state is detected, the system may be configured to transition to the alarm screen as an interrupt.

[0081] Next, the main display screen, the patient status display screen (P102), is shown. On this screen, basic patient information such as nameplate information, pictogram information, warning information, and error status is displayed. This allows necessary information to be displayed to medical professionals such as nurses and doctors, caregivers, and family members providing care.

[0082] The patient status display screen (P102) does not display detailed information because it can be viewed by the patient, their family at the hospital, and third parties visiting the patient. If necessary, authentication is performed and the user logs in, which switches to the login screen (P104). From the login screen, it is possible to transition to various screens. For example, it is possible to switch to the patient information display screen (P114) which can display patient information, the biometric information display screen (P106) which can display biometric information values, the graph display screen (P108) which can display the history of biometric information values, and the electronic medical record registration screen (P110) which registers the biometric information values ​​in the electronic medical record.

[0083] Furthermore, you can switch to the alarm settings / history screen (P116) where you can set the conditions for triggering an alarm, and the reminder screen (P112) where you can set what needs to be done next (for example, medication instructions).

[0084] Furthermore, a separate notification process is executed as an interruption, independent of the screen in question. When any biometric information value reaches a caution or warning threshold, the notification process is executed, and a notification is sent to other devices. At this time, the system may also be configured to display on each screen as appropriate that a notification has been sent.

[0085] Thus, according to this embodiment, it becomes possible to display patient information in a centralized manner, and by switching screens as needed, it becomes possible to display appropriate information. Furthermore, by centrally acquiring information from multiple measuring devices and registering it in the electronic medical record, it becomes possible to centrally manage patient information.

[0086] [4. Explanation of each process] Next, each process in this embodiment will be explained with reference to the diagrams.

[0087] [4.1 Main Processing] The main processing in this embodiment will be explained with reference to Figure 14. The main processing is performed by the control unit 100 reading and executing the main program 132 stored in the storage unit 110.

[0088] First, it is determined whether or not an alarm state is in effect (step S102). Specifically, each vital value is compared with the alarm threshold to determine whether it exceeds or falls below the alarm threshold, and then it is determined whether or not an alarm should be issued. If an alarm needs to be issued, the alarm process is executed (step S102; Yes → step S104, Figure 15).

[0089] Note that whether an alarm threshold has been exceeded varies depending on the type of biological information. In addition, in some cases, both are judged according to specific criteria (i.e., whether vital values ​​are within a predetermined range).

[0090] Next, a patient status display process is executed to determine the patient's condition and display the patient's condition based on the determined information (step S106, Figure 16). If login authentication is not performed (or if login fails), the process is repeated from step S102 (step S108; No → step S102).

[0091] If login authentication is successful (Step S108; Yes), the staff screen, which is the login screen, is displayed (Step S110). The staff screen is a screen where various processes can be selected. If a staff process is selected here (Step S112; Yes), the process is executed according to the selected staff process (Step S114). The processes executed here will be described later.

[0092] If staff processing is not selected (step S112; No), or if logout is not performed even after staff processing has been executed, the login state continues and the process is repeatedly executed (step S116; No → step S110). On the other hand, if logout is performed, the user is logged out, and the process is repeatedly executed from step S102 (step S116; Yes → step S102).

[0093] The staff processes selected here correspond to the processes P106-P116 explained in the screen transition diagram in Figure 13. The processes will be explained using process flows and screen examples.

[0094] [4.2 Alarm Handling] Alarm processing will be explained using Figure 15. Alarm processing corresponds to P100 in Figure 13 (step S104 in Figure 14), and is achieved by the control unit 100 reading and executing the alarm program 134 stored in the storage unit 110.

[0095] First, it is determined whether or not there is a device connection error (step S202). If there is a device connection error, the device error output is displayed (step S202; Yes → step S204).

[0096] Next, it is determined whether or not there is any biological information that would trigger an alarm (step S202; No → step S206 or step S204 → step S206). Specifically, each biological information value is compared with the alarm threshold to determine whether or not an alarm is in place. If there is any biological information value that would trigger an alarm (step S206; Yes), the notification process is executed (step S208).

[0097] One example of notification processing is that notification processing is performed from the notification unit 260, or an alarm screen is displayed on the display unit 170. Note that detailed information is not displayed until after login (after authentication).

[0098] Although the alarm processing was explained as being performed in step S104 of Figure 14, it may also be performed as an interrupt process after checking at regular intervals.

[0099] In this way, if there is any biological information that triggers an alarm, it is possible to output an alarm by performing notification processing. In addition, if there is a device connection error, it is also possible to output a device error as one of the alarms. Note that device connection errors may be output in a different way, or not output at all.

[0100] [4.3 Patient Status Display Processing] [4.3.1 Processing Flow] The patient status display process will be explained using Figure 16. The patient status display process corresponds to P102 in Figure 13 (step S106 in Figure 14), and is realized by the control unit 100 reading and executing the patient status display program 136 stored in the storage unit 110.

[0101] First, the individual electronic medical record data 120 is read (step S302). Alternatively, patient authentication may be performed before reading this electronic medical record data, and the data of the authenticated patient may be read.

[0102] Next, a nameplate area is created from the basic information and medical information contained in the individual electronic medical record data 120 (step S304), and then a pictogram area is created from the caution information and the set pictograms (step S306).

[0103] Specifically, a nameplate area (an area on the display screen where nameplate information is displayed) is created from basic information such as name, room number, and attending physician stored in individual electronic medical record data 120, which is synchronized with the electronic medical record data 452 of the electronic medical record server 40.

[0104] Furthermore, pictograms are created based on general cautionary information for patients and caregivers stored in the individual electronic medical record data 120.

[0105] Next, a warning area is created based on the warning information (step S308), and if there is error information, error information is generated (step S310). Here, the warning information displayed in the warning area is created based on information intended to alert professionals such as medical personnel and caregivers. Therefore, the area is created in a way that the content cannot be understood by non-medical personnel such as patients and their families. Similarly, although the error information includes information related to alarms, the area is created in a way that the content cannot be understood by non-medical personnel such as patients and their families.

[0106] Then, a patient status display screen is generated and displayed in each area created in the steps described above (step S312).

[0107] [4.3.2 Patient Status Identification and Display Processing] Next, the patient status identification display process is executed, and the patient status identification is displayed on the patient status display screen (step S314). The patient status identification display process will now be explained using Figure 17.

[0108] First, when the logout process is performed (step S352; Yes), the currently stored patient status information is cleared (step S354). Then, continuous biological information and measured biological information are received (input) (step S356).

[0109] When continuous biological information or measured biological information is received, the current patient status is determined (step S358). Here, the current patient status is determined to be one of the following states: "Warning," "Caution," or "Normal," based on all the received biological information. Specifically, if any biological information value is included in the Caution level of the alarm threshold, the status is determined to be "Caution," and if any biological information value is included in the Warning level of the alarm threshold, the status is determined to be "Warning."

[0110] Next, the segment patient status is updated (steps S362-S370). Specifically, if the segment patient status is "warning," it remains "warning" (step S362; Yes).

[0111] Next, if the current patient status is "Warning" when the interval patient status is anything other than "Warning", the interval patient status is set to "Warning" (Step S362; No → Step S364; Yes → Step S366). In other words, if the current patient status becomes "Warning" when the interval patient status is "Caution" or "Normal", the interval patient status becomes "Warning".

[0112] Furthermore, if the segment patient status is "normal" and the current patient status is "caution," the segment patient status is set to "caution" (Step S362; No → Step S364; No → Step S368; Yes → Step S370). In other words, if the segment patient status is "normal" and the current patient status becomes "caution," the segment patient status becomes "caution." Note that if the segment patient status is "caution," and the current patient status is either "normal" or "caution," the "caution" state is maintained (Step S362; No → Step S364; No → Step S368; Yes → Step S370).

[0113] Furthermore, if the current patient status remains "normal" and the interval patient status is also "normal," the interval patient status will remain "normal" (Step S362; No → Step S364; No → Step S368; No).

[0114] Thus, as the patient's status progresses from "Warning" > "Caution" > "Normal," the patient status for each interval is updated to reflect that increased level of importance. Furthermore, once a patient reaches a higher level of importance, that status will be maintained until it is cleared (for example, until the next login).

[0115] Then, based on the patient's condition (interval patient condition, current patient condition), the patient condition identification display is updated (step S372). This allows staff to easily check the current patient condition and the worst condition the patient had since the last logout.

[0116] Then, the process from step S356 is repeatedly executed until the login process is performed again (step S374; No → step S356).

[0117] Here, we will explain the general operation of the patient status identification display using Figure 18. Figure 18(a) is an example of a patient status identification display shown on the screen. M102 displays an identification display based on the patient status in a specific section, and M104 displays an identification display based on the current patient status. In this embodiment, for visibility, the identification display M104 is displayed larger, but the size may be the same, or it may have a different shape or position.

[0118] Figure 18(b) shows an example of an identification indicator for each patient condition. For example, M110 indicates normal, M112 indicates caution, and M114 indicates warning. This indicator may be changed by color, movement, or shape. For example, normal could be indicated by "white," caution by "yellow," and warning by "red."

[0119] The operation will be briefly explained using Figures 18(c) to (e). Note that t1 will be the time of the previous logout, and t2 will be the current time.

[0120] Figure 18(c) shows that at time t1 the patient's condition was "normal," but then it briefly entered a "warning" state, and then transitioned to a "caution" state before reaching t2.

[0121] In this case, the patient status indicator M102 is displayed as "Warning" because it was once in the "Warning" state from t1 onwards. Also, since the patient is currently at the "Caution" level (t2), the indicator M104 is displayed as "Caution".

[0122] Figure 18(d) shows a situation where the patient's condition was "caution" at time t1, but is now "normal" at time t2. In this case, the identification indicator M102 for the interval patient condition will be identified as "caution". Also, since the patient's condition at time t2 is "normal", the identification indicator M104 will be identified as "normal".

[0123] Figure 18(e) shows a case where the patient's condition was "normal" at time t1, but transitioned to "caution" and then "warning" along the way. Currently (t2), the patient is still at the "warning" level. At this time, the identification indicator M102, which shows the patient's condition for the interval, becomes "warning," and the identification indicator M104, which shows the patient's current condition, also becomes "warning."

[0124] Note that while Figure 18 illustrates two identification indicators for illustrative purposes, multiple indicators may be provided. For example, in addition to the identification indicator for the patient's upper body (entire body) as described above, identification indicators based solely on continuous biological information may be provided. Furthermore, special identification indicators may be provided in association with specific biological information (e.g., respiratory rate).

[0125] [4.3.3 Screen Example] Next, we will explain using an example screen showing the results of this process. Figure 19 is an example of the patient status display screen W200. On display screen W200, the patient's name and the name of the attending physician are displayed in areas R202 and R204 as nameplate information. These items are appropriately selected and displayed from the patient information registered in the electronic medical record.

[0126] Furthermore, area R206 is designated as a pictogram area, where pictograms and other symbols are displayed. In addition, area R208 displays particularly important warning information. This warning information is displayed in a way that is only understandable to professionals such as medical personnel and nursing home staff.

[0127] Furthermore, the R210 is notified that an error has occurred. In order to display the error details, an authentication process must be performed and the screen switched to another screen. This prevents non-experts, such as medical professionals or caregivers, from viewing the error.

[0128] Furthermore, the operation and status of the status detection device 20 may be displayed on the display screen W200. For example, the status may be displayed as shown in area R212. The connection status of the sensor is also displayed. This makes it possible to quickly understand whether the sensor is disconnected or unavailable.

[0129] Furthermore, patient status identification is displayed. In Figure 19, the previous patient status identification is displayed in M200, and the current patient status identification is displayed in M202. Various methods are possible for displaying patient status; for example, an underline may be displayed below the patient's name, and identification may be indicated by the color or thickness of the line, or a separate icon may be displayed.

[0130] Furthermore, in this embodiment, patient status identification is performed on the entire biological information, including continuous biological information and measured biological information. However, for example, continuous biological information and measured biological information may be displayed separately, or biological information may be displayed separately for each type of biological information, such as displaying only respiration separately.

[0131] [4.4 Biometric Information Display Processing] Next, we will explain the biological information display process. The biological information display process corresponds to P106 in Figure 13. In other words, it is the process of displaying biological information values ​​based on the patient's electronic medical record data.

[0132] Figure 20 shows an example of the display screen W300 when this process is executed. Display screen W300 shows the biometric information value for each biometric information. In addition, area R302 shows the date and time when the displayed biometric information value was registered.

[0133] Furthermore, next to the biometric data values, the alarm threshold is clearly displayed in area R304. In other words, the alarm threshold is displayed so that the range of attention levels and warning levels is clearly defined.

[0134] Furthermore, the display of biometric data may be configured to change its background color if it falls within the attention or warning level range. For example, R306 displays a pulse rate of "126 bpm." Since this biometric data falls within the attention level, the background is identified and displayed in a color corresponding to the attention level (e.g., yellow).

[0135] Additionally, an indicator may be displayed to show whether or not to send an alert in conjunction with the biometric information. For example, the R308 indicator indicates that an alert will be sent if the pulse rate (biometric value) reaches a warning level.

[0136] Furthermore, the R310 is identified as a device that initiates an alert process if the respiratory vital signs (respiratory rate) exceed a certain level.

[0137] Furthermore, the R312 and R314 displays indicate that no notification processing will be performed. The display in Figure 20 is just one example, but in this way, it is possible to display whether or not to perform a notification based on biometric information as needed.

[0138] Furthermore, the system may be configured to allow users to easily set up reporting by selecting (touching) the relevant mark. For example, touching the mark may allow users to switch between "Report OFF," "Report at Warning Level or Higher," and "Report on Warning."

[0139] [4.5 Graph Display Processing] Next, we will explain the graph display process. The graph display process is performed at P108 in Figure 13. In other words, it is the process of displaying the changes in biological information registered in the electronic medical record as a graph.

[0140] Figure 21 shows an example of the display screen W400 when this process is executed. Display screen W400 shows the transitions of each biological information value. In addition, the alarm threshold range is also displayed on the graph of each biological information. This makes it easy to check when there is an abnormality in each biological information.

[0141] Furthermore, when this graph is displayed, if one biometric information is selected, a graph showing only that biometric information may be displayed.

[0142] [4.6 Electronic Medical Record Registration Process] [4.6.1 Processing Flow] Next, the electronic medical record registration process for registering biological information in the electronic medical record will be explained using Figure 22. The electronic medical record registration process is realized when the control unit 100 reads and executes the electronic medical record registration program 138 stored in the storage unit 110.

[0143] First, patient information is read (step S402), and the patient's biometric information is read from the individual electronic medical record data 120 (step S404). The type of biometric information and alarm thresholds retrieved here may be read based on the patient's basic information (e.g., patient ID), or they may be set to common values.

[0144] Next, continuous biological information is received from the state detection device 20, and the value of the received biological information is displayed (step S408). If there is an instruction to input biological information (step S410; Yes), the biological information value is manually entered (step S412).

[0145] In this case, if the biometric data falls within the range that triggers an alarm, an identification display may be provided. For example, if the biometric data falls within the attention level, the background could be displayed in yellow, and if it falls within the warning level, the background could be displayed in red, or text could be displayed. This allows medical professionals and care staff to understand that there is currently a problem with the biometric data, and also allows for warnings about input errors, etc.

[0146] Furthermore, the continuous biological information displayed on the display screen may be read and displayed as biological information (biological information values) detectable from the state detection device 20, or it may be displayed as biological information read at a certain time.

[0147] Furthermore, if measured biological information is received from another measuring device 60 (step S414; Yes), the measured biological information is stored (step S416). In this case, the currently displayed biological information value is updated and stored in the individual electronic medical record data 120.

[0148] Here, the timing of the measurement of biological information received from other measuring devices 60 is not limited. In this figure, it is explained as an example in step S416, but measurement of biological information that has been received in advance may also be used. Furthermore, the measurement of biological information stored in the individual electronic medical record data 120 (i.e., electronic medical record data 452) can also be any type. For example, if the value measured the first time is incorrect, it may not be stored, and the value of a remeasured value may be stored instead.

[0149] Then, if there is an instruction to register the electronic medical record (step S418; Yes), the electronic medical record data 452 is registered in the electronic medical record server 40 (step S420).

[0150] [4.6.2 Screen Example] Figure 23 shows an example of the display screen W500 when this process is executed. Display screen W500 shows each biometric information and its value. Similar to Figure 20, the alarm threshold is displayed in area R502, and if each biometric information value is at the attention level or warning level, an identification display is shown as in R504.

[0151] Furthermore, as shown in area R506, the previous measurement may also be displayed. The date and time of the previous measurement are also displayed above the biometric information. This allows healthcare professionals and care staff to notice changes in biometric values.

[0152] Furthermore, regarding the displayed biometric information values, for continuous biometric information, the displayed values ​​may be updated in real time, or the values ​​at a specific point in time may be displayed. In addition, values ​​stored in the electronic medical record data (individual electronic medical record data 120 or electronic medical record data 452) may be displayed.

[0153] By selecting "Register" from this screen, the currently displayed biometric values ​​can be registered (stored) in the electronic medical record data. Furthermore, past biometric values ​​can be referenced by using the history reference function.

[0154] Additionally, settings may be configured to determine whether or not to issue a notification based on biometric information. For example, the R308 is configured to issue a notification if the pulse rate (biometric value) reaches a warning level.

[0155] Furthermore, the R310 is configured to trigger an alert if the respiratory vital signs (respiratory rate) exceed a warning level. The R312 and R314 displays are configured not to trigger an alert.

[0156] By selecting "Register," the data is registered in the electronic medical record, and the notification level table 126 is also updated.

[0157] [4.7 Reminder Processing] Next, we will explain the reminder function. The reminder function allows staff and medical professionals (nurses, etc.) to register reminders for the next tasks they need to perform. For example, Figure 24 shows an example of the W600 display screen that appears when this function is executed. By registering tasks that should be displayed as various reminders, they can be displayed on the patient status display screen and the alarm display screen.

[0158] [4.8 Patient Information Display Processing] Next, we will explain the patient information display process. The patient information display process is a process that allows for the display of information related to patients. For example, it is possible to display, input, and set basic patient information, medical information, cautionary information, pictograms, etc.

[0159] For example, Figure 25 shows an example of the display screen W700 that appears when this process is executed. The display screen W700 reads and displays basic information such as the patient's name, gender, and blood type from the electronic medical record.

[0160] [4.9 Alarm Settings and History Processing] Next, we will explain alarm settings and history processing. This process allows you to set alarm thresholds and configure whether or not an alarm should be triggered. It also allows you to review past alarms as a history. Furthermore, these alarm thresholds are also used as thresholds for notification.

[0161] Figure 26 shows an example of the W800 display screen that appears when alarm setting and history processing are performed. The W800 display screen allows you to set alarm thresholds. For example, the upper limit alarm threshold can be set to R804 for the attention level and R802 for the warning level.

[0162] Additionally, the lower limit alarm thresholds can be set as R808 for the attention level and R806 for the warning level.

[0163] Furthermore, it is possible to configure whether or not to output an alarm when the device enters the attention level range or the warning level range. For example, in the case of the R810, the setting is to not output an alarm (notify).

[0164] In the display screen W850 shown in Figure 27, the R850 is configured to output an alarm when the device enters the attention level range. This setting could also be configured to include sounds or lights, or separate alarms could be set for attention and warning levels.

[0165] [5. Reporting Process] Next, the notification process in this embodiment will be described. The notification process is an interrupt process that sends a notification to a designated recipient when one of the patient's biological information values ​​reaches a notification level.

[0166] [5.1 First Notification Processing] First, the first notification process will be explained using Figure 28. First, the patient's biological information is acquired (step S502). Then, it is determined whether or not there is any biological information that has changed from a normal level to a warning level (step S504). That is, it is determined whether the biological information value of the biological information for which the notification setting is "warning" in the notification level table 126 falls within the range of the warning level.

[0167] Then, if the biometric information value for which the notification setting is "caution" exceeds (falls below) the caution level threshold (falls within the caution level range), a notification is sent to the first notification destination (Step S504; Yes → Step S506). Here, as an example, the first notification destination is a portable terminal device held by the assigned nurse, or a terminal device located in the nurse's station, as shown in Figure 9.

[0168] Furthermore, if any biometric data changes from "normal" or "caution" to "warning," a notification is sent to the second notification destination (Step S504; No → Step S508; Yes → Step S510). In other words, in the notification level table 126, if the biometric data value of biometric data for which the notification setting is "caution" or "warning" exceeds (falls below) the warning level threshold (falls within the warning level range), a notification is sent to the second notification destination.

[0169] As an example, the secondary reporting destinations, as shown in Figure 9, include the mobile terminal device held by the assigned nurse, the terminal device located in the nurses' station, and the mobile terminal device held by the attending physician.

[0170] If the notification setting is simply "ON," then step S504 determines whether or not the ON state has been reached. For example, if the setting is to notify when a patient leaves bed (bed exit is "ON"), then the notification is sent to the first notification destination when the patient leaves bed. In this case, the notification destination may also be the second notification destination.

[0171] Figure 29 shows an example of the display screen of the W1000, a portable terminal device used by a nursing officer. The display screen is the "Alarm List" screen, showing alarms (notifications) for each patient.

[0172] For example, the R1000 displays a notification along with the patient's biometric information. This notification may be displayed as a pop-up on the operation screen or by switching screens. The R1000's notification display may also be distinguished by changing the color or icon depending on whether the level is a warning or caution.

[0173] Furthermore, as with the R1000, when a caution level (warning level) is reached, biometric information and biometric values ​​may be displayed together.

[0174] Furthermore, these threshold levels may be set from the mobile terminal device 55. For example, a screen that allows setting each piece of information, as shown in the display screen W1100 of Figure 30, may be displayed, allowing medical professionals such as nurses and doctors, as well as care staff, to set them as needed. This makes it possible to change the thresholds for the necessary patients, enabling more appropriate notifications.

[0175] Furthermore, the reporting threshold can be changed depending on the time of day or environment. For example, the threshold could be set to change between daytime and nighttime, or it could be changed according to the number of staff (for example, according to the number of patients receiving reports).

[0176] [5.2 Second Notification Processing] Next, the second notification process will be explained using Figure 31. Note that for the second notification process, the same reference numerals are used for processes identical to the first notification process in Figure 28, and detailed explanations are omitted.

[0177] After acquiring the patient's biometric information, if the biometric value for which the notification setting is "caution" exceeds (or falls below) the caution level threshold, a notification is sent to the first notification destination. At this time, it is determined whether a predetermined amount of time has elapsed since the last notification to the first notification destination (step S552). In other words, if the predetermined amount of time has not elapsed since the last notification, it is determined that the patient remains at the caution level, and no notification is sent (step S552; No → step S502). If the predetermined amount of time has elapsed, a notification is sent to the first notification destination (step S552; Yes → step S506).

[0178] Similarly, if the value of a predetermined biometric information exceeds (or falls below) the warning level threshold, a notification is sent to a second notification recipient. At this time, it is determined whether a predetermined amount of time has elapsed since the last notification to the second notification recipient (step S554). That is, if the predetermined amount of time has not elapsed since the last notification, it is determined that the level remains at a warning level, and no notification is sent (step S554; No → step S502). If the predetermined amount of time has elapsed, a notification is sent to the second notification recipient (step S554; Yes → step S510).

[0179] Thus, the second notification process makes it possible to prevent multiple notifications from being issued when biometric information values ​​fluctuate.

[0180] [5.3 Third Notification Processing] Next, the third notification process will be explained using Figures 32 and 33. For example, as in this example, the notification process may be implemented via the server 30.

[0181] Specifically, as shown in Figure 32, the patient's biometric information is acquired by the patient status display device 10 (S600), and biometric information that is in a notification state (for example, when it is determined to be Yes in step S504 or step S508 of the processing example described above) is transmitted to the server 30 (S602).

[0182] The server sends a notification destination request to the electronic medical record server 40 in order to obtain the notification destination from the received notification status biometric information. The electronic medical record server 40 determines the notification destination from the information of the assigned nurse and attending physician registered in the electronic medical record and sends it to the server 30 as a notification destination response (S606).

[0183] Next, server 30 sends an alarm notification to the terminal device and mobile terminal device that are designated as recipients of the notification (S608). When a mobile terminal device receives an alarm notification, the alarm action is performed (for example, the confirmation button is touched by the nurse using the mobile terminal device), the alarm action is performed (S614), and an alarm confirmation response is sent to server 30 (S616). This allows server 30 to manage what alarms have occurred (are in a notification state) for each patient and which staff member is responding. This managed information is updated as an alarm list (S618).

[0184] Alternatively, this alarm action may be performed directly by the patient status display device 10 (S610), or an alarm acknowledgment response may be sent from the patient status display device 10 to the server 30 (S612).

[0185] The alarm list can then be viewed on each terminal device and mobile terminal device. In other words, the alarm list is sent from the server 30 to the mobile terminal device (S620), making it possible to view it on each terminal device and mobile terminal device.

[0186] Figure 33 shows an example of the W1100 display screen showing an alarm list. Here, patients who have had alarms, either currently or in the past, are listed. In addition, it is displayed whether each patient is currently being treated or not. Furthermore, the screen shows which staff member is treating the patient and what the state of the patient's vital signs (values) was when the alarm occurred.

[0187] The sequence diagram in Figure 32 is just one example, but the server 30 may perform the processing and the patient status display device 10 may receive the results in this manner.

[0188] In other words, various programs (for example, the main program 132, the alarm program 134, the patient status display program 136, the electronic medical record registration program 138, and the notification program 140) are executed on the server 30 as needed. The patient status display device 10 sends biometric information to the server 30, and similar processing can be achieved by accessing the server 30, for example, using a web browser or a dedicated application.

[0189] Furthermore, although the patient status display device 10 is configured separately as a display terminal 1000 and a connection device 2000, it may also be provided as a single, integrated patient status display device 10.

[0190] By separating the display terminal 1000 from the connection device 2000, the display terminal 1000 has the advantage of being able to use a tablet device that meets certain conditions. This means that commercially available tablet devices, computers, or smartphones can be used.

[0191] Furthermore, while the patient status display device 10 is typically installed near the bed, the same screen can be displayed on the terminal device 50 and the portable terminal device 55. For example, even while a nurse is on rounds, they can check patient information on the portable terminal device 55, and by using the terminal device 50 at the nurse's station, it becomes possible to manage all patients together.

[0192] Furthermore, it becomes possible to update vital signs using the terminal device 50 at any time, even during medical examinations or tests, thereby improving the usability of the electronic medical record.

[0193] [6. Variant] Although embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and designs and the like that do not depart from the spirit of this invention are also included in the scope of the claims.

[0194] Furthermore, in the embodiments, the programs that run in each device are programs that control the CPU and the like (programs that make the computer function) in order to realize the functions of the embodiments described above. The information handled by these devices is temporarily stored in a temporary storage device (for example, RAM) during processing, and then stored in various ROMs or HDDs, and read, modified, and written by the CPU as needed.

[0195] Here, the recording medium for storing the program may be any of the following: semiconductor media (e.g., ROM, non-volatile memory card, etc.), optical recording media / magneto-optical recording media (e.g., DVD (Digital Versatile Disc), MO (Magneto Optical Disc), CD (Compact Disc), BD, etc.), magnetic recording media (e.g., magnetic tape, flexible disk, etc.). Furthermore, in addition to realizing the functions of the above-described embodiment by executing the loaded program, the functions of the present invention may also be realized by processing in cooperation with the operating system or other application programs based on the instructions of the program.

[0196] Furthermore, when distributing the program to the market, it can be stored on a portable recording medium and distributed, or transferred to a server computer connected via a network such as the Internet. In this case, the server's storage device is, of course, also included in the present invention. [Explanation of Symbols]

[0197] 1. Patient reporting system 3 beds 5 Mattresses 10. Patient status display device 1000 Display terminals 100 Control Unit 110 Storage section 112 Biometric Information 114 Continuous Biological Information 116 Measured Biological Information 120 Individual Electronic Medical Record Data 122 Alarm threshold table 124 Patient status identification information 126 Reporting Level Table 132 Main Program 134 Alarm Programs 136 Patient Status Display Program 138 Electronic Medical Record Registration Program 140 Reporting Program 150 Equipment Communication Unit 160 Operation section 170 Display section 180 LAN Communications Department 2000 Connection device 200 Control Unit 210 Storage section 220 Communications Department 230 Interface section 240 Wireless Communication Section 250 Equipment Communication Unit 260 Hochi Department 20 State detection device 30 servers 40 Electronic medical record server 400 Control Unit 410 Communications Department 450 Storage section 452 Electronic medical record data 50 Terminal devices 55 Mobile terminal devices 60 Measuring devices 65 Authentication Card

Claims

1. A control unit that displays a first display screen, which includes the patient status for an individual patient and is assigned to that individual patient, on the display unit, An acquisition unit that acquires the biological information of an individual patient, After the first display screen is displayed by the control unit, the authentication unit obtains the staff's authentication information and performs authentication. Equipped with, After authentication, the control unit can display a second display screen on the display unit on which alarms related to the patient's condition can be set, and a third display screen on which the biological information can be acquired. The first display screen includes a pictogram set for each individual patient, After setting an alarm on the second display screen, if the patient's condition meets the conditions for the alarm, the control unit will display different content on the first display screen without authentication and on the third display screen after authentication. Device.

2. The apparatus according to claim 1, wherein, after the state in which the third display screen is displayed, the acquisition unit is capable of acquiring the biological information when a measuring device is held over it.

Images