Calling device recovery support system, program, and calling device recovery support method

Abstract

This system provides support to help users without specialized knowledge of nurse call system paging devices recover from malfunctions. [Solution] When the maintenance terminal 2 receives an abnormality detection notification for any of the call devices 91 from the main unit 8 of the nurse call system 7, it displays the device ID of the call device 91 and the details of the abnormality (no response, delayed response, error message, etc.) included in the abnormality detection notification, and prompts the maintenance manager to select a recovery procedure for the call device in which the abnormality was detected from among several recovery procedures that are stored in advance. The maintenance terminal 2 then transmits the selected recovery procedure, along with the abnormality detection notification, to the support terminal 3 installed in the waiting area (nurse center, etc.) of the users (doctors, nurses, caregivers, etc.) who use the nurse call system 7. In response, the support terminal 3 displays the device ID of the call device 91 and the details of the abnormality included in the abnormality detection notification, along with the recovery procedure.

Description

Technical Field

[0001] The present invention relates to a technology for assisting in the recovery of a calling device in which an abnormality has occurred in a nurse call system.

Background Art

[0002] Patent Document 1 discloses a medical device monitoring system that detects an abnormality in a medical device and notifies a nurse call system. In this medical device monitoring system, when an abnormality occurs in a medical device, the medical device outputs a warning sound and a warning light or changes a display to notify the medical device monitoring device of the abnormality. Then, when the medical device monitoring device simultaneously detects a warning sound and the output of a warning light or a change in the display from the medical device to be monitored, it determines that an abnormality has occurred in this medical device and notifies the nurse call system of the detection of the abnormality in this medical device.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, the medical device monitoring system described in Patent Document 1 does not take into account the case where there is a malfunction in the nurse call system's call device. As a result, it may be difficult for users of the nurse call system to notice a malfunction in the call device. Furthermore, if a user notices a malfunction in the call device, they will usually request the maintenance manager to restore it, but such malfunctions can often be resolved using one of several typical recovery procedures, and the user may be able to handle it themselves. In such cases, the maintenance manager will explain to the user which typical recovery procedure to try, but explaining such typical recovery procedures every time is cumbersome. Moreover, if the user cannot contact the maintenance manager, they must determine the recovery procedure themselves, but it is difficult to determine the correct recovery procedure without specialized knowledge of the maintenance and management of the call device.

[0005] This invention has been made in view of the above circumstances, and its purpose is to help users who lack specialized knowledge regarding the maintenance and management of nurse call system call devices to restore a call device that has malfunctioned. [Means for solving the problem]

[0006] To solve the above problems, in a first embodiment of the present invention, when a maintenance terminal receives an abnormality detection notification from the main unit of the nurse call system regarding a call device housed in the main unit, it displays the identification information of the call device and the details of the abnormality (no response, delayed response, error message, etc.) contained in the abnormality detection notification, and allows the maintenance manager to select a recovery procedure suitable for recovering from the abnormality of the call device from among a plurality of recovery procedures stored in advance. The selected recovery procedure is then transmitted along with the abnormality detection notification to a support terminal installed in the waiting area (nurse center, etc.) of users (doctors, nurses, caregivers, etc.) of the nurse call system. Upon receiving this, the support terminal displays the identification information of the call device and the details of the abnormality contained in the abnormality detection notification along with the recovery procedure.

[0007] For example, a first aspect of the present invention is: A call device recovery support system that assists in the recovery of a nurse call system's call device from malfunction, Equipped with a maintenance terminal and a support terminal, The aforementioned maintenance terminal is Notification receiving means for receiving abnormality detection notifications from the main unit of the nurse call system, the main unit of the nurse call system is connected to the notification receiving means, A procedure selection means that displays the identification information of the calling device and the details of the abnormality included in the abnormality detection notification received by the notification receiving means, and accepts the selection of a desired recovery procedure from among a plurality of recovery procedures stored in advance, The system includes a procedure transmission means that transmits the recovery procedure selected by the procedure selection means, along with the anomaly detection notification, to the support terminal. The aforementioned support terminal is A procedure receiving means for receiving the recovery procedure and the anomaly detection notification from the maintenance terminal, The system includes a procedure display means that displays the recovery procedure received by the procedure receiving means, together with the identification information of the calling device and the details of the abnormality included in the abnormality detection notification received by the procedure receiving means along with the recovery procedure.

[0008] Furthermore, in a second aspect of the present invention, a support terminal installed in a waiting area (such as a nurse center) for users (doctors, nurses, caregivers) using the nurse call system receives an abnormality detection notification from the main unit of the nurse call system regarding a call device housed in the main unit. The support terminal displays the identification information of the call device and the details of the abnormality (such as no response, delayed response, or error message) included in the abnormality detection notification. The inquiry terminal displays a predetermined question regarding the abnormality of the call device, receives a response from the user, and uses the user's response and pre-stored information from the nurse call system to create an inquiry statement asking for the recovery procedure for the call device in which the abnormality was detected. The inquiry statement is then sent to a predetermined AI server that provides AI (Artificial Intelligence) services, and the AI ​​server obtains and displays a recovery procedure suitable for this call device.

[0009] For example, a second aspect of the present invention is: A call device recovery support system that assists in the recovery of a nurse call system's call device from malfunction, Equipped with a support terminal and an inquiry terminal, The aforementioned support terminal is Notification receiving means for receiving abnormality detection notifications from the main unit of the nurse call system, the main unit of the nurse call system is connected to the notification receiving means, The system includes a notification display means that displays the identification information of the calling device and the details of the abnormality included in the abnormality detection notification received by the notification receiving means, The aforementioned inquiry terminal is A questioning means that displays a predetermined question regarding the abnormality of the calling device displayed on the support terminal and accepts answers to said question, An inquiry statement creation means creates an inquiry statement that inquires about the recovery procedure for the call device in which an abnormality has been detected, using the answers received by the aforementioned questioning means and the nurse call system information stored in advance. A procedure acquisition means that transmits the query statement created by the query statement creation means to a predetermined AI server that provides AI (Artificial Intelligence) services, and obtains the recovery procedure from the AI ​​server, The system includes a procedure display means for displaying the recovery procedure acquired by the procedure acquisition means. [Effects of the Invention]

[0010] According to a first aspect of the present invention, by installing a support terminal at a waiting area (such as a nurse center) for users (doctors, nurses, caregivers, etc.) of the nurse call system, when an abnormality in a call device is detected, the user can be notified of the fact along with the recovery procedure. Furthermore, the maintenance manager can use the maintenance terminal to select a recovery procedure suitable for the abnormal call device from among several pre-prepared recovery procedures, based on the identification information and nature of the abnormality of the call device, and notify the support terminal. This improves convenience.

[0011] Also, according to the second aspect of the present invention, similar to the first aspect of the present invention, by installing a support terminal at the waiting place of a user who uses a nurse call system, when an abnormality of a calling device is detected, the fact can be notified to the user. Further, the user can send an inquiry sentence to the AI server to inquire about the recovery procedure of the calling device in which an abnormality has been detected by using an inquiry terminal to answer the questions of the inquiry terminal based on the identification information of the calling device and the content of the abnormality displayed on the support terminal, and obtain the recovery procedure from the AI server. Thereby, convenience is improved.

[0012] Thus, according to the present invention, even a user who has no specialized knowledge about the calling device of the nurse call system can be assisted so that they can recover the calling device in which an abnormality has occurred.

Brief Description of the Drawings

[0013] [Figure 1] FIG. 1 is a diagram showing the schematic configuration of a calling device recovery support system 1 according to the first embodiment of the present invention together with the schematic configuration of a nurse call system 7 to be the recovery support target. [Figure 2] FIG. 2 is a sequence diagram for explaining the operation of the calling device recovery support system 1 according to the first embodiment of the present invention. [Figure 3] FIG. 3 is a sequence diagram for explaining the operation of the calling device recovery support system 1 according to the first embodiment of the present invention and is a continuation of FIG. 2. [Figure 4] FIG. 4 is a schematic functional configuration diagram of the maintenance terminal 2. [Figure 5] FIG. 5(A) is a diagram showing an example of an abnormality detection notification display screen 210, and FIG. 5(B) is a diagram showing an example of a recovery procedure selection screen 220. [Figure 6] FIG. 6 is a diagram schematically showing a registration content example of the abnormality detection notification storage unit 204. [Figure 7] FIG. 7 is a diagram schematically showing a registration content example of the recovery procedure storage unit 205. [Figure 8]FIG. 8 is a flowchart for explaining the operation of the maintenance terminal 2. [Figure 9] FIG. 9 is a schematic functional configuration diagram of the support terminal 3. [Figure 10] FIG. 10 is a diagram showing an example of the recovery guidance display screen 310. [Figure 11] FIG. 11 is a flowchart for explaining the operation of the support terminal 3. [Figure 12] FIG. 12 is a schematic functional configuration diagram of the main device 8. [Figure 13] FIG. 13 is a flowchart for explaining the state monitoring operation of the main device 8. [Figure 14] FIG. 14 is a diagram showing the schematic configuration of the call device recovery support system 1' according to the second embodiment of the present invention together with the schematic configuration of the nurse call system 7' to be recovered. [Figure 15] FIG. 15 is a sequence diagram for explaining the operation of the call device recovery support system 1' according to the second embodiment of the present invention. [Figure 16] FIG. 16 is a schematic functional configuration diagram of the maintenance terminal 2'. <​​​​​​​​​​​​​​​​​​​​​​​​​​​[First Embodiment] First, a first embodiment of the present invention will be described.

[0016] Figure 1 is a diagram showing the schematic configuration of the call device recovery support system 1 according to this embodiment, along with the schematic configuration of the nurse call system 7 that is the target of recovery support.

[0017] As shown in the figure, the call device recovery support system 1 according to this embodiment assists in the recovery of a call device 91 from an abnormality that occurs in any of the multiple call devices 91 included in the nurse call system 7.

[0018] Here, the nurse call system 7 targeted for recovery support is configured to include a call device 91 installed at each hospital bed or bedside in a hospital, nursing home, etc., used by patients, care recipients, etc. to call doctors, nurses, caregivers, etc.; a telephone 90 installed in a waiting area (nurse center, etc.) for doctors, nurses, caregivers, etc., to respond to calls (nurse calls) from the call device 91; and a main unit 8 that houses the telephone 90 and the call device 91. The telephone 90 is connected to the main unit 8 via a LAN (Local Area Network) 92. The call device 91 is wirelessly connected to an AP (Access Point) 93 and is connected to the main unit 8 via the AP 93 and LAN 92. In addition to the telephone 90 and the call device 91, the main unit 8 also houses the maintenance terminal 2 and relay device 4 described later, and provides internal telephone service to these terminals 2, 90 and devices 4, 91 that it houses.

[0019] The call system recovery support system 1 comprises a maintenance terminal 2, a support terminal 3, and a relay device 4. The maintenance terminal 2 is a terminal carried by the maintenance manager of the nurse call system 7 and is connected to the main unit 8 via a WAN (Wide Area Network) 94, a GW (Gateway) 95, and a LAN 92. The support terminal 3 is installed in the waiting area for doctors, nurses, caregivers, etc. (users of the nurse call system 7) and is connected to the relay device 4 via the LAN 92. As described above, the relay device 4 is housed in the main unit 8 of the nurse call system 7 and relays communication between the main unit 8 and the support terminal 3.

[0020] Figures 2 and 3 are sequence diagrams illustrating the operation of the call device recovery support system 1 according to this embodiment.

[0021] The main unit 8 periodically sends a status check request to each of the call devices 91 and receives a status check response containing information about the operating status of each call device 91, thereby monitoring the status of each call device 91 (S100). When it detects an abnormality in any of the call devices 91 (S101), it sends an abnormality detection notification to the maintenance terminal 2 (S102). This abnormality detection notification includes the device ID, which is the identification information of the call device 91 in which the abnormality was detected, the details of the abnormality (no response, delayed response, and error messages included in the status check response, etc.), and the notification ID, which is the identification information of this abnormality detection notification. This abnormality detection notification is sent to the maintenance terminal 2 via LAN 92, gateway 95, and WAN 94.

[0022] When the maintenance terminal 2 receives an anomaly detection notification from the main unit 8, it displays the device ID of the call device in which the anomaly was detected and the details of the anomaly, as included in the anomaly detection notification (S103), and displays a recovery procedure selection screen to accept the selection of a recovery procedure for the call device 91 in which the anomaly was detected from among several recovery procedures that have been stored in advance (S104). Then, when it receives the operation to select a recovery procedure from the maintenance manager (S105), it sends a recovery guidance to the main unit 8, which includes the selected recovery procedure and the anomaly detection notification, with the destination being the support terminal 3 (S106).

[0023] In response, the main unit 8 transmits the recovery guidance received from the maintenance terminal 2 to the relay device 4 (S107). The relay device 4 relays the recovery guidance received from the main unit 8 to the support terminal 3 (S108), and the support terminal 3 displays the anomaly detection notification and recovery procedure included in the recovery guidance received from the relay device 4 (S109).

[0024] As described above, users of the nurse call system 7 can learn about the call device 91 that experienced an abnormality, along with the details of the abnormality, by checking the abnormality detection notification and recovery procedure displayed on the support terminal 3, and can also learn the recovery procedure to restore the call device 91 from the abnormality.

[0025] Subsequently, when the support terminal 3 receives the results of the recovery procedure from the user of the nurse call system 7, along with the designation of an anomaly detection notification (S110), it sends an implementation result notification to the relay device 4, which includes the correspondence information between the procedure name of the recovery procedure and its implementation result, and the notification ID of the designated anomaly detection notification, with the destination being the maintenance terminal 2 (S111). In response, the relay device 4 relays the implementation result notification received from the support terminal 3 to the main unit 8 (S112), and the main unit 8 sends the implementation result notification received from the relay device 4 to the maintenance terminal 2 (S113). The maintenance terminal 2 then displays the anomaly detection notification and the results of the recovery procedure, which are identified by the notification ID included in the implementation result notification received from the main unit 8 (S114).

[0026] Next, the maintenance terminal 2 and support terminal 3 that constitute the call device recovery support system 1 according to this embodiment will be described.

[0027] Since the relay device 4 can utilize an existing relay device that relays signals between the main device 8 and the support terminal 3, a detailed explanation of it will be omitted.

[0028] First, let me explain maintenance terminal 2.

[0029] Figure 4 is a schematic diagram of the functional configuration of maintenance terminal 2.

[0030] As shown in the figure, the maintenance terminal 2 includes a wireless interface unit 200, a human-machine interface unit 201, a notification receiving unit 202, a notification display unit 203, an anomaly detection notification storage unit 204, a recovery procedure storage unit 205, a procedure selection unit 206, a recovery guidance transmission unit 207, a result receiving unit 208, and a result display unit 209.

[0031] The wireless interface unit 200 is an interface for connecting to the WAN 94 via a wireless base station, access point, etc. (not shown).

[0032] The man-machine interface unit 201 is an interface for displaying information to the maintenance administrator, who is the user of the maintenance terminal 2, and for receiving various operations from the maintenance administrator. It is configured with input / output devices such as a liquid crystal display with touch panel functionality.

[0033] The notification receiving unit 202 receives an anomaly detection notification from the main unit 8 via the wireless interface unit 200.

[0034] The notification display unit 203 displays an anomaly detection notification display screen 210 on the human-machine interface unit 201, which displays an anomaly detection notification received by the notification receiving unit 202.

[0035] Figure 5(A) shows an example of the anomaly detection notification display screen 210.

[0036] As shown in the figure, the anomaly detection notification display screen 210 displays the device ID 211 and the details of the anomaly 212 of the call device 91 in which the anomaly was detected, along with a button 213 that accepts a call instruction for the recovery procedure selection screen 220, which will be described later.

[0037] The anomaly detection notification storage unit 204 stores the anomaly detection notifications received by the notification receiving unit 202.

[0038] Figure 6 is a schematic diagram showing an example of the registered contents of the anomaly detection notification storage unit 204.

[0039] As shown in the figure, the anomaly detection notification storage unit 204 stores an anomaly detection notification record 2040 for an anomaly detection notification received from the main unit 8. The anomaly detection notification record 2040 has a field 2041 for registering the notification ID of the anomaly detection notification, a field 2042 for registering the device ID of the call device 91 in which the anomaly was detected, a field 2043 for registering the details of the anomaly (no response, delayed response, error message, etc.), and a field 2044 for registering whether the recovery from the anomaly was successful or not. Field 2044 stores a list of correspondence information between the procedure name of the recovery procedure that was performed and the result of the procedure (recovery successful, recovery failed).

[0040] Here, fields 2041 to 2043 register the notification ID, device ID, and details of the anomaly included in the anomaly detection notification. On the other hand, field 2044 registers the correspondence information between the procedure name of the recovery procedure included in the implementation result notification, which has the same notification ID as the anomaly detection notification, and the implementation result. Therefore, field 2044 remains unregistered (null) until the result receiving unit 208, described later, receives an implementation result notification from the support terminal 3 that has the same notification ID as the notification ID in field 2041.

[0041] The recovery procedure storage unit 205 stores the recovery procedure for the call device 91 in which an abnormality was detected.

[0042] Figure 7 is a schematic diagram illustrating an example of the registered contents of the recovery procedure storage unit 205.

[0043] As shown in the figure, the recovery procedure storage unit 205 stores a recovery procedure record 2050 for each recovery procedure that can be taken to resolve an abnormality in the calling device 91. The recovery procedure record 2050 has a field 2051 for registering the procedure ID, which is the identification information of the recovery procedure, a field 2052 for registering the procedure name of the recovery procedure, and a field 2053 for registering the recovery procedure.

[0044] When button 213 is operated on the anomaly detection notification display screen 210 displayed on the man-machine interface unit 201, the procedure selection unit 206 displays a recovery procedure selection screen 220 on the man-machine interface unit 201, linked to the anomaly detection notification displayed on the anomaly detection notification display screen 210. This screen allows the user to select one of the recovery procedure records 2050 stored in the recovery procedure storage unit 205. The procedure selection unit 206 then accepts the selection of the desired recovery procedure record 2050 from the maintenance administrator via the recovery procedure selection screen 220.

[0045] Figure 5(B) shows an example of the recovery procedure selection screen 220.

[0046] As shown in the diagram, the recovery procedure selection screen 220 displays a recovery procedure list 221 that accepts the selection of a record 2050 from among the recovery procedure records 2050 stored in the recovery procedure storage unit 205. The titles of the items included in this recovery procedure list 221 use the procedure name from field 2052 of the recovery procedure record 2050. The maintenance administrator can select the recovery procedure record 2050 corresponding to the item by selecting an item from the recovery procedure list 221, for example by checking the checkbox in front of the title. It is also possible to select multiple recovery procedure records 2050 from the recovery procedure list 221. In addition, the recovery procedure selection screen 220 displays a comment input field 222 for optionally accepting comments from the user of the nurse call system 7, and a send button 223 for sending recovery guidance.

[0047] When the send button 223 is operated on the recovery procedure selection screen 220 displayed on the man-machine interface unit 201, the recovery guidance transmission unit 207 transmits recovery guidance, which includes the anomaly detection notification associated with the recovery procedure selection screen 220 and the record 2050 of the recovery procedure selected by the procedure selection unit 206, to the support terminal 3 via the wireless interface unit 200. If a comment has been entered in the comment input field 222 of the recovery procedure selection screen 220, this comment is also included in the recovery guidance and transmitted.

[0048] The result receiving unit 208 receives the implementation result notification from the support terminal 3 via the wireless interface unit 200. It also searches the anomaly detection notification storage unit 204 for an anomaly detection notification record 2040 that contains the same notification ID as the notification ID included in the received implementation result notification, and registers a list of correspondence information between the procedure name of the recovery procedure performed and its implementation result, as included in the implementation result notification, in field 2044 of the retrieved record 2040.

[0049] The result display unit 209 then displays on the man-machine interface unit 201 a list of correspondence information between the procedure names of the implemented recovery procedures and their implementation results, which is included in the implementation result notification received by the result receiving unit 208, along with the anomaly detection notification having a notification ID included in the implementation result notification.

[0050] The functional configuration of the maintenance terminal 2 shown in Figure 4 is realized as a process in a general-purpose computer such as a smartphone or tablet PC (Personal Computer) equipped with a CPU (Central Processing Unit), memory, auxiliary storage device such as an SSD (Solid State Drive), and communication device such as a wireless NIC (Network Interface Card), by the CPU loading a predetermined program from the auxiliary storage device into memory and executing it.

[0051] Figure 8 is a flowchart illustrating the operation of maintenance terminal 2.

[0052] When the notification receiving unit 202 receives an anomaly detection notification from the main unit 8 via the wireless interface unit 200 (YES in S200), it adds a new anomaly detection notification record 2040 to the anomaly detection notification storage unit 204, and registers the notification ID, device ID, and anomaly details included in the anomaly detection notification in fields 2041 to 2043 of this record 2040. The notification display unit 203 also displays the anomaly detection notification display screen 210 on the man-machine interface unit 201 (S201). The anomaly detection notification received from the main unit 8 is displayed on this anomaly detection notification display screen 210 (see Figure 5(A)).

[0053] Subsequently, when the button 213 for calling up the recovery procedure selection screen 220 on the anomaly detection notification display screen 210 displayed on the man-machine interface unit 201 is operated (YES in S202), the procedure selection unit 206 displays the recovery procedure selection screen 220 associated with this anomaly detection notification on the man-machine interface unit 201 (S203). Then, on the recovery procedure selection screen 220, when at least one item is selected from the recovery procedure list 221, and a comment is entered in the comment input field 222 as necessary, and the send button 223 is operated (YES in S204), the procedure selection unit 206 reads the recovery procedure record 2050 corresponding to the selected item from the recovery procedure storage unit 205, and generates recovery guidance that includes this recovery procedure record 2050 and the anomaly detection notification associated with the recovery procedure selection screen 220. If a comment has been entered in the comment input field 222 of the recovery procedure selection screen 220, this comment is also included in the recovery guidance. The procedure selection unit 206 then transmits this recovery guidance to the support terminal 3 via the wireless interface unit 200 (S205).

[0054] Furthermore, when the result receiving unit 208 receives an implementation result notification from the support terminal 3 via the wireless interface unit 200 (YES in S206), it searches the anomaly detection notification storage unit 204 for an anomaly detection notification record 2040 having a field 2041 in which the same notification ID as the notification ID included in the received implementation result notification is registered, and registers a list of correspondence information between the procedure name of the implemented recovery procedure and its implementation result, which is included in the implementation result notification, in field 2044 of the retrieved record 2040. It also passes this anomaly detection notification record 2040, in which the procedure name of the recovery procedure and its implementation result are registered, to the result display unit 209. In response, the result display unit 209 displays the device ID (device ID of the call device 91 in which the anomaly was detected), the content of the anomaly, the procedure name of the implemented recovery procedure, and its implementation result, which are included in the anomaly detection notification record 2040, on the man-machine interface unit 201 (S207).

[0055] Next, I will explain support terminal 3.

[0056] Figure 9 is a schematic diagram of the functional configuration of support terminal 3.

[0057] As shown in the figure, the support terminal 3 includes a network interface unit 300, a human-machine interface unit 301, a recovery guidance receiving unit 302, a recovery guidance display unit 303, a recovery guidance storage unit 304, an implementation result receiving unit 305, and an implementation result notification unit 306.

[0058] The network interface unit 300 is an interface for connecting to the relay device 4 via LAN 92.

[0059] The human-machine interface unit 301 is an interface for displaying information to users of the support terminal 3, such as doctors, nurses, and caregivers, and for receiving various operations from them. It is configured to include input devices such as a keyboard and mouse, and display devices such as an LCD display.

[0060] The recovery guidance receiving unit 302 receives recovery guidance from the maintenance device 2 via the wireless interface unit 200.

[0061] The recovery guidance display unit 303 displays a recovery guidance display screen 310 on the man-machine interface unit 301, which displays the recovery guidance received by the recovery guidance receiving unit 302.

[0062] Figure 10 shows an example of the recovery guidance display screen 310.

[0063] The recovery guidance display screen 310 includes an anomaly detection alert display field 311 and a recovery guidance display field 312.

[0064] The abnormality detection alert display field 311 displays the device ID of the call device 91 in which the abnormality was detected and the details of the abnormality, as included in the recovery guidance received by the recovery guidance receiving unit 302. The recovery guidance display field 312 displays the recovery procedure 313 included in the recovery guidance received by the recovery guidance receiving unit 302, and if the recovery guidance includes a comment 314, this comment 314 is also displayed.

[0065] Doctors, nurses, caregivers, and other users of the support terminal 3 can recognize which call device 91 is malfunctioning and perform the necessary repair work by checking the information displayed on the recovery guidance screen 310, even without specialized knowledge of the maintenance and management of the call devices 91 of the nurse call system 7.

[0066] The recovery guidance storage unit 304 stores the recovery guidance (anomaly detection notification, recovery procedure, and comments) received by the recovery guidance receiving unit 302.

[0067] The execution result receiving unit 305 receives the results of the recovery procedure from the user via the man-machine interface unit 301. For example, it displays the recovery guidance stored in the recovery guidance storage unit 304 as a list on the man-machine interface unit 301 and accepts the user's selection of one of the recovery guidances. Then, it displays a list of the names of the recovery procedures included in the selected recovery guidance and accepts the user's selection of the names of one or more recovery procedures that have been performed, as well as the execution result (recovery successful, recovery failed, etc.) for each performed recovery procedure.

[0068] The implementation result notification unit 306 then creates an implementation result notification that includes the notification ID of the anomaly detection notification included in the recovery guidance specified by the implementation result reception unit 305, and a list of correspondence information between the procedure name of the recovery procedure received by the implementation result reception unit 305 and its implementation result, and transmits this implementation result notification to the maintenance terminal 2 via the network interface unit 300.

[0069] The functional configuration of the support terminal 3 shown in Figure 9 is realized as a process in a general-purpose computer such as a PC, which is equipped with a CPU, memory, auxiliary storage device such as an SSD, and a communication device such as a NIC, by the CPU loading a predetermined program from the auxiliary storage device into memory and executing it.

[0070] Figure 11 is a flowchart illustrating the operation of the support terminal 3.

[0071] When the recovery guidance receiving unit 302 receives recovery guidance from the maintenance terminal 2 via the network interface unit 300 (YES in S300), it registers this recovery guidance in the recovery guidance storage unit 304. The recovery guidance display unit 303 also displays the recovery guidance display screen 310 on the man-machine interface unit 301 (S301). This recovery guidance display screen 310 displays the recovery guidance received from the maintenance terminal 2 (see Figure 10).

[0072] Furthermore, when the implementation result receiving unit 305 receives a transmission instruction for implementation result notification from the user via the man-machine interface unit 201 (YES in S302), it displays the recovery guidance stored in the recovery guidance storage unit 304 as a list on the man-machine interface unit 301 and accepts the user's selection of one of the recovery guidance (S303). Then, it displays a list of the procedure names of the recovery procedures included in the selected recovery guidance and accepts the user's selection of the procedure names of one or more recovery procedures that have been performed (S304), and accepts the input of the implementation result for each recovery procedure that has been performed (S305). The implementation result notification unit 306 then creates an implementation result notification that includes the notification ID of the anomaly detection notification included in the selected recovery guidance, a list of correspondence information between the procedure name of the selected recovery procedure and the input implementation result, and sends this implementation result notification to the maintenance terminal 2 via the network interface unit 300 (S306).

[0073] Next, we will describe the main unit 8 that constitutes the nurse call system 7.

[0074] Furthermore, the calling device 91 can utilize an existing calling device that has the function of returning a status confirmation response containing information about its own operating status in response to status confirmation requests sent periodically from the main unit 8, so a detailed explanation of this will be omitted.

[0075] Figure 12 is a schematic functional configuration diagram of the main unit 8.

[0076] As shown in the figure, the main unit 8 includes a network interface unit 800, a call control unit 801, a relay processing unit 802, a terminal information storage unit 803, a status monitoring unit 804, and an abnormality detection notification unit 805.

[0077] The network interface unit 800 is an interface for connecting to LAN92.

[0078] The call control unit 801 establishes and releases communication paths between the calling device 91 and the telephone 90, and between the maintenance terminal 2 and the relay device 4, in accordance with a call control protocol such as SIP (Session Initiation Protocol).

[0079] The relay processing unit 802 relays communication between the call device 91 and the telephone 90, and between the maintenance terminal 2 and the relay device 4, via the communication path established by the call control unit 801, in accordance with a transmission protocol such as RTP (Real-time Transport Protocol).

[0080] The terminal information storage unit 803 stores terminal information, including device ID, number information, and address information, for each of the telephones 90, call devices 91, and relay devices 4 that are connected to the main unit 8.

[0081] The status monitoring unit 804 periodically sends a status confirmation request to each call device 91 identified by the terminal information stored in the terminal information storage unit 803, and monitors the status of each call device 91 by receiving a status confirmation response in return. If a timeout occurs after a predetermined period of time without receiving a status confirmation response from a call device 91, if a status confirmation response is received from a call device 91 with a delay beyond the standard time, or if the status confirmation response received from a call device 91 contains an error message indicating an abnormal operating state such as emergency battery operation, the status monitoring unit 804 determines that the operating state of the call device 91 is abnormal and detects the abnormality of that call device 91.

[0082] Then, when the status monitoring unit 804 detects an abnormality in the call device 91, the abnormality detection notification unit 805 sends an abnormality detection notification to the maintenance terminal 2 via the network interface unit 800. This abnormality detection notification includes the device ID of the call device 91 in which the abnormality was detected, the details of the abnormality, and the notification ID assigned to this abnormality detection notification.

[0083] The functional configuration of the main unit 8 shown in Figure 12 can be implemented in hardware using integrated logic ICs such as ASICs (Application Specific Integrated Circuits) and FPGAs (Field Programmable Gate Arrays), or in software using computers such as DSPs (Digital Signal Processors). Alternatively, it can be implemented as a process in a general-purpose computer such as a PC, which is equipped with a CPU, memory, auxiliary storage devices such as HDDs (Hard Disk Drives) and SSDs, and communication devices such as NICs, by having the CPU load a predetermined program from the auxiliary storage device into memory and execute it.

[0084] Figure 13 is a flowchart illustrating the status monitoring operation of the main unit 8.

[0085] This process is performed for each calling device 91 housed in the main unit 8.

[0086] When the periodic monitoring timing arrives (S400), the status monitoring unit 804 sends a status confirmation request to the call device 91 via the network interface unit 800 (S401), and waits for a status confirmation response to be sent from the call device 91 (S402).

[0087] Then, if the call device 91 does not send a status confirmation response (NO in S402) and a timeout occurs after a predetermined period of time (YES in S403), the status monitoring unit 804 reads the device ID of the call device 91 from the terminal information storage unit 803 and passes it to the abnormality detection notification unit 805 along with the abnormality content "no response". In response, the abnormality detection notification unit 805 sends an abnormality detection notification to the maintenance terminal 2 via the network interface unit 800 (S406). This abnormality detection notification includes the notification ID assigned to this abnormality detection notification, the device ID received from the status monitoring unit 804, and the abnormality content "no response".

[0088] Furthermore, if the status confirmation response is received from the call device 91 with a delay from the standard time (YES in S402, YES in S404), the status monitoring unit 804 reads the device ID of the call device 91 from the terminal information storage unit 803 and passes it to the abnormality detection notification unit 805 along with the abnormality description "response delay". In response, the abnormality detection notification unit 805 sends an abnormality detection notification to the maintenance terminal 2 via the network interface unit 800 (S406). This abnormality detection notification includes the notification ID assigned to this abnormality detection notification, the device ID received from the status monitoring unit 804, and the abnormality description "response delay".

[0089] Furthermore, if a status confirmation response is received from the call device 91 within the standard time (YES in S402, NO in S404), but this status confirmation response includes an error message (YES in S405), the status monitoring unit 804 reads the device ID of the call device 91 from the terminal information storage unit 803 and passes it to the anomaly detection notification unit 805 along with the error message. In response, the anomaly detection notification unit 805 sends an anomaly detection notification to the maintenance terminal 2 via the network interface unit 800 (S406). This anomaly detection notification includes the notification ID assigned to this anomaly detection notification, the device ID received from the status monitoring unit 804, and an error message as the content of the anomaly.

[0090] The first embodiment of the present invention has been described above.

[0091] In this embodiment, by installing a support terminal 3 at the waiting area (nurse center, etc.) of the users of the nurse call system 7 (doctors, nurses, caregivers, etc.), if an abnormality occurs in the call device 91, the users of the nurse call system 7 can quickly recognize the fact that an abnormality has occurred in the call device 91, along with appropriate recovery procedures, through the output from the support terminal 3.

[0092] Furthermore, using the maintenance terminal 2, the maintenance administrator can notify the support terminal 3 of the appropriate recovery procedure by selecting the most suitable recovery procedure for the call device 91 that detected the abnormality, based on the device ID and the nature of the abnormality of the call device 91 that detected the abnormality, from among several pre-prepared recovery procedures. This allows the maintenance administrator to present the appropriate recovery procedure to the user with simple operations for abnormalities that the user can handle themselves. This reduces the burden on the maintenance administrator. For example, if the nature of the abnormality is the error message "Emergency battery power," the recovery procedure "Check call device power" is selected, and if the nature of the abnormality is "Response delay," the recovery procedure "Restart call device" is selected. Also, if an abnormality detection notification with the nature of the abnormality being "No response" has been sent from the main unit 8 to the maintenance terminal 2 for a single call device 91, the recovery procedure "Check call device power" is selected, and if it has been sent from the main unit 8 to the maintenance terminal 2 for multiple call devices 91, the recovery procedures "Check wireless connection" and / or "Check main unit settings" are selected. This allows maintenance managers to assist users of the nurse call system 7 in restoring the call device 91 without having to spend time explaining typical recovery procedures, and enables the assisted users of the nurse call system 7 to deal with the malfunction of the call device 91 themselves.

[0093] Therefore, according to this embodiment, even users such as doctors, nurses, and caregivers who do not have specialized knowledge regarding the maintenance and management of the call device 91 of the nurse call system 7 can be supported so that they can restore the call device 91 when a malfunction occurs.

[0094] Furthermore, in this embodiment, the support terminal 3 receives from the user of the nurse call system 7 the recovery procedure performed in response to the abnormality of the call device 91 and the result of its implementation, along with the device ID of the call device 91, and transmits an implementation result notification, including the device ID, the implemented recovery procedure, and the result of its implementation, to the maintenance terminal 2. The maintenance terminal 2 then displays the implementation result notification received from the support terminal 3. As a result, the maintenance manager can find out the result of the recovery procedure they proposed for the call device 91 that detected the abnormality, thereby understanding the current state of the call device 91 and utilizing the knowledge gained for future maintenance and management.

[0095] Furthermore, in this embodiment, the main unit 8 monitors the status of the call device 91, and if it detects an abnormality in the call device 91, it sends an abnormality detection notification to the maintenance terminal 2, which includes the device ID of the call device 91 and the details of the detected abnormality. Therefore, the maintenance manager can quickly become aware of any abnormalities in the call device 91.

[0096] [Second Embodiment] Next, a second embodiment of the present invention will be described.

[0097] Figure 14 is a diagram showing the schematic configuration of the call device recovery support system 1' according to this embodiment, along with the schematic configuration of the nurse call system 7' that is the target of the recovery support.

[0098] Here, components having the same function as those in the first embodiment of the present invention shown in Figure 1 are denoted by the same reference numerals.

[0099] As shown in the figure, the call device recovery support system 1' according to this embodiment assists in the recovery of the call device 91 of the nurse call system 7' from an abnormality.

[0100] The difference between the nurse call system 7' being restored and the nurse call system 7 shown in Figure 1 is that the main unit 8' has been replaced with a main unit 8'. The other configurations are the same as those of the nurse call system 7 shown in Figure 1.

[0101] Furthermore, the differences between the call device recovery support system 1' and the call device recovery support system 1 shown in Figure 1 are that maintenance terminals 2' and support terminals 3' have been replaced with maintenance terminals 2' and support terminals 3', and that an inquiry terminal 5 has been newly added. The inquiry terminal 5 is a terminal carried by the user of the nurse call system 7' (doctors, nurses, caregivers, etc.), and it sends an inquiry message via WAN 94 to the AI ​​server 6 that provides AI (Artificial Intelligence) services to inquire about the recovery procedure, and obtains the recovery procedure from the AI ​​server 6.

[0102] Figure 15 is a sequence diagram illustrating the operation of the call device recovery support system 1' according to this embodiment.

[0103] The main unit 8' periodically sends a status check request to each of the call devices 91 and receives a status check response containing information about the operating status of each call device 91, thereby monitoring the status of each call device 91 (S150). When it detects an abnormality in any of the call devices 91 (S151), it sends an abnormality detection notification to the relay device 4 (S152). This abnormality detection notification includes the device ID of the call device 91 in which the abnormality was detected, the details of the abnormality (no response, delayed response, and error messages included in the status check response, etc.), and the notification ID assigned to this abnormality detection notification. The relay device 4 then relays the abnormality detection notification received from the main unit 8' to the support terminal 3' (153), and the support terminal 3' displays the device ID of the call device 91 in which the abnormality was detected and the details of the abnormality included in the abnormality detection notification received from the relay device 4 (S154).

[0104] Next, the user of the nurse call system 7' confirms the device ID and details of the abnormality of the call device 91 displayed on the support terminal 3', and then performs an inquiry operation on the inquiry terminal 5 that the user is carrying. In response, the inquiry terminal 5 displays a question screen that asks for the items necessary to create an inquiry statement to ask the AI ​​server 6 for the recovery procedure of the abnormal call device 91. As will be described later, the items to be answered on this question screen include the device ID and details of the abnormality of the call device 91. The system then accepts the answer to the question from the user of the nurse call system 7' (S155).

[0105] Then, when the inquiry terminal 5 receives the device ID of the call device 91 in which an abnormality has been detected and the details of the abnormality from the user of the nurse call system 7' via the question screen, it uses this device ID and details of the abnormality, along with the configuration information of the nurse call system 7' that has been stored in advance, to create an inquiry statement that asks the AI ​​server 6 for the recovery procedure for the call device 91 in which an abnormality has been detected. Then, it sends the created inquiry statement to the AI ​​server 6 (S156). Next, the inquiry terminal 5 receives the recovery procedure from the AI ​​server 6 and displays it (S157).

[0106] As described above, users of the nurse call system 7' can learn about the call device 91 in which an abnormality has been detected, along with the details of the abnormality, by checking the abnormality detection notification displayed on the support terminal 3'. Furthermore, by checking the recovery procedure displayed on the inquiry terminal 5, they can learn the appropriate recovery procedure to restore the call device 91 in which an abnormality has been detected.

[0107] Subsequently, when the support terminal 3' receives the results of the recovery procedure from the user of the nurse call system 7', along with the designation of an anomaly detection notification (S158), it sends an implementation result notification to the relay device 4, which includes the name of the recovery procedure performed, the corresponding information of the procedure's implementation result, and the designated anomaly detection notification, with the destination being the maintenance terminal 2' (S159). In response, the relay device 4 relays the implementation result notification received from the support terminal 3' to the main unit 8' (S160), and the main unit 8' sends the implementation result notification received from the relay device 4 to the maintenance terminal 2' (S161). The maintenance terminal 2' then displays the anomaly detection notification included in the implementation result notification received from the main unit 8, the recovery procedure performed, and its implementation result (S162).

[0108] Next, the maintenance terminal 2', support terminal 3', and inquiry terminal 5 that constitute the call device recovery support system 1' according to this embodiment will be described.

[0109] First, let me explain maintenance terminal 2'.

[0110] Figure 16 is a schematic diagram of the functional configuration of maintenance terminal 2'.

[0111] As shown in the figure, the maintenance terminal 2' includes a wireless interface unit 250, a human-machine interface unit 251, a result receiving unit 252, and a result display unit 253.

[0112] The wireless interface unit 250 is an interface for connecting to the WAN 94 via a wireless base station, access point, etc. (not shown).

[0113] The man-machine interface unit 251 is an interface for displaying information to the maintenance administrator, who is the user of the maintenance terminal 2', and is configured to include an output device such as a liquid crystal display.

[0114] The result receiving unit 252 receives the implementation result notification from the support terminal 3' via the wireless interface unit 250.

[0115] The result display unit 253 then displays the anomaly detection notification, the implemented recovery procedure, and its implementation results, which are included in the implementation result notification received by the result receiving unit 252, on the man-machine interface unit 251.

[0116] The functional configuration of maintenance terminal 2' shown in Figure 16 is similar to that of maintenance terminal 2 shown in Figure 4. In a general-purpose computer such as a smartphone or tablet PC, equipped with a CPU, memory, auxiliary storage device such as an SSD, and a communication device such as a wireless NIC, the CPU loads a predetermined program from the auxiliary storage device into memory and executes it, thereby realizing it as a process.

[0117] Figure 17 is a flowchart illustrating the operation of maintenance terminal 2'.

[0118] When the result receiving unit 252 receives an implementation result notification from the support terminal 3' via the wireless interface unit 250 (YES in S250), it passes the received implementation result notification to the result display unit 253. In response, the result display unit 253 displays the device ID of the call device 91 in which the abnormality was detected, the details of the abnormality, the recovery procedure performed, and the results thereof, which are included in the implementation result notification received from the result receiving unit 252, on the man-machine interface unit 251 (S251).

[0119] Next, I will explain the support terminal 3'.

[0120] Figure 18 is a schematic diagram of the functional configuration of support terminal 3'.

[0121] As shown in the figure, the support terminal 3' includes a network interface unit 350, a human-machine interface unit 351, a notification receiving unit 352, a notification display unit 353, an anomaly detection notification storage unit 354, an implementation result receiving unit 355, and an implementation result notification unit 356.

[0122] The network interface unit 350 is an interface for connecting to the relay device 4 via LAN 92.

[0123] The human-machine interface unit 351 is an interface for displaying information to users of the support terminal 3', such as doctors, nurses, and caregivers, and for receiving various operations from them. It is configured to include input devices such as a keyboard and mouse, and display devices such as an LCD display.

[0124] The notification receiving unit 352 receives an anomaly detection notification from the main unit 8' via the network interface unit 350.

[0125] The notification display unit 353 displays an anomaly detection notification display screen on the man-machine interface unit 351 to display the anomaly detection notification received by the notification receiving unit 352. Here, the anomaly detection notification display screen that the notification display unit 353 displays on the man-machine interface unit 351 is, for example, the anomaly detection notification display screen 210 shown in Figure 5(A) with the button 213 omitted.

[0126] The anomaly detection notification storage unit 354 stores the anomaly detection notifications received by the notification receiving unit 352. Here, the record of the anomaly detection notification stored in the anomaly detection notification storage unit 354 is obtained by omitting field 2044 from the anomaly detection notification record 2040 shown in Figure 6.

[0127] The execution result receiving unit 355 receives the results of the recovery procedure from the user via the man-machine interface unit 351. For example, it displays a list of anomaly detection notifications stored in the anomaly detection notification storage unit 354 on the man-machine interface unit 351 and accepts the user to specify one of the anomaly detection notifications. Then, it accepts input from the user of the results of each recovery procedure performed by the user in response to the anomaly of the call device 91 identified by the specified anomaly detection notification (recovery successful, recovery failed, etc.).

[0128] The implementation result notification unit 356 then creates an implementation result notification that includes the anomaly detection notification specified by the user, the recovery procedure entered by the user, and corresponding information regarding the implementation result, and transmits this implementation result notification to the maintenance terminal 2' via the network interface unit 350.

[0129] The functional configuration of the support terminal 3' shown in Figure 18 is similar to that of the support terminal 3 shown in Figure 9. It is implemented as a process in a general-purpose computer such as a PC, which is equipped with a CPU, memory, auxiliary storage devices such as an HDD or SSD, and a communication device such as a NIC, by the CPU loading a predetermined program from the auxiliary storage device into memory and executing it.

[0130] Figure 19 is a flowchart illustrating the operation of the support terminal 3'.

[0131] When the notification receiving unit 352 receives an anomaly detection notification from the main unit 8' via the network interface unit 350 (YES in S350), it registers this anomaly detection notification in the anomaly detection notification storage unit 354. The notification display unit 353 also displays an anomaly detection notification display screen on the man-machine interface unit 351 and displays the anomaly detection notification on this anomaly detection notification display screen (S351).

[0132] Furthermore, when the implementation result receiving unit 355 receives a transmission instruction for an implementation result notification from the user via the man-machine interface unit 351 (YES in S352), it displays the anomaly detection notifications stored in the anomaly detection notification storage unit 354 as a list on the man-machine interface unit 351 and accepts the user to specify one of the anomaly detection notifications (S353). Then, it accepts input from the user via the man-machine interface unit 351 of one or more recovery procedures that have been performed (S354), and accepts input of the implementation result for each recovery procedure that has been performed (S355). The implementation result notification unit 356 then creates an implementation result notification that includes the specified anomaly detection notification and the corresponding information of the input recovery procedure and its implementation result, and sends this implementation result notification to the maintenance terminal 2' via the network interface unit 350 (S356).

[0133] Next, we will explain inquiry terminal 5.

[0134] Figure 20 is a schematic diagram of the functional configuration of inquiry terminal 5.

[0135] As shown in the figure, the inquiry terminal 5 includes a wireless interface unit 500, a human-machine interface unit 501, a system configuration information storage unit 502, a question display / answer reception unit 503, an inquiry text template storage unit 504, an inquiry text creation unit 505, a recovery procedure acquisition unit 506, and a recovery procedure display unit 507.

[0136] The wireless interface unit 500 is an interface for connecting to the WAN 94 via a wireless base station, access point, etc. (not shown).

[0137] The man-machine interface unit 501 is an interface for displaying information to users (doctors, nurses, caregivers, etc.) of the nurse call system 7' and for receiving various operations from users, and is configured with input / output devices such as a liquid crystal display with touch panel functionality.

[0138] The system configuration information storage unit 502 stores configuration information of the nurse call system 7' (information about the main unit 8', information about the calling device 91, connection information between the main unit 8' and the calling device 91, etc.).

[0139] The question display and answer reception unit 503, in accordance with the inquiry operation received from the user of the nurse call system 7' via the man-machine interface unit 501, displays a question screen 510 on the man-machine interface unit 501 for creating an inquiry message asking for the recovery procedure of the call device 91 in which an abnormality has been detected, and receives an answer from the user of the nurse call system 7' on the question screen 510.

[0140] Figure 21 shows an example of a question screen 510 for creating an inquiry.

[0141] As shown in the diagram, the question screen 510 for creating an inquiry statement displays a selection field 511 for the user to select their job title from a checklist, an input field 512 for the user to enter the device ID (device ID of the call device 91 in which the anomaly was detected) included in the anomaly detection notification displayed on the support terminal 3', an input field 513 for the user to enter the details of the anomaly included in the anomaly detection notification, an input field 514 for the user to enter comments as needed, and a confirm button 515 for the user to confirm the answer.

[0142] The query template storage unit 504 stores a template query for inquiring with the AI ​​server 6 about the recovery procedure for the call device 91 in which an abnormality has been detected.

[0143] The inquiry statement creation unit 505, based on the answers received by the question display / answer reception unit 503 and the configuration information of the nurse call system 7' stored in the system configuration information storage unit 502, creates an inquiry statement from the inquiry statement template storage unit 504 to inquire with the AI ​​server 6 about the recovery procedure for the call device 91 in which an abnormality has been detected.

[0144] For example, if a template inquiry is stored in the inquiry template storage unit 504, such as "I work in [job title]. An error has occurred in the nurse call system's paging device. The error is [error details]. [Another paging device is connected] [No other paging devices are connected] to the access point that wirelessly connects to the paging device where the error occurred. Please tell me how to recover the paging device. [Comment]," then the strings [job title], [error details], and [comment] in the text are replaced with the user's job title, the error details of the paging device 91, and the comment received from the user via the question screen 510 for creating the inquiry. Furthermore, the system refers to the device ID (device ID of the call device 91 in which an abnormality was detected) received from the user via the question screen 510 for creating the inquiry statement, and the configuration information of the nurse call system 7' stored in the system configuration information storage unit 502, to determine the connection status of the access point wirelessly connected to the call device 91 in which an abnormality was detected. Based on this determination, it deletes either "[Another call device is connected]" or "[No other call device is connected]". This creates the inquiry statement.

[0145] The recovery procedure acquisition unit 506 transmits an inquiry statement created by the inquiry statement creation unit 505 to the AI ​​server 6 via the wireless interface unit 500, and acquires the recovery procedure for the call device 91 in which an abnormality was detected from the AI ​​server 6.

[0146] The recovery procedure display unit 507 then displays the recovery procedure acquired by the recovery procedure acquisition unit 506 on the man-machine interface unit 501.

[0147] The functional configuration of the inquiry terminal 5 shown in Figure 20 is realized as a process in a general-purpose computer such as a smartphone or tablet PC, which is equipped with a CPU, memory, auxiliary storage device such as an SSD, and a communication device such as a wireless NIC, by the CPU loading a predetermined program from the auxiliary storage device into memory and executing it.

[0148] Figure 22 is a flowchart illustrating the operation of the inquiry terminal 5.

[0149] This flow is initiated when the man-machine interface unit 501 receives an inquiry operation from a user of the nurse call system 7' who has confirmed the anomaly detection notification displayed on the support terminal 3'.

[0150] First, the question display / answer reception unit 503 displays a question screen 510 on the man-machine interface unit 501 for creating an inquiry to ask about the recovery procedure for the call device 91 in which an abnormality has been detected, and receives answers from the user of the nurse call system 7' regarding the user's occupation and the contents of the abnormality detection notification displayed on the support terminal 3' (device ID of the call device 91 in which the abnormality was detected and the details of the abnormality) (S400).

[0151] Next, the inquiry statement creation unit 505, based on the answers received by the question display / answer reception unit 503 and the configuration information of the nurse call system 7' stored in the system configuration information storage unit 502, creates an inquiry statement from the inquiry statement template storage unit 504 to inquire with the AI ​​server 6 about the recovery procedure for the call device 91 in which an abnormality has been detected (S401).

[0152] Then, the recovery procedure acquisition unit 506 transmits the inquiry statement created by the inquiry statement creation unit 505 to the AI ​​server 6 via the wireless interface unit 500, and acquires the recovery procedure for the call device 91 in which an abnormality was detected from the AI ​​server 6 (S402).

[0153] Then, the recovery procedure display unit 507 displays the recovery procedure acquired by the recovery procedure acquisition unit 506 on the man-machine interface unit 501 (S403).

[0154] Next, we will describe the main unit 8' that constitutes the nurse call system 7'.

[0155] The main unit 8' according to this embodiment differs from the main unit 8 according to the first embodiment shown in Figure 12 in that the main unit 8 according to the first embodiment sends an anomaly detection notification to the maintenance terminal 2, whereas the main unit 8' according to this embodiment sends an anomaly detection notification to the support terminal 3'. Otherwise, it is the same as the main unit 8 according to the first embodiment.

[0156] The second embodiment of the present invention has been described above.

[0157] In this embodiment, similar to the first embodiment of the present invention, by installing a support terminal 3' at the waiting area (nurse center, etc.) of the user of the nurse call system 7' (doctor, nurse, caregiver, etc.), if an abnormality occurs in the call device 91, the user of the nurse call system 7' can quickly grasp the fact that an abnormality has occurred in the call device 91 through the output from the support terminal 3'.

[0158] Furthermore, by referring to the anomaly detection notification displayed on the support terminal 3' and entering an answer on the question screen 510 displayed on the inquiry terminal 5, the user can have the inquiry terminal 5 create an inquiry message asking for the recovery procedure for the call device 91 where the anomaly was detected and send it to the AI ​​server 6, from which the recovery procedure can be obtained. This improves convenience because, even if the user cannot contact the maintenance manager, they can obtain the appropriate recovery procedure for anomalies they can handle themselves with just a simple answer input. For example, the inquiry terminal 5 stores a template text for inquiries, such as: "I work in the [job category]. An error has occurred in the nurse call system's call device. The error is [error description]. [Another call device is connected] [No other call devices are connected] to the access point that wirelessly connects to the call device where the error occurred. Please tell me how to recover the call device. [Comment]." The system then replaces the bracketed strings [job category], [error description], and [comment] in this text with the user's job category, the error description of the call device 91, and the comment received from the user via the question screen 510. The system also refers to the device ID of the call device 91 where the error was detected and the pre-stored configuration information of the nurse call system 7' to determine the connection status of the access point that wirelessly connects to the call device 91 where the error occurred. Based on this determination, the system deletes either [Another call device is connected] or [No other call devices are connected]. This creates an inquiry and sends it to the AI ​​server 6 to obtain the recovery procedure. This allows users such as doctors, nurses, and caregivers who do not have specialized knowledge of the nurse call system 7' to make appropriate inquiries to the AI ​​server 6 and obtain the recovery procedure for the call device 91 in which an abnormality has been detected.

[0159] Therefore, according to this embodiment, even users such as doctors, nurses, and caregivers who do not have specialized knowledge regarding the maintenance and management of the call device 91 of the nurse call system 7' can be assisted in restoring the call device 91 when an abnormality occurs.

[0160] Furthermore, in this embodiment, the support terminal 3' receives from the user of the nurse call system 7' the recovery procedure performed in response to the abnormality of the call device 91 and its results, along with the designation of an abnormality detection notification to inform of this abnormality, and transmits an implementation result notification, including the abnormality detection notification, recovery procedure, and implementation result, to the maintenance terminal 2'. The maintenance terminal 2' then displays the implementation result notification received from the support terminal 3'. As a result, the maintenance manager can know the call device 91 in which the abnormality was detected, the recovery procedure performed in response to the abnormality of the call device 91, and its results, thereby understanding the current state of the call device 91 and utilizing the knowledge gained for future maintenance and management.

[0161] Furthermore, in this embodiment, the main unit 8' monitors the status of the call device 91, and if it detects an abnormality in the call device 91, it sends an abnormality detection notification to the support terminal 3', which includes the device ID of the call device 91 and the details of the detected abnormality. Therefore, users of the nurse call system 7' can quickly become aware of any abnormalities in the call device 91.

[0162] It should be noted that the present invention is not limited to the embodiments described above, and numerous modifications are possible within the scope of its essence.

[0163] For example, in each of the embodiments described above, the main units 8 and 8' accommodate the support terminals 3 and 3' via the relay device 4, but the present invention is not limited to this. The main units 8 and 8' may directly accommodate the support terminals 3 and 3'. In this case, the relay device 4 is not necessary.

[0164] Furthermore, in each of the above embodiments, the support terminals 3 and 3' are wired connections to the LAN 92, but they may also be connected to the LAN 92 via a wireless connection with the access point 93. Also, the calling device 91 is connected to the LAN 92 via a wireless connection with the access point 93, but it may also be connected to the LAN 92 via a wired connection. [Explanation of Symbols]

[0165] 1, 1': Calling device recovery support system 2, 2': Maintenance terminal 3, 3': Support terminal 4: Relay device 5: Inquiry terminal 6: AI server 7, 7': Nurse call system 8, 8´: Main device 90: Telephone 91: Calling device 92: LAN 93:AP 94:WAN 95:GW 200, 250, 500: Wireless interface section 201, 251, 301, 351, 501: Human-machine interface section 202, 352: Notification receiving unit; 203, 353: Notification display unit 204, 354: Anomaly detection notification storage unit; 205: Recovery procedure storage unit 206: Procedure Selection Unit 207: Recovery Guidance Transmission Unit 208, 252: Result receiving unit 209, 253: Result display unit 300, 350, 800: Network Interface Unit 302: Recovery guidance receiving unit 303: Recovery guidance display unit 304: Recovery guidance storage unit; 305, 355: Implementation result reception unit 306, 356: Implementation result notification unit; 502: System configuration information storage unit 503: Question display / answer reception unit 504: Inquiry message template storage unit 505: Inquiry Text Creation Department 506: Recovery Procedure Acquisition Department 507: Recovery procedure display unit 801: Call control unit 802: Relay processing unit 803: Terminal Information Storage Unit 804: Status Monitoring Unit 805: Anomaly Detection Notification Unit

Claims

1. A call device recovery support system that assists in the recovery of a nurse call system's call device from malfunction, Equipped with a maintenance terminal and a support terminal, The aforementioned maintenance terminal is Notification receiving means for receiving abnormality detection notifications from the main unit of the nurse call system, the main unit of the nurse call system is connected to the notification receiving means, A procedure selection means that displays the identification information of the calling device and the details of the abnormality included in the abnormality detection notification received by the notification receiving means, and accepts the selection of a desired recovery procedure from among a plurality of recovery procedures stored in advance, The system includes a procedure transmission means that transmits the recovery procedure selected by the procedure selection means, along with the anomaly detection notification, to the support terminal. The aforementioned support terminal is A procedure receiving means for receiving the recovery procedure and the anomaly detection notification from the maintenance terminal, The procedure display means displays the recovery procedure received by the procedure receiving means together with the identification information of the calling device and the details of the abnormality included in the abnormality detection notification received by the procedure receiving means. A call device recovery support system characterized by the following features.

2. A call device recovery support system according to claim 1, The aforementioned support terminal is An implementation result receiving means that receives the recovery procedure and its results, along with the identification information of the call device, for the call device in which an abnormality was detected. The system further includes an implementation result notification means that transmits an implementation result notification to the maintenance terminal, which includes the recovery procedure, implementation result, and identification information of the calling device, received by the implementation result receiving means. The aforementioned maintenance terminal is The system further includes an implementation result display means for displaying the recovery procedure, implementation result, and identification information of the calling device included in the implementation result notification received from the support terminal. A call device recovery support system characterized by the following features.

3. A call device recovery support system according to claim 1 or 2, The main unit further comprises the above-mentioned main unit, The main device is A status monitoring means for monitoring the status of the calling device, The system includes an abnormality detection notification means that, when the status monitoring means detects an abnormality in the call device, transmits the abnormality detection notification, which includes the identification information of the call device and the details of the detected abnormality, to the maintenance terminal. A call device recovery support system characterized by the following features.

4. A call device recovery support system that assists in the recovery of a nurse call system's call device from malfunction, Equipped with a support terminal and an inquiry terminal, The aforementioned support terminal is Notification receiving means for receiving abnormality detection notifications from the main unit of the nurse call system, the main unit of the nurse call system is connected to the notification receiving means, The system includes a notification display means that displays the identification information of the calling device and the details of the abnormality included in the abnormality detection notification received by the notification receiving means, The aforementioned inquiry terminal is A questioning means that displays a predetermined question regarding the abnormality of the calling device displayed on the support terminal and accepts answers to said question, An inquiry statement creation means creates an inquiry statement that inquires about the recovery procedure for the call device in which an abnormality has been detected, using the answers received by the aforementioned questioning means and the configuration information of the nurse call system that is stored in advance. A procedure acquisition means that transmits the query statement created by the query statement creation means to a predetermined AI server that provides AI (Artificial Intelligence) services, and obtains the recovery procedure from the AI ​​server, The procedure includes a procedure display means for displaying the recovery procedure acquired by the procedure acquisition means. A call device recovery support system characterized by the following features.

5. A call device recovery support system according to claim 4, It also has a maintenance terminal, The aforementioned support terminal is An implementation result receiving means that receives the recovery procedure and its results, along with the identification information of the call device, for the call device in which an abnormality was detected. The system further includes an implementation result notification means that transmits an implementation result notification to the maintenance terminal, which includes the recovery procedure, implementation result, and identification information of the calling device, received by the implementation result receiving means. The aforementioned maintenance terminal is The system has an implementation result display means that displays the recovery procedure, implementation result, and identification information of the calling device included in the implementation result notification received from the support terminal. A call device recovery support system characterized by the following features.

6. A call device recovery support system according to claim 4 or 5, The main unit further comprises the above-mentioned main unit, The main device is A status monitoring means for monitoring the status of the calling device, The system includes an abnormality detection notification means that, when the status monitoring means detects an abnormality in the calling device, transmits an abnormality detection notification to the support terminal, which includes the identification information of the calling device and the details of the detected abnormality. A call device recovery support system characterized by the following features.

7. A program for a nurse call system recovery support system that assists in recovering from malfunctions in the call device of a nurse call system, which enables a computer to function as a maintenance terminal, Notification receiving means for receiving abnormality detection notifications from the main unit of the nurse call system, the main unit of the nurse call system, A procedure selection means that displays the identification information of the calling device and the details of the abnormality included in the abnormality detection notification received by the notification receiving means, and accepts the selection of a desired recovery procedure from a plurality of recovery procedures stored in advance, and The computer functions as a procedure transmission means, which transmits the recovery procedure selected by the procedure selection means, along with the anomaly detection notification, to the support terminal of the nurse call system. A program characterized by the following features.

8. A program for a nurse call system recovery support system that assists in recovering from malfunctions in the call device of a nurse call system, which enables a computer to function as an inquiry terminal, A questioning means that displays a predetermined question regarding an abnormality of the calling device on the support terminal of the nurse call system and receives an answer to the said question. An inquiry statement creation means creates an inquiry statement that inquires about the procedure for recovering from a malfunction of the call device, using the answers received by the aforementioned questioning means and the nurse call system information stored in advance. Procedure acquisition means for sending the query statement created by the query statement creation means to a predetermined AI server that provides AI (Artificial Intelligence) services, and obtaining the recovery procedure from the AI ​​server, and The computer is configured to function as a procedure display means for displaying the recovery procedure acquired by the procedure acquisition means. A program characterized by the following features.

9. A method for assisting in the recovery of a nurse call system's call device from an abnormality, using a maintenance terminal and a support terminal, The aforementioned maintenance terminal is When the main unit of the nurse call system receives an abnormality detection notification for the call device it houses, it displays the identification information of the call device and the details of the abnormality included in the abnormality detection notification, accepts the selection of a desired recovery procedure from among a plurality of pre-stored recovery procedures, and transmits the selected recovery procedure, along with the abnormality detection notification, to the support terminal. The aforementioned support terminal is Upon receiving the recovery procedure and the anomaly detection notification from the maintenance terminal, the recovery procedure will be displayed along with the identification information of the calling device and the details of the anomaly included in the anomaly detection notification. A method for supporting the recovery of a call device, characterized by the following features.

10. A method for assisting in the recovery of a nurse call system's call device from an abnormality, using a support terminal and an inquiry terminal, The aforementioned support terminal is When the main unit of the nurse call system receives an abnormality detection notification from the call device it houses, it displays the identification information of the call device and the details of the abnormality included in the abnormality detection notification. The aforementioned inquiry terminal is The support terminal displays a predetermined question regarding the abnormality of the call device, receives an answer to the question, and uses the received answer and the pre-stored configuration information of the nurse call system to create an inquiry statement asking for the recovery procedure for the call device in which the abnormality was detected. The created inquiry statement is then sent to a predetermined AI server that provides AI (Artificial Intelligence) services, and the recovery procedure is obtained from the AI ​​server and displayed. A method for supporting the recovery of a call device, characterized by the following features.

Images