Care Support System

Abstract

To provide a care support system that enables even an inexperienced care provider to create a schedule or provide care. SOLUTION: A care support device 100 transmits a request including information about a care provider and a request to generate candidates for a schedule for carrying out actions for a care recipient to a large-scale language model server 200, receives an estimation result output from the large-scale language model server 200 in response to the transmitted request, and displays a schedule based on the received estimation result. As a result, candidates for a schedule are obtained, so that even an inexperienced care provider can create a schedule or carry out care.

Description

[Technical field]

[0001] The present invention relates to a system that supports a care provider in caring for a care recipient, and more particularly to a care support system that enables even an inexperienced care provider to create a schedule or provide care. [Background technology]

[0002] 2. Description of the Related Art Conventionally, as a technology for supporting a care provider such as a care manager in caring for a care recipient such as an elderly person, for example, the technology described in Patent Document 1 is known.

[0003] The technology described in Patent Document 1 involves inputting at least one piece of information among the hopes of the care recipient or their family, the goals for realizing the hopes, and the tasks for realizing the hopes in achieving the goals, and using a trained model that has been trained based on care management information in which the hopes, goals or tasks, and the action items necessary to achieve the goals are associated, inferring action items from the input information and presenting the estimated action items. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2021-114276 A Summary of the Invention [Problem to be solved by the invention]

[0005] However, in the technology described in Patent Document 1, although action items can be obtained by providing a wish, goal, or task, the caregiver must create a schedule for carrying out the action items. Since the schedule is created based on the period and frequency for carrying out the action items presented, it is difficult for an inexperienced caregiver to create the schedule.

[0006] Therefore, the present invention has been made with a focus on the unresolved issues inherent in such conventional technology, and aims to provide a care support system that allows even inexperienced care providers to create schedules or provide care. [Means for solving the problem]

[0007] [Invention 1] In order to achieve the above object, the care support system of Invention 1 comprises an input means for inputting a request including actions to be taken for a care recipient and a request to generate a schedule for carrying out the actions to be taken into a large-scale language model, and an acquisition means for acquiring information output from the large-scale language model in response to the request.

[0008] Here, the schedule includes, for example, a schedule in which action items are associated with the time to perform them in a predetermined period (for example, one day, one week, one month), a schedule in which action items are associated with the time to perform them for each predetermined period, or a schedule that combines these. The same applies to the care support systems of Inventions 4 and 6 below.

[0009] In addition, the present system may be realized as a single device, terminal, or other equipment, or may be realized as a network system in which multiple devices, terminals, or other equipment are communicatively connected. In the latter case, each component may belong to any of the multiple devices, etc., as long as they are communicatively connected to each other. The same applies to the care support systems of Inventions 4 and 6 below.

[0010] [Invention 2] Furthermore, in the care support system of Invention 2, in the care support system of Invention 1, the request includes a period during which the action item is to be performed.

[0011] [Invention 3] Furthermore, the care support system of Invention 3 is the care support system of either Invention 1 or 2, wherein the request includes a frequency of performing the action item.

[0012] [Invention 4] The care support system of Invention 4 further comprises an input means for inputting a request including a period for performing actions for a care recipient and a request to generate a schedule for performing the actions to be performed into a large-scale language model, and an acquisition means for acquiring information output from the large-scale language model in response to the request.

[0013] [Invention 5] Furthermore, in the care support system of Invention 5, in the care support system of Invention 4, the request includes a frequency of performing the action item.

[0014] [Invention 6] The care support system of Invention 6 further comprises an input means for inputting a request including a frequency of performing actions for a care recipient and a request to generate a schedule for performing the actions to be performed into a large-scale language model, and an acquisition means for acquiring information output from the large-scale language model in response to the request.

[0015] [Invention 7] Furthermore, the care support system of Invention 7 is a care support system of any one of Inventions 1, 2, 4 to 6, wherein the request includes attributes of the care recipient or care provider, or information regarding the care recipient or the care provider.

[0016] [Invention 8] Furthermore, the care support system of Invention 8 is a care support system of any one of Inventions 1, 2, and 4 to 6, wherein the request includes the wishes of the care recipient or his / her family, a goal for realizing the wishes, a problem that needs to be solved in order to achieve the goal, or a deadline for achieving the goal.

[0017] [Invention 9] Furthermore, the care support system of Invention 9 is a care support system of any one of Inventions 1, 2, and 4 to 6, wherein the request includes a wish of the care recipient or his / her family, a problem that needs to be solved in order to realize the wish, a goal set for solving the problem, or a deadline for achieving the goal. Effect of the Invention

[0018] As described above, according to the care support system of Invention 1, a schedule can be obtained by providing action items, so that even an inexperienced care provider can create a schedule or provide care.

[0019] Furthermore, according to the care support system of Invention 2, a schedule can be obtained that takes into consideration the period during which each action item is to be performed.

[0020] Furthermore, according to the care support system of the third or fifth aspect, a schedule can be obtained that takes into account the frequency with which the action items are to be performed.

[0021] Furthermore, according to the care support system of Invention 4, a schedule can be obtained by providing a period for carrying out the action items, so that even an inexperienced care provider can create a schedule or carry out care.

[0022] Furthermore, according to the care support system of Invention 6, a schedule can be obtained by providing the frequency with which the action items are to be performed, so that even an inexperienced care provider can create a schedule or provide care.

[0023] Furthermore, according to the care support system of Invention 7, it is possible to obtain a schedule that takes into consideration the attributes of the care recipient or care provider or information regarding the care recipient or care provider.

[0024] Furthermore, according to the care support system of Invention 8, a schedule can be obtained that takes into account hopes, goals, challenges, or deadlines for achieving them.

[0025] Furthermore, according to the care support system of Invention 9, a schedule can be obtained that takes into account hopes, issues, goals, or deadlines for achieving them. [Brief description of the drawings]

[0026] [Figure 1] FIG. 1 is a block diagram showing a configuration of a network system. [Diagram 2] 1 is a diagram showing a hardware configuration of a care support device 100. FIG. [Diagram 3] This is a conceptual diagram showing the connection relationship between hopes, goals, tasks, and implementation items. [Figure 4] 13 is a flowchart showing a care plan creation process. [Diagram 5] This is a screen showing a care management table when preferences are input from multiple candidates. [Figure 6] 13 is a screen showing a care management table when a goal is input from a plurality of candidates. [Figure 7] 13 is a screen showing a care management table when a task is input from a plurality of candidates. [Figure 8] 13 is a screen showing a care management table when action items are input from a plurality of candidates. [Figure 9] 13 is a flowchart showing a schedule creation process. [Figure 10] This is the screen for inputting the implementation items, implementation period, and implementation frequency. [Figure 11] This is a screen that displays schedule candidates. [Figure 12] This is a screen that displays details of a schedule candidate. [Figure 13] A conceptual diagram showing the connection between hopes, goals, and challenges. [Figure 14] FIG. 1 is a conceptual diagram showing the connection between hopes, goals, and actions. [Figure 15] This is a conceptual diagram showing the connection relationship between hopes, issues, and action items. [Figure 16] FIG. 1 is a conceptual diagram showing the relationship between goals, tasks, and action items. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0027] An embodiment of the present invention will now be described with reference to Figures 1 to 12.

[0028] First, the configuration of this embodiment will be described. FIG. 1 is a block diagram showing the configuration of a network system.

[0029] As shown in FIG. 1, a care support device 100 that supports a care provider in caring for a care recipient, and a large-scale language model server 200 that generates information using a large language model are connected to the Internet 199.

[0030] Next, the configuration of the care support device 100 will be described. FIG. 2 is a diagram showing a hardware configuration of the care support device 100. As shown in FIG.

[0031] As shown in FIG. 2, the care support device 100 is composed of a CPU (Central Processing Unit) 30 that controls calculations and the entire system based on a control program, a ROM (Read Only Memory) 32 in which the control program etc. of the CPU 30 are stored in advance in a specified area, a RAM (Random Access Memory) 34 for storing data read from the ROM 32 etc. and calculation results required in the calculation process of the CPU 30, and an I / F (InterFace) 38 that mediates the input and output of data to and from external devices. These are connected to each other and capable of sending and receiving data by a bus 39, which is a signal line for transferring data.

[0032] Connected to the I / F 38 as external devices are an input device 40 consisting of a keyboard, mouse, etc. capable of inputting data as a human interface, a storage device 42 which stores data, tables, etc. as files, and a display device 44 which displays a screen based on an image signal.

[0033] Next, the relationship between hopes, goals, tasks, and implementation items will be explained. The care management table of this embodiment manages in correspondence with (1) the "hopes" of the care recipient, (2) "goals" for realizing the wishes, (3) "issues" that need to be resolved in order to achieve the goals, and (4) "action items" necessary to resolve the issues.

[0034] FIG. 3 is a conceptual diagram showing the relationship between hopes, goals, tasks, and action items. For each wish, one or more goals are set to realize the wish, as shown in FIG. 3. In the example of FIG. 3, goal 1-1, goal 1-2, and other goals are set for wish 1, and goal 2-1, goal 2-2, and other goals are set for wish 2. Since the goals to be set correspond to each wish, goals 1-1, 1-2, 2-1, and 2-2 may have the same or similar tendencies or contents, but are basically independent of each other. The care provider hears the wishes of the care recipient and writes the heard wishes in the care management table. Then, the care provider sets a goal to realize the wish based on his / her own experience, care history, etc., and writes the set goal in the care management table. One or more goals may be set as necessary.

[0035] Next, for each goal, one or more tasks that need to be solved to achieve the goal are set. In the example of FIG. 3, task 1-1-1, task 1-1-2, and other tasks are set for goal 1-1, task 1-2-1, task 1-2-2, and other tasks are set for goal 1-2, task 2-1-1, task 2-1-2, and other tasks are set for goal 2-1, and task 2-2-1, task 2-2-2, and other tasks are set for goal 2-2. Since the tasks to be set correspond to each goal, tasks 1-1-1, 1-1-2, 1-2-1, 1-2-2, 2-1-1, 2-1-2, 2-2-1, and 2-2-2 may have the same or similar tendencies or contents, but are basically independent of each other. The care provider sets tasks that need to be solved to achieve the above-mentioned set goals based on their own experience and care history, and enters the set tasks in the care management table. One or more tasks may be set as necessary.

[0036] Next, for each task, one or more action items necessary to solve the task are set. In the example of Fig. 3, action item 1-1-1-1, action item 1-1-1-2 and other action items are set for task 1-1-1, action item 1-1-2-1, action item 1-1-2-2 and other action items are set for task 1-1-2, action item 1-2-1-1, action item 1-2-1-2 and other action items are set for task 1-2-1, action item 1-2-1-2 and other action items are set, and action item 1-2-2-1, action item 1-2-2-2 and other action items are set for task 1-2-2. In addition, for task 2-1-1, action item 2-1-1-1, action item 2-1-1-2 and other action items have been set; for task 2-1-2, action item 2-1-2-1, action item 2-1-2-2 and other action items have been set; for task 2-2-1, action item 2-2-1-1, action item 2-2-1-2 and other action items have been set; and for task 2-2-2, action item 2-2-2-1, action item 2-2-2-2 and other action items have been set. Since the action items to be set correspond to each issue, action items 1-1-1-1, 1-1-1-2, 1-1-2-1, 1-1-2-2, 1-2-1-1, 1-2-1-2, 1-2-2-1, 1-2-2-2, 2-1-1-1, 2-1-1-2, 2-1-2-1, 2-1-2-2, 2-2-1-1, 2-2-1-2, 2-2-2-1, 2-2-2-2 may have the same or similar tendencies or contents, but are basically independent of each other. Based on their own experience and care history, the care provider sets the action items necessary to solve the above-mentioned set issues and enters the set action items in the care management table. One or more action items may be set as necessary.

[0037] Next, the configuration of the large-scale language model server 200 will be described. The large-scale language model server 200 is configured to have the same hardware configuration as the care support device 100. The large-scale language model is a deep learning model that pre-learns from a huge amount of data what is called a language model that models human spoken words based on their occurrence probability. When the large-scale language model server 200 receives a request, it uses the large-scale language model to statistically estimate the generation probability of the next word from the sentence included in the received request, and transmits the estimation result to the request source. As the large-scale language model, for example, known technologies described in the Internet sites "https: / / chatgpt-lab.com / n / n418d3aa56f0b" and "https: / / agirobots.com / chatgpt-mechanism-and-problem / " can be adopted.

[0038] The contents of the hopes, goals, tasks, and implementation items and their coupling relationships as shown in Figure 3 are publicly known at least in JP 2020-190818 A. This publicly known information is learned in the large-scale language model.

[0039] Next, the operation of this embodiment will be described. First, the case of creating a care plan will be described.

[0040] The CPU 30 is made up of an MPU (Micro-Processing Unit) or the like, and starts a predetermined program stored in a predetermined area of ​​the ROM 32, and executes the care plan creation process shown in the flowchart of FIG. 4 in accordance with the program.

[0041] FIG. 4 is a flowchart showing the care plan creation process. The care plan creation process is initiated in response to a request from a user such as a care provider, and when executed by the CPU 30, first, the process proceeds to step S100 as shown in FIG.

[0042] In step S100, when input of the name of the care recipient is requested, the name of the care recipient is input from the input device 40.

[0043] FIG. 5 is a screen showing a care management table when preferences are input from multiple candidates. Next, the process proceeds to step S102, and when the input of the care recipient's wish is requested, a display process of the wish candidates is executed. In this display process, the wish candidates are displayed on the display device 44 as follows. In the care support device 100, a request including a request to generate wish candidates is generated and transmitted to the large-scale language model server 200. The request may be, for example, "Please provide the wish candidates of the care recipient when providing care to the care recipient." In the care support device 100, when an estimation result (for example, a text including one or more candidates) output from the large-scale language model server 200 in response to the request is received, the wish candidates of the care recipient are displayed on the display device 44 based on the received estimation result, as shown in FIG. 5. Here, the care provider selects one of the displayed candidates. In the example of FIG. 5, "I want to go home," "I want to continue living at home," and "I want to be able to walk" are displayed as wish candidates, and the care provider selects, for example, "I want to go home." When a wish is selected, the process proceeds to step S104, and the selected wish is input from the input device 40.

[0044] Next, the process proceeds to step S106, where input of the wishes of the family of the care recipient is requested, and the wishes of the family of the care recipient are input via the input device 40.

[0045] FIG. 6 is a screen showing a care management table when a goal is input from multiple candidates. Next, the process proceeds to step S108, and when the input of the goal is requested, a display process of the goal candidates is executed. In this display process, the goal candidates are displayed on the display device 44 as follows. In the care support device 100, a request including the wishes input in steps S104 and S106 and a request to generate goal candidates is generated and transmitted to the large-scale language model server 200. The request may be, for example, "The wish of the subject in providing care to the subject is XX. The wish of the subject's family is XX." or "Please provide goal candidates for realizing these wishes in providing care to the subject." When the care support device 100 receives the estimation result output from the large-scale language model server 200 in response to the request, the display device 44 displays the goal candidates for realizing the wishes as shown in FIG. 6 based on the received estimation result. Here, the care provider selects one of the displayed candidates. In the example of FIG. 6, "perform daily rehabilitation," "spend time without anxiety in a facility," "reduce the burden of care on the family," and "be able to go to the toilet" are displayed as goal candidates, and the care provider selects, for example, "perform daily rehabilitation" from among these. When the target is selected, the process proceeds to step S110, where the selected target is input from the input device 40.

[0046] FIG. 7 is a screen showing a care management table when a task is input from multiple candidates. Next, the process proceeds to step S112, and when input of a task is requested, a display process of task candidates is executed. In this display process, task candidates are displayed on the display device 44 as follows. In the care support device 100, a request including the goal input in step S110 and a request to generate task candidates is generated and transmitted to the large-scale language model server 200. The request may be, for example, "The goal of care when providing care to the subject is XX." and "Please give candidates of tasks that need to be solved to achieve this goal." In the care support device 100, when an estimation result output from the large-scale language model server 200 in response to the request is received, as shown in FIG. 7, candidates of tasks that need to be solved to achieve the goal are displayed on the display device 44 based on the received estimation result. Here, the care provider selects one of the displayed candidates. In the example of FIG. 7, "insufficient amount of water," "low food intake," and "poor bowel control" are displayed as task candidates, and the care provider selects, for example, "insufficient amount of water." When a task is selected, the process proceeds to step S114, and the selected task is input from the input device 40.

[0047] FIG. 8 is a screen showing a care management table when action items are input from a number of candidates. Next, the process proceeds to step S116, and when the input of the action item is requested, a display process of the action item candidates is executed. In this display process, the action item candidates are displayed on the display device 44 as follows. In the care support device 100, a request including the task input in step S114 and a request to generate action item candidates is generated and transmitted to the large-scale language model server 200. The request may be, for example, "The nursing task in providing care to the subject is XX." and "Please provide candidates of action items necessary to solve this task." In the care support device 100, when the estimation result output from the large-scale language model server 200 in response to the request is received, candidates of action items necessary to solve the task are displayed on the display device 44 based on the received estimation result, as shown in FIG. 8. Here, the care provider selects one of the displayed candidates. In the example of FIG. 8, "regular medical check-up," "medication management," and "provision of meals according to the medical condition" are displayed as action item candidates, and the care provider selects, for example, "regular medical check-up." When an action item is selected, the process proceeds to step S118, in which the selected action item is input from the input device 40.

[0048] Although not shown in the figure, the period during which the action item is to be performed (hereinafter referred to as the "period") and the frequency at which the action item is to be performed (hereinafter referred to as the "frequency") can also be input along with the input of the action item. In this case, candidates for the period and the frequency can also be obtained from the large-scale language model server 200. Specifically, a request including the action item and a request to generate candidates for the period and the frequency is generated and transmitted to the large-scale language model server 200. The request may be, for example, "The action item of care to be performed for the subject is XX." or "Please provide candidates for the period and the frequency at which this action item is to be performed." When the care support device 100 receives the estimation result output from the large-scale language model server 200 in response to the request, candidates for the period and the frequency are displayed on the display device 44 based on the received estimation result. Here, the care provider inputs the period and the frequency by selecting one of the displayed candidates. It is also possible to obtain candidates for only one of the period and the frequency from the large-scale language model server 200, not limited to both the period and the frequency.

[0049] Next, the process proceeds to step S120, and when an input of a deadline for achieving the goal (hereinafter referred to as the "deadline") is requested, a display process of candidates for the deadline is executed. In this display process, candidates for the deadline are displayed on the display device 44 as follows. In the care support device 100, a request including the goal input in step S110 and a request to generate candidates for the deadline is generated and transmitted to the large-scale language model server 200. The request may be, for example, "The goal of care when providing care to the subject is XX." or "Please provide candidates for the deadline for achieving this goal." In the care support device 100, when an estimation result output from the large-scale language model server 200 in response to the request is received, candidates for the deadline for achieving the goal are displayed on the display device 44 based on the received estimation result. Here, the care provider selects one of the displayed candidates. When the deadline is selected, the process proceeds to step S122, and the selected deadline is input from the input device 40.

[0050] Next, the process proceeds to step S124, where input of update contents is requested, and update contents for the previous input are input from the input device 40.

[0051] Next, the process proceeds to step S126, where input of the achievement rate is requested, and the achievement rate (percentage) of the goal is input from the input device 40.

[0052] Next, the process proceeds to step S128, where input of the realization rate is requested, and the desired realization rate (percentage) is input from the input device 40. The realization rate is input based on responses from the care recipient or family members.

[0053] Next, the process proceeds to step S130, where input of the wish realization history is requested, and the wish realization history including the dates when the wishes were realized is input from the input device 40. The wish realization history is input based on responses from the care recipient or family members.

[0054] Next, the process proceeds to step S132, where input of the goal achievement history is requested, and the goal achievement history including the dates on which the goals were achieved is input from the input device 40.

[0055] Next, the process proceeds to step S134, and care management information including the name, wishes of the care recipient, wishes of the family, goals, tasks, implementation items (or implementation period and implementation frequency), achievement deadline, update contents, achievement rate, realization rate, wish realization history, and goal achievement history inputted in steps S100, S104, S106, S110, S114, S118, S122 to S132 is registered in the storage device 42. Care management information is registered for each care recipient.

[0056] Then, proceeding to step S136, for each care recipient, the name, wishes of the care recipient, wishes of the family, goals, tasks, implementation items (or implementation period and implementation frequency), achievement deadline, update contents, achievement rate, realization rate, wish realization history, and goal achievement history are displayed on the display device 44 based on the care management information in the storage device 42. For example, each item in the care management table of Figs. 5 to 8 is displayed in the corresponding item column of the care management information.

[0057] Next, a case where a schedule for carrying out action items (hereinafter referred to as a "schedule") is created will be described.

[0058] The CPU 30 starts a predetermined program stored in a predetermined area of ​​the ROM 32, and executes a schedule creation process shown in the flowchart of FIG. 9 in accordance with the program.

[0059] FIG. 9 is a flowchart showing the schedule creation process. The schedule creation process is initiated in response to a request from a user such as a care provider, and when executed by the CPU 30, first the process proceeds to step S200 as shown in FIG.

[0060] FIG. 10 shows the screen for inputting the action items, implementation period, and implementation frequency. In steps S200 to S204, the action items, the action period, and the action frequency (hereinafter collectively referred to as "action items, etc.") are input. For example, when the care provider selects any of the care management information in the storage device 42, the selected care management information is read from the storage device 42, and the action items, etc. included in the read care management information are input as initial values ​​to the screen of FIG. 10.

[0061] In the example of FIG. 10, three implementation items are input. In the first line, "regular medical examination" is input as the implementation item, "2024 / 4 / 1-2024 / 4 / 30" is input as the implementation period, and "once a month" is input as the implementation frequency. This indicates that a regular medical examination will be performed once a month for the care recipient during the period from 2024 / 4 / 1-2024 / 4 / 30. Similarly, the second line indicates that medication management will be performed once a day for the care recipient during the period from 2024 / 4 / 1-2024 / 6 / 30, and the third line indicates that meals according to the medical condition will be provided to the care recipient three times a week during the period from 2024 / 4 / 1-2024 / 5 / 31. The contents of the implementation items input from the care management information can be changed on the screen of FIG. 10. If the care provider wants to add more implementation items, the care provider can add a row by clicking the "Add Row" button and input the implementation items. Then, when the input contents of the action items are confirmed, the care provider clicks the "Confirm" button.

[0062] FIG. 11 shows a screen displaying schedule candidates. FIG. 12 shows a screen displaying details of a schedule candidate.

[0063] Next, the process proceeds to step S206, where a display process of schedule candidates is executed. In this display process, schedule candidates are displayed on the display device 44 as follows. In the care support device 100, a request including the action items input in steps S200 to S204 and a request to generate schedule candidates is generated and transmitted to the large-scale language model server 200. The request may be, for example, "The action items, implementation period, and implementation frequency of care to be performed for the subject are XX." "Based on these action items, implementation period, and implementation frequency, please create multiple candidates for a schedule in one-week units for carrying out these action items. Please output the results in a list." When the care support device 100 receives the estimation results output from the large-scale language model server 200 in response to the request, the display device 44 displays schedule candidates based on the received estimation results, as shown in FIG. 11. A "details" button is displayed for each candidate. When the care provider clicks the "details" button, the details of the schedule are displayed as shown in FIG. 12, and the details can be confirmed. Then, the care provider selects one of the displayed candidates on the screen of Fig. 11 and clicks the "Decide" button. When the "Decide" button is clicked, the process goes to step S208 and the schedule is selected.

[0064] Next, the process proceeds to step S210 to determine whether a request to edit the selected schedule has been input, and if it is determined that a request to edit the schedule has been input (YES), the process proceeds to step S212 to display a screen for editing the selected schedule. The care provider can edit the schedule on this screen.

[0065] Next, the process proceeds to step S214, where schedule information regarding the selected schedule is registered in the storage device 42. The schedule information is registered in association with the care management information.

[0066] Then, the process proceeds to step S216, where the selected schedule is displayed on the display device 44. If the schedule is for a week, the schedule is displayed as a weekly schedule table as shown in FIG.

[0067] Next, the effects of this embodiment will be described. In this embodiment, a request including actions to be taken for the care recipient and a request to generate schedule candidates is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the sent request is received, and a schedule is displayed based on the received estimation result.

[0068] This allows for obtaining schedule candidates, so that even a care provider with little experience can create a schedule or provide care.

[0069] Furthermore, in this embodiment, a request including a request to generate a desired candidate is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the sent request is received, and the desired candidate is displayed based on the received estimation result.

[0070] This allows desired candidates to be obtained, so that even a care provider with little experience can create a care plan or provide care.

[0071] Furthermore, in this embodiment, a request including the desire input in steps S104 and S106 and including a request to generate target candidates is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and target candidates are displayed based on the received estimation result.

[0072] This allows for obtaining goal candidates that take into account the wishes of the caregiver, so that even a care provider with little experience can create a care plan or provide care.

[0073] Furthermore, in this embodiment, a request including the goal input in step S110 and including a request to generate task candidates is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and task candidates are displayed based on the received estimation result.

[0074] This allows for candidate tasks that take the goal into consideration, so that even a care provider with little experience can create a care plan or provide care.

[0075] Furthermore, in this embodiment, a request including the task input in step S114 and including a request to generate candidates for action items is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and candidates for action items are displayed based on the received estimation result.

[0076] This provides candidates for action items that take the issues into consideration, allowing even inexperienced care providers to create care plans or provide care.

[0077] Furthermore, in this embodiment, a request including the goal input in step S110 and including a request to generate candidates for the achievement deadline is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and candidates for the achievement deadline are displayed based on the received estimation result.

[0078] This allows for obtaining candidates for deadlines that take the goals into consideration, so that even care providers with little experience can create care plans or provide care.

[0079] In this embodiment, step S206 corresponds to the input means of the first invention or the acquisition means of the first invention.

[0080] [Modifications] In the above embodiment and its modified example, the display process in step S102 generates a request including a request to generate desired candidates, but the request is not limited to this and may include other information. For example, a request including attributes of the care recipient (e.g., gender, age, blood type, level of care required, living environment, disease name, level of cognitive function, details of symptoms related to cognitive function, physical level, excretion status, dietary status, economic level, and information on drug use status; the same applies below) and including a request to generate desired candidates can be generated. This makes it possible to obtain desired candidates that take into account the attributes of the care recipient.

[0081] In the above embodiment and its modified example, the display process in step S108 generates a request including the wishes input in steps S104 and S106 and a request to generate target candidates, but the request is not limited to this and may include other information. For example, a request can be generated that includes the attributes of the care recipient and the wishes input in steps S104 and S106 and includes a request to generate target candidates. This makes it possible to obtain target candidates that take into account the attributes of the care recipient.

[0082] In the above embodiment and its modified example, the display process in step S112 generates a request including the goal input in step S110 and including a request to generate task candidates, but the request is not limited to this and may include other information. For example, a request can be generated that includes the desires input in steps S104 and S106 and the goal input in step S110 and includes a request to generate task candidates. This makes it possible to obtain task candidates that take the desires into consideration. Also, for example, a request can be generated that includes the attributes, desires, and goals of the care recipient and includes a request to generate task candidates.

[0083] In the above embodiment and its modified example, in the display process of step S116, a request including the task input in step S114 and a request to generate candidates for action items is generated, but the request may include other information. For example, a request including the goal input in step S110 and the task input in step S114 and a request to generate candidates for action items can be generated. This makes it possible to obtain candidates for action items that take the goal into consideration. For example, a request including hope, goal, and task and a request to generate candidates for action items can be generated. For example, a request including the attributes, hope, goal, and task of the care recipient and a request to generate candidates for action items can be generated.

[0084] In addition, in the above embodiment and its variations, information on four items, namely, hopes, goals, tasks, and implementation items, is registered, but this is not limited to this, and information on at least one of these items can also be registered.

[0085] In the above embodiment and its modified example, information on four items, hope, goal, task, and implementation, is selectively input, but the present invention is not limited to this, and information on at least one of these items may be selectively input. For example, the following configuration may be adopted.

[0086] [Configuration 1] A request including some of the desires, goals, and challenges and including a request to generate candidates for the remaining parts is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and candidates are displayed based on the received estimation result.

[0087] Explain the relationship between hopes, goals and challenges in Structure 1. FIG. 13 is a conceptual diagram showing the connection between hopes, goals, and challenges.

[0088] For one wish, one or more goals are set to realize it, as shown in FIG. 13. In the example of FIG. 13, goal 1-1, goal 1-2, and other goals are set for wish 1, and goal 2-1, goal 2-2, and other goals are set for wish 2. Since the goals to be set correspond to each wish, goals 1-1, 1-2, 2-1, and 2-2 may have the same or similar tendencies or contents, but are basically independent of each other. The care provider hears the wishes of the care recipient and writes the heard wishes in the care management table. Then, the care provider sets a goal to realize the wish based on his / her own experience, care history, etc., and writes the set goal in the care management table. One or more goals may be set as necessary.

[0089] Next, for each goal, one or more tasks that need to be solved to achieve the goal are set. In the example of FIG. 13, task 1-1-1, task 1-1-2, and other tasks are set for goal 1-1, task 1-2-1, task 1-2-2, and other tasks are set for goal 1-2, task 2-1-1, task 2-1-2, and other tasks are set for goal 2-1, and task 2-2-1, task 2-2-2, and other tasks are set for goal 2-2. Since the tasks to be set correspond to each goal, tasks 1-1-1, 1-1-2, 1-2-1, 1-2-2, 2-1-1, 2-1-2, 2-2-1, and 2-2-2 may have the same or similar tendencies or contents, but are basically independent of each other. The care provider sets tasks that need to be solved to achieve the above-mentioned set goals based on their own experience and care history, and enters the set tasks in the care management table. One or more tasks may be set as necessary.

[0090] For cooperation with the large-scale language model server 200, for example, configurations 1A and 1B can be adopted.

[0091] [Configuration 1A] A request including one piece of information among hopes, goals, and problems, and including a request to generate one or two pieces of information other than the hopes, goals, and problems, is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request, and candidates are displayed based on the received estimation result.

[0092] Hereinafter, the notation "A / B" refers to a configuration in which a request including A and a request to generate B is sent to the large-scale language model server 200, and an inference result B output from the large-scale language model server 200 in response to the request is received. Configuration 1A includes the following configurations: "hope / goal", "hope / challenge", "goal / hope", "goal / challenge", "challenge / hope", "challenge / goal", "hope / goal and challenge", "goal / hope and challenge", "challenge / hope and goal".

[0093] [Configuration 1B] A request including two pieces of information out of hope, goal, and problem is sent to the large-scale language model server 200, including a request to generate information other than the hope, goal, and problem, an estimation result output from the large-scale language model server 200 in response to the request, and candidates are displayed based on the received estimation result.

[0094] Structure 1B includes the following structures: "Hope and goals / challenges," "Hope and challenges / goals," and "Goals and challenges / hopes."

[0095] [Configuration 2] A request including some of the wishes, goals, and actions and a request to generate candidates for the remaining parts is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and candidates are displayed based on the received estimation result.

[0096] The relationship between hopes, goals and implementation items in Structure 2 is explained. FIG. 14 is a conceptual diagram showing the connection relationship between hopes, goals, and actions.

[0097] For one wish, one or more goals are set to realize it, as shown in FIG. 14. In the example of FIG. 14, goal 1-1, goal 1-2, and other goals are set for wish 1, and goal 2-1, goal 2-2, and other goals are set for wish 2. Since the goals to be set correspond to each wish, goals 1-1, 1-2, 2-1, and 2-2 may have the same or similar tendencies or contents, but are basically independent of each other. The care provider hears the wishes of the care recipient and writes the heard wishes in the care management table. Then, the care provider sets a goal to realize the wish based on his / her own experience, care history, etc., and writes the set goal in the care management table. One or more goals may be set as necessary.

[0098] Next, for one goal, one or more action items are set that are necessary to solve the problem that needs to be solved to achieve the goal. In the example of Figure 14, action item 1-1-1, action item 1-1-2, and other action items are set for goal 1-1, action item 1-2-1, action item 1-2-2, and other action items are set for goal 1-2, action item 2-1-1, action item 2-1-2, and other action items are set for goal 2-1, and action item 2-2-1, action item 2-2-2, and other action items are set for goal 2-2. Since the action items to be set correspond to each goal, action items 1-1-1, 1-1-2, 1-2-1, 1-2-2, 2-1-1, 2-1-2, 2-2-1, and 2-2-2 may have the same or similar tendencies or contents, but are basically independent of each other. Based on their own experience and care history, the care provider sets the action items necessary to solve the problems that need to be solved in order to achieve the above-mentioned set goals, and enters the action items that have been set in the care management table. One or more action items may be set as necessary.

[0099] For cooperation with the large-scale language model server 200, for example, configurations 2A and 2B can be adopted.

[0100] [Configuration 2A] A request including one piece of information among hopes, goals, and implementation items and including a request to generate one or two other pieces of information among hopes, goals, and implementation items is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and candidates are displayed based on the received estimation result.

[0101] Structure 2A includes the following structures: "hope / goal," "hope / action items," "goal / hope," "goal / action items," "action items / hope," "action items / goal," "hope / goal and action items," "goal / hope and action items," and "action items / hope and goal."

[0102] [Configuration 2B] A request including two pieces of information out of desires, goals, and actions, and including a request to generate information other than the desires, goals, and actions, is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request, and candidates are displayed based on the received estimation result.

[0103] Structure 2B includes the following structures: "Hope and goals / action items," "Hope and action items / goals," and "Goals and action items / hopes."

[0104] [Configuration 3] A request including some of the desires, issues, and actions and a request to generate candidates for the remaining parts is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and candidates are displayed based on the received estimation result.

[0105] The relationship between hopes, challenges and implementation items in Structure 3 is explained. FIG. 15 is a conceptual diagram showing the connection relationship between hopes, issues, and action items.

[0106] For one wish, one or more tasks that need to be solved to achieve the goal to realize the wish are set, as shown in FIG. 15. In the example of FIG. 15, task 1-1, task 1-2, and other tasks are set for wish 1, and task 2-1, task 2-2, and other tasks are set for wish 2. Since the tasks to be set correspond to each wish, tasks 1-1, 1-2, 2-1, and 2-2 may have the same or similar tendencies or contents, but are basically independent of each other. The care provider hears the wishes of the care recipient and writes the heard wishes in the care management table. Then, the care provider sets the tasks that need to be solved to achieve the goal to realize the wish based on his / her own experience, care history, etc., and writes the set tasks in the care management table. One or more tasks may be set as necessary.

[0107] Next, for each problem, one or more action items necessary to solve the problem are set. In the example of FIG. 15, action items 1-1-1, 1-1-2, and other action items are set for problem 1-1, action items 1-2-1, 1-2-2, and other action items are set for problem 1-2, action items 2-1-1, 2-1-2, and other action items are set for problem 2-1, and action items 2-2-1, 2-2-2, and other action items are set for problem 2-2. Since action items to be set correspond to each problem, action items 1-1-1, 1-1-2, 1-2-1, 1-2-2, 2-1-1, 2-1-2, 2-2-1, and 2-2-2 may have the same or similar tendencies or contents, but are basically independent of each other. The care provider sets the action items necessary to solve the problem set above based on his / her own experience and care history, and enters the set action items in the care management table. One or more implementation items may be set as necessary.

[0108] For cooperation with the large-scale language model server 200, for example, configurations 3A and 3B can be adopted.

[0109] [Configuration 3A] A request including one piece of information among hopes, tasks, and actions, and including a request to generate one or two other pieces of information among hopes, tasks, and actions, is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request, and candidates are displayed based on the received estimation result.

[0110] Structure 3A includes the following structures: "hopes / issues," "hopes / implementations," "issues / hopes," "issues / implementations," "implementations / hopes," "implementations / issues," "hopes / issues and implementation items," "issues / hopes and implementation items," and "implementations / hopes and issues."

[0111] [Configuration 3B] A request including two pieces of information out of hopes, tasks, and actions, and including a request to generate information other than the hopes, tasks, and actions, is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request, and candidates are displayed based on the received estimation result.

[0112] Structure 3B includes the following structures: "Hope and issues / items to be implemented," "Hope and issues / items to be implemented," and "Issues and issues / hopes."

[0113] [Configuration 4] A request including some of the goals, tasks, and action items and including a request to generate candidates for the remaining parts is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and candidates are displayed based on the received estimation result.

[0114] The relationship between the goals, tasks, and implementation items in Structure 4 is explained. FIG. 16 is a conceptual diagram showing the connection relationship between goals, tasks, and action items.

[0115] For one goal, one or more tasks that need to be solved to achieve the goal are set, as shown in FIG. 16. In the example of FIG. 16, task 1-1, task 1-2, and other tasks are set for goal 1, and task 2-1, task 2-2, and other tasks are set for goal 2. Since tasks to be set correspond to each goal, tasks 1-1, 1-2, 2-1, and 2-2 may have the same or similar tendencies or contents, but are basically independent of each other. The care provider hears the wishes of the care recipient, sets a goal to realize the wishes heard based on his / her own experience and care history, and writes the set goal in the care management table. Then, the care provider sets a task that needs to be solved to achieve the above goal based on his / her own experience and care history, and writes the set task in the care management table. One or more tasks may be set as necessary.

[0116] Next, for each problem, one or more action items necessary to solve the problem are set. In the example of FIG. 16, action items 1-1-1, 1-1-2, and other action items are set for problem 1-1, action items 1-2-1, 1-2-2, and other action items are set for problem 1-2, action items 2-1-1, 2-1-2, and other action items are set for problem 2-1, and action items 2-2-1, 2-2-2, and other action items are set for problem 2-2. Since action items to be set correspond to each problem, action items 1-1-1, 1-1-2, 1-2-1, 1-2-2, 2-1-1, 2-1-2, 2-2-1, and 2-2-2 may have the same or similar tendencies or contents, but are basically independent of each other. The care provider sets the action items necessary to solve the problem set above based on his / her own experience and care history, and enters the set action items in the care management table. One or more implementation items may be set as necessary.

[0117] For cooperation with the large-scale language model server 200, for example, configurations 4A and 4B can be adopted.

[0118] [Configuration 4A] A request including one piece of information among the goal, tasks, and action items and including a request to generate one or two other pieces of information among the goal, tasks, and action items is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and candidates are displayed based on the received estimation result.

[0119] Structure 4A includes the following structures: "Goals / challenges", "Goals / implementations", "Challenges / goals", "Challenges / implementations", "Implementations / goals", "Implementations / goals", "Goals / goals and implementations", "Challenges / goals and implementations", and "Implementations / goals and challenges".

[0120] [Configuration 4B] A request including two pieces of information among the goal, tasks, and action items and including a request to generate information other than the goal, tasks, and action items is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and candidates are displayed based on the received estimation result.

[0121] Structure 4B includes the following structures: "Objectives and issues / implementation items," "Objectives and implementation items / issues," and "Issues and implementation items / objectives."

[0122] [Configuration 5] A request including some of the desires, goals, tasks, and actions and a request to generate candidates for the remaining parts is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and candidates are displayed based on the received estimation result.

[0123] For example, configurations 5A, 5B, and 5C can be adopted for cooperation with the large-scale language model server 200. Note that configurations 5A, 5B, and 5C include the above-described embodiment and their modifications.

[0124] [Configuration 5A] A request including one piece of information among hopes, goals, tasks, and implementation items and including a request to generate one, two, or three pieces of information other than the hopes, goals, tasks, and implementation items is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and candidates are displayed based on the received estimation result.

[0125] Structure 5A includes the following structures: "Hope / goal", "Hope / challenge", "Hope / implementation items", "Goal / hope", "Goal / challenge", "Goal / implementation items", "Challenges / hope", "Challenges / goal", "Challenges / implementation items", "Implementation items / hope", "Implementation items / goal", "Implementation items / challenges", "Hope / goal and challenges", "Hope / goal and implementation items", "Hope / challenges and implementation items", "Goal / hope and challenges", "Goal / hope and implementation items", "Goal / challenges and implementation items", "Challenges / hope and goals", "Challenges / goal and implementation items", "Implementation items / hope and goals", "Implementation items / hope and challenges", "Implementation items / goal and challenges", "Hope / goal, challenges and implementation items", "Challenges / hope, goal and implementation items", "Implementation items / hope, goal and challenges".

[0126] [Configuration 5B] A request including two pieces of information among hopes, goals, tasks, and implementation items and including a request to generate one or two pieces of information other than the hopes, goals, tasks, and implementation items is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and candidates are displayed based on the received estimation result.

[0127] Structure 5B includes the following structures: "Hope and goals / challenges", "Hope and goals / implementations", "Hope and challenges / goals", "Hope and challenges / implementations", "Hope and implementations / goals", "Hope and implementations / challenges", "Goals and challenges / hopes", "Goals and challenges / implementations", "Goals and implementations / hopes", "Goals and implementations / challenges", "Challenges and implementations / hopes", "Challenges and implementations / goals", "Hope and goals / challenges and implementations", "Hope and issues / goals and implementations", "Hope and implementations / goals and challenges", "Goals and challenges / hopes and implementations", "Goals and implementations / hopes and issues", "Challenges and implementations / hopes and goals".

[0128] [Configuration 5C] A request including three pieces of information among hopes, goals, tasks, and implementation items and including a request to generate information other than the hopes, goals, tasks, and implementation items is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and candidates are displayed based on the received estimation result.

[0129] Structure 5C includes the following structures: "Hope, goals, and issues / implementations," "Hope, goals, and issues / implementations," and "Goals, goals, and issues / hopes."

[0130] [Configuration 6A] In any of configurations 1A, 1B, 2A, 2B, 3A, 3B, 4A, 4B, and 5A to 5C, the request includes an attribute of the care recipient or includes a request to generate an attribute of the care recipient.

[0131] Configurations for sending a request including attributes include (1) a configuration for sending a request including only attributes and including a generation request, and (2) a configuration for sending a request including attributes and other information (e.g., wishes, goals, tasks, implementation items, implementation period, implementation frequency, schedule, achievement deadline, achievement rate or realization rate, information about the care provider (e.g., attributes, daily plans, information about the means of transportation used; the same applies below), and other information) (hereinafter, this "other information" is the same in (4) and 6A2 to 6A4 below.) and including a generation request.

[0132] The configuration of transmitting a request including a request to generate attributes includes (3) a configuration of transmitting a request including a request to generate only attributes, and (4) a configuration of transmitting a request including a request to generate attributes and other information. Note that requests (3) and (4) can include information other than the generation request, like requests (1) and (2).

[0133] Moreover, the following configurations can be adopted as application examples of configuration 6A. Note that among the following configurations, configurations 6A1 to 6A5 do not assume configurations 1A, 1B, 2A, 2B, 3A, 3B, 4A, 4B, and 5A to 5C.

[0134] [Configuration 6A1] This is a configuration combining (1) and (3), in which a request including only the attributes of the care recipient and a request to generate only the attributes of the care recipient is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and the received estimation result is displayed.

[0135] [Configuration 6A2] This is a combination of (1) and (4), in which a request including only the attributes of the care recipient and a request to generate the attributes and other information of the care recipient is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and the received estimation result is displayed.

[0136] [Configuration 6A3] is a combination of (2) and (3), in which a request including attributes of the care recipient and other information and including a request to generate only the attributes of the care recipient is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and the received estimation result is displayed.

[0137] [Configuration 6A4] is a combination of (2) and (4), in which a request including attributes and other information of the care recipient and a request to generate the attributes and other information of the care recipient is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and the received estimation result is displayed.

[0138] [Configuration 6A5] In configurations 6A1 to 6A4, information about the care recipient (e.g., attributes, daily schedule, distance to the facility, travel time to the facility, travel cost to the facility, information on the means of transportation used to get to the facility; the same applies below) is used instead of the attributes of the care recipient.

[0139] [Configuration 6A6] This is a configuration in which Configurations 1A, 1B, 2A, 2B, 3A, 3B, 4A, 4B, 5A to 5C, 6B, 6B1 to 6B6, 7, 7A to 7E, 8, 8A to 8E, 9, and 10 are applied to Configurations 6A1 to 6A5.

[0140] [Configuration 6B] In configurations 1A, 1B, 2A, 2B, 3A, 3B, 4A, 4B, 5A-5C, 6A, 6A1-6A6, the request includes attributes of the care provider (e.g., gender, age, years of work experience, and other information on work experience; the same applies below), or includes a request to generate attributes of the care provider. Here, care providers include, for example, those who have cared for a care recipient (past), those who are caring for a care recipient (present), those who plan to care for a care recipient (future), and those who have a specified relationship with these persons (e.g., those with the same years of work, years of experience, number of people in charge, and other achievements or within a specified range).

[0141] Configurations for sending a request including attributes include (1) a configuration for sending a request including only attributes and including a generation request, and (2) a configuration for sending a request including attributes and other information (e.g., hopes, goals, tasks, implementation items, implementation period, implementation frequency, schedule, achievement deadline, achievement rate or realization rate, information about the care recipient, and other information) (hereinafter, this "other information" is the same in (4) below, 6B2 to 6B4.) and including a generation request.

[0142] The configuration of transmitting a request including a request to generate attributes includes (3) a configuration of transmitting a request including a request to generate only attributes, and (4) a configuration of transmitting a request including a request to generate attributes and other information. Note that requests (3) and (4) can include information other than the generation request, like requests (1) and (2).

[0143] Moreover, the following configurations can be adopted as application examples of configuration 6B. Note that among the following configurations, configurations 6B1 to 6B5 do not assume configurations 1A, 1B, 2A, 2B, 3A, 3B, 4A, 4B, 5A to 5C, 6A, and 6A1 to 6A6.

[0144] [Configuration 6B1] This is a configuration combining (1) and (3), in which a request including only the attributes of a care provider and a request to generate only the attributes of the care provider is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and the received estimation result is displayed.

[0145] [Configuration 6B2] This is a combination of (1) and (4), in which a request including only the attributes of a care provider and a request to generate the attributes and other information of the care provider is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and the received estimation result is displayed.

[0146] [Configuration 6B3] This is a combination of (2) and (3), in which a request including a care provider's attributes and other information and a request to generate only the care provider's attributes is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and the received estimation result is displayed.

[0147] [Configuration 6B4] This is a combination of (2) and (4), in which a request including attributes and other information of a care provider and a request to generate the attributes and other information of a care provider is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and the received estimation result is displayed.

[0148] [Configuration 6B5] In configurations 6B1 to 6B4, information on the care provider is used instead of the attributes of the care provider.

[0149] [Configuration 6B6] This is a configuration in which Configurations 1A, 1B, 2A, 2B, 3A, 3B, 4A, 4B, 5A to 5C, 6A, 6A1 to 6A6, 7, 7A to 7E, 8, 8A to 8E, 9, and 10 are applied to Configurations 6B1 to 6B5.

[0150] [Configuration 7] In configurations 1A, 1B, 2A, 2B, 3A, 3B, 4A, 4B, 5A to 5C, 6A, 6A1 to 6A6, 6B, and 6B1 to 6B6, the request includes an achievement deadline, an achievement rate, or a realization rate, or includes a request to generate an achievement deadline, an achievement rate, or a realization rate.

[0151] Configurations for sending a request including a deadline for achievement include (1) a configuration for sending a request including only the deadline for achievement and the achievement rate or realization rate and including a request for generation, and (2) a configuration for sending a request including the deadline for achievement, the achievement rate or realization rate and other information (e.g., hopes, goals, tasks, implementation items, implementation period, implementation frequency, schedule, information about the care recipient, information about the care provider, and other information) (hereinafter, this "other information" is the same in (4) and 7B to 7D below.) and including a request for generation.

[0152] The configuration of transmitting a request including a request to generate an achievement deadline, achievement rate, or realization rate includes (3) a configuration of transmitting a request including a request to generate only an achievement deadline, achievement rate, or realization rate, and (4) a configuration of transmitting a request including a request to generate an achievement deadline, achievement rate, or realization rate, and other information. Note that requests (3) and (4) can include information other than the generation request, like requests (1) and (2).

[0153] Moreover, the following configurations can be adopted as application examples of configuration 7. Note that among the following configurations, configurations 7A to 7D do not assume configurations 1A, 1B, 2A, 2B, 3A, 3B, 4A, 4B, 5A to 5C, 6A, 6A1 to 6A6, 6B, and 6B1 to 6B6.

[0154] [Configuration 7A] is a configuration combining (1) and (3), in which a request including only the deadline, the achievement rate, or the realization rate and including a request to generate only the deadline, the achievement rate, or the realization rate is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and the received estimation result is displayed.

[0155] [Configuration 7B] This is a combination of (1) and (4), in which a request including only the achievement deadline, achievement rate or realization rate and a request to generate the achievement deadline, achievement rate or realization rate and other information is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and the received estimation result is displayed.

[0156] [Configuration 7C] is a combination of (2) and (3), in which a request including a deadline, an achievement rate or realization rate, and other information and a request to generate only the deadline, the achievement rate, or the realization rate is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and the received estimation result is displayed.

[0157] [Configuration 7D] is a combination of (2) and (4), in which a request including a deadline, an achievement rate or realization rate, and other information and a request to generate the deadline, an achievement rate or realization rate, and other information is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and the received estimation result is displayed.

[0158] [Configuration 7E] This is a configuration in which Configurations 1A, 1B, 2A, 2B, 3A, 3B, 4A, 4B, 5A to 5C, 6A, 6A1 to 6A6, 6B, 6B1 to 6B6, 8, 8A to 8E, 9, and 10 are applied to Configurations 7A to 7D.

[0159] [Configuration 8] In configurations 1A, 1B, 2A, 2B, 3A, 3B, 4A, 4B, 5A to 5C, 6A, 6A1 to 6A6, 6B, 6B1 to 6B6, 7, and 7A to 7E, the request includes an action item, an action period, or an action frequency, or includes a request to generate an action item, an action period, or an action frequency.

[0160] Configurations for sending a request including an implementation item, implementation period, or implementation frequency include (1) a configuration for sending a request including only the implementation item, implementation period, or implementation frequency and including a generation request, and (2) a configuration for sending a request including the implementation item, implementation period, or implementation frequency and other information (e.g., hopes, goals, tasks, schedule, deadline for achievement, achievement rate or realization rate, information about the care recipient, information about the care provider, and other information) (hereinafter, this "other information" is the same in (4) below and 8B to 8D.) and including a generation request.

[0161] The configuration for transmitting a request including a request to generate an action item, an implementation period, or an implementation frequency includes (3) a configuration for transmitting a request including a request to generate only an action item, an implementation period, or an implementation frequency, and (4) a configuration for transmitting a request including a request to generate an action item, an implementation period, or an implementation frequency and other information. Note that the requests in (3) and (4) can include information other than the generation request, like the requests in (1) and (2).

[0162] Moreover, the following configurations can be adopted as application examples of configuration 8. Of the following configurations, configurations 8A to 8D do not assume configurations 1A, 1B, 2A, 2B, 3A, 3B, 4A, 4B, 5A to 5C, 6A, 6A1 to 6A6, 6B, 6B1 to 6B6, 7, and 7A to 7E.

[0163] [Configuration 8A] This is a configuration combining (1) and (3), in which a request including only an action item, an action period, or an action frequency and including a request to generate only an action item, an action period, or an action frequency is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and the received estimation result is displayed.

[0164] [Configuration 8B] This is a combination of (1) and (4), in which a request including only the action item, the action period, or the action frequency and a request to generate the action item, the action period, or the action frequency and other information is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and the received estimation result is displayed.

[0165] [Configuration 8C] is a combination of (2) and (3), in which a request including an action item, an implementation period or implementation frequency, and other information and a request to generate only the action item, the implementation period or the implementation frequency is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and the received estimation result is displayed.

[0166] [Configuration 8D] is a combination of (2) and (4), in which a request including an action item, an action period or an action frequency, and other information and a request to generate the action item, the action period or the action frequency, and other information is sent to the large-scale language model server 200, an estimation result output from the large-scale language model server 200 in response to the request is received, and the received estimation result is displayed.

[0167] [Configuration 8E] This is a configuration in which Configurations 1A, 1B, 2A, 2B, 3A, 3B, 4A, 4B, 5A to 5C, 6A, 6A1 to 6A6, 6B, 6B1 to 6B6, 7, 7A to 7E, 9, and 10 are applied to Configurations 8A to 8D.

[0168] [Configuration 9] A configuration for transmitting a request including one of two combinations of information on the care recipient, information on the care provider, hopes, goals, tasks, implementation items, implementation period, implementation frequency, achievement deadline, achievement rate, and realization rate, and including a request to generate the other combination. In this case, the connection relationship as shown in Figure 3 has two levels.

[0169] [Configuration 10] A configuration for transmitting a request including a request for generating any one of information on the care recipient, information on the care provider, hopes, goals, tasks, implementation items, implementation period, implementation frequency, achievement deadline, achievement rate, and realization rate. In this case, the connection relationship as shown in FIG. 3 does not exist.

[0170] In the above embodiment and its modified example, the display process in step S206 generates a request including the action items and a request to generate schedule candidates, but the request may include other information. For example, the following configuration may be adopted.

[0171] (1) The request includes action items and a request to generate a schedule. (2) The request includes an action item and an execution period, and includes a request to generate a schedule.

[0172] (3) The request includes an action item and an action frequency, and includes a request to generate a schedule.

[0173] (4) The request includes an action item, an action period, and an action frequency, and includes a request to generate a schedule.

[0174] (5) The request includes an implementation period and a request to generate a schedule. (6) The request includes an implementation period and implementation frequency and includes a request to generate a schedule.

[0175] (7) The request includes a request to generate a schedule, including an execution frequency. (8) The requests in (1) to (7) may further include attributes of the care recipient, or may include only attributes of the care recipient and a request to generate a schedule.

[0176] (9) The requests in (1) to (8) may further include attributes of a care provider, or may include only attributes of a care provider and a request to generate a schedule.

[0177] (10) The requests in (1)-(9) may further include information about the care recipient, or may be requests that include only information about the care recipient and a request to generate a schedule.

[0178] (11) The requests in (1) to (10) may further include information about the care provider, or may include only information about the care provider and a request to generate a schedule.

[0179] (12) In the combined relationship of hope, goal, task, and action items shown in Fig. 3, the requests of (1) to (11) further include hope, goal, task, deadline, achievement rate, or realization rate. Alternatively, the requests may include only hope, goal, task, deadline, achievement rate, or realization rate, and may include a request to generate a schedule.

[0180] (13) In the combined relationship of hope, goal, and task shown in Fig. 13, the requests (1) to (11) further include hope, goal, task, deadline, achievement rate, or realization rate. Alternatively, the requests may include only hope, goal, task, deadline, achievement rate, or realization rate, and may include a request to generate a schedule.

[0181] (14) In the combined relationship between the hope, the goal, and the action items shown in Fig. 14, the requests (1) to (11) further include the hope, the goal, the deadline, the achievement rate, or the realization rate. Alternatively, the requests may include only the hope, the goal, the deadline, the achievement rate, or the realization rate, and may include a request to generate a schedule.

[0182] (15) In the combined relationship of the hope, task, and action items shown in Fig. 15, the requests (1) to (11) further include the hope, task, or realization rate. Alternatively, the requests may include only the hope, task, or realization rate, and may include a request to generate a schedule.

[0183] (16) In the binding relationship between the goal, task, and action item shown in Fig. 16, the requests (1) to (11) further include the goal, task, deadline, achievement rate, or realization rate. Alternatively, the requests may include only the goal, task, deadline, achievement rate, or realization rate, and may include a request to generate a schedule.

[0184] Furthermore, in the above embodiment and its variations, the display process in step S206 generates a request including implementation items, implementation period, and implementation frequency, and including a request to generate schedule candidates (one or more schedules); however, without being limited to this, it is possible to generate a request including a request to generate one schedule or a request to generate a predetermined number of schedules.

[0185] In addition, in the above embodiment and its modified examples, the terms "goal" and "challenge" are used, but this is not limiting, and the terms "goal" and "challenge" may be defined as "long-term goal" and "short-term goal", respectively, with the same meaning.

[0186] In addition, in the above embodiment and its modified examples, the term "implementation items" is used, but this is not limited thereto, and "implementation items" may be defined as "measures," "services," "service menus," "service items," "service contents," etc., which are equivalent in meaning.

[0187] In addition, in the above embodiment and its variations, the term is defined as "items to be implemented that are necessary to solve the problem," but it is not limited to this and can also be defined as "items to be implemented that are necessary to achieve the goal."

[0188] In addition, in the above embodiment and its modified example, one goal is defined, but it is not limited to this, and two or more goals can be defined, for example, a "long-term goal" and a "short-term goal". When there is a connection between the goals, the above embodiment and its modified example can be similarly applied as a configuration in which each goal is selectively input. This also applies to hopes, issues, and implementation items.

[0189] In addition, in the above embodiment and its variations, a "goal for realizing a hope" and "problems that need to be solved in order to achieve a goal" are defined, but it is also possible to define a "goal for realizing a hope" as an "problem that needs to be solved in order to realize a hope" and a "problem that needs to be solved in order to achieve a goal" as a "goal set to solve the problem".

[0190] In the above embodiment and its modified example, the schedule is generated by a large-scale language model, but the present invention is not limited to this, and the schedule can be estimated by AI (Artificial Intelligence). Specifically, the configuration includes an acquisition means for acquiring input information, and an estimation means for estimating the schedule and other information from the input information acquired by the acquisition means, using a trained model trained based on the same type of information as the input information and the schedule and other information. For example, the following configuration can be adopted.

[0191] (1) The input information includes the implementation items. (2) The input information includes the implementation items and implementation period. (3) The input information includes the items to be implemented and the frequency of implementation.

[0192] (4) The input information includes the implementation items, implementation period, and implementation frequency. (5) Input information includes a request to generate a schedule, including an implementation period.

[0193] (6) Input information includes a request to generate a schedule, including implementation duration and implementation frequency. (7) Input information includes a request to generate a schedule, including implementation frequency.

[0194] (8) The input information in (1) to (7) may further include attributes of the care recipient, or may be a request including only attributes of the care recipient and a request to generate a schedule.

[0195] (9) The input information in (1) to (8) may further include attributes of a care provider, or may be a request including only attributes of a care provider and a request to generate a schedule.

[0196] (10) The input information in (1)-(9) may further include information about the care recipient, or may be a request that includes only information about the care recipient and includes a request to generate a schedule.

[0197] (11) The input information in (1) to (10) may further include information about the care provider, or may be a request that includes only information about the care provider and includes a request to generate a schedule.

[0198] (12) In the combined relationship of the hope, goal, task, and action items shown in Fig. 3, the input information (1) to (11) further includes the hope, goal, task, deadline, achievement rate, or realization rate, or may be a request including only the hope, goal, task, deadline, achievement rate, or realization rate and including a request to generate a schedule.

[0199] (13) In the combined relationship between hope, goal, and task shown in Fig. 13, the input information (1) to (11) further includes hope, goal, task, deadline, achievement rate, or realization rate, or may be a request including only hope, goal, task, deadline, achievement rate, or realization rate and including a request to generate a schedule.

[0200] (14) In the combined relationship between the hope, the goal, and the action items shown in Fig. 14, the input information (1) to (11) further includes the hope, the goal, the deadline, the achievement rate, or the realization rate, or may be a request including only the hope, the goal, the deadline, the achievement rate, or the realization rate, and including a request to generate a schedule.

[0201] (15) In the combined relationship between the hope, the task, and the implementation items shown in Fig. 15, the input information (1) to (11) further includes the hope, the task, or the realization rate. Alternatively, it may be a request including only the hope, the task, or the realization rate and including a request to generate a schedule.

[0202] (16) In the binding relationship between the goal, task, and action item shown in Fig. 16, the input information (1) to (11) further includes the goal, task, deadline, achievement rate, or realization rate, or may be a request including only the goal, task, deadline, achievement rate, or realization rate and including a request to generate a schedule.

[0203] (17) In addition, in the above embodiment and its modified examples, information other than the generation request included in the request to the large-scale language model can be used as input information for the AI, and information output from the large-scale language model in response to the request can be used as output information for the AI. In this case, the trained model learns based on the same type of information as the input information and the output information. Then, the input information is acquired, and the trained model is used to estimate the output information from the acquired input information.

[0204] In the above embodiment and its modified example, the care support device 100 is realized as a single device, but the present invention is not limited to this and can also be realized as a network system. A care support server and multiple user terminals are connected to a network such as the Internet. The care support server is configured to have the same functions as the care support device 100. The difference is that the care support server receives information from the user terminal instead of input by the input device 40, and transmits information to the user terminal instead of displaying on the display device 44.

[0205] Furthermore, in the above embodiment and its modified examples, the storage device 42 included in the care support device 100 is used, but the present invention is not limited to this, and an external storage device such as a database server can also be used.

[0206] In addition, in the above embodiment and its modified examples, when executing the process shown in the flowchart of FIG. 4, a case has been described in which a program pre-stored in ROM 32 is executed. However, this is not limited to the above, and the program showing these procedures may be read from a storage medium in which the program is stored, into RAM 34, and executed.

[0207] Here, storage media refers to semiconductor storage media such as RAM and ROM, magnetic storage type storage media such as FD and HD, optically readable storage media such as CD, CDV, LD and DVD, and magnetic storage type / optically readable storage media such as MO, and includes any storage medium that can be read by a computer, regardless of the reading method (electronic, magnetic, optical, etc.).

[0208] Furthermore, the present invention is not limited to the above-mentioned embodiment and its modified examples, and can be applied to other cases without departing from the spirit of the present invention. For example, the present invention can be applied not only to nursing care, but also to cases in which a caregiver supports the care of a care recipient (looking after, protecting, caring for, nursing, etc.) in the fields of medicine (rehabilitation, treatment, etc.) or welfare (physical, intellectual, mental, etc.). [Explanation of symbols]

[0209] 100...care support device, 30...CPU, 32...ROM, 34...RAM, 38...I / F, 40...input device, 42...storage device, 44...display device, 199...Internet, 200...large-scale language model server

Claims

1. an input means for inputting information about a care recipient, the information including a distance to a facility, a travel time to the facility, a travel cost to the facility, or information about a means of transportation to the facility, into the large-scale language model, the request including a request to generate a schedule for carrying out actions for the care recipient; and acquiring means for acquiring schedule information output from the large-scale language model in response to the request.

2. In claim 1, A care support system characterized in that the request includes the action items, a time period or frequency for performing the action items, or a request to generate the action items, a time period or frequency for performing the action items.

3. In claim 1, A care support system characterized in that the request includes a deadline for achieving a goal for realizing the wishes of the care recipient or his / her family, or a goal to be achieved by solving a problem that needs to be solved in order to realize the wishes, a rate of achievement of the goal, or a rate of realization of the wishes, or includes a request to generate the deadline, the rate of achievement, or the rate of realization.

Images