Management systems and management methods

Abstract

Securely manage residents' schedules. [Solution] The management system 100 manages the schedules of one or more residents of a facility. The management system 100 includes a processor and a storage unit that stores a first identification information that identifies each of the one or more residents, associated with a second identification information that identifies user U of the management system 100. The processor acquires a third identification information that identifies user U who has accessed the management system 100. The processor determines the resident identified by the first identification information associated with the second identification information that matches the third identification information. The processor acquires the available dates for booking events for the determined resident from the schedule managed by the management system 100. The processor outputs the schedule information indicating the available dates to the user terminal 200 used by the accessing user U.

Description

Technical Field

[0001] The present disclosure relates to a management system and a management method. Background Art

[0002] Japanese Patent Laid-Open No. 2005-55989 discloses a hotel guest room reservation system. Prior Art Literature Patent Literature

[0003] Patent Document 1 Japanese Patent Laid-Open No. 2005-55989 Summary of the Invention Problem to be Solved by the Invention

[0004] Generally, in a hotel guest room reservation system, any user who accesses the system can check the room availability. A system that allows anyone to view room availability is not suitable for residential facilities (e.g., nursing care facilities, etc.). Generally, reservations for events (e.g., going out, staying out overnight, visiting, etc.) of residents in residential facilities are made by parties related to the resident (e.g., family members, etc.) on behalf of the resident. If anyone can view a resident's schedule, it is not secure from a security perspective.

[0005] The present disclosure has been made in view of the above problems, and an object thereof is to safely manage the schedules of residents. Means for Solving the Problem

[0006] (1) A management system according to a certain aspect of this disclosure is a system for managing the schedules of one or more residents of a facility. The management system comprises a processor and a storage unit that stores a first identification information that identifies each of the one or more residents, associated with a second identification information that identifies a user of the management system. The processor obtains a third identification information that identifies a user who has accessed the management system. The processor determines the resident identified by the first identification information associated with the second identification information that matches the third identification information. The processor obtains the available dates from the above schedule for which the determined resident can book an event. The processor outputs the schedule information indicating the available dates to a first user terminal used by the accessing user.

[0007] (2) In the management system described in (1) above, an event includes at least one of the following: going out, staying out overnight, and meeting someone.

[0008] (3) In the management system described in (1) above, the processor further outputs to the first user terminal reception information for accepting reservations for events of the determined residents from the accessing user.

[0009] (4) In the management system described in (3) above, an event includes at least one of going out and staying overnight. The reception information includes information for receiving whether the determined resident requires meals.

[0010] (5) In the management system described in (4) above, the processor outputs information regarding the meal requirements of one or more residents to a facility terminal used by the facility staff.

[0011] (6) In the management system described in (3) above, the reception information includes information for receiving instructions on whether or not to disclose reservation information, which indicates the content of the reservation received from the accessing user, to other users identified by a second identification information associated with a first identification information that identifies the resident who has been identified.

[0012] (7) In the management system described in (6) above, after the processor receives an instruction to make the reservation information public to other users, if another user accesses the management system, the processor outputs the reservation information to a second user terminal used by the other user.

[0013] (8) In the management system described in (1) above, an event includes at least one of going out and staying overnight. The available dates do not include dates on which the determined resident has a reservation to go out or stay overnight.

[0014] (9) In the management system described in (1) above, events include visits. Available dates do not include dates on which a visit reservation has been made for the determined resident.

[0015] (10) In the management system described in (1) above, an event includes at least one of the following: going out, staying overnight, and visiting. Available dates do not include dates on which the determined resident has a reservation for going out, staying overnight, or visiting.

[0016] (11) In the management system described in (1) above, the processor updates the schedule when it receives a reservation for an event from a determined resident.

[0017] (12) In the management system described in any one of (1) to (11) above, the facility is a nursing care facility.

[0018] (13) A management method according to another aspect of the present disclosure is a method executed by a computer for managing schedules of one or more residents of a facility. The computer includes a storage unit that stores, in association with each other, first identification information for identifying each of the one or more residents, and second identification information for identifying a user of a management system for managing schedules. The management method includes: acquiring third identification information that identifies a user who has accessed the management system; determining a resident identified by first identification information associated with second identification information that matches the third identification information; acquiring bookable dates, on which an event of the determined resident can be booked, from the schedule; and outputting date information indicating the bookable dates to a first user terminal used by the user who has accessed the system.

[0019] (14) A management program according to another aspect of the present disclosure causes a computer to execute the management method according to (13) above. Effects of the Invention

[0020] According to the present disclosure, schedules of residents can be securely managed. Brief Description of the Drawings

[0021] [Figure 1] FIG. 1 is a diagram showing a system including the management system according to the present embodiment. [Figure 2] FIG. 2 is a diagram showing an example of the facility according to the present embodiment. [Figure 3] FIG. 3 is a diagram showing an example of a configuration of the management system 100. [Figure 4] FIG. 4 is a diagram showing an example of resident information 132. [Figure 5] FIG. 5 is a diagram showing an example of user information 133. [Figure 6] FIG. 6 is a flowchart showing an example of a processing procedure of reception processing according to the present embodiment. [Figure 7] FIG. 7 is a diagram showing a first part of the reception processing. [Figure 8] FIG. 8 is a diagram showing a second part of the reception processing. [Figure 9]This diagram shows the third part of the reception process. [Figure 10] This is a diagram showing the fourth part of the reception process. [Figure 11] This is a diagram showing the fifth part of the reception process. [Figure 12] This is a diagram showing the sixth part of the reception process. [Figure 13] This is a diagram showing the seventh part of the reception process. [Figure 14] This is a diagram showing the eighth part of the reception process. [Figure 15] This is a diagram showing the ninth part of the reception process. [Figure 16] This figure shows an example of a notification screen for reservation information that has been instructed to be made public. [Figure 17] This figure shows an example of a notification screen for reservation information that has not been instructed to be made public. [Figure 18] This figure shows a first example of the screen displayed on the facility terminal 300. [Figure 19] This figure shows a second example of the screen displayed on the facility terminal 300. [Figure 20] This figure shows a third example of the screen displayed on the facility terminal 300. [Modes for carrying out the invention]

[0022] Hereinafter, embodiments and modifications of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals, and their descriptions will not be repeated.

[0023] [Embodiment] Figure 1 shows a system including a management system according to this embodiment. System 1 includes a management system 100, one or more user terminals 200, and one or more facility terminals 300. The management system 100, the one or more user terminals 200, and the one or more facility terminals 300 are connected to a network 500.

[0024] The management system 100 is a system for managing the schedules of one or more residents of a facility. The management system 100 is, for example, composed of a cloud server. The "facility" will be described later with reference to Figure 2. The user terminal 200 is a terminal used by user U of the management system 100. The user terminal 200 includes a display 299.

[0025] User terminal 200a is a user terminal 200 used by user U1 of the management system 100. User terminal 200a is an example of the "first user terminal" in this disclosure.

[0026] User terminal 200b is a user terminal 200 used by user U2 of management system 100. User terminal 200b is an example of a "second user terminal" in this disclosure.

[0027] The facility terminal 300 is a terminal used by the facility staff ST. The facility terminal 300 includes a display 399.

[0028] The number of user terminals 200 included in System 1 is determined according to the number of users U in the management system 100. The number of facility terminals 300 included in System 1 only needs to be one or more.

[0029] Figure 2 shows an example of a facility according to this embodiment. Group X is an example of a "facility" in this disclosure. Group X includes one or more residential care facilities. In this embodiment, Group X includes care facility X1, care facility X2, and care facility X3. Each care facility has one or more residents R. For example, care facility X1 has residents R1, R2, and R3. Care facility X2 has residents R4 and R5. Care facility X3 has residents R6 and R7.

[0030] The management system 100 is configured to allow those associated with each resident R within group X to book events for that resident R. Events include going out, staying overnight, and visits.

[0031] Related parties to resident R include resident R's family, relatives, partner, or any person authorized by resident R or facility staff ST to make event reservations on behalf of resident R. In this embodiment, users U1 and U2 are related parties to resident R1. User U1 is, for example, resident R1's daughter, and user U2 is, for example, resident R1's son.

[0032] User U3 is related to resident R2. Users U4, U5, and U6 are related to resident R3. User U7 is related to resident R4. User U8 is related to resident R5. User U1 is related to resident R6. Users U9 and U10 are related to resident R7. In this way, there is one or more related persons for each resident R.

[0033] User U1 is related to both resident R1 and resident R6. For example, resident R1 is User U1's mother, and resident R6 is User U1's husband's mother.

[0034] Figure 3 shows an example of the configuration of the management system 100. The management system 100 includes a processor 101, memory 102, storage 103, and a communication interface 104.

[0035] The processor 101 includes processing circuitry such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit).

[0036] Memory 102 includes a volatile storage device such as DRAM (Dynamic Random Access Memory) or SRAM (Static Random Access Memory).

[0037] The storage 103 includes, for example, a non-volatile storage device such as an HDD (Hard Disk Drive), an SSD (Solid State Drive), or flash memory. The storage 103 is an example of a “storage unit” in this disclosure. The storage 103 stores a program 131, resident information 132, user information 133, schedule information 134, meal information 135, and screen data 136.

[0038] Program 131 includes a system program, including the OS (Operating System), and a management program for controlling the operation of the management system 100. The processor 101 performs various processes by reading the system program and the management program, loading them into memory 102, and executing them. In this embodiment, the main process performed by the processor 101 is the "schedule management process," which manages the schedules of the residents of group X. The "schedule management process" will be described later with reference to Figures 6 to 20.

[0039] Program 131 may be provided not as a standalone program, but incorporated as part of any other program. In this case, the processing according to this embodiment is realized in cooperation with the other program. Even if a program does not include such a partial module, it does not deviate from the spirit of the management system 100 according to this embodiment. Furthermore, some or all of the functions provided by Program 131 may be implemented by dedicated hardware.

[0040] Tenant information 132 will be described later with reference to Figure 4. User information 133 will be described later with reference to Figure 5.

[0041] Schedule information 134 includes the schedules of all residents R of Group X. Schedule information 134 is an example of "schedules managed by the management system 100" in this disclosure. Meal information 135 includes information regarding the meal requirements of all residents R of Group X.

[0042] The screen data 136 includes screen data to be output to the user terminal 200 and screen data to be output to the facility terminal 300.

[0043] The communication interface 104 connects the management system 100 to the network 500.

[0044] Although only one processor is shown in Figure 3, the management system 100 may include multiple processors.

[0045] Figure 4 shows an example of resident information 132. For each resident R in group X, resident information 132 includes a resident ID (Identification), the name of resident R, and a user ID. The resident ID is information that identifies each resident R. The resident ID is an example of "first identification information" in this disclosure. The user ID is information that identifies user U of the management system 100. The user ID is an example of "second identification information" in this disclosure. Storage 103 stores the resident ID in association with the name of resident R identified by the resident ID and the user ID.

[0046] User U, identified by a user ID stored in association with a resident ID, is a related party to resident R, who is identified by the resident ID. The management system 100 is configured to register related parties for each resident R. Specifically, the management system 100 is configured to accept operations from facility staff ST or related parties of resident R, and to store user IDs that identify related parties of resident R, associated with the resident ID that identifies resident R.

[0047] In the example shown in Figure 4, the relatives of resident R1 are user U with user ID U0001 and user U with user ID U0002. User U with user ID U0001 is, for example, resident R1's daughter, and user U with user ID U0002 is, for example, resident R1's son. The only relative of resident R2 is user U with user ID U0003. Thus, there is one or more relatives registered for each resident R.

[0048] Furthermore, in the example shown in Figure 4, user U, whose user ID is U0001, is related to both resident R1 and resident R6. Resident R1 is, for example, the mother of user U, whose user ID is U0001, and resident R6 is, for example, the mother of user U's husband. Thus, it is possible for one user U to be registered as related to multiple residents R.

[0049] Figure 5 shows an example of user information 133. User information 133 includes, for each user U of the management system 100, a user ID, the name of user U, and a login ID and login password for user U to log in to the management system 100. Storage 103 stores the name of user U identified by the user ID in association with the user ID. Storage 103 also stores the combination of login ID and login password for user U identified by the user ID to log in to the management system 100 in association with the user ID.

[0050] The management system 100 is configured to accept operations from the facility's staff ST or the user U of the management system 100 and to store user information 133 (register user information 133).

[0051] The schedule management process will be explained with reference to Figures 6 to 20. The schedule management process includes a reception process for receiving event reservations for resident R from people related to resident R, and a process for outputting the details of the received reservations to the facility terminal 300. The reception process includes a process for receiving outing reservations for resident R, a process for receiving overnight stay reservations for resident R, and a process for receiving visitation reservations for resident R.

[0052] Figure 6 is a flowchart showing an example of the processing procedure for the reception process according to this embodiment. The process shown in this flowchart is performed when predetermined conditions are met (for example, at predetermined intervals).

[0053] First, in step S1, the processor 101 determines whether or not it has received a login operation from the user terminal 200 to the management system 100. If it has received a login operation from the user terminal 200 to the management system 100 (YES in step S1), the processor 101 proceeds to step S2. On the other hand, if it has not received a login operation from the user terminal 200 to the management system 100 (NO in step S1), the processor 101 terminates the reception process.

[0054] In step S2, the processor 101 obtains identification information to identify user U who accessed the management system 100. Specifically, the processor 101 obtains from user information 133 a user ID associated with a combination that matches the combination of login ID and login password entered in the accepted login operation. The user ID obtained from user information 133 in step S2 is an example of the "third identification information" in this disclosure.

[0055] Next, in step S3, the processor 101 determines the resident R associated with user U who accessed the management system 100. Specifically, first, the processor 101 refers to the resident information 132 and identifies the resident ID (first identification information) associated with the user ID (second identification information) that matches the user ID (third identification information) obtained in step S2. Next, the processor 101 determines that the resident R identified by the identified resident ID (first identification information) is the resident R associated with user U who accessed the management system 100.

[0056] Next, in step S4, the processor 101 obtains the available dates for booking the event of resident R, which was determined in step S3, from the schedule information 134.

[0057] Next, in step S5, the processor 101 outputs the schedule information indicating the available dates obtained in step S4 to the user terminal 200 used by user U who accessed the management system 100 (logged into the management system 100). If user U who accessed the management system 100 is user U1 (see Figure 1), in step S5, the processor 101 outputs the schedule information to user terminal 200a.

[0058] Next, in step S6, the processor 101 receives the event reservation for resident R, determined in step S3, from the user terminal 200 that output the schedule information. After step S6, the processor 101 terminates the reception process.

[0059] Referring to Figures 7 through 17, we will explain the details of the reception process using the example of user U1 (see Figure 5), whose user ID is U0001, accessing the management system 100 and reserving an event for resident R1.

[0060] Figure 7 shows the first part of the reception process. First, in step S101, the processor 101 receives a request for the login screen from the user terminal 200a (see Figure 1) used by user U1. Next, the processor 101 outputs the login screen G1 to the user terminal 200a.

[0061] The login screen G1 is displayed on the display 299 of the user terminal 200a (see Figure 1). The login screen G1 includes a field 201 for entering a login ID to log in to the management system 100, and a field 202 for entering a login password to log in to the management system 100.

[0062] If a login ID and login password are entered on the login screen G1, the processor 101 proceeds to step S102. In step S102, the processor 101 executes step S2 described above and authenticates user U1 who has accessed the management system 100 (logged into the management system 100). Specifically, first, the processor 101 obtains a user ID (third identification information) from user information 133 that is associated with a combination that matches the combination of login ID and login password entered on the login screen G1 (step S2). Next, the processor 101 authenticates user U identified by the user ID obtained from user information 133. In the example shown in Figure 7, the processor 101 authenticates user U1 (see Figure 5) whose user ID is U0001. After authenticating user U1, the processor 101 outputs the menu screen G2 to the user terminal 200a.

[0063] Menu screen G2 is displayed on the display 299 of the user terminal 200a. Menu screen G2 includes a button 203 for initiating a reservation for resident R to go out or stay overnight, and a button 204 for initiating a reservation for resident R to meet with a visitor.

[0064] If button 203 is pressed, the processor 101 proceeds to step S103. On the other hand, if button 204 is pressed, the processor 101 proceeds to step S117.

[0065] Figure 8 shows the second part of the reception process. In step S103, the processor 101 executes step S3 described above and outputs screen G3 to the user terminal 200a for selecting the resident R for whom a reservation for going out or staying overnight has been made. As shown in Figure 4, the resident IDs (first identification information) associated with the user ID "U0001" (second identification information) of user U1 are R001 and R006. Therefore, if the user U who accessed the management system 100 is user U1, the processor 101 executes step S3 to determine that residents R1 and R6 are residents R associated with the user U who accessed the management system 100.

[0066] Screen G3 is displayed on the display 299 of the user terminal 200a. Screen G3 includes a button 205 for selecting the resident R for whom a reservation to go out or stay overnight is to be made, from among the one or more residents R determined in step S3. In the example shown in Figure 8, the button 205 includes a button 205a for selecting resident R1 and a button 205b for selecting resident R6.

[0067] If a resident R for whom a reservation to go out or stay overnight is made is selected on screen G3, the processor 101 proceeds to step S104. In the example shown in Figure 8, resident R1 is selected on screen G3 (button 205a is pressed). In step S104, the processor 101 outputs screen G4 to the user terminal 200a for making a reservation for resident R (resident R1 in the example shown in Figure 8) to go out or stay overnight.

[0068] Screen G4 is displayed on the display 299 of the user terminal 200a. Screen G4 includes radio buttons 206a and 206b for selecting whether to make a reservation for going out or staying overnight. If radio button 206a is pressed, the processor 101 proceeds to step S105. On the other hand, if radio button 206b is pressed, the processor 101 proceeds to step S110.

[0069] Figure 9 shows the third part of the reception process. Steps S105 to S109 are an example of the process for accepting a reservation to go out for resident R. In step S105, the processor 101 executes step S4 described above, and then executes step S5 described above. Specifically, first, as step S4, the processor 101 obtains from the schedule information 134 the available dates for which resident R1, selected on screen G3, can make a reservation to go out. The available dates for which resident R1 can make a reservation to go out do not include dates for which resident R1 has a reservation to go out, stay overnight, or have a visit. Next, as step S5, the processor 101 outputs screen G5 to the user terminal 200a.

[0070] Screen G5 is displayed on the display 299 of the user terminal 200a. Screen G5 includes schedule information 207 that shows the available dates for which resident R1, selected on screen G3, can make an outing reservation. In the example shown in Figure 9, available dates for resident R1 to make an outing reservation are marked with a circle, and dates for which resident R1 cannot make an outing reservation are not marked with a circle. Note that screen G5 only needs to include available dates for resident R (resident R1 in the example shown in Figure 9) to make an outing reservation, and the display method of these available dates is not limited to the display method shown in Figure 9.

[0071] Screen G5 further includes a field 208 for selecting an outing date. If an outing date is selected from the available dates on screen G5, the processor 101 proceeds to step S106. In step S106, the processor 101 outputs screen G6 to the user terminal 200a, with the outing date selected on screen G5 highlighted.

[0072] Screen G6 is displayed on the display 299 of the user terminal 200a. On screen G6, the outing date selected on screen G5 is highlighted. In the example shown in Figure 9, April 21, 2025 is selected as the outing date. Note that screen G6 only needs to include the outing date selected on screen G5, and the display method of the outing date is not limited to the display method shown in Figure 9. After step S106, the processor 101 moves the process to step S107.

[0073] Figure 10 shows the fourth part of the reception process. In step S107, the processor 101 outputs screen G7 to the user terminal 200a to accept the reservation for an outing by resident R1, selected on screen G3, on the date selected on screen G5.

[0074] Screen G7 is displayed on the display 299 of the user terminal 200a. Screen G7 is an example of "received information" in this disclosure. Screen G7 includes a first part G71 and a second part G72. When user U1 performs a scroll operation on the display 299 of the user terminal 200a, the first part G71 and the second part G72 are switched and displayed on the user terminal 200a.

[0075] Screen G7 includes a field 209 for entering the time of going out and a field 210 for entering the place of going out. Screen G7 further includes a field 211 for entering the person who will go to pick up resident R1, who was selected on Screen G3. Screen G7 further includes a field 212 for entering whether resident R1, who was selected on Screen G3, needs meals. Field 212 is an example of "information for receiving the determination of whether a resident needs meals" in this disclosure.

[0076] Screen G7 further includes checkbox 213. Checkbox 213 is information for receiving instructions on whether or not to disclose reservation information, which shows the details of the reservation received from user U who accessed the management system 100, to "other users". "Other users" refers to one or more users U identified by one or more user IDs (second identification information) associated with the resident ID (first identification information) that identifies resident R for whom an event reservation was made by user U who accessed the management system 100, excluding user U who accessed the management system 100. In the example shown in Figure 10, "other users" refers to one or more users U identified by one or more user IDs (second identification information) associated with the resident ID (first identification information) that identifies resident R1 selected on screen G3, excluding user U1 who is currently accessing the management system 100. In other words, in the example shown in Figure 10, "other users" refers to one or more related parties of resident R1 selected on screen G3, excluding user U1 who is currently accessing the management system 100.

[0077] As shown in Figure 4, the user IDs (second identification information) associated with the resident ID (first identification information) that identifies resident R1 selected on screen G3 are "U0001" and "U0002". As shown in Figure 5, the user U identified by "U0001" is user U1, and the user U identified by "U0002" is user U2. In the example shown in Figure 10, since user U1 is accessing the management system 100, the "other user" is user U2.

[0078] Screen G7 further includes a field 214 for entering messages from user U1 to the facility. Screen G7 further includes a field 215 for confirming messages from the facility to user U1. Screen G7 further includes a button 216 for transitioning to the confirmation screen.

[0079] If button 216 is pressed, the processor 101 proceeds to step S108. In step S108, the processor 101 outputs a confirmation screen G8 to the user terminal 200a.

[0080] Confirmation screen G8 is displayed on the display 299 of the user terminal 200a. Confirmation screen G8 includes reservation information 217. Reservation information 217 shows the details of the reservation received from user U1 (i.e., the details of the reservation entered or selected by user U1 on screens G5 and G7). Confirmation screen G8 further includes a button 218 for returning to screen G7 and a button 219 for confirming the reservation.

[0081] If button 219 is pressed, the processor 101 proceeds to step S109. In step S109, the processor 101 executes step S6 described above. More specifically, in step S6, the processor 101 accepts the reservation indicated by the reservation information 217 and updates the schedule information 134 and meal information 135 based on the reservation information 217. Furthermore, the processor 101 accepts instructions on whether or not to make the reservation information 217 public to "other users" (user U2 in the example shown in Figure 10).

[0082] Specifically, if checkbox 213 is selected and button 219 is pressed, processor 101 receives an instruction to disclose reservation information 217 to "other users". On the other hand, if checkbox 213 is not selected and button 219 is pressed, processor 101 receives an instruction not to disclose reservation information 217 to "other users". After step S109, processor 101 terminates the acceptance process.

[0083] Figure 11 shows the fifth part of the reception process. Steps S110 to S116 are an example of the process for accepting a reservation for an overnight stay for resident R. In step S110, the processor 101 executes step S4 described above, and then executes step S5 described above. Specifically, first, as step S4, the processor 101 obtains the available dates for which an overnight stay reservation for resident R1, selected on screen G3, can be made from the schedule information 134. The available dates for which an overnight stay reservation for resident R1 can be made do not include dates on which resident R1 has reservations for going out, staying overnight, or having a visit. Next, as step S5, the processor 101 outputs screen G9 to the user terminal 200a.

[0084] Screen G9 is displayed on the display 299 of the user terminal 200a. Screen G9 includes schedule information 220 indicating the available dates for which resident R1, selected on screen G3, can make an overnight stay reservation. In the example shown in Figure 11, the available dates for which resident R1, selected on screen G3, can make an overnight stay reservation are marked with a circle, while the dates for which resident R1, selected on screen G3, cannot make an overnight stay reservation are not marked with a circle. Note that screen G9 only needs to include the available dates for which resident R (resident R1 in the example shown in Figure 11), selected on screen G3, can make an overnight stay reservation, and the display method of these available dates is not limited to the display method shown in Figure 11.

[0085] Screen G9 further includes a field 221 for selecting the start date of the overnight stay. If a start date for the overnight stay is selected from the available dates on screen G9, the processor 101 proceeds to step S111. In step S111, the processor 101 outputs screen G10 to the user terminal 200a, with the start date of the overnight stay selected on screen G9 highlighted.

[0086] Screen G10 is displayed on the display 299 of the user terminal 200a. On screen G10, the start date of the overnight stay selected on screen G9 is highlighted. In the example shown in Figure 11, April 8, 2025 is selected as the start date of the overnight stay. Note that screen G10 only needs to include the start date of the overnight stay selected on screen G9, and the display method of the start date is not limited to the display method shown in Figure 11. After step S111, the processor 101 moves the process to step S112.

[0087] Figure 12 shows the sixth part of the reception process. In step S112, the processor 101 outputs screen G11 to the user terminal 200a.

[0088] Screen G11 is displayed on the display 299 of the user terminal 200a. Screen G11 includes a field 223 for user U1 to enter the time to pick up resident R1. Screen G11 further includes a field 222 for selecting the end date of the overnight stay. If an end date of the overnight stay is selected on screen G11, the processor 101 proceeds to step S113. In step S113, the processor 101 outputs screen G12 to the user terminal 200a, with the end date of the overnight stay selected on screen G11 highlighted.

[0089] Screen G12 is displayed on the display 299 of the user terminal 200a. On screen G12, the end date of the overnight stay selected on screen G11 is highlighted. In the example shown in Figure 12, April 9, 2025 is selected as the end date of the overnight stay. Note that screen G12 only needs to include the end date of the overnight stay selected on screen G11, and the display method of the end date is not limited to the display method shown in Figure 12. After step S113, the processor 101 moves the process to step S114.

[0090] Figure 13 shows the seventh part of the reception process. In step S114, the processor 101 outputs screen G13 to the user terminal 200a to accept the reservation for an overnight stay for resident R1, selected on screen G3, for the dates selected on screens G9 and G11.

[0091] Screen G13 is displayed on the display 299 of the user terminal 200a. Screen G13 is an example of "received information" in this disclosure. Screen G13 includes a first part G131 and a second part G132. By user U1 performing a scroll operation on the display 299 of the user terminal 200a, the first part G131 and the second part G132 are switched and displayed on the user terminal 200a.

[0092] Screen G13 includes a field 224 for entering the time of return and a field 225 for entering the location of the outing. Screen G13 further includes a field 226 for entering the person who will pick up resident R1, who was selected on screen G3. Screen G13 further includes a field 227 for entering whether resident R1, who was selected on screen G3, requires meals. Field 227 is an example of "information for receiving the determination of whether resident requires meals" in this disclosure. Field 227 includes fields for entering whether resident R1, who was selected on screen G3, requires meals on the start date of the outing and the end date of the outing.

[0093] Screen G13 further includes checkbox 228. Checkbox 228 is information for receiving instructions on whether or not to disclose reservation information, which shows the details of the reservation received from user U who accessed the management system 100, to "other users". "Other users" are as described above. In the example shown in Figure 13, "other users" are one or more related parties of resident R1 selected on screen G3, excluding user U1 who is currently accessing the management system 100. In other words, in the example shown in Figure 13, "other users" is user U2.

[0094] Screen G13 further includes a field 229 for entering messages from user U1 to the facility. Screen G13 further includes a field 230 for confirming messages from the facility to user U1. Screen G13 further includes a button 231 for transitioning to a confirmation screen.

[0095] If button 231 is pressed, the processor 101 proceeds to step S115. In step S115, the processor 101 outputs confirmation screen G14 to the user terminal 200a.

[0096] Confirmation screen G14 is displayed on the display 299 of the user terminal 200a. Confirmation screen G14 includes reservation information 232. Reservation information 232 shows the details of the reservation received from user U1 (i.e., the details of the reservation entered or selected by user U1 on screens G9, G11, and G13). Confirmation screen G14 further includes a button 233 for returning to screen G13 and a button 234 for confirming the reservation.

[0097] If button 234 is pressed, the processor 101 proceeds to step S116. In step S116, the processor 101 executes step S6 described above. More specifically, in step S6, the processor 101 accepts the reservation indicated by the reservation information 232 and updates the schedule information 134 and meal information 135 based on the reservation information 232. Furthermore, the processor 101 accepts instructions on whether or not to make the reservation information 232 public to "other users" (user U2 in the example shown in Figure 13).

[0098] Specifically, if checkbox 228 is selected and button 234 is pressed, processor 101 accepts an instruction to disclose reservation information 232 to "other users". On the other hand, if checkbox 228 is not selected and button 234 is pressed, processor 101 accepts an instruction not to disclose reservation information 232 to "other users". After step S116, processor 101 terminates the acceptance process.

[0099] Figure 14 shows the eighth part of the reception process. Steps S117 to S122 are an example of the process for accepting a visitation reservation for resident R. In step S117, the processor 101 executes step S3 described above and outputs screen G15 to the user terminal 200a for selecting resident R for whom a visitation reservation is to be made. As described above, if the user U who accessed the management system 100 is user U1, the processor 101 executes step S3 to determine that residents R1 and resident R6 are residents R associated with user U who accessed the management system 100.

[0100] Screen G15 is displayed on the display 299 of the user terminal 200a. Screen G15 includes a button 235 for selecting the resident R for whom a meeting is to be scheduled from among the one or more residents R determined in step S3. In the example shown in Figure 14, the button 235 includes a button 235a for selecting resident R1 and a button 235b for selecting resident R6.

[0101] If resident R for whom a visitation reservation is to be made is selected on screen G15, the processor 101 proceeds to step S118. In the example shown in Figure 14, resident R1 is selected on screen G15 (button 235a is pressed). In step S118, the processor 101 executes step S4 described above, and then executes step S5 described above. Specifically, first, as step S4, the processor 101 obtains the available dates for which a visitation reservation can be made for resident R1, who was selected on screen G15, from the schedule information 134. The available dates for which a visitation reservation can be made for resident R1 do not include dates on which resident R1 is out, staying overnight, or has a scheduled visitation. Next, as step S5, the processor 101 outputs screen G16 to the user terminal 200a.

[0102] Screen G16 is displayed on the display 299 of the user terminal 200a. Screen G16 includes radio buttons 236a and 236b for selecting the method of meeting. If radio button 236a is pressed, the processor 101 accepts a visit as the method of meeting. On the other hand, if radio button 236b is pressed, the processor 101 accepts an online meeting as the method of meeting.

[0103] Screen G16 further includes schedule information 237 indicating available dates for booking a visit with resident R1, selected on screen G15. In the example shown in Figure 14, available dates for booking a visit with resident R1 are marked with a circle, while dates for which a visit with resident R1 is not possible are not marked with a circle. Note that screen G16 only needs to include available dates for booking a visit with resident R (resident R1 in the example shown in Figure 14), selected on screen G15, and the display of these available dates is not limited to the display shown in Figure 14.

[0104] Screen G16 further includes a field 238 for selecting a meeting date. If a meeting date is selected from the available dates on screen G16, the processor 101 proceeds to step S119. In step S119, the processor 101 outputs screen G17 to the user terminal 200a, with the meeting date selected on screen G16 highlighted.

[0105] Screen G17 is displayed on the display 299 of the user terminal 200a. On screen G17, the meeting date selected on screen G16 is highlighted. In the example shown in Figure 14, April 17, 2025 is selected as the meeting date. Note that screen G17 only needs to include the meeting date selected on screen G16, and the display method of the meeting date is not limited to the display method shown in Figure 14. After step S119, the processor 101 moves the process to step S120.

[0106] Figure 15 shows the ninth part of the reception process. In step S120, the processor 101 outputs screen G18 to the user terminal 200a to accept the reservation of a visit for resident R1, selected on screen G15, on the date selected on screen G16.

[0107] Screen G18 is displayed on the display 299 of the user terminal 200a. Screen G18 is an example of "received information" in this disclosure. Screen G18 includes a first part G181 and a second part G182. By user U1 performing a scroll operation on the display 299 of the user terminal 200a, the first part G181 and the second part G182 are switched and displayed on the user terminal 200a.

[0108] Screen G18 includes a field 239 for selecting the meeting time. On Screen G18, times when meetings can be booked are marked with a circle, and times when meetings cannot be booked are not marked with a circle. Note that Screen G18 only needs to include times when meetings can be booked, and the display of times when meetings can be booked is not limited to the display shown in Figure 15. Screen G18 further includes a checkbox 240. The checkbox 240 is information for receiving instructions on whether or not to disclose the reservation information, which shows the details of the reservation received from user U who accessed the management system 100, to "other users". "Other users" are as described above. In the example shown in Figure 15, "other users" are one or more related parties of resident R1 selected on Screen G15, excluding user U1 who is currently accessing the management system 100. In other words, in the example shown in Figure 15, "other users" is user U2.

[0109] Screen G18 further includes a field 241 for entering messages from user U1 to the facility. Screen G18 further includes a field 242 for confirming messages from the facility to user U1. Screen G18 further includes a button 243 for transitioning to the confirmation screen.

[0110] If button 243 is pressed, the processor 101 proceeds to step S121. In step S121, the processor 101 outputs a confirmation screen G19 to the user terminal 200a.

[0111] Confirmation screen G19 is displayed on the display 299 of the user terminal 200a. Confirmation screen G19 includes reservation information 244. Reservation information 244 shows the details of the reservation received from user U1 (i.e., the details of the reservation entered or selected by user U1 on screens G16 and G18). Confirmation screen G19 further includes a button 245 to return to screen G18 and a button 246 to confirm the reservation.

[0112] If button 246 is pressed, the processor 101 proceeds to step S122. In step S122, the processor 101 executes step S6 described above. More specifically, in step S6, the processor 101 accepts the reservation indicated by the reservation information 244 and updates the schedule information 134 based on the reservation information 244. Furthermore, the processor 101 accepts instructions on whether or not to disclose the reservation information 244 to "other users" (user U2 in the example shown in Figure 15).

[0113] Specifically, if checkbox 240 is selected and button 246 is pressed, processor 101 accepts an instruction to disclose reservation information 244 to "other users". On the other hand, if checkbox 240 is not selected and button 246 is pressed, processor 101 accepts an instruction not to disclose reservation information 244 to "other users". After step S122, processor 101 terminates the acceptance process.

[0114] Figure 16 shows an example of a notification screen for reservation information that has been instructed to be made public. Notification screen G20 is displayed on the user terminal 200 used by the aforementioned "other users".

[0115] After receiving an instruction from user U1 to disclose reservation information to "other users," processor 101 outputs the reservation information to the user terminal 200 used by the "other user" when that "other user" accesses the management system 100. For example, after receiving an instruction from user U1 to disclose reservation information showing the details of an event reservation for resident R1 to "other users," if user U2, who is the "other user," selects a date indicated by the reservation information on a screen where user U2 selects the dates for resident R1's outing, overnight stay, or visit, processor 101 outputs notification screen G20 to the user terminal 200b (see Figure 1) used by user U2. The screen for selecting resident R1's outing dates is screen G5 (see Figure 9). The screens for selecting resident R1's overnight stay dates are screen G9 (see Figure 11) and screen G11 (see Figure 12). The screen for selecting resident R1's visit dates is screen G16 (see Figure 14).

[0116] Notification screen G20 includes message 247, which shows the reservation information. This allows "other users" to see who has booked which event for resident R1 on the selected date. Notification screen G20 further includes button 248 to return to the previous screen (i.e., the screen where resident R1's outing, overnight stay, or visitation dates are selected).

[0117] Figure 17 shows an example of a notification screen for reservation information that has not been instructed to be made public. Notification screen G21 is displayed on the user terminal 200 used by the aforementioned "other user".

[0118] After receiving an instruction not to disclose the reservation information to "other users," the processor 101 outputs a message to the user terminal 200 used by the "other user" indicating that the reservation cannot be made if the "other user" accesses the management system 100 and selects a date indicated by the reservation information.

[0119] For example, after receiving an instruction from user U1 not to disclose reservation information showing the details of resident R1's event reservation to "other users", if user U2, who is "another user," selects a date indicated by the reservation information on the screen where resident R1 can go out, stay overnight, or have a visit, the processor 101 outputs a notification screen G21 to the user terminal 200b (see Figure 1) used by user U2.

[0120] Notification screen G21 includes a message 249 indicating that a reservation cannot be made. On the other hand, notification screen G21 does not include a message indicating reservation information. Therefore, "other users" can know that they cannot reserve an event for resident R1 on the selected date. However, "other users" cannot know who has reserved which event for resident R1 on the selected date. Notification screen G21 further includes a button 250 to return to the previous screen (i.e., the screen where resident R1's outing, overnight stay, or visitation dates are selected).

[0121] Referring to Figures 18 to 20, the process of outputting the details of received reservations to the facility terminal 300 as part of the schedule management process will be explained.

[0122] Figure 18 shows a first example of a screen displayed on the facility terminal 300. Screen G31 is displayed on the display 399 of the facility terminal 300 (see Figure 1). Screen G31 indicates whether resident R needs meals. Screen G31 is an example of "information regarding the need for meals for one or more residents" in this disclosure. When the processor 101 receives a request from the facility terminal 300 for a screen indicating whether resident R needs meals, the processor 101 generates screen G31 based on the meal information 135 and outputs screen G31 to the facility terminal 300.

[0123] Screen G31 displays the number of cancellations (non-required) for breakfast, lunch, snacks, and dinner on a daily basis. Screen G31 includes buttons 301 and 302. When button 301 is pressed, processor 101 generates screen G32 (see Figure 19) based on meal information 135 and outputs screen G32 to facility terminal 300. When button 302 is pressed, processor 101 generates screen G33 (see Figure 20) based on meal information 135 and outputs screen G33 to facility terminal 300.

[0124] Figure 19 shows a second example of a screen displayed on the facility terminal 300. Screen G32 is displayed on the display 399 of the facility terminal 300. Screen G32 is an example of "information regarding the meal requirements of one or more residents" in this disclosure. In the example shown in Figure 19, screen G32 shows a list of residents R who do not require lunch on April 2, 2025.

[0125] Figure 20 shows a third example of a screen displayed on the facility terminal 300. Screen G33 is displayed on the display 399 of the facility terminal 300. Screen G33 is an example of "information regarding the necessity of meals for one or more residents" in this disclosure. In the example shown in Figure 20, screen G33 shows the necessity of each meal on April 2, 2025, for resident R who has applied that they do not need any of the meals on April 2, 2025.

[0126] Furthermore, it is sufficient for information regarding the resident R's meal needs to be output to the facility terminal 300, and the screens displayed on the facility terminal 300 are not limited to those shown in Figures 18 to 20.

[0127] Thus, the storage 103 stores a resident ID (first identification information) that identifies each of the one or more residents R, associating it with a user ID (second identification information) that identifies user U of the management system 100. The processor 101 obtains a user ID (third identification information) that identifies user U who accessed the management system 100. The processor 101 determines which resident R is identified by the resident ID (first identification information) associated with the user ID (second identification information) that matches the third identification information. The processor 101 obtains the available dates for booking events for the determined resident R from the schedule information 134. The processor 101 outputs the schedule information showing the available dates to the user terminal 200 used by user U who accessed the management system 100. Therefore, only user U identified by the user ID associated with the resident ID that identifies resident R can view the available dates for booking resident R. Thus, the management system 100 can securely manage the schedules of resident R.

[0128] Events include going out, staying overnight, and visits. This allows user U, who has access to the management system 100, to see the available dates for resident R to go out, stay overnight, and visits.

[0129] The processor 101 outputs reception information (for example, screen G7 shown in Figure 10, screen G13 shown in Figure 13, or screen G18 shown in Figure 15) to the user terminal 200 used by user U, allowing the user U to accept reservations for events of the determined resident R from user U who has accessed the management system 100. This allows user U, who has accessed the management system 100, to reserve events of the determined resident R.

[0130] If resident R, who has been assessed as needing a meal, goes out or stays overnight elsewhere, meals may not be required. Screen G7 (Reception Information) includes a field 212 for entering whether resident R needs meals. Screen G13 (Reception Information) includes a field 227 for entering whether resident R needs meals. Therefore, the management system 100 can manage the number of canceled (unnecessary) meals.

[0131] The processor 101 outputs information regarding resident R's meal needs to a facility terminal 300 used by facility staff ST. This allows staff ST to know whether resident R needs meals. Therefore, according to the management system 100, food waste can be reduced.

[0132] Screen G7 (Reception Information) includes checkbox 213. Screen G13 (Reception Information) includes checkbox 228. Screen G18 (Reception Information) includes checkbox 240. This allows user U, who accesses the management system 100, to specify whether or not to disclose reservation information showing the details of their reservation to "other users". Therefore, according to the management system 100, the convenience for user U is improved.

[0133] After receiving an instruction to make reservation information public to "other users," the processor 101 outputs the reservation information to the user terminal 200 used by "other users" when "other users" access the management system 100. Therefore, according to the management system 100, the convenience for user U is improved.

[0134] The available dates for booking do not include dates on which the determined resident R has scheduled outings, overnight stays, or visits. This allows user U to accurately understand resident R's schedule. Therefore, according to the management system 100, overlapping bookings can be prevented.

[0135] The processor 101 updates the schedule information 134 when it accepts a reservation for an event for the determined resident R. This allows user U to obtain the latest available dates for resident R by accessing the management system 100. Therefore, the management system 100 improves the convenience for user U.

[0136] [Example 1] An event may include at least one of the following: going out, staying overnight, and visiting. An event may include at least one of the following: going out, staying overnight, visiting, bathing, rehabilitation, and recreation.

[0137] If the event includes at least one of going out and staying overnight, it is preferable that the screen for booking the determined resident R's outing (e.g., screen G7) includes information for receiving whether the determined resident R requires meals.

[0138] If the event includes at least one of going out and / or staying overnight, it is preferable that the screen for booking the overnight stay for the determined resident R (e.g., screen G13) includes information for receiving whether the determined resident R requires meals.

[0139] If an event includes at least one of going out or staying overnight, it is preferable that the available dates do not include any dates on which the determined resident R has a reservation for going out or staying overnight.

[0140] If the event includes visits, it is preferable that the available dates do not include dates on which visits are already scheduled for the determined resident R.

[0141] If an event includes at least one of going out, staying overnight, or having a visit, it is preferable that the available dates do not include any dates on which the determined resident R has a scheduled outing, overnight stay, or visit.

[0142] [Differentiation 2] In this disclosure, "facility" may include one or more residential facilities. Therefore, "facility" may include, in place of, or in addition to residential care facilities, at least one of a hospital and a residential facility for persons with disabilities.

[0143] [Difference 3] The management system 100 may be configured not only so that user U can reserve events for resident R using user terminal 200, but also so that facility staff ST can reserve events for resident R using facility terminal 300.

[0144] [Differentiation Example 4] The management system 100 may output a list of reservation information to the facility terminal 300.

[0145] [Difference 5] The management system 100 may be configured to modify reservation information based on requests from user terminals 200 or facility terminals 300.

[0146] The management system 100 may be configured to delete reservation information (cancel reservations) based on requests from user terminals 200 or facility terminals 300.

[0147] The embodiments and variations disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of this disclosure is indicated by the claims rather than the foregoing description, and all modifications are intended to be within the meaning and scope equivalent to the claims. [Explanation of Symbols]

[0148] 1 System, 100 Management System, 101 Processor, 102 Memory, 103 Storage, 104 Communication Interface, 131 Program, 132 Resident Information, 133 User Information, 134 Schedule Information, 135 Meal Information, 136 Screen Data, 200, 200a, 200b User Terminal, 201, 202, 208~212, 214, 215, 221~227, 229, 230, 238, 239, 241, 242 Fields, 203~205, 205a, 205b, 216, 218, 219, 231, 233, 234, 235, 235a, 235b, 243, 245, 246, 248, 250, 301, 302 Buttons, 206a, 206b, 236a, 236b Radio buttons, 207, 220, 237 Schedule information, 213, 228, 240 Checkboxes, 217, 232, 244 Reservation information, 247, 249 Messages, 299, 399 Display, 300 Facility terminal, 500 Network, G1 Login screen, G2 Menu screen, G3, G4, G5, G6, G7, G9, G10, G11, G12, G13, G15, G16, G17, G18, G31, G32, G33 Screen, G8, G14, G19 Confirmation screen, G20, G21 Notification screen, G71, G131, G181 First part, G72, G132, G182 The latter half consists of R, R1, R2, R3, R4, R5, R6, R7 residents, U, U1, U2, U3, U4, U5, U6, U7, U8, U9, U10 users, ST staff, X group, and X1, X2, X3 nursing care facilities.

Claims

1. A management system for managing the schedules of one or more residents of a facility, Processor and The system includes a storage unit that stores a second identification information that identifies a user of the management system, associated with a first identification information that identifies each of the one or more residents, The aforementioned processor, A third identification piece is obtained that identifies the user who accessed the aforementioned management system. Determine the resident identified by the first identification information associated with the second identification information that matches the third identification information, The available dates for booking the event for the determined resident are obtained from the schedule, A management system that outputs schedule information indicating the available reservation dates to the first user terminal used by the user who accessed the system.

2. The management system according to claim 1, wherein the event includes at least one of going out, staying overnight, and meeting someone.

3. The management system according to claim 1, wherein the processor further outputs to the first user terminal reception information for receiving the reservation of the event of the determined resident from the accessed user.

4. The aforementioned event includes at least one of going out and staying overnight, The management system according to claim 3, wherein the reception information includes information for receiving whether or not the determined resident requires meals.

5. The management system according to claim 4, wherein the processor outputs information regarding the necessity of meals for one or more residents to a facility terminal used by the facility staff.

6. The management system according to claim 3, wherein the reception information includes information for receiving instructions on whether or not to disclose reservation information indicating the content of the reservation received from the accessed user to other users identified by the second identification information associated with the first identification information that identifies the determined resident.

7. The management system according to claim 6, wherein the processor, after receiving an instruction to disclose the reservation information to the other user, outputs the reservation information to a second user terminal used by the other user when the other user accesses the management system.

8. The aforementioned event includes at least one of going out and staying overnight, The management system according to claim 1, wherein the available reservation dates do not include dates on which the determined resident has a reservation to go out or stay overnight elsewhere.

9. The aforementioned event includes meetings, The management system according to claim 1, wherein the available reservation dates do not include dates on which the determined resident has a reservation for a visit.

10. The aforementioned event includes at least one of the following: going out, staying overnight, and meeting with someone. The management system according to claim 1, wherein the available reservation dates do not include dates on which the determined resident has a reservation for going out, staying overnight elsewhere, or having a visit.

11. The management system according to claim 1, wherein the processor updates the schedule when it receives a reservation for the event of the determined resident.

12. The management system according to any one of claims 1 to 11, wherein the facility is a nursing care facility.

13. A management method for managing the schedules of one or more residents of a facility, implemented by a computer, The computer includes a storage unit that stores a first identification information that identifies each of the one or more residents, associated with a second identification information that identifies a user of the management system for managing the schedule, The aforementioned management method is, To obtain a third identification piece that identifies the user who accessed the aforementioned management system, To determine the resident identified by the first identification information associated with the second identification information which matches the third identification information, Obtain from the aforementioned schedule the available dates for booking the event for the determined resident, A management method comprising outputting schedule information indicating the available reservation dates to a first user terminal used by the user who accessed the service.

14. A management program that causes a computer to execute the management method described in claim 13.

Images