Side effect management system, side effect management server, and side effect management server program

Abstract

To enable presentation of a treatment for side effects.SOLUTION: A side effect management system comprises a patient terminal and a management server. The management server includes: an acquisition section that acquires, from the patient terminal, vital data on a patient and a subjective symptom caused by a side effect of an anticancer agent used by the patient; a processing section that acquires, on the basis of the vital data and the subjective symptom, a determination result of a treatment action to be taken by the patient with respect to the subjective symptom; and output section that outputs the treatment action to the patient terminal.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a side effect management system, a side effect management server, and a side effect management server program.

Background Art

[0002] There is a technology that proposes what side effects may occur based on the user's condition and the drugs used for treatment (see Patent Document 1).

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] However, from the patient's perspective, it is impossible to distinguish between the symptoms associated with cancer and the side effects of drug therapy, and they do not know the level of response, timing, or appropriate way to convey to medical staff, and are struggling to balance treatment and life. Also, for medical institutions, it is difficult to grasp the patient's situation outside the hospital, and side effect management may not be appropriately carried out in some cases.

[0005] The present invention has been made in view of such a background, and an object thereof is to provide a technology capable of presenting countermeasures against side effects.

Means for Solving the Problems

[0006] The main invention of the present invention for solving the above problems is a side effect management system including a patient terminal and a management server, wherein the management server includes: an acquisition unit that acquires from the patient terminal the patient's vital data and the subjective symptoms resulting from the side effects of the anticancer agent used by the patient; a processing unit that obtains a determination result of the countermeasure action that the patient should take for the subjective symptoms based on the vital data and the subjective symptoms; and an output unit that outputs the countermeasure action to the patient terminal.

[0007] Regarding other problems disclosed in the present application and their solution methods, they will be clarified by the embodiments of the invention and the drawings.

Effect of the Invention

[0008] According to the present invention, it is possible to present countermeasures against side effects.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Embodiments for Carrying Out the Invention

[0010] <Summary of the Invention> The content of the embodiment of the present invention will be listed and described. The present invention has, for example, the following configuration. [Item 1] A side effect management system including a patient terminal and a management server, wherein the management server comprises an acquisition unit that acquires from the patient terminal the patient's vital data and the subjective symptoms caused by the side effects of the anticancer drugs used by the patient, a processing unit that obtains a determination result of the coping behavior that the patient should take for the subjective symptoms based on the vital data and the subjective symptoms, and an output unit that outputs the coping behavior to the patient terminal. A side effect management system characterized by comprising the above. [Item 2] The system according to Item 1, wherein the acquisition unit acquires the subjective symptoms by causing the patient terminal to display the presence or absence of the subjective symptoms and the state of the subjective symptoms and allowing the patient to select them. A side effect management system characterized by the above. [Item 3] The system according to Item 2, wherein the processing unit comprises a classification unit that classifies the patient into a predetermined patient group based on the vital data and the subjective symptoms, and a determination unit that determines the coping behavior according to the classified patient group. A side effect management system characterized by comprising the above. [Item 4] The system according to Item 3, wherein the classification unit evaluates the state of the acquired subjective symptoms using a predetermined degree, and classifies the patient into a patient group by performing a predetermined weighting on the vital data, the evaluated degree, or a combination thereof. A side effect management system characterized by the above. [Item 5] The system according to Item 3 or Item 4, further comprising a patient behavior management unit that manages and associates the coping behavior for each patient group, wherein the determination unit determines the coping behavior for the patient belonging to the classified patient group by referring to the patient behavior management unit. A side effect management system characterized by [Item 6] The side effect management system according to Item 1, wherein the output unit outputs the coping behavior to a predetermined institution that manages the patient, A side effect management system characterized by [Item 7] A side effect management server configured to be communicable with a patient terminal, an acquisition unit that acquires the patient's vital data and subjective symptoms caused by side effects of an anticancer agent used by the patient from the patient terminal; and a processing unit that acquires a determination result of a coping behavior that the patient should take for the subjective symptoms based on the vital data and the subjective symptoms; an output unit that outputs an action based on the determination result to the patient terminal, A side effect management server characterized by comprising [Item 8] A side effect management server configured to be communicable with a patient terminal, an acquisition unit that acquires the patient's vital data and subjective symptoms caused by side effects of an anticancer agent used by the patient from the patient terminal, a processing unit that acquires a determination result of a coping behavior that the patient should take for the subjective symptoms based on the vital data and the subjective symptoms, and an output unit that outputs an action based on the determination result to the patient terminal, A side effect management server program characterized by functioning as [Item 9] A side effect management method using a patient terminal and a side effect management server, wherein the patient terminal acquires the patient's vital data and subjective symptoms caused by side effects of an anticancer agent used by the patient from the patient, and the management server acquires the vital data and the subjective symptoms from the patient terminal; performs a process of acquiring a determination result of a coping behavior that the patient should take for the subjective symptoms based on the vital data and the subjective symptoms; executing a step of outputting an action based on the determination result to the patient terminal; A side effect management system characterized by the above.

[0011] <Overview of the system> Hereinafter, a side effect management system according to an embodiment of the present invention will be described. The side effect management system of this embodiment determines the actions to be taken by the patient using a unique algorithm based on the subjective symptoms and vital data input by the patient, and based on the results, provides information to the patient and medical staff and shares information from this program. As a result, side effects caused by the anticancer drugs used by the patient can be detected early, and by supporting the patient's independent management of side effects and the doctor's early response to side effects, it is possible to continue drug therapy safely while suppressing the aggravation of side effects.

[0012] FIG. 1 is a diagram showing an overall configuration example of the side effect management system. The side effect management system of this embodiment includes a management server 2. The management server 2 is communicably connected to the patient terminal 1 and the medical institution terminal 3 via a communication network. The communication network is, for example, the Internet, and is constructed by a public telephone line network, a mobile phone line network, a wireless communication path, Ethernet (registered trademark), or the like.

[0013] The patient terminal 1 is a computer operated by the patient. The patient terminal 1 can be, for example, a smartphone, a tablet computer, a personal computer, or the like.

[0014] The medical institution terminal 3 is a computer operated by medical staff such as doctors and nurses. The medical institution terminal 3 can be, for example, a smartphone, a tablet computer, a personal computer, or the like.

[0015] The management server 2 may be a general-purpose computer such as a workstation or a personal computer, or may be logically realized by cloud computing.

[0016] <Management Server> FIG. 2 is a diagram showing an example of the hardware configuration of management server 2. Note that the illustrated configuration is an example, and it may have other configurations. Management server 2 includes a CPU 201, a memory 202, a storage device 203, a communication interface 204, an input device 205, and an output device 206. The storage device 203 stores various data and programs, such as a hard disk drive, a solid state drive, or a flash memory. The communication interface 204 is an interface for connecting to a communication network, such as an adapter for connecting to Ethernet (registered trademark), a modem for connecting to a public telephone network, a wireless communication device for performing wireless communication, a USB (Universal Serial Bus) connector or an RS232C connector for serial communication, etc. The input device 205 inputs data, such as a keyboard, a mouse, a touch panel, a button, a microphone, etc. The output device 206 outputs data, such as a display, a printer, a speaker, etc. Note that each functional unit of management server 2 described later is realized by the CPU 201 reading a program stored in the storage device 203 into the memory 202 and executing it, and each storage unit of management server 2 is realized as a part of the storage area provided by the memory 202 and the storage device 203.

[0017] FIG. 3 is a diagram showing an example of the software configuration of management server 2. Management server 2 includes a patient behavior management unit 231, a vital storage unit 232, a subjective symptom storage unit 233, an acquisition unit 211, a processing unit 212, and an output unit 213. The processing unit 212 includes a classification unit 221 and a determination unit 222.

[0018] The patient behavior management unit 231 manages by associating coping behaviors for each patient group. The patient behavior management unit 231 can be implemented as a storage unit that stores content (which may be text data or may be one or more types of data including still images, moving images, voices, etc.) for explaining the coping behaviors to the patient. It is also possible to store the content in an external database, and the patient behavior management unit 231 can be implemented as a functional unit that accesses the external database to obtain the content.

[0019] The patient groups can be sorted, for example, by side effects and / or vital data as described later. Here, side effects refer to harmful and unintended reactions to pharmaceuticals. Side effects can occur in any patient but do not necessarily occur, and there are individual differences, and symptoms can range from mild to severe. Specifically, side effects include, for example, fatigue, malaise, shortness of breath, fever, dry cough, anemia, interstitial pneumonia, etc., but are not limited to these, and can include common side effects described in the package insert of the anticancer agent in question. Side effects can include the subjective symptoms themselves, for example, fatigue, malaise, shortness of breath, fever, dry cough, etc. Side effects can include symptoms that do not match the subjective symptoms, for example, anemia, interstitial pneumonia, etc. Side effects that do not match the subjective symptoms can be identified by vital data or a combination of vital data and subjective symptoms. Vital data is information obtained due to a patient's life activities, and is also referred to as biological information, vital signs, etc. Specifically, vital data includes, for example, blood pressure, body temperature, pulse rate, respiration, weight, body fat, etc., but is not limited to these, and may include other information such as blood tests and urine tests. The degree of side effects can be, for example, three levels: mild, moderate, and severe, but is not limited to these, and may be two levels or four levels or more.

[0020] The coping actions are information indicating the actions that patients should take when side effects occur. The coping actions can be of three types: observation, self-care, and contact with a medical institution (phone recommendation), but are not limited to these, and may be one or two of these, or may include other actions. Self-care may include specific details of self-care. For example, it may include information on self-care published in a "Manual for Dealing with Severe Side Effects by Disease Type". In this embodiment, the coping actions are assumed to include the type of coping action (coping action type) and the description of the coping action (coping action details). The coping action types that can be set are "observation", "self-care", and "phone recommendation". When the coping action type is "observation", no coping action details are set, or "observe the situation", "live daily life while taking rest", etc. can be set. When the coping action type is "self-care", information indicating what kind of self-care to perform is set as the coping action. When the coping action type is "phone recommendation", no coping action details are set, or "contact the hospital", etc. can be set. The patient behavior management unit 231 can store the coping action type and the coping action details in association with the information identifying the patient group and the information indicating the side effects.

[0021] For side effects where the subjective symptoms or vital data are the side effects themselves, the patient behavior management unit 231 can store the coping actions with the degree of subjective symptoms as the patient group. FIG. 4 is a diagram for explaining the information managed by the patient behavior management unit 231 for side effects where the subjective symptoms are the side effects themselves. As shown in FIG. 4, for subjective symptoms such as fatigue and malaise, the degree of subjective symptoms is set as the patient group, and the coping action type and the coping action corresponding to the degree of subjective symptoms for each side effect are set.

[0022] For example, for fatigue and malaise, if the degree of subjective symptoms is "mild", the coping action of "observation" can be set, if it is "moderate", the coping action of "self-care" with "take sufficient rest" can be set, and if it is "severe", the coping action of "phone recommendation" can be set.

[0023] For example, regarding shortness of breath, if the degree of subjective symptoms is "mild", the coping action of "monitoring" can be set; if it is "moderate" or "severe", the coping action of "phone recommendation" can be set.

[0024] For example, regarding fever, if the degree of vital data (hereinafter referred to as the vital degree) is "mild", the coping action of "monitoring" can be set; if it is "moderate" or "severe", the coping action of "phone recommendation" can be set.

[0025] For example, regarding dry cough, if the degree of subjective symptoms is "mild", the coping action of "monitoring" can be set; if it is "moderate" or "severe", the coping action of "phone recommendation" can be set.

[0026] The patient behavior management unit 231 can store the coping actions for side effects where the subjective symptoms or vital data are not the side effects themselves, as the coping actions corresponding to patient groups classified based on one degree of subjective symptoms, a combination of multiple degrees of subjective symptoms, one vital degree, a combination of multiple vital degrees, or a combination of one or more degrees of subjective symptoms and one or more vital degrees. Figure 5 is a diagram for explaining the information managed by the patient behavior management unit 231 regarding side effects where the subjective symptoms are not the side effects themselves. In this case, the classification of patient groups is determined by performing predetermined weighting using a unique algorithm for one degree of subjective symptoms, a combination of multiple degrees of subjective symptoms, one vital degree, a combination of multiple vital degrees, or a combination of one or more degrees of subjective symptoms and one or more vital degrees.

[0027] As shown in FIG. 5, for example, regarding anemia, if the degree of the subjective symptom of "shortness of breath" is "severe" or "moderate", "telephone recommendation"; if "fatigue and lassitude" is "severe", "telephone recommendation"; if "palpitation" is "severe", "telephone recommendation"; if "shortness of breath" is "mild" and "fatigue and lassitude" is "moderate", "telephone recommendation"; if "shortness of breath" is "mild" and "palpitation" is "moderate", "telephone recommendation"; if "fatigue and lassitude" is "moderate" and "palpitation" is "moderate", "telephone recommendation"; for other combinations of the degree of subjective symptoms and / or the degree of vital signs, coping actions of "observation" can be set.

[0028] For example, regarding interstitial pneumonia, if the degree of the vital sign of "fever" is "severe" or "moderate", "telephone recommendation"; if "shortness of breath" is "severe" or "moderate", "telephone recommendation"; if "dry cough" is "severe" or "moderate", "telephone recommendation"; if "fever" is "mild" and "shortness of breath" is "mild", "telephone recommendation"; if "fever" is "mild" and "dry cough" is "mild", "telephone recommendation"; if "shortness of breath" is "mild" and "dry cough" is "mild", "telephone recommendation"; for other combinations of the degree of subjective symptoms and / or the degree of vital signs, coping actions of "observation" can be set.

[0029] The vital sign storage unit 232 stores the vital sign data acquired from the patient. The vital sign data can include, for example, blood pressure (systolic blood pressure and / or diastolic blood pressure), body temperature, and the like. The vital sign storage unit 232 can store the vital sign data in association with the patient and the date (or date and time).

[0030] The subjective symptom storage unit 233 stores the subjective symptoms acquired from the patient. The subjective symptoms can include fatigue, lassitude, shortness of breath, fever, dry cough, and the like. The subjective symptom storage unit 233 can also store the degree of the subjective symptoms (hereinafter referred to as the degree of subjective symptoms). The subjective symptom storage unit 233 can store the subjective symptoms and the degree of subjective symptoms in association with the patient and the date (or date and time). The degree of subjective symptoms can be, for example, three levels of mild, moderate, and severe, but is not limited thereto, and can be two levels or four levels or more.

[0031] The acquisition unit 211 acquires the patient's vital data and subjective symptoms. The acquisition unit 211 can receive from the patient terminal 1 the vital data and subjective symptoms input by the patient. The acquisition unit 211 may acquire vital data from a measuring device. The acquisition unit 211 can acquire subjective symptoms, for example, by causing the patient terminal 1 to display the presence or absence of subjective symptoms and the state of subjective symptoms and having the patient make a selection. The acquisition unit 211 can register the acquired vital data in the vital storage unit 232 and the subjective symptom storage unit 233 in association with the patient and the acquired date.

[0032] The acquisition unit 211 can also acquire the degree of subjective symptoms. The acquisition unit 211 can acquire subjective symptom information by causing the patient terminal 1 to display information regarding the presence or absence of subjective symptoms and the degree of subjective symptoms and having the patient make a selection.

[0033] The acquisition unit 211 can prepare options according to the degree for each subjective symptom.

[0034] For example, regarding the degree of fatigue and tiredness, the acquisition unit 211 provides the patient terminal 1 with "There is fatigue and tiredness, but it does not interfere with daily life" as a mild option, "There is fatigue and tiredness, which interferes with cooking, cleaning, selection, going out, etc." as a moderate option, and "There is fatigue and tiredness, which interferes with eating, changing clothes, using the toilet, taking a bath, etc." as a severe option, and allows the patient to select one of these.

[0035] For example, regarding the degree of shortness of breath, the acquisition unit 211 provides the patient terminal 1 with "There is a little difficulty breathing" as a mild option, "There is difficulty breathing even with a little movement, which interferes with cooking, cleaning, washing, going out, etc." as a moderate option, and "There is difficulty breathing even with a little movement or even when at rest, which interferes with eating, changing clothes, using the toilet, taking a bath, etc." as a severe option, and allows the patient to select one of these.

[0036] For example, the acquisition unit 211 provides the patient terminal 1 with options regarding the degree of dry cough, such as "coughing slightly" as a mild option, "coughing or having difficulty with cooking, cleaning, washing, going out, etc. due to symptoms" as a moderate option, and "coughing severely or having difficulty with eating, changing clothes, using the toilet, taking a bath, etc. due to symptoms" as a severe option, and allows the patient to select one of these options.

[0037] The processing unit 212 obtains a determination result of the coping actions that the patient should take for the subjective symptoms based on the vital data and the subjective symptoms. The processing unit 212 may include a classification unit 221 and a determination unit 222.

[0038] The classification unit 221 can classify patients into patient groups based on the vital data and the subjective symptoms. The classification unit 221 can evaluate the degree of the obtained subjective symptoms and classify the patients into patient groups by performing predetermined weighting on the vital data, the evaluated degree, or a combination thereof.

[0039] When the subjective symptom is the side effect itself, the classification unit 221 can determine the patient group according to the degree of the subjective symptom (mild, moderate, severe).

[0040] When the subjective symptom is not the side effect itself, the classification unit 221 can determine the patient group based on the subjective symptom and / or the vital data.

[0041] The classification unit 221 can classify vital data according to the degree (hereinafter referred to as the vital degree). The vital degree can be, for example, three levels of mild, moderate, and severe, but is not limited thereto, and may be two levels or four levels or more. For example, the classification unit 221 can classify the vital degree of "hypertension" as mild when the systolic blood pressure is 135 or more and less than 160, moderate when it is 160 or more and less than 180, and severe when it is 180 or more. For example, the classification unit 221 can classify the vital degree of "fever" as mild when the body temperature is 37 to 37.4 degrees, moderate when it is 37.5 to 37.9 degrees, and severe when it is 38.0 degrees or more. The classification unit 212 can also refer to the vital information storage unit 232 and classify the vital degree of "hypertension" as mild, moderate, or severe when the systolic blood pressure of the above classification continues for a predetermined period (for example, 2 days, 5 days, etc.) or more. When these classifications cannot be made, the classification unit 212 can prevent the use of the vital information for information processing.

[0042] The determination unit 222 determines a coping action according to the classified patient group. The determination unit 222 can refer to the patient behavior management unit 231 to determine a coping action for a patient belonging to the classified patient group. When the subjective symptom is the side effect itself, the determination unit 222 can determine the coping action by reading out the coping action corresponding to the subjective symptom and the degree of subjective symptom from the patient behavior management unit 231.

[0043] The output unit 213 outputs the coping action to the patient terminal 1. The output unit 213 can output the coping action to a predetermined institution that manages patients. The output unit 213 can transmit information for identifying the patient, subjective symptoms, the degree of subjective symptom, vital data, and the determination result of the coping action to the medical institution terminal 3. The output unit 214 may transmit these when the degree of side effect and / or the vital degree is equal to or higher than a predetermined threshold value (which may be a different threshold value depending on the side effect).

[0044] <Operation> FIG. 6 is a diagram for explaining the operation of the management server 2.

[0045] The management server 2 acquires vital information, subjective symptom information, and the degree of subjective symptoms from the patient terminal 1 (S301), and classifies the vital information according to the degree of vitality (S302).

[0046] The management server 2 classifies patients into patient groups based on the vital information, subjective symptom information, degree of vitality, and degree of subjective symptoms (S303).

[0047] The management server 2 acquires the side effects and the coping actions corresponding to the patient group from the patient behavior management unit 231 (S304), and transmits the acquired coping actions to the patient terminal 1 (S305).

[0048] The management server 2 can transmit the information for identifying the patient, side effects, coping actions, vital data, subjective symptoms, and the degree of subjective symptoms to the medical institution terminal 3 (S306). Note that the management server 2 may transmit only this information regarding a specific patient group to the medical institution terminal 3.

[0049] As described above, according to the side effect management system of the present embodiment, side effects can be estimated based on the patient's vital data and subjective symptoms, and the actions that the patient should take can be proposed accordingly.

[0050] Although the present embodiment has been described above, the above embodiment is for facilitating the understanding of the present invention and is not for limiting and interpreting the present invention. The present invention can be changed and improved without departing from its gist, and equivalents of the present invention are also included therein.

Explanation of Reference Numerals

[0051] 1 Patient terminal 2 Management server 3 Medical institution terminal

Claims

1. A side effect management system including a patient terminal and a management server, wherein the management server has an acquisition unit that acquires the patient's vital data and the subjective symptoms caused by the side effects of the anticancer drugs used by the patient from the patient terminal, a processing unit that obtains a determination result of the coping action to be taken by the patient for the subjective symptoms based on the vital data and the subjective symptoms, and an output unit that outputs the coping action to the patient terminal, and is characterized by comprising the above.

2. The system according to claim 1, wherein the acquisition unit acquires the subjective symptoms by causing the patient terminal to display the presence or absence and the state of the subjective symptoms and allowing the patient to select them. and is characterized by comprising the above.

3. The system according to claim 2, wherein the processing unit has a classification unit that classifies the patient into a predetermined patient group based on the vital data and the subjective symptoms, and a determination unit that determines the coping action according to the classified patient group, and is characterized by comprising the above.

4. The system according to claim 3, wherein the classification unit evaluates the state of the acquired subjective symptoms using a predetermined degree, and classifies the patient into a patient group by performing a predetermined weighting on the vital data, the evaluated degree, or a combination thereof. and is characterized by comprising the above.

5. The system according to claim 3 or claim 4, further comprising a patient behavior management unit that manages and associates the coping actions for each patient group, wherein the determination unit determines the coping action for the patient belonging to the classified patient group by referring to the patient behavior management unit. and is characterized by comprising the above.

6. The side effect management system according to claim 1, wherein the output unit outputs the coping action to a predetermined institution that manages the patient. and is characterized by comprising the above.

7. A side effect management server configured to be communicable with a patient terminal, having an acquisition unit that acquires the patient's vital data and the subjective symptoms caused by the side effects of the anticancer drugs used by the patient from the patient terminal, and a processing unit that obtains a determination result of the coping action to be taken by the patient for the subjective symptoms based on the vital data and the subjective symptoms, and an output unit that outputs an action based on the determination result to the patient terminal, and is characterized by comprising the above.

8. A side effect management server configured to be communicable with a patient terminal, an acquisition unit that acquires from the patient terminal the patient's vital data and subjective symptoms resulting from side effects of an anticancer agent used by the patient, a processing unit that obtains a determination result of a coping action to be taken by the patient with respect to the subjective symptoms based on the vital data and the subjective symptoms, and an output unit that outputs an action based on the determination result to the patient terminal, wherein the side effect management server program is caused to function as such.

9. A side effect management method using a patient terminal and a side effect management server, wherein the patient terminal acquires from the patient the patient's vital data and subjective symptoms resulting from side effects of an anticancer agent used by the patient, and the management server performs a step of acquiring the vital data and the subjective symptoms from the patient terminal, performs a process of obtaining a determination result of a coping action to be taken by the patient with respect to the subjective symptoms based on the vital data and the subjective symptoms, and performs a step of outputting an action based on the determination result to the patient terminal, characterizing a side effect management system.

Images