Bed system and information processing method

Abstract

Providing bed systems and information processing methods suitable for patient care. [Solution] The bed system is a bed system including a bed, and includes a control unit that, if neither location identification information representing the location of the bed nor patient identification information representing the patient using the bed has been acquired, acquires location identification information, acquires patient identification information when location identification information has been acquired, and associates bed identification information that identifies the bed, location identification information and patient identification information when patient identification information has been acquired.

Description

Technical Field

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

Background Art

[0002] Conventionally, techniques for tracking the position of a bed or a nurse have been known. For example, Patent Document 1 discloses a technique for identifying the position of a bed by using a communication module provided on a wall.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] To provide a bed system, an information processing method, and the like suitable for caring for patients and the like.

Means for Solving the Problems

[0005] One aspect of the present disclosure is a bed system including a bed, the position identification information representing the position of the bed and the patient identification information representing the patient using the bed are not obtained, obtaining the position identification information, obtaining the patient identification information when the position identification information is obtained, bed identification information for identifying the bed when the patient identification information is obtained, and a control unit for associating the position identification information and the patient identification information.

[0006] Another aspect of this disclosure relates to an information processing method for a bed system including a bed, which performs a process to acquire location identification information when neither location identification information representing the location of the bed nor patient identification information representing the patient using the bed has been acquired; performs a process to acquire patient identification information when location identification information has been acquired; and associates bed identification information identifying the bed, location identification information, and patient identification information when patient identification information has been acquired. [Brief explanation of the drawing]

[0007] [Figure 1] This diagram explains the background of this disclosure. [Figure 2] This is a diagram illustrating an example of the configuration of an information processing system. [Figure 3] This is a diagram illustrating an example of a bed configuration. [Figure 4] This diagram illustrates an example configuration of a bedside terminal device. [Figure 5] This diagram illustrates an example of a server system configuration. [Figure 6] This diagram illustrates an example of a terminal device configuration. [Figure 7] This is a diagram illustrating the situation around the bed. [Figure 8] This is a sequence diagram illustrating the process of coordinating the bed, location, and patient. [Figure 9] This figure shows an example of data linking beds, locations, and patients. [Figure 10] This figure shows an example of data stored in the memory unit of a server system. [Figure 11] This is a sequence diagram illustrating the patient authentication process based on facial images. [Figure 12] This is a sequence diagram illustrating the coordinated process between the bed and the sensing device. [Figure 13] This figure shows an example of data used to manage sensing data. [Figure 14] This is a sequence diagram illustrating the activation process for equipment (electronic devices). [Figure 15] This is a sequence diagram for explaining the confirmation and cancellation process of the cooperation between the bed and the position (bedside terminal device). [Figure 16] This is a diagram for explaining the transition of code information according to the cooperation state. [Figure 17] This is a diagram showing an example of a screen for displaying code information for patients. [Figure 18] This is a diagram showing an example of a screen for displaying code information for nurses. [Figure 19] This is a sequence diagram for explaining the transition of code information according to the cooperation state. [Figure 20] This is a sequence diagram for explaining the update process of code information based on the change of a doctor's instruction. [Figure 21] This is a diagram showing an example of code information displayed in association with an update object. [Figure 22] This is a diagram for explaining the process using code information for nurses. [Figure 23] This is a sequence diagram for explaining the process related to sensing data. [Figure 24] This is a diagram for explaining the process using code information for nurses. [Figure 25A] This is a diagram showing an example of a screen displayed based on code information for patients. [Figure 25B] This is a diagram showing an example of a screen displayed based on code information for patients. [Figure 25C] This is a diagram showing an example of a screen displayed based on code information for patients. [Figure 26] This is a sequence diagram for explaining the settlement process based on code information for patients. [Figure 27] This is a diagram for explaining the settlement process based on code information for patients. [Figure 28] This is a diagram showing an example of a screen for displaying code information for delivery staff. [Figure 29A] This is a diagram showing an example of a screen displayed based on code information for patients. [Figure 29B] This is a diagram showing an example of a screen displayed based on code information for patients. [Figure 29C] This figure shows an example of a screen displayed based on patient code information. [Figure 30] This figure shows an example of the placement of static code information. [Figure 31] This diagram shows an example of the arrangement of wireless communication tags and readers. [Figure 32A] This figure shows an example of data included in an electronic medical record. [Figure 32B] This figure shows an example of data included in an electronic medical record. [Figure 33A] This diagram illustrates the modes of the bedside terminal device. [Figure 33B] This diagram illustrates the modes of the bedside terminal device. [Modes for carrying out the invention]

[0008] This embodiment will be described below with reference to the drawings. In the drawings, the same or equivalent elements are denoted by the same reference numerals, and redundant descriptions are omitted. This embodiment described below is not intended to unduly limit the content described in the claims. Furthermore, not all of the configurations described in this embodiment are essential components of this disclosure.

[0009] 1. Background Figure 1 is a diagram illustrating the background of the invention relating to this disclosure, and illustrates the work environment of a nurse working in a hospital or the like. As shown in Figure 1, sensing devices (hereinafter also referred to as sensing devices) that sense the patient's condition, such as an imaging device 700 and a detection device 810, are placed near the patient's bed 100. The nurse determines the patient's condition by acquiring sensing data obtained by these devices. For example, the nurse may view the sensing data displayed on the display unit 240 of the bedside terminal device 200, or she may view the sensing data using a terminal device 600 that she carries with her (details will be described later with reference to Figure 2). In addition, if it is determined that the patient's condition has suddenly changed based on the sensing data, the nurse may receive a notification to that effect.

[0010] Patients may also use a nurse call system to summon a nurse. For example, the bedside terminal device 200 may have a function to execute a nurse call, or a separate nurse call device with buttons, a microphone, a speaker, etc., may be placed near the bed 100.

[0011] As shown in Figure 1, nurses receive instructions from physicians. These instructions specify actions that nurses must follow in order to provide appropriate treatment to patients, such as "imposing dietary restrictions on the patient" or "administering specific medications to the patient." The term "physician" here may include both physicians from the department to which the nurse belongs (hereinafter also referred to as the "affiliated department") and physicians from other departments, as shown in Figure 1. Physicians from other departments may be physicians from different departments within the same hospital as the nurse, or physicians from different hospitals.

[0012] Instructions from a physician may be communicated verbally or in writing by the physician or other nurses during handover or other means. Alternatively, data representing the physician's instructions may be registered in the electronic medical record, and nurses may access the electronic medical record using devices such as bedside terminals 200 or terminals 600 to obtain the physician's instructions.

[0013] Furthermore, as shown in Figure 1, nurses can provide more appropriate care by utilizing the tacit knowledge of highly skilled nurses or by delegating some of their tasks to staff from other professions such as occupational therapists and physical therapists.

[0014] It should be noted that methods for digitizing the tacit knowledge of experienced nurses are already known, and similar methods may be applied to the sharing of tacit knowledge in this embodiment. Digitization here may involve, for example, creating training data that represents the tacit knowledge of experienced nurses using digital data, or creating application software (hereinafter simply referred to as "application") that allows users to perform care according to the training data. By using such an application, it becomes possible for less experienced nurses to perform the same actions as experienced nurses.

[0015] As described above, nurses must comply with physicians' instructions and take appropriate action when changes in a patient's condition are observed based on sensing data, or when a nurse call is made. To achieve this, nurses are required to clearly understand the physician's instructions, know how to respond appropriately to sudden changes in a patient's condition, and appropriately understand the patient's wishes when a nurse call is made. However, some of this information is not easy for nurses to grasp, making it difficult for them to take appropriate action.

[0016] Information that nurses may find difficult to grasp includes instructions (patient behavior and changes in instructions), risks (sudden changes in patient condition), and patient wishes.

[0017] For example, if a patient has multiple illnesses, the doctor's instructions regarding the patient may include instructions related to the nurse's department and instructions related to other departments. For instance, if a patient being treated for diabetes develops a severe condition and develops cataracts, leading to hospitalization in the ophthalmology department, the ophthalmology nurse will receive instructions regarding the cataracts from the ophthalmologist in their department, as well as instructions regarding diabetes from the internist, and will monitor the patient's behavior to ensure compliance with both sets of instructions. In this example, the ophthalmology nurse needs to monitor the patient's behavior based on the instructions regarding dietary and fluid restrictions for diabetes. However, ophthalmology nurses are often unfamiliar with caring for diabetic patients, making it difficult for them to understand how to comply with the instructions (how to monitor the patient's behavior).

[0018] Furthermore, in the acute phase, when a patient's condition is likely to change rapidly, physicians' orders may change suddenly. In this case, regardless of the medical department, it is not easy for nurses to grasp the changes in physicians' orders (changes in orders). For example, nurses check the latest orders when handover takes place, but if the orders change after that handover, it is not easy for nurses to grasp the changes. It is assumed that the changed orders will be registered in the electronic medical record, but in order for nurses to grasp these orders, they would need to proactively check the details of the electronic medical record. Therefore, forcing nurses to do such checks is not easy from the perspective of workload.

[0019] Furthermore, patient risks (which may specifically include risks related to changes in condition, and which will also be referred to as sudden changes in patient condition hereafter) can be detected using sensing data, etc., as described above, and by having nurses take appropriate measures according to the risks, it is possible to suppress the worsening of the patient's condition. However, as can be seen from the examples of internal medicine and ophthalmology above, nurses may have difficulty understanding risks that they do not frequently encounter in their department, and therefore may also have difficulty understanding countermeasures. For example, if a patient with asthma is admitted to the ophthalmology department, the ophthalmology nurse can understand the patient's asthma using the electronic medical record, but even if symptoms such as coughing are detected, the detection result may not be immediately linked to asthma. Moreover, the difficulty in linking symptoms and risks (such as asthma) is particularly noticeable at night or when nurses who are not assigned to the patient are taking care of them. This is because nurses do not necessarily have the information necessary to interpret what the patient's behavior means.

[0020] Furthermore, when a patient uses the nurse call system, the patient's requests can be diverse, making it difficult to understand the patient's needs (or understand their wishes) solely from the call system. For example, even if a patient complains of a headache via the nurse call system, the nurse may not be able to identify the underlying disease or determine the necessary response. This is particularly evident when the patient has multiple illnesses, as in the example above.

[0021] Therefore, the information processing system 10 according to this embodiment enables nurses to easily recognize information that is difficult to grasp. Specifically, the information processing system 10 provides a nurse interface that presents information including physician instructions, and a patient interface that easily reflects the patient's wishes.

[0022] As a prerequisite, the information processing system 10 according to this embodiment performs processing to easily link the bed 100, the location where the bed 100 is placed (ward and patient room), and the patient using the bed 100. Furthermore, the information processing system 10 in this embodiment may also perform processing to link risk detection devices and equipment (electronic devices) used by the patient with the patient. Equipment includes, for example, a television 910 and a refrigerator 920, which will be described later using Figure 2. By performing such system linkage, it becomes possible to appropriately link various information acquired around the bed 100 with the patient. As a result, it becomes possible to provide a nurse interface that presents information about the patient (especially information that is difficult for nurses to grasp) to the patient's assigned nurse, and to provide a patient interface that presents information tailored to the patient's condition.

[0023] The following sections will first describe an example configuration of the information processing system 10. Then, the system integration process will be explained. Finally, the details of the interface for presenting appropriate information to both nurses and patients will be described.

[0024] 2. Example System Configuration Figure 2 is a diagram illustrating an example configuration of an information processing system 10 including a bed system according to this embodiment. The information processing system 10 includes a bed 100, a bedside terminal device 200, a server system 300, an electronic medical record server 400, a station terminal device 500, and a terminal device 600 (portable terminal device). The bed system according to this embodiment includes at least a bed 100. The bed system may also include other components of the information processing system 10, such as a bedside terminal device 200 or an imaging device 700. Furthermore, the bedside terminal device 200 may be omitted from the configuration shown in Figure 2. For example, some or all of the processing performed by the bedside terminal device 200, as described below, may be performed by other devices such as the terminal device 600.

[0025] The information processing system 10 may also include an imaging device 700, a detection device 810, a measuring device 820, an authentication card 830, a television 910, a refrigerator 920, etc. However, the configuration of the information processing system 10 is not limited to the example in Figure 2, and various modifications can be made, such as omitting some components or adding other components. For example, the information processing system 10 may include a terminal device different from the station terminal device 500. The terminal device here may be, for example, a PC (Personal Computer) located within the hospital, or a PC located outside the hospital and connected to other devices of the information processing system 10 via a network. Some or all of the processing performed by the server system 300, which will be described below, may be performed on the said PC. The same applies to Figure 3, etc., which will be described later, in which modifications such as omitting or adding components are possible.

[0026] The bed 100 is bedding used by a patient. For example, a mattress 170 is placed on the bed 100, and the patient lies on the mattress 170. An imaging device 700 and a detection device 810 are provided near the bed 100. The imaging device 700 is a camera fixed to, for example, the frame of the bed 100, but it may also be fixed to the wall of the patient's room. The detection device 810 is a sheet-like or plate-like device provided between, for example, the bed 100 and the mattress 170.

[0027] The imaging device 700 outputs captured images using sensors such as a CCD (Charge-Coupled Device) image sensor or a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor. The captured images here may be moving images or still images. The imaging device 700 is installed near the bed 100 and, for example, captures images of a patient in a hospital room.

[0028] The detection device 810 is a device that senses information related to the patient's sleep. The detection device 810 includes a pressure sensor (e.g., a pneumatic sensor) that outputs a pressure value. When the user lies down, the detection device 810 detects the user's body vibrations (body movement, vibration) via the mattress 170. Based on the detected body vibrations, the detection device 810 obtains information related to respiratory rate, heart rate, activity level, posture, wakefulness / sleep, and getting out of bed / staying in bed. The detection device 810 may output sensor data representing body vibrations, and other devices such as the server system 300 may perform processing to obtain information such as respiratory rate based on this sensor data. The following describes an example in which the detection device 810 outputs information such as respiratory rate.

[0029] For example, the detection device 810 may analyze the periodicity of body movement and calculate the respiratory rate and heart rate from the peak frequency. The periodicity analysis may be performed 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 810 may also detect body vibrations per sampling unit time and output the number of detected body vibrations as the activity level. Furthermore, when the user gets out of bed, the detected pressure value decreases compared to when the user is in bed, so the detection device 810 may determine whether the user is in bed or out of bed based on the pressure value and its time-series changes. However, the method for determining whether the user is in bed or out of bed is not limited to this, and various modifications such as detecting vibrations can be implemented. The detection device 810 may also determine non-REM sleep and REM sleep, and determine the depth of sleep. The sleep-related determination may be performed based on the respiratory rate and heart rate, based on the amount of body movement (e.g., activity level), or using both.

[0030] The detection device 810 outputs biological information (such as respiration and heart rate) representing the patient's biological activity status, and sleep information (such as sleep / wake status, sleep depth, and whether the patient is out of bed or in bed) to the server system 300. The detection device 810 may output the sensing results to the server system 300 via the bedside terminal device 200, or it may output the sensing results to the server system 300 without going through the bedside terminal device 200.

[0031] A device equipped with a load sensor may be used as the bed 100. In this case, the bed 100 may output at least one of the patient's biological information and sleep information. The bed 100 may also output information representing changes in the patient's center of gravity and information representing their sleeping posture. Furthermore, the detection device 810 and the bed 100 with a load sensor may be used in combination.

[0032] The bedside terminal device 200 is a device that has a patient status notification function (notification function) and may be connected to the detection device 810 or to other devices included in the information processing system 10 via a network.

[0033] For example, the bedside terminal device 200 may include a display device and a connection device. The display device is, for example, a tablet-type display terminal that displays various information and accepts input for various operations. The connection device is a hub device for connecting the display device and the various devices. For example, the connection device may be connected to a detection device 810 to continuously acquire the patient's biometric information. The connection device may also receive biometric information from various measuring devices 820 (for example, a thermometer) or from a device worn by the patient (for example, a wristwatch-type wearable measuring device). The connection device may also perform authentication processing (for example, patient authentication or login processing for nurses, etc.) by reading an authentication card 830. The connection device may perform authentication processing using NFC (Near Field Communication), which is an example of short-range wireless communication, or it may perform authentication processing using other methods such as barcodes, infrared, or IC tags. For example, a user (nurse, doctor, care staff) can check the values ​​of biometric information and notification content by logging in, and can register that information in the electronic medical record as needed.

[0034] The network is connected to, for example, a server system 300, an electronic medical record server 400, a station terminal device 500, and a terminal device 600.

[0035] The server system 300 is a server that provides various services and may be connected to the LAN within the hospital or facility, or it may be located externally via the internet.

[0036] The server system 300 may consist of one server or may include multiple servers. For example, the server system 300 may include a database server and an application server. The database server stores various data such as biological information and sleep information. The application server performs processing described later using Figures 11 and 15. The multiple servers here may be physical servers or virtual servers. If virtual servers are used, the virtual servers may be located on a single physical server or distributed across multiple physical servers. For example, the server system 300 according to this embodiment may include a first server that processes location identification information and patient identification information to be associated with the bed 100, and a second server (nurse call server) that performs processing related to nurse calls described later using Figures 25A-25C. In this case, the first server and the second server may be physically different servers or the same server. As described above, the specific configuration of the server system 300 in this embodiment can be modified in various ways.

[0037] The electronic medical record server 400 is a server that stores electronic medical record information about patients. The electronic medical record server 400 is typically a server connected to a network within the hospital or facility, but it may also be an external cloud server, for example. Electronic medical records can contain various types of information. Electronic medical records, as shown in Figures 32A and 32B, include basic information, medical history, diagnostic information, medication information, test results, consultation information, treatment information, rehabilitation history, vaccination history, lifestyle information, family history, consent forms / signatures, insurance / medical information, medical team information, social background, mental health, emergency response plan, medical resource history, communication with family, infection control, risk assessment, physician's instructions, measurement results, response history, nurse call history, rehabilitation care history, transfer / referral letter history, therapeutic guidance history, patient complaint / chief complaint history, patient behavior information, blood glucose information, diet therapy information, water intake information, electrocardiogram information, pulse information, information on visits to multiple departments, inter-departmental coordination information, behavioral video recordings, video file storage information, physician / nurse responses based on videos, respiratory rate information, arterial blood oxygen saturation information, excretion information, room temperature / humidity information, etc. However, Figures 32A and 32B are specific examples of information included in electronic medical records, and various modifications are possible, such as omitting some information or adding other information. Further details of each piece of information are shown in Figures 32A and 32B, so a detailed explanation will be omitted.

[0038] The electronic medical record system of this embodiment may include other systems. Examples of other systems include nursing support systems, rehabilitation department systems, critical care department systems, and nutrition department systems.

[0039] The station terminal device 500 is a terminal device installed in the nurses' station or management room. By using the station terminal device 500, users such as nurses can check the status of the bedside terminal device 200 (i.e., the status of the patient corresponding to the bedside terminal device 200) from a location other than the patient's room.

[0040] The terminal device 600 is a portable device used by medical staff, such as doctors and nurses. The terminal device 600 for medical staff connects to a network (e.g., LAN) via a wireless connection. By using the terminal device 600, medical staff can check information from the bedside terminal device 200 from various locations within the hospital.

[0041] Furthermore, at least one of the station terminal device 500 and the terminal device 600 may perform a process to notify (inform) the nurse of the patient's condition. The notification process performed by the station terminal device 500 and / or the terminal device 600 may be initiated by the bedside terminal device 200 or by the server system 300.

[0042] Next, using Figures 3-6, we will explain an example of the configuration of each device included in the information processing system 10.

[0043] Figure 3 shows an example configuration of the bed 100. The bed 100 includes, for example, a processing unit 110, a storage unit 120, a communication unit 130, an operation unit 140, a drive unit 150, and a movable part 160. The bed 100 may also include load sensors and the like, which are not shown in Figure 3.

[0044] The processing unit 110 of this embodiment is composed of the following hardware. The hardware may include at least one of a circuit that processes digital signals and a circuit that processes analog signals. For example, the hardware may consist of one or more circuit devices or one or more circuit elements mounted on a circuit board. One or more circuit devices may be, for example, an IC (Integrated Circuit) or an FPGA (Field-Programmable Gate Array). One or more circuit elements may be, for example, a resistor or a capacitor.

[0045] Furthermore, the processing unit 110 may be implemented by the following processor. The bed 100 in this embodiment includes a memory for storing 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 a storage unit 120 or another type of memory. The processor includes hardware. Various types of processors can be used, such as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), or a DSP (Digital Signal Processor). The memory may be a semiconductor memory such as SRAM (Static Random Access Memory), DRAM (Dynamic Random Access Memory), or flash memory, or a register, or 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 instructions that can be read by the computer, and the functions of the processing unit 110 are realized as processing when the processor executes these instructions. The instructions here may be instructions from an instruction set that constitutes a program, or instructions that instruct the hardware circuit of the processor to operate.

[0046] The storage unit 120 is the work area of ​​the processing unit 110 and stores various information. The storage unit 120 can be implemented using various types of memory, and the memory may be semiconductor memory such as SRAM, DRAM, ROM (Read Only Memory), or flash memory, or it may be a register, a magnetic storage device, or an optical storage device. The storage unit 120 may also store drive programs, etc., for driving the drive unit 150, which will be described later.

[0047] The communication unit 130 is an interface for communication over a network, and when the bed 100 performs wireless communication, it includes, for example, an antenna, an RF (radio frequency) circuit, and a baseband circuit. However, the bed 100 may also perform wired communication, in which case the communication unit 130 may include a communication interface such as a USB connector or an Ethernet connector, and a control circuit for said communication interface. The communication unit 130 may operate according to the control of the processing unit 110, or it may include a communication control processor different from the processing unit 110.

[0048] The operating unit 140 is an operating interface for controlling the position and angle of the movable part 160. For example, the operating unit 140 may be an operating panel connected by wire or wirelessly to a control box where the processing unit 110 is located. The operating panel may include, for example, buttons for setting the driving direction and amount of the movable part 160.

[0049] The drive unit 150 is an actuator or the like that drives the movable part 160 of the bed 100. The bed 100 in this embodiment may be, for example, a nursing care bed in which the angle of the bottom, which is the surface on which the mattress is placed, can be adjusted. For example, the bed 100 has a plurality of bottoms divided into a plurality of members as the movable part 160, and the drive unit 150 adjusts the angle of the bottom by changing the position and orientation of at least a part of the plurality of bottoms based on the control of the processing unit 110. For example, the drive unit 150 may control the back angle (control of the bottom on the head side) or the foot angle (control of the bottom on the foot side).

[0050] The bed 100 may also be a bed with adjustable leg height. In this case, the drive unit 150 is an actuator or the like that drives the leg, which is the movable part 160. In this way, the height of the entire bed 100 can be adjusted by driving the drive unit 150.

[0051] As shown in Figure 3, the bed 100 may be connected to the imaging device 700 via the communication unit 130. The processing unit 110 may perform image processing such as object recognition on the captured image captured by the imaging device 700.

[0052] Figure 4 shows an example configuration of a bedside terminal device 200. The bedside terminal device 200 includes, for example, a processing unit 210, a storage unit 220, a communication unit 230, a display unit 240, an operation unit 250, a notification unit 260, and an interface unit 270. The bedside terminal device 200 may also include a display device and a connection device as described above. For example, the display device includes the display unit 240 in Figure 4, and the connection device includes the processing unit 210, storage unit 220, communication unit 230, operation unit 250, notification unit 260, and interface unit 270 in Figure 4. However, the configuration shown in Figure 4 can be provided in either the display device or the connection device at will, and it is not prohibited for them to be distributed and provided in both the display device and the connection device.

[0053] The processing unit 210 is comprised of hardware including at least one of a circuit for processing digital signals and a circuit for processing analog signals. The processing unit 210 may also be implemented by a processor. Various types of processors can be used, such as a CPU, GPU, or DSP. The functions of the processing unit 210 are realized as processing when the processor executes instructions stored in the memory of the bedside terminal device 200.

[0054] The storage unit 220 is the work area of ​​the processing unit 210 and is implemented by various types of memory such as SRAM, DRAM, and ROM. For example, the storage unit 220 stores biological information acquired from the detection device 810 and the measuring device 820.

[0055] The communication unit 230 is an interface for communication over a network and includes, for example, an antenna, an RF circuit, and a baseband circuit. The communication unit 230 communicates with the server system 300, for example, over a network. The communication unit 230 may perform wireless communication or wired communication, and the specific communication method is not limited.

[0056] The display unit 240 is an interface for displaying various information, and may be a liquid crystal display, an organic EL display, or another type of display. The operation unit 250 is an interface for receiving user input. The operation unit 250 may be a button or the like provided on the display device or connection device. Alternatively, the display unit 240 and the operation unit 250 may be a touch panel configured as an integrated unit.

[0057] The notification unit 260 may include a light-emitting unit, a vibration unit, a sound output unit, etc. The light-emitting unit is, for example, an LED (light-emitting diode) and provides notification by emitting light. The vibration unit is, for example, a motor and provides notification by vibration. The sound output unit is, for example, a speaker and provides notification by sound.

[0058] The interface unit 270 is the interface for connecting the measuring device 820 and reading the authentication card 830. The interface unit 270 is a port that accepts connections of connectors such as USB (Universal Serial Bus). However, the communication unit 230 may also function as the interface unit 270, as is the case when the authentication card 830 is read using NFC.

[0059] The bedside terminal device 200 may also be connected to equipment placed in the patient's room via the communication unit 230. For example, the bedside terminal device 200 may be connected to a television 910 and a refrigerator 920.

[0060] Figure 5 is a block diagram showing a detailed configuration example of the server system 300. The server system 300 includes, for example, a processing unit 310, a storage unit 320, and a communication unit 330.

[0061] The processing unit 310 is comprised of hardware including at least one of a circuit for processing digital signals and a circuit for processing analog signals. The processing unit 310 may also be implemented by a processor. Various types of processors can be used, such as a CPU, GPU, or DSP. The functions of the processing unit 310 are realized as processing when the processor executes instructions stored in the memory of the server system 300.

[0062] The memory unit 320 is the work area of ​​the processing unit 310 and is implemented by various types of memory such as SRAM, DRAM, and ROM.

[0063] The communication unit 330 is an interface for communication over a network, and when the server system 300 performs wireless communication, it includes, for example, an antenna, an RF circuit, and a baseband circuit. The specific communication method of the communication unit 330 can be implemented in various variations.

[0064] The electronic medical record server 400, like the server system 300, is a device that includes a processing unit, a storage unit, a communication unit, and the like. A detailed explanation of the configuration of the electronic medical record server 400 will be omitted.

[0065] Figure 6 is a block diagram showing a detailed configuration example of the terminal device 600. The terminal device 600 may include, for example, a processing unit 610, a storage unit 620, a communication unit 630, a display unit 640, and an operation unit 650.

[0066] The processing unit 610 is comprised of hardware including at least one of a circuit for processing digital signals and a circuit for processing analog signals. The processing unit 610 may also be implemented by a processor. Various types of processors can be used, such as a CPU, GPU, or DSP. The functions of the processing unit 610 are realized as processing when the processor executes instructions stored in the memory of the terminal device 600.

[0067] The memory unit 620 is the work area of ​​the processing unit 610 and is implemented by various types of memory such as SRAM, DRAM, and ROM.

[0068] The communication unit 630 is an interface for communication over a network and includes, for example, an antenna, an RF circuit, and a baseband circuit. The communication unit 630 communicates with the server system 300, for example, over a network. For example, the communication unit 630 may communicate with the server system 300 over a LAN and also communicate with the bed 100 and the bedside terminal device 200 using short-range wireless communication such as Bluetooth®. Various variations are possible for the specific communication method of the communication unit 630.

[0069] The display unit 640 is an interface for displaying various information, and may be a liquid crystal display, an organic EL display, or another type of display. The operation unit 650 is an interface for receiving user input. The operation unit 650 may be a button or the like provided on the terminal device 600. Alternatively, the display unit 640 and the operation unit 650 may be a touch panel configured as an integrated unit.

[0070] Furthermore, the terminal device 600 may include configurations not shown in Figure 6. For example, the terminal device 600 may have various sensors such as motion sensors like acceleration sensors and gyro sensors, pressure sensors, and GPS (Global Positioning System) sensors. The terminal device 600 may also include a light-emitting unit, a vibration unit, a sound input unit, a sound output unit, etc. The light-emitting unit is, for example, an LED, and provides notification by emitting light. The vibration unit is, for example, a motor, and provides notification by vibration. The sound input unit is, for example, a microphone. The sound output unit is, for example, a speaker, and provides notification by sound.

[0071] The station terminal device 500, like the terminal device 600, is a device that includes a processing unit, a storage unit, a communication unit, a display unit, an operation unit, etc. The terminal device 600 may be, for example, a smartphone or a tablet terminal, and the station terminal device 500 may be, for example, a PC. A detailed explanation of the configuration of the station terminal device 500 is omitted.

[0072] The bed system according to this embodiment is a bed system including a bed 100. The control unit of the bed system performs a process to acquire location identification information if neither location identification information representing the location of the bed 100 nor patient identification information representing the patient using the bed 100 has been acquired (hereinafter also referred to as the first mode). If location identification information has been acquired (hereinafter also referred to as the second mode), the control unit performs a process to acquire patient identification information. If patient identification information has been acquired (hereinafter also referred to as the third mode), the control unit performs a process to associate bed identification information, location identification information, and patient identification information that identify the bed 100. The storage unit of the bed system (for example, storage unit 120) stores the associated bed identification information, location identification information, and patient identification information. The control unit of the bed system may also output the associated information to devices other than the bed 100, such as a server system 300 or a bedside terminal device 200.

[0073] The control unit of the bed system corresponds to the processing unit 110 of the bed 100. However, the bed system may include other devices such as a bedside terminal device 200, and the control unit may be implemented by such other device (for example, the processing unit 210 of the bedside terminal device 200).

[0074] According to the method of this embodiment, it becomes possible to distinguish between a state in which the linkage of bed 100 has not been initiated (first mode), a state in which bed 100 and its placement location are associated (second mode), and a state in which bed 100 is associated with both its placement location and the patient using it (third mode). Furthermore, after appropriately linking bed 100, its location, and the patient, it becomes possible to output the resulting correspondence between bed 100, its location, and the patient to a device such as a server system 300. This makes it clear which hospital room bed 100 is located in and which patient is using it, so that, for example, information acquired around bed 100 can be appropriately associated with the patient, and appropriate information can be presented to nurses and patients based on this association. As a result, it becomes possible to appropriately present information that is difficult for nurses to grasp, such as physician's orders and patient's wishes. In this embodiment, a state in which bed 100 is associated with the patient using it but not with its placement location (fourth mode) may also be used. An example of using the fourth mode will be described later as a modification.

[0075] Furthermore, some or all of the processing performed by the bed system in this embodiment may be implemented by a program. The processing performed by the bed system refers, in a narrow sense, to the processing performed by the bed 100, but may also include processing performed by other devices such as the bedside terminal device 200.

[0076] The program according to this embodiment can be stored in a non-temporary information storage medium (information storage device), which is a medium readable by a computer. The information storage medium can be implemented as, for example, an optical disc, a memory card, an HDD, or a semiconductor memory. The semiconductor memory is, for example, a ROM. The processing unit 110, etc., performs various processing according to this embodiment based on the program stored in the information storage medium. That is, the information storage medium stores a program that causes the computer to function as the control unit of the bed system, etc. The computer is a device that includes an input device, a processing unit, a storage unit, and an output unit. Specifically, the program according to this embodiment is a program that causes the computer to execute each of the steps described later using Figure 8, etc.

[0077] Furthermore, the method of this embodiment can be applied to an information processing method that includes the following steps: If a bed system including a bed has not yet acquired either location identification information representing the location of the bed or patient identification information representing the patient using the bed, the information processing method includes acquiring location identification information; acquiring patient identification information when location identification information has been acquired; and associating bed identification information that identifies the bed, location identification information, and patient identification information when patient identification information has been acquired.

[0078] 3. System Integration Next, we will explain system integration. Specifically, we will describe the integration of beds, locations, and patients; the integration of sensing devices; and the integration of equipment. We will also explain the processes for maintaining and terminating these integrations.

[0079] 3.1 Bed, location, and patient coordination In hospitals and other medical facilities, when a patient using a particular bed (100) is discharged, that bed becomes vacant and is then used by a new patient. In other words, since the patient using bed 100 changes, it is necessary to associate bed 100 with the patient in the system integration.

[0080] Furthermore, changes in the patient's condition when using bed 100 may result in a change in the patient's hospital room. For example, a patient who was receiving treatment in the ICU (Intensive Care Unit) may be moved to a general ward after their condition improves. In this case, moving the patient along with bed 100 can reduce the burden of relocation for the patient. In other words, since bed 100 and the location in which it is used change, it is necessary to associate bed 100 with its location in system integration.

[0081] Therefore, the bed system performs processing to link the bed, location, and patient. Specifically, the control unit of the bed system (for example, the processing unit 110 of bed 100) may acquire the captured image taken by the imaging device 700. The control unit of the bed system causes the imaging device 700 to capture code information arranged in correspondence with the location, and acquires location identification information based on said code information. For example, the control unit acquires location identification information by analyzing the code information contained in the captured image. The control unit also acquires patient identification information by causing the imaging device 700 to capture an area including the patient's face. In this way, the bed 100, location, and patient can be linked using the imaging device 700.

[0082] Patent Document 1 discloses a method for determining the location of a bed using a communication module installed on the wall. However, the method in Patent Document 1 requires individual configuration of location data for each communication module, which may not be user-friendly. Depending on the scale of the system, configuration may need to be done by the system provider (vendor) rather than the system user (hospital staff), which would place a heavy burden on system construction. Furthermore, installing multiple communication modules on the wall could result in a large-scale device. In the case of multi-bed rooms, multiple beds may exist in one room, and the correspondence between location and bed may be unclear. In this respect, the method of this embodiment enables the linking of bed 100 and location using a simple means of code information. When reading code information, since it is not pairing via communication, it is possible to suppress the association of different beds even in multi-bed rooms. In addition, in the method of this embodiment, the imaging device 700 used for automatic location linking can also be used for patient communication.

[0083] For example, the bed system includes a bedside terminal device 200, which is a terminal device having a display unit 240 and is located near the bed 100. The display unit 240 of the bedside terminal device 200 may display code information. For example, the bedside terminal device 200 is pre-associated with a location, and even if the patient moves with the bed 100, the bedside terminal device 200 remains fixed in its associated location. In such a usage example, since the bedside terminal device 200 is uniquely associated with a location, the code information displayed on the display unit 240 of the bedside terminal device 200 can be used as information to uniquely identify the location. However, a display different from the display unit 240 of the bedside terminal device 200 may display the code information. Alternatively, as will be described later using Figure 30, static code information printed on a medium such as paper or cloth may be attached near the bed. Furthermore, various variations are possible in the form of the code information used to acquire location identification information.

[0084] Figure 7 illustrates an example of the situation around the bed 100 when the display unit 240 of the bedside terminal device 200 displays code information. For example, when a patient is lying on their side in bed 100, the display unit 240 of the bedside terminal device 200 may be provided on the head side of the patient, and the imaging device 700 may be provided on the leg side of the patient. The display unit 240 displays code information as described above. Although the explanation uses an example where imaging is done with the imaging device 700, it is not limited to this, and imaging may also be done with the camera of the bedside terminal device 200, for example.

[0085] In this case, for example, by orienting the optical axis of the imaging device 700 toward the patient's head, it becomes possible to include both the code information displayed on the display unit 240 and the face of the patient lying down in the field of view. Therefore, it becomes possible to perform code information interpretation processing and patient face recognition processing based on the captured image output by the imaging device 700. In this case, the first captured image capturing the code information and the second captured image capturing the patient's face may have the same field of view but be captured at different timings. For example, the first captured image may be captured when the bed 100 is placed in a predetermined position (and before the patient starts using it), and the second captured image may be captured after the patient starts using it. Note that the algorithms for code information interpretation processing and face recognition processing are different. Therefore, for example, when processing real-time camera images (moving images), the processing algorithm may be switched depending on whether the captured image is the first captured image or the second captured image. The identification of the captured image is determined, for example, depending on whether the bed 100 is in first mode or second mode. The order in which multiple processing algorithms operate may be predetermined, and for example, a code information interpretation processing algorithm may be operated in that order, and after interpretation, a face recognition processing algorithm may be operated. Alternatively, if the captured image is stored as a still image (an image of a given frame from a moving image), the first and second captured images may be stored separately, and then processing according to the corresponding algorithm may be performed.

[0086] However, the arrangement of the display unit 240 and the imaging device 700 is not limited to this. For example, the display unit 240 may be located on the patient's leg side and the imaging device 700 on the patient's head side. Also, if the imaging device 700 is configured to change the imaging direction, the position of the imaging device 700 can be flexibly changed. For example, the direction in which the display unit 240 is positioned relative to the imaging device 700 may differ from the direction in which the face of a patient lying on their side is positioned. In this case, the first and second images may differ not only in their imaging timing but also in their field of view.

[0087] Figure 8 is a sequence diagram illustrating the process of linking bed 100, its location, and the patient. Note that at the start of the process shown in Figure 8, bed 100 is not associated with either its location or the patient; that is, it is in the first mode.

[0088] When this process begins, in step S101, the display unit 240 of the bedside terminal device 200 displays code information representing the location where the bedside terminal device 200 is placed. That is, the code information here corresponds to location identification information. The code information may include the location identification information itself, or it may be link information to the location identification information. The location identification information may include, for example, a hospital ID that identifies the hospital, a ward ID that identifies the ward within the hospital, and a room ID that identifies the patient room within the ward. Furthermore, if the patient room is a multi-bed room shared by multiple patients, the location identification information may also include information that identifies the specific location within the patient room. The following describes an example where the code information is a QR code (registered trademark), but the code information in this embodiment is not limited to this.

[0089] In step S102, the power to bed 100 is turned on. For example, bed 100 is turned off when the patient using it moves, or when bed 100 is moved to another location, and the power is turned on again by the process in step S102.

[0090] In step S103, the processing unit 110 of the bed 100 performs a process to start the imaging device 700 via the communication unit 130. For example, as shown in Figure 7, the imaging device 700 is positioned near the bed 100 and is pre-configured to communicate with the communication unit 130.

[0091] The imaging device 700, activated by the bed 100, begins capturing images. For example, if the imaging device 700 includes a movable part that automatically adjusts the imaging range (optical axis, field of view), in step S104, the imaging device 700 operates the movable part so that it includes the QR code displayed in the processing of step S101. For example, the set value (angle, etc.) of the movable part capable of capturing a QR code is stored in the storage unit 120 of the bed 100, and in step S103, the processing unit 110 may instruct the imaging device 700 to operate according to the set value. In step S104, the imaging device 700 drives the movable part based on the instruction of the processing unit 110. If the imaging device 700 does not have a movable part, the processing of step S104 may be omitted. In this case, in step S103, the processing unit 110 may instruct the imaging device 700 to capture using a fixed field of view.

[0092] In step S105, the imaging device 700 acquires an image containing the QR code displayed on the display unit 240 of the bedside terminal device 200. In step S106, the imaging device 700 outputs the image to the bed 100.

[0093] In step S106, the processing unit 110 obtains location identification information corresponding to the QR code by performing a QR code interpretation process. Since the QR code interpretation process is a well-known method, a detailed explanation is omitted. The location identification information may be contained in the QR code itself. Alternatively, the QR code may contain link information to the location identification information, and the processing unit 110 may use this link information to obtain the location identification information.

[0094] When the bedside terminal device 200 is not connected to the bed 100 (when the bed 100 located nearby is in the first mode), it may display location identification information and code information corresponding to pairing information for connecting the bed 100 and the bedside terminal device 200 on the display unit 240. The first mode is a state in which neither the location nor the patient is linked to the bed 100, and as described above, the bed 100 is in the first mode at the start of Figure 8. For example, the code information displayed in step S101 may include not only location identification information but also pairing information. Similar to the location identification information, the code information may include the pairing information itself or may include link information for obtaining the pairing information.

[0095] For example, if a passcode is required to connect to the bedside terminal device 200, the pairing information may include that passcode. The pairing information may also include other information necessary for connecting the bed 100 and the bedside terminal device 200, and the specific information can be modified in various ways depending on the communication method. However, if a wired connection is made using a USB cable, LAN cable, etc., pairing information is not required to connect the bed 100 and the bedside terminal device 200, so the QR code does not need to include pairing information. Also, as will be described later as a modification using Figure 30, the QR code including location identification information may be a static QR code. In this case, since the QR code is provided independently of the bedside terminal device 200, there is a possibility that the QR code and the bedside terminal device 200 cannot be associated one-to-one. Therefore, when a static QR code is used, the QR code does not need to have pairing information for connecting to a specific bedside terminal device 200. Considering the above, the case in which the code information includes pairing information is when communication between the bed 100 and the bedside terminal device 200 is conducted wirelessly, and the bedside terminal device 200 displays a QR code.

[0096] In this way, by using code information (QR code) to associate the bed 100 with its location, it becomes possible to smoothly connect the bed 100 and the bedside terminal device 200. In this case, in step S107, the processing unit 110 obtains pairing information by interpreting the QR code.

[0097] In step S108, the processing unit 110 stores in the storage unit 120 the bed ID associated with the bed 100 and the location identification information obtained in step S107. For example, the storage unit 120 may update the table data.

[0098] Figure 9 shows an example of table data stored in the memory unit 120. As shown in Figure 9, the table data includes a bed ID that identifies the bed 100, location identification information that identifies its location, and patient identification information that identifies the patient. The table data may also include a bedside terminal ID and location identification information that identifies the location of the bedside terminal, which are not shown in Figure 9. The bed ID is set, for example, when the bed 100 is introduced to the hospital, and its value is stored in the memory unit 120. When the bed 100 is in the first mode, since neither the location nor the patient is linked, the location identification information and patient identification information are set to blank (or some initial value). The process in step S108 corresponds to writing the value obtained in step S108 into the location identification information column of the table data shown in Figure 9. This links the bed 100 with its location. In other words, the bed 100, which was in the first mode in steps S101-S107, transitions to the second mode through the process in step S108.

[0099] In step S109, the bed 100 establishes a connection with the bedside terminal device 200 using the pairing information acquired in step S107. Since the specific connection sequence is publicly known for each communication method, a detailed explanation is omitted.

[0100] When bed 100 transitions to the second mode, it performs processing to coordinate with the patient. If the imaging device 700 includes a movable part that automatically adjusts the imaging range, in step S110, the imaging device 700 operates the movable part so that the face of the patient lying on bed 100 is included in the imaging range. For example, the storage unit 120 of bed 100 stores a setting value (angle, etc.) for the movable part that allows imaging of an area where the patient's face is likely to be located when the patient lies on bed 100, and the processing unit 110 may instruct the imaging device 700 to operate according to this setting value, provided that it has transitioned to the second mode (not shown in Figure 8). In step S110, the imaging device 700 drives the movable part based on the instruction from the processing unit 110. If the imaging device 700 does not have a movable part, the processing in step S110 may be omitted. In this case, the processing unit 110 may instruct the imaging device 700 to perform imaging using a fixed field of view.

[0101] In step S111, the imaging device 700 acquires an image including the patient's face. In step S112, the imaging device 700 outputs the image to the bed 100.

[0102] In step S113, the processing unit 110 extracts the region corresponding to the patient's face from the captured image as a face image. For example, the processing unit 110 performs a process to crop the region of the captured image that is estimated to be the patient's face, using a skin-color region extraction process or a known object detection process. The patient identification information in this embodiment may be, for example, the patient's face image. Note that the processing in step S113 is not mandatory, and the entire captured image may be treated as the patient's face image.

[0103] In step S114, the processing unit 110 associates the bed ID associated with the bed 100 with the patient identification information (face image) acquired in step S113 and stores it in the storage unit 120. For example, the storage unit 120 may update the table data shown in Figure 9. The processing in step S114 corresponds to writing the value (face image) acquired in step S113 into the patient identification information column of the table data shown in Figure 9. This establishes a link between the bed 100 and the patient. Since the bed 100 and its location have already been linked by the processing shown in step S108, the bed 100, which was in the second mode in steps S109-S113, transitions to the third mode through the processing in step S114.

[0104] In step S115, the processing unit 110 outputs data associating the bed 100, its location, and the patient. For example, the processing unit 110 may send data including the bed ID, location identification information, and patient identification information updated in step S114 to the bedside terminal device 200. In this way, the bed 100, its location, and the patient are linked, and the results of this linkage can be used by various devices, including the bedside terminal device 200.

[0105] For example, the processing unit 210 of the bedside terminal device 200 may transmit the data received from the bed 100 to the server system 300 via the communication unit 230. The processing unit 310 of the server system 300 stores the received data in the storage unit 320. If the bed 100 is connected to a network, the bed 100 may transmit the above data to the server system 300 without going through the bedside terminal device 200.

[0106] Figure 10 shows an example of table data stored in the storage unit 320 of the server system 300. As shown in Figure 10, the storage unit 320 stores data that associates bed ID, location ID (location identification information), patient ID, instruction ID, purchase history ID, and device usage history ID. However, the items shown in Figure 10 are examples, and modifications such as omitting some items or adding other items are possible.

[0107] For example, the processing unit 310 obtains the bed ID, location identification information, and patient identification information directly from the bed 100 or via the bedside terminal device 200. The processing unit 310 then identifies the record corresponding to the obtained bed ID from the table data shown in Figure 10 and writes the location identification information obtained from the bed 100 as the location ID value of that record. Similarly, the processing unit 310 writes the patient identification information (face image) obtained from the bed 100 as the patient ID value of that record. Note that the patient ID and face image may be different pieces of information. In that case, the processing unit 310 may perform an authentication process to identify the patient ID from the face image and then write the identified patient ID and face image to the record. An example of the authentication process will be described later using Figure 11.

[0108] The table data in Figure 10 stored in the memory unit 320 may include, for example, records corresponding to each of the multiple beds 100 present in the hospital. In this way, it becomes possible to understand the location of each of the multiple beds 100 present in the hospital and which patient is using it. Furthermore, if a bed 100 is linked to a location but not to a patient (second mode), it can be determined that the bed 100 is vacant. In other words, it is possible to determine the vacancy rate at the hospital level or ward level based on the data shown in Figure 10. This information may also be shared between different hospitals. In this way, it becomes possible for hospitals to understand each other's vacancy rates, thus supporting hospital staff when they are looking for a hospital to transfer patients to.

[0109] In the data shown in Figure 10, the instruction ID is information that identifies the instruction given by the physician to the nurse regarding the patient in question. For example, the server system 300 according to this embodiment may store table data (a relational database in the narrow sense) representing the physician's instructions. This table data includes an instructioner ID that identifies the physician who gave the instructions, the content of the instructions, and agent information that identifies the person who received the instructions. The agent information may be the agent's attributes (department, team, working hours, etc.) or an ID that identifies a specific person. For example, the storage unit 320 of the server system 300 may store table data representing the physician's instructions for each patient. The instruction ID shown in Figure 10 is an ID that identifies one of the tables among multiple table data representing the physician's instructions. Information regarding the physician's instructions may be managed in the electronic medical record as physician instruction information shown in Figure 32B. In this case, the table data associated with the instruction ID shown in Figure 10 is included in the electronic medical record.

[0110] Furthermore, the server system 300 or electronic medical record server 400 according to this embodiment may store table data representing the purchase history for each patient. The purchase history ID shown in Figure 10 is an ID that identifies the table data representing the purchase history of the target patient. The table data identified by the purchase history ID includes information such as the purchase item ID that identifies the purchased item, payment status (paid / unpaid), and amount. The purchased item may be daily necessities, meals, or room upgrades, and details will be described later using Figures 29A, 29C, etc.

[0111] Furthermore, the server system 300 or electronic medical record server 400 according to this embodiment may store table data representing the usage history of devices for each patient. The device usage history ID shown in Figure 10 is an ID that identifies table data representing the usage history of sensing devices (detection device 810, measuring device 820, etc.) used for sensing the target patient. The table data identified by the device usage history ID includes the date representing the timing of use, the device ID that identifies the device, the acquired data, etc. The data included in the table data will be described later with reference to Figures 12-13.

[0112] Furthermore, in the method of this embodiment, a facial image of the patient may be acquired in advance when the patient is admitted to the hospital, and this facial image may be associated with a patient ID that identifies the patient and stored in the storage unit 320. Since this process is performed, for example, at the admission procedure stage, at this point the patient is not using the bed 100, and there is no link between the patient and the bed 100. Then, when the bed 100 and the patient's facial image are linked by the process described above using Figure 8, the processing unit 310 may perform patient authentication processing based on the facial image acquired at the time of admission.

[0113] Figure 11 is a sequence diagram illustrating the authentication process. The process shown in Figure 11 may be executed, for example, between steps S113 and S114 in Figure 8 (not shown in Figure 8), or after the process in S115 in Figure 8.

[0114] When the process shown in Figure 11 is disclosed, first in step S201, the processing unit 210 of the bedside terminal device 200 transmits the face image to the server system 300 via the communication unit 230. For example, in step S115, the processing unit 210 transmits the bed ID, location identification information, and face image obtained from the bed 100 to the server system 300.

[0115] In step S202, the processing unit 310 of the server system 300 performs a process to identify the patient ID of the patient corresponding to the facial image by comparing the facial image received in step S201 with master data (facial images acquired during hospital admission procedures) that has been previously stored in the storage unit 320. At this time, incidental information such as the patient's name may also be identified.

[0116] In step S203, the processing unit 310 performs a matching process based on the patient ID. The data subject to the matching process may be the data shown in Figure 10, or it may be an electronic medical record stored in the electronic medical record server 400. For example, as part of the matching process, the processing unit 310 may perform a process to determine whether or not the link between the identified patient and the bed 100 has been completed.

[0117] If the link between the identified patient and bed 100 has not been completed, it means that the patient has undergone admission procedures, but the bed 100 to be used has not yet been determined. In other words, it is considered acceptable to store the patient's ID in association with the bed ID in the table data shown in Figure 10. Therefore, in step S204, the processing unit 310 stores the patient ID (and the patient's facial image) in the table data of Figure 10, and sends a response to the bedside terminal device 200 indicating that the registration of the bed 100, location, and patient linkage results has been completed.

[0118] This confirms that processing using the results of the coordination between bed 100, location, and patient is permitted. Therefore, in step S205, the bedside terminal device 200 sends and receives data with the server system 300. Specifically, the bedside terminal device 200 performs processing to display code information for nurses to present data to nurses, and processing to display code information for patients to present data to patients. Details of these will be described later using Figures 17-19, etc.

[0119] On the other hand, if no matching face image exists in step S202, or if a face image exists but it is an image of a staff member such as a nurse, then it is inappropriate to link the face image to bed 100 because it does not represent an inpatient. Furthermore, even if the face image corresponds to a patient, if the patient corresponding to that face image is already linked to another bed 100, it is undesirable to link one patient to multiple beds 100. For example, a patient with dementia may mistakenly use a bed 100 other than their own, but by excluding patients who have already been linked to bed 100, it is possible to prevent such incorrect linking in such cases. In these cases, the processing unit 310 does not register the patient ID or the patient's face image in the table data of Figure 10. Then, in step S206, the processing unit 310 sends a response indicating patient registration failure to the bedside terminal device 200.

[0120] Although not shown in Figure 11, the bedside terminal device 200 may notify the bed 100 that patient registration has failed. Upon receiving this notification, the bed 100 deletes the patient's face image from the data shown in Figure 9 and transitions to the second mode. In this way, the process from step S110 onwards in Figure 8 is executed again, making it possible to attempt to connect with an appropriate patient.

[0121] 3.2 Sensing Devices If bed 100 has a communication module (communication unit 130), the sensing device such as the detection device 810 shown in Figure 1 may be directly connected to bed 100. In this case, the bed 100 and the sensing device will be linked. As described above, since bed 100 is linked to the location and the patient, the sensing data detected by the sensing device will be data that can be easily identified as being acquired at a specific location and for a specific patient.

[0122] Figure 12 is a sequence diagram illustrating the coordination process between the bed 100 and the sensing device. First, in step S301, the power to the sensing device is turned on. This causes the sensing device to start operating.

[0123] In step S302, the communication unit of the sensing device searches for devices whose radio wave strength is equal to or greater than a threshold. At this time, the sensing device may search for devices whose radio wave strength is equal to or greater than a threshold and whose device type is a bed 100. In step S303, the communication unit of the sensing device sends a connection request to the found devices. In this way, the sensing device can attempt to connect with beds 100 that are within a predetermined distance range.

[0124] In step S304, bed 100 sends a response to the sensing device authorizing the connection in response to the connection request. In step S305, the connection between bed 100 and the sensing device is established. After the connection is established, in step S306, the sensing device sends the detected sensing data to bed 100.

[0125] Figure 13 illustrates an example of data stored in the storage unit 120 of the bed 100. In particular, Figure 13 may be an example of data used for managing the sensing data transmitted in step S306.

[0126] As shown in Figure 13, the storage unit 120 of the bed 100 stores data that associates a device ID that identifies the sensing device, a date representing the timing when the sensing data was acquired, the specific sensing data, and the transmission status of the said sensing data. The transmission status here refers to information that identifies whether or not the corresponding sensing data has been transmitted to an external device. In this way, the bed 100 can store sensing data in association with the source sensing device, the acquisition timing, and the transmission status.

[0127] If the bed 100 and the bedside terminal device 200 are already linked (for example, if the process shown in Figure 8 has been completed), in step S307, the processing unit 110 may associate the sensing data with the bed ID and send it to the bedside terminal device 200. Specifically, the processing unit 110 associates the records included in the table data shown in Figure 13 whose transmission status is "not transmitted" with the bed ID and sends them. In step S308, the bedside terminal device 200 sends the data received from the bed 100 to the server system 300.

[0128] The processing unit 310 of the server system 300 performs a process to add the device usage history ID to the received record, for example, and then adds the device usage history ID to the table data described above using Figure 10. The processing unit 310 extracts the record corresponding to the bed ID received in step S308 from the table data using the bed ID as the search key, and writes the value of the device usage history ID that was assigned to the data obtained in step S308 to the device usage history ID field of the record. The processing unit 310 then stores the data obtained in step S308 in the storage unit 320 in association with the device usage history ID. For example, the storage unit 320 may store a device usage history table (not shown) that associates the device usage history ID, device ID, date, and sensing data.

[0129] Although the above example shows a connection between the bed 100 and the sensing device, the connection may also be made between the bedside terminal device 200 and the sensing device, as shown in Figure 1. As shown in step S115 of Figure 8, the bedside terminal device 200 obtains the bed ID of the bed 100 it is connected to, and is therefore able to associate the bed ID with the sensing data and transmit it to the server system 300.

[0130] The sensing device may also be connected to the terminal device 600. In this case, when measuring using the measuring device 820, the terminal device 600 may cooperate with the bedside terminal device 200 and obtain a bed ID from the bedside terminal device 200. The terminal device 600 may then associate the sensing data obtained from the sensing device with the bed ID and transmit it to the server system 300 via the bedside terminal device 200.

[0131] In this case, the linkage between the terminal device 600 and the bedside terminal device 200 may be performed using a user interface for nurses (hereinafter also referred to as UI), as described later using Figure 24, etc. This makes it easy to associate sensing data with the bed 100, its location, and the patient, thus enabling a user-friendly interface for managing sensing data related to the patient.

[0132] Furthermore, although the above example shows sensing data being transmitted to the server system 300 via the bedside terminal device 200, the bedside terminal device 200 may be omitted. For example, the bed 100 or terminal device 600 that acquired the sensing data may transmit the sensing data directly to the server system 300.

[0133] Furthermore, the imaging device 700 used in the process of linking the bed 100 with the patient's position may subsequently be used as a sensing device for monitoring the patient. Here, monitoring refers to functions such as fall detection and bed exit detection. Methods related to monitoring are described in U.S. Patent Application No. 18 / 133720, filed April 12, 2023, entitled "BED SYSTEM," U.S. Patent Application No. 17 / 324262, filed May 19, 2021, entitled "Remote watching system and remote watching application," and U.S. Patent Application No. 17 / 326612, filed May 21, 2021, entitled "Bed system." These patent applications are incorporated by reference in their entirety in this specification. In this case, the captured images output by the imaging device 700 may be managed as sensing data using data of the structure shown in Figure 13 or Figure 10.

[0134] 3.3 Coordination of equipment Furthermore, in the bed system according to this embodiment, the bedside terminal device 200 may be connected to an electronic device which is equipment installed near the bed 100. In this case, the control unit of the bed system (for example, the processing unit 110 of the bed 100) may, when the power of the electronic device is turned on while the bed 100 and the bedside terminal device 200 are linked, output electronic device identification information that identifies the electronic device in association with the bed identification information, location identification information, and patient identification information.

[0135] In this context, equipment (electronic devices) refers to, for example, a television 910 or refrigerator 920 placed in a patient's room and available for use by the patient. According to the method of this embodiment, it becomes easier to associate equipment with patients, making it possible to appropriately manage the patient's use of the equipment.

[0136] Figure 14 is a sequence diagram illustrating the equipment management process. As a prerequisite for this process, it is assumed that the bed 100 and the bedside terminal device 200 are already linked, as described above using Figure 8. Furthermore, since the equipment is not frequently replaced, it is assumed that the equipment and the bedside terminal device 200 are already linked.

[0137] In step S401, the equipment is powered on. In step S402, the equipment that has started operating notifies the connected bedside terminal device 200 that it has been powered on.

[0138] In step S403, the processing unit 210 of the bedside terminal device 200 processes a screen on the display unit 240 that provides instructions for using the equipment. This screen is for explaining to the patient how to use the equipment. Televisions 910 and refrigerators 920 installed in the patient's room may operate on the condition that the patient pays a fee. In this case, in step S403, the display unit 240 may display a screen that provides information such as the required fee, the usable time after inserting the prescribed fee, and the location of the payment slot. If payment is made by prepaid card, the display unit 240 may also display a screen that provides information such as how to purchase a prepaid card and the location of the prepaid card slot. The processing unit 210 of the bedside terminal device 200 displays the instructions screen and, if the patient selects prepaid card payment, may activate a card receiving device equipped with a prepaid card slot.

[0139] In step S404, the patient performs an operation to activate the equipment based on the instructions, and the equipment accepts the operation. If the activation operation is performed correctly, the equipment starts operating in step S405. For example, after step S405, the equipment notifies the bedside terminal device 200 that the activation is complete, along with electronic device identification information that identifies the equipment. The bedside terminal device 200 stores the electronic device identification information in association with the bed identification information, location identification information, and patient identification information acquired through the process described above, using Figure 8. By transmitting the bed identification information, location identification information, patient identification information, and electronic device identification information to the server system 300, the bedside terminal device 200 can properly perform coordination including the equipment.

[0140] Furthermore, payment for equipment may be made using electronic money. In particular, in this embodiment, code information (QR code) may be displayed as the patient UI, and the use of equipment may be made by payment using the QR code. Specific examples of payment using code information will be described later with reference to Figures 26-27, etc., along with details of the patient UI.

[0141] 3.4 Maintaining and Disconnecting Links When the linkage between the bed 100, its position, and the patient described above is performed using Figure 8, a process to check whether the linkage is maintained (polling) may be performed periodically. For example, when the linkage is complete, the bed 100 and the bedside terminal device 200 are connected (step S109 in Figure 8).

[0142] Therefore, the bedside terminal device 200 may periodically send connection confirmation requests to the bed 100. If the connection is maintained, the bed 100 will send a response to the request. If a response is received, the bedside terminal device 200 will determine that the connection is maintained.

[0143] Figure 15 is a sequence diagram illustrating the specific processing flow when there is no response. For example, consider the case where the power to bed 100 is turned off in step S501. In this case, in step S502, the bedside terminal device 200 sends the polling (request) described above to bed 100, but as shown in step S503, bed 100 does not return a response.

[0144] In this case, in step S504, the display unit 240 of the bedside terminal device 200 may display that the connection with the bed 100 has been disconnected. This makes it possible to inform nurses and other staff of the connection status between the bed 100 and the bedside terminal device 200. Note that in the process shown in Figure 15, when the connection is off, it is not immediately determined that the link has been disconnected; a confirmation process is performed.

[0145] Specifically, in step S505, the bedside terminal device 200 queries the server system 300 regarding the status of the bed 100. For example, the bedside terminal device 200 sends a query to the server system 300, along with a bed ID that identifies the bed 100, asking whether the bed 100 that was previously connected is now connected to another location.

[0146] In step S506, the server system 300 searches for a record with the corresponding bed ID from the data shown in Figure 10. In step S507, the server system 300 notifies the bedside terminal device 200 of the search results. For example, the server system 300 may send to the bedside terminal device 200 the result of determining whether the target bed 100 is registered at another location.

[0147] If bed 100 is registered at another location, the bedside terminal device 200 determines that the connection with bed 100 has been terminated. In this case, in step S508, the bedside terminal device 200 deletes the data associating the bed ID, location identification information, and patient identification information. This data is, for example, the data that the bedside terminal device 200 acquired from bed 100 through the process shown in step S115 of Figure 8 and stored in the storage unit 220. The bedside terminal device 200 may also notify the server system 300 that the connection has been terminated (not shown in Figure 15). Based on this notification, the server system 300 extracts the record with the bed ID corresponding to the bedside terminal device 200 from Figure 10 and performs a process to delete the location identification information and patient ID contained in that record. The processing unit 310 may also perform a process to back up existing data to another table (a table for saving data for which the connection has been terminated) from the viewpoint of saving acquired sensing data and the purchase history of the target patient.

[0148] Furthermore, if bed 100 and bedside terminal device 200 are linked, the display unit 240 of bedside terminal device 200 may display the bed ID of the linked bed 100 to indicate the linkage to the nurse. Therefore, if the linkage is terminated, in step S509, the display content of the display unit 240 may be changed so that it does not display the bed ID.

[0149] This makes it possible to appropriately maintain and disconnect the linked state of bed 100. For example, when cleaning a patient's room, the cable connecting bed 100 and bedside terminal 200 may be temporarily disconnected. In such cases, if the data held by the bedside terminal device 200 is deleted immediately after disconnecting the cable, nurses and other staff would have to re-register this data, which may not be user-friendly. As in this embodiment, if the bedside terminal device 200 retains the data until bed 100 is registered at another location, user-friendliness is improved. Note that Figure 15 illustrates an example in which the previous linked state is retained until bed 100 is connected to another bedside terminal device 200, but it is not limited to this. For example, if there is no response to step S503 for a predetermined period of time, a process to reset the linked state may be performed.

[0150] Furthermore, while the process of deleting data associated with bed ID, location identification information, and patient identification information stored in the storage unit 220 of the bedside terminal device 200 has been described (step S508), the data stored in the storage unit 120 of bed 100 (the data described above using Figure 9) is also updated as appropriate. For example, when the power to bed 100 is turned off, the storage unit 120 of bed 100 may perform a process to automatically delete the location identification information and patient identification information associated with bed ID (a process to reset the linkage). Note that since the bed ID is information assigned to bed 100, deletion is unnecessary.

[0151] 4. User Interface (UI) As described above, in the method of this embodiment, the bed 100, its location, and the patient are associated. As also mentioned above, the bed 100 may be linked with equipment such as a bedside terminal device 200, a sensing device, and other supplies. These linkages may be managed in the server system 300 using the data described above, for example, as shown in Figure 10.

[0152] The server system 300 according to this embodiment may present various types of information, for example, via a bedside terminal device 200. As described above, the bedside terminal device 200 is linked to the bed 100 and is therefore associated with the patient using the bed 100. The nurse in charge of the patient can also be identified based on the shift schedule, etc. Therefore, based on the above linkage, appropriate information can be presented to the desired patient or the desired nurse. Specifically, the display unit 240 of the bedside terminal device 200 may display code information (QR code), and the patient's terminal device or the nurse's terminal device 600 may read the code information to present the information. Note that the code information may be displayed using a display other than the display unit 240. A specific example of the UI will be described below. Note that the code information for presenting information to patients, etc., is not limited to what is displayed on the display unit 240 or a display, but static code information printed on paper, etc., may also be used. An example of using static code information will be described later as a modification.

[0153] 4.1 Code Information Figure 16 is a diagram illustrating the transition of code information displayed on the display unit 240. The display unit 240 shown in the lower left of Figure 16 indicates a state in which the bedside terminal device 200 is not connected to the bed 100. As described above, in this embodiment, the bedside terminal device 200 is arranged in a predetermined position. In other words, this state corresponds to states such as the bed 100 not being at that position, the bed 100 being present but not powered on, or the bed 100 being powered on but the pairing process not being completed.

[0154] In this case, the display unit 240 displays code information (hereinafter referred to as QR code A) which includes at least location identification information. QR code A is the code information displayed by the display unit 240 in the process shown in step S101 of Figure 8. In other words, QR code A is the code information used for linking the bed 100 with its location. QR code A may also include pairing information used for pairing the bed 100 with the bedside terminal device 200, as described above.

[0155] As described above using Figure 8, the bed 100 acquires position identification information and pairing information based on the image captured by the imaging device 700 and connects with the bedside terminal device 200 (steps S107-S109). As a result, the bed 100 transitions from a first mode in which it is not linked to either the position or the patient, to a second mode in which it is linked to the position but not to the patient.

[0156] As shown in the lower center of Figure 16, when bed 100 transitions to the second mode (a state in which location identification information has been acquired but patient identification information has not been acquired), the display unit 240 displays code information different from QR code A (hereinafter referred to as QR code B). For example, when the connected bed 100 is in the second mode, the bedside terminal device 200 may display code information corresponding to the screen prompting the acquisition of patient identification information as QR code B on the display unit 240. In this way, the code information displayed on the bedside terminal device 200 can be used to smoothly transition bed 100 to the third mode.

[0157] For example, QR code B contains information about a bed ID that identifies a bed 100 that has been linked to the bedside terminal device 200. QR code B also contains information indicating that the linked bed 100 is awaiting patient registration, in other words, that the bed 100 is vacant. This allows us to indicate which beds 100 are vacant and require patient registration. For example, QR code B may also be code information for displaying information for nurses or administrators. When a nurse reads QR code B using the terminal device 600, the display unit 640 of the terminal device 600 displays the above information.

[0158] Furthermore, QR code B includes information such as the hospital name, ward name, room number, and bed number within the room, along with text indicating that bed 100 is vacant. The display unit 640 of the terminal device 600, which reads QR code B, displays this information. The hospital name and other information may also be displayed on the display unit 240 of the bedside terminal device 200 in association with QR code B (for example, alongside QR code B). Alternatively, to facilitate the patient interaction process shown in Figure 8, the display unit 640 may display text or pictograms prompting the patient to lie down on bed 100. In this way, the QR code B displayed on the bedside terminal device 200 can be used to support the acquisition of facial images by the imaging device 700.

[0159] The imaging device 700 captures an image of the patient's face, thereby establishing coordination between the bed 100 and the patient (steps S110-S115 in Figure 8). As a result, the bed 100 transitions to a third mode in which it is coordinated with both its position and the patient.

[0160] As shown in the lower right of Figure 16, when the bed 100 transitions to the third mode, the display unit 240 displays code information (hereinafter referred to as QR code C) that is different from both QR code A and QR code B. Note that in Figure 16, for convenience, the same code is shown as QR code A to QR code C, but these code information are different in their code patterns (the arrangement patterns of black and white).

[0161] QR code C is not limited to a single piece of code information, but may include multiple pieces of code information that change depending on the situation. For example, when the bedside terminal device 200 is connected to the bed 100 and the bed 100 is in third mode (a state in which location identification information and patient identification information have been acquired), the display unit 240 displays at least one of the following: first code information (hereinafter also referred to as QR code C1), which is code information corresponding to the nurse's screen for the nurse in charge of the patient, and second code information (hereinafter also referred to as QR code C2), which is code information corresponding to the patient's screen for the patient.

[0162] QR code C1 for nurses includes information such as changes in physician's orders or changes in the patient's condition. QR code C2 for patients includes information for making calls to summon nurses and other staff, as well as information for payment related to the use of supplies and the purchase of daily necessities.

[0163] Figure 17 shows an example of a display screen that shows a QR code C2 for patients. For example, when displaying the QR code C2, the display unit 240 may display a patient-specific screen with relatively less information. In the example in Figure 17, the display unit 240 displays the QR code C2 and text indicating that the QR code C2 is patient-specific code information. Since patients are not medical professionals, they have little need to view detailed information, and depending on their medical condition, there is information that should not be disclosed to patients. Therefore, the display unit 240 may display information that is easy for patients to understand or information that is safe for patients to view, along with the QR code C2. For example, in addition to the information shown in Figure 17, the display unit 240 may also display the patient's name, room number, etc.

[0164] Figure 18 shows an example of a display screen that shows QR code C1 for nurses. The screen that displays QR code C1 may be a screen that contains a relatively larger amount of patient information than the screen that displays QR code C2 for patients (hereinafter also referred to as the patient screen). For example, as shown in Figure 18, the display unit 240 may display a patient screen that includes the patient's name, pictograms, etc.

[0165] The pictograms used here represent information about the patient's condition. For example, a patient with the designation AAAA, whose mode of transportation is walking, will have a patient screen that includes a pictogram representing walking. Similarly, the patient screen will include pictograms corresponding to the patient being allowed to move freely within their room (free movement within the room), being allowed to drink beverages, and being prohibited from eating or drinking at night. By using pictograms, the patient's condition can be presented to nurses and other staff in an easy-to-understand manner. For example, displaying a pictogram indicating a patient's recent fall can help prevent accidentally taking an injured patient to rehabilitation.

[0166] Furthermore, patients with a rating of AAAA are associated with factors requiring special attention, such as needing blood glucose monitoring, wearing hearing aids in both ears, going out or staying overnight elsewhere, being prohibited from consuming alcohol, and being prescribed medication to be taken before meals. The patient screen may include text that represents these details, for example. The patient screen may also include information such as the attending physician, assigned nurse, admission date, expected discharge date, and medical department.

[0167] Furthermore, as shown in Figure 18, if it is desired to present information to a specific nurse (Nurse A) among the multiple nurses responsible for a patient named AAAA, the display unit 240 may display the nurse's name, etc., associated with QR code C2. In the example in Figure 18, the patient screen includes text near QR code C2 that identifies the target nurse, such as "To Nurse A," and text that prompts the reader to scan the code, such as "Please scan the QR code."

[0168] As described above, the bedside terminal device 200 may display different code information on the display unit 240 in each of the following states: when it is not connected to the bed 100, when it is connected to the bed 100 and the bed 100 is in second mode (a state in which location identification information has been acquired but patient identification information has not been acquired), and when it is connected to the bed 100 and the bed 100 is in third mode (a state in which location identification information and patient identification information have been acquired). In this way, it becomes possible to present information that matches the coordination status of the bed 100. For example, a nurse who reads QR codes A to C using the terminal device 600 can understand the status of the bed system. The display unit 240 may also display text, etc., indicating the location of the bed 100 and the coordination status with the patient, in association with the QR codes.

[0169] Figure 19 is a sequence diagram illustrating the transition of code information displayed on the display unit 240. First, in step S601, the display unit 240 displays a QR code A that includes location identification information and pairing information.

[0170] In step S602, the imaging device 700 captures QR code A. In step S603, the imaging device 700 transmits the captured image to the bed 100. In step S604, the processing unit 110 of the bed 100 obtains location identification information and pairing information by interpreting QR code A. In S605, the storage unit 120 stores the bed ID and location identification information in association. In step S606, the bed 100 and the bedside terminal device 200 are paired. The processes in steps S602-S606 correspond to the processes in steps S105-S109 in Figure 8.

[0171] Triggered by the completion of pairing with bed 100, in step S607, the display unit 240 displays QR code B, which is different from QR code A. As described above, QR code B may include information to facilitate communication with the patient.

[0172] In step S608, the imaging device 700 captures an image of the patient's face. In step S609, the imaging device 700 transmits the patient's face image to the bed 100. In step S610, the storage unit 120 stores the bed ID and patient identification information in association. In step S611, the bed 100 notifies the bedside terminal device 200 that communication with the patient is complete (it has moved to the third mode). The processing in steps S608-S611 corresponds to the processing in steps S111-S115 in Figure 8.

[0173] When the display unit 240 receives notification that bed 100 has transitioned to the third mode, in step S612, it displays QR code C2 for the patient as QR code C. For example, in a state where no care is being provided by a nurse (default state), the display unit 240 may display QR code C2.

[0174] When a nurse provides care to a patient, for example in step S613, the terminal device 600 accepts the operation to activate the application and the operation to select the patient to be cared for. The application here is, for example, a medical application used by doctors, nurses, administrative staff, etc., within the hospital. Then, in step S614, as the nurse moves, the terminal device 600 moves closer to the patient to be cared for.

[0175] If the distance to the bedside terminal device 200 falls below a predetermined level, in step S615, the terminal device 600 sends a notification to the bedside terminal device 200. This notification may be sent using Bluetooth, NFC, or another method. For example, the processing unit 610 of the terminal device 600 may send a notification to the bedside terminal device 200 if it has received a selection operation for a predetermined patient and the distance to the bedside terminal device 200 that is linked to the selected patient is below a predetermined level. In this way, it becomes possible to accurately determine whether or not patient care will be performed by a nurse. In step S615, a login process to the bedside terminal device 200 using the nurse's ID may be performed (automatic login).

[0176] When the notification in step S615 is received, the bedside terminal device 200 can determine that a nurse has moved to the vicinity to provide patient care. Therefore, in step S616, the display unit 240 displays QR code C1 for the nurse as QR code C. In this way, it becomes possible to switch between the patient screen and the nurse screen under appropriate conditions.

[0177] The above description concerns the transitions from the lower left to the lower right of Figure 16 (the transition of bed 100 from the first mode to the second mode, and from the second mode to the third mode). However, the mode transitions in this embodiment are not limited to these, and a transition from the third mode to the first mode may also occur, as shown in the transition from the lower right to the lower left of Figure 16. For example, if the pairing between bed 100 and bedside terminal device 200 is dissolved by the process described above using Figure 15, bedside terminal device 200 returns to a state where it is not connected to bed 100 (step S508). Therefore, the display unit 240 returns to a state where it displays a QR code A containing location identification information and pairing information.

[0178] 4.2 Nurse UI Next, we will explain the UI for nurses using QR code C1. The QR code C1 for nurses (first code information) is information that, when read by the first terminal device (terminal device 600) used by the nurse, displays patient information corresponding to patient identification information on the display unit (display unit 640) of the first terminal device. In this way, it becomes possible to appropriately allow a specific nurse (in the narrow sense, the nurse in charge of that patient) to view information about a specific patient. Nurses can refer to the electronic medical record on the electronic medical record server 400 using the display unit 240 of the bedside terminal device 200, but by reading the QR code using terminal device 600, there is the advantage that the operation of the bedside terminal device 200 (in the narrow sense, the login operation) can be omitted. Furthermore, QR code C1 may also be code information for extracting and displaying some information of relatively high importance from the data contained in the electronic medical record, or code information for displaying information that is not desirable for the patient to view. In this case, nurses can use the bedside terminal device 200 and terminal device 600 depending on the content of the information they want to view.

[0179] For example, as mentioned above, one type of information that is difficult for nurses to grasp is instructions from doctors. Since doctors' instructions are expected to be registered in electronic medical records, nurses can check these instructions using bedside terminal devices 200, etc., if they have the time. However, checking detailed information for all assigned patients would place a heavy burden on nurses and is therefore not easy.

[0180] Therefore, the bed system of this embodiment may use a QR code C1 for nurses to present information related to the doctor's instructions to the nurses. According to the method of this embodiment, it becomes possible to appropriately present information that nurses may find difficult to grasp.

[0181] In this case, the nurse can confirm the latest instructions from the doctor at that time during the handover. Therefore, the display unit 240 of the bedside terminal device 200 according to this embodiment may display an object representing the update in association with the first code information when the instruction information representing instructions from other staff to the nurse regarding the patient corresponding to the patient identification information has been updated.

[0182] This approach clearly indicates that the displayed QR code C1 likely contains information that the nurse is unaware of. Therefore, it helps prevent nurses from missing instructions. Conversely, if no object indicating an update is displayed, the nurse can assume that the doctor's instructions have not changed since the handover. Consequently, if there are other higher-priority tasks, the nurse can be instructed to skip scanning QR code C1.

[0183] Figure 20 is a sequence diagram illustrating the process of displaying QR code C1. First, in step S701, the physician's terminal device 600 receives an input from the physician for instructions to the nurse and transmits the received content to the server system 300. These instructions include information that identifies the patient in question.

[0184] In step S702, the server system 300 adds the received instructions to the electronic medical record stored in the electronic medical record server 400. Specifically, the processing unit 310 identifies the patient related to the instructions based on the information received in step S701 and performs the process of adding the instructions to the electronic medical record of that patient.

[0185] In step S703, the server system 300 sends a QR code update instruction to the bedside terminal device 200 associated with the patient related to the instruction. The QR code here is QR code C, specifically QR code C1 for nurses.

[0186] In step S704, the display unit 240 of the bedside terminal device 200 displays the updated QR code C1 in association with the object representing the update. As described above, the processing in steps S703 and S704 may be performed only if the instruction update occurs after the latest handover.

[0187] Figure 21 shows an example of a QR code C1 associated with an object representing an update. The object and QR code C1 shown in Figure 21 are displayed on a patient screen that displays patient information, for example, similar to Figure 18.

[0188] As shown in Figure 21, the object representing the update is, for example, a circular object of a predetermined color. However, other objects may be used as long as they are objects that the nurse can understand to represent an update. Also, as shown in Figure 21, QR code C1 may include information indicating when the instruction was updated (in this case, the date and time). In this way, it becomes possible to make the nurse understand that the doctor's instruction has been updated and the timing of that update before reading QR code C1. Therefore, by comparing the timing of the handover with the timing of the update, the nurse can determine whether the change in the instruction is information they are already aware of or new information.

[0189] Although not shown in Figure 21, the bedside terminal device 200 may also display summary information representing an overview of the instruction information in association with the first code information (QR code C1). Furthermore, when the first code information is read by the nurse's terminal device 600 (first terminal device), the display unit 640 of the terminal device 600 may display detailed information relating to the instruction information, which contains more information than the summary information.

[0190] The summary information here represents the category of the instruction, such as "dietary restriction instructions" or "carbohydrate restriction instructions." The detailed information specifies the nurse's actions, such as "work with a nutritionist to limit calorie intake to 1800 kcal per day" or "adjust insulin units in insulin therapy according to the time of day." The summary information may also represent multiple timings at which the instruction information was updated (time-series information of update timings), and the detailed information may represent the specific content of the updates at those multiple timings. "Multiple timings" here may include a predetermined number of update timings from the most recent update timing, or it may include update timings where the time difference from the current time is less than or equal to a predetermined threshold. Furthermore, the summary information may represent the content of the instruction at the most recent timing, and the detailed information may be time-series information (information representing the update history) that includes the content of the instruction at update timings prior to that most recent timing.

[0191] In this way, nurses can grasp the gist of the doctor's instructions before reading the QR code C1 using the terminal device 600. Therefore, nurses can decide whether to read the QR code C1 to check the detailed information or whether it is unnecessary to check the detailed information because the instructions are already known. Furthermore, since the detailed information of the instructions is not displayed on the display unit 240 of the bedside terminal device 200, it is possible to suppress the display of information that is undesirable to show to patients or their families in a manner that allows patients to view it. Also, from the perspective of not showing unnecessary information to patients, the nurse's terminal device 600 may be a wearable device such as AR (Augmented Reality) glasses. When the imaging unit of the wearable device reads the QR code C1, the detailed information may be displayed on the display of the wearable device.

[0192] As mentioned above, when a patient is receiving treatment in a medical department other than the nurse's department, instructions from a physician in a different department become particularly difficult for the nurse to grasp. Therefore, the display unit 240 may display information about the medical department to which the physician who issued the instructions belongs as summary information.

[0193] Figure 22 is a diagram illustrating the operation of the information processing system 10. Note that the explanation of how the QR code displayed on the display unit 240 changes between QR code A and QR code C depending on the situation is the same as in Figure 16, so a detailed explanation is omitted. As mentioned above, QR code C1 for nurses is displayed when bed 100 is in the third mode.

[0194] For example, a staff member such as a doctor registers a change in instructions to the server system 300 using a terminal device 600 (corresponding to "Request to other staff" shown in Figure 22). For example, the doctor's terminal device 600 sends the patient ID of the target patient and information indicating the specific instructions to the server system 300. Based on the received information, the server system 300 sends information to the bedside terminal device 200 associated with the patient ID to reflect the instructions in the QR code C1. For example, the server system 300 may send the updated QR code C1 itself. Alternatively, the server system 300 may send information indicating the content of the instructions to the bedside terminal device 200, and the bedside terminal device 200 may generate the QR code C1 (corresponding to "Reflecting request content in QR" shown in Figure 22). The display unit 240 of the bedside terminal device 200 displays the updated QR code C1, an object indicating the update, and summary information.

[0195] When a nurse or caregiver assigned to a patient reads the updated QR code C1 using the terminal device 600, instructions from the doctor or other medical professional are presented to the nurse or caregiver (corresponding to "Understanding requests from other staff" shown in Figure 22). In this way, instructions given among medical staff can be presented to the appropriate staff member in an easily understandable manner.

[0196] Furthermore, the QR code C1 for nurses may also contain information used to manage sensing data from sensing devices that use the terminal device 600 as a hub. For example, the measuring device 820 includes a device carried by the nurse. These measuring devices 820 may have communication capabilities and may be pre-connected to the nurse's terminal device 600. In this way, when a nurse performs a measurement using the measuring device 820, the sensing data is stored in the terminal device 600. However, since the measuring device 820 carried by the nurse will be used at different locations within the hospital and for different patients, it is necessary to associate the sensing data with where and for which patient it was acquired. The QR code C1 may include at least one piece of information: bed ID, location identification information, and patient identification information. Since the association of bed 100, location, and patient has been completed by the process described above using Figure 8, the association of sensing data with location and patient is possible with any one of these pieces of information. The QR code C1 may also include two or more of these pieces of information.

[0197] Figure 23 is a sequence diagram illustrating the process of associating necessary information with sensing data. As mentioned above, it is assumed that the terminal device 600 and the sensing device (e.g., measuring device 820) are already linked.

[0198] First, in step S801, the display unit 240 of the bedside terminal device 200 displays a QR code. The QR code here is a QR code C corresponding to the third mode, as explained using Figures 16 and 19, and is a QR code C1 for nurses. In this case, the QR code C1 includes the bed ID, location identification information, patient identification information, etc., as described above.

[0199] In step S802, the terminal device 600 reads the QR code C1. In step S803, the processing unit 610 interprets the QR code C1 to obtain the bed ID, location identification information, and patient identification information.

[0200] In step S804, the sensing device performs measurement processing based on the nurse's operation and outputs the sensing data to the terminal device 600.

[0201] In step S805, the terminal device 600 associates the acquired sensing data with the data (e.g., bed ID) acquired through the interpretation process in step S804 and transmits it to the server system 300.

[0202] Figure 24 illustrates the operation of the information processing system 10 in this case. Note that the explanation of how the QR code displayed on the display unit 240 changes between QR code A and QR code C depending on the situation is the same as in Figure 16, so a detailed explanation is omitted. As described above, QR code C1 for nurses is displayed when bed 100 is in third mode. By reading this QR code, information such as the patient ID is transmitted to the terminal device 600. As a result, the sensing data measured by the sensing device and stored in the terminal device 600 is transmitted to the server system 300, linked to the patient ID, etc. This makes it easy to associate sensing data with patients and their locations.

[0203] Furthermore, in the method of this embodiment, the processing unit 610 of the terminal device 600 may perform a determination based on sensing data, for example, a determination of whether an abnormality has occurred in the patient. In this case, the measured value of the sensing data that serves as the criterion for the determination (for example, a determination threshold for whether or not there is an abnormality) may be variable according to the patient's attributes, etc. In this case, the QR code C1 for the nurse may contain information including the value of the measured value (corresponding to "Reflecting the set value of the measured value in the QR code" in Figure 24). In this way, the criteria for determination based on sensing data can be flexibly changed for each patient, and such changes can be easily implemented using a QR code.

[0204] Figure 23 illustrates the process of acquiring sensing data after reading QR code C1, but it is not limited to this. For example, measurements using a sensing device may be performed first, and then QR code C1 may be read by the terminal device 600 when the nurse uploads the data. In this case, reading the QR code triggers the upload of the stored sensing data (Figure 24).

[0205] 4.3 Patient UI Next, we will explain the patient UI using QR code C2. QR code C2 may be used as an interface for patient calls to summon nurses, payments for the use of equipment and purchase of daily necessities, and patient guidance. Each of these will be explained below.

[0206] <Call> The QR code C2 (second code information) may be information that, when read by a second terminal device used by the patient, displays a screen on the display unit of the second terminal device used by the patient to express their wishes. In this way, it is possible to realize an interface that makes it easier for patients to express their wishes compared to conventional nurse call systems that use physical buttons. In this case, the QR code C2 may include at least one piece of information: bed ID, location identification information, and patient identification information. The second terminal device then outputs the result of the operation representing the patient's expression of wishes, associating it with at least one piece of information: bed ID, location identification information, and patient identification information. In this way, it is possible to appropriately identify the patient who performed the operation representing their wishes. Furthermore, it becomes possible to notify nurses and other staff of the patient's wishes using a device that the patient is familiar with. For example, the patient's terminal device transmits information to the server system 300 or terminal device 600 via the bedside terminal device 200.

[0207] Figure 25A shows an example of a screen displayed by the display unit of a terminal device that reads QR code C2. The screen shown in Figure 25A includes information that identifies the patient (e.g., name), along with operation objects corresponding to the patient's requirements, such as "Contact Nurse," "Order Meal," and "Go Shopping." If "Contact Nurse" is selected, a process to call medical staff is executed. If "Order Meal" is selected, a specific menu is displayed, and if a specific menu is selected, a process to order food from the cafeteria is executed. If "Go Shopping" is selected, a product list is displayed, and if a specific product is selected, a process to order from the purchasing department is executed. In addition, if "Order Meal" or "Go Shopping" is selected, a process to call the cafeteria or purchasing department (call process) is executed, and the patient may place an order verbally. This makes the patient's intention clearer compared to simply pressing a button to call a nurse, making it easier for nurses and other staff to respond.

[0208] In this case, the display unit 240 of the bedside terminal device 200 may change the information contained in the QR code C2 depending on the room the patient is hospitalized in and the patient's condition. For example, the processing unit 310 of the server system 300 determines the information contained in the QR code C2, and the display unit 240 displays the QR code C2 determined by the processing unit 310.

[0209] For example, the screen shown in Figure 25A is a web page written using a markup language such as HTML, and the QR code C2 may include link information (URL: Uniform Resource Locator) to that web page. The processing unit 310 may change the destination URL depending on the patient. For example, the processing unit 310 changes the URL included in the QR code C2 based on the electronic medical record stored in the electronic medical record server 400. For example, if the target is a patient who has been instructed to restrict their diet, the processing unit 310 does not need to display the "Meal Order" item. Alternatively, the processing unit 310 may display "Meal Order" but restrict the available menu items more than usual. In addition, various variations can be implemented to modify the display screen according to the patient.

[0210] Furthermore, QR code C2 (second code information) may also be information that causes the display unit of the terminal device used by the patient (second terminal device) to display a screen containing a first display object for the patient to contact a nurse and a second display object for the patient to contact staff other than nurses.

[0211] Figure 25B shows an example of a screen that appears when the user selects "Contact Nurse" in Figure 25A. For example, the screen shown in Figure 25B includes options for "Life Support," "Medical Requests," and "Emergency." "Life Support" refers to tasks that can be performed by caregivers, such as requests for water and food, assistance with toileting, assistance with changing positions, operation of the TV and air conditioner, answering visitors, handing over remote controls and telephones, and adjusting the bed position. "Medical Requests" refers to tasks that can be performed by nurses, such as complaints of pain or discomfort, requests regarding medication, and feeling unwell. "Emergency" refers to tasks that require immediate attention, such as falls, injuries, and acute health problems.

[0212] In this case, when a button selection operation is performed in Figure 25B, information representing the result of the operation is sent to the server system 300, and the processing unit 310 performs a process to determine the notification destination based on the selected item. In the above example, the processing unit 310 notifies the caregiver's terminal device 600 of calls in which "Life Support" is selected, and notifies the nurse's terminal device 600 of calls in which "Medical Request" and "Emergency." Note that the consultation content (button) and the notification destination are not limited to being uniquely associated, and the processing unit 310 may perform a process to estimate the notification destination each time using a trained model or the like.

[0213] In this way, when a patient wants to directly contact (call) a staff member, not all calls are notified to nurses, but can be routed to the appropriate staff member according to the patient's wishes. As a result, each staff member can reduce the frequency of responding to calls outside their area of ​​expertise, thus reducing their workload. In other words, the patient's wishes, which were difficult to grasp with the method of this embodiment, can be clarified by providing an appropriate interface. As described above using Figure 25A, buttons such as "Order a meal" or "Go shopping" may be included in the second display object for contacting staff other than nurses.

[0214] As mentioned above, the "Life Support" and "Medical Requests" shown in Figure 25B each contain multiple requests, but a screen that allows for the selection of more specific requests may also be used. Figure 25C shows an example of another screen that appears when the operation "Contact Nurse" is selected in Figure 25A. For example, the screen shown in Figure 25C may include buttons such as "I need to go to the toilet," "My IV drip is finished," and "I want something to drink." In this way, the patient's wishes can be presented to nurses and caregivers in a more easily understandable manner. As in the example above, the terminal device contacts a caregiver if "I need to go to the toilet" or "I want something to drink" is selected, and contacts a nurse if "My IV drip is finished" is selected. Alternatively, the patient's terminal device may display a screen that allows the selection of specific requests such as "I need to go to the toilet," "My IV drip is finished," or "I want something to drink" when the patient's QR code C2 is scanned. Specifically, the patient's terminal device may display buttons indicating specific requests such as "I need to go to the toilet" instead of the "Contact Nurse" button on the screen shown in Figure 25A. Alternatively, the patient's terminal device may display the screens shown in Figures 25A and 25B, and if "Support for daily life" is selected, it may also display a screen including sub-items such as "I need to go to the toilet" or "I want something to drink." In this way, various modifications to the details of the display screen are possible.

[0215] <Payment> Furthermore, the QR code C2 (second code information) related to the patient may also be information that the patient uses to make payments at the hospital. For example, as described above using Figure 14, equipment placed in the patient's room (such as the television 910 and refrigerator 920) can be used by the patient upon payment. As mentioned above, payment may be made in cash or by using a prepaid card.

[0216] In recent years, electronic payments using QR codes have also become widely used. Therefore, in this embodiment, the QR code C2 displayed on the display unit 240 may be code information for electronic payments. For example, when a patient's terminal device reads the QR code C2, a QR code payment application may be launched, and payment may be made in the same way as for general shopping. The QR code payment application here may be an application for using a widely used payment platform, or an application for using a system-specific service according to this embodiment. In this way, there is no need to prepare cash or prepaid cards, thus reducing the burden on the patient.

[0217] Figure 26 is an example of a payment process using QR code C2, and is a sequence diagram illustrating the payment process for using equipment in a patient's room. Note that the fact that the bed 100 and the bedside terminal device 200 are linked, and that the bedside terminal device 200 and the equipment are linked, is the same as the process described above using Figure 14.

[0218] In step S901, the equipment is powered on. In step S902, the equipment that has started operating notifies the connected bedside terminal device 200 that it has been powered on. These processes are the same as those shown in steps S401-S402 of Figure 14.

[0219] In step S903, the processing unit 210 of the bedside terminal device 200 displays instructions for using the equipment and a QR code C2 which is payment code information. For example, the display unit 240 may display the QR code C2 and also display text prompting the patient to scan the QR code C2 to make a payment for using the equipment.

[0220] In step S904, the patient's terminal device reads the QR code C2 displayed on the display unit 240 based on the patient's operation. In step S905, the terminal device launches an electronic payment application based on the reading result and executes the payment process. In step S906, the terminal device notifies the server system 300 of the payment result. The notification in step S906 may be sent from a payment server (not shown).

[0221] In step S907, the processing unit 310 of the server system 300 approves the payment. Specifically, upon receiving the notification in step S906, the server system 300 determines that the payment has been successfully completed. In this embodiment, the bedside terminal device 200 is associated with a location and also cooperates with the patient through the process described above using Figure 8. Therefore, with the method of this embodiment, it is possible to identify which patient made the payment for the equipment in which hospital room.

[0222] In step S908, the processing unit 310 identifies the bedside terminal device 200 related to the payment and transmits information to the bedside terminal device 200 that authorizes the activation of the equipment. If multiple pieces of equipment are linked to the bedside terminal device 200 and payment has been made for some of these pieces of equipment, the processing unit 310 may transmit information to identify the equipment in step S908.

[0223] In step S909, the processing unit 210 of the bedside terminal device 200 activates the equipment that is linked to the bedside terminal device 200 based on permission from the server system 300 shown in step S908. In step S910, the equipment starts operating.

[0224] The above sequence diagrams show an example where the equipment and the bedside terminal device 200 are connected, but the system is not limited to this. For example, if the equipment is not connected to the bedside terminal device 200, the display unit of the equipment (e.g., the display of the television 910) may display a screen prompting the patient to connect to the bedside terminal device 200, or a screen prompting the patient to make a nurse call to request assistance from a nurse or other staff member. When making a nurse call, for example, a button such as "Request equipment connection" may be added to the screen shown in Figures 25A and 25B. This would clearly indicate the patient's intention to use the equipment.

[0225] Figure 27 illustrates the operation of the information processing system 10 in this case. Note that the explanation of how the QR code displayed on the display unit 240 changes between QR code A and QR code C depending on the situation is the same as in Figure 16, so a detailed explanation is omitted. As mentioned above, the patient's QR code C2 is displayed when the bed 100 is in the third mode.

[0226] The QR code C2 may also be code information for electronic payment, as described above. When the patient's terminal device reads the QR code C2, it transitions to a payment screen and the payment for the use of the equipment is processed. After the payment is completed, the patient's terminal device sends a request to the server system 300 to use the equipment. The server system 300 confirms the contents of the usage request and instructs the bedside terminal device 200 to activate the equipment. The bedside terminal device 200 activates the equipment that has been linked and for which the patient has completed payment.

[0227] Furthermore, payment here is not limited to payment for the use of equipment, but may also include payment for meals, daily necessities, and other goods. For example, when a patient orders a meal or goods using the screen shown in Figure 25A, the terminal device transmits the order details to the server system 300. The server system 300 generates a QR code C2, which is code information for electronic payment including the billing amount, based on the order details, and transmits it to the bedside terminal device 200. The display unit 240 of the bedside terminal device 200 displays the QR code C2. When the patient's terminal device reads the QR code C2, it transitions to a payment screen and the payment for the meal or goods is processed.

[0228] After payment is completed, the patient's terminal device sends a request for the purchase to the server system 300. The server system 300 instructs the corresponding department (cafeteria, purchasing department, etc.) to deliver the goods. For example, if the delivery instruction is sent to the cafeteria, the cooking staff prepares the specified meal and delivers it to the patient's room. Or, if the delivery instruction is sent to the purchasing department, the purchasing department staff gathers the specified goods and delivers them to the patient's room. Alternatively, the delivery of meals or goods may be carried out by nurses or other staff. In this way, even patients who have difficulty moving (such as patients with fractures) can place orders using the bedside terminal device 200 and their own terminal device. Therefore, convenience is improved compared to calling a nurse via the nurse call system and verbally telling them what items they want to purchase.

[0229] It is also possible to entrust the delivery of goods to an external delivery service. The goods delivered here may be items purchased from the hospital cafeteria or store, as mentioned above, or items purchased from an external vendor (for example, a well-known e-commerce site). In this case, the delivery person will obtain the patient's room number as information to identify the delivery address along with the order details. In the case of a multi-bed room, the delivery person may also obtain information to identify bed 100. The delivery person will deliver the goods based on the patient's room number, etc.

[0230] However, in hospitals, a patient's room may change during their stay. In such cases, if deliveries are made based solely on the room number or bed number, there is a possibility that the goods will be delivered to a patient other than the original orderer. While misdeliveries can be prevented if the patient signs for the delivery, some hospitalized patients may have difficulty moving around or spend long periods sleeping and may not be able to respond to deliveries.

[0231] Therefore, the code information (QR code C) displayed when bed 100 is in the third mode may be information used for verifying the delivery destination (signing for delivery completion). Figure 28 shows an example of a screen displaying a QR code C used for delivery. The screen in Figure 28 is displayed, for example, on the display unit 240 of the bedside terminal device 200. The QR code C may be associated with text for the delivery person, such as "Delivery person, please obtain a completion stamp using this QR code."

[0232] In this case, QR code C includes patient identification information and location identification information. The patient's order details are also shared with the server system 300, and the processing unit 310 may include information indicating the order details, such as the product name and order date and time, in QR code C. When making a delivery, the delivery person launches a specific application on their terminal device and uses that application to read QR code C. This application has delivery functions and is software that can obtain information from a server that manages information such as the package's destination and recipient name. The application obtains patient identification information and location identification information corresponding to the bedside terminal device 200 by interpreting QR code C. The application then determines that the delivery is complete if the order details obtained from the server match the interpretation result of QR code C, and outputs an error if they do not match.

[0233] Using this type of code information reduces the need for patients to interact with delivery personnel, thus improving convenience.

[0234] Furthermore, the patient's terminal device is not prevented from reading the delivery code information. For example, when the patient's terminal device reads QR code C, the order details may be displayed on the terminal device's display. In this way, the patient can confirm the order details (products and scheduled delivery date). For example, when the patient places an order, or when the scheduled delivery date for the order arrives, the processing unit 310 of the server system 300 may perform a process to update QR code C. The updated QR code C is displayed in association with an object indicating that it has been updated, as shown in Figure 28. The object indicating the update is, for example, a circular object of a predetermined color, as in the example shown in Figure 21, but other objects may be used. In this way, the patient can be notified that the displayed QR code contains important information.

[0235] Furthermore, the payment according to this embodiment is not limited to the use of equipment, ordering meals, and purchasing goods as described above, but can broadly include other payments such as payments for hospitalization expenses.

[0236] <Information> Furthermore, the patient's QR code C2 (second code information) may contain information that displays a screen providing guidance or recommendations to the patient. The information displayed on this guidance or recommendation screen may be changed based on the patient's electronic medical record information. This allows for appropriate guidance / recommendations tailored to the patient's condition.

[0237] Figures 29A and 29C show examples of screens used for guidance or recommendations. Figure 29A is an example of a screen displayed on the display unit of a terminal device that reads a QR code C2 displayed to, for example, a patient after surgery. In other words, when the display unit 240 targets a patient whose time elapsed since surgery is below the first threshold, it displays a QR code C2 containing a URL corresponding to the screen shown in Figure 29A.

[0238] If not much time has passed since surgery, the patient's condition is not stable, so it is preferable for them to rest in a calm environment. Therefore, in this case, QR code C2 may display information on a screen showing information about paid rooms (private rooms). In the example in Figure 29A, in addition to the patient's name, age, gender, and current room information, information on available paid rooms and an application button are displayed. When the application button is selected, a room change request is sent to the server system 300. This change request is sent to the nurse's terminal device 600 or station terminal device 500. Based on this change request, the nurse performs tasks such as moving the patient to a different room. The private room fee may be settled before discharge, and in this case, the settlement process may be performed using the patient's QR code C2 as described above.

[0239] Figure 29B shows an example of a screen displayed on the terminal device's display unit after reading a QR code C2, for example, for a patient whose elapsed time since admission is below the second threshold. If not much time has passed since admission, it is assumed that the patient does not have sufficient information about their hospital floor. Therefore, in this case, QR code C2 displays a map of the hospital floor. QR code C2 may also include information such as a hospital introduction and visiting hours.

[0240] Figure 29C shows an example of a screen displayed on the display unit of a terminal device that reads a QR code C2, for example, for a patient the day after admission. For example, the screen shown in Figure 29B may be displayed on the first day of admission, and the screen shown in Figure 29C may be displayed from the following day onward.

[0241] On the day of admission, the admission procedures are hectic, and the short length of stay makes it difficult to determine what items are needed. However, by the day after admission, it becomes clear what items are lacking based on the previous day's activities. Therefore, in this case, QR code C2 may display information such as a screen recommending changes to meals or the purchase of items. Figure 29C shows an example of recommending the purchase of pajamas and an upgrade to meals. If the patient purchases pajamas or upgrades their meals, payment processing using the aforementioned QR code C2 may be performed.

[0242] As described above, by considering electronic medical records and other data when displaying guidance / recommendations, it is possible to present information that matches the patient's condition. For example, if a patient is elderly and unfamiliar with operating electronic devices, it may not be easy for them to find the desired information from among many guidance items. However, the method of this embodiment makes it possible to present appropriate information to such patients.

[0243] 4.4 Other UI The server system 300 (and electronic medical record server 400) described above is not limited to use within a single hospital, but may be shared by multiple hospitals. For example, each of multiple hospitals may use devices such as beds 100, bedside terminal devices 200, and terminal devices 600, and these devices may be connected to a common server system 300.

[0244] In this case, the table data showing the correspondence between bed 100, location, and patient, as shown in Figure 10, will include information about multiple hospitals. Therefore, the location identification information in this case will include not only information that identifies the ward or room, but also information that identifies the hospital (in a broad sense, information that identifies the facility, including nursing homes, etc.). Furthermore, information acquired at one hospital may be accessible from station terminal devices 500 and terminal devices 600 at other hospitals. This allows for the sharing of bed usage status (vacancy rate), making it possible to efficiently handle transfers and other related matters.

[0245] Furthermore, a QR code (QR code C1) containing information about patients admitted to Hospital 1 may be displayed on the display of the device used at Hospital 2. This would allow doctors and nurses at Hospital 2 to access highly important information about patients at Hospital 1. For example, if a patient is scheduled to be transferred from Hospital 1 to Hospital 2, sharing highly important information in advance as described above would facilitate a smooth transfer to Hospital 2. For instance, doctors and primary nurses could review detailed information included in the electronic medical record, while nurses in the same department but not the primary nurse could view only the simplified information based on the QR code.

[0246] Furthermore, the process of displaying code information for patients hospitalized at the first hospital in a remote location is not limited to being performed at the second hospital, but may also be performed at the home of the patient's family. For example, there may be cases where the patient and their family live separately, such as when the patient is elderly and their children are independent. In this case, since the family is unlikely to be medical professionals, it may not be easy for them to understand the patient's condition even if they are presented with a detailed electronic medical record. Therefore, the server system 300 provides a QR code for the family, and when a terminal device used by the patient's family reads the QR code, the terminal device's display unit displays information indicating an overview of the patient's condition. For example, the QR code may be displayed on a PC used by the patient's family, and the QR code may be read using a smartphone. In this case, it becomes possible to change the QR code itself according to the patient's condition, or to display additional information (whether there is an update, the timing of the update, etc.) associated with the QR code.

[0247] Alternatively, a static QR code may be provided to the patient's family. For example, the patient's family may print the QR code provided by the server system 300 onto paper and scan the printed QR code with a smartphone or similar device. The QR code may include, for example, a link to a web page displaying the patient's summary information. The server system 300 updates the information contained in the web page according to the patient's condition. In this way, the patient's family can always check the patient's condition by scanning the same QR code. An example of processing using a static QR code will be described later as a modified example.

[0248] 5. Variations The following describes some variations.

[0249] 5.1 Static QR Codes The above describes a QR code that changes dynamically depending on the situation. For example, the QR code includes QR codes A to C, which change depending on the connection status of bed 100. Furthermore, QR code C includes QR code C1 for nurses and QR code C2 for patients, and the information in these codes may change according to the patient's electronic medical record information, etc.

[0250] However, the code information according to this embodiment is not limited to dynamic information, but may also be static information. For example, the code information may be a code printed on a medium such as paper or cloth and placed in a predetermined position. In this way, information can be presented using fixed code information, making it possible to reduce the processing load associated with generating the code information.

[0251] Figure 30 shows an example of the arrangement of static code information. Figure 30 illustrates a multi-bed room in which multiple beds 100 are arranged in one room. For example, the code information is printed on a medium QRC, and the medium QRC is placed in association with the beds 100. The medium QRC on which the code information is printed may be attached to the wall corresponding to the bed 100, as shown in Figure 30, or it may be attached to a curtain or the like that partitions the beds 100. Furthermore, the attachment position of the medium QRC is not limited to this, and various variations such as the floor or ceiling can be implemented. The code information printed on the medium QRC is different depending on the position (bed 100), but the code information associated with one position is static information that does not change even if the electronic medical record changes.

[0252] The static code information may function as code information used to associate a location with bed 100 (corresponding to QR code A mentioned above), or as code information to present information tailored to the nurse or patient (corresponding to QR code C mentioned above), or it may function as both.

[0253] When using static code information, the content may be modified based on data (such as account name or attributes) held by the application that is launched by reading the code information. For example, the application requests content from the server system 300 using the account name, attributes, and the result of reading the QR code as parameters. The processing unit 310 of the server system 300 determines the content based on the parameters and sends that content to the application as a response.

[0254] For example, if the application reads the code information while the nurse is logged into the nurse's terminal device 600, the terminal device 600 sends a content request to the server system 300 that includes the nurse's account name, attributes representing the nurse, and location identification information contained in the code information. The processing unit 310 identifies the patient based on the location identification information contained in the QR code and creates content for the nurse regarding that patient. As described above, this content may be information indicating that the doctor's instructions have changed, or it may be information that is not desirable for the patient to view. The processing unit 310 may also determine, based on the account name, whether the nurse requesting the content is the patient's assigned nurse or a different nurse, and may modify the content based on the determination result. The processing unit 310 sends the created content to the requesting terminal device 600. The display unit 640 of the terminal device 600 displays the content, making it possible to present appropriate information to the nurse.

[0255] Similarly, if the application reads the code information on the patient's terminal device while the patient is logged in, the patient's terminal device sends a content request to the server system 300 including the patient's account name, attributes representing the patient, and location identification information contained in the code information. The processing unit 310 identifies the patient based on the location identification information contained in the QR code and creates content for that patient. For example, the processing unit 310 may obtain the patient's electronic medical record from the electronic medical record server 400 and create guidance / recommendation content according to the electronic medical record (Figures 29A-29C). The processing unit 310 may also create content for nurse calls (Figures 25A-25B). Furthermore, the processing unit 310 may perform authentication based on the account name to determine whether the patient who read the QR code is the appropriate patient linked to the location (in other words, whether the patient is mistakenly using someone else's bed 100).

[0256] The attribute here may also be the delivery person. In this case, the static QR code may function as the delivery confirmation code information described above, using Figure 28.

[0257] Furthermore, from the perspective of improving patient convenience, the above application does not need to be installed on the patient's terminal device. Alternatively, the above application may be installed on the patient's terminal device, but login operations do not need to be performed. If a static QR code is read without an account (not logged in), the processing unit 310 may create patient-specific content. In this way, patients can view information tailored to their situation without having to perform complex operations related to the application.

[0258] 5.2 NFC The above describes an example in which information is presented to nurses and patients by reading QR code C after the bed 100, its location, and the patient have been matched. However, the method of this embodiment is not limited to this, and near-field wireless communication such as NFC may be used instead of QR code C. Using NFC has the advantage of being easier for the user to operate compared to using QR code.

[0259] For example, the interface unit 270 of the bedside terminal device 200 may include an NFC tag or an NFC reader. Then, by performing NFC communication between the terminal device and the interface unit 270, content suitable for the user of the terminal device may be displayed on the display unit of the terminal device.

[0260] For example, when a nurse logs in to the application of the terminal device 600, the terminal device 600 performs NFC communication, and the content for the nurse is displayed on the display unit 640 of the terminal device 600. For example, the terminal device 600 transmits the account name and attributes of the application to the bedside terminal device 200. The bedside terminal device 200 transmits a content request to the server system 300, associating position identification information with the account name and attributes. The processing in the server system 300 is the same as in the case of using the static QR code described above. The bedside terminal device 200 transmits the acquired content to the terminal device 600, and the display unit 640 displays the content. Similarly, when the terminal device performing NFC communication is the patient's terminal device or the delivery person's terminal device, content can be displayed according to the user of the terminal device and the situation of the user.

[0261] Also, the object of performing NFC communication is not limited to the interface unit 270 of the bedside terminal device 200. For example, similar to the example of attaching a static QR code to a wall or the like, an NFC tag seal may be attached to a wall, a curtain, or the like in association with a position. The nurse or patient performs NFC communication by bringing the terminal device close to the NFC tag seal and transmits a content request including the reading result of the NFC tag seal to the server system 300. In this case as well, similar to the example of using a static QR code, content can be displayed according to the user and the situation of the user.

[0262] 5.3 Wireless Tag and Reader (RFID) Furthermore, above, an example of using code information (QR code) for the association with the position of the bed 100 has been described, but the method of this embodiment is not limited to this.

[0263] For example, the control unit of the bed system may acquire the output of a reader that reads data attached to a wireless communication tag. When the bed 100 is in the first mode (a state where neither position identification information nor patient identification information has been acquired), the control unit of the bed system may acquire position identification information by reading a first tag, which is a wireless communication tag arranged in association with a position. The wireless communication tag here is, for example, an RFID (Radio Frequency Identification) tag, and the reader is an RFID reader. By doing so, it becomes possible to link the position of the bed 100 with the wireless communication tag.

[0264] FIG. 31 is a diagram for explaining an arrangement example of a wireless communication tag and a reader. In FIG. 31, an example of a multi-bed ward is shown as in FIG. 30. For example, as shown in FIG. 31, the wireless communication tags TG are arranged in association with respective positions and include position identification information for uniquely identifying the positions. The wireless communication tags TG may be arranged on the wall or on the curtain. Further, the wireless communication tags TG may be arranged on the bedside terminal device 200. On the other hand, the reader RD is arranged on the bed 100 and moves as the bed 100 moves. Here, the reading range of the reader RD is, for example, about 1 - 2 meters. When the bed 100 is arranged at a prescribed position in the ward, only one wireless communication tag TG corresponding to that position can be read, and wireless communication tags TG corresponding to other positions cannot be read. Alternatively, when the reader RD can read a plurality of tags, it may be set to read only the tag with the highest radio wave intensity.

[0265] By doing so, it becomes possible to determine which position the bed 100 on which the reader RD is arranged corresponds to according to the reading result of the wireless communication tag TG by the reader RD. That is, it becomes possible to associate the bed 100 with the position identification information using the wireless communication tag TG and the reader RD.

[0266] Furthermore, if bed 100 is in second mode (a state in which location identification information has been acquired but patient identification information has not been acquired), the control unit of the bed system may acquire patient identification information by reading a second tag, which is a wireless communication tag attached to the patient. The second tag is, for example, a tag that can be attached to the patient's clothing and contains patient identification information that uniquely identifies the patient. When the reader RD placed on bed 100 reads the second tag, the patient corresponding to that second tag is located near bed 100. In other words, it can be determined that there is a high probability that the patient identified by the patient identification information of the second tag is the user of bed 100.

[0267] In this way, it becomes possible to determine which patient is using the bed 100 where the reader RD is located, based on the reading result of the wireless communication tag TG by the reader RD. In other words, it becomes possible to associate the bed 100 with patient identification information using the wireless communication tag TG and the reader RD.

[0268] 5.4 Modified Bed Modes and Mode Transitions The above describes the modes of bed 100 included in the bed system: Mode 1, in which bed 100 is not linked to either location identification information or patient identification information; Mode 2, in which bed 100 is linked to location identification information but not to patient identification information; and Mode 3, in which bed 100 is linked to both location identification information and patient identification information. As an example of mode transition, an example of transitioning from Mode 1 to Mode 2, and then from Mode 2 to Mode 3 was described. Hereafter, such mode transitions will be denoted as "Mode 1 → Mode 2 → Mode 3". An example of bed 100 returning from Mode 3 to Mode 1 when pairing is dissolved was also described (Figure 16, etc.).

[0269] However, the modes of the bed 100 according to this embodiment are not limited thereto. For example, the bed 100 may have a fourth mode that is not linked to location identification information but is linked to patient identification information. When the bed 100 transitions from the first mode to the third mode, it is not limited to the transition from the first mode to the second mode to the third mode described above, but may also transition from the first mode to the fourth mode to the third mode. In other words, if the bed 100 has not acquired either location identification information or patient identification information, location identification information may be acquired first (transition to the second mode), or patient identification information may be acquired first (transition to the fourth mode). In this way, it becomes possible to flexibly determine the order of linkage with location and patient. For example, if patient identification information can be acquired immediately by the patient's wristband (RFID) or facial recognition, but it takes time to update the location identification information, the transition from the first mode to the fourth mode to the third mode may occur.

[0270] Alternatively, if a patient admitted to the ICU is moved to a general ward, bed 100, which is in the third mode, may transition from the third mode to the fourth mode by performing a process that disconnects the link with the location (deletes the location identification information) while maintaining the connection with the patient (maintains the patient identification information). In this way, if the same patient continues to use bed 100 in a different location, it is possible to update the location identification information while maintaining the patient identification information. In the above example, after bed 100 moves to the general ward, it acquires location identification information based on the reading result of the QR code or RFID associated with the new location. As a result, bed 100 transitions from the fourth mode back to the third mode.

[0271] The fourth mode may also be used, for example, during the emergency transport of a patient. If a patient who has been urgently transported is temporarily staying in a room other than a normal hospital room or treatment room, bed 100 can obtain patient identification information from the RFID in the patient's wristband or facial recognition, but it may not be able to read the QR code or RFID tag in the hospital room. In this case, bed 100 in the fourth mode will be identified as being for emergency use.

[0272] Alternatively, the fourth mode may be used for the use of bed 100 at the patient's home. For example, in the case of community-based integrated care, bed 100 according to this embodiment may be installed at the home of a patient receiving home care rather than in a hospital. If it is determined that the patient is receiving home care, and patient identification information is obtained, hospital location identification information is no longer necessary, so bed 100 is registered in the fourth mode. In this case, instead of location identification information, a label indicating that it is in use at the patient's home and the patient's address information are registered in the storage unit 120 of bed 100 and the storage unit 320 of the server system 300. The decision of whether or not to assign a label here (determining whether bed 100 is being used at the patient's home) may be made by the processing unit 110, etc., obtaining patient information registered in the electronic medical record based on the patient identification information obtained when the patient is identified. In this case, whether the patient is an inpatient or a patient receiving home care is pre-registered in the electronic medical record. The processing unit 110, etc. may also assign the above label if it is determined that the bed system being used is not located within the hospital. In this case, bed 100 in mode 4 is identified as being in use at the patient's home.

[0273] The processing unit 110 may also determine whether the bed system, including the bed 100, is located within the hospital based on the network to which the bed 100 is connected. For example, the bed system may store information representing the hospital network in advance. This information may be, for example, the SSID (Service Set Identifier) ​​of a connecting device (such as a router) installed within the hospital, but it may also be other information. The processing unit 110 then determines that the bed system is located within the hospital if the information representing the network to which the bed 100 is connected matches any of the information representing the hospital network.

[0274] If a bed system is determined to be located within a hospital, then the system is subject to in-hospital operation. Specifically, bed 100 may transition from mode 1 → mode 2 → mode 3 as described above, or from mode 1 → mode 4 → mode 3. When it transitions to mode 3, it is identified as being used in a normal manner within the hospital. On the other hand, if it transitions from mode 1 to mode 4 within the hospital but does not transition to mode 3 (for example, if it does not transition to mode 3 even after a predetermined time has elapsed since transitioning to mode 4), then, as described above, bed 100 in mode 4 is identified as being used in an emergency within the hospital.

[0275] On the other hand, if it is determined that the bed system is not located within the hospital, the system will be used for operation at the patient's home. Specifically, bed 100 is capable of acquiring patient identification information, but it is not expected to acquire location identification information. Therefore, bed 100 will transition from mode 1 to mode 4, and will not transition to mode 3. In this case, as described above, bed 100 in mode 4 will be identified as being in use at the patient's home.

[0276] Furthermore, although the above describes an example where the transition destination from the second mode is the third mode (for example, Figure 16), the method of this embodiment is not limited to this. For example, if the bed 100 is moved while location identification information has been acquired but patient identification information has not, the processing unit 110 of the bed 100 may transition to the first mode by releasing the link with the location (deleting the location identification information from the storage unit 120).

[0277] 5.5 Display screen for patient QR code and display screen for nurse QR code The above describes an example in which the patient's QR code C2 is displayed on the screen shown in Figure 17, and the nurse's QR code C1 is displayed on the screen shown in Figure 18, which contains a relatively larger amount of information. However, the information displayed on the patient screen in Figure 18 is the result of extracting some of the data contained in the electronic medical record, and is displayed in an easy-to-understand manner using pictograms. Therefore, the screen shown in Figure 18 may also be used as a screen displayed to the patient.

[0278] For example, in step S612 of Figure 19, the display unit 240 of the bedside terminal device 200 may display a QR code C2 for the patient on a screen that includes pictograms similar to those in Figure 18. Then, in step S616 of Figure 19, the display unit 240 of the bedside terminal device 200 may display a QR code C1 for the nurse on a screen that includes pictograms similar to those in Figure 18. In other words, the display unit 240 may make the display content other than the QR code common between the screen that displays the QR code C2 for the patient and the screen that displays the QR code C1 for the nurse. When a nurse logs into the bedside terminal device 200 using NFC or the like, the display unit 240 displays a nurse screen that shows more detailed information than the patient screen shown in Figure 18.

[0279] Alternatively, in step S612 of Figure 19, the display unit 240 of the bedside terminal device 200 displays the patient's QR code C2 on a screen that includes pictograms similar to those in Figure 18. Then, in step S616 of Figure 19, the display unit 240 of the bedside terminal device 200 may display the nurse's QR code C1 on a screen that includes pictograms similar to those in Figure 18, as well as more detailed information for the nurse. In other words, the display unit 240 increases the amount of information displayed when it detects the approach of a nurse, as shown in steps S613-S614 of Figure 19, similar to the example in Figures 17-18, but the level of detail of the information displayed on each screen may be higher than in Figures 17-18. Thus, various modifications are possible to the information included on the screen that displays the nurse's QR code C1 and the screen that displays the patient's QR code C2.

[0280] Although the example of displaying the QR code C1 for nurses has been described, when a nurse logs in to the bedside terminal device 200 using NFC or the like without using the QR code C1 for nurses, the screen may be deformed to display the content read by the QR code C1 for nurses as well. In this case, the display unit 240 of the bedside terminal device 200 will display only the QR code C2 for patients.

[0281] 5.6 Other examples of association between bed and position identification information As described above, examples of the bed 100 acquiring position information by reading dynamic code information displayed on the display unit 240 of the bedside terminal device 200 using the imaging device 700, and examples of acquiring position identification information by reading static code information arranged on a wall surface or the like using the imaging device 700 have been described. However, the process of associating the bed 100 with the position identification information is not limited to this.

[0282] For example, information for specifying the position identification information may be input using the user interface of the bed 100. The user interface here may be, for example, a remote control for adjusting the angle of the bottom of the bed 100. Also, when the bed 100 is operable using the terminal device 600, the user interface may be the operation unit 650 of the terminal device 600.

[0283] The server system 300 associates the position identification information with a character string in advance. The character string here is, for example, a multi-digit number, but may include letters, symbols, etc. For example, a multi-digit number obtained by arranging the identification number of the ward, the identification number of the room, and the identification number of the bed position in the room is associated with the position identification information. However, the character string here only needs to be associated with the position identification information on a one-to-one basis, and the specific content is not limited to this.

[0284] Then, when the bed 100 is moved to a predetermined position, the nurse inputs a string corresponding to the destination position using the interface of the bed 100. The bed 100 then performs a process to identify the location based on the input string. For example, the processing unit 110 of the bed 100 may obtain the location identification information by querying the server system 300 using the string. Alternatively, the processing unit 110 may store the string itself as the location identification information. In this way, even if, for example, the bedside terminal device 200 is omitted, it becomes possible to associate the bed 100 with the location identification information.

[0285] Alternatively, the bed 100 may be associated with location identification information using an imaging device provided on a nurse's terminal device 600, etc. For example, static code information including bed identification information for bed 100 is assigned to the bed 100 in advance. For example, the static code information including bed identification information may be printed on a medium such as paper, and the medium may be attached to a predetermined location on the bed 100. Also, static code information including location identification information may be attached to the wall of the patient room, etc., as described above.

[0286] The nurse uses the imaging device of the terminal device 600 to read both the static QR code on the bed 100 and the static QR code on the wall. The processing unit 610 of the terminal device 600 obtains bed identification information by interpreting the QR code on the bed 100 and obtains location identification information by interpreting the QR code on the wall. The processing unit 610 then performs a process to associate the acquired bed identification information with the location identification information. For example, the terminal device 600 may output the information associating the bed identification information and location identification information to the bed 100 and the server system 300. This makes it possible to associate the bed 100 with the location identification information. In this example, even if a bedside terminal device 200 is not provided (especially if the imaging device 700 is not provided on the bed 100), it is still possible to associate the bed 100 with the location identification information.

[0287] 5.7 Location identification information of bedside terminal device The above describes the process of associating location identification information and patient identification information with bed 100. In this example, we considered a case where the position of the bedside terminal device 200 is fixed. In other words, in the above example, we considered a case where the bedside terminal device 200 and location identification information are pre-associated, and this association does not change. Therefore, a QR code A representing location identification information can be displayed on the bedside terminal device 200 (Figures 7 and 16), and the imaging device 700 can associate the location identification information with bed 100 by reading the QR code A. Furthermore, by associating bed 100 with location identification information, it is also possible to simultaneously associate bed 100 with bedside terminal device 200.

[0288] However, the method of this disclosure is not limited thereto, and the bedside terminal device 200 may be movable. In this case, in order to properly determine the location of the bedside terminal device 200, it is necessary to appropriately associate identification information that identifies the bedside terminal device 200 (hereinafter referred to as BS terminal identification information) with location identification information. Furthermore, even if the bed 100 acquires location identification information that represents the location of the bed 100, since this location identification information is not associated with the bedside terminal device 200, it may be necessary to separately associate the bed 100 with the bedside terminal device 200. Hereinafter, location identification information associated with the bed 100 will be referred to as bed location identification information, and location identification information associated with the bedside terminal device 200 will be referred to as BS terminal location identification information.

[0289] Figures 33A and 33B illustrate the operating modes of the bedside terminal device 200 and examples of information stored in the storage unit 220 in each operating mode. The bedside terminal device 200 may have different first to fourth modes depending on the state of coordination with other information, for example, the bed 100.

[0290] The first mode is an operating mode that corresponds to a state in which the bedside terminal device 200 is not linked to BS terminal location identification information, patient identification information, or bed 100. In this case, as shown in Figure 33A, the bedside terminal device 200 stores only BS terminal identification information that identifies the bedside terminal device 200.

[0291] The bedside terminal device 200 operating in the first mode may, for example, perform a process to acquire BS terminal location identification information. For example, the bedside terminal device 200 includes an imaging device (not shown) and performs a process to read a static QR code provided on a wall or the like using the imaging device. Alternatively, as in the example of associating the bed 100 with location identification information described above, a nurse or the like may input location identification information using the user interface of the bedside terminal device 200, or the QR code may be imaged using the nurse's terminal device 600.

[0292] The second mode is an operating mode that corresponds to a state in which the bedside terminal device 200 is linked with BS terminal location identification information, but is not linked with patient identification information or bed 100. In this case, as shown in Figure 33A, the bedside terminal device 200 stores BS terminal identification information and BS terminal location identification information.

[0293] The bedside terminal device 200 operating in the second mode may, for example, perform a process to acquire patient identification information. For example, the bedside terminal device 200 includes an imaging device (not shown) and performs a process to capture a facial image of the patient using the imaging device. This process is the same as the process by which the bed 100 acquires patient identification information, so a detailed explanation is omitted.

[0294] Alternatively, the bedside terminal device 200 operating in second mode may perform a process to acquire bed identification information and bed position identification information associated with the bed identification information in order to cooperate with the bed 100. For example, the display unit 240 of the bedside terminal device 200 may display a QR code for cooperation, and the bedside terminal device 200 and the bed 100 may cooperate by the imaging device 700 reading the QR code. Alternatively, the bed 100 and the bedside terminal device 200 may cooperate by searching for a device with high radio wave strength using a communication method such as WiFi or Bluetooth.

[0295] The third mode is an operating mode in which the bedside terminal device 200 is linked with BS terminal location identification information and is linked with at least one of patient identification information and bed 100. For example, as shown in Figure 33A, the bedside terminal device 200 in the third mode may be linked with the patient but not with bed 100. In this case, the storage unit 220 of the bedside terminal device 200 stores BS terminal identification information, BS terminal location identification information and patient identification information, but does not store bed identification information and bed location identification information.

[0296] Alternatively, as shown in Figure 33A, the third mode bedside terminal device 200 may be in a state where it is in cooperation with the bed 100 but not in cooperation with patient identification information. In this case, the storage unit 220 of the bedside terminal device 200 stores BS terminal identification information, BS terminal location identification information, bed identification information, and bed location identification information, but does not store patient identification information. For example, the processing unit 210 performs a comparison process between the BS terminal location identification information and the bed location identification information, and determines that the cooperation between the bedside terminal device 200 and the bed 100 is complete if the two represent the same location. The processing unit 210 may determine that the cooperation with the bed 100 has failed if the two represent different locations.

[0297] Alternatively, as shown in Figure 33A, the bedside terminal device 200 in the third mode may be in a state of coordination with the patient and the bed 100. In this case, the storage unit 220 of the bedside terminal device 200 stores BS terminal identification information, BS terminal location identification information, patient identification information, bed identification information, and bed location identification information. This state corresponds to the third mode of the bed 100 described above and is a state in which processing based on the correspondence between the bed 100, the bedside terminal device 200, the patient, and the location can be performed.

[0298] Furthermore, similar to the example where bed 100 can operate in a fourth mode without being linked to location identification information, the bedside terminal device 200 may also operate in a fourth mode. The fourth mode is an operating mode that corresponds to a state in which the bedside terminal device 200 is linked to at least one of patient identification information and bed 100, but not to location. For example, as shown in Figure 33B, the bedside terminal device 200 in the fourth mode may be linked only to the patient. In this case, the storage unit 220 of the bedside terminal device 200 stores BS terminal identification information and patient identification information, but does not store BS terminal location identification information, bed identification information, and bed location identification information.

[0299] Alternatively, as shown in Figure 33B, the fourth mode bedside terminal device 200 may be in a state where it is only connected to the bed 100. In this case, the storage unit 220 of the bedside terminal device 200 stores BS terminal identification information and bed identification information, but does not store BS terminal location identification information, patient identification information, and bed location identification information.

[0300] Alternatively, as shown in Figure 33B, the bedside terminal device 200 in the fourth mode may be in a state of coordination with the patient and the bed 100. In this case, the storage unit 220 of the bedside terminal device 200 stores BS terminal identification information, patient identification information, and bed identification information, but does not store BS terminal location identification information and bed location identification information.

[0301] By providing a fourth mode, it becomes possible to perform processing that associates two or more of the following: the bed 100, the bedside terminal device 200, and the patient, even when location association is not performed. The state in which location association is not performed includes, as in the example described above regarding the fourth mode of the bed 100, cases where a patient who has been urgently transported is temporarily staying in a room other than a normal hospital room or treatment room.

[0302] Although this embodiment has been described in detail above, it will be readily apparent to those skilled in the art that many modifications are possible without substantially departing from the novel aspects and effects of this embodiment. Therefore, all such modifications are included within the scope of this disclosure. For example, any term that appears at least once in the specification or drawings together with a broader or synonymous term may be replaced with that different term anywhere in the specification or drawings. Furthermore, all combinations of this embodiment and its modifications are also included within the scope of this disclosure. In addition, the bed system, information processing system, server system, bed, bedside terminal device, terminal device configuration and operation, etc., are not limited to those described in this embodiment, and various modifications are possible. [Explanation of Symbols]

[0303] 10... Information processing system, 100... Bed, 110... Processing unit, 120... Memory unit, 130... Communication unit, 140... Operation unit, 150... Drive unit, 160... Movable unit, 170... Mattress, 200... Bedside terminal device, 210... Processing unit, 220... Memory unit, 230... Communication unit, 240... Display unit, 250... Operation unit, 260... Notification unit, 270... Interface unit, 300... Server system, 310... Processing 320...Storage Unit, 330...Communication Unit, 400...Electronic Medical Record Server, 500...Station Terminal Device, 600...Terminal Device, 610...Processing Unit, 620...Storage Unit, 630...Communication Unit, 640...Display Unit, 650...Operation Unit, 700...Imaging Device, 810...Detection Device, 820...Measurement Device, 830...Authentication Card, 910...Television, 920...Refrigerator, QRC...Media, RD...Reader, TG...Wireless Communication Tag

Claims

1. A bed system including a bed, If neither the location identification information representing the bed's position nor the patient identification information representing the patient using the bed has been obtained, then the location identification information is obtained. When the location identification information is obtained, the patient identification information is obtained, The system includes, when the patient identification information is obtained, a bed identification information that identifies the bed, a position identification information, and a control unit that associates the patient identification information, Bed system.

2. In the bed system according to claim 1, The control unit, The imaging device captures the code information arranged in correspondence with the aforementioned position, and the position identification information is obtained based on the code information. A bed system that, when the location identification information is obtained, causes the imaging device to image the region including the patient's face, and obtains the patient identification information based on the image of the region including the patient's face.

3. In the bed system according to claim 2, The bedside terminal device, which is a terminal device having a display unit and is provided near the bed, further includes A bed system in which the display unit of the bedside terminal device displays the code information.

4. In the bed system according to claim 3, The aforementioned bedside terminal device is A bed system that displays different code information on the display unit in each of the following states: when not connected to the bed, when connected to the bed and the bed has acquired the position identification information but has not acquired the patient identification information, and when connected to the bed and the bed has acquired the position identification information and the patient identification information.

5. In the bed system according to claim 3, The aforementioned bedside terminal device is A bed system in which, when the bed has acquired the position identification information and the patient identification information, the bed displays on the display unit at least one of the first code information, which is the code information corresponding to a nurse's screen for the nurse in charge of the patient, and the second code information, which is the code information corresponding to a patient's screen for the patient.

6. In the bed system described in claim 5, The aforementioned first code information is A bed system that, when read by the first terminal device used by the nurse, displays patient information corresponding to the patient identification information on the display unit of the first terminal device.

7. In the bed system described in claim 6, The aforementioned bedside terminal device is When instruction information representing instructions from other staff to the nurse regarding the patient corresponding to the patient identification information is updated, A bed system that associates and displays an object representing an update with the aforementioned first code information.

8. In the bed system described in claim 7, The aforementioned bedside terminal device is Summary information representing the outline of the instruction information is displayed in association with the first code information. The aforementioned first code information is A bed system that, when read by the first terminal device, displays on the display unit of the first terminal device more detailed information than the summary information regarding the instruction information.

9. In the bed system described in claim 5, The aforementioned second code information is, A bed system that, when read by a second terminal device used by the patient, displays a screen on the display unit of the second terminal device used by the patient to express their wishes.

10. In the bed system according to claim 9, The aforementioned second code information is, A bed system is a bed system that causes the display unit of the second terminal device to display a screen including a first display object for the patient to contact the nurse and a second display object for the patient to contact staff other than the nurse.

11. In the bed system according to claim 9 or 10, The aforementioned second code information is, The aforementioned patient's information for making payments at the hospital is part of the bed system.

12. In the bed system according to claim 9 or 10, The aforementioned second code information is, A bed system that displays information for the patient, which is modified based on the electronic medical record information relating to the patient.

13. In the bed system according to claim 3, The aforementioned bedside terminal device is A bed system that, when not connected to the bed, displays the code information corresponding to the position identification information and pairing information for connecting the bed and the bedside terminal device on the display unit.

14. In the bed system according to claim 3, The aforementioned bedside terminal device is A bed system that, when the bed has acquired the position identification information but has not acquired the patient identification information, displays the code information corresponding to a screen prompting the acquisition of the patient identification information on the display unit.

15. In the bed system according to claim 2, The code information is static information of a bed system placed at the aforementioned location.

16. In the bed system according to claim 1 or 2, The bedside terminal device, which is a terminal device having a display unit and is provided near the bed, further includes The bedside terminal device is connected to an electronic device which is equipment installed near the bed. The control unit, A bed system that, when the bed and the bedside terminal device are linked, triggered by the power being turned on of the electronic device, outputs electronic device identification information that identifies the electronic device in association with the bed identification information, the location identification information, and the patient identification information.

17. In the bed system according to claim 1, The control unit, A bed system that acquires location identification information by reading data attached to a first tag, which is a wireless communication tag positioned in correspondence with the aforementioned location.

18. In the bed system according to claim 17, The control unit, A bed system that acquires patient identification information by reading a second tag, which is a wireless communication tag attached to the patient.

19. A bed system including a bed, If neither the location identification information representing the bed's position nor the patient identification information representing the patient using the bed has been obtained, the process of obtaining the location identification information is performed. When the location identification information is obtained, the process of obtaining the patient identification information is performed. When the patient identification information is obtained, the bed identification information that identifies the bed, the location identification information, and the patient identification information are associated with each other. Information processing methods.

Images