Progress management system, progress management method, and program

Abstract

This system provides a progress management system, methods, and programs that allow hospitals to monitor the progress of each patient's care services at any time. [Solution] In the progress management system, the processor 10C of the server 10 includes: an issuing unit that issues an access code associated with a first user engaged in hospital operations; a creation unit that creates patient data linked to the identification information of the first user in response to access by a second user, who is a patient hospitalized in the hospital or a family member of a patient, using the access code; an updating unit that updates the data to include first information indicating the status of adjustments for the selection of care services in response to instructions from one or more third users or second users who introduce care services to be used by the second user after discharge; and an output unit that outputs data linked to the identification information in response to a request from the first user.

Description

Technical Field

[0001] The present disclosure relates to a progress management system, a progress management method, and a program.

Background Art

[0002] Intermediary agents such as referral companies introduce facility services such as nursing homes or home-visit care and other home-based services to patients requiring nursing care at home or in a facility.

[0003] Regarding the introduction of nursing care facilities to patients, Japanese Unexamined Patent Application Publication No. 2024-119033 (Patent Document 1) discloses a system that can enable patients who do not have sufficient knowledge about nursing care to determine the appropriateness related to identifying appropriate nursing care facilities that match their wishes and introducing such nursing care facilities.

Prior Art Literature

Patent Literature

[0004]

Patent Document 1

Summary of the Invention

Problem to be Solved by the Invention

[0005] When selecting a nursing care service for after discharge, a patient hospitalized in a hospital may tour or experience a nursing care service introduced by an intermediary agent or the like.

[0006] A patient may not report or may conceal the progress of nursing care service selection to hospital employees. In such a case, a hospital employee may be requested by the patient for assistance in selecting a nursing care service just before the scheduled discharge date, or may postpone the discharge date for a patient who cannot find an acceptable nursing care service by the scheduled discharge date.

[0007] Therefore, in order to secure hospital beds, it is preferable for hospital staff to contact patients or their families to confirm whether the patient is proceeding smoothly with the selection of care services. However, confirming progress in the above manner to avoid discrepancies in understanding between hospital staff and patients is time-consuming and laborious. The technology described in Patent Document 1 enables support for patients in selecting care services, but there is room for improvement in terms of how hospitals can grasp the status of patients' care service selection.

[0008] One of the purposes of this disclosure is to address these issues by enabling hospital staff to monitor the progress of each patient's care services at any time. [Means for solving the problem]

[0009] A progress management system in one aspect of this disclosure comprises an issuing unit, a creation unit, an updating unit, and an output unit. The issuing unit issues an access code associated with a first user engaged in hospital operations. The creation unit creates patient data linked to the first user's identification information in response to access by a second user, who is a patient hospitalized in the hospital or a family member of a patient, using the access code. The updating unit updates the data to include first information indicating the status of the selection of care services in response to instructions from one or more third users or the second user to introduce care services that the patient will use after discharge to the second user. The output unit outputs data linked to the identification information in response to a request from the first user.

[0010] In another aspect of this disclosure, the progress management system further comprises a support unit that assists in the collaboration between a second user and one or more third users. The update unit updates the first information based on the status of the collaboration support.

[0011] In another embodiment of this disclosure, the update unit updates the data to include second information indicating the patient's scheduled discharge date, in response to instructions from the first or second user. The progress management system further includes a notification unit that outputs a notification to at least one of the first or second user urging them to select care services, based on the number of days until the scheduled discharge date being below a threshold and the first information not including information indicating the planned care services to be used after discharge.

[0012] In another aspect of this disclosure, the notification unit selects a specific third user from among one or more third users based on the fact that the first information does not include information indicating the third user to be consulted, and adds the information of the specific third user to the notification.

[0013] In another aspect of this disclosure, a particular third user is selected based on an evaluation score for each of one or more third users.

[0014] In another aspect of this disclosure, the evaluation value is calculated from at least one of the evaluation results of the first or second user on the target third user among one or more third users, and the success rate of the target third user.

[0015] Furthermore, the notification department will identify one or more potential care services that can be used from the scheduled discharge date, based on the availability of one or more care services and the number of days required from the application to the start of service, and will add information about one or more potential care services to the notification.

[0016] A progress management method according to one aspect of the present disclosure comprises: issuing, by one or more processors, an access code associated with a first user working at a hospital; creating, by one or more processors, patient data linked with the identification information of the first user in response to access using the access code by a second user, wherein the second user is a patient hospitalized at the hospital or a family member of the patient; updating, by one or more processors, the data to include first information indicating an adjustment status of care service selection in response to an instruction from one or more third users or the second user, wherein the third users introduce care services that the patient uses after discharge from the hospital to the second user; and outputting, by one or more processors, the data linked to the identification information in response to a request from the first user.

[0017] A program according to one aspect of the present disclosure causes a computer to execute the above progress management method. Effects of the Invention

[0018] According to the present disclosure, a hospital can check the progress status of each patient's care service at any time. Brief Description of Drawings

[0019] [Figure 1] It is a diagram schematically illustrating an example of the progress management system according to the present embodiment. [Figure 2] It is a diagram illustrating an example of the server shown in FIG. 1. [Figure 3] It is a flowchart illustrating an example of an adjustment flow for care service selection implemented in the progress management system shown in FIG. 1 and FIG. 2. [Figure 4] It is a diagram illustrating an example of an evaluation request screen for an intermediary. [Figure 5] It is a diagram illustrating an example of data managed by the progress management system. [Figure 6] It is a diagram illustrating a consultation application screen for an intermediary, which is an example of a support screen. [Figure 7] It is a diagram illustrating a care service introduction screen, which is an example of a support screen. [Figure 8] It is a diagram showing an application screen for a visit to a nursing care service, which is an example of a support screen. [Figure 9] It is a diagram showing an application screen for use of a nursing care service, which is an example of a support screen. [Figure 10] It is a diagram showing an example of a confirmation screen for an adjustment status. [Figure 11] It is a flowchart showing an example of a flow of output processing for a reminder notification. [Figure 12] It is a diagram showing an example of a notification screen. [Figure 13] It is a diagram showing another example of a notification screen.

Mode for Carrying Out the Invention

[0020] Hereinafter, embodiments and modified examples according to the present disclosure will be described with reference to the drawings. In the following description, the same reference numerals are assigned to the same parts and components. Their names and functions are also the same. Therefore, detailed description of these will not be repeated. Note that the embodiments and modified examples described below may be selectively combined as appropriate.

[0021] <Configuration of Progress Management System> Figure 1 is a diagram schematically showing an example of a progress management system according to the present embodiment. The progress management system 1 shown in Figure 1 is a system that manages the status of adjustment for selection of nursing care services to be used after discharge of a patient hospitalized in a hospital. Adjustment for selection of nursing care services includes interactions between a user U1 including a patient U1A or a family member U1B of the patient U1A, and one or more intermediaries U3 that introduce nursing care services. Adjustment for selection of nursing care services may also include interactions between the user U1 and one or more nursing care service providers U4.

[0022] The progress management system 1 includes a server 10 and terminals 30A, 30B, 30C. Furthermore, the progress management system 1 may also include a terminal 30D.

[0023] Server 10 may comprise one or more computers, one or more virtual machines or containers built in a cloud environment, or a combination thereof. Server 10 creates, updates, and outputs data 20A for patient U1A. Server 10 receives update instructions for data 20A from terminals 30A, 30B, 30C, and 30D.

[0024] Terminals 30A, 30B, 30C, and 30D communicate with server 10 using a web browser or dedicated application installed on each of them.

[0025] Terminals 30A, 30B, 30C, and 30D are used by user U1, medical professional U2, intermediary U3, and care service provider U4, respectively. Therefore, server 10 can function as a platform connecting user U1, medical professional U2, intermediary U3, and care service provider U4. Medical professional U2 refers to individuals engaged in hospital operations, including hospital staff, doctors, or nurses. Care service provider U4 includes operators of care facilities or providers of home care services.

[0026] Terminal 30A outputs instructions to the server 10 to create or update data 20A in response to operations by user U1. Terminal 30A also supports communication between user U1 and intermediary U3 or care service provider U4.

[0027] Terminal 30B outputs at least one of the following to server 10 in response to an operation by medical professional U2: an update of data 20A and an output instruction.

[0028] Terminal 30C outputs an update instruction for data 20A to server 10 in response to an operation by intermediary U3. Terminal 30C also supports communication between user U1 and intermediary U3.

[0029] Terminal 30D outputs an update instruction for data 20A to server 10 in response to an operation by care service provider U4. Terminal 30D supports communication between user U1 and care service provider U4.

[0030] User U1, healthcare professional U2, and intermediary U3 are examples of the “Second User,” “First User,” and “Third User” as defined in this disclosure, respectively.

[0031] In this specification, the term "terminal 30" is used when referring to common properties of terminals 30A, 30B, 30C, and 30D. Terminal 30 is, for example, a tablet, smartphone, personal computer, or any other information processing device.

[0032] <Server internal configuration> Figure 2 shows an example of the server shown in Figure 1. The server 10 shown in Figure 2 comprises a processor 10C, memory 10D, storage 10E, and a communication interface (IF) 10F.

[0033] The processor 10C includes a CPU (Central Processing Unit) or an MPU (Micro Processing Unit), etc. The processor 10C reads the program 106 stored in the storage 10E and expands it into memory 10D. The processor 10C executes the expanded program 106. By the processor 10C executing the program 106, the issuing unit 100, the creation unit 101, the update unit 102, and the output unit 103 are realized. Furthermore, the support unit 104 and the notification unit 105 may also be realized by the processor 10C executing the program 106. Note that if the server 10 is implemented by multiple computers, the processor 10C may include multiple processors provided by the multiple computers.

[0034] Memory 10D includes, for example, volatile storage devices such as DRAM (Dynamic Random Access Memory) or SRAM (Static Random Access Memory).

[0035] The storage 10E includes, for example, a non-volatile storage device such as an HDD (Hard Disk Drive), an SSD (Solid State Drive), or flash memory. The storage 10E also includes a storage device located inside the server 10 and a storage device connected to the server 10 via a network, such as a NAS (Network Attached Storage). The storage 10E stores the program 106, various information used to execute the program 106, and data 20A for each patient U1A. That is, the storage 10E stores the data 20A linked to the patient U1A's identification information (patient ID).

[0036] Furthermore, storage 10E may store intermediary information 20C for each intermediary U3. That is, storage 10E may store intermediary information 20C linked to the identification information (intermediary ID) of intermediary U3. In addition, storage 10E may store care service information 20D for each care service provider U4. That is, storage 10E may store care service information 20D linked to the identification information (care service provider ID) of care service provider U4.

[0037] Intermediary information 20C is registered according to input from terminal 30C. Intermediary information 20C shows the name of the intermediary, its location, and the area in which it can provide referrals. Intermediary information 20C also shows the referral record. The referral record shows the evaluation results of intermediary U3 from at least one of user U1 and medical professional U2, and the success rate of introducing care services. The evaluation results are shown, for example, on a 5-point scale from "1" to "5". The success rate is the ratio of the number of users U1 who had care services confirmed to be used after discharge by the scheduled discharge date to the total number of users U1 who were introduced to care services. Furthermore, intermediary information 20C may also show the intermediary fee and the content of the appeal to care managers and users U1.

[0038] The care service information 20D is registered according to the input from terminal 30D. The care service information 20D shows the name, address, conditions required of the user (e.g., level of care), fees, and available services (including medical services). In addition, the care service information 20D shows the availability of care services and the number of days required from application to service commencement.

[0039] Data 20A includes information 201 regarding the status of selection of care services and information 202 regarding the planned discharge date. Information 201 regarding the status of selection and information 202 regarding the planned discharge date are examples of the "first information" and "second information" in this disclosure, respectively.

[0040] The communication interface 10F communicates with the terminal 30 via a wired or wireless network.

[0041] The issuing unit 100 issues an access code associated with healthcare worker U2. Specifically, the issuing unit 100 receives an issuance instruction from terminal 30B. The issuance instruction has the identification information 20E of healthcare worker U2 attached to it. Upon receiving the issuance instruction, the issuing unit 100 creates an access code corresponding to the identification information 20E attached to the issuance instruction. The issuing unit 100 transmits the created access code to terminal 30B. The issuing unit 100 links the identification information 20E and the access code and stores them in storage 10E.

[0042] The creation unit 101 creates data 20A linked to the identification information 20E of healthcare professional U2 in response to access by user U1 using an access code. Specifically, upon receiving access using an access code, the creation unit 101 reads the identification information 20E linked to the access code from storage 10E. The creation unit 101 then creates data 20A linked to the read identification information 20E. When creating data 20A, the creation unit 101 may send an input form for the information included in data 20A to terminal 30A.

[0043] The update unit 102 updates the data 20A. The update unit 102 updates the data 20A to include adjustment status information 201 in response to instructions from at least one of user U1 and intermediary U3. The update unit 102 may also update the data 20A to include scheduled discharge date information 202 in response to instructions from at least one of user U1 and healthcare professional U2. Specifically, the update unit 102 receives an update request from at least one of terminals 30A, 30B, and 30C. The update unit 102 updates the data 20A based on the content of the update request. The update request includes at least the information to be changed and the content to be changed. The update unit 102 may also receive an update request from terminal 30D and update the data 20A based on the content of the update request.

[0044] Furthermore, the update unit 102 may update the adjustment status information 201 of the data 20A based on the support status of the support unit 104, which will be described later. Specifically, the update unit 102 may monitor the support status of the support unit 104 and update the adjustment status information 201 according to the monitoring results.

[0045] The output unit 103 outputs data 20A linked to the identification information 20E of healthcare professional U2 in response to a request from healthcare professional U2. Specifically, the output unit 103 receives an output instruction for data 20A from terminal 30B. The identification information 20E is attached to the output instruction. When the output unit 103 receives the output instruction, it reads the data 20A linked to the identification information 20E attached to the output instruction from storage 10E. The output unit 103 then transmits the read data 20A to terminal 30B.

[0046] The support unit 104 assists in the coordination between user U1 and one or more intermediary agents U3. Specifically, the support unit 104 outputs a screen (support screen) to terminals 30A and 30C to assist in the coordination between user U1 and intermediary agents U3, and receives input to the support screen. The support screen includes a screen containing at least one of intermediary agent information 20C and care service information 20D, a screen for requesting consultation with intermediary agent U3, and a chat screen for consultation. The support unit 104 processes the input to the support screen.

[0047] The support unit 104 may assist in the collaboration between user U1 and one or more care service providers U4. Specifically, the support unit 104 outputs a screen (support screen) to terminals 30A and 30D to assist in the collaboration between user U1 and care service providers U4, and receives input to the support screen. The support screen includes a screen containing care service information 20D, a screen for requesting consultation with care service providers U4, and a chat screen for consultation. The support unit 104 processes the input to the support screen.

[0048] The notification unit 105 periodically reads the data 20A. The notification unit 105 determines whether two conditions are met: firstly, that the difference between the scheduled discharge date indicated by the scheduled discharge date information 202 and the time when the data 20A was read is less than or equal to a threshold; and secondly, that the adjustment status information 201 does not include any planned care services to be used after discharge. If the notification unit 105 determines that both conditions are met, it outputs a notification (hereinafter referred to as a "reminder notification") to at least one of the medical professional U2 and user U1 to urge them to select care services. That is, if the notification unit 105 determines that both conditions are met, it outputs a reminder notification to at least one of the terminals 30A and 30B. Furthermore, if the notification unit 105 determines that both conditions are met, it may also output a reminder notification to terminal 30C.

[0049] The threshold included in the first condition may be a fixed value or may be set dynamically. For example, the threshold may be set by healthcare professional U2. Alternatively, the threshold may be set according to the number of applications for care services. Specifically, the threshold is set to be larger the smaller the number of applications for care services. For example, if the number of applications is 5 or less, the threshold is set to (10 - number of applications). Alternatively, the threshold may be set to the average number of days it takes to decide on care services.

[0050] <Flowchart for managing the progress of selecting care services> Figure 3 is a flowchart showing an example of the flow of adjustment for selecting care services implemented in the progress management system shown in Figures 1 and 2.

[0051] First, the processor 10C determines whether or not an access code issuance instruction has been entered from the terminal 30B (step S1). The issuance instruction is accompanied by the identification information 20E of the medical professional U2. If the processor 10C determines that no issuance instruction has been entered (NO in step S1), it repeats step S1.

[0052] The issuance instruction is input from terminal 30B when operation S101 is performed on terminal 30B. Operation S101 is an operation in which healthcare worker U2 requests the issuance of an access code. In response to operation S101, terminal 30B sends an issuance instruction to server 10 with the identification information 20E of healthcare worker U2 attached.

[0053] If the processor 10C determines that an issuance instruction has been entered (YES in step S1), it issues an access code linked to the identification information 20E of the medical professional U2 and transmits it to the terminal 30B (step S2). The access code may include, for example, a string representing a URL (Uniform Resource Locator) or a two-dimensional code.

[0054] Upon receiving the access code, healthcare worker U2 performs action S102. Action S102 is the action of distributing the issued access code to user U1. For example, methods of distributing the access code include delivery by email and printing.

[0055] Next, the processor 10C determines whether or not it has received an access request using an access code from the terminal 30A (step S3). If the processor 10C determines that it has not received an access request (NO in step S3), it repeats step S3.

[0056] Access using an access code is performed by operation S103 on terminal 30A. Operation S103 is the operation in which user U1 specifies the connection destination indicated by the access code.

[0057] If the processor 10C determines that it has received access using an access code (YES in step S3), it reads the identification information 20E of the healthcare worker U2 associated with the access code from the storage 10E. The processor 10C creates data 20A associated with the read identification information 20E (step S4). When creating data 20A, the processor 10C may output an instruction to input the planned discharge date to at least one of terminals 30A and 30B. The processor 10C updates the planned discharge date information 202 in data 20A to indicate the entered planned discharge date.

[0058] Next, the processor 10C determines whether or not it has provided terminals 30A and 30C with a support screen to assist in the collaboration between user U1 and intermediary U3 (step S5).

[0059] Operation S104 may be performed on the support screen. Operation S104 is an input operation on the support screen by user U1 or intermediary U3.

[0060] In step S5, the processor 10C may determine whether or not it has provided terminals 30A and 30D with a support screen to assist in the collaboration between user U1 and care service provider U4. In this case, user U1 or care service provider U4 will perform an input operation on the support screen.

[0061] If the processor 10C determines that a support screen has been provided (YES in step S5), it updates data 20A based on the input to the support screen (step S6). In step S6, the adjustment status information 201 and the scheduled discharge date information 202 of data 20A are updated as appropriate.

[0062] If it determines that a support screen is not provided (NO in step S5), or after step S6, the processor 10C determines whether or not an output instruction has been input from terminal 30B (step S7).

[0063] The output instruction is input from terminal 30B when operation S105 is performed on terminal 30B. Operation S105 is an operation in which healthcare worker U2 requests to view data 20A. The output instruction is accompanied by the identification information 20E of healthcare worker U2.

[0064] When the processor 10C determines that an output instruction has been input (YES in step S7), it outputs data 20A corresponding to the identification information 20E attached to the output instruction to the terminal 30B (step S8).

[0065] If it determines that no data output instruction has been entered (NO in step S7), or after step S8, the processor 10C determines whether the current time is after the scheduled discharge date based on the scheduled discharge date information 202 (step S9). If the processor 10C determines that the current time is before the scheduled discharge date (NO in step S9), it returns to the process in step S5.

[0066] If the processor 10C determines that the current time is after the scheduled discharge date (YES in step S9), it requests at least one of the user U1 and the medical professional U2 to evaluate the intermediary U3 (step S10). Specifically, the processor 10C outputs a screen requesting evaluation of the intermediary U3 to at least one of the terminals 30A and 30B.

[0067] When terminals 30A and 30B receive the evaluation request screen, operation S106 is performed. Operation S106 is the operation in which user U1 or healthcare professional U2 inputs the evaluation results to intermediary U3.

[0068] Figure 4 shows an example of a screen for requesting an evaluation from an intermediary. As shown in Figure 4, the evaluation screen includes a display field 40 and an evaluation entry field 41. The display field 40 is created based on data 20A. The evaluation entry field 41 is used to enter the evaluation results.

[0069] Next, the processor 10C updates the referral record (evaluation result) of the intermediary information 20C based on input from user U1 and healthcare professional U2 (step S11). At this time, the processor 10C also updates the success rate included in the referral record based on the adjustment status information 201.

[0070] <Example Data> Figure 5 shows an example of data managed by the progress management system. Figure 5 shows data 20A for four patients U1A. As shown in Figure 5, data 20A includes hospital ID, adjustment status, name, planned discharge date, system registration date, intermediary ID, desired conditions for care services, care services inquired about, care services visited, care services applied for, planned care services to be used, and service start date. Specifically, data 20A includes the following elements (hereinafter referred to as "data fragments"): hospital ID 700, status 701, name 702, planned discharge date 703, system registration date 704, intermediary ID 705, preferences 706, inquiries 707, visits 708, applications 709, services used 710, and service start date 711.

[0071] Discharge date information 202 includes the scheduled discharge date 703. Coordination status information 201 includes status 701, intermediary ID 705, preference 706, inquiry 707, visit 708, application for use 709, service used 710, and service start date 711.

[0072] Next, the method for creating data 20A will be explained. When processor 10C determines that it has received access using an access code, it reads the identification information 20E of healthcare worker U2 associated with the access code from storage 10E. Processor 10C then creates data 20A linked to the read identification information 20E. Here, processor 10C links the identification information 20E and data 20A by writing the identification information 20E to the hospital ID 700 of the created data 20A.

[0073] When processor 10C creates data 20A, it outputs an instruction to terminal 30A to input the name of patient U1A. Based on the information input from terminal 30A, processor 10C updates the name 702. Processor 10C outputs an instruction to input the planned discharge date 703 to at least one of terminals 30A and 30B. Based on the information input from at least one of terminals 30A and 30B, processor 10C updates the planned discharge date 703.

[0074] Refer to Figure 6 to explain the updating of the intermediary ID 705 and the desired intermediary ID 706. Figure 6 is a diagram showing an example of a support screen, which is a consultation request screen for an intermediary. The support screen shown in Figure 6 is created by the processor 10C and displayed on the terminal 30A. The support screen shown in Figure 6 includes an input form for entering the name, consultation details, and intermediary. Specifically, the input form includes a name input field 500 for entering the name of user U1, a consultation details input field 501 for entering the consultation details, and an intermediary input field 502 for entering the desired intermediary. User U1 performs the input operation on the consultation request screen according to the displayed content. The processor 10C inquires with the terminal 30C of intermediary U3, which was entered in the intermediary input field 502, whether or not the consultation can be accepted. When the processor 10C receives a response of acceptance from the terminal 30C, it updates the intermediary ID 705 to indicate intermediary U3 (the intermediary to be consulted) which was entered in the intermediary input field 502. Intermediary ID 705 corresponds to intermediary information 20C. Processor 10C updates preference 706 based on the input in consultation content input field 501. For example, based on the input "I wish to be admitted to a nursing care facility" in consultation content input field 501, processor 10C updates preference 706 to indicate "facility".

[0075] Refer to Figures 7-9 to explain the updates to Situation 701, Inquiry 707, Visit 708, Application for Use 709, Service Used 710, and Service Start Date 711.

[0076] Figure 7 shows an example of a support screen, specifically an introduction screen for care services. The support screen shown in Figure 7 includes a display field 60, a "Visit Application" button 61, an "Inquiry" button 62, and an "Admission Application" button 63. The display field 60 is created based on the care service information 20D and displays the details of the care service. User U1 confirms the displayed content and performs input operations on the introduction screen. The processor 10C switches the support screen based on the selected button. For example, when the "Visit Application" button 61 is selected, the processor 10C outputs the care service visit application screen. Also, when the "Inquiry" button 62 is pressed, the processor 10C outputs the care service inquiry screen. When the "Admission Application" button 63 is pressed, the processor 10C outputs the care service application screen.

[0077] Figure 8 shows an example of a support screen, specifically a screen for applying to visit a care service. The application screen shown in Figure 8 includes an input form for entering name, phone number, and contact information, as well as an application button. User U1 performs the input operation on the application screen according to the displayed content. Based on the input to the application button, Processor 10C updates the visit 708 to indicate the care service to be applied for. The entered information is output to terminal 30C or terminal 30D. Intermediary U3 checks the information output to terminal 30C and coordinates the visit arrangements with care service provider U4. Care service provider U4 checks the information output to terminal 30D and coordinates the visit arrangements with user U1.

[0078] Inquiry 707 is updated in the same manner as Inquiry 708. That is, the processor 10C updates inquiry 707 to indicate the care service to be inquired about, based on the input to the care service inquiry screen.

[0079] Figure 9 shows an example of a support screen, specifically a screen for applying for long-term care services. The application screen shown in Figure 9 includes input forms for name and desired conditions, and an application button. User U1 performs input operations on the application screen according to the screen content. When the application button is pressed, processor 10C outputs a support screen showing the application details to terminal 30C or terminal 30D. Also, when the application button is pressed, processor 10C updates application 709 to indicate the long-term care service to which the application is being made. Intermediary U3 checks the information output to terminal 30C and coordinates the arrangements for using long-term care services with long-term care service provider U4. Long-term care service provider U4 checks the information output to terminal 30D and coordinates the arrangements for using long-term care services with user U1.

[0080] The processor 10C outputs an input instruction to at least one of terminals 30C and 30D to determine whether or not user U1 is eligible to use care services. Upon receiving input from at least one of terminals 30C and 30D indicating that the service is available, the processor 10C updates the service to be used 710 and the service start date 711 based on the information entered on the application screen.

[0081] Furthermore, upon receiving input indicating that two or more care services are available, the processor 10C outputs a screen to the terminal 30A for selecting the care services to be used. The processor 10C then updates the service 710 to indicate the selected care services.

[0082] The processor 10C sets the status 701 to "Under Consideration" as the default. The processor 10C updates the status 701 to indicate "Decision" when it receives input from at least one of terminals 30C and 30D that care services are available.

[0083] Thus, data 20A is updated as needed in response to input from terminal 30. Furthermore, data 20A is updated as needed in response to input on the support screen for collaboration between user U1 and intermediary U3 or care service provider U4. Therefore, data 20A shows the latest progress.

[0084] <Screen showing adjustment status> When the processor 10C determines that an output instruction has been received, it outputs data 20A corresponding to the identification information 20E attached to the output instruction to the terminal 30B. The method of outputting data 20A is, for example, to output a confirmation screen of the adjustment status that includes the information indicated by data 20A. This allows the medical professional U2 to check the adjustment status of the selection of care services for patient U1A at any time.

[0085] Figure 10 shows an example of a screen for checking the adjustment status. As shown in Figure 10, the screen for checking the adjustment status displays the adjustment status, name, expected discharge date, system registration date, name of the intermediary, desired conditions for care services, number of care services inquired about, number of care services visited, number of care services applied for, planned care services, and the start date of care service use. The adjustment status, name, expected discharge date, system registration date, name of the intermediary, desired conditions for care services, planned care services, and start date of care service use are based on the data fragments Status 701, Name 702, Expected Discharge Date 703, System Registration Date 704, Intermediary ID 705, Desired Conditions 706, Services Used 710, and Service Start Date 711, respectively. The number of care services inquired about, the number of care services visited, and the number of care services applied for correspond to the number of care services shown in Inquiry 707, Visit 708, and Application 709, respectively.

[0086] The text on the confirmation screen showing the name of the intermediary includes a hyperlink to a detailed screen showing the content of the intermediary information 20C corresponding to the intermediary name. The text on the confirmation screen showing the name of the care service includes a hyperlink to a detailed screen showing the content of the care service information 20D corresponding to the care service name. In addition, the text showing the number of care services inquired about, the number of care services visited, and the number of care services applied for includes a hyperlink to a screen showing one or more care service information 20D corresponding to inquiry 707, visit 708, and service used 710, respectively. For example, if inquiry 707 indicates two care services, the confirmation screen will include the text "2 items" indicating the number of care services inquired about. The text "2 items" also includes hyperlinks to screens showing the two care service information 20D corresponding to inquiry 707. User U1 and healthcare professional U2 can view detailed information about the care service or intermediary by clicking the hyperlink. Furthermore, user U1 and healthcare professional U2 can view a list of care services related to their selection by clicking on the hyperlink for the number of items.

[0087] <Notification Processing> Refer to Figures 11-13 to explain the notification process. Figure 11 is a flowchart showing an example of the output process for reminder notices. For example, the flowchart shown in Figure 11 is executed daily. The flow shown in Figure 11 may be executed in parallel with the flow shown in Figure 3.

[0088] First, the processor 10C reads each data 20A (step S201). Based on the planned discharge date information 202 contained in the data 20A, the processor 10C determines whether the number of days from the present to the patient U1A's planned discharge date is less than or equal to a threshold (step S202). If it determines that the number of days until the planned discharge date is greater than the threshold (NO in step S202), the processor 10C terminates processing.

[0089] If the processor determines that the number of days until the scheduled discharge date is below a threshold (YES in step S202), the processor 10C determines whether or not care services to be used after discharge are registered in the adjustment status information 201 (step S203). If the processor 10C determines that care services to be used after discharge are registered (YES in step S203), it terminates the process.

[0090] If processor 10C determines that no care services to be used after discharge are registered (NO in step S203), it determines whether or not the intermediary agency U3 to be consulted is registered in the coordination status information 201 (step S204).

[0091] If the processor 10C determines that the intermediary U3 to be consulted is not registered (NO in step S204), it selects a specific intermediary from among one or more intermediary U3 (step S205). Specifically, the processor 10C calculates an evaluation value for each of the one or more intermediary U3 based on the referral record included in the intermediary information 20C. Then, the processor 10C selects an intermediary with a relatively high evaluation value. For example, the processor 10C selects an intermediary with an evaluation value higher than the standard value (e.g., 4.0).

[0092] The evaluation value is calculated from at least one of the following: the evaluation results of one or more intermediaries U3 by healthcare professional U2 or user U1, and the success rate of referrals by the intermediary. For example, processor 10C may calculate the evaluation value as the average of the evaluation results from user U1. Processor 10C may calculate the evaluation value as the average of the evaluation results from healthcare professional U2. Processor 10C may calculate the evaluation value as the average of the evaluation results from user U1 and healthcare professional U2. Processor 10C may determine the success rate as the evaluation value. Alternatively, processor 10C may calculate the evaluation value based on the average of the evaluation results from user U1, the average of the evaluation results from healthcare professional U2, and the success rate. Specifically, if patient U1A has an average evaluation result of 4.0 from user U1, an average evaluation result of 2.5 from healthcare professional U2, and a success rate of 80% (converted to 4.0 on a 5-point scale), the evaluation value would be 3.5.

[0093] If the processor 10C determines that the intermediary U3 to be consulted is registered (NO in step S204), or if it performs step S206 after step S205, it performs step S206. In step S206, the processor 10C refers to the care service information 20D and identifies one or more care service candidates that can be used from the scheduled discharge date, based on the availability of one or more care services and the number of days required from application to service commencement.

[0094] Next, the processor 10C outputs a notification (reminder notification) to at least one of the terminals 30A and 30B to prompt the selection of post-discharge care services (step S207). For example, the processor 10C outputs a notification screen representing the reminder notification to at least one of the terminals 30A and 30B. By checking the reminder notification output from the server 10, user U1 can recognize that patient U1A needs to urgently select the care services to receive after discharge. In addition, healthcare professional U2 can prompt user U1 to select care services at an appropriate time.

[0095] In step S207, if the adjustment status information 201 indicates that the intermediary U3 is the one to be consulted, the processor 10C may also output a reminder notification to the terminal 30C of the intermediary U3. This allows the intermediary U3 to recognize that it is necessary to expedite communication with user U1 in order to select care services.

[0096] Processor 10C adds information about a specific intermediary to the reminder notice. Furthermore, processor 10C adds information about one or more care service candidates to the reminder notice.

[0097] Figure 12 shows an example of a notification screen. The notification screen shown in Figure 12 includes a display field 111 for a specific intermediary selected in step S205. Specifically, the display field 111 includes the names of one or more intermediaries, a rating for each intermediary, and the area in which they can be introduced. Furthermore, the processor 10C may include display fields 112 for other intermediaries of the specific intermediary in the notification screen. The processor 10C may highlight the display field 111 to clearly distinguish it from the display field 112.

[0098] This makes it easier for user U1, who has not yet decided on a referral service provider, to choose one by referring to the notification screen shown in Figure 12. Alternatively, it makes it easier for healthcare professional U2 to introduce a referral service provider to user U1.

[0099] Figure 13 shows another example of a notification screen. As shown in Figure 13, the notification screen includes information on one or more care service candidates identified in step S206. Information on each care service candidate is generated based on the care service information 20D and includes, for example, the name, address, requirements for the user (e.g., level of care), fees, and available services (including medical services).

[0100] This makes it easier for user U1 to select care services by referring to the notification screen shown in Figure 13. Alternatively, it makes it easier for healthcare professional U2 to assist user U1 in selecting care services.

[0101] Furthermore, if the processor 10C includes a care service that is the subject of the advertisement among one or more care service candidates, it may highlight the information of the care service that is the subject of the advertisement.

[0102] <Variation> The processor 10C may provide terminals 30C and 30D with a screen for receiving updates to the data 20A. This allows the intermediary U3 or the care service provider U4 to input an update instruction for the data 20A on the screen at any time. The processor 10C updates the data 20A in response to the update instruction.

[0103] <Note> The embodiments and variations described above include the following technical concepts. [Configuration 1] It is a progress management system, An issuing department that issues access codes associated with the first user working in the hospital, A creation unit that creates data of the patient linked to the identification information of the first user, in response to access by a second user who is a patient hospitalized in the above hospital or a family member of the above patient using the above access code, An update unit updates the data to include first information indicating the status of adjustments to the selection of care services, in response to one or more third users who introduce the care services that the above-mentioned patient will use after discharge to the above-mentioned second user, or instructions from the above-mentioned second user. A progress management system comprising an output unit that outputs the data linked to the identification information in response to a request from the first user. [Configuration 2] It includes a support unit that assists in the collaboration between the above-mentioned second user and the above-mentioned one or more third users, The update unit described above is a progress management system as described in Configuration 1, which updates the above-mentioned First Information based on the support status of the above-mentioned collaboration. [Configuration 3] The update unit updates the data to include second information indicating the patient's scheduled discharge date, in response to instructions from the first or second user. A progress management system according to configuration 1 or 2, comprising a notification unit that outputs a notification to at least one of the first user and the second user urging them to select the care services, based on the fact that the number of days until the scheduled discharge date is below a threshold and the first information does not include information indicating the schedule for the care services to be used after discharge. [Structure 4] Based on the fact that the above-mentioned first information does not include information indicating the third user to whom the consultation was made, the notification unit stated: Select a specific third user from among the one or more third users mentioned above. The progress management system described in Configuration 3, which adds the information of the specific third-party user to the above notification. [Composition 5] The progress management system described in Configuration 4, wherein the above-mentioned specific third user is selected based on the evaluation value for each of the above one or more third users. [Composition 6] The progress management system according to configuration 5, wherein the above evaluation value is calculated from at least one of the evaluation results of the first user or the second user for the target third user among the one or more third users, and the success rate of the target third user. [Composition 7] The above notification section is, Based on the availability of one or more care services and the number of days required from application to service commencement, identify one or more potential care services that can be used from the above-mentioned scheduled discharge date. A progress management system according to any of configurations 3 to 6, which adds information on one or more care service candidates to the above notification. [Structure 8] A method for managing progress, One or more processors issue an access code associated with the first user working in the hospital, The above one or more processors create data of the above patient linked to the identification information of the first user in response to access by a second user, who is a patient hospitalized in the above hospital or a family member of the above patient, using the above access code. The above one or more processors update the above data to include first information indicating the status of adjustments to the selection of care services, in response to instructions from the above second user or from the above second user, in order to introduce the above second user to the above second user of care services that the above patient will use after discharge. A progress management method comprising the above-mentioned one or more processors outputting the above-mentioned data associated with the above-mentioned identification information in response to a request from the above-mentioned first user. [Composition 9] A program that causes a computer to execute a progress management method, The above progress management method is: To issue an access code associated with the first user working in the hospital, In response to access by a second user, who is a patient hospitalized in the above hospital or a family member of the above patient, using the above access code, data of the above patient is created, linked to the identification information of the first user. The above data is updated to include first information indicating the status of the selection and coordination of care services, based on the instructions of one or more third users or the second user to introduce the care services that the above patient will use after discharge to the above second user, A program comprising outputting the data associated with the above identification information in response to a request from the above-mentioned first user.

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

[0105] 1 Progress Management System, 10 Server, 10C Processor, 10D Memory, 10E Storage, 10F Communication Interface, 20A Data, 20C Intermediary Information, 20D Care Service Information, 20E Identification Information, 30, 30A, 30B, 30C, 30D Terminal, 40 Display Field, 41 Evaluation Entry Field, 60 Display Field, 61 Visit Application Button, 62 Inquiry Button, 63 Admission Application Button, 100 Issuance Section, 101 Creation Section, 102 Update Section, 103 Output Section, 104 Support Section, 105 Notification Section, 106 Program, 111, 112 Display Field, 201 Adjustment Status Information, 202 Discharge Date Information, 500 Name Input Field, 501 Consultation Details Input Field, 502 Intermediary Input Field, U1 User, U1A Patient, U1B Family members, U2 healthcare workers, U3 intermediaries, U4 care service providers.

Claims

1. It is a progress management system, An issuing department that issues access codes associated with the first user engaged in hospital operations, A creation unit that creates patient data linked to the identification information of the first user in response to access by a second user, who is a patient hospitalized in the hospital or a family member of the patient, using the access code, An update unit updates the data to include first information indicating the status of adjustments to the selection of care services, in response to instructions from one or more third users or the second user to introduce care services that the patient will use after discharge to the second user. A progress management system comprising: an output unit that outputs the data associated with the identification information in response to a request from the first user.

2. The system includes a support unit that assists in the cooperation between the second user and the one or more third users, The progress management system according to claim 1, wherein the update unit updates the first information based on the support status of the collaboration.

3. The update unit updates the data to include second information indicating the patient's scheduled discharge date, in response to instructions from the first or second user. The progress management system according to claim 1 or 2, further comprising a notification unit that outputs a notification to at least one of the first user and the second user urging them to select the care services, based on the fact that the number of days until the scheduled discharge date is below a threshold and the first information does not include information indicating the schedule for the care services to be used after discharge.

4. The notification unit, based on the fact that the first information does not include information indicating the third user to whom the consultation is made, Select a specific third user from among the one or more third users mentioned above. The progress management system according to claim 3, wherein information of the specific third user is added to the notification.

5. The progress management system according to claim 4, wherein the specific third user is selected based on the evaluation value for each of the one or more third users.

6. The progress management system according to claim 5, wherein the evaluation value is calculated from at least one of the evaluation results of the first user or the second user for the target third user among the one or more third users, and the success rate of the target third user.

7. The aforementioned notification unit, Based on the availability of one or more care services and the number of days required from application to service commencement, one or more potential care services available from the scheduled discharge date will be identified. The progress management system according to claim 3, wherein information on one or more care service candidates is added to the notification.

8. A method for managing progress, One or more processors issue an access code associated with a first user working in the hospital, The one or more processors create patient data linked to the identification information of the first user in response to access by a second user, who is a patient hospitalized in the hospital or a family member of the patient, using the access code. The one or more processors update the data to include first information indicating the status of adjustments to the selection of care services, in response to instructions from one or more third users or the second user to introduce care services that the patient will use after discharge to the second user. A progress management method comprising the one or more processors outputting the data associated with the identification information in response to a request from the first user.

9. A program that causes a computer to execute a progress management method, The aforementioned progress management method is, To issue an access code associated with the first user working in the hospital, In response to access by a second user, who is a patient hospitalized in the aforementioned hospital or a family member of the aforementioned patient, using the access code, data of the aforementioned patient is created, linked to the identification information of the first user. The data is updated to include first information indicating the status of the selection of care services, in response to instructions from one or more third users or the second user to introduce the care services that the patient will use after discharge to the second user, A program comprising outputting the data associated with the identification information in response to a request from the first user.

Images