Information processing apparatus, information processing method, and program

Abstract

To provide an information processor, an information processing method and a program for improving the efficiency of assignment work to a project executer by a project manager.SOLUTION: An information processing apparatus 1 includes a target registration processing unit 31 that registers a plurality of targets of a project, a charge registration processing unit 32 that registers a plurality of executors who are candidates for charge of executing the project, and a charge request management unit 33 that, when receiving a request for assignment of the project to the target from a project manager who manages the project, notifies the executor of the request for charge of the project, receives a response of acceptance or rejection to the request for charge from the executor, and presents the response to the project manager. The executor is set as a formal person in charge of the project.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to an information processing device, an information processing method, and a program. [Background technology]

[0002] The development of a community-based integrated care system is underway, establishing a comprehensive support system to enable those requiring care to continue living independently in their familiar communities. In the field of nursing care in particular, a system in which local medical, nursing care, welfare, and lifestyle support services work together and cooperate is desirable. For example, in the field of nursing care, a community-based integrated care center serves as the support point for elderly care users, while care managers often create care plans, assign care service providers, and manage the progress of the plans. Implementing a care plan requires timely requests, negotiations, and assignments with service providers. However, securing the schedules of busy care managers and service providers, selecting appropriate service providers, and managing the progress of care plans are time-consuming tasks that often lead to overwork for those involved. In nursing care services, improving the quality of services provided to users and securing the necessary personnel and time are necessary, but this is difficult for the reasons mentioned above.

[0003] A technology that supports projects targeting such care recipients using information processing technology such as communication networks is known. Patent Document 1, for example, describes this type of technology. Patent Document 1 relates to a nursing care service management system. In the nursing care service management system of Patent Document 1, a job information registration unit of a management server registers job information from businesses, including the location, time, job content, and working conditions. A job request presentation unit of a smartphone searches the registered job information according to the set conditions and displays a list of job information selectable by the job seeker. Then, an application information management unit of the management server acquires application information for the selected job information and accepts a selection operation from the business that provided the job information. A contract management unit concludes a contract between the business related to the application information and the job seeker based on the application information selected by the business. A work schedule information display unit of the smartphone searches information related to the concluded contract according to the set conditions and displays it as a list of work schedule information. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2024-13985 Summary of the Invention [Problem to be solved by the invention]

[0005] Care managers, who act as project managers, need to assign tasks to other care service providers, doctors, nurses, and other project executors. This type of assignment is not limited to cases where it is decided by a job posting, but may also be made between care managers and supporters who are already acquainted with them. Conventional technology has room for improvement in terms of efficient collaboration between care managers and supporters.

[0006] The present invention has been made in view of the above circumstances, and has as its object to provide an information processing device, an information processing method, and a program that can improve the efficiency of assignment work for project managers to project implementers. [Means for solving the problem]

[0007] In order to achieve the above object, one aspect of the present invention is an information processing device that manages a project, comprising: a target registration processing unit that registers multiple targets of the project; a person in charge registration processing unit that registers multiple implementers who are candidates for being in charge of the project; and a person in charge request management unit that, upon receiving a request for assignment of the target to the project from a project manager who manages the project, notifies the implementer of the request to be in charge of the project, receives a response of acceptance or rejection to the request from the implementer, and presents the response to the project manager; and, upon receiving an assignment instruction from the project manager for the implementer who has accepted the assignment request, the person in charge request management unit sets the implementer as the official person in charge of the project.

[0008] Another aspect of the present invention is an information processing method for an information processing device that manages a project, the information processing method including: a target registration step of registering multiple targets of the project; a person in charge registration step of registering multiple implementers who are candidates for being in charge of the project; and a person in charge request management step of, upon receiving a request from a project manager that manages the project to assign the project to the target, notifying the implementer of the request to be in charge of the project, receiving a response of acceptance or rejection to the request from the implementer and presenting the response to the project manager, and, upon receiving an assignment instruction from the project manager for the implementer who has accepted the assignment request, setting the implementer as the official person in charge of the project.

[0009] Another aspect of the present invention is a computer program for managing a project, the program causing a computer to execute the following steps: a target registration step for registering multiple targets of the project; a person in charge registration step for registering multiple implementers who are candidates for being in charge of the project; and a person in charge request management step for, upon receiving a request for assignment of the target to the project from a project manager who manages the project, notifying the implementer of the request to be in charge of the project, receiving a response of acceptance or rejection to the request from the implementer and presenting the response to the project manager, and, upon receiving an assignment instruction from the project manager for the implementer who has accepted the assignment request, setting the implementer as the official person in charge of the project. [Effects of the Invention]

[0010] According to the present invention, it is possible to provide an information processing device, an information processing method, and a program that can improve the efficiency of the assignment work of a project manager to project implementers. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a diagram showing a project support system to which an information processing device according to an embodiment of the present invention is applied; [Figure 2] 1 is a block diagram showing a hardware configuration of an information processing device according to an embodiment of the present invention; [Figure 3] FIG. 2 is a functional block diagram showing an example of a functional configuration of the information processing device according to the present embodiment. [Figure 4] FIG. 10 is a schematic diagram illustrating an assignment process performed by the information processing device. [Figure 5] 10 is an example of a confirmation screen of the usage status of the project support system displayed on the service provider terminal. [Figure 6] 10 is an example of a response screen to a request for a person in charge. [Figure 7] 10 is an example of a consultation destination setting screen for requesting a person in charge. [Figure 8]10 is an example of a notification screen for a request to be handled when the contact tool is set to email. [Figure 9] 10 is a flowchart illustrating a series of steps until assignment processing is performed by the information processing device. [Figure 10] 10 is an example of an event setting screen displayed on a service provider terminal of an event setter. [Figure 11] 10 is a diagram illustrating an example of a schedule candidate input section of an event setting screen. [Figure 12] 10 is an example of an event notification screen when the contact tool is set to email. [Figure 13] 10 is an example of an event setting screen displayed on a service provider terminal of a participant. [Figure 14] 10 is a flowchart illustrating a series of steps until an event is set by an information processing device. [Figure 15] 10 is an example of a chat screen displayed on a service provider terminal of a participant who has started a chat. [Figure 16] 10 is an example of a message notification screen when the contact tool is set to email. [Figure 17] 10 is an example of a chat screen displayed on a service provider terminal of a participant in a chat room. [Figure 18] 10 is a flowchart illustrating a flow of chat management processing by an information processing device. [Figure 19] 10 is an example of a chat screen displayed on the service provider terminal of the participant in the chat room after data sharing. [Figure 20] 10 is an example of a shared data management screen displayed on a service provider terminal of a data sharer. [Figure 21] 10 is an example of a data sharing notification screen when the contact tool is set to email. [Figure 22] 10 is a flowchart illustrating a flow of a data sharing process performed by an information processing device. DETAILED DESCRIPTION OF THE INVENTION

[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0013] <System configuration> First, the overall system configuration will be described. Fig. 1 is a diagram showing a project support system 100 to which an information processing device 1 according to one embodiment of the present invention is applied. The project support system 100 provides a service to support a project in which multiple project executors participate to carry out work related to a target. The project executors here may be individuals or organizations such as corporations.

[0014] There are no particular limitations on the projects that can be supported by the project support system 100. Below, a case will be described in which the project support system 100 supports a project in which a community comprehensive support center, a care manager, or the like assigns service providers and carries out various types of collaboration for people requiring care.

[0015] The project support system 100 is realized by an information processing device 1 that transmits and receives various information to and from service provider terminals 3-1 to 3-n via a communication network such as the Internet.

[0016] The service provider terminals 3-1 to 3-n are computers used by project implementers who are candidates for project implementation. The service provider terminals 3-1 to 3-n are each used by a different project implementer. The project implementers are care managers, medical practitioners such as doctors, nurses, and other service providers whose project involves supporting support recipients such as care recipients.

[0017] The service provider terminals 3-1 to 3-n are configured by smartphones, tablets, personal computers, etc. The service provider terminals 3-1 to 3-n may transmit and receive various information to and from the information processing device 1 using a pre-installed program, or may transmit and receive various information through a web browser. In the following description, matters common to the service provider terminals 3-1 to 3-n may be simply described as the service provider terminal 3.

[0018] The information processing device 1 is a computer that manages a project. The information processing device 1 functions as a server that provides various information related to project management to the service provider terminals 3-1 to 3-n. The information processing device 1 of this embodiment manages projects by managing the sending and receiving of messages between project participants on a communication network and the sharing of data between project participants via the communication network.

[0019] <Hardware configuration> Next, an example of hardware constituting the information processing device 1 will be described. Fig. 2 is a block diagram showing the hardware configuration of the information processing device 1 according to this embodiment. The information processing device 1 includes a CPU (Central Processing Unit) 11 as a processor, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a bus 14, an input / output interface 15, an output unit 16, an input unit 17, a storage unit 18, a communication unit 19, and a drive 20.

[0020] The CPU 11 executes various processes in accordance with programs recorded in the ROM 12 or programs loaded from the storage unit 18 into the RAM 13. The RAM 13 also stores data and the like required for the CPU 11 to execute various processes. The CPU 11, the ROM 12, and the RAM 13 are interconnected via a bus 14. An input / output interface 15 is also connected to this bus 14.

[0021] An output unit 16, an input unit 17, a storage unit 18, a communication unit 19, and a drive 20 are connected to the input / output interface 15. The output unit 16 is composed of a display, a speaker, etc., and outputs various information as images and sounds. The input unit 17 is composed of a keyboard, a mouse, etc., and inputs various information. The storage unit 18 is composed of a hard disk, a DRAM (Dynamic Random Access Memory), etc., and stores various data. The communication unit 19 communicates with other devices via a network including the Internet.

[0022] Removable media 21, such as a magnetic disk, optical disk, magneto-optical disk, or semiconductor memory, is appropriately attached to the drive 20. Programs read from the removable media 21 by the drive 20 are installed in the storage unit 18 as needed. The removable media 21 can also store various data stored in the storage unit 18 in the same way as the storage unit 18.

[0023] The hardware configuration described here is merely an example. The computer described in this embodiment including the information processing device 1 may have a configuration common to that of FIG. 2, or a different configuration. The computer may also be configured by two or more computers. The service provider terminal 3 in FIG. 1 is, for example, a smartphone, tablet, or personal computer having the same hardware configuration as that shown in FIG. 2.

[0024] <Functional configuration> Next, a description will be given of the functional configuration of the information processing device 1. Fig. 3 is a functional block diagram showing an example of the functional configuration of the information processing device 1 according to this embodiment.

[0025] As shown in Figure 3, the information processing device 1 has a target registration processing unit 31, a person in charge registration processing unit 32, a person in charge request management unit 33, an event setting reception unit 34, a schedule adjustment unit 35, a chat management unit 36, a message notification unit 37, a shared data reception unit 38, a shared data management unit 39, and a shared data notification unit 40 as functional units realized on a processor (CPU 11).

[0026] <Assign person function> First, the object registration processing unit 31, the person-in-charge registration processing unit 32, and the person-in-charge request management unit 33, which assign people in charge of a project, will be described.

[0027] The target registration processing unit 31 executes a registration process for registering multiple targets of the project. In this embodiment, the targets of the project are users who use support services for people requiring care, etc. Hereinafter, the people requiring care may be simply referred to as users.

[0028] The target registration processing unit 31 registers information about users who have undergone the registration procedure in the database 90. The information about the users includes, for example, the user's name, date of birth, sex, address, telephone number, level of care required, current illness, medical history, and a summary that describes various reference information. The target registration processing unit 31 can also manage, as required items, information that is necessary to determine whether or not to provide medical and care-related services from the information about the users. Furthermore, the target registration processing unit 31 may, for example, manage data that contributes to the provision of support services for each user by linking it to the information.

[0029] The method for registering the project target is not particularly limited. The registration procedure is performed, for example, based on a request from the project executor who receives a request from the care recipient, the care recipient himself, or a supporter of the care recipient. The registration procedure for the project target may be performed by the service provider terminal 3 via a communication network, or may be directly input to the information processing device 1 by a system administrator or the like who manages the information processing device 1.

[0030] The person-in-charge registration processing unit 32 executes a process for registering multiple project managers who are candidates for project managers. Project managers include individuals and organizations that participate in the project and provide services. Project managers include people of various professions, such as care managers, doctors, nurses, and care workers. The person-in-charge registration processing unit 32 registers project managers whose registration procedures have been completed in the database 90. In this embodiment, a "project manager" refers to a project manager who has the authority to assign other project managers to the project. In other words, the project manager has management authority in addition to his or her role as a project manager. Not only the initial project registrant, but also the project manager who is officially assigned to the project, as described below, may be able to assign other project managers as project managers.

[0031] The method for performing the registration procedure of the performer is not particularly limited. The registration procedure may be performed, for example, by the service provider terminal 3 via a communication network, or may be directly input into the information processing device 1 by a system administrator or the like who manages the information processing device 1. The registration procedure may be realized by a bulk import function using data in a predetermined format (for example, CSV (Comma-Separated Values) format or database format).

[0032] The assignment request management unit 33 executes an assignment process to assign a fulfilment person to the care recipient who is the subject of the project. The assignment request management unit 33 makes a provisional assignment in response to an assignment request from the project manager, obtains a response from the candidate fulfilment person to the provisional assignment, and performs processing for the manager to decide on the official assignment based on the response. In addition, when the project manager or official fulfilment person makes an assignment request, the fulfilment registration processing unit 32 can automatically register the candidate as the fulfilment person by specifying the name and contact tool destination (email address, SNS account, etc.). This allows fulfilment person registration to be completed at the same time as the assignment request without going through a prior registration procedure, thereby further improving work efficiency.

[0033] When multiple project managers have accepted the project request, the project manager presents a list of project managers who have accepted the request to the project administrator. The project manager can select a project manager to set as the official project manager from among the project managers who have accepted the request. For example, when multiple project managers of the same job type have accepted the request, the project manager selects a project manager as the official project manager by taking into consideration the user's situation, geographical conditions, the project manager's expertise, etc. The project manager sends a confirmation notice to the project manager who has been selected as the official project manager, and a non-confirmation notice to the project managers who have not been selected. This allows all project managers who have accepted the request to clearly understand the results of their selection.

[0034] FIG. 4 is a schematic diagram illustrating the process of assigning a project manager by the information processing device 1. In FIG. 4, the service provider terminal 3-1 is used by a project manager who will manage a project. A project manager can also be a project manager for another project. Similarly, a project manager for one project can also be a project manager for another project.

[0035] Hereinafter, the project manager may be simply referred to as the project manager. The service provider terminals 3-2 to 3-4 are project managers who are candidates for assignment to be requested by the project manager.

[0036] An assignment request can also be made by a project manager who has been officially assigned to the role. For example, the service provider terminal 3-4 can make a new assignment request to a project manager who uses the service provider terminal 3-5. This assignment request is made in the same way as a project manager's assignment request.

[0037] In this embodiment, some or all of the project managers who are officially assigned to a project can have the authority to assign new project managers. This allows each project manager to utilize their expertise and network to add necessary personnel to the project as needed. For example, a project manager who is assigned as a doctor can assign appropriate nurses or physical therapists based on their medical expertise, while a project manager who is assigned as a nurse can assign additional care workers based on their experience in visiting nursing. Expanding the network of experts through word of mouth in this way allows for the flexible creation of an optimal care team tailored to the needs of the user.

[0038] Furthermore, the assignment request management unit 33 performs a sending process to notify various information according to the contact tool (communication means) set for each executor. The contact tool is registered in the database 90 in association with each executor. The contact tool is, for example, email, a social networking service (SNS) such as LINE (registered trademark) or Slack (registered trademark), or a short message service (SMS). If the contact tool of a certain executor is set to an email address, the assignment request management unit 33 sends a notification by email to the set address. If the contact tool of another executor is set to an SNS such as LINE (registered trademark) that sends and receives messages, the notification is sent by an SNS message.

[0039] The communication tool and the task request management unit 33 of the information processing device 1 are linked together using, for example, an API (Application Programming Interface). Each task executor can register multiple communication tools, and the task request management unit 33 can send a notification to one or multiple selected communication tools from the multiple communication tools registered to the task executor.

[0040] The project request management unit 33 inserts a link into the notification of the contact tool, which includes connection information on the communication network to transition to a screen where the project manager can respond, make a selection, etc. By selecting the link, the project manager can transition to the system screen of the project support system 100 and respond to the notification, make a selection, etc.

[0041] In addition, the assignment request management unit 33 may perform processing to change the information presented depending on the attributes of the person who will carry out the assignment, the stage at which the request was made, the stage at which the person officially became in charge, etc.

[0042] 5 is an example of a confirmation screen for the usage status of the project support system 100 displayed on the service provider terminal 3. The confirmation screen in FIG. 5 includes a pre-confirmation status display 101, a post-confirmation status display 102, and a usage registration instruction section 103.

[0043] The pre-confirmation status display 101 displays a list of unconfirmed service requests for the performer of the service provider terminal 3. The pre-confirmation status display 101 displays various information for each service request, such as the response date, the date of receipt of the service request, the requester, the user's age, the user's gender, part of the user's address, the level of care required, current illness, medical history, and summary. The response date displays the date and time the response was accepted or an answer instruction section 104 for making an answer based on these.

[0044] When the response instruction unit 104 is operated, a response screen is displayed on the service provider terminal 3. FIG. 6 is an example of a response screen for a handling request. The response screen shown in FIG. 6 is triggered by an operation of the response instruction unit 104 and displayed as a pop-up on the confirmation screen of FIG. 5. The response screen displays information indicating the source of the handling request. In this example, the project manager who made the handling request is clearly indicated as "Requester: (Project Manager) Executor A / Organization a." This allows the executor who receives the handling request to clearly understand who made the request before responding. When the executor operates the acceptance response unit 108, which displays "OK" in FIG. 6, the executor accepts the handling request, and when the refusal response unit 109, which displays "NG," the executor rejects the handling request. When the executor accepts the handling request, the date of the response is displayed in the response date field of the pre-confirmation status display 101, as shown in FIG. 5. When the executor rejects the handling request, the executor removes the executor from the pre-confirmation status display 101.

[0045] The post-confirmation status display 102 displays information about the users currently in charge. The post-confirmation status display 102 displays information for each user, such as the user's name, gender, complete address, telephone number, care level, consultation destination, contact information, and summary. Since this information about the users is for the users for whom the project manager is officially in charge, information that identifies the individual, such as the name and complete address, is also displayed. By operating the usage registration instruction unit 103 shown in Figure 5, the project manager can transition to a screen for registering user information, and register the user information. In addition, the post-confirmation status display 102 displays, for each user, an event setting operation unit 131, a chat start unit 132, and a data management screen call unit 133 for collaboration between staff members.

[0046] The sounded-out destination displays the response result of the handling request made by the executor. In this example, the response of executor B of organization b, who is one of the sounded-out destinations that sent the handling request, is refusal, while the response of executor C of organization c is acceptance. In addition, the sounded-out destination also displays an assignment request instruction section 105 that allows the executor to make an assignment request. In the example of FIG. 5, the assignment request instruction section 105 displays "+Sound out."

[0047] When the assignment request instruction unit 105 is operated, a consultation destination setting screen is displayed on the service provider terminal 3. Fig. 7 is an example of the consultation destination setting screen for making a handling request. The consultation destination setting screen shown in Fig. 7 is triggered by the operation of the assignment request instruction unit 105 and is displayed as a pop-up on the confirmation screen in Fig. 5.

[0048] In the example of FIG. 7, the consultation destination setting screen displays a search input field 111 for inputting the name of a person to search for a person (candidate for assignment) who will provide support to user A, a selection field 112 for selecting a person by clicking or the like, and a consultation destination list 113 in which the selected person is displayed. The person to whom the assignment request is made uses the search input field 111 or the selection field 112 to select a person to whom the assignment request is made. The person to whom the assignment request is made may be a person who has been registered in advance as a candidate for assignment by the project manager, or may be a person who is registered at the stage of accepting this assignment request. When the consultation determination section 114, which displays "Consider", is operated, the person to whom the assignment request is made is requested. When the cancellation instruction section 115, which displays "Cancel", is operated, the consultation destination setting is canceled.

[0049] In the sounding destination setting screen of this embodiment, information on the sounding destinations that have already been sounded out can be displayed in the sounding destination list 113. Specifically, for the sounding destinations, the name or organization name of the sounding destinations is displayed together with the response status (accepted, rejected, no response) to the request. This allows the project manager to consider additional sounding destinations while checking the list of sounding destinations that have already been sounded out and the responses that have been received.

[0050] Furthermore, in the contact list 113, newly approached performers are displayed separately from those who have already been approached. For example, newly approached performers are visually distinguished by marking them with a "new" mark or by changing the display color. Furthermore, by providing a delete button (not shown) corresponding to each prospective contact, it is possible to delete a selected prospective contact before approaching them. This allows the project manager to make flexible adjustments while making final confirmations of the prospective contacts.

[0051] This configuration allows project managers to efficiently select additional candidates by referring to the past inquiry history and response results. For example, if all the candidates for a certain job type have declined, it is possible to make the decision to search for and inquire about additional candidates in a different region or field of expertise.

[0052] When the consultation determination unit 114 is operated, a notification is sent to each of the implementers set as the consultation destinations. In the example of Fig. 4, the handling request management unit 33 notifies the implementer of the service provider terminal 3-2 of the handling request by a message on SNS_A, notifies the implementer of the service provider terminal 3-3 of the handling request by email, and notifies the implementer of the service provider terminal 3-4 of the handling request by a message on SNS_B. Each notification includes a link containing connection destination information on the communication network for transitioning to a screen (the screen of Fig. 5 or Fig. 6) for responding to the handling request.

[0053] Furthermore, when a fulfiller who has become a fulfiller using the service provider terminal 3-4 requests an assignment to the fulfiller of the service provider terminal 3-5, the fulfillment request management unit 33 notifies the fulfiller of the fulfillment request by a message of SNS_C. This notification also includes a link destination including connection destination information on the communication network for transitioning to a screen for responding to the fulfillment request (the screen in FIG. 5 or FIG. 6).

[0054] Fig. 8 is an example of a notification screen for a request for responsibility when the contact tool is set to email. The email notification screen in Fig. 8 includes a standard request 120, user information 121, and a link 122 for transitioning to a response screen of the project support system 100. Note that the request for responsibility can include not only the standard request 120, but also a message originally created by the project manager.

[0055] In this embodiment, the assignment request management unit 33 performs a masking process to prevent the user who is the target of the project before confirmation from being identified by not disclosing the entire name and address of the user in the user information 121 to the project manager who is being approached. In this example, the information to be masked among the information about the user is information that identifies an individual and is not managed as a required item.

[0056] If the Executor's contact tool is set to another contact tool, the notification will be sent in a format appropriate to that contact tool. For example, if the contact tool is set to an SNS, the notification will include a similar link via a message on that SNS.

[0057] Next, the flow of the task assignment process will be described with reference to Fig. 9. Fig. 9 is a flowchart illustrating a series of steps up to the assignment process by the information processing device 1.

[0058] In step S1, the target registration processing unit 31 executes a registration process for registering a person requiring care support who is a target of the project. The registration of a user who is a person requiring care support is performed, for example, through the service provider terminal 3-1.

[0059] In step S2, the person-in-charge registration processing unit 32 executes a process of registering a fulfilment person. The fulfilment person to be registered is a service provider who can provide support to the care-requiring person who is the target of the project, and is a person-in-charge candidate.

[0060] In step S3, the assignment request management unit 33 receives a request for assignment of a fulfilment person to a care-requiring person from the service provider terminal 3-1 of the fulfilment person who will be the project manager.

[0061] In step S4, the assignment request management unit 33 performs processing to notify the assignment request on the contact tool to the service provider terminals 3-2 to 3-4 of the candidate assignees designated by the project manager. The notification displayed on the contact tool includes a link 122 that transitions to a screen for replying.

[0062] In step S5, the assignment request management unit 33 receives responses to the assignment requests from the respective executors from the service provider terminals 3-2 to 3-4.

[0063] In step S6, the assignment request management unit 33 performs processing to display the received response results on the communication tool of the project manager's service provider terminal 3-1. The response notification displayed on the communication tool includes a link that transitions to a screen for confirming the response. Depending on the project manager's settings, the assignment request management unit 33 can also enable direct confirmation operations from the link on the communication tool. In this case, the project manager can select the link to instantly confirm the person in charge as the official person in charge without going through the response confirmation screen, and simultaneously, a confirmation notification including the user's personal information is sent to the person in charge. This eliminates the previously required work of preparing and sending personal information at the office, significantly reducing the time required for assignment work. The assignment request management unit 33 can also similarly notify rejection responses, allowing the project manager to quickly select an alternative candidate.

[0064] In step S7, the assignment request management unit 33 assigns a formal person in charge of the project based on the formal assignment instruction on the service provider terminal 3-1 by the project manager.

[0065] In step S8, if the assignment request management unit 33 receives a new assignment request from the service provider terminal 3-4 of the executor who is officially set in charge, the processing proceeds to step S9 (step S8; Yes). If the assignment request management unit 33 does not receive a new assignment request from the executor who is officially set in charge, the processing ends without making a new assignment (step S8; No).

[0066] In step S9, the person in charge request management unit 33 notifies the person in charge of the request using a communication tool corresponding to the candidate person designated by the official person in charge. As a result, the person in charge is notified of the request on the communication tool of the service provider terminal 3-5 of the person designated as the candidate person in charge. The notification displayed on this communication tool also includes a link 122 that transitions to a screen for replying.

[0067] In step S10, the handling request management unit 33 receives a response to the handling request from the executor from the service provider terminal 3-5.

[0068] In step S11, the assignment request management unit 33 notifies the received response result to the service provider terminal 3-4 of the project manager who is the project manager.

[0069] In step S12, the responsibility request management unit 33 assigns a formal person in charge of the project based on the formal assignment instruction of the person in charge on the service provider terminal 3-4. Through this series of processes, the project executor, who is a service provider for the care-requiring person who is the target of the project, is assigned.

[0070] As explained above, the information processing device 1 of this embodiment comprises a target registration processing unit 31 that registers multiple targets of a project, a person in charge registration processing unit 32 that registers multiple implementers who are candidates for being in charge of carrying out the project, and a person in charge request management unit 33 that, upon receiving a request for assignment to the target project from the project manager who manages the project, notifies the implementer of the request for project assignment, receives a response of acceptance or rejection to the request from the implementer, and presents the response to the project manager; upon receiving an assignment instruction from the project manager for an implementer who has accepted the assignment request, the person in charge request management unit 33 sets the implementer as the official person in charge of the project.

[0071] In addition, the information processing method of this embodiment includes a target registration step of registering multiple targets of the project, a person in charge registration step of registering multiple executors who are candidates for being in charge of the project, and a person in charge request management step of, upon receiving a request for assignment to the target project from a project manager who manages the project, notifying the executor of the request to be in charge of the project, receiving a response of acceptance or rejection to the request from the executor and presenting the response to the project manager, and, upon receiving an assignment instruction from the project manager for the executor who has accepted the assignment request, setting the executor as the official person in charge of the project.

[0072] In addition, the program of this embodiment causes a computer to execute the following steps: a target registration step for registering multiple targets of a project; a person in charge registration step for registering multiple executors who are candidates for being in charge of the project; and a person in charge request management step for, upon receiving a request for assignment to the target project from a project manager who manages the project, notifying the executor of the request for being in charge of the project, receiving a response from the executor to accept or reject the request for being in charge and presenting the response to the project manager, and, upon receiving an assignment instruction from the project manager for the executor who has accepted the assignment request, setting the executor as the official person in charge of the project.

[0073] In this way, by configuring the information processing device 1, information processing method, and program, a project manager who has initiated a project can perform the processing required to gather the members necessary to implement the project on the project support system 100. This significantly reduces time and effort, and improves the efficiency of the project manager's assignment work to project implementers. The information processing device 1, information processing method, and program can support personnel involved in planning and managing integrated services related to home medical care and nursing, and can speed up the assignment and management of necessary personnel when a care recipient or patient requires some kind of support, such as when continuous care is required after discharge from the hospital.

[0074] In addition, when the person in charge request management unit 33 of this embodiment receives a request for additional assignment from the official person in charge of the project, it notifies the other person in charge of the request, receives a response from the person in charge and presents it to the official person in charge, and when it receives an assignment instruction from the person in charge for the person in charge who accepted the additional assignment request, it sets the person in charge as the official person in charge of the project.

[0075] This allows the project manager who initially initiated the project, as well as the assigned staff, to gather the necessary members for the project. For example, when nursing care support is gradually shifted to visiting medical appointments by doctors or nurses, the doctor assigned to the project can add a new nurse to the project staff.

[0076] Furthermore, the assignment request management unit 33 of this embodiment transmits the assignment request in such a way that part of the information that can identify the target of the project cannot be confirmed by the project owner.

[0077] This prevents personal identifying information from being disclosed before the person in charge officially takes charge, reducing the burden of information management for those who refuse requests.

[0078] In addition, the assignment request management unit 33 of this embodiment executes processing to display, on the contact tool set for the project manager, a link 122 including connection information on the communication network for transitioning to a screen for responding to the assignment request on the project support system 100, along with notification of the assignment request.

[0079] This allows the person in charge to confirm that they have received the request using the contact tool they use, preventing them from overlooking the request. Also, the contact tool transitions to a screen where they can respond to the request, making it possible to streamline the work required to respond to the request.

[0080] In addition, the assignment request management unit 33 of this embodiment executes processing to display, on the communication tool set for each project manager or project implementer, a link 122 including connection information on the communication network for transitioning to a screen for issuing assignment instructions on the project support system 100, along with a notification of the response to the assignment request.

[0081] This allows the project manager and project manager to confirm that they have received a response to the project manager's request using their own communication tool, preventing the project manager from overlooking a response to a request. In addition, the project manager and project manager can move to the screen for issuing assignment instructions from the communication tool they normally use, streamlining the work required to officially assign responsibilities.

[0082] In particular, in the system of this embodiment, even project managers who do not have an account for the project support system 100 can use various functions through their own communication tools. Specifically, even project managers who are not logged in to the system can respond to requests for work, obtain personal information through confirmation notifications, participate in chats, respond to and add dates and times to event schedule adjustments, download shared files, and so on. This eliminates the need for all parties involved to create accounts on the platform, and enables collaboration using only the communication tools that each person normally uses. This mechanism significantly reduces the barriers to system implementation and improves the productivity of all project managers involved in the project.

[0083] <Event setting function> Next, the event setting receiving unit 34 and schedule adjusting unit 35, which are mainly responsible for setting events such as meetings for carrying out a project, will be described.

[0084] The event setting reception unit 34 executes a process of receiving, from an event setter, one of the project executors, information on schedule candidates (candidates for dates, dates, etc.) for the date and time of an event related to the project, and event information indicating potential participants (those who need to participate or are desirable to participate in; hereinafter referred to as participants as appropriate) who will participate in the event. The event setter is the above-mentioned project manager or an executor who has officially taken charge. Hereinafter, the executor who sets up the event will be referred to as the event setter, and those who participate or plan to participate in the event will be referred to as participants.

[0085] The event setter operates the event setting operation unit 131 while the usage status confirmation screen of Fig. 5 is displayed, thereby displaying the event setting screen. Fig. 10 shows an example of the event setting screen displayed on the service provider terminal 3 of the event setter. The event setting screen shown in Fig. 10 is triggered by an operation of the event setting operation unit 131 to pop up on the confirmation screen of Fig. 5.

[0086] 10, the event setting screen displays a conference information input section 141 where the conference name and conference details can be entered in text, and an event addition instruction section 142 for instructing the addition of an event to a schedule. Addition of a schedule can be performed in cooperation with a calendar system. The operation of adding a schedule may also be performed in cooperation with an external calendar system.

[0087] When the event operator operates the event addition instruction section 142, the event setting screen of Fig. 10 transitions to a screen shown in Fig. 11. Fig. 11 is a diagram showing the schedule candidate input section 145 of the event setting screen.

[0088] As shown in FIG. 11 , the schedule candidate input unit 145 displays candidate dates and times and planned event participants, as well as a schedule confirmation unit 146 and a transmission instruction unit 147 for confirming the schedule. Multiple candidate dates and times can be set, and multiple planned event participants can also be set. The event setting reception unit 34 allows each planned participant to be set as a required or optional participant. The schedule candidate input unit 145 displays the required / optional status of each participant, allowing the event planner to easily confirm candidate dates and times for which all required participants are available (marked with a circle) when finalizing the schedule. Planned event participants are project managers who are assigned to the project based on the project objectives. In this example, project manager A of organization A is the event planner, and project manager D of organization D is a participant in the event. The event planner selects "Yes" from the options displayed in the pull-down menu if they wish to participate, "No" from the options displayed in the pull-down menu if they wish to not participate, and "△" from the options displayed in the pull-down menu if they wish to participate with conditions.

[0089] In this embodiment, the event setting receiving unit 34 sets a text input field 148 in which free-form text can be entered for "cannot participate" and "conditionally participate." For example, the text input field 148 for "cannot participate" can be used to enter the reason for absence, project or event issues, problems, etc. The text input field 148 for "conditionally participate" can be used to enter the conditions for participation, project or event issues, problems, etc.

[0090] Note that only one person can enter their own response (yes, no, conditionally) to the candidate date and time. Therefore, event planner A cannot enter the response of event planner D of organization D, and can only enter their own response. On the other hand, adding new candidate dates and times can be done by participants as well as the event planner.

[0091] When the event planner or participant inputs the transmission instruction unit 147, event information indicating the schedule candidates and the participants participating in the event is transmitted from the service provider terminal 3 to the information processing device 1. This allows not only the event planner but also the participants to add new candidate dates and times and send response requests to all participants. The event setting reception unit 34 acquires the schedule candidates for the event and the participants of the event based on the event information received by the information processing device 1. Information identifying the participants of the event may be directly included in the event information, or may be indirectly acquired by the information processing device 1 from information associated with the user information included in the event information.

[0092] The schedule adjustment unit 35 executes a process of presenting options to participants included in the event information set by the event planner. The schedule adjustment unit 35 also presents responses to the options to the event planner, and when the event planner confirms the schedule candidate, the schedule adjustment unit 35 sets the confirmed schedule candidate as the official schedule and sends a confirmation notification to all participants. Note that "presentation" in this embodiment is a broad concept that includes not only direct display on the terminal screens of the participants and the event planner, but also notification via a communication tool (email, SNS, etc.) set by each individual, and making the information viewable by screen transitions from the notification. This significantly reduces the effort and time required for individual communication, which was previously required.

[0093] The schedule adjustment unit 35 also performs processing to present options and display responses from participants on the communication tool set for each of the event planner or participants. The assignment request management unit 33 inserts a link containing connection information on a communication network to transition to a screen where the event planner or participant can respond to the options or make a selection, into the notification from the communication tool. By selecting the link, the event planner or participant can transition to the system screen of the project support system 100 and respond to the notification or make a selection. The event planner can also receive a notification and respond when another participant adds a new candidate date and time. The communication tool and the schedule adjustment unit 35 of the information processing device 1 are linked together using, for example, an API.

[0094] FIG. 12 is an example of an event notification screen when the communication tool is set to email. The email notification screen in FIG. 12 includes, in addition to a standard request 150, non-standard information such as the conference name and details entered by the event planner, user information 151, and a link 152 for transitioning to the response screen of the project support system 100. Note that since the person in charge has already been determined, the user information 151 includes the user's full name and address. Note that if the participant's communication tool is set to another communication tool, the notification will be sent in a format appropriate to that communication tool. For example, if the communication tool is set to an SNS, a notification including a similar link will be sent via a message on that SNS.

[0095] The participant transitions to the response screen shown in FIG. 13 by selecting a link 152 included in the email informing them of the presentation of options as shown in FIG. 12. FIG. 13 is an example of an event setting screen displayed on the participant's service provider terminal 3. In the example of FIG. 13, the event setting screen displayed on the participant's service provider terminal 3 displays a conference information display 155 that displays the conference name and conference details, a schedule candidate selection section 156 where the participant inputs their response to the schedule candidate, a text input field 157, and a schedule addition operation section 158. When the schedule addition operation section 158 is operated, a screen is displayed where the participant can input a new candidate date and time, just like the event planner. However, the conference name and conference details are only displayed and cannot be changed. A response request for the candidate date and time added by the participant can also be sent to all participants by a transmission instruction section (not shown).

[0096] As shown in FIG. 13, the schedule candidate selection unit 156 presents answer options for the candidate dates and times set by the event planner or participants. In this example, the participant who receives the options is executor D of organization d, and only executor D's part can set an answer option. Executor D, who is a participant, selects whether he or she can attend, cannot attend, or can attend with conditions for the candidate dates and times. If executor D can attend, he or she will select "○" from the options displayed in the pull-down menu; if he or she cannot attend, he or she will select "×" from the options displayed in the pull-down menu; and if he or she can attend with conditions, he or she will select "△" from the options displayed in the pull-down menu.

[0097] In this embodiment, the schedule adjustment unit 35 sets a text input field 157 in which free-form text can be entered for "cannot participate" and "conditionally participate." For example, the reason for absence, issues with the project or event, problems, etc. can be entered in the text input field 157 for "cannot participate." The conditions for participation, issues with the project or event, problems, etc. can be entered in the text input field 157 for "conditionally participate."

[0098] When the schedule addition operation unit 158 ​​is operated, an input field (not shown) is displayed for the participant to input the date and time of a new schedule candidate. In this input field, the participant can set the date and time of the candidate date and time. The schedule candidate added by the participant is added as a new row in the schedule candidate selection unit 156, and other participants, including the event planner, can also respond to the candidate date and time.

[0099] The schedule addition operation unit 158 ​​is an operation unit for the participant to add a new schedule candidate date and time. The method for adding a schedule is the same as the method for adding a schedule by the event planner. As described above, the screen shown in Fig. 13 is an example, and the schedule addition operation unit 158 ​​may be omitted, or the participant may also instruct to confirm the schedule.

[0100] Next, the flow of the event setting process will be described with reference to Fig. 14. Fig. 14 is a flowchart illustrating a series of steps up to event setting by the information processing device 1. In the following description of the flowchart in Fig. 14, the service provider terminal 3 used by the event setter will be referred to as service provider terminal 3-1, and the service provider terminal 3 used by the participants will be referred to as service provider terminal 3-2.

[0101] In step S15, the event setting receiving unit 34 acquires event information indicating schedule candidates for the event and participants who will participate in the event from the service provider terminal 3-1 of the event setter via the communication network.

[0102] In step S16, the schedule adjustment unit 35 presents options to the participant's service provider terminal 3-2, allowing the participant to select whether to participate in the event, not to participate, or to participate with conditions. In this embodiment, the participant is notified that an event has been set by a message on the contact tool set, and a link 152 in the message prompts the participant to respond to the schedule candidate.

[0103] In step S17, the schedule adjustment unit 35 receives the participant's response results from the participant's service provider terminal 3-2 via the communication network. These response results may include schedule candidates newly added by the participant.

[0104] In step S18, the schedule adjustment unit 35 presents the participants' response results to the service provider terminals of all the event stakeholders, including the service provider terminal 3-1 of the event planner and the service provider terminal 3-2 of the participants, via the communications network. When presenting these response results, each participant is also notified of a link to a screen that allows them to provide further responses or add candidate dates and times. This allows not only the event planner but all participants to grasp the response status of other participants in real time. The presentation of the response results also includes a link that allows the event planner to respond to the schedule.

[0105] In step S19, when a date confirmation operation is performed on the service provider terminal 3-1 of the event planner, the schedule adjustment unit 35 confirms the event schedule (step S19; Yes). In step S20, the schedule adjustment unit 35 notifies all participants that the event date has been confirmed. The event planner can also cancel an event that has already been confirmed. When a cancellation operation is performed, the schedule adjustment unit 35 notifies all participants that the event has been canceled.

[0106] In step S19, if the event planner does not perform a date confirmation operation on the service provider terminal 3-1, the schedule adjustment unit 35 returns to step S15 and sets a new schedule candidate (step S19; No). In this case, a schedule candidate with no response entered may be deleted by the person who added the candidate date and time (the event planner or a participant), or the schedule candidate with no response entered may be automatically deleted. Also, if an operation to cancel the event setting is performed in the processing of step S19, the event setting processing may be terminated without returning to step S15.

[0107] As described above, the information processing device 1 of this embodiment includes an event setting receiving unit 34 that receives, from an event setter who carries out a project, event information indicating schedule candidates for an event related to the project and participants who will participate in the event, and a schedule adjustment unit 35 that presents participants with options to select whether they can participate in the event, cannot participate, or can participate with conditions, based on the event information, and receives response results from participants who can participate, cannot participate, or can participate with conditions, and presents these to the event setter.

[0108] Furthermore, the information processing method of this embodiment includes an event setting reception step of receiving, from an event planner who carries out a project, event information indicating a candidate schedule for an event related to the project and participants who will participate in the event, and a schedule adjustment step of presenting participants with options to select whether they can participate in the event, cannot participate, or can participate with conditions, based on the event information, and accepting response results from participants who can participate, cannot participate, or can participate with conditions, and presenting these to the event planner.

[0109] In addition, the program of this embodiment causes a computer to execute an event setting reception step of receiving, from an event planner who carries out a project, event information indicating a candidate schedule for an event related to the project and participants who will participate in the event, and a schedule adjustment step of presenting participants with options to select whether they can participate in the event, cannot participate, or can participate with conditions, based on the event information, and accepting response results from participants who can participate, cannot participate, or can participate with conditions, and presenting these to the event planner.

[0110] In this way, the information processing device 1, information processing method, and program configuration make it easy to set event dates for each person in charge, even in projects involving multiple people from different organizations, reducing the burden of schedule coordination. Participants can set their availability, non-availability, or conditional availability for schedule candidates, so even if the proposed schedule candidate does not suit them, they can review the conditions and consider rescheduling the event. In particular, by presenting options to participants and providing responses to the event planner through each participant's own communication tool, coordination work that previously took a huge amount of time through individual communication via email or phone can be significantly streamlined. Furthermore, schedule confirmation and cancellation notifications are also automatically handled through the communication tool, thereby achieving time savings across the entire event management process.

[0111] Furthermore, the schedule adjustment unit 35 of this embodiment adds free-form text entry fields 148 and 157 to at least conditional participation and presents them to the participants.

[0112] This allows the user to adjust the event schedule while checking the available time and other event-related information entered in text entry field 148 and text entry field 157.

[0113] In addition, the schedule adjustment unit 35 of this embodiment accepts additional candidate schedules from the event planner who has been presented with the answer results, presents the added candidate schedules to the participants, and accepts new answer results from participants who are able to participate, unable to participate, or able to participate with conditions, and presents these to the event planner.

[0114] This allows participants to present alternative schedules even if the schedule options set by the event planner are inconvenient, thereby reducing the amount of back-and-forth communication required for schedule adjustment and easing the burden of schedule adjustment.

[0115] In addition, the schedule adjustment unit 35 of this embodiment executes processing to display, on the contact tool set for the participant, a link 152 including connection information on the communication network for transitioning to a screen for responding to the participation request on the project support system 100, along with a notification of the event participation request.

[0116] This allows participants to check that schedule candidates for the event have been presented using the communication tool they use, preventing them from missing the presentation of schedule candidates.In addition, since the screen for confirming schedule candidates is displayed from the communication tool they normally use, the work required to confirm schedule candidates is also made more efficient.

[0117] In addition, the schedule adjustment unit 35 of this embodiment executes processing to display, on the communication tool set by the event planner, a link 152 including connection information on the communication network for transitioning to a screen for confirming the event on the project support system 100, along with notification of responses from participants.

[0118] This allows the event planner to check that responses to the event's schedule candidates have been submitted using their own communication tool, preventing participants from missing their responses. In addition, because the screen for participants' responses is accessed from the communication tool they normally use, the work required to check responses to schedule candidates can be made more efficient.

[0119] In the above embodiment, the event participants were official persons associated with the user, but it is also possible to add event participants manually or from another system.

[0120] In the above embodiment, the candidate schedules are initially set by the event planner, but this configuration is not limited to this. For example, when setting candidate schedules, the candidate schedule dates and times may be automatically set from schedules set in the calendars used by the participants. In this case, if a participant has multiple schedules set, such as personal and work, a date and time among the multiple schedules that does not have any scheduled events can be set as a candidate schedule. In this way, candidate schedules may be automatically set by the information processing device 1. The calendar may also be a tool for a different system. Furthermore, the calendar may display all schedules, or may be extracted only based on a certain project or condition. Furthermore, when the date of an event is confirmed or canceled, the schedule adjustment unit 35 can automatically update the calendar system used by each participant.

[0121] <Chat function and data sharing function> First, the chat management unit 36 ​​and the message notification unit 37, which are responsible for the chat function that realizes the exchange of messages between project personnel, will be described.

[0122] The chat management unit 36 ​​saves the message history of a chat room in which multiple participants participate, and executes processing to display a chat screen on the project support system 100. In this embodiment, the multiple participants are project managers who are officially assigned to be in charge of the project. Hereinafter, project managers who participate in a chat room may be referred to as participants.

[0123] A participant operates the chat starting unit 132 while the usage status confirmation screen of Fig. 5 is displayed, thereby displaying a chat screen. Fig. 15 is an example of a chat screen displayed on the service provider terminal 3 of a participant who has started a chat. The chat screen shown in Fig. 15 is triggered by an operation of the chat starting unit 132 and is displayed as a pop-up on the confirmation screen of Fig. 5.

[0124] 15, the chat screen displays a project target display 161, a message history display 162, a message input section 163, a destination setting section 164, a send instruction section 165, and a data attachment instruction section 180. The project target display 161 indicates the name of the chat room. In this example, the chat was started by operating the chat start section 132 in the user B's column of the post-confirmation status display 102, so user B is displayed in the project target display 161.

[0125] The message history display 162 displays past messages sent, the sender of the message, and the date and time the message was sent. The message history display 162 clearly indicates whether each message is addressed to everyone or to an individual (direct message), and also visually identifies unread messages. The chat management unit 36 ​​can also provide a function whereby, if a message sender has unread readers of a message they sent, this is clearly displayed, and a list of unread readers can be checked by selecting the identification display. The message input unit 163 is a field where the message sender inputs text. The destination setting unit 164 allows the message sender to specify the destination of the message. In this example, the executor set as the person in charge of user B is a candidate for the destination. It is also possible to set individual recipients of the message, rather than all the people in charge. The send instruction unit 165, when operated with text entered in the message input unit 163, sends the message to the destination set in the destination setting unit 164.

[0126] If only specific participants are selected in the destination setting unit 164, the chat screen may display a message indicating that it is in direct message (DM) mode (for example, "Individual message with person in charge X"), making it clear that the message will not be displayed to other participants.

[0127] When a message is sent from a participant in a chat room, the message notification unit 37 notifies the participant of the chat room set as the message destination that the message has been entered. In this embodiment, the message notification unit 37 notifies the participant that a new message has been entered on the communication tool set for each participant. This notification on the communication tool includes a link containing connection information on the communication network for transitioning to a chat screen on the project support system 100. The communication tool and the message notification unit 37 of the information processing device 1 are linked together using, for example, an API.

[0128] FIG. 16 is an example of a message notification screen when the communication tool is set to email. The email notification screen in FIG. 16 includes transmission information 170, message content information 171, and a link 172 for transitioning to a chat screen of the project support system 100. In this example, the transmission information 170 displays Executor A as the sender of the message and User B, the target of the project. The message content information 171 indicates the content of the message that triggered the notification in text. A participant transitions from the email notification screen to the chat screen shown in FIG. 15 by selecting link 172 included in the email as shown in FIG. 16. Note that if the participant's communication tool is set to another communication tool, the notification will be sent in a format appropriate to that communication tool. For example, if the communication tool is set to an SNS, a notification including a similar link will be sent via a message on that SNS.

[0129] The message read management function will be described with reference to Fig. 17. Fig. 17 is an example of a chat screen displayed on the service provider terminal 3 of the chat room participants. Fig. 17 displays a project target display 161, a message history display 162, a message input section 163, a destination setting section 164, a send instruction section 165, a data attachment instruction section 180, and in addition a read operation section 166.

[0130] When the read operation unit 166 is operated, the chat management unit 36 ​​performs a process of changing the unread status of a message to a read status. Thus, in this embodiment, the read or unread status of a message in a chat room is changed triggered by a participant's operation. This is an important function that takes into account the fact that medical and nursing care workers are often unable to respond immediately, preventing missed responses or accidents due to messages being automatically marked as read and allowing for careful processing later. The chat management unit 36 ​​can also provide a function that allows message senders to edit or delete messages they have sent. Furthermore, from the perspective of protecting personal information, a function can be provided for sending only a notification and a link for messages containing sensitive information, without including the message body in the notification. Sensitive information can be determined automatically using AI or manually by the sender setting a flag.

[0131] Next, the flow of chat management processing by the chat management unit 36 ​​and the message notification unit 37 will be described with reference to Fig. 18. Fig. 18 is a flowchart illustrating the flow of chat management processing by the information processing device 1. In the following description of the flowchart in Fig. 18, the service provider terminal 3 used by the sender of a message as a participant will be referred to as service provider terminal 3-1, and the service provider terminal 3 used by the receiver of the message will be referred to as service provider terminal 3-2.

[0132] In step S21, the chat management unit 36 ​​receives an instruction to display a chat room from the service provider terminal 3-1 via the communication network. The instruction to display the chat room may be an operation of the chat start unit 132 in Fig. 5 on the service provider terminal 3-1, or may be an operation to select the link 172 included in the email in Fig. 16.

[0133] In step S22, the chat management unit 36 ​​transmits information for displaying a corresponding chat screen based on a display instruction for a chat room of the service provider terminal 3-1. For example, in the case of an operation of the chat starting unit 132, information for displaying a chat screen that displays a message history of the relevant user is transmitted. In addition, in the case of an operation for selecting the link 172, information for displaying a chat screen of the user associated with the link 172 is transmitted. As a result, the chat screen of the chat room corresponding to the service provider terminal 3-1 is displayed.

[0134] In step S23, the chat manager 36 receives a message transmission request from the service provider terminal 3-1. This transmission request also includes information specifying the destination of the message.

[0135] In step S24, the chat management unit 36 ​​saves the message in the message history of the chat room, so that the participants who are to receive the message set as the destination can view the message by displaying the chat screen on the service provider terminal 3-2.

[0136] In step S25, the message notification unit 37 performs processing for displaying a message reception notification and a link to a chat screen on the communication tool set for the participant specified as the message destination. For example, if the communication tool is set to email, the message notification unit 37 sends an email containing a message reception notification and a link to transition to the chat screen to the email address set for the participant. If the communication tool is set to an SNS, the message notification unit 37 uses an API to send information for displaying a message containing a message reception notification and a link to display the chat screen on the SNS.

[0137] In step S26, the chat management unit 36 ​​receives an instruction to display the chat room from the service provider terminal 3-2 via the communication network. The instruction to display the chat room may be a selection operation of the link 172 included in the email in Fig. 16, or an operation of the chat start unit 132 in Fig. 5 on the service provider terminal 3-2.

[0138] In step S27, the chat management unit 36 ​​transmits information for displaying a corresponding chat screen based on a display instruction for the chat room from the service provider terminal 3-2. This process is similar to the process in step S22.

[0139] In step S28, when the destination participant performs a read instruction operation on the chat screen of the service provider terminal 3-2 using the read operation unit 166, the process proceeds to step S29 (step S28: Yes). In step S29, the chat management unit 36 ​​performs a process of changing the message status of the destination participant from an unread state to a read state.

[0140] In step S28, if the read operation unit 166 is not operated on the chat screen of the service provider terminal 3-2, the process ends without going through step S29 (step S28: No). In this case, the status of the message remains unread.

[0141] Next, a shared data receiving unit 38, a shared data management unit 39, and a shared data notification unit 40, which are responsible for the function of sharing data between project personnel, will be described.

[0142] When the shared data receiving unit 38 receives a request from a data provider to share data stored in cloud storage with a sharee, the shared data receiving unit 38 acquires storage destination information for the sharee to connect to the storage destination in the cloud storage.

[0143] Cloud storage stores data so that it can be downloaded by the intended recipient via a communication network. When the shared data receiving unit 38 receives a sharing request from the provider to the intended recipient, it acquires storage destination information for the intended recipient to access the data. The data may be stored in internal storage managed by the information processing device 1 or in external cloud storage. When using external cloud storage, online storage such as Google Drive, Dropbox, OneDrive, and Fileforce can be used. The data provider and the intended recipient can use multiple types of cloud storage simultaneously. For example, data from a business that does not have cloud storage or photos taken with a mobile device can be directly uploaded to the internal storage of the information processing device 1.

[0144] The following describes how data is accepted by the shared data accepting unit 38. When a participant in a chat room selects data attachment instruction unit 180 on the chat screen as shown in Fig. 17, the screen transitions to a data selection screen. On the data selection screen, the participant registers the destination on the cloud storage for the data they wish to upload.

[0145] The shared data accepting unit 38 registers the storage destination (connection destination information) registered by the participant who is the data provider as storage destination information. The actual storage destination of the data may be the internal storage of the information processing device 1 or external cloud storage. The shared data accepting unit 38 provides a unified user interface regardless of the type of storage destination. This eliminates operational difficulties due to differences in UI / UX between different external storages and improves user convenience, including automating security settings. In addition, the shared data accepting unit 38 performs processing to set data viewing or download permissions for data sharers with whom the data is shared. For example, the executor set as the person in charge of user B becomes the data sharer who is granted data viewing or download permissions.

[0146] The shared data management unit 39 manages the requested data so that it can be shared with participants. Figure 19 shows an example of a chat screen displayed on the service provider terminal 3 of a chat room participant after data sharing. Figure 19 also shows a chat screen displayed on the service provider terminal 3 of Executor C, a participant in User B's chat room. Chat room participants can download data by clicking on the area displaying each data name. In this example, Executor A uploads the data "Proposal.doc" and "Creation Data.csv," while Executor C uploads the data "Related Materials.pdf." The shared data management unit 39 automatically generates and displays a notification message on the chat screen when data is uploaded. This eliminates the need for the data provider to manually enter a message such as "File Uploaded." The shared data management unit 39 also manages unread data independently of unread message management, and provides a function for identifying unread users for each data item and displaying a list of unread users. This list of unread users can be viewed by all participants, not just the data provider, allowing the entire team to share the status of data confirmation.

[0147] Executor A will be the provider of the data "Proposal.doc" and "Data for Creation.csv", and will be the data sharer of the data "Related Materials.pdf" shared by Executor C. Executor C will be the provider of the data "Related Materials.pdf", and will be the data sharer of the data "Proposal.doc" and "Data for Creation.csv" shared by Executor A.

[0148] Furthermore, the shared data management unit 39 displays a shared data management screen showing a list of data for which sharing requests have been made based on operations by participants. For example, when a participant operates the data management screen calling unit 133 while the usage status confirmation screen of Fig. 5 is displayed, the shared data management screen is displayed.

[0149] Fig. 20 is an example of a shared data management screen displayed on the service provider terminal 3 of the data sharer. Fig. 20 is a shared data management screen displayed on the service provider terminal 3 of the performer A by the shared data management unit 39. The shared data management screen in the example of Fig. 20 displays a data registration instruction unit 181 and a shared data list 182.

[0150] Executor A can upload data by selecting and operating the data registration instruction section 181. In this way, data can be shared not only from the chat screen but also from the shared data management screen. The process for sharing data is the same as when it is performed from the chat screen.

[0151] The shared data list 182 displays a list of data shared with the person in charge of user B (a participant in the chat room), who is the target of the project. In this example, the shared data list 182 shows "related materials.pdf" as data shared with executor A by executor C. It also shows "proposal.doc" and "data for creation.csv" as data shared by executor A with executor C. A corresponding download instruction section 185 is displayed for each piece of data, regardless of the data status (unread / read). In addition, a deletion instruction section 186 for deleting the data from the shared data is displayed for each of "proposal.doc" and "data for creation.csv," which are provided by executor A, while the deletion instruction section 186 is not displayed for "related materials.pdf," which is provided by executor C.

[0152] When data is viewed or downloaded, the shared data management unit 39 switches the data status of the participant from unread to read. Specifically, the status is switched to read when the share target clicks the download instruction unit 185, regardless of whether the actual download is completed or saved. For example, when the performer A selects the download instruction unit 185 corresponding to "related materials.pdf" in FIG. 20, the data status of "related materials.pdf" set for the performer A is switched from unread to read. In this example, the display mode of the "related materials.pdf" portion changes. The shared data management unit 39 may also process the "related materials.pdf" portion to be excluded.

[0153] The shared data management unit 39 can also display a list of unread users that displays the sharers whose data status is unread to the data provider. The shared data management unit 39 changes the display mode, such as excluding the sharers whose data status has been switched to read from the list of unread users.

[0154] For example, an API is used to link the cloud storage with the shared data accepting unit 38 and the shared data managing unit 39 of the information processing device 1. Note that permission settings for external cloud storage are automatically performed using the API provided by each storage.

[0155] When a sharing request is made, the shared data notification unit 40 executes processing to display, on the communication tool set for the sharing target, a notification indicating that a data sharing request has been made, as well as a link including connection information on a communication network for transitioning to a screen for viewing or downloading the data. The communication tool and the shared data notification unit 40 of the information processing device 1 are linked together using, for example, an API.

[0156] FIG. 21 shows an example of a data sharing notification screen when the communication tool is set to email. The email notification screen in FIG. 21 includes transmission information 190, sharing notification information 191, and a link 192 for transitioning to the chat screen of the project support system 100. In this example, the transmission information 190 displays the data provider, Project Manager A, and the project target, User B. The sharing notification information 191 displays text notifying the user that the data has been shared. By selecting the link 192 included in the email shown in FIG. 21, the data sharer can transition to the chat screen shown in FIG. 19 and download the data. The inclusion of a link to the chat screen allows participants who do not have an account with the project support system 100 to access the chat screen via the communication tool and download the shared data. Participants without accounts are often passive recipients of shared information, and this mechanism facilitates smooth data sharing. The link 192 may also transition to the shared data management screen shown in FIG. 20. If a participant's communication tool is set to another communication tool, the notification will be sent in a format appropriate to that communication tool. For example, if the contact tool is set to an SNS, a notification including a similar link will be sent via a message on that SNS.

[0157] Furthermore, when a sharing request is made, the chat management unit 36 ​​may automatically add a sharing notification message to the chat screen to notify that the sharing request has been made.

[0158] Next, the flow of data sharing processing by the shared data receiving unit 38, the shared data management unit 39, and the shared data notification unit 40 will be described with reference to Fig. 22. Fig. 22 is a flowchart illustrating the flow of data sharing processing by the information processing device 1. In the following description of the flowchart in Fig. 22, the service provider terminal 3 used by the data provider will be referred to as service provider terminal 3-1, and the service provider terminal 3 used by the data sharing target will be referred to as service provider terminal 3-2.

[0159] In step S31, the shared data accepting unit 38 accepts a data sharing request from the service provider terminal 3-1 and registers the storage destination information in the cloud storage. As described above, the data sharing request may be made from the data attachment instructing unit 180 on the chat screen or from the data registration instructing unit 181 on the shared data management screen.

[0160] In step S32, the shared data accepting unit 38 sets access rights to the storage destination of the cloud storage for the data sharing target based on the accepted sharing request, thereby enabling the data sharing target to access the data stored in the cloud storage.

[0161] In step S33, the shared data notification unit 40 notifies the sharing target of a data sharing request on the communication tool set for the target. This sharing request notification includes a link to transition to a chat screen or a shared data management screen, which is a screen for downloading data from cloud storage.

[0162] In step S34, when a download instruction operation is performed from the chat screen or the shared data management screen to instruct downloading, the shared data management unit 39 proceeds to step S35 (step S34; Yes). In step S35, the shared data management unit 39 executes processing to start downloading of data by the service provider terminal 3-2 based on the storage destination information. In step S36, the shared data management unit 39 switches the data status of the data for which processing to start downloading has been performed from an unread state to a read state.

[0163] In step S34, if a download instruction operation to instruct downloading is not performed from the chat screen or the shared data management screen, the shared data management unit 39 does not go through the processing of steps S35 and S36, and the processing ends with the data status remaining in an unread state (step S34; No).

[0164] As described above, the information processing device 1 of this embodiment includes a chat management unit 36 ​​that saves a history of messages entered by participants in a chat room in which multiple participants can participate and displays a chat screen containing the messages on the system, and a message notification unit 37 that, when a new message is entered for a specified participant in the chat room, executes processing to display, on the contact tool set for the participant, a notification that a new message has been entered, as well as a link 172 containing connection information on a communication network for transitioning to a chat screen on the project support system 100.

[0165] In addition, the information processing method of this embodiment includes a chat management step of saving a history of messages entered by participants in a chat room in which multiple participants can participate and displaying a chat screen containing the messages on the system, and a message notification step of, when a new message is entered for a specified participant in the chat room, executing processing to display, on the contact tool set for the participant, a notification indicating that a new message has been entered, as well as a link 172 containing connection information on a communication network for transitioning to a chat screen on the project support system 100.

[0166] In addition, the program of this embodiment causes a computer to execute the following steps: a chat management step of saving a history of messages entered by participants in a chat room in which multiple participants can participate and displaying a chat screen containing the messages on the system; and a message notification step of, when a new message is entered for a specified participant in the chat room, executing processing to display, on the contact tool set for the participant, a notification that a new message has been entered, along with a link containing connection information on a communication network for transitioning to a chat screen on the project support system 100.

[0167] In this way, by configuring the information processing device 1, the information processing method, and the program, participants can chat from their own communication tools even if they are not logged in to the project support system 100, and can efficiently exchange information via chat. In addition, since participants can transition to the chat screen from their usual communication tools, messages can be effectively prevented from being overlooked. Even in a project involving multiple people from different organizations, communication between chat participants can be made more efficient and collaboration can be improved.

[0168] Furthermore, the chat management unit 36 ​​of this embodiment changes the message status from unread to read when a participant performs a read instruction operation on the chat screen.

[0169] As a result, the message status does not change from unread to read just by opening the chat screen, but changes to read only when a read instruction operation is performed. Therefore, if you need to check the message again later, you can check the message but not operate the read operation unit 166, and the message will remain unread, allowing you to use it like a memo to check the message later. The read and unread status of both your own and others' messages are displayed so that they can be viewed. In other words, the message status can be used to manage the read and unread status of your own messages, and is provided as something that can be used to understand the read and unread status of others' messages.

[0170] The information processing device 1 of this embodiment further includes a shared data management unit 39 that, when an operation to request data sharing is performed on the chat screen, manages the data so that it can be shared with participants. When the data is viewed or downloaded, the shared data management unit 39 switches the status of the participant's data from unread to read, and manages the data status for the data independently of the message status. The read (downloaded) and unread (not downloaded) statuses of both the participant's own data and those of others are presented so that they can be viewed. In other words, the data status can be used to manage the read / unread status of one's own data, and is provided as something that can be used to understand the read / unread status of others' data.

[0171] This allows the status of a message and the data to be shared related to the message to be in different states. For example, the message can be marked as read while the data related to the message can be marked as unread for later review, or the data status can be marked as read while the message status is marked as unread for later reply to the message.

[0172] Furthermore, the information processing device 1 of this embodiment is equipped with a shared data receiving unit 38 that, when it receives a request from a data provider to share data stored in cloud storage with a target shareee, acquires destination information for the target shareee to connect to the destination in cloud storage, and a shared data management unit 39 that displays a shared data screen showing a list of data for which a request to share has been made to the target shareee, and, when data is selected by the target shareee on the shared data screen, performs processing to allow the target shareee to view or download the data from the cloud storage based on the destination information.

[0173] In addition, the information processing method of this embodiment includes a shared data reception step in which, when a request for sharing of data stored in cloud storage from a data provider to a target recipient is received, the target recipient acquires destination information for connecting to the destination in cloud storage; and a shared data management step in which a shared data screen showing a list of data for which a request for sharing has been made to the target recipient, and, when data is selected by the target recipient on the shared data screen, a process is performed to allow the target recipient to view or download the data from the cloud storage based on the destination information.

[0174] In addition, the program of this embodiment causes a computer to execute the following steps: a shared data reception step in which, when a data provider receives a request to share data stored in cloud storage with a target recipient, the target recipient acquires storage destination information for connecting to the storage destination in cloud storage; and a shared data management step in which a shared data screen is displayed showing a list of data for which a request to share has been made to the target recipient, and, when data is selected by the target recipient on the shared data screen, a process is performed to allow the target recipient to view or download the data from the cloud storage based on the storage destination information.

[0175] By configuring the information processing device 1, the information processing method, and the program in this way, the storage destination of the data to be shared becomes cloud storage, so there is no need to reserve an area for storing the data on the information processing device 1 side. Furthermore, the person with whom the data is to be shared can view or download the data through a screen displayed on the project support system 100 without operating the cloud storage. Therefore, even if the data is stored in cloud storage that the person does not normally use, there is no need to remember how to operate the cloud storage, and data can be shared only by operating the project support system 100. According to the multiple information processing devices 1, the information processing method, and the program of this embodiment, unified management of data on the platform can be realized.

[0176] Furthermore, the shared data accepting unit 38 of this embodiment performs processing for setting permissions for sharing users to view or download data on the cloud storage.

[0177] This allows access rights to be set for the data to be shared when a sharing request is received. Therefore, the person with whom the data is to be shared does not need to perform any operations to obtain access rights. While imposing certain access restrictions, the operation of viewing or downloading the data to be shared can be made easier and more efficient.

[0178] In addition, the information processing device 1 of this embodiment further includes a shared data notification unit 40 that, when a sharing request is made, executes processing to display, on the contact tool set for the sharing target, a notification indicating that a data sharing request has been made, as well as a link including connection information on a communication network for transitioning to a screen for viewing or downloading the data.

[0179] This allows the data recipient to confirm that the data has been shared using their own communication tool, preventing them from overlooking the fact that the data has been shared. In addition, the process of sharing data can be streamlined, as the user can be redirected to a screen where they can view or download the data from their usual communication tool.

[0180] Furthermore, when data is viewed or downloaded, the shared data management unit 39 of this embodiment switches the data status of the data of the sharing target from an unread state to a read state.

[0181] This allows the user to easily and quickly narrow down the data to be checked based on the data status (unread or read) that indicates whether the shared data has been checked.

[0182] The shared data management unit 39 displays a list of unread users that displays sharing targets whose data status is unread, and excludes sharing targets whose data status has been switched to read from the list of unread users.

[0183] This allows the data provider to identify the people with whom the data has been shared who have not yet confirmed the data to be shared, and to promptly take various measures, such as sending reminders or re-notifying them.

[0184] As described above, the project support system 100 of this embodiment enables efficient personnel assignment and plan execution management in accordance with service plans for care and home medical care recipients, and easily unifies the integration of various information sources. More specifically, it facilitates the selection, assignment, and management of medical and care service providers, centralizes status management of contact, requests, negotiations, and approvals with service providers, and centralizes communication between care managers and service providers. It also supports the work of care managers, provides a user interface that shows the status of each service provider and staff member, and manages and visualizes communication history with each stakeholder, allowing each staff member to easily understand the status of the project. Furthermore, by enabling various information integration methods, it enables the participation of service providers (executors) who have difficulty implementing a system. This enables a communication platform that enhances the level of collaboration between care and medical teams.

[0185] Although one embodiment of the present invention has been described above, the present invention is not limited to the above-described embodiment, and modifications, improvements, etc. within the scope of achieving the object of the present invention are included in the present invention.

[0186] Furthermore, the above-described series of processes can be executed by hardware or software. In other words, the above-described functional configuration is merely an example and is not particularly limited. That is, it is sufficient for the information processing device 1 to have the function of executing the above-described series of processes as a whole, and the type of functional block used to realize this function is not particularly limited to the above example. Furthermore, the location of the functional block is not particularly limited and may be arbitrary. For example, the functional block of the information processing device 1 may be transferred to another device, etc. Conversely, the functional block of another device may be transferred to a server, etc. Furthermore, one functional block may be configured as a single piece of hardware, a single piece of software, or a combination thereof.

[0187] When a series of processes is executed by software, the programs constituting the software are installed onto a computer or the like from a network or a recording medium. The computer may be a computer incorporated into dedicated hardware. The computer may also be a computer capable of executing various functions by installing various programs, such as a server, a general-purpose smartphone, or a personal computer.

[0188] The recording medium containing such a program may be configured as not only a removable medium (not shown) that is distributed separately from the device main body in order to provide the program, but also a recording medium that is provided in a state that it is pre-installed in the device main body, etc. Since the program can be distributed via a network, the recording medium may be installed in or accessible to a computer that is connected or connectable to the network.

[0189] In this specification, the steps describing the program recorded on the recording medium include not only processes that are performed in chronological order, but also processes that are not necessarily performed in chronological order but are performed in parallel or individually. Also, in this specification, the term "system" means an overall device composed of multiple devices or multiple means, etc. [Explanation of symbols]

[0190] 1. Information processing equipment 31 Target registration processing unit 32 Registration Processing Unit 33 Request Management Department 34 Event Setting Reception Department 35 Schedule Coordination Department 36 Chat Management Department 37 Message notification section 38 Shared Data Reception Department 39 Shared Data Management Department 40 Shared data notification section 100 Project Support System

Claims

1. An information processing device for managing a project, an object registration processing unit that registers a plurality of objects of the project; a person-in-charge registration processing unit that registers a plurality of project candidates; an assignment request management unit that, upon receiving a request for assignment to the target project from a project manager who manages the project, notifies the executor of the assignment request for the project, receives a response of acceptance or rejection to the assignment request from the executor, and presents the response to the project manager; Equipped with The said request management unit When the project manager issues an assignment instruction to the executor who has accepted the assignment request, the executor is set as an official person in charge of the project. Information processing device.

2. The said request management unit When receiving an additional assignment request from the official person in charge of the project, notify the other person in charge of the assignment request, receive the response from the other person in charge, and present it to the official person in charge; When the assignment instruction from the person in charge is received from the person who accepted the additional assignment request, the person in charge is set as the official person in charge of the additional project. The information processing device according to claim 1 .

3. The said request management unit Sending the request to the project manager in such a way that some of the information that can identify the target of the project cannot be confirmed by the project manager. The information processing device according to claim 1 .

4. The said request management unit Execute a process on a contact tool set for the executor to display a link including connection destination information on a communication network for transitioning to a screen for responding to the request for responsibility together with a notification of the request for responsibility.

4. The information processing device according to claim 1.

5. The said request management unit Execute a process on a communication tool set for each of the project manager and the project executor to display a link including connection destination information on a communication network for transitioning to a screen for issuing the assignment instruction together with a notification of the response to the request for assignment.

4. The information processing device according to claim 1.

6. An information processing method for an information processing device that manages a project, an object registration step of registering a plurality of objects of the project; a person-in-charge registration step of registering a plurality of persons who are candidates for carrying out the project; a task request management step of notifying the executor of the request to be in charge of the project when a request for assignment of the project to the target is received from a project manager who manages the project, receiving a response of acceptance or rejection to the request from the executor and presenting the response to the project manager, and, when an assignment instruction from the project manager is received for the executor who has accepted the assignment request, setting the executor as an official person in charge of the project; An information processing method including:

7. A computer program for managing projects, an object registration step of registering a plurality of objects of the project; a person-in-charge registration step of registering a plurality of persons who are candidates for carrying out the project; a task request management step of notifying the executor of the request to be in charge of the project when a request for assignment of the project to the target is received from a project manager who manages the project, receiving a response of acceptance or rejection to the request from the executor and presenting the response to the project manager, and, when an assignment instruction from the project manager is received for the executor who has accepted the assignment request, setting the executor as an official person in charge of the project; A program for executing the above on a computer.

Images