JP7486061B1 - Nursing care and/or medical support system, program, computer device, and information processing method - Google Patents

Abstract

[Problem] To provide a nursing care and/or medical support system that allows businesses in different industries to easily cooperate with each other and that easily satisfies the needs of each business. [Solution] A nursing care and/or medical support system is realized by a plurality of terminal devices and a server device. The plurality of terminal devices include a first terminal device of a first user who belongs to a predetermined area, and a second terminal device of a second user. The server device includes a first allocation unit that allocates a patient who belongs to the predetermined area to the first user, a first ticket generation unit that generates a first ticket, a first update unit that updates the status of the first ticket based on input of first information to the first terminal device, a second allocation unit that allocates the patient to the second user when a predetermined condition is satisfied, a second ticket generation unit that generates a second ticket, and a second update unit that updates the status of the second ticket based on input of second information to the second terminal device. [Selected Figure] FIG.

Description

The present invention relates to a nursing care and/or medical care support system, a program, a computer device, and an information processing method.

In recent years, attention has been focused on the community-based comprehensive care system, which provides comprehensive medical and nursing care support tailored to the circumstances of each local community within the framework of the local community where people live. In a community-based comprehensive care system, the community-based comprehensive care support center, multiple medical institutions, nursing care institutions, and other operators in the area are required to share necessary information and cooperate with each other to efficiently provide various services.

As an example of a system that links a local medical system and a nursing care system, Patent Document 1 discloses a nursing care support system that includes a nursing care support information management server that transmits and receives information between a terminal device of a nursing care institution and a medical information providing server that constitutes a medical system linked to a specified electronic medical record information system, and provides medical information to the terminal device that is determined to be able to access the medical information.

JP 2015-28773 A

In a community-based comprehensive care system, it is necessary for many businesses in different industries within the region to work together to care for patients. In other words, a community-based comprehensive care system requires collaboration between medical institutions and care institutions, and between the community-based comprehensive care support center and medical institutions and care institutions, but Patent Document 1 does not disclose how this collaboration will occur.

When looking at the many businesses such as community comprehensive care support centers, medical institutions, and nursing care institutions, their functions and characteristics differ greatly between different industries, and even within the same industry, their functions and characteristics differ depending on the specialty, facilities, number of employees, etc. In this situation, if an on-premises system is adopted in which each business installs its own server, the interfaces connecting the servers of each business must be developed individually, and there is a risk that the different interface systems between each business will cause problems in collaboration. On the other hand, if a public cloud such as the SaaS (Software as a Service) system is adopted, it will be difficult to meet the needs of each business, which has different functions and characteristics.

The present invention has been made in consideration of the above problems. In other words, the present invention is a support system that supports the creation of a community-based comprehensive care system in which businesses within a given area work together to provide care and/or medical care to patients, and aims to provide a support system that makes it easy for businesses in different industries to work together and that easily satisfies the needs of each business.

A nursing care and/or medical support system according to an embodiment of the present invention includes:
A nursing care and/or medical support system realized by a plurality of terminal devices and a server device communicably connected to each of the plurality of terminal devices,
The plurality of terminal devices
a first terminal device used by a first user who belongs to a predetermined area;
a plurality of second terminal devices used by a plurality of second users each belonging to the predetermined region and each in a different business from that of the first users;
The server device
A registration unit that registers patient data of patients who belong to the predetermined region;
a first allocation unit that allocates a patient indicated by the registered patient data to the first user;
a first ticket generating unit configured to generate a first ticket for managing a task of the first user for a patient assigned to the first user;
a first update unit that updates a status of the first ticket based on first information input by the first user to the first terminal device;
a second allocation unit that allocates a patient assigned to the first user to one of the plurality of second users based on the first information when a status of the first ticket satisfies a predetermined condition;
a second ticket generating unit configured to generate a second ticket for managing a task of the second user for a patient assigned to the second user;
a second update unit that updates a status of the second ticket based on second information input by the second user to the second terminal device;
including.

The present invention provides a support system that supports the creation of a community-based comprehensive care system in which businesses within a specified area work together to provide care and/or medical care to patients, and that makes it easy for businesses in different industries to work together and to satisfy the needs of each business.

FIG. 1 is a schematic diagram showing an example of the configuration of a support system according to an embodiment of the present invention. FIG. 2 is a block diagram showing an example of the configuration of a terminal device. FIG. 3 is a block diagram showing an example of the configuration of a server device. FIG. 4 is a schematic diagram showing an example of a method of providing services to patients from each business operator in a conventional example and a method of providing services to patients by a support system according to an embodiment of the present invention. FIG. 5 is a flowchart showing an example of processing by the support system according to an embodiment of the present invention. FIG. 6 is a schematic diagram showing an example of task management using tickets. FIG. 7 is a schematic diagram showing an example of a change in a task managed by a ticket. FIG. 8 is a flowchart showing an example of processing by the support system according to an embodiment of the present invention. FIG. 9 is a schematic diagram showing an example of invalid ticket information.

The following describes an embodiment of the present invention with reference to the drawings. Note that in each drawing, the same elements are given the same reference numerals, and duplicate descriptions will be omitted as appropriate.

(System Configuration)
FIG. 1 is a schematic diagram showing an example of the configuration of a support system according to an embodiment of the present invention. The support system 100A is a system for supporting the construction of a community-based comprehensive care system in a predetermined area A. The support system 100A includes a plurality of first terminal devices 10 such as first terminal devices 10A and 10B, a plurality of second terminal devices 20 such as second terminal devices 20A and 20B, a plurality of third terminal devices 30 such as third terminal devices 30A and 30B, and a server device (computer device) 50A. Each terminal device included in the support system 100A is a terminal device used by a business operator belonging to a predetermined area A. Note that the "business operator belonging to area A" refers to, for example, a business operator that provides or can provide nursing care or medical services in area A.

The support system 100B is a system for supporting the construction of a community-based comprehensive care system in a specified area B. The support system 100B includes a plurality of first terminal devices 10 such as first terminal devices 10C, 10D, a plurality of second terminal devices 20 such as second terminal devices 20C, 20D, a plurality of third terminal devices 30 such as third terminal devices 30C, 30D, and a server device (computer device) 50B. Each terminal device included in the support system 100B is a terminal device used by a business operator belonging to the specified area B. Note that an "enterprise belonging to area B" refers to, for example, a business operator that provides or can provide nursing care or medical services in area B.

Support system 100A and support system 100B differ in the number of terminal devices they include and the areas they support, but they have the same main elements and functions. Similarly, server device 50A and server device 50B also have the same main elements and functions. Therefore, in the following explanation, support systems 100A and 100B will be collectively referred to as support system 100, and server devices 50A and 50B will be collectively referred to as server device 50.

Each terminal device is a device used by each business operator belonging to the region. The first terminal device 10 is, for example, a terminal used by a regional comprehensive care support center (hereinafter also simply referred to as the "support center"), which is a comprehensive supporter of nursing care and/or medical care in the specified region, or a care manager (care manager). The second terminal device 20 is, for example, a terminal used by a nursing care institution. Note that "nursing care institutions" include businesses that provide home-based services such as visiting care and day care, and businesses that provide facility/residential services such as nursing care facilities for the elderly and life care for residents of specific facilities. The third terminal device 30 is, for example, a terminal used by a medical institution. Although not shown in the figure, the support system 100 may further include a fourth terminal device used by businesses that provide life support and nursing care prevention, such as senior citizens' clubs and NPOs.

Each terminal device may be a stationary terminal such as a desktop PC (personal computer), or may be a portable terminal such as a notebook PC, smartphone, tablet, or wearable device.

Here, the "first user" and "second user" described in the claims are not particularly limited as long as they are a combination of businesses of different industries as described above. For example, if the "first user" described in the claims is a support center or a care manager, the "second user" described in the claims may be a care facility and/or a medical institution. In this case, the "first terminal device" described in the claims corresponds to the first terminal device 10 in FIG. 1, and the "second terminal device" described in the claims corresponds to the second terminal device 20 and/or the third terminal device 30 in FIG. 1.

For example, if the "first user" described in the claims is a medical institution, the "second user" described in the claims may be a care facility. In this case, the "first terminal device" described in the claims corresponds to the third terminal device 30 in FIG. 1, and the "second terminal device" described in the claims corresponds to the second terminal device 20 in FIG. 1. In this case, instead of or in addition to the care facility, the "second user" described in the claims may include a support center or a care manager. In other words, the "second terminal device" described in the claims may include the first terminal device 10 instead of or in addition to the second terminal device 20.

The server device 50 can be connected to each of the terminal devices via the communication network 40. The support system 100 is configured, for example, as a private cloud type system. Operation input information received by each terminal device is transmitted to the server device 50, and the results of various processes performed by the server device 50 are received by each terminal device.

(Configuration of terminal device)
Fig. 2 is a block diagram showing an example of the configuration of a terminal device. The first terminal device 10 shown in Fig. 2 includes a control unit (processor) 11, a storage unit (storage, memory) 15, and a communication IF (Interface) 16. Although Fig. 2 shows an example of the configuration of the first terminal device 10, the second terminal device 20 and the third terminal device 30 may also adopt a similar configuration. Furthermore, each terminal device may be configured to be able to connect to the server device 50 after being authenticated by, for example, ID authentication, password authentication, or the like.

The control unit 11 controls the operation of the first terminal device 10. The control unit 11 includes, for example, a CPU (Central Processing Unit), an MPU (Micro Processing Unit), a GPU (Graphics Processing Unit), etc. The control unit 11 can function as the transmission/reception unit 12, the display unit 13, and the operation input unit 14 by reading and executing programs stored in the memory unit 15.

The transmission/reception unit 12 is connected to the communication network 40 via the communication IF 16, for example, and transmits and receives various information to and from the server device 50. Specifically, the operation input unit 14 transmits information received by the server device 50 and receives information for displaying the results of various processes performed by the server device 50. The display unit 13 outputs the information received from the server device 50 as an image to a display device. The display device may be a display mounted on the first terminal device 10 or an external display connected to the first terminal device 10. The operation input unit 14 accepts operation input from a user. Specifically, the operation input unit 14 accepts input of information (first information or second information described below) related to a task to be performed by an operator using the first terminal device 10. The operation input unit 14 may include, for example, a keyboard or a touch panel.

The storage unit 15 includes a ROM (Read Only Memory) and a RAM (Random Access Memory). The storage unit 15 stores programs used by the first terminal device 10 and various data received from the server device 50. The communication IF 16 performs signal modulation/demodulation processing and frequency conversion processing, for example, so that the first terminal device 10 can transmit and receive information to and from other communication devices. In addition to the above, the first terminal device 10 may also have various functions that are conventionally known.

(Configuration of the server device)
3 is a block diagram showing an example of the configuration of a server device 50. The server device 50 shown in FIG.

The control unit 51 controls the operation of the server device 50. The control unit 51 is configured to include, for example, a CPU, an MPU, a GPU, etc. The control unit 51 can function as a transmission/reception unit 52, a display unit 53, an operation input unit 54, a registration unit 55, an allocation unit 56, a ticket generation unit 57, an update unit 58, and an invalidation management unit 59 by reading and executing a program 62 stored in the memory unit 61.

The transmission/reception unit 52 is connected to the communication network 40 via the communication IF 65, for example, and transmits and receives various information to and from each terminal device, such as the first terminal device 10, the second terminal device 20, and the third terminal device 30. Specifically, it receives information related to operation inputs received by each terminal device, and transmits information to each terminal device for displaying the results of various processes performed by the server device 50 on each terminal device. The display unit 53 outputs the processing results of the server device 50 as images to an external display connected to the server device 50. The operation input unit 54 receives operation inputs from an administrator of the server device 50. The operation input unit 54 may include, for example, a keyboard. Note that if the server device 50 does not have an interface for connecting to an external display, keyboard, or the like, the display unit 53 and the operation input unit 54 may not have the functions.

The registration unit 55 registers data on patients who belong to a specific region corresponding to the support system 100 in the storage unit 61 as patient data 63. The patient data is received, for example, from each terminal device or input based on the operation of an administrator of the server device 50. The patient data 63 may include, for example, the patient's name, address, and information related to the patient's health, such as PHR (Personal Health Record) data and EHR (Electric Health Record) data.

The allocation unit 56 allocates the patient indicated by the patient data 63 registered by the registration unit 55 to one of the businesses. The allocation unit 56 may, for example, determine the business to which the patient is to be allocated based on the contents of the patient data 63. The allocation unit 56 may also, for example, determine the business to which the patient is to be allocated by referring to the business data 65 instead of or in addition to the patient data 63.

The allocation unit 56 includes a first allocation unit 56A that allocates a patient to a first user, and a second allocation unit 56B that allocates a patient to a second user. For example, when the patient data 63 is referenced and a visit by a support center or a care manager has not been made, or a support plan has not been formulated, the first allocation unit 56A may select either a support center or a care manager as the first user and allocate the patient. Also, when the patient data 63 is referenced and it is determined that an urgent examination is necessary, the first allocation unit 56A may select any medical institution as the first user and allocate the patient.

When the status of the first ticket, which will be described later, satisfies a predetermined condition, the second allocation unit 56B allocates the patient that was assigned to the first user to one of the multiple second users based on the first information, which will be described later. In addition, when the status of the second ticket, which will be described later, satisfies a predetermined condition, the allocation unit 56 may allocate the patient that was assigned to the second user to the first user or one of the multiple second users based on the second information, which will be described later.

The ticket generation unit 57 generates tickets that manage the business operator's tasks for patients assigned to the business operator by the assignment unit 56. The ticket generation unit 57 includes a first ticket generation unit 57A that generates a first ticket that manages the first user's tasks for patients assigned to the first user, and a second ticket generation unit 57B that generates a second ticket that manages the second user's tasks for patients assigned to the second user. These tickets will be described in detail in a later paragraph.

The update unit 58 updates the status of the ticket based on information input to each terminal device used by each business operator and transmitted to the server device 50. The update unit 58 includes a first update unit 58A that updates the status of the first ticket based on input of first information to a terminal device used by a first user, and a second update unit 58B that updates the status of the second ticket based on input of second information to a terminal device used by a second user. The first update unit 58A invalidates the first ticket if the task of the first user is not executable. Furthermore, the second update unit 58B invalidates the second ticket if the task of the second user is not executable.

The invalidation management unit 59 manages in which task the first ticket or second ticket was invalidated. The invalidation management unit 59 can store in the ticket data 64 invalid ticket information such as in which task the multiple tickets generated for each business were invalidated, i.e., the ratio of tickets invalidated in each task to tickets that were valid and advanced to the next status, the reason for invalidation, and the date and time when the tickets were invalidated.

The storage unit 61 includes a ROM (Read Only Memory) and a RAM (Random Access Memory). The storage unit 61 stores a program 62 used by the server device 50, patient data 63 registered by the registration unit 55, ticket data 64 generated by the ticket generation unit 57 and whose status is updated by the update unit 58, business data 65 of each business belonging to the area, and the like. The ticket data 64 also includes information about invalidated tickets. In addition, it is preferable that the ticket data 64 is associated with the corresponding patient data 63. The business data 65 may include the address, size, type of service that can be provided, availability, and the like of each business. The communication IF 66 performs, for example, signal modulation/demodulation processing and frequency conversion processing so that the server device 50 can transmit and receive information to and from each terminal device. In addition to the above, the server device 50 may have various functions that have been publicly known in the past.

(Example of system operation)
Before describing an example of the operation of the support system 100 according to an embodiment of the present invention, first, an overview will be given of the differences between the conventional example and the support system 100. Fig. 4 is a schematic diagram showing an example of a method of providing services from each business to a patient in the conventional example and a method of providing services to a patient by the support system according to an embodiment of the present invention.

The left side of Figure 4 shows a conventional method M1 of providing services. In conventional method M1, support center 41, medical institutions 42A-42B, and care institutions 43A-43C each provide services to patient 46 using their own individual systems. In such cases, each business entity manages the data of multiple patients, and the data of one patient is distributed across each business entity. In addition, because each entity uses its own individual system, it is difficult to link data between the various businesses.

On the other hand, the right side of Figure 4 shows method M2 of service provision by support system 100. In method M2 by support system 100, support center 41, medical institutions 42A-42B, and care institutions 43A-43C each provide services to patient 46 using the same support system 100. Furthermore, even if the services provided by each provider are of different types, they are all managed using the concept of tickets. This allows data for a single patient to be managed centrally, making it easier for each provider to understand the patient's data and to work together with each other.

Below, an example of the operation of the support system 100 will be described in detail with reference to Figs. 5 to 9. Fig. 5 is a flowchart showing an example of processing by the support system according to one embodiment of the present invention. Note that the order of each process constituting each flowchart described in this specification may be random and may be executed in parallel as long as no contradictions or inconsistencies occur in the process content. Also, some of the processes constituting each flowchart described in this specification may be omitted.

In the following, an example will be described in which the first user is a support center that uses the first terminal device 10 and the second user is a care facility that uses the second terminal device 20, but the first user and the second user are not limited to this example.

In step S1, the control unit 51 of the server device 50 registers data of patients who belong to a specific region covered by the support system 100 in the storage unit 61 as patient data 63. Step S1 may be executed, for example, based on an operation by an administrator of the server device 50. Furthermore, prior to step S1, step S0 may be executed in which the control unit 11 of the first terminal device 10 accepts input of patient data by a staff member of the support center, and step S1 is executed in response to the server device 50 receiving the data.

In step S2, the control unit 51 refers to the patient data 63 registered in step S1 and assigns the patient to the first user. In this example, since the patient is registered for the first time and no support plan has been formulated, the support center is selected as the first user and the patient is assigned to the support center.

In step S3, the control unit 51 generates a first ticket that manages the tasks to be performed by the support center for the patient assigned in step S2. When the first ticket is generated, the first ticket becomes viewable on the first terminal device 10 in response to a request from the first terminal device 10. In addition, the patient data 63 of the patient may be viewable on the first terminal device.

In step S4, if an operation to invalidate the first ticket is performed on the first terminal device 10 (Yes in step S4), the process proceeds to 1 in FIG. 8.

It is preferable that the operation to invalidate the first ticket be allowed only to be performed by, for example, a support center staff member with a certain level of authority (e.g., a person who decides who will be in charge of an assigned patient and who approves the completion of the task for the first ticket. Hereinafter, a person with a certain level of authority will be referred to as a "manager"). The manager will invalidate the first ticket when, taking into consideration the overall situation, it is determined that it will be difficult to execute the subsequent task, such as when there is no one who can be in charge of the patient, when a visit to the patient's home is not possible due to the patient's circumstances or the person in charge's circumstances, or when a visit is made but a business that will provide the next service cannot be assigned to the patient.

In step S4, if no operation to invalidate the first ticket is performed on the first terminal device 10 (No in step S4), the process proceeds to step S5. In step S5, the control unit 11 of the first terminal device 10 accepts input of information (first information) related to the task managed by the first ticket. The input first information is transmitted to the server device 50.

In step S6, the control unit 51 updates the status of the first ticket based on the first information received from the first terminal device 10. The first task managed by the first ticket is, for example, determining the person in charge of the patient. When the information of the person in charge is input as the first information in step S5 and the information is received by the server device 50, the status of the first ticket is updated to a state in which the first task has been completed. This also makes it possible, for example, to input the first information regarding the next task in the first terminal device 10.

In step S7, the control unit 51 determines whether the status of the first ticket satisfies a predetermined condition. If the predetermined condition is not met (No in step S7), the process returns to step S4, and the series of processes from step S4 to step S7 are repeated. Here, the predetermined condition in step S7 is, for example, that the status of the first ticket is updated to a state in which all tasks managed by the first ticket are completed.

If the predetermined condition is met (Yes in step S7), in step S8, the control unit 51 assigns the patient to the second user based on the first information entered in the first ticket recorded in the ticket data 64. In this example, it is assumed that the first information contains information on the care facility to be selected as the second user. That is, in this example, it is assumed that the support center, which is the first user, specifies the care facility to be the second user.

In step S9, the control unit 51 generates a second ticket that manages the tasks to be performed by the care facility for the patient assigned in step S8. When the second ticket is generated, the second ticket becomes viewable on the second terminal device 20 in response to a request from the second terminal device 20. In addition, information related to the patient's first ticket and the patient data 63 of the patient may be viewable on the second terminal device 20.

In step S10, if an operation to invalidate the second ticket is performed on the second terminal device 20 (Yes in step S10), the process proceeds to 1 in FIG. 8.

It is preferable that the operation to invalidate the second ticket be performed, for example, only by the manager of the care facility. As explained in step S4, the manager invalidates the second ticket when he or she determines that it will be difficult to execute the subsequent task after considering the overall situation.

In step S10, if no operation to invalidate the second ticket is performed on the second terminal device 20 (Yes in step S10), the process proceeds to step S11. In step S11, the control unit 11 of the second terminal device 20 accepts input of information (second information) related to the task managed by the second ticket. The input second information is transmitted to the server device 50.

In step S12, the control unit 51 updates the status of the second ticket based on the first information received from the second terminal device 20. The first task managed by the second ticket is, for example, determining the person in charge of the patient. When the person in charge information is input as the second information in step S12 and the server device 50 receives the information, the status of the second ticket is updated to a state in which the first task has been completed. This also makes it possible, for example, to input second information regarding the next task in the second terminal device 20.

In step S13, the control unit 51 determines whether the status of the second ticket satisfies a predetermined condition. If the predetermined condition is not met (No in step S13), the process returns to step S10, and the series of processes from step S10 to step S13 are repeated. Here, the predetermined condition in step S13 is, for example, that the status of the second ticket is updated to a state in which all tasks managed by the second ticket are completed.

If the predetermined condition is met (Yes in step S13), in step S14, the control unit 51 assigns the patient to the next provider based on the second information entered in the second ticket recorded in the ticket data 64, the patient data 63, etc. After that, a series of processes related to ticket generation and ticket status update as described above are repeated, and the process ends when a predetermined termination condition is met. Note that the next provider selected in step S14 may be, for example, a support center or a care manager, or a medical institution. It may also be another care facility, or it may be the same care facility as the care facility selected in step S8.

The process related to the tickets described with reference to FIG. 5 will be described in more detail below with reference to FIG. 6. FIG. 6 is a schematic diagram showing an example of task management using tickets. When a patient is assigned to the pool 101 of the support center 41 in step S2 of FIG. 5, a first ticket 102 is generated. It is preferable that the patients assigned to the pool 101 can be viewed in a list form on the first terminal device 10, for example.

The tasks managed by the first ticket 102 preferably consist of at least three steps including a pre-step 110, an on-step 120, and a post-step 130. The pre-step 110 includes tasks to be performed before providing services to the patient. The pre-step 110 may include, for example, a task 111 for determining a person in the support center 41 who will be responsible for the patient, and a task 112 for determining a visit schedule for visiting the patient's home.

The on stage 120 is a stage for inputting information about the services provided to the patient. The on stage 120 may include, for example, a task 121 for inputting the patient's condition at the time of the visit, and a task 122 for inputting an evaluation of the patient's health condition and a support plan. The post stage 130 includes tasks that occur after the service is provided to the patient. The post stage 130 may include, for example, a task 131 for inputting the next business that will provide the service to the patient, and a task 132 for receiving approval from the manager of the support center 41 for the series of tasks performed by the person in charge. In the example of FIG. 8, in step S5, information about the above-mentioned tasks 111, 112, 121, 122, 131, and 132 is accepted as the first information.

When a patient is assigned to the pool 201 of the care facility 43 in step S8 of FIG. 5, a second ticket 202 is generated. It is preferable that the patients assigned to the pool 201 can be viewed in a list on, for example, the second terminal device 20 used by the care facility 43.

Similar to the first ticket 102, the tasks managed by the second ticket 202 preferably consist of at least three steps including a pre-step 210, an on-step 220, and a post-step 230. The pre-step 210 includes tasks to be performed before providing services to the patient. The pre-step 210 may include, for example, a task 211 to determine the person in charge of the patient within the care facility 43, and a task 212 to determine a visit schedule for visiting the patient's home.

The on stage 220 is a stage for inputting information about the services provided to the patient. The on stage 220 may include, for example, a task 221 for inputting the patient's condition at the time of the visit and a task 222 for inputting the services provided to the patient. The post stage 230 includes tasks that occur after the services are provided to the patient. The post stage 130 may include, for example, a task 231 for inputting a report about the patient and a task 232 for receiving approval from the manager of the care facility 43 for the series of tasks performed by the person in charge. In the example of FIG. 8, in step S11, information about the above-mentioned tasks 211, 212, 221, 222, 231, and 232 is accepted as second information. Also, when the next business operator is selected in step S14 of FIG. 8, a ticket for that business operator is linked after the second ticket 202.

Here, it is preferable that the tasks managed by the second ticket 202 can be changed for each business operator, for example. FIG. 7 is a schematic diagram showing an example of changing the tasks managed by the ticket. In the example of FIG. 7, the tasks 221 and 222 in the on-phase 220 of the second ticket 202 and the task 231 in the post-phase 230 are displayed as "Builder", and can be changed according to the type of service provided by the business operator and the work of the person in charge. For example, if it is necessary to provide the service repeatedly to the patient, the task 231 may be set to select the next business operator, and the care facility itself may be input as the business operator that will provide the next service. The ability to change the content of the tasks makes it easier to satisfy the needs of each business operator, and also makes it possible to flexibly respond to each business operator while using the same system.

Tasks 211 and 212 in the pre-stage 210 and task 232 in the post-stage 230 may also be changeable. Tasks in the first ticket 102 may also be changeable in the same way as the second ticket 202. It is preferable to adopt a no-code system so that tasks can be changed by the business operator themselves.

Returning to the explanation of the operation example using the flowchart, FIG. 8 is a flowchart showing an example of processing by the support system according to one embodiment of the present invention. Specifically, FIG. 8 shows an example of processing after an operation to invalidate the ticket is performed in step S4 or S10 of FIG. 5.

In step S21, the control unit 51 updates the ticket data 64 so that the status of the ticket for which the invalidation operation has been performed becomes invalid. In addition, in step S22, the control unit 51 stores invalid ticket information (e.g., the reason for invalidation, the date and time when the ticket became invalid, etc.) regarding the invalid ticket, which is the ticket that has been invalidated, in the ticket data 64.

If there is a request to output the invalid ticket information (Yes in step S23), in step S24, the control unit 51 outputs the invalid ticket information. In step S24, for example, in response to a request from each terminal device, the invalid ticket information is output (transmitted) to each terminal device. By making the invalid ticket information viewable on each terminal device, it becomes possible to provide the manager, etc. with auxiliary information for making the next decision. By providing the invalid ticket information, for example, the manager can more appropriately take additional measures such as selecting the next operator, and it becomes easier to understand problems occurring at each operator.

In step S25, the control unit 51 assigns the patient to the next business operator. After that, the series of processes related to ticket generation and ticket status update as described above are repeated, and the process ends when a predetermined end condition is met.

Figure 9 is a schematic diagram showing an example of invalid ticket information. In the example of Figure 9, invalid ticket information D101, D111, D112, D121, D122, D131, D132, D201, D211, D212, D221, D222, D231, and D232 are shown, which correspond to each task of each ticket and show the ratio of tickets that were invalidated in each task and tickets that were valid and proceeded to the next task. For example, invalid ticket information D111 is information corresponding to task 111, and shows the ratio of tickets that were invalidated in task 111 and tickets that were valid and proceeded to the next task. In the example of Figure 9, there is one ticket that was invalidated in task 111. It is preferable that by selecting one of the invalid tickets, the reason for the invalidation, the date and time when the ticket was invalidated, etc. can be viewed.

In nursing care and/or medical support, it is important to understand not how much service was provided to the patient, but how much service could not be provided. Analyzing invalid ticket information makes it easier to understand structural problems in the local community-based integrated care system and take appropriate measures.

Although one embodiment of the present invention has been described above in detail, the present invention is not limited to the above-mentioned embodiment, and suitable modifications and improvements are possible. The present invention is defined by the claims, and includes all modifications within the meaning and scope of the claims.

[Additional Notes]
As described above, the present specification discloses the following:
(1) A nursing care and/or medical support system including a plurality of terminal devices and a server device communicably connected to each of the plurality of terminal devices,
The plurality of terminal devices
a first terminal device used by a first user who belongs to a predetermined area;
a plurality of second terminal devices used by a plurality of second users each belonging to the predetermined region and each in a different business from that of the first users;
The server device includes:
A registration unit that registers patient data of patients who belong to the predetermined region;
a first allocation unit that allocates a patient indicated by the registered patient data to the first user;
a first ticket generating unit configured to generate a first ticket for managing a task of the first user for a patient assigned to the first user;
a first update unit that updates a status of the first ticket based on first information input by the first user to the first terminal device;
a second allocation unit that allocates a patient assigned to the first user to one of the plurality of second users based on the first information when a status of the first ticket satisfies a predetermined condition;
a second ticket generating unit configured to generate a second ticket for managing a task of the second user for a patient assigned to the second user;
a second update unit that updates a status of the second ticket based on second information input by the second user to the second terminal device;
A care and/or medical support system, including:

(2) The first user is a comprehensive supporter of nursing care and/or medical care in the specified area, and the second user includes a plurality of medical institutions and/or a plurality of nursing care institutions.
Or,
The first user is a medical institution, and the second users include a plurality of care institutions.
A care and/or medical support system as described in (1) above.

(3) when a status of the second ticket satisfies a predetermined condition, assigning the patient assigned to the second user to the first user or any one of the plurality of second users based on the second information;
A nursing care and/or medical support system according to (1) or (2) above.

(4) the task managed by the second ticket is configured with at least three steps including pre, on, and post;
The pre-input step includes a step of inputting, as the second information, a person in charge of the patient among the second users;
The step of turning on includes a step of inputting information regarding a service provided by the person in charge to the patient as the second information;
The post includes a step of inputting a report of the patient as the second information.
A care and/or medical support system according to any one of (1) to (3) above.

(5) Information to be input in the second ticket can be changed depending on the second user or the person in charge.
A care and/or medical support system as described in (4) above.

(6) the first update unit invalidates the first ticket when the task of the first user is not executable;
the second update unit invalidates the second ticket when a task of the second user is not executable;
the server device further includes an invalidation management unit that manages in which task the first ticket or the second ticket has been invalidated;
A care and/or medical support system according to any one of (1) to (5) above.

(7) A program executed on a computer device that includes a processor and is communicatively connectable to each of a plurality of terminal devices,
The plurality of terminal devices
a first terminal device used by a first user who belongs to a predetermined area;
a plurality of second terminal devices used by a plurality of second users each belonging to the predetermined region and each in a different business from that of the first users;
The program causes the processor to:
a registration step of registering patient data of patients who belong to the predetermined region;
a first allocation step of allocating a patient represented by the registered patient data to a first user;
a first ticket generating step of generating a first ticket for managing a task of the first user for a patient assigned to the first user;
a first updating step of updating a status of the first ticket based on receiving first information inputted to the first terminal device by the first user;
a second allocation step of allocating a patient assigned to the first user to any one of the plurality of second users based on the first information when a status of the first ticket satisfies a predetermined condition;
a second ticket generation step of generating a second ticket for managing a task of the second user for a patient assigned to the second user;
a second updating step of updating a status of the second ticket based on receiving second information inputted to the second terminal device by the second user;
A program to execute.

(8) A computer device capable of communicating with each of a plurality of terminal devices,
The plurality of terminal devices
a first terminal device used by a first user who belongs to a predetermined area;
a plurality of second terminal devices used by a plurality of second users each belonging to the predetermined region and each in a different business from that of the first users;
The computer device comprises:
A registration unit that registers patient data of patients who belong to the predetermined region;
a first allocation unit that allocates a patient represented by the registered patient data to a first user;
a first ticket generating unit configured to generate a first ticket for managing a task of the first user for a patient assigned to the first user;
a first update unit that updates a status of the first ticket based on receiving first information input to the first terminal device by the first user;
a second allocation unit that allocates a patient assigned to the first user to one of the plurality of second users based on the first information when a status of the first ticket satisfies a predetermined condition;
a second ticket generating unit configured to generate a second ticket for managing a task of the second user for a patient assigned to the second user;
a second update unit that updates a status of the second ticket based on receiving second information input to the second terminal device by the second user;
A computer device comprising:

(9) An information processing method executed in a computer device that has a processor and is communicatively connected to each of a plurality of terminal devices, comprising:
The plurality of terminal devices
a first terminal device used by a first user who belongs to a predetermined area;
a plurality of second terminal devices used by a plurality of second users each belonging to the predetermined region and each in a different business from that of the first users;
The processing method includes causing the processor to:
a registration step of registering patient data of patients who belong to the predetermined region;
a first allocation step of allocating a patient represented by the registered patient data to a first user;
a first ticket generating step of generating a first ticket for managing a task of the first user for a patient assigned to the first user;
a first updating step of updating a status of the first ticket based on receiving first information inputted to the first terminal device by the first user;
a second allocation step of allocating a patient assigned to the first user to any one of the plurality of second users based on the first information when a status of the first ticket satisfies a predetermined condition;
a second ticket generating step of generating a second ticket for managing a task of the second user for a patient assigned to the second user;
a second updating step of updating a status of the second ticket based on receiving second information inputted to the second terminal device by the second user;
An information processing method.
This information processing method supports the creation of a community-based comprehensive care system in which businesses within a specified area work together to provide care and/or medical care to patients, making it easier for businesses from different industries to work together and to satisfy the needs of each business.

10A-D, 10: First terminal device 20A-D, 20: Second terminal device 30A-D, 30: Third terminal device 40: Communication network 50A, 50B, 50: Server device 100A, 100B, 100: Support system 102: First ticket 202: Second ticket

Claims (8)

A nursing care and/or medical support system realized by a plurality of terminal devices and a server device communicably connected to each of the plurality of terminal devices,
The plurality of terminal devices
a first terminal device used by a first user who belongs to a predetermined area;
a plurality of second terminal devices used by a plurality of second users each belonging to the predetermined region and each in a different business from that of the first users;
The server device
A registration unit that registers patient data of patients who belong to the predetermined region;
a first allocation unit that allocates a patient indicated by the registered patient data to the first user;
a first ticket generating unit configured to generate a first ticket for managing a task of the first user for a patient assigned to the first user;
a first update unit that updates a status of the first ticket based on first information input by the first user to the first terminal device;
a second allocation unit that allocates a patient assigned to the first user to one of the plurality of second users based on the first information when a status of the first ticket satisfies a predetermined condition;
a second ticket generating unit configured to generate a second ticket for managing a task of the second user for a patient assigned to the second user;
a second update unit that updates a status of the second ticket based on second information input by the second user to the second terminal device;
Including,
The first user is a comprehensive supporter of care and/or medical care in the specified area, and the second user includes a plurality of medical institutions and/or a plurality of care institutions.
Or,
A care and/or medical support system , wherein the first user is a medical institution and the second users include a plurality of care institutions . When a status of the second ticket satisfies a predetermined condition, the patient assigned to the second user is assigned to the first user or one of the plurality of second users based on the second information.
The nursing and/or medical support system according to claim 1 . The task managed by the second ticket is configured with at least three steps including pre, on, and post;
The pre-input step includes a step of inputting, as the second information, a person in charge of the patient among the second users;
The step of turning on includes a step of inputting information regarding a service provided by the person in charge to the patient as the second information;
The post includes a step of inputting a report of the patient as the second information.
A care and/or medical support system according to claim 1 or 2. The second ticket is capable of changing information to be input in the on-line depending on the second user or the person in charge.
The nursing and/or medical support system according to claim 3 . the first update unit invalidates the first ticket when a task of the first user is not executable;
the second update unit invalidates the second ticket when a task of the second user is not executable;
the server device further includes an invalidation management unit that manages in which task the first ticket or the second ticket has been invalidated;
A care and/or medical support system according to claim 1 or 2. A program executed on a computer device having a processor and communicatively connectable to each of a plurality of terminal devices,
The plurality of terminal devices
a first terminal device used by a first user who belongs to a predetermined area;
a plurality of second terminal devices used by a plurality of second users each belonging to the predetermined region and each in a different business from that of the first users;
The program causes the processor to:
a registration step of registering patient data of patients who belong to the predetermined region;
a first allocation step of allocating a patient represented by the registered patient data to a first user;
a first ticket generating step of generating a first ticket for managing a task of the first user for a patient assigned to the first user;
a first updating step of updating a status of the first ticket based on receiving first information inputted to the first terminal device by the first user;
a second allocation step of allocating a patient assigned to the first user to any one of the plurality of second users based on the first information when a status of the first ticket satisfies a predetermined condition;
a second ticket generation step of generating a second ticket for managing a task of the second user for a patient assigned to the second user;
a second updating step of updating a status of the second ticket based on receiving second information inputted to the second terminal device by the second user;
Run the command ,
The first user is a comprehensive supporter of care and/or medical care in the specified area, and the second user includes a plurality of medical institutions and/or a plurality of care institutions.
Or,
The first user is a medical institution and the second users include a plurality of care institutions . A computer device capable of communicating with each of a plurality of terminal devices,
The plurality of terminal devices
a first terminal device used by a first user who belongs to a predetermined area;
a plurality of second terminal devices used by a plurality of second users each belonging to the predetermined region and each in a different business from that of the first users;
The computer device comprises:
A registration unit that registers patient data of patients who belong to the predetermined region;
a first allocation unit that allocates a patient represented by the registered patient data to a first user;
a first ticket generating unit configured to generate a first ticket for managing a task of the first user for a patient assigned to the first user;
a first update unit that updates a status of the first ticket based on receiving first information input to the first terminal device by the first user;
a second allocation unit that allocates a patient assigned to the first user to one of the plurality of second users based on the first information when a status of the first ticket satisfies a predetermined condition;
a second ticket generating unit configured to generate a second ticket for managing a task of the second user for a patient assigned to the second user;
a second update unit that updates a status of the second ticket based on receiving second information input to the second terminal device by the second user;
Including,
The first user is a comprehensive supporter of care and/or medical care in the specified area, and the second user includes a plurality of medical institutions and/or a plurality of care institutions.
Or,
The first user is a medical institution and the second users include a plurality of care institutions . An information processing method executed in a computer device having a processor and communicatively connectable to each of a plurality of terminal devices, comprising:
The plurality of terminal devices
a first terminal device used by a first user who belongs to a predetermined area;
a plurality of second terminal devices used by a plurality of second users each belonging to the predetermined region and each in a different business from that of the first users;
The processing method includes causing the processor to:
a registration step of registering patient data of patients who belong to the predetermined region;
a first allocation step of allocating a patient represented by the registered patient data to a first user;
a first ticket generating step of generating a first ticket for managing a task of the first user for a patient assigned to the first user;
a first updating step of updating a status of the first ticket based on receiving first information inputted to the first terminal device by the first user;
a second allocation step of allocating a patient assigned to the first user to any one of the plurality of second users based on the first information when a status of the first ticket satisfies a predetermined condition;
a second ticket generation step of generating a second ticket for managing a task of the second user for a patient assigned to the second user;
a second updating step of updating a status of the second ticket based on receiving second information inputted to the second terminal device by the second user;
Run the command ,
The first user is a comprehensive supporter of care and/or medical care in the specified area, and the second user includes a plurality of medical institutions and/or a plurality of care institutions.
Or,
An information processing method , wherein the first user is a medical institution and the second users include a plurality of care institutions .

Images