Information processing system and information processing method

Abstract

To provide an information processing system, an information processing method, and the like, which are suitable for caring for a patient and the like.SOLUTION: An information processing system includes: a notification setting section that sets an execution condition of notification processing of notifying a care provider of the necessity of checking a patient; a notification section that executes the notification processing if it is determined that the execution condition is satisfied; and a display processing section that causes a display section to display a setting screen used for setting of the notification processing. The notification setting section obtains ward load information representing a degree of loads needed for the care provider to deal with the notification processing in units of wards if the notification processing is executed, and obtains allowable load information representing a degree of allowable loads. The display processing section executes display processing for the setting screen including information indicating a relationship between the ward load information and the allowable load information.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present invention relates to an information processing system, an information processing method, and the like. [Background technology]

[0002] Conventionally, there are known methods for calculating the workload when caring for a care recipient such as a patient. For example, Patent Document 1 discloses a method for calculating a realistic workload for each staff member. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2021-197075 Summary of the Invention [Problem to be solved by the invention]

[0004] An information processing system, an information processing method, etc. suitable for caring for patients, etc. are provided. [Means for solving the problem]

[0005] One aspect of the present disclosure includes a notification setting unit that sets execution conditions for a notification process that notifies a caregiver that a patient needs to be checked, a notification unit that executes the notification process when it is determined that the execution conditions are met, and a display processing unit that performs processing to display a setting screen used for setting the notification process on a display unit, wherein the notification setting unit obtains ward load information that indicates the degree of load on the caregiver required to respond on a ward basis when the notification process for the patient is performed, and obtains target information that indicates a time target for responding to the notification process and allowable load information that indicates the degree of allowable load based on the number of caregivers responding to the notification process, and the display processing unit is related to an information processing system that performs display processing of the setting screen that includes information indicating the relationship between the ward load information and the allowable load information.

[0006] Another aspect of the present disclosure relates to an information processing method that performs processing to display a setting screen used for setting a notification process on a display unit, sets execution conditions for the notification process that notify a caregiver that the patient needs to be confirmed, and executes the notification process when it is determined that the execution conditions are met, and in setting the execution conditions, obtains ward load information that represents the degree of load on the caregiver required to respond on a ward basis when the notification process for the patient is performed, obtains target information that represents a time target for responding to the notification process and allowable load information that represents the degree of allowable load based on the number of caregivers responding to the notification process, and in processing to display the setting screen, performs display processing for the setting screen that includes information showing the relationship between the ward load information and the allowable load information. [Brief explanation of the drawings]

[0007] [Figure 1] FIG. 1 illustrates an example of the configuration of an information processing system. [Figure 2] FIG. 1 is a diagram illustrating an example of a functional configuration of an information processing system. [Figure 3] FIG. 1 is a diagram illustrating an example of the configuration of a bed. [Figure 4] FIG. 1 is a diagram illustrating an example of the configuration of a detection device. [Figure 5] 10 is a flowchart illustrating a notification setting process in the information processing system. [Figure 6] 10 is a flowchart illustrating a notification process in the information processing system. [Figure 7] 10 is a flowchart illustrating a process for obtaining ward load information. [Figure 8] 10 is an example of load master data. [Figure 9] 10 is an example of hospital room master data. [Figure 10] 10 is an example of judgment master data. [Figure 11] 10 is an example of judgment master data. [Figure 12A] 10 is an example of a pictogram associated with a pictogram code. [Figure 12B] 10 is an example of a pictogram associated with a pictogram code. [Figure 13] 10 is an example of judgment master data. [Figure 14] 10 is an example of judgment master data. [Figure 15] 10 is a flowchart illustrating a process for obtaining allowable load information. [Figure 16] 10A and 10B are diagrams illustrating a process for obtaining allowable load information by regression analysis. [Figure 17] 10 is an example of a setting screen. [Figure 18] 10 is an example of a patient screen. [Figure 19] 10 is another example of a setting screen. [Figure 20] 10 is an example of a screen for associating a pictogram code with a patient. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, the present embodiment will be described with reference to the drawings. In the drawings, identical or equivalent elements are designated by the same reference numerals, and duplicate explanations will be omitted. Note that the present embodiment described below does not unduly limit the content described in the claims. Furthermore, not all of the configurations described in the present embodiment are necessarily essential components of the present disclosure.

[0009] 1. System configuration example The information processing system 10 according to this embodiment appropriately performs notification processing for a caregiver, for example, when the caregiver is caring for a patient. Specifically, the information processing system 10 prevents excessive notifications from being sent to the caregiver or preventing necessary notifications from being sent to a patient in need of care. Details of the processing in the information processing system 10 will be described later. Note that a patient in this embodiment refers to, for example, a patient hospitalized in a hospital, but may also be a resident of a nursing home. In a narrow sense, a caregiver is a nurse working in a hospital, but may also include occupational therapists, physical therapists, etc. The caregiver may also include a caregiver, a care manager, etc.

[0010] FIG. 1 illustrates an example configuration of an information processing system 10 according to the present embodiment. The information processing system 10 includes, for example, a bed 100, an information processing device 200, and a terminal device 300. However, the configuration of the information processing system 10 is not limited to the example illustrated in FIG. 1 , and modifications such as omitting some components or adding other components are possible. For example, the information processing system 10 according to the present embodiment may be a part of the configuration illustrated in FIG. 1 , and the information processing system 10 may be the information processing device 200. Furthermore, while FIG. 1 illustrates two beds 100, 100-1 and 100-2, the number of beds 100 is not limited to this. Similarly, while FIG. 1 illustrates two terminal devices 300, 300-1 and 300-2, the number of terminal devices 300 is not limited to this. Furthermore, the information processing system 10 may include a sensing device 500, such as a detection device 400, which will be described later with reference to FIG. 4.

[0011] The bed 100 is bedding used by a patient. The bed 100 here may have movable parts (for example, legs 160a and a bottom 160b described later with reference to FIG. 3) for adjusting the height and angle. The bed 100 may also include a load sensor for detecting pressure (for example, load sensors 140A-140D described later with reference to FIG. 3). The bed 100 outputs information on the height and angle, as well as sensing results using sensors such as the load sensors 140A-140D, to the information processing device 200.

[0012] The information processing device 200 performs processing to determine whether or not a notification to a caregiver is necessary by assessing the patient's condition based on information from the bed 100. Communication between the bed 100 and the information processing device 200 is performed wirelessly using a method such as IEEE802.11 or Bluetooth. However, communication between the bed 100 and the information processing device 200 may also be performed via a wired connection.

[0013] The information processing device 200 is, for example, a server system. The server system may consist of one server or may include multiple servers. For example, the server system may include a database server and an application server. The database server may store information transmitted from the bed 100. The application server performs various processes based on this information. The application server executes the processes of each step described below, for example, with reference to FIG. 5 . The multiple servers here may be physical servers or virtual servers. If a virtual server is used, the virtual server may be provided on one physical server or may be distributed across multiple physical servers. As described above, the specific configuration of the server system in this embodiment can be modified in various ways.

[0014] For example, the information processing device 200 may be a management server installed in a hospital, and may perform various processes such as storing electronic medical records and managing patients and caregivers, in addition to notifying caregivers. Alternatively, the information processing device 200 may be a server system installed separately from the hospital's management server. The information processing device 200 may be a cloud server connected to the hospital's network via a public communication network such as the Internet, and may receive information from the bed 100 via a management server not shown in FIG. 1. Alternatively, the information processing device 200 may include both a management server and a cloud server in the hospital, and may be realized by distributed processing of both servers. The information processing device 200 may also be realized by other types of devices, such as a PC (Personal Computer).

[0015] The terminal device 300 is a device used by, for example, a caregiver. Specifically, the terminal device 300 is a device provided to each of a plurality of caregivers, and performs a process of presenting various pieces of information about the patient acquired from the information processing device 200 to the caregivers. Note that the terminal device 300 and the bed 100 are not limited to being provided separately. As will be described later, the terminal device 300 may be incorporated into the bed 100.

[0016] In this embodiment, an execution condition for the notification process is set for the patient, and the information processing device 200 determines whether the execution condition is satisfied. If the execution condition is satisfied, the information processing device 200 causes the notification unit 320 (e.g., a speaker) of the terminal device 300 to execute the notification process. In this way, for example, when an abnormality occurs in the patient or when supervision becomes necessary, it becomes possible to prompt the caregiver to take appropriate action.

[0017] 2 is a diagram illustrating the functional configuration of the information processing system 10. The information processing system 10 includes a sensing device 500, an information processing device 200, and a terminal device 300. The information processing device 200 includes a notification setting unit 210, a display processing unit 220, a notification determination unit 230, a notification unit 240, a storage unit 250, and a display unit 260. The terminal device 300 includes a display unit 310 and a notification unit 320. However, the configuration of each device in the information processing system 10 is not limited to the example in FIG. 2, and modifications such as omitting some components or adding other components are possible.

[0018] The sensing device 500 outputs a sensing result obtained by sensing the condition of the patient to the information processing device 200. Here, the sensing device 500 is, for example, the bed 100 including the load sensors 140A-140D. However, the sensing device 500 can be various devices such as the detection device 400 described later with reference to FIG. 4, an image sensor such as a camera, a wearable device, an RFID (Radio Frequency Identification) tag, and an RFID reader.

[0019] Furthermore, the sensing device 500 is not limited to a device that acquires information representing the condition of a patient, but may also acquire information representing the condition of the patient's surrounding environment. For example, when a bed 100 is used as the sensing device 500, the sensing results of the bed 100 may include information such as the height of the bed and the angle of the bottom 160b. Various devices such as a thermometer, a hygrometer, and a light meter can be used as the sensing device 500 that senses the condition of the surrounding environment. Details of the sensing device 500 will be described later.

[0020] The notification setting unit 210 of the information processing device 200 performs processing to set conditions for executing notification processing (hereinafter referred to as notification conditions) that notify a caregiver that the patient needs to be checked. For example, the notification conditions may be information that indicates the patient's position or posture around the bed 100, such as "out of bed" or "sitting on the edge of the bed." "Out of bed" indicates a condition that executes notification processing when the patient leaves the bed 100. "Sitting on the edge of the bed" indicates a condition that executes notification processing when the patient sits on the edge of the bed 100. Notification conditions based on the patient's position and posture (hereinafter also referred to as patient notification conditions) are not limited to "out of bed" and "sitting on the edge of the bed." Notification conditions may also include conditions other than patient notification conditions. Details of notification conditions will be described later.

[0021] The display processing unit 220 performs processing to display a setting screen, which is a screen for setting notification conditions, on the display unit. Details of the setting screen will be described later with reference to FIG. 17 . The display unit here may be the display unit 260 of the information processing device 200 or the display unit 310 of the terminal device 300. For example, when a user of the information processing device 200 (such as a hospital administrator) sets notification conditions, the display processing unit 220 displays the setting screen on the display unit 260. When a caregiver sets notification conditions, the display processing unit 220 displays the setting screen on the display unit 310. The display processing unit 220 may also perform processing to display the setting screen on a display unit other than the display unit 260 and the display unit 310.

[0022] The notification determination unit 230 acquires the sensing result from the sensing device 500 via, for example, a communication unit (communication interface) not shown. Then, the notification determination unit 230 determines whether or not the notification condition is satisfied based on the sensing result.

[0023] The notification unit 240 executes notification processing to the caregiver when the notification determination unit 230 determines that the notification condition is satisfied. For example, the notification unit 240 causes the notification unit 320 of the terminal device 300 to execute the notification processing. When multiple caregivers each own a terminal device 300, the notification unit 240 may extract a caregiver who should be in charge of the target patient from the multiple caregivers and cause the notification unit 320 of the terminal device 300 of the extracted caregiver to execute the notification processing. Alternatively, the notification unit 240 may cause the multiple terminal devices 300 to execute the notification processing collectively.

[0024] The notification setting unit 210, display processing unit 220, notification determination unit 230, and notification unit 240 described above may be included in a processing unit (not shown). The processing unit of this embodiment is configured by the following hardware. The hardware may include at least one of a circuit for processing digital signals and a circuit for processing analog signals. For example, the hardware may be configured by one or more circuit devices or one or more circuit elements mounted on a circuit board. The one or more circuit devices may be, for example, an IC (Integrated Circuit), an FPGA (Field-Programmable Gate Array), etc. The one or more circuit elements may be, for example, a resistor, a capacitor, etc.

[0025] The processing unit may be realized by the following processor. The information processing device 200 of this embodiment includes a memory that stores information and a processor that operates based on the information stored in the memory. The information is, for example, a program and various data. The memory may be the storage unit 250 or another memory. The processor includes hardware. Various processors such as a central processing unit (CPU), a graphics processing unit (GPU), or a digital signal processor (DSP) can be used as the processor. The memory may be a semiconductor memory such as a static random access memory (SRAM), a dynamic random access memory (DRAM), or a flash memory, or may be a register, a magnetic storage device such as a hard disk drive (HDD), or an optical storage device such as an optical disk drive. For example, the memory stores computer-readable instructions, and the processor executes the instructions to realize the functions of each unit of the processing unit (the notification setting unit 210, the display processing unit 220, the notification determination unit 230, and the notification unit 240) as processing. The instruction here may be an instruction from an instruction set that constitutes a program, or an instruction that instructs the hardware circuitry of the processor to operate.

[0026] The storage unit 250 serves as a work area for each section of the processing unit and stores various information. The storage unit 250 can be implemented using various types of memory, and the memory may be a semiconductor memory such as an SRAM, a DRAM, a ROM (Read Only Memory), or a flash memory, or may be a register, a magnetic storage device, or an optical storage device. The storage unit 250 may store, for example, notification conditions for each patient and sensing results from the sensing device 500. The storage unit 250 may also store load master data (described later using FIG. 8), hospital room master data (described later using FIG. 9), and judgment master data (described later using FIGS. 10-11 and 13-14). The storage unit 250 may also store patient profiles, electronic medical records, and management information for caregivers (such as shift and skill information).

[0027] Display unit 260 is an interface that displays various information, and may be a liquid crystal display, an organic EL display, or any other type of display.

[0028] Similarly, the display unit 310 of the terminal device 300 is an interface that displays various information, and may be a liquid crystal display, an organic EL display, or any other type of display.

[0029] The notification unit 320 notifies the user of the terminal device 300 of information. The notification unit 320 may be, for example, a speaker that notifies by sound. The notification unit 320 may also be a vibration unit (motor) that notifies by vibration. The display unit 310 may also function as the notification unit 320. In this case, the display unit 310 that is the notification unit 320 notifies by image.

[0030] As described above, the information processing system 10 (or, more specifically, the information processing device 200) of this embodiment includes a notification setting unit 210, a notification unit 240, and a display processing unit 220. The notification setting unit 210 of this embodiment calculates ward load information and allowable load information. The ward load information is information that indicates the level of load required for caregivers to respond to a ward-by-ward notification process when a notification process is performed for a patient belonging to the ward being processed. The allowable load information is information that indicates the level of allowable load, and is calculated based on target information that indicates a time target for responding to the notification process and the number of caregivers responding to the notification process. The display processing unit 220 performs display processing for a setting screen that includes information indicating the relationship between the ward load information and the allowable load information. The ward load information and the allowable load information will be described in detail later. The setting screen will also be described later with reference to FIG. 17.

[0031] According to the method of this embodiment, it is possible to calculate the load of caregivers on a ward-by-ward basis estimated from the preset notification conditions as ward load information, and to calculate the allowable load estimated from the target time and the number of caregivers as allowable load information. By displaying these relationships on the setting screen, it is possible to let the user (administrator and / or caregiver) recognize whether the current notification conditions are within the allowable load range.

[0032] Therefore, if the ward load information exceeds the allowable load information, the user is expected to delete some notification conditions or change them to a less load mode, thereby preventing notifications from being sent so frequently that the caregiver cannot handle them. Furthermore, if the allowable load information exceeds the ward load information, the caregiver has some spare capacity, allowing the user to add new notification conditions, for example. As a result, it is possible to prevent notification conditions from being overlooked for patients who require a high level of care. When adding notification conditions, the display processing unit 220 may perform processing to display a setting screen including notification conditions recommended for the target patient. Details will be described later.

[0033] Furthermore, some or all of the processing performed by the information processing system 10 of this embodiment may be realized by a program. The processing performed by the information processing system 10 is, in a narrow sense, processing performed by the information processing device 200, but may also include processing executed by the bed 100 or the terminal device 300.

[0034] The program according to this embodiment can be stored in, for example, a non-transitory information storage medium (information storage device), which is a medium readable by a computer. The information storage medium can be realized, for example, by an optical disc, a memory card, a HDD, or a semiconductor memory. The semiconductor memory is, for example, a ROM. The processing units (notification setting unit 210, display processing unit 220, notification determination unit 230, and notification unit 240) perform various processes of this embodiment based on the program stored in the information storage medium. In other words, the information storage medium stores a program for causing a computer to function as a processing unit. A computer is a device equipped with an input device, a processing unit, a storage unit, and an output unit. Specifically, the program according to this embodiment is a program for causing a computer to execute each step described below using FIG. 4, etc.

[0035] The technique of this embodiment can also be applied to an information processing method including the following steps. The information processing method includes a step of displaying a setting screen used to set up a notification process on a display unit, a step of setting execution conditions for the notification process that notifies caregivers that patient confirmation is required, and a step of executing the notification process when it is determined that the execution conditions are met. In setting the execution conditions, the information processing method calculates ward load information that represents the level of load on caregivers required to respond to a patient notification process on a ward basis when the notification process is performed, calculates allowable load information that represents the allowable level of load based on target information that represents a time target for responding to the notification process and the number of caregivers responding to the notification process, and in the process of displaying the setting screen, displays a setting screen including information indicating the relationship between the ward load information and the allowable load information.

[0036] 2. Specific examples of sensing devices Next, a description will be given of a specific example of the sensing device 500. The sensing device 500 may be the bed 100 as described above with reference to FIG.

[0037] Fig. 3 shows a detailed configuration example of bed 100. As shown in Fig. 3, load sensors 140 that detect pressure are arranged on bed 100. Fig. 3 shows an example in which load sensors 140A-140D are arranged at four locations on bed 100 (more specifically, four locations corresponding to the four corners of bed 100). However, the number and locations of load sensors 140 are not limited to this, and various modifications are possible.

[0038] The load sensor 140 may be, for example, a piezoelectric sensor using a piezoelectric element that generates an electric charge when pressure is applied, or a strain sensor that detects deformation of a material due to pressure as a change in electrical resistance. Various types of load sensors are known, including the piezoelectric sensor and strain sensor described above, and a wide range of such types can be applied in this embodiment. Therefore, a detailed description of the configuration of the load sensor 140 will be omitted.

[0039] The bed 100 may also be a nursing bed having legs 160a and a bottom 160b as the movable part 160, and capable of adjusting the height by moving the legs 160a and adjusting the angle (back angle, etc.) by moving the bottom 160b.

[0040] The bed 100 includes a drive unit (not shown) such as an actuator that drives the movable unit 160 of the bed 100. For example, the bed 100 has a plurality of bottoms 160b divided into a plurality of members as the movable unit 160, and the drive unit adjusts the angle of the bottoms 160b by changing the position and orientation of at least some of the plurality of bottoms 160b under the control of a processor (not shown) included in the bed 100. For example, the drive unit may be used to control the back angle (control of the bottoms 160b on the head side) or the foot angle (control of the bottoms 160b on the foot side).

[0041] The drive unit is an actuator or the like that drives the leg portion 160a. In this way, the height of the entire bed 100 can be adjusted by driving the drive unit.

[0042] The bed 100 may output the output of the load sensors 140A-140D to the information processing device 200 as a sensing result regarding the patient's position and posture, or may output the state (height and angle) of the movable part 160 to the information processing device 200 as a sensing result regarding the patient's environment, or may perform both of these processes.

[0043] Fig. 4 is a diagram illustrating the configuration of a detection apparatus 400 that measures biological information, which is another example of the sensing device 500. The detection apparatus 400 is, for example, as shown in Fig. 4, a sheet-like or plate-like device that is provided between the bottom 160b of the bed 100 and the mattress 180. The detection apparatus 400 is a device that senses information related to the patient's sleep. The detection apparatus 400 includes a pressure sensor (e.g., an air pressure sensor) that outputs a pressure value.

[0044] When the user goes to bed, the detection device 400 detects the user's body vibrations (body movement, vibrations) through the mattress 180. Based on the detected body vibrations, the detection device 400 obtains information related to the respiration rate, heart rate, activity level, posture, wakefulness / asleep, and getting out / being in bed. Note that the detection device 400 may output sensor data representing the body vibrations, and another device such as the information processing device 200 may execute a process to obtain information such as the respiration rate based on the sensor data. An example in which the detection device 400 outputs information such as the respiration rate will be described below.

[0045] For example, the detection device 400 may analyze the periodicity of body movement and calculate the respiratory rate and heart rate from the peak frequency. The periodicity may be analyzed using, for example, a Fourier transform. The respiratory rate is the number of breaths per unit time. The heart rate is the number of heartbeats per unit time. The unit time is, for example, one minute. The detection device 400 may also detect body vibrations per sampling unit time and output the number of detected body vibrations as the amount of activity. When the user gets out of bed, the detected pressure value decreases compared to when the user is in bed. Therefore, the detection device 400 may determine whether the user is out of bed or in bed based on the pressure value or a time-series change. However, the method for determining whether the user is out of bed or in bed is not limited to this, and various modifications, such as detecting vibrations, are possible. The detection device 400 may also determine whether the user is in non-REM sleep or REM sleep, or the depth of sleep. The sleep determination may be performed based on the respiratory rate and heart rate, the amount of body movement (e.g., the amount of activity), or both.

[0046] The detection device 400 outputs the patient's biological information (information on breathing, heart rate, sleep, etc.) and position and posture information (information on posture, information on getting out of bed / being in bed, etc.) as sensing results to the information processing device 200. As described above, if the bed 100 includes the load sensor 140, the position and posture of the patient can be estimated based on information from the load sensor 140. In this case, either the bed 100 or the detection device 400 does not need to output sensing results related to the patient's position and posture. Alternatively, the information processing device 200 may acquire sensing results related to the patient's position and posture from both the bed 100 and the detection device 400 and use these sensing results in combination to determine the notification condition.

[0047] The sensing device 500 is not limited to the above examples. For example, the sensing device 500 may include cameras placed at various locations in the ward. The cameras may be placed, for example, in the patient's room or in a shared space in the ward (such as a hallway or a lounge), and output image data as sensing results to the information processing device 200. The information processing device 200 determines the patient's location by performing image processing (person detection processing in a narrow sense) on the image data. For example, the information processing device 200 may identify the patient by performing face recognition processing on the person. In this way, the information processing device 200 can estimate the patient's location based on which patient is captured in the image data output from which camera. Furthermore, methods for performing skeletal tracking processing based on image data are widely known, and in this embodiment, these methods can be applied to estimate the patient's posture from the camera output.

[0048] The sensing device 500 may also include a wearable device. For example, watch-type wearable devices that can detect a patient's pulse rate and the like are widely known. Therefore, by using these wearable devices as the sensing device 500, it becomes possible to output the patient's biological information to the information processing device 200.

[0049] The sensing device 500 may also include an RFID tag attached to the patient and an RFID reader placed at a predetermined location in the hospital. The storage unit 250 may store data associating the patient ID with the tag ID of the RFID tag, and data indicating the location of the RFID reader. In this way, it becomes possible to estimate the patient's location based on the reading result of the RFID reader.

[0050] The sensing device 500 may also include a thermometer and a hygrometer, which are devices that measure environmental information. The thermometer detects the temperature around the patient. The hygrometer detects the humidity around the patient. The thermometer and the hygrometer transmit the temperature and humidity to the information processing device 200 as sensing results of the environment around the patient.

[0051] The sensing device 500 that senses the patient's surrounding environment may include a CO2 measuring device, an illuminance meter, etc. In this case, the sensing device 500 transmits information such as the carbon dioxide concentration and illuminance to the information processing device 200 as sensing results.

[0052] Furthermore, the sensing device 500 in this embodiment is not limited to the above-mentioned examples, but can be expanded to various devices capable of sensing the state of a patient or the state of the surrounding environment.

[0053] 3. Notification condition settings and notification processing The flow of processing executed by the information processing system 10 (or more specifically, the information processing device 200) will be described below. First, the overall flow will be described, and then each step will be described in detail.

[0054] 3.1 Overall flow 5 is a flowchart illustrating the notification setting process in the notification setting unit 210. When this process starts, first, in step S101, the notification setting unit 210 obtains ward load information. The ward load information is information obtained by obtaining the degree of load on caregivers required to handle notification processing for each ward.

[0055] Specifically, in step S101, when a notification process related to a patient is executed, the notification setting unit 210 may calculate, as patient load information, information that indicates the degree of load required for a caregiver to respond to the notification process. In other words, the patient load information is information that indicates the load on a patient-by-patient basis. The notification setting unit 210 obtains ward load information based on patient load information of multiple patients admitted to the ward. Furthermore, in step S101, the notification setting unit 210 may perform processing to determine notification conditions recommended for the patient. Details of the processing in step S101 will be described later.

[0056] In step S102, the notification setting unit 210 obtains information indicating the degree of allowable load for each ward based on the past history, and sets this as allowable load information. For example, the notification setting unit 210 may obtain the degree of allowable load per caregiver based on the past history, and obtain the allowable load information by multiplying the obtained value by the number of caregivers actually working. Details of the processing in step S102 will be described later.

[0057] By the above processing, ward load information and allowable load information are obtained. Note that the processing of step S101 and the processing of step S102 do not need to be executed consecutively, and each processing may be executed independently. Furthermore, the processing of step S101 and the processing of step S102 may be executed at different times or with different frequencies. For example, the trigger for executing the processing of step S101 may be different from the trigger for executing the processing of step S102. The execution timing of each processing will be described later.

[0058] Next, in step S103, the notification setting unit 210 determines whether the latest ward load information and allowable load information are larger or smaller based on a comparison process. For example, if the value of the ward load information exceeds the value of the allowable load information, it is determined that the notification settings tend to be excessive, and that it may take time for the caregiver to respond. If the value of the ward load information is below the value of the allowable load information, it is determined that the caregiver has leeway and that it is possible to add notification conditions. If the ward load information and the allowable load information are comparable, it is determined that a balanced state is achieved.

[0059] In step S104, the display processing unit 220 performs processing to display a setting screen that reflects the determination result in step S103 on the display unit 260. As described above, the setting screen may be displayed on the display unit 310 of the terminal device 300, or on a display unit of another device. For example, as will be described later with reference to Fig. 17, the display processing unit 220 may display an object OB1 that indicates the magnitude relationship between the ward load information and the allowable load information. Details of the setting screen will be described later.

[0060] In step S105, the notification setting unit 210 may also determine whether or not a user input operation on the setting screen has been received. For example, when a user input is made using an operation unit of a device that displays the setting screen, information representing the user input is transmitted to the notification setting unit 210. The user input here includes, for example, addition, deletion, or change of a notification condition.

[0061] If a user input is accepted (step S105: Yes), in step S106, the notification setting unit 210 performs processing to update the patient's notification conditions based on the content of the input operation. As will be described later with reference to FIG. 7, if the patient's notification conditions are changed, the value of the ward load information may change. Therefore, after processing in step S106, the notification setting unit 210 may return to step S101 and perform processing to update the ward load information.

[0062] If the setting screen is closed without accepting any user input (step S105: No), the notification setting unit 210 ends the process.

[0063] By performing the process shown in Figure 5, it is possible to clearly show the relationship between the load that may be caused by the set notification conditions and the load that the caregiver can handle, and then prompt the user to add, delete, change, etc. the notification conditions. As a result, it is possible to prevent excessive notification settings from being made or necessary notification settings from being omitted.

[0064] When the notification setting process is performed, the information processing system 10 executes the notification process using the set notification conditions. Fig. 6 is a flowchart illustrating the notification process in the notification determination unit 230 and the notification unit 240. When this process starts, first, in step S201, the notification determination unit 230 acquires a sensing result from the sensing device 500. For example, each of the multiple sensing devices 500 transmits the sensing result to the notification determination unit 230 at a frequency set for each device.

[0065] In step S202, the notification determination unit 230 determines whether the set notification condition is satisfied for each patient based on the sensing result. For example, when sensing results for a predetermined period are acquired, the notification determination unit 230 may determine whether the notification condition is satisfied based on the sensing results.

[0066] The notification conditions here may be, for example, patient notification conditions related to the patient's position, posture, and sleep / wakefulness. For example, the notification setting unit 210 may be able to set the following conditions as patient notification conditions: "monitoring," "getting out of bed," "sitting on the edge of the bed," "standing up," and "awakening." "Monitoring" refers to a condition for executing notification processing when a predetermined period of time has passed since the patient left the room. "Monitoring" may also be a condition for executing notification processing when a predetermined period of time has passed since the patient left the bed 100. "Getting out of bed" refers to a condition for executing notification processing when the patient leaves the bed 100. "Sitting on the edge of the bed" refers to a condition for executing notification processing when the patient sits on the edge of the bed 100. "Standing up" refers to a condition for executing notification processing when the patient sits upright on the bed 100. "Awakening" refers to a condition for executing notification processing when the patient transitions from a sleeping state to a wakeful state.

[0067] As described above, it is possible to perform the processes of detecting the patient's position, posture, and sleep determination by using the sensing device 500. Therefore, the notification determination unit 230 determines whether or not each of the notification conditions, "watching over," "getting out of bed," "sitting on the edge of bed," "standing up," and "awakening," is satisfied based on the sensing results.

[0068] The notification conditions here may also be conditions related to the patient's surrounding environment. For example, the notification setting unit 210 may be able to set conditions such as "bed height X cm" and "bed angle θ or more" as notification conditions. The notification conditions related to the bed 100 will also be referred to as the current bed state below.

[0069] "Bed height X cm" indicates a condition for executing notification processing when the height of the surface of the bottom 160b of the bed 100 (or the surface of the mattress 180) deviates from X cm. Note that X here is not limited to a single numerical value, but may be a given numerical range. Furthermore, by preparing multiple values ​​for X such as X1, X2, X3, etc., multiple notification conditions may be used for the height of the bed 100. "Bed angle θ or more" indicates a condition for executing notification processing when the angle of the bottom 160b of the bed 100 is θ (degrees) or more. Here, multiple values ​​such as 30°, 45°, and 60° may be set for θ. Furthermore, a notification condition related to the back angle and a notification condition related to the foot angle may be set for the bed angle.

[0070] As described above, it is possible to obtain the bed height and bed angle based on, for example, the state of the movable part 160 of the bed 100 (the driving state of the driving part). Therefore, the notification determination unit 230 determines whether or not the notification conditions of "bed height X cm" and "bed angle θ or more" are satisfied based on the sensing results from the bed 100.

[0071] Alternatively, biological information such as breathing and heart rate may be used as the notification condition, or environmental information such as temperature, humidity, and illuminance may be used, or a combination of two or more of these may be used.

[0072] If it is determined that the notification conditions are met (step S202: Yes), in step S203, the notification determination unit 230 determines whether the value of the patient load information of the target patient is equal to or greater than a threshold. The patient load information is information that indicates the degree of load required for a caregiver to respond to a notification process when the notification process related to the patient is executed as described above, and is obtained in the process of step S101 in Fig. 5. Details of the process for obtaining the patient load information will be described later using steps S302-S303 in Fig. 7.

[0073] If the patient load information is equal to or greater than the threshold value (step S203: Yes), in step S204, the notification unit 240 performs notification processing using a first mode. If the patient load information is less than the threshold value (step S203: No), in step S205, the notification unit 240 performs notification processing using a second mode different from the first mode. For example, if the alarm unit 320 of the terminal device 300 is a speaker that outputs sound, the notification unit 240 performs processing to output a first sound in step S204, and processing to output a second sound in step S205. Alternatively, if the alarm unit 320 is a vibration unit (motor), the notification unit 240 may perform processing to vibrate the vibration unit with a first vibration pattern in step S204, and processing to vibrate the vibration unit with a second vibration pattern in step S205.

[0074] Furthermore, when the display unit 310 of the terminal device 300 also functions as the notification unit 320, the notification unit 240 may perform processing to display the first image data in step S204, and processing to display the second image in step S205. The first image data and the second image data may differ in, for example, the images, icons, text, etc. included therein.

[0075] As described above, the notification unit 240 of this embodiment may determine the notification mode of the notification process based on the patient load information. For example, as described above, the notification unit 240 may use different display modes when the patient load information value is equal to or greater than a predetermined threshold and when it is less than the predetermined threshold. Furthermore, the number of display modes is not limited to two, and three or more display modes may be used. As will be described in detail later with reference to FIG. 8, the value of the patient load information tends to increase, for example, when the patient's condition is poor. Therefore, according to the method of this embodiment, it is possible to present the load required for response and the priority (degree of urgency) of the response to the caregiver at the notification process stage. As a result, it is possible to encourage the caregiver to take an appropriate response. For example, the caregiver can appropriately determine priority when notification processes overlap, or can promptly request another caregiver to take over if it is difficult to respond.

[0076] If the notification condition is not satisfied (step S202: No), the processes of steps S203 to S205 are omitted.

[0077] 3.2 Ward Load Information Next, the ward load information used in the notification setting process will be described in detail. The notification setting unit 210 of this embodiment may obtain patient load information. For example, the notification setting unit 210 obtains patient load information in the process of obtaining ward load information shown in step S101 of FIG. 5. Specifically, in this embodiment, the patients include multiple patients hospitalized in the ward to be processed. The notification setting unit 210 may obtain patient load information for each of the multiple patients, representing the level of load required for caregivers to care for each patient when notification processing is performed. The notification setting unit 210 then obtains ward load information representing the level of load on the ward based on the patient load information corresponding to the multiple patients. According to the method of this embodiment, obtaining patient load information makes it possible to estimate the load required for care for each patient. For example, the notification setting unit 210 obtains patient load information taking into account individual patient differences. As a result, obtaining ward load information based on the patient load information of multiple patients makes it possible to improve the accuracy of the ward load information. The detailed processing flow will be described below.

[0078] Fig. 7 is a flowchart illustrating the process of obtaining ward load information shown in step S101 of Fig. 5. The process shown in Fig. 7 may be executed for each of the beds 100 provided in a hospital, for example.

[0079] In step S301, the notification setting unit 210 determines whether the bed 100 to be processed is being used by a patient. For example, the storage unit 250 of the information processing device 200 may store, as management data, data associating the bed ID of the bed 100 with the patient ID of the patient using the bed 100. The notification setting unit 210 may read the data from the storage unit 250 and determine whether the patient ID is associated with the bed 100 to be processed.

[0080] If there is a patient in bed 100 (step S301: Yes), in step S302, the notification setting unit 210 sets the value of the patient load information of the target patient to 1. Note that 1 here is an example of a reference value for the value of patient load information, and other values ​​may be set.

[0081] Next, in step S303, the notification setting unit 210 adds a predetermined value to the value of the patient load information based on the load master data. For example, the notification setting unit 210 may calculate the patient load information based on a fall risk, which includes at least one of the patient's fall risk and the risk of falling. The fall risk refers to the risk of a patient falling. Here, falls include falls in various places and situations, such as falling while walking, falling in the toilet, and falling while going up and down stairs. The risk of falling refers to the risk of a patient falling from the bed 100, chair, wheelchair, etc. In this way, it is possible to set the patient load information according to the level of the fall risk. For example, the memory unit 250 may store information representing a patient's fall risk in association with the patient, and the notification setting unit 210 may read the information from the memory unit 250.

[0082] Fig. 8 is an example of load master data in this embodiment. As shown in Nos. 1 to 3 in Fig. 8, for example, the load master data in this embodiment may include data associating the degree of fall risk with an additional value of patient load information. Here, the degree of fall risk is evaluated in three stages, I, II, and III, and the corresponding additional values ​​(load values) are associated with 0.5, 1.0, and 1.5, respectively. With regard to fall risk, I represents a relatively low risk state, and III represents a relatively high risk state. Although omitted in Fig. 8, a stage representing a sufficiently low fall risk (for example, no fall risk) may be provided, and this stage may be associated with an additional value of 0.

[0083] For example, in step S303, the notification setting unit 210 identifies the stage of the fall risk by referring to the electronic medical record of the patient being processed. Furthermore, the notification setting unit 210 identifies an additional value according to the patient's fall risk by referring to the load master data in Figure 8, and adds the identified additional value to the value of the patient load information. For example, if the fall risk of a patient whose patient load information value was set to 1 by the processing of step S302 is III, the notification setting unit 210 updates the value to 2.5 by adding 1.5 to the patient load information.

[0084] Alternatively, the notification setting unit 210 may obtain patient load information based on information about the patient's room. This information may be, for example, the distance from the nurse's station, which is the base of the caregiver. As shown in Nos. 4 and 5 of FIG. 8, the load master data of this embodiment may include data associating the distance from the nurse's station to the patient's room with an additional value of the patient load information. Here, the distance is evaluated in two stages, close and far, and the corresponding additional values ​​(load values) are 0.0 and 1.5, respectively. This makes it possible to set patient load information according to the ease of access to the patient's room.

[0085] FIG. 9 is an example of hospital room master data representing the attributes of a hospital room. The hospital room master data is information that associates a ward code that identifies a ward, a room code that identifies a hospital room, and the distance between the target hospital room and the nearest nurse station. The hospital room master data is stored, for example, in the memory unit 250. The memory unit 250 may also store, as management data, data that associates a patient ID of a patient with a room ID (room code) that represents the patient's room.

[0086] In step S303, the notification setting unit 210 reads the data from the storage unit 250 and identifies the hospital room code representing the patient's room. The notification setting unit 210 identifies the distance between the patient's room and the nurse station by referring to the hospital room master data. The notification setting unit 210 further identifies an additional value according to the distance by referring to the load master data in FIG. 8, and adds the identified additional value to the value of the patient load information. For example, if the distance between the patient's room and the nurse station, whose value of the patient load information was set to 1 by the processing in step S302, is actually "far," the notification setting unit 210 adds 1.5 to the patient load information to update the value to 2.5.

[0087] While the distance based on the nurse station has been exemplified above, the method of this embodiment is not limited to this. For example, if the position information of the caregiver can be measured, the notification setting unit 210 may periodically obtain the current position of the caregiver in charge of the patient and the position of the patient's room, and update the patient load information based on the distance and the load master data.

[0088] The hospital room master data may also include information indicating attributes other than the distance of the hospital room. The hospital room attribute may be, for example, information indicating whether the hospital room is a normal hospital room or a sterile room. In this case, the load master data in FIG. 8 may include data associating a normal hospital room with an additional value of 0.0, and data associating a sterile room with an additional value of 2.0. In this example, when the sterile room is the target, the additional value associated with the sterile room is relatively large because of the large load caused by disinfection and wearing a clean suit.

[0089] Alternatively, the notification setting unit 210 may obtain patient load information based on medical condition information related to the patient's condition. For example, although not shown in FIG. 8 , the load master data of this embodiment may include data associating a patient's medical condition with an additional value of the patient load information. For example, the load master data may include data associating a medical condition such as "limb disability" with an additional value of 1.0 and data associating a medical condition such as "cerebral infarction" with an additional value of 2.0. The load master data may also include data associating a medical condition such as "within Y days after surgery" with an additional value of Z. Here, the values ​​Y and Z may be set to a single value or a set of multiple values. For example, an additional value of 3.0 may be assigned to "within 3 days after surgery" and an additional value of 1.5 may be assigned to "within 7 days after surgery." The medical conditions (disabilities, medical history) included in the load master data are not limited to the above examples; various medical conditions, such as visual impairment, dementia, and epilepsy, may also be applicable. The medical condition information is stored, for example, in the storage unit 250.

[0090] At this time, the notification setting unit 210 may obtain patient load information based on the patient's electronic medical record. The electronic medical record includes, for example, information indicating the diagnosis results of a doctor. As described above, the information processing device 200 of this embodiment is expected to be able to link with an in-hospital system, and the electronic medical record is stored in the storage unit 250, for example. Therefore, since the processing load when referencing the electronic medical record is expected to be low, it becomes possible to obtain patient load information using accurate information based on expert judgment without increasing the system load.

[0091] Furthermore, the process of determining patient load information is not limited to a process that uses only one of the risk of falling, hospital room, or medical condition, but may be a process that combines two or more of these. For example, if the patient's risk of falling is stage II and the hospital room is far from the nurse station, the patient load information may be updated to 3.5, which is the standard value of 1 plus 1.0 and 1.5.

[0092] The patient load information for the target patient is obtained by the processing of steps S302-S303 described above. Next, in step S304, the notification setting unit 210 determines whether the notification setting is on for the target patient (whether any notification conditions have already been assigned). If the notification setting is on, the value of the patient load information is added to the ward load information. On the other hand, if the notification setting is off, the notification process for the target patient is not executed in the first place, and therefore it is not expected that a load will be generated for the notification process for that patient. In this case, the value of the patient load information is not added to the ward load information. By executing the processing of step S304 for all patients admitted to the target ward, the total value of the patient load information for patients for whom notification settings have been set is obtained as the ward load information. As described above, since the patient load information reflects the condition of each patient, the ward load information is considered to be a value that accurately estimates the load on caregivers for notification processes on a ward-by-ward basis.

[0093] 3.3 Recommended conditions for notification processing After calculating the patient load information and updating the ward load information as necessary (steps S302-S304 in FIG. 7), the notification setting unit 210 may determine the notification conditions recommended for the target patient. For example, in step S305, the notification setting unit 210 determines whether the patient's condition matches any of the data in the determination master data. Below, several specific examples of the determination master data will be described.

[0094] 3.3.1 Allowable Range of Movement For example, the notification setting unit 210 may determine the execution conditions of the notification process recommended for the patient based on the patient's allowable range of movement. Fig. 10 shows an example of determination master data used in the process of determining the recommended notification conditions. As shown in Fig. 10, the determination master data here may be data in which the patient's allowable range of movement indicated in the electronic medical record, a pictogram, and the recommended notification conditions are associated with each other.

[0095] For example, if caregivers could grasp detailed information such as electronic medical records, they would be able to provide appropriate care tailored to each patient. However, since caregivers are expected to be responsible for multiple patients, it is not easy to accurately grasp the vast amount of information about every patient. Furthermore, some caregivers are responsible for supplementary patient care, or for care in specific areas such as rehabilitation. These caregivers may only have limited contact with the patient, making it difficult for them to grasp detailed information about that patient.

[0096] Therefore, in this embodiment, a visually easy-to-understand pictogram may be associated with each patient's status for management. In the example of Fig. 10, the patient's status represents the range of permitted movement, and specifically includes states such as "free within the hospital," "free within the ward," "free within the hospital room," and "prohibited movement." "Free within the hospital" represents a state in which movement within the hospital is not restricted. "Free within the ward" represents a state in which movement within the ward is not restricted, but movement outside the ward is restricted. "Free within the hospital room" represents a state in which movement within the hospital room is not restricted, but movement outside the room is restricted. "Prohibited movement" represents a state in which leaving the bed 100 is restricted.

[0097] For example, in this embodiment, pictogram codes that do not overlap with each other may be assigned to each of the following: free movement within the hospital, free movement within the ward, free movement within the hospital room, and no movement. Each pictogram code corresponds to a single pictogram. Here, the pictogram code is, for example, numerical data, but data in other formats may also be used. In the example of FIG. 10, the four pictogram codes corresponding to free movement within the hospital, free movement within the ward, free movement within the hospital room, and no movement are each associated with a human-shaped pictogram of a different color or pattern.

[0098] By associating the patient's condition with a pictogram in this way, it becomes possible to inform the caregiver of the patient's condition using a visually easy-to-understand pictogram. For example, by using the pictogram shown in FIG. 10, even a caregiver who does not often come into contact with the patient can easily understand the patient's permitted range of movement. An example of a display screen using pictograms will be described later with reference to FIG. 18. However, in this embodiment, the use of a pictogram code is not essential, and other data may be used as long as it is possible to identify the patient's condition, such as the patient's permitted range of movement.

[0099] For example, the notification setting unit 210 acquires the pictogram code assigned to the patient by reading the electronic medical record from the storage unit 250. The process of assigning a pictogram code (pictogram) to the patient will be described later with reference to FIGS. 19 and 20.

[0100] Then, in step S305 of Fig. 7, the notification setting unit 210 determines whether the pictogram codes assigned to the patient include a pictogram code that matches any of "free in hospital," "free in ward," "free in hospital room," and "no movement" based on the determination master data of Fig. 10. If the pictogram code assigned to the patient corresponds to the determination master data (step S305: Yes), in step S306, the notification setting unit 210 determines recommended notification conditions based on the determination result using the determination master data.

[0101] For example, when a patient is assigned a pictogram code corresponding to in-hospital free, the notification setting unit 210 determines that a recommended notification condition is unnecessary (there is no recommended notification condition) based on the determination master data of FIG. 10. When a patient is assigned a pictogram code corresponding to in-ward free, the notification setting unit 210 determines that the recommended notification condition is "monitoring." When a patient is assigned a pictogram code corresponding to in-hospital free, the notification setting unit 210 determines that the recommended notification condition is "get out of bed." When a patient is assigned a pictogram code corresponding to no movement, the notification setting unit 210 determines that the recommended notification condition is "sitting on the edge" or "standing up."

[0102] In this way, it is possible to prompt the user to set appropriate notification conditions according to the allowable movement range. For example, in the display processing shown in step S104 of Fig. 5, the display processing unit 220 may display a setting screen including recommended notification conditions on the display unit. A specific example will be described later with reference to Fig. 17. Note that if the pictogram code assigned to the patient does not correspond to the determination master data (step S305: No), the processing of step S306 is omitted.

[0103] 3.3.2 Transportation Furthermore, the process using the determination master data shown in step S305 is not limited to the above example. For example, the notification setting unit 210 may determine the execution conditions for the notification process recommended for the patient based on the patient's means of transportation.

[0104] Fig. 11 is another example of the determination master data. The determination master data shown in Fig. 11 may include, for example, a pictogram code representing a patient's transportation means, a type of notification condition (determination data), a determination condition, a condition determination formula, and an attribute.

[0105] As in the above-described example, the pictogram code is associated with a specific pictogram. FIG. 12A shows pictograms associated with a patient's means of transportation. For example, in this embodiment, transportation means are pre-defined as walking, a cane, a wheelchair, a walker, and bed transfer, and a pictogram code is assigned to each of them. Here, the pictogram code for walking is 110, the pictogram code for a cane is 120, and the pictogram code for a wheelchair is 130. Similarly, codes that do not overlap with the pictogram codes representing other means of transportation are assigned to walkers and bed transfers. Of the pictograms shown in FIG. 12A, the pictogram representing walking is associated with pictogram code 110, the pictogram representing a cane is associated with pictogram code 120, and the pictogram representing a wheelchair is associated with pictogram code 130.

[0106] 12A, for a state such as "bed rest" that is difficult to display with a pictogram, data including text may be used. In this embodiment, for example, an attention code may be assigned to a state that is difficult to display with a pictogram, and data including text indicating the state may be associated with one attention code. In this case, the patient's state can also be presented as a text icon, making it possible to inform the caregiver of the patient's state in an easy-to-understand manner.

[0107] Returning to Figure 11, we will continue the explanation. In the judgment master data shown in Figure 11, judgment data, judgment conditions, and condition judgment formulas are associated with pictogram codes. The judgment data represents the attributes of the notification conditions, and in this case indicates that the target is patient notification conditions (in a narrow sense, notification conditions related to the patient's position, posture, and sleep / wakefulness). The judgment conditions represent the criteria for the conditions that are determined based on the patient's condition. The condition judgment formula is information that indicates the range of the condition, and specifically, it may be data that represents one of "same," "greater than," or "less than" based on the judgment conditions.

[0108] Note that "large" in the condition determination formula represents, for example, a measure of tolerance for a patient's behavior, and for example, in the patient notification conditions, the magnitude relationship may be specified in the order of (watching > getting out of bed > sitting on the edge of bed > standing up > awake). Note that if there is a notification condition "not set," which indicates that the notification condition has not been set, "not set" may be set to a larger side than "watching" or a smaller side than "awake." Furthermore, as will be described later with reference to FIG. 13, if the notification condition is a condition related to the range of motion of bed 100 (current bed state), the magnitude relationship may be determined based on the numerical values ​​of height and angle.

[0109] A condition is identified by a combination of a judgment condition and a condition judgment expression. Attributes in FIG. 11 are data that identify whether the identified condition is a recommended notification condition or a non-recommended notification condition. While FIG. 11 shows an example in which the judgment master data includes a column that identifies recommended / non-recommended conditions, the processing of this embodiment is not limited to this. For example, a list (whitelist) consisting of data including recommended conditions and a list (error list) consisting of data including non-recommended conditions may be managed as different judgment master data.

[0110] The notification setting unit 210 identifies a pictogram code associated with a patient and identifies recommended or non-recommended notification conditions based on the judgment conditions and condition judgment formula associated with the pictogram code. If the notification conditions already set for the patient do not match the recommended notification conditions, or if the notification conditions already set for the patient match the non-recommended notification conditions, the notification setting unit 210 prompts the patient to change the already set notification conditions. Furthermore, if no notification conditions have been set for the patient, the notification setting unit 210 may prompt the patient to add a notification condition. Changing or adding notification conditions is performed by, for example, displaying a setting screen on the display unit (display unit 260 or display unit 310) via the display processing unit 220.

[0111] A specific example will be described. For example, suppose that a target patient is assigned data (110) representing walking as a pictogram code. In this case, the notification setting unit 210 first extracts the data in the first row by searching for the pictogram code corresponding to walking from the determination master data in FIG. 11 (step S305 in FIG. 7). Then, the notification setting unit 210 determines that the recommended notification condition is "watching" because the determination condition is "same as," the condition determination formula is "same as," and the attribute is "recommended" (step S306). If the pictogram code is walking, the target patient is considered to be able to walk on his / her own, and therefore there is considered to be little need to closely manage movements on the bed 100 or short periods of getting out of bed.

[0112] Next, the notification setting unit 210 compares the notification conditions already set for the target patient with the recommended notification conditions. Here, assume that a notification condition of "sitting on the edge of the bed" has already been set for the target patient. In this case, since "sitting on the edge of the bed" and "supervision" are different, the notification setting unit 210 determines that the already set notification conditions do not match the recommended notification conditions. Therefore, the notification setting unit 210 outputs "supervision" as the recommended notification condition. For example, in step S104 of FIG. 5, the display processing unit 220 may display a setting screen including the recommended notification conditions on the display unit.

[0113] The same applies when other pictogram codes are used. For example, if the pictogram code is a cane, the target patient needs a cane but is able to move around on his or her own to a certain extent, so there is little need to closely monitor the patient's movements on the bed 100 or short periods of getting out of bed. Therefore, the notification setting unit 210 determines "monitoring" as the recommended notification condition based on the determination conditions, the condition determination formula, and the attributes. Then, the notification setting unit 210 determines whether or not to perform processing to present the recommended notification condition to the user based on a comparison process between the set notification condition and the recommended notification condition.

[0114] Furthermore, if the pictogram code is a wheelchair, the judgment condition is "sitting on the edge of the bed," the condition judgment formula is "greater than," and the attribute is "not recommended." Therefore, the notification setting unit 210 determines "sitting on the edge of the bed" and "getting out of bed" as non-recommended notification conditions based on the magnitude relationship (watching > getting out of bed > sitting on the edge of the bed > getting up > awake). Because wheelchair-using patients cannot move on their own, a caregiver must assist the patient before getting out of bed, for example, when they reach the edge of the bed. In other words, the data here corresponds to cases where "sitting on the edge of the bed" or "getting out of bed," for which notification processing is executed at or after getting out of bed, is considered undesirable.

[0115] Then, the notification setting unit 210 performs a comparison process between the set notification conditions and the non-recommended notification conditions. For example, if the set notification conditions are included in the non-recommended notification conditions, the notification setting unit 210 may perform a process of identifying notification conditions other than the non-recommended notification conditions as recommended notification conditions (step S306 in FIG. 7). Here, the notification conditions other than the non-recommended notification conditions are patient notification conditions other than "monitoring" and "getting out of bed", for example, a set of "sitting on the edge of bed", "standing up", and "awakening".

[0116] The fourth row in FIG. 11 is an example of a pictogram code representing a state in which "notification setting is required." For example, a pictogram code representing "notification setting is required" is assigned to a patient with some kind of medical condition. In this case, the notification setting unit 210 sets the judgment condition to "unspecified," the condition judgment formula to "same as," and the attribute to "not recommended." "Unspecified" represents an empty set in which none of the patient notification conditions, "monitoring," "getting out of bed," "sitting on the edge of bed," "standing up," or "awakening," are set. In other words, in this case, the empty set notification condition is determined to be an unrecommended notification condition. For example, if none of the patient notification conditions, "monitoring," "getting out of bed," "sitting on the edge of bed," "standing up," or "awakening," are set, the notification setting unit 210 recommends changing the notification condition because the current notification condition matches the unrecommended notification condition. The recommended notification condition is the complement of the empty set and is a set of the patient notification conditions, "monitoring," "getting out of bed," "sitting on the edge of bed," "standing up," and "awakening." In other words, the notification setting unit 210 recommends setting any patient notification condition.

[0117] In the above example, the data attribute in the first and second lines of FIG. 11 is "recommended" and the data attribute in the third and fourth lines is "not recommended", but the present invention is not limited to this.

[0118] For example, in the case of a patient who uses a wheelchair, notification conditions such as "sitting on the edge of bed," "standing up," and "awakening" can notify in advance that transfer assistance is required, but frequent notification processing may increase the burden on the caregiver. Therefore, it may be possible to deliberately set notification conditions such as "monitoring" and "leaving bed" from the perspective of suppressing the frequency of notifications and focusing on detecting abnormalities such as the wheelchair user leaving bed 100.

[0119] In this case, the data attribute in the third row of the judgment master data in FIG. 11 is "recommended." In this example, the attribute changes depending on whether intensive care or reduced notification frequency is prioritized. As can be seen from the above example, in this embodiment, data containing the same judgment condition and condition judgment expression may be treated as data representing recommended notification conditions or as data representing non-recommended notification conditions. For example, the values ​​in the attribute column shown in FIG. 11 may be changed based on user operation. Alternatively, the notification setting unit 210 may change the attribute value based on the relationship between the latest ward load information and allowable load information.

[0120] Furthermore, the ability to change attributes is not limited to data corresponding to wheelchairs, but also applies to data in other rows of the judgment master data shown in Figure 11, and to data in each row of the judgment master data described below using Figures 13 and 14.

[0121] 3.3.3 Bed movement range Furthermore, the pictogram codes used in this embodiment and the pictograms associated with these pictogram codes are not limited to transportation means. For example, as shown in FIG. 12B, the patient's condition may represent the range of motion of the bed 100 recommended for the patient. For example, in this embodiment, the back angle of the bed 100 is pre-defined as 30° or less, 45° or less, and 60° or less, and a pictogram code is assigned to each of these. For example, the pictogram code for 30° or less is 210, the pictogram code for 45° or less is 220, and the pictogram code for 60° or less is 230. Of the pictograms shown in FIG. 12B, the pictogram representing 30° or less is associated with pictogram code 210, the pictogram representing 45° or less is associated with pictogram code 220, and the pictogram representing 60° or less is associated with pictogram code 230. For example, for the "heads up prohibited" condition, data including a warning code and text may be used.

[0122] Fig. 13 is another example of the determination master data. The determination master data shown in Fig. 13 may include data associating a pictogram code, a type of notification condition (determination data), a determination condition, a condition determination formula, and attributes, similar to the determination master data shown in Fig. 11. The determination data here is the current bed state representing the notification condition related to the range of motion of the bed 100.

[0123] For example, suppose a target patient is assigned the pictogram code 130, which corresponds to a wheelchair. In this case, in step S305 of FIG. 7, the notification setting unit 210 extracts the data in the first row by searching for the pictogram code corresponding to a wheelchair from the determination master data of FIG. 13. Then, since the determination condition is "bed height is X cm," the condition determination formula is "greater than," and the attribute is "not recommended," the notification setting unit 210 determines in step S306 of FIG. 7 that "bed height greater than X cm" is a not recommended notification condition. Therefore, the notification setting unit 210 determines that the recommended notification condition is "bed height X cm or less." In the case of a wheelchair-using patient, the patient needs to transfer from the bed 100 to the wheelchair. It is known that transfer assistance is easier when the bed 100 is relatively high. In other words, since "bed height greater than X cm" is a desirable condition that does not require notification, if the opposite notification condition, "bed height less than X cm," is set, it becomes possible to notify the caregiver that the height of bed 100 is too low to be suitable for transfer.

[0124] The notification setting unit 210 determines whether the set notification condition matches the recommended notification condition "bed height X cm or less." If they do not match, the notification setting unit 210 performs processing to present the recommended notification condition "bed height X cm or less" to the user.

[0125] Furthermore, if the patient has been assigned a pictogram code indicating a 30° head-up limit, the notification setting unit 210 extracts the data in the second row of FIG. 13. The notification setting unit 210 determines that the recommended notification condition is "bed angle greater than 30°" based on the determination condition, the condition determination formula, and the attribute. The notification setting unit 210 determines whether the set notification condition matches the recommended notification condition "bed angle greater than 30°." If they do not match, the notification setting unit 210 performs processing to present the recommended notification condition to the user. In this way, it is possible to recommend notification settings that warn users who do not want excessive head-up tilt when the back angle becomes excessively high. The same applies to the 45° head-up limit and the 60° head-up limit.

[0126] Furthermore, if a pictogram code representing fluid thickness has been assigned to the patient, the notification setting unit 210 extracts the data in the fifth row of FIG. 13. Fluid thickness is a pictogram code representing adding a certain thickness to the target patient's food and drink. The notification setting unit 210 determines that the recommended notification condition is "bed angle less than 30°" based on the judgment condition, the condition judgment formula, and the attribute. Patients who require thickened food and drink have reduced swallowing ability, so it is desirable to raise the back angle of the bed 100 to a certain degree when eating and drinking. In other words, when targeting such patients, by executing the notification process on the condition that the bed angle is below a predetermined value, it is possible to encourage the patient to adjust the back angle to make swallowing easier.

[0127] The notification setting unit 210 determines whether the set notification condition matches the recommended notification condition "bed angle less than 30°." If they do not match, the notification setting unit 210 performs processing to present the recommended notification condition to the user. In this way, it can be recommended that a patient with poor swallowing ability be encouraged to elevate their head to assist swallowing.

[0128] 3.3.4 Combinations of medical conditions 10 to 13, the processing based on information associated with pictogram codes, such as the allowable range of movement, the means of movement, and the movable range of the bed 100, has been described. However, the method of this embodiment is not limited to processing using pictogram codes.

[0129] Fig. 14 is another example of the determination master data. The determination master data shown in Fig. 11 may include, for example, a patient profile, a type of notification condition (determination data), a determination condition, and a condition determination formula. Although omitted in Fig. 14, the determination master data may also include an attribute specifying recommended / non-recommended, similar to the examples of Figs. 11 and 13.

[0130] As shown in Figure 14, the patient profile may include medical conditions such as disability, medical history, surgery date, and risk of falling. The judgment data, judgment conditions, and condition judgment formula are the same as those of the judgment master data in Figure 11, etc. In this way, it becomes possible to recommend appropriate notification conditions according to the patient's condition, even for cases where it is difficult to use pictogram codes.

[0131] For example, for patients with limb disabilities, notification conditions may be recommended that take into account detection of sitting up or a bed height that makes it easy to move around. For patients with visual impairments, notification conditions based on "sitting on the edge of the bed" may be recommended, taking into account the need for assistance when leaving the bed 100. For patients with a history of epilepsy, who are prone to sudden falls, notification conditions based on "supervision" may be recommended. For patients with a history of surgery, notification conditions based on the number of days since the surgery and notification conditions based on "supervision" may be recommended. For patients with a mild risk of falling (patients with a fall risk level of I), notification conditions based on "sitting on the edge of the bed" may be recommended, in order to prevent them from falling from the bed 100 or falling while moving.

[0132] Furthermore, the medical conditions included in the patient profile and the conditions associated with the medical conditions are not limited to those shown in FIG. 14, and various modifications are possible.

[0133] Although various types of judgment master data have been exemplified above, it is possible that the condition of a patient or bed 100 matches multiple records contained in the judgment master data. A record here refers to one line of data in the judgment master data. A record matches when the patient's condition, etc., satisfies the condition judgment expression contained in the record.

[0134] For example, a patient's condition may satisfy the condition expression of a first record whose attribute is "recommended" and also satisfy the condition expression of a second record whose attribute is "not recommended." In this case, if the first record is taken into consideration, a recommended notification condition has already been set, so no recommendation for a change is necessary. On the other hand, if the second record is taken into consideration, a non-recommended notification condition has already been set, so it is desirable to recommend a change. In this case, the notification setting unit 210 may perform processing on all records that satisfy the condition expression. For example, the notification setting unit 210 may extract all records whose attribute is "recommended" but whose condition expression is not satisfied, and all records whose attribute is "not recommended" but whose condition expression is satisfied, and recommend recommended notification conditions for all of the records.

[0135] Alternatively, the notification setting unit 210 may set priorities among the records and execute only the processes related to the records with relatively high priorities. For example, in the method of this embodiment, judgment master data may be used in which the conditions expressed by multiple records are mutually contradictory. In this case, priorities may be set among at least the records with conflicting conditions, and the processes may be executed according to the priorities.

[0136] Alternatively, the method of this embodiment may use determination master data in which records with similar conditions, in which the notification conditions are easily satisfied (lower conditions), and records with less likely to satisfy the notification conditions (higher conditions), coexist. For example, when pictogram codes are used as shown in FIG. 11, the determination master data may include multiple records for the same pictogram code. For example, for the pictogram code "walking," a record representing the recommended conditions "same as" "monitoring" and "getting out of bed" may coexist with a record representing the recommended conditions "same as" "getting out of bed." In this case, the latter will notify at the "getting out of bed" stage, which is earlier than "monitoring," making notification processing more likely to occur. In this case, as in the above example, priorities may be set among the records, and processing may be performed according to the priorities. In this case, priority may be given to records with lower conditions, or records with higher conditions may be given priority.

[0137] 3.4 Load Capacity Information Next, the process of obtaining the allowable load information shown in step S102 of Fig. 5 will be described. The notification setting unit 210 may determine the allowable load information based on the history of ward load information and the history of time information indicating the time required for the caregiver to respond to the notification process. In this way, it becomes possible to obtain the allowable load information, which is the level of load that the caregiver is estimated to be able to handle, based on the past care history.

[0138] 15 is a flowchart illustrating the process of obtaining allowable load information. First, in step S401, the notification setting unit 210 reads past data from the storage unit 250. For example, the notification setting unit 210 acquires the history of ward load information for the past month, the history of the number of caregivers who worked in the target ward, and the history of the time it took for the caregiver to respond after the notification process was sent to the caregiver.

[0139] 7, since it is possible to obtain patient load information and ward load information from information such as electronic medical records, the notification setting unit 210 can acquire a history of ward load information by managing the ward load information obtained at each timing in association with the timing. Also, since it is possible to identify when and in which ward a caregiver worked based on the hospital's work records, the notification setting unit 210 can acquire a history of the number of caregivers by referring to the work records.

[0140] The information processing device 200 may also store a history of what kind of notification processing has been performed for which patient in the storage unit 250. When a caregiver has responded to a notification processing, the caregiver may register information indicating that the caregiver has responded to the notification processing in the information processing device 200 via the terminal device 300. The notification setting unit 210 can acquire a history of the time it took for the caregiver to respond after the notification processing was performed by referring to information related to the notification processing and the response.

[0141] In step S402, the notification setting unit 210 calculates an actual load index Z by dividing the value of the ward load information by the number of caregivers. The actual load index Z is information that represents the load per caregiver in the past history. This allows the notification setting unit 210 to obtain multiple pairs (Z, E) of the actual load index Z and the time E required from notification processing to completion of response.

[0142] Furthermore, in step S402, the notification setting unit 210 performs regression analysis based on a plurality of pairs of values ​​(Z, E) to determine the regression equation Z=f(E). Note that the function f here may be a linear function or a nonlinear function. Various methods for determining a regression equation are known, and since these methods can be widely applied in this embodiment, detailed description will be omitted.

[0143] In step S403, the notification setting unit 210 acquires goal information that indicates a time goal for responding to the notification process. The goal information may be a preset value, or may be numerical data that the user inputs on a setting screen that will be described later with reference to FIG. 17. The notification setting unit 210 calculates f(T) from the target time T indicated by the goal information and the regression equation.

[0144] Here, the value of f(T) represents the actual load index estimated based on past history that allows the notification process to be completed within the target time T. As described above, the actual load index is information that represents the load per caregiver based on past history. Therefore, the notification setting unit 210 obtains the number of caregivers working in the target ward during the period for which the allowable load information is to be calculated, and calculates the product of the number of caregivers and f(T). This product represents the load estimated to allow the notification process to be completed within the target time T for the entire ward, and corresponds to the allowable load information in this embodiment.

[0145] FIG. 16 is a diagram illustrating the above processing. In FIG. 16, the vertical axis represents the time E required from notification processing to completion of the response, and the horizontal axis represents the actual load index Z. Here, it is assumed that a regression equation Z=f(E) is obtained, as shown in the prediction graph indicated by the solid line in FIG. 16. In this example, it is assumed that 5 minutes is entered as the target time T. In this case, the value of the vertical axis in the prediction graph is 5 (minutes) at the point where the value of the horizontal axis is 10. Therefore, the value of f(T) is 10, and it can be seen that the allowable load per caregiver is 10. Therefore, the notification setting unit 210 calculates the allowable load information by multiplying the number of caregivers in charge of the ward by 10, which is the load per person.

[0146] As shown in Fig. 16, the notification setting unit 210 may calculate a 95% confidence interval based on a set of multiple values ​​(Z, E). In Fig. 16, the dashed-dotted line is a graph representing the upper limit of 95%, and the dashed line is a graph representing the lower limit of 95%. The notification setting unit 210 may calculate an actual load index based on the target information (target time T) and either the upper limit of 95% or the lower limit of 95%, and calculate allowable load information by multiplying the actual load index by the number of caregivers.

[0147] In the example of Figure 16, the upper limit of 95% represents data for cases where it took a long time to respond to the notification process. In other words, if an upper limit of 95% is used, the allowable load will be estimated low. This will encourage the user to adjust the number of patients for whom the notification condition is set to on, thereby reducing the burden on caregivers.

[0148] The 95% lower limit represents data for cases where notification processing was completed smoothly. In other words, using a 95% lower limit results in an overestimate of the allowable load. This encourages users to adjust the number of patients for whom the notification condition is set to on, enabling more thorough care for patients.

[0149] The interval determined from the past history is not limited to the 95% confidence interval, and various statistics calculated from the history can be used to determine the allowable load information.

[0150] Although the above description deals with an example in which the value of the allowable load information is a simple product of f(T) and the number of caregivers, the method of this embodiment is not limited to this. For example, depending on the caregiver's skills, it is possible that a caregiver can complete care with a relatively heavy load within the target time, or that only a caregiver with a relatively light load can be performed. Therefore, the notification setting unit 210 may calculate the allowable load information by processing the value of f(T) taking into account the caregiver's skills.

[0151] For example, the notification setting unit 210 may calculate the tolerable workload for a caregiver by multiplying f(T) by a coefficient α determined according to the caregiver's skill, α×f(T). Here, α is a coefficient that is 1 for a caregiver with standard skills, and increases as the skill level increases and decreases as the skill level decreases. The skill level of a caregiver is determined based on, for example, the qualifications held by the caregiver, years of service, and evaluations from management, all of which are stored in the storage unit 250.

[0152] The notification setting unit 210 calculates the allowable load information by calculating the sum of α×f(T) calculated for each caregiver. This allows for processing that takes into account the skills of the caregivers, making it possible to calculate the allowable load information with high accuracy.

[0153] 3.5 Screen display Next, examples of screens that the display processing unit 220 causes the display unit 260 or the display unit 310 to display will be described.

[0154] 3.5.1 Settings screen Fig. 17 is an example of a setting screen displayed in step S104 of Fig. 5. For example, the setting screen displays a screen including the number of caregivers at the timing to be processed, the target time T as target information, information indicating the relationship between ward load information and allowable load information, and the setting status of notification conditions for each patient. Note that the timing to be processed may be the current time or a future time.

[0155] In the example of FIG. 17, it is displayed that the number of caregivers in charge of the target ward is 10, and the target time T is set to 5 minutes.

[0156] In addition, an object OB1 is displayed as information representing the relationship between the ward load information and the allowable load information. The object OB1 includes a semicircular pie chart (donut graph) and a needle-shaped object pointing to a predetermined position on the pie chart. For example, the position pointed to by the needle-shaped object changes depending on the relationship between the ward load information and the allowable load information. For example, the center of the pie chart represents a state in which the value of the ward load information and the value of the allowable load information are equal. Using this state as a reference, the position pointed to by the needle-shaped object moves to the left as the value of the ward load information becomes relatively smaller, and the position pointed to by the needle-shaped object moves to the right as the value of the ward load information becomes relatively larger. In this way, it is possible to present the relationship between the ward load information and the allowable load information to the user in a visually easy-to-understand manner.

[0157] However, the information representing the relationship between ward load information and allowable load information may be, for example, a list of the values ​​of the ward load information and the values ​​of the allowable load information, or an icon whose content changes depending on the ratio or difference between the values ​​of the ward load information and the values ​​of the allowable load information, or other types of objects may be used.

[0158] In the example of Figure 17, the notification condition settings are displayed for each of the four patients. For example, the notification conditions for patients A and B are not set (off). For patients C and D, "get out of bed" has already been set as a notification condition. This allows the user to understand the notification conditions for each patient hospitalized in the ward.

[0159] The display processing unit 220 may also display a setting screen including execution conditions for notification processing recommended for the patient (recommended notification conditions) on the display unit. In the example of Fig. 17, the display processing unit 220 displays "sitting up" for Patients A and B, and "edge sitting position" for Patient D as the recommended notification conditions. In this way, it is possible to not only notify the user of the current notification conditions, but also to prompt the user to change the notification conditions to suit the patient's condition.

[0160] The process for determining the recommended notification conditions to be set is as described above with reference to Figures 10 to 14. Note that if the target patient does not fall under any of the judgment master data, or if the target patient falls under the judgment master data but the set notification conditions and the recommended notification conditions match, the recommended notification conditions do not have to be displayed. In the example of Figure 17, the recommended notification conditions for patient C are not displayed.

[0161] 17, the display processing unit 220 may display the reason why the recommended notification condition is recommended together with the recommended notification condition. The reason here may be, for example, a pictogram code in the determination master data of FIG. 11 or FIG. 13, or a patient profile in the determination master data of FIG. 14. In the example of FIG. 17, the reason for patient A, which is limb disability, and the reason for patient B, which is within three days after surgery, correspond to the patient profile. The reason for patient D, which is a wheelchair, is the patient's means of transportation and corresponds to the pictogram code. In this way, it is possible to make the user understand the reason for recommendation, and it is possible to support the user in deciding whether or not to adopt the recommended notification condition.

[0162] The setting screen may also be capable of accepting an operation to change the notification conditions. For example, in FIG. 17 , "sitting up" and "edge sitting position," which represent recommended notification conditions, are objects (such as buttons) that can accept a selection operation, and when a user performs an operation to select the object, the operation content may be transmitted to the notification setting unit 210 of the information processing device 200. The notification setting unit 210 performs a process to change the notification conditions of the target patient to recommended notification conditions based on the received operation content. The operation to change the notification conditions is not limited to the operation of selecting the recommended notification conditions, and may also be capable of changing to any notification conditions, such as by a selection operation using a pull-down menu or an input operation using a text box.

[0163] When a notification condition is changed (e.g., newly added), a caregiver must respond when a notification process for the target patient is performed. Therefore, the notification setting unit 210 performs a process of updating the ward load information by adding the patient load information of the target patient to the ward load information (the process of returning from step S106 to S101 in FIG. 5 and step S304 in FIG. 7). The display processing unit 220 updates the information representing the relationship between the ward load information and the allowable load information by using the updated ward load information. In the example of FIG. 17, the position indicated by the needle-shaped object moves to the right as the ward load information is updated. Note that an existing notification condition may be deleted. In this case, the notification setting unit 210 performs a process of updating the ward load information by subtracting the patient load information of the target patient from the ward load information. As a result, in the example of FIG. 17, the position indicated by the needle-shaped object moves to the left.

[0164] Furthermore, the notification setting unit 210 may determine whether or not to permit the setting of execution conditions for notification processing for patients for whom notification processing has not been set, based on a comparison process between the ward load information and the allowable load information. The display processing unit 220 may display different setting screens depending on whether the notification setting unit 210 determines that the setting of notification conditions is permitted or not permitted.

[0165] For example, as shown in FIG. 17, if the value of the ward load information is small relative to the value of the allowable load information and the caregiver still has some leeway, the notification setting unit 210 may allow the addition of a new notification condition. In this case, the display processing unit 220 displays a setting screen including recommended notification conditions for patient A and patient B, for which notification conditions have not been set, as shown in FIG. 17, for example. On the other hand, if the value of the ward load information is very large relative to the value of the allowable load information and the caregiver does not have enough leeway, the notification setting unit 210 may refuse to add a new notification condition. In this case, the display processing unit 220 displays a setting screen that does not include the recommended notification conditions for patient A and patient B. For example, in FIG. 17, "getting up" for patient A and patient B may not be displayed.

[0166] Furthermore, the display / hide of recommended notification conditions is not limited to those determined in common for multiple patients. For example, if the patient load information value of patient A is small and the patient load information value of patient B is large, adding notification conditions will have less of an impact on patient A than on patient B. Therefore, if the ward load information value is very large relative to the allowable load information value, the display processing unit 220 may display a setting screen that includes recommended notification conditions for patient A but does not include recommended notification conditions for patient B. Alternatively, patient B, who has large patient load information, may be considered to be in greater need of care than patient A and should be prioritized. Therefore, if the ward load information value is very large relative to the allowable load information value, the display processing unit 220 may display a setting screen that includes recommended notification conditions for patient B but does not include recommended notification conditions for patient A.

[0167] Furthermore, the decision to display / hide the recommended notification conditions is not limited to when adding new notification conditions, but may be made when changing notification conditions for a patient for which the notification conditions have already been set. For example, the display processing unit 220 may determine whether to display a setting screen including the recommended notification conditions for patient D or a setting screen not including the recommended notification conditions for patient D, as shown in Fig. 17, based on the relationship between the ward load information and the allowable load information.

[0168] 3.5.2 Screens containing pictograms Figure 18 is an example of a patient screen that displays information about a specific patient and includes pictograms. As shown in Figure 18, the patient screen includes the patient's name, notification conditions, and a pictogram corresponding to the pictogram code.

[0169] 18, a patient named AAAA is displayed. Also, an object OB2 is displayed indicating that the notification condition is set to "standing up" and that a notification will be sent when three seconds or more have passed since the motion was detected.

[0170] Furthermore, the display processing unit 220 may display a screen including an object representing a warning when the notification conditions set for the patient differ from the recommended notification conditions. In the example of Fig. 18, an object OB3 including an exclamation mark (!) next to the patient's name is displayed. This makes it possible to prompt the user to review the notification conditions.

[0171] Although an example has been shown here in which an object OB3 representing a warning is displayed on a screen displaying individual patient information, the present invention is not limited to this. For example, the display processing unit 220 may display a setting screen including an object representing a warning when the execution conditions recommended for the patient differ from the execution conditions set for the patient. For example, the display processing unit 220 may display a warning object on the setting screen shown in FIG. 17. As described above, since the notification conditions can be changed on the setting screen, it is useful to encourage the user to review the notification conditions on the setting screen.

[0172] The patient screen may also include a pictogram that matches the patient's condition. For example, patient AAAA's means of transportation is walking, so the pictogram code 110, which represents walking, is assigned. In this case, the display processing unit 220 displays a patient screen that includes a pictogram that corresponds to the pictogram code 110. Similarly, in Figure 18, a patient screen is displayed that includes a pictogram that corresponds to the free space in the hospital room (Figure 10), a pictogram that corresponds to a state in which drinking is permitted, and a pictogram that corresponds to a state in which eating and drinking at night is prohibited.

[0173] Furthermore, a patient AAAA may be associated with factors requiring special attention, such as the need for blood glucose monitoring, wearing both hearing aids, going out or staying out overnight, being prohibited from consuming alcohol, and being prescribed medication to be taken before meals. This information may be managed, for example, as a warning code or as other information. The patient screen may include, for example, text indicating the content of the warning code.

[0174] The patient screen may also include information such as the patient's doctor, nurse in charge, admission date, expected discharge date, and department.

[0175] 19 is an example of a setting screen for setting detailed notification conditions for each patient. The screen shown in FIG. 19 may pop up when a predetermined operation is performed on the patient screen of FIG. 18, for example. The predetermined operation here is, for example, a selection operation of object OB2 representing the notification conditions, but other operations may also be used. The setting of notification conditions in this embodiment may be performed on the screen described above using FIG. 17, on the screen shown in FIG. 19, or both.

[0176] In FIG. 19 , for example, a toggle button for turning the notification process on / off (setting / not setting the notification condition) is displayed. When the notification process is set to on using the toggle button, the display processing unit 220 displays a button for selecting one of “awakening,” “sitting up,” “sitting on the edge of the bed,” “getting out of bed,” and “monitoring” as a notification condition related to the patient notification condition. In the example of FIG. 19 , “monitoring” is set, so the display processing unit 220 displays multiple buttons for selecting the time from moving out of the hospital room (or getting out of bed) to the execution of notification. In this example, the 10-minute button is selected. Note that the load sensor 140 may be used to determine the patient notification condition. Therefore, the display processing unit 220 may display a button prompting the input of the patient's weight in order to set a reference load value. When the decision button is selected, the notification setting unit 210 sets the notification condition for the patient according to the selected button. In the example of FIG. 19 , “monitoring” and “10 minutes” are selected, so the notification setting unit 210 sets the notification condition for the target patient as “monitoring (10 minutes).”

[0177] It is assumed here that the patient has not performed the necessary notification settings. Therefore, the display processing unit 220 may display a setting screen including an object OB4 representing a warning, as shown in Fig. 19. The object OB4 here is an icon representing a bell and warning text, but as can be seen from the example of the object OB3 in Fig. 18, the form of the warning object is not limited to this.

[0178] Figure 20 is an example of an editing screen for associating patients with pictograms (pictogram codes). For example, the editing screen may include pictograms associated with each of multiple patients. In the example of Figure 20, four pictograms, such as walking and free movement in the room, are associated with patient AAAA (see Figure 18), while no pictograms are associated with other patients, and an icon indicating "not assigned" is displayed.

[0179] For example, when a selection operation of any pictogram (icon) is performed, the display processing unit 220 may display a list of pictograms that can be set. The list of pictograms may include, for example, the multiple pictograms shown in FIGS. 12A and 12B. The list here may also include icons corresponding to attention codes. When a user performs an operation to select any pictogram in the list, the selected pictogram and a pictogram code corresponding to the selected pictogram are assigned to the target patient. In this way, it is possible to assign a pictogram code corresponding to the condition of each patient to each patient. The assigned pictogram code may be used in the process of determining recommended notification conditions, as described above with reference to FIGS. 10 to 14, or may be used in the display process of the patient screen shown in FIG. 18.

[0180] 4. Timing of execution of each process Next, specific examples of the execution timing of the process for obtaining ward load information (step S101 in FIG. 5) and the execution timing of the process for obtaining allowable load information (step S102) will be described.

[0181] 4.1 Ward Load Information As described above, in the method of this embodiment, the load on caregivers on a ward-by-ward basis when notification processing is performed is calculated as ward load information, and the relationship between the ward load information and the allowable load information is presented on a display screen such as a settings screen.

[0182] Ward load information is calculated based on the patient load information of multiple patients, as described above with reference to FIG. 7. Therefore, when the patient load information changes, it is desirable that the ward load information also change accordingly. This prevents the value of the ward load information from deviating from the actual degree of load that may be placed on caregivers. As a result, more appropriate notification settings can be achieved.

[0183] For example, the notification setting unit 210 may obtain patient load information based on an electronic medical record. Specifically, as described above using step S303 in Fig. 7, the notification setting unit 210 may read medical condition information such as "limb disability," "cerebral infarction," and "within Y days after surgery" from the electronic medical record, and perform processing to add a value corresponding to the medical condition to the patient load information. Furthermore, if the fall risks shown in Nos. 1 to 3 in Fig. 8 are recorded in the electronic medical record, this information may be read from the electronic medical record and used in the processing to determine the patient load information.

[0184] In such a case, the notification setting unit 210 may update the patient load information when an update to the electronic medical record is used as a trigger. For example, the notification setting unit 210 may periodically read out the update history of the electronic medical record stored in the storage unit 250 or the like, and if the electronic medical record has been updated, execute the process of step S101 in FIG. 5. Details of the process of step S101 are as described above with reference to FIG. 7. Specifically, the notification setting unit 210 executes a process of adding a predetermined value to the value of the patient load information based on the read result of the electronic medical record and the load parameter master (step S303 in FIG. 7). Alternatively, when an operation to update the electronic medical record is performed from a terminal device used by a doctor, an instruction to execute the process of updating the patient load information may be push-notified to the notification setting unit 210.

[0185] The notification setting unit 210 then updates the ward load information based on the updated patient load information (step S304 in FIG. 7). In this way, when a change in the patient's condition is recorded, the patient load information and ward load information are promptly updated. This makes it possible to prevent the value of the ward load information from deviating from the degree of load that may actually occur on caregivers.

[0186] Furthermore, when a period of a given length is divided into multiple subperiods, the notification setting unit 210 may update the ward load information at the timing of a transition from one subperiod to another of the multiple subperiods. In other words, the notification setting unit 210 may update the ward load information when a transition from one subperiod to another is used as a trigger.

[0187] Here, the period of a given length is one day, and the sub-periods may be periods obtained by dividing one day into multiple periods, such as morning, afternoon, night, late night, etc. In this way, it becomes possible to appropriately adjust the ward load information throughout the day.

[0188] For example, during the late night hours, it is expected that many patients will be asleep. Therefore, compared to other times when patients are more active, the probability of an event (such as getting out of bed) that would satisfy the notification condition occurring is lower during the late night hours. Even if there is a patient for whom a significant burden would be placed on the caregiver if a notification process were executed, no burden would be placed on the caregiver if the notification process for that patient were not executed. In other words, since the probability of notification processing occurring during the late night hours is lower than at other times, the degree of burden that may occur is also relatively low. Alternatively, since patients are less active during the late night hours, even if some notification process is executed, it is easier for the caregiver to respond, and the burden may be relatively small.

[0189] Therefore, the notification setting unit 210 may correct the ward load information according to the sub-period. For example, as described above, since the probability of notification processing occurring and the load required for response may be relatively low late at night, the notification setting unit 210 performs correction processing to reduce the value of the ward load information. Furthermore, the correction processing here is not limited to reducing the value of the ward load information in the late-night time slot. For example, the notification setting unit 210 may perform correction processing to increase the value of the ward load information in the daytime when patients are most active. In addition, various modifications can be made to the setting of time slots within a day and the content of the correction processing for each time slot.

[0190] When updating ward load information, the patient load information value for each of multiple patients may be updated, and the updated ward load information may be calculated based on the updated patient load information. For example, the notification setting unit 210 may multiply the patient load information value by a given coefficient set for each patient. Alternatively, the storage unit 250 may store different load master data depending on the time period. The notification setting unit 210 may then calculate patient load information for the time period to be processed based on the pictogram code or patient profile (condition information) associated with the patient and the load master data that matches the time period to be processed.

[0191] When patient load information is updated for each sub-period in this way, it becomes possible to finely adjust the ward load information. For example, when using the load master data in Figure 8, it is possible to adjust the correction range for each item, such as increasing the difference in the load value for the risk of falling between daytime and nighttime, and decreasing the difference in the distance from the nurse station between daytime and nighttime. Therefore, it is possible to flexibly adjust the correction range for patient load information depending on which item in the load master data a patient matches.

[0192] Alternatively, when updating ward load information, the notification setting unit 210 may directly correct the ward load information calculated from the patient load information without updating the value of the patient load information. For example, the notification setting unit 210 may use the value of the ward load information calculated from the patient load information as a reference value and multiply the reference value by a correction coefficient according to the time period. In this case, there is no need to update individual patient load information, which reduces the processing load.

[0193] Furthermore, the given period and subperiod are not limited to the above examples. For example, the given period may be one week, and the subperiod may be one day. In this case, it becomes possible to adjust the patient load information according to the day of the week. For example, if care (rehabilitation, etc.) is provided in a ward on a specific day of the week that is not available on other days, it is possible that the probability of notification processing occurring and the load that may occur if notification processing is performed differ between that specific day and other days of the week. In this regard, by adjusting the ward load information according to the day of the week, it becomes possible to reflect the above-mentioned fluctuations depending on the day of the week in the ward load information.

[0194] Furthermore, a given period may be a relatively long period, such as one year, and a sub-period may be one month or a season, such as spring, summer, autumn, or winter. For example, during the season when seasonal influenza is prevalent, the burden on caregivers may be greater than in other seasons. For example, if influenza occurs in a ward, infection prevention measures may be necessary in addition to regular care. In this case, for example, by increasing the value of the ward load information in winter relatively compared to other seasons, it becomes possible to respond to such seasonal load fluctuations. Note that the ward load information may be updated by updating the patient load information, as described above, or by directly correcting the ward load information.

[0195] 4.2 Load capacity information Furthermore, when the caregiver group includes multiple caregivers who work in shifts, the notification setting unit 210 may update the allowable load information when the multiple caregivers are replaced. As described above with reference to Figures 15 and 16, the allowable load information is determined, for example, by the number of caregivers. Therefore, by updating the allowable load information at the time of a shift change (shift change) when the number of caregivers may change, it is possible to obtain the allowable load information with high accuracy.

[0196] For example, if a three-shift system is adopted in which caregivers work in shifts by dividing 24 hours into three shifts, the process shown in step S102 in Fig. 5 is executed at each of the timings for changing between day shifts and night shifts, between night shifts and night shifts, and between night shifts and day shifts. Also, other working styles such as a two-shift system may be used.

[0197] For example, when calculating allowable load information for day shifts, the notification setting unit 210 may execute processing including the regression analysis shown in FIG. 16 using historical data for day shifts from the past month. Similarly, allowable load information for night shifts is calculated based on historical data for past night shifts, and allowable load information for night shifts is calculated based on historical data for past night shifts. In this way, the historical data can be separated by working time period, making it possible to calculate allowable load information with high accuracy. However, the notification setting unit 210 may use the same historical data regardless of working time period.

[0198] In the above example, the process of obtaining the allowable load information may be executed a predetermined number of times each day (for example, three times each day). In this case, the data used as the history data is data for the past month, starting from the processing timing. In other words, the notification setting unit 210 may execute the process of obtaining the allowable load information each day, shifting the range of the history data by one day at a time. In this way, the discrepancy between the target range of the history data and the processing timing is suppressed, making it possible to obtain the allowable load information with high accuracy.

[0199] However, the range of historical data used to calculate the allowable load information is not limited to the period starting from the processing timing. For example, the notification setting unit 210 may calculate the allowable load information based on historical data from the same season one year ago. For example, during periods when new caregivers are hired or transferred, the number of caregivers unfamiliar with the work increases, which may reduce the allowable load level. In this case, using historical data from the same season makes it possible to properly calculate the allowable load information.

[0200] 4.3 Dealing with patients outside the hospital The above describes an example in which patient load information is obtained for patients in a hospital (hereinafter also referred to as inpatients), and ward load information is obtained based on patient load information for each ward. However, the method of the present disclosure is not limited to this, and information on patients outside the hospital may also be used.

[0201] The patient here is, for example, a patient whose electronic medical record has been acquired by the information processing device 200. Specifically, the patient here may be a patient who has visited or been admitted to a hospital that has introduced the service according to this embodiment, and who is currently an outpatient patient recuperating at a place other than a hospital, such as at home or in a nursing home. In this case, the information processing device 200 can determine the risk of falling and medical condition information (presence or absence of limb disabilities, etc.) by referring to the electronic medical record of the outpatient patient.

[0202] The notification setting unit 210 may obtain patient load information for an out-of-hospital patient based on the out-of-hospital patient's electronic medical record and load master data. The patient load information for an out-of-hospital patient is information that indicates the degree of load required to treat the out-of-hospital patient, for example, when the out-of-hospital patient is transported to a hospital ward. In this case, transport refers to emergency transport in the narrow sense, but may also include cases where the patient visits an outpatient clinic on their own.

[0203] The process for obtaining patient load information is the same as the example in Fig. 7. However, in this modification, the processing target of step S301 is not limited to beds 100 in the ward, but is expanded to include out-of-hospital patients.

[0204] The notification setting unit 210 performs processing to add the patient load information of out-of-hospital patients to the ward load information of the ward corresponding to the emergency outpatient department and / or the ward load information of the ward corresponding to the medical department where the patient has a history of visiting in the past. In this way, it becomes possible to obtain ward load information that includes the load when an out-of-hospital patient is transported to the target ward. As a result, it becomes possible to perform appropriate notification processing that takes into account cases where an out-of-hospital patient is transported.

[0205] When out-of-hospital patients are the target, the notification setting unit 210 may obtain the patient load information or ward load information using a method different from that used when inpatients are the control. For example, when out-of-hospital patients are the target, the notification setting unit 210 may perform a correction process to change the value of the patient load information compared to inpatients.

[0206] For example, if an outpatient patient falls or trips while trying to stand up from bed 100, it is likely that the patient's family or other relatives will first check the patient's condition and, if there does not appear to be any serious injuries, will monitor the patient's condition without transporting the patient to a hospital. The same applies if symptoms such as irregular breathing occur; if the problem can be resolved by the patient's family or other relatives, no care at the hospital is necessary. In other words, when an outpatient patient is transported to a hospital, it is assumed that the patient's condition is serious and the burden of treatment is high. Considering this, it is desirable to set the patient load information for outpatient patients higher than that for inpatient patients.

[0207] On the other hand, as described above, if an out-of-hospital patient can be cared for by a family member or the like, care by a caregiver (e.g., a nurse) working at the hospital is not required. In contrast, abnormalities occurring in inpatients must be handled by a caregiver working at the hospital. Considering this, out-of-hospital patients are less likely to require care from a nurse or the like than inpatient patients, so it is desirable to set the patient load information for out-of-hospital patients lower than that for inpatient patients. Furthermore, in cases where an emergency transport is required, the destination is not fixed; rather, the destination is dynamically determined from multiple hospitals that can handle emergency care according to availability. Therefore, even if a patient has a history of being hospitalized or visiting a certain hospital, they may not necessarily be transported to that hospital, and may be transported to a different hospital. From this perspective, out-of-hospital patients are less likely to require care in a ward than inpatient patients, so it is desirable to set the patient load information for out-of-hospital patients lower than that for inpatient patients.

[0208] For example, the notification setting unit 210 may set a correction coefficient β1 greater than 1 and a correction coefficient β2 less than 1. The notification setting unit 210 may obtain patient load information for outpatients by using the same load master data as for inpatients and then performing corrections using the correction coefficients β1 and β2. As described above, the correction coefficient β1 is a coefficient that takes into account the possibility that an outpatient patient's condition may be more serious if transported to a hospital. As described above, the correction coefficient β2 is a coefficient that takes into account the possibility that an outpatient patient may not be transported to a target ward even if an abnormality occurs in the outpatient patient. The specific values ​​of β1 and β2 are arbitrary and can be flexibly determined taking into account the degree of influence of each factor. For example, the notification setting unit 210 may determine the correction coefficient β1 based on the medical history, medication history, etc. of the outpatient patient. The notification setting unit 210 may also obtain emergency patient admission histories for multiple emergency wards included in the target area and set the correction coefficient β2 based on the admission histories.

[0209] As described above, out-of-hospital patients are not transported to a fixed hospital. Therefore, the notification setting unit 210 may perform a process of adding the patient load information of the out-of-hospital patient to the ward load information for each of multiple hospitals to which the out-of-hospital patient may be transported. In this case, the notification setting unit 210 may vary the correction coefficient β2 depending on the hospital. For example, the notification setting unit 210 may calculate the ratio of the number of admitted patients to the total number of emergency patients for each hospital based on past history, and use this ratio as the correction coefficient β2 for the target hospital.

[0210] In the above, an example has been described in which correction processing is performed after using common load master data for inpatients and outpatients, but this is not limited to this. For example, the notification setting unit 210 may obtain patient load information for outpatients using load master data for outpatients that is different from the load master data for inpatients described above. In the load master data for outpatients, for example, the hospital (ward) may be included in the addition conditions, and different load values ​​may be added for each hospital.

[0211] Although the above describes an example in which the process for obtaining patient load information differs between inpatients and outpatients, this is not limiting. For example, as described above, a correction process may be performed after obtaining ward load information. For example, the notification setting unit 210 may obtain ward load information that takes into account outpatients by performing a correction process on ward load information obtained by performing the same process for inpatients and outpatients, depending on the proportion of outpatients among the total number of patients, the history of emergency patient admissions for the ward in question, etc.

[0212] The process after the ward load information is obtained is the same as in the example described above. That is, for each of the multiple hospitals (wards), a notification process is executed based on the relationship between the ward load information including out-of-hospital patients and the allowable load information of the ward.

[0213] 5. Data Collection Using the Bed Although the above description has been given of an example in which the bed 100 and the terminal device 300 are separate entities, the method of the present disclosure is not limited to this. For example, the bed 100 may be a nursing care bed whose bottom surface angle and height are adjustable as described above, and may include a control device (control box) that is provided with a processor and memory for controlling these. The control device may also serve as the terminal device 300 of this embodiment.

[0214] For example, the information processing device 200 stores a table linking the ID of the bed 100 with the patient, thereby identifying the patient using the bed 100. The bed 100 (terminal device 300) identifies the location of the bed 100 by communicating with a communication device that identifies the location. The communication device may be, for example, a router, or a wall unit (for example, a smart plug that connects to a commercial power source) that is placed on the wall of a room or the like.

[0215] The bed 100 (terminal device 300) communicates with devices having communication capabilities (such as the detection device 400), and data from each device is registered with the patient identified. Such beds are described, for example, in U.S. patent application Ser. No. 17 / 360,382, filed June 28, 2021, entitled "Monitoring of patient supports," or U.S. patent application Ser. No. 17 / 883,071, filed August 8, 2022, entitled "Hospital headwall communication system." These patent applications are incorporated herein by reference in their entireties.

[0216] In this way, it becomes possible to collect various information in the vicinity of the bed 100, determine whether the notification conditions are met based on the collected information, and present the determination results.

[0217] Although the present embodiment has been described in detail above, those skilled in the art will readily understand that many modifications are possible without substantially departing from the novel features and advantages of the present embodiment. Therefore, all such modifications are intended to be included within the scope of the present disclosure. For example, a term described at least once in the specification or drawings with a different term having a broader or equivalent meaning may be replaced with that different term anywhere in the specification or drawings. Furthermore, all combinations of the present embodiment and modifications are also included within the scope of the present disclosure. Furthermore, the configurations and operations of the information processing system, bed, detection device, sensing device, information processing device, terminal device, etc. are not limited to those described in the present embodiment, and various modifications are possible. [Explanation of symbols]

[0218] 10 Information processing system, 100, 100-1, 100-2 Bed, 140, 140A-140D Load sensor, 160 Movable part, 160a Leg, 160b Bottom, 180 Mattress, 200 Information processing device, 210 Notification setting unit, 220 Display processing unit, 230 Notification determination unit, 240 Notification unit, 250 Memory unit, 260 Display unit, 300, 300-1, 300-2 Terminal device, 310 Display unit, 320 Notification unit, 400 Detection device, 500 Sensing device, OB1-OB4 Object

Claims

1. a notification setting unit that sets execution conditions for a notification process that notifies a caregiver that patient confirmation is required; a notification unit that executes the notification process when it is determined that the execution condition is satisfied; a display processing unit that performs processing to display a setting screen used for setting the notification processing on a display unit; Including, The notification setting unit When the notification process for the patient is performed, ward load information is obtained that indicates the degree of load on the caregiver per ward required for the caregiver to respond; calculating allowable load information representing an allowable load level based on target information representing a time target for responding to the notification process and the number of caregivers responding to the notification process; The display processing unit An information processing system that performs display processing on the setting screen including information indicating the relationship between the ward load information and the allowable load information.

2. In claim 1, the patients include a plurality of patients admitted to the ward; The notification setting unit For each of the plurality of patients, patient load information is obtained that indicates the degree of load required for the caregiver to handle the patient when the notification process is performed; An information processing system that calculates the ward load information that indicates the degree of load on the ward based on the patient load information corresponding to the plurality of patients.

3. In claim 2, The notification setting unit An information processing system that determines the patient load information based on at least one of the patient's risk of falling, the patient's condition, and information about the patient's room.

4. In claim 3, The notification setting unit determining the patient burden information based on the patient's electronic medical record; updating the patient load information when the electronic medical record is updated; An information processing system that updates the ward load information based on the updated patient load information.

5. In any one of claims 1 to 4, The notification setting unit An information processing system that updates the ward load information when a period of a given length is divided into multiple subperiods and the period changes from one of the multiple subperiods to another.

6. In any one of claims 1 to 4, The notification setting unit determining whether to permit setting of the execution conditions for the notification process for the patient for whom the notification process has not been set based on a comparison process between the ward load information and the allowable load information; The display processing unit An information processing system that displays different setting screens depending on whether it is determined that the setting of the execution conditions is permitted or not.

7. In any one of claims 1 to 4, When the caregiver includes a plurality of caregivers, and the plurality of caregivers work in shifts, The notification setting unit is an information processing system that updates the allowable load information when the caregivers are replaced.

8. In any one of claims 1 to 4, The notification setting unit An information processing system that determines the allowable load information based on a history of the ward load information and a history of time information that indicates the time required for the caregiver to respond to the notification process.

9. In any one of claims 1 to 4, The notification setting unit An information processing system that determines the execution conditions recommended for the patient based on at least one of the patient's medical condition, the patient's allowable range of movement, the patient's means of transportation, and the bed's range of movement recommended for the patient.

10. In claim 9, The display processing unit an information processing system that displays the setting screen including the execution conditions recommended for the patient;

11. In claim 9, The display processing unit An information processing system that displays the setting screen including an object representing a warning when the execution conditions recommended for the patient differ from the execution conditions set for the patient.

12. In any one of claims 2 to 4, The notification unit An information processing system that determines a notification mode of the notification process based on the patient load information.

13. A setting screen used for setting the notification process is displayed on the display unit. setting an execution condition for the notification process that notifies the caregiver that a patient check is required; When it is determined that the execution condition is satisfied, the notification process is executed; In setting the execution conditions, deriving ward load information that indicates the degree of load required for the caregiver to respond on a ward basis when the notification process for the patient is performed; calculating allowable load information representing an allowable load level based on target information representing a time target for responding to the notification process and the number of caregivers responding to the notification process; In the process of displaying the setting screen, An information processing method for performing display processing on the setting screen including information indicating the relationship between the ward load information and the allowable load information.

Images