Apparatus for managing patient for preventing disease worsening and method for controlling thereof

Abstract

A patient management device for preventing disease exacerbation and a control method thereof are provided. The device includes a memory storing at least one process for managing a patient to prevent disease exacerbation and a processor that performs operations based on said process. The processor determines whether drug prescription and surgery are necessary based on the patient's condition, performs pre-management for different purposes depending on said necessity, and when said pre-management is completed, determines whether said purpose has been achieved, and determines whether to re-perform said pre-management or proceed with drug prescription and surgery depending on said achievement.

Description

Technology Field

[0001] The present disclosure relates to a patient management device for preventing disease exacerbation and a method for controlling the same. Background Technology

[0002] The process of a doctor prescribing medication is a crucial medical act involving diagnosing a patient's condition and selecting the most suitable drug. Accurate and appropriate prescribing accelerates a patient's recovery, while incorrect prescribing can lead to side effects or serious complications.

[0003] However, conventionally, since medication is prescribed based on the diagnosis of the patient regardless of treatment compliance, there is a problem in that medication is prescribed even to patients who can be managed through lifestyle management. Prior art literature

[0004] Korean Patent Publication No. 10-1522333, May 15, 2015 The problem to be solved

[0005] The embodiments disclosed in this disclosure are intended to provide a patient management device and a control method for preventing disease exacerbation.

[0006] The problems that this disclosure aims to solve are not limited to those mentioned above, and other unmentioned problems will be clearly understood by a person skilled in the art from the description below. means of solving the problem

[0007] A patient management device for preventing disease exacerbation according to one aspect of the present disclosure for achieving the aforementioned technical problem comprises a memory storing at least one process for managing a patient to prevent disease exacerbation and a processor that performs operations based on said process, wherein the processor determines whether drug prescription and surgery are necessary based on the condition of said patient, performs pre-management for different purposes according to said necessity, and when said pre-management is completed, determines whether said purpose is achieved, and determines whether to re-perform said pre-management or to proceed with drug prescription and surgery according to said achievement.

[0008] In addition, the processor may set the purpose to make the patient's condition capable of receiving the drug prescription and surgery when the drug prescription and surgery are required, and to set the purpose to check whether the patient's condition improves without receiving the drug prescription and surgery when the drug prescription and surgery are not required.

[0009] In addition, the processor may further be configured for the purpose of verifying the expected response of the patient's body during the drug prescription and surgery when the drug prescription and surgery are required.

[0010] In addition, the processor may decide to proceed with the drug prescription and surgery when the objective is achieved in cases where the drug prescription and surgery are required, and decide to re-conduct the preliminary management when the objective is not achieved in cases where the drug prescription and surgery are required, and decide not to proceed with the drug prescription and surgery when the objective is achieved in cases where the drug prescription and surgery are not required, and decide to re-conduct the preliminary management when the objective is not achieved in cases where the drug prescription and surgery are not required.

[0011] In addition, the above-mentioned prior management includes management of at least one of exercise, diet, sleep, and lifestyle habits, and the processor may modify the management method based on performance data and result data provided from the patient's terminal as the prior management proceeds according to the management method, which sets a management method for the at least one according to the patient's condition.

[0012] In addition, if the processor decides to re-conduct the prior management, it may reset the management method for the re-conducted prior management based on the execution data and result data of the previously conducted prior management.

[0013] In addition, the above-mentioned pre-management may be set to different periods for cases where the above-mentioned drug prescription and surgery are required and cases where the above-mentioned drug prescription and surgery are not required, respectively.

[0014] In addition, the processor can determine whether to proceed with post-care for the patient based on the performance data and result data regarding the pre-care.

[0015] In addition, a patient management method for preventing disease exacerbation according to another aspect of the present disclosure for achieving the technical problem described above is

[0016] Additionally, if the above drug prescription and surgery are required, the objective may be set to make the patient's condition capable of receiving the above drug prescription and surgery, and if the above drug prescription and surgery are not required, the objective may be set to verify whether the patient's condition improves without receiving the above drug prescription and surgery.

[0017] In addition, if the above drug prescription and surgery are necessary, the above objective may be further set to confirm the expected response of the patient's body during the above drug prescription and surgery.

[0018] In addition, the step of determining whether to re-conduct the aforementioned preliminary management or proceed with drug prescription and surgery may be determined by deciding to proceed with the drug prescription and surgery when the objective is achieved in cases where the drug prescription and surgery are necessary, and deciding to re-conduct the aforementioned preliminary management when the objective is not achieved in cases where the drug prescription and surgery are necessary, and deciding not to proceed with the drug prescription and surgery when the objective is achieved in cases where the drug prescription and surgery are not necessary, and deciding to re-conduct the aforementioned preliminary management when the objective is not achieved in cases where the drug prescription and surgery are not necessary.

[0019] Additionally, the above-mentioned preliminary management includes management of at least one of exercise, diet, sleep, and lifestyle habits, and the step of conducting the above-mentioned preliminary management may include the step of setting a management method for the at least one according to the condition of the patient and the step of modifying the management method based on performance data and result data provided from the patient's terminal as the above-mentioned preliminary management is conducted according to the management method.

[0020] Additionally, if it is decided to re-conduct the aforementioned preliminary management, the method may further include a step of resetting the management method for the re-conducted preliminary management based on the performance data and result data of the previously conducted preliminary management.

[0021] In addition, the above-mentioned pre-management may be set to different periods for cases where the above-mentioned drug prescription and surgery are required and cases where the above-mentioned drug prescription and surgery are not required, respectively.

[0022] In addition, the above method may further include a step of determining whether to proceed with post-care for the patient based on performance data and result data regarding the above-mentioned pre-care.

[0023] In addition, a computer program stored on a computer-readable recording medium for executing a method for implementing the present disclosure may be further provided.

[0024] In addition, a computer-readable recording medium for recording a computer program for executing a method for implementing the present disclosure may be further provided. Effects of the invention

[0025] According to the aforementioned means for solving the problem of the present disclosure, by conducting pre-treatment management of the patient before drug prescription / surgery, unnecessary medical procedures can be reduced and treatment compliance can be increased.

[0026] The effects of the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by a person skilled in the art from the description below. Brief explanation of the drawing

[0027] FIG. 1 is a block diagram of a patient management device for preventing disease exacerbation according to the present disclosure. FIG. 2 is a flowchart of a patient management method for preventing disease exacerbation according to the present disclosure. FIG. 3 is a diagram illustrating a process for cases requiring drug prescription and surgery according to one embodiment of the present disclosure. FIG. 4 is a diagram illustrating a process in which drug prescription and surgery are not required according to one embodiment of the present disclosure. Specific details for implementing the invention

[0028] Throughout this disclosure, the same reference numerals denote the same components. This disclosure does not describe all elements of the embodiments, and general content in the art to which this disclosure pertains or content that overlaps between embodiments is omitted. The terms “part, module, component, block” as used in the specification may be implemented in software or hardware, and depending on the embodiments, a plurality of “parts, modules, components, blocks” may be implemented as a single component, or a single “part, module, component, block” may include a plurality of components. Throughout the specification, when a part is described as being “connected” to another part, this includes not only direct connection but also indirect connection, and indirect connection includes connection via a wireless communication network.

[0029] Furthermore, when it is stated that a part "includes" a certain component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components.

[0030] Throughout the specification, when it is stated that a component is located "on" another component, this includes not only cases where a component is in contact with another component, but also cases where another component exists between the two components.

[0031] The terms first, second, etc. are used to distinguish one component from another, and the components are not limited by the aforementioned terms.

[0032] Singular expressions include plural expressions unless there is an obvious exception in the context.

[0033] In each step, identification codes are used for convenience of explanation and do not describe the order of the steps; the steps may be performed differently from the specified order unless a specific order is clearly indicated in the context.

[0034] The operating principles and embodiments of the present disclosure will be described below with reference to the attached drawings.

[0035] Prior to the explanation, the meanings of the terms used in this specification are briefly explained. However, since the explanation of terms is intended to aid in understanding this specification, it should be noted that unless explicitly stated as a limiting factor, they are not used to limit the technical scope of this disclosure.

[0036] In this specification, the term "device" includes all various devices capable of performing computational processing and providing results to a user. For example, a device may include a computer, a server device, and a portable terminal, or be any one of these forms.

[0037] Here, the computer may include, for example, a notebook, desktop, laptop, tablet PC, slate PC, etc. equipped with a web browser.

[0038] The above server device is a server that processes information by communicating with an external device, and may include an application server, a computing server, a database server, a file server, a game server, a mail server, a proxy server, and a web server.

[0039] The above portable terminal may include, for example, all types of handheld-based wireless communication devices such as PCS (Personal Communication System), GSM (Global System for Mobile communications), PDC (Personal Digital Cellular), PHS (Personal Handyphone System), PDA (Personal Digital Assistant), IMT (International Mobile Telecommunication)-2000, CDMA (Code Division Multiple Access)-2000, W-CDMA (W-Code Division Multiple Access), WiBro (Wireless Broadband Internet) terminals, smartphones, etc., as well as wearable devices such as watches, rings, bracelets, anklets, necklaces, glasses, contact lenses, or head-mounted devices (HMDs).

[0040] FIG. 1 is a block diagram of a patient management device for preventing disease exacerbation according to the present disclosure.

[0041] Referring to FIG. 1, the patient management device (10) (hereinafter, patient management device) for preventing disease exacerbation of the present disclosure may be a server device that provides patient management services.

[0042] The patient management device (10) can provide a patient management service that determines whether to prescribe medication or surgery based on the prognosis by conducting preliminary management of diet, exercise, sleep, lifestyle habits, etc., before deciding on medication prescription or surgery for a patient with a disease.

[0043] Here, "disease" may refer to conditions such as diabetes, hypertension, hypotension, and anemia, but is not limited thereto and may include all types of diseases.

[0044] The patient terminal (20) may refer to a terminal device of a user who uses the services provided by the patient management device (10). The patient may use the services in the form of an online web or app by installing a service application (program) on their terminal device.

[0045] The patient terminal (20) may be an information processing means such as a computer, and may refer to any device including a processor such as a control unit, a shooting means such as a camera, an input / output means including a touch screen, and a communication function. That is, any device such as a smartphone, tablet, PDA, laptop, desktop, etc., can be applied.

[0046] Referring to FIG. 1, the patient management device (10) may include a communication unit (11), a memory (12), and a processor (13). The processor (13) may include a pre-management module (131), a surgery / prescription module (132), and a post-management module (133).

[0047] However, in some embodiments, the patient management device (10) and the processor (130) may include fewer or more components than the components shown in FIG. 1.

[0048] The communication unit (11) may include one or more modules that enable wireless or wired communication between the patient management device (10) and the patient terminal (20), between the patient management device (10) and an external device (not shown), between the patient management device (10) and an external server (not shown), and between the patient management device (10) and a communication network. For example, it may include at least one of a wired communication module, a wireless communication module, a short-range communication module, and a location information module.

[0049] Various types of communication networks may be used, for example, wireless communication methods such as WLAN (Wireless LAN), Wi-Fi, Wibro, Wimax, and HSDPA (High Speed ​​Downlink Packet Access), or wired communication methods such as Ethernet, xDSL (ADSL, VDSL), HFC (Hybrid Fiber Coax), FTTC (Fiber to The Curb), and FTTH (Fiber to The Home).

[0050] Meanwhile, the communication network is not limited to the communication method presented above, and may include all forms of communication methods that are widely known or will be developed in the future, in addition to the communication method described above.

[0051] The wired communication module may include various wired communication modules such as a Local Area Network (LAN) module, a Wide Area Network (WAN) module, or a Value Added Network (VAN) module, as well as various cable communication modules such as USB (Universal Serial Bus), HDMI (High Definition Multimedia Interface), DVI (Digital Visual Interface), RS-232 (recommended standard 232), power line communication, or POTS (plain old telephone service).

[0052] In addition to Wi-Fi modules and WiBro (Wireless broadband) modules, the wireless communication module may include wireless communication modules that support various wireless communication methods such as GSM (global System for Mobile Communication), CDMA (Code Division Multiple Access), WCDMA (Wideband Code Division Multiple Access), UMTS (universal mobile telecommunications system), TDMA (Time Division Multiple Access), LTE (Long Term Evolution), 4G, 5G, and 6G.

[0053] A short-range communication module is for short-range communication and can support short-range communication by using at least one of Bluetooth™, RFID (Radio Frequency Identification), Infrared Data Association (IrDA), UWB (Ultra Wideband), ZigBee, NFC (Near Field Communication), Wi-Fi (Wireless-Fidelity), Wi-Fi Direct, and Wireless USB (Wireless Universal Serial Bus) technologies.

[0054] Memory (12) may store at least one process for managing the patient to prevent disease exacerbation.

[0055] The memory (12) can store data supporting various functions of the patient management device (10) and programs for the operation of the processor (13), and can store input / output data (e.g., music files, still images, videos, etc.), and can store a number of application programs (or applications) running on the patient management device (10), data for the operation of the patient management device (10), and commands. At least some of these application programs can be downloaded from an external server via wireless communication.

[0056] The memory (12) may include at least one type of storage medium among flash memory type, hard disk type, SSD type (Solid State Disk type), SSD type (Silicon Disk Drive type), multimedia card micro type, card type memory (e.g., SD or XD memory, etc.), RAM (random access memory; RAM), SRAM (static random access memory), ROM (read-only memory; ROM), EEPROM (electrically erasable programmable read-only memory), PROM (programmable read-only memory), magnetic memory, magnetic disk, and optical disk. Additionally, the memory (12) may be a database that is separate from the patient management device (10) but connected via wired or wireless connection. Alternatively, the database may be included in the patient management device (10) as an individual component with the memory (12).

[0057] The processor (13) may perform the aforementioned operation using data stored in the memory, which stores data for an algorithm or a program that reproduces the algorithm for controlling the operation of components within the patient management device (10). At this time, the memory (12) and the processor (13) may each be implemented as separate chips. Alternatively, the memory (12) and the processor (13) may be implemented as a single chip.

[0058] In addition, the processor (13) can control one or a combination of the components described above in order to implement various embodiments according to the present disclosure described in FIGS. 2 to 4 below on the patient management device (10).

[0059] The pre-management module (131) of the processor (13) can analyze and classify the patient's current condition and perform pre-management using a management method determined according to the current condition.

[0060] The surgery / prescription module (132) of the processor (13) can re-analyze the patient's condition after pre-management and decide whether or not to proceed with surgery / prescription.

[0061] The post-management module (133) of the processor (13) can determine rehabilitation management (post-management) based on the performance status of the pre-management stage.

[0062] Below, with reference to FIGS. 2 to 5, a method for managing the career of medical professionals will be explained in detail.

[0063] FIG. 2 is a flowchart of a patient management method for preventing disease exacerbation according to the present disclosure.

[0064] FIG. 3 is a diagram illustrating a process for cases requiring drug prescription and surgery according to one embodiment of the present disclosure.

[0065] FIG. 4 is a diagram illustrating a process in which drug prescription and surgery are not required according to one embodiment of the present disclosure.

[0066] For convenience of explanation, each step is described below as being performed by the processor (13), but each step can be understood as being performed by any one of the pre-management module (131), surgery / prescription module (132), post-management module (133) and modules not shown in FIG. 1 included in the processor (13).

[0067] Referring to FIG. 3, the processor (13) of the patient management device (10) can determine whether drug prescription and surgery are necessary based on the patient's condition (S210).

[0068] Here, the patient's condition refers to a condition related to the patient's health and can be analyzed through at least one or a combination of two of biometric data, blood test data, urine and body fluid test data, imaging test data, heart and lung-related test data, sleep data, exercise data, and dietary data.

[0069] Biometric data may include blood pressure, heart rate, body temperature, and oxygen saturation.

[0070] Blood test data may include blood glucose, cholesterol levels, CBC (Complete Blood Count), liver / kidney function tests, CRP, and ESR.

[0071] Imaging examination data may include X-ray, CT (Computed Tomography), MRI (Magnetic Resonance Imaging), ultrasound, and PET (Positron Emission Tomography).

[0072] The processor (13) can determine whether medication prescription and surgery are currently necessary for the patient based on the analyzed patient's current condition. That is, even if the patient has a disease, there may be room for improvement in their condition without medication prescription; therefore, instead of unconditionally deciding on medication prescription after diagnosis, it is divided into two cases (cases where medication prescription and surgery are necessary and cases where they are not) depending on the patient's current condition.

[0073] Next, the processor (13) of the patient management device (10) can perform pre-management for different purposes depending on the above necessity (S220).

[0074] In other words, pre-treatment management can be conducted whether medication prescriptions or surgery are required or not, but different objectives can be set and carried out for each case.

[0075] In cases where drug prescription and surgery are required, the processor (13) can be set to the purpose of making the patient's condition suitable for drug prescription and surgery.

[0076] According to the embodiment, when drug prescription and surgery are required, the processor (13) may be further configured for the purpose of checking the expected response of the patient's body during drug prescription and surgery.

[0077] In cases where drug prescription and surgery are not required, the processor (13) can be set for the purpose of checking whether the patient's condition improves without drug prescription and surgery.

[0078] Here, pre-management may include management of at least one of exercise, diet, sleep, and lifestyle habits, and a method of management of at least one of exercise, diet, sleep, and lifestyle habits may be established depending on the patient's condition.

[0079] Exercise-related management methods may include, but are not limited to, exercise time, exercise volume, and exercise routines.

[0080] Dietary management methods may include, but are not limited to, meal times, meal portions, and diet.

[0081] Sleep-related management methods may include, but are not limited to, sleep duration and amount of sleep.

[0082] Lifestyle management methods may include, but are not limited to, the frequency of smoking, the frequency of drinking, the frequency of caffeine intake, and the time spent using electronic devices.

[0083] Specifically, management methods can be set differently depending on the patient's condition (e.g., blood pressure levels). For example, if blood pressure is high, dietary management methods can be set with a low-salt diet to lower blood pressure, and exercise management methods can be set that combine aerobic exercise and strength training.

[0084] In addition, the pre-treatment period can be set to different durations for cases requiring medication and surgery and cases not requiring medication and surgery. For example, it can be set to 2 weeks when medication and surgery are required, and to 1 week when medication and surgery are not required.

[0085] Pre-management can be performed according to the management method during the period set in this way. The patient can check the management method through the service application and perform requests for each item of the management method. Accordingly, the processor (13) can receive performance data and result data regarding the pre-management from the patient terminal (20).

[0086] Here, performance data may be data regarding whether each item has been performed. Specifically, performance data may include whether the criteria required by each item (time, quantity, frequency, etc.) have been met. For example, if a patient adhered to the exercise time for the first exercise suggested in the exercise management method but did not adhere to the exercise quantity and routine, the performance data may be generated as 'Exercise time met, Exercise quantity not met, Exercise routine not met'.

[0087] Result data may be data regarding the patient's condition changing as pre-management is performed.

[0088] The processor (13) can modify the management method based on the execution data and result data provided from the patient terminal (20).

[0089] Specifically, the processor (13) can modify the management method based on performance data and result data at pre-set intervals during a set period. For example, if the set period is one week, the management method can be modified based on performance data and result data for that day at one-day intervals.

[0090] The processor (13) can modify the management method according to the relationship between the execution data and the result data.

[0091] According to an embodiment, if the patient's condition worsens even though the patient has met all criteria (time, amount, frequency, etc.) for the first exercise proposed in the exercise management method, the criteria for all items of the first exercise may be modified.

[0092] According to the embodiment, if the patient's condition improves even though the patient did not meet the criteria for time among all criteria (time, amount, diet, etc.) for the first meal proposed in the dietary management method, the criteria for the time of the first meal may be modified.

[0093] According to an embodiment, if the patient's condition improves even though the patient has not met all criteria (time, amount, frequency, etc.) for the first exercise proposed in the exercise management method, the processor (13) may provide a survey asking for specific details of the date to the patient terminal (20). The processor (13) may analyze the response to the survey to modify all criteria (time, amount, frequency, etc.) for the first exercise, or delete the items for the first exercise and create a new second exercise to set criteria for each item.

[0094] Next, the processor (13) of the patient management device (10) can determine whether the objective has been achieved when the preliminary management is completed (S230).

[0095] The processor (13) can measure and analyze the patient's condition again once the preliminary management is complete.

[0096] In cases where drug prescription and surgery are required, the processor (13) can determine that the purpose has been achieved if it is confirmed that the patient's current condition, which has been analyzed again, is in a state where drug prescription and surgery can be performed.

[0097] In cases where drug prescription and surgery are required, the processor (13) can determine that the purpose has been achieved if the expected response of the patient's body during drug prescription and surgery is confirmed based on the patient's current condition analyzed again.

[0098] In cases where drug prescription and surgery are not required, the processor (13) can determine that the purpose has been achieved if it is confirmed that the patient's current condition, which was analyzed again, has improved without drug prescription and surgery.

[0099] Next, the processor (13) of the patient management device (10) can determine whether to re-manage the pre-treatment or proceed with drug prescription and surgery depending on whether the objective is achieved (S240).

[0100] If the objective is achieved when drug prescription and surgery are necessary, the processor (13) may decide to proceed with drug prescription and surgery for the patient.

[0101] If the objective is not achieved in cases where drug prescription and surgery are required, the processor (13) may decide to proceed with the preliminary management again.

[0102] If the objective is achieved when drug prescription and surgery are not necessary, the processor (13) may decide not to proceed with drug prescription and surgery for the patient.

[0103] If the objective is not achieved in cases where drug prescription and surgery are not required, the processor (13) may decide to proceed with the pre-treatment again.

[0104] Referring to FIG. 3, the processor (13) can perform pre-management according to a management method set according to the patient's condition when drug prescription and surgery are required (S31).

[0105] Next, the processor (13) can determine whether a pre-management period (e.g., 2 weeks) has been exceeded at each preset interval (e.g., 1 day) (S32).

[0106] If the pre-management period (e.g., 2 weeks) has not been exceeded, the processor (13) can perform monitoring based on the performance data and result data of the corresponding date (S33). That is, through monitoring, the management method can be modified at pre-set intervals (e.g., 1 day). This allows the patient to receive effective management with a management method that changes according to their condition every day.

[0107] If the pre-management period (e.g., 2 weeks) is exceeded, the processor (13) can analyze the result of the pre-management (the condition of the patient who completed the pre-management) (S34).

[0108] Next, the processor (13) can determine whether the objective has been achieved through the results of the prior management (S35).

[0109] If the objective is not achieved, the processor (13) may decide to re-manage the pre-management (S36).

[0110] If the objective is achieved, the processor (13) may decide not to proceed with drug prescription and surgery (S37). At this time, the processor (13) may set the direction for drug prescription and surgery based on the confirmed expected response.

[0111] Referring to FIG. 4, the processor (13) can perform pre-management according to a management method set according to the patient's condition when drug prescription and surgery are not required (S41).

[0112] Next, the processor (13) can determine whether a pre-management period (e.g., 1 week) has been exceeded at each preset interval (e.g., 1 day) (S42).

[0113] If the pre-management period (e.g., 1 week) has not been exceeded, the processor (13) can perform monitoring based on the performance data and result data of that date (S43). That is, through monitoring, the management method can be modified at pre-set intervals (e.g., 1 day). This allows the patient to receive effective management with a management method that changes according to their condition every day.

[0114] If the pre-management period (e.g., 1 week) is exceeded, the processor (13) can analyze the result of the pre-management (the condition of the patient who completed the pre-management) (S44).

[0115] Next, the processor (13) can determine whether the objective has been achieved through the results of the prior management (S45).

[0116] If the objective is not achieved, the processor (13) may decide to re-manage the pre-management (S46).

[0117] If the objective is achieved, the processor (13) may decide not to proceed with drug prescription and surgery (S47). That is, since the patient's condition has improved through prior care, drug prescription and surgery are not to proceed.

[0118] Meanwhile, if it is decided to re-conduct the preliminary management, the processor (13) can reset the management method and management period for the re-conducted preliminary management based on the performance data and result data of the previously conducted preliminary management.

[0119] Specifically, the processor (13) can reset the management method for the pre-management to be performed again by comprehensively considering the number of times the management method was modified in the previously performed pre-management, the content modified for each time, and the change in the patient's condition after the modified management method was applied.

[0120] The processor (13) can set the duration of the re-conducted pre-management to be shorter than the duration of the previous pre-management. For example, if the duration of the previous pre-management was 2 weeks, the duration of the re-conducted pre-management can be set to 1 week.

[0121] In addition, the processor (13) of the patient management device (10) can determine whether to proceed with post-management of the patient based on performance data and result data regarding pre-management.

[0122] That is, the processor (13) can determine rehabilitation management matters based on the process and results of the pre-management stage.

[0123] The processor (13) can analyze the performance data and result data for all pre-management performed (including both the initial pre-management and the re-performed pre-management) to set the post-management method for the patient.

[0124] Here, follow-up care may include group rehabilitation, partnership rehabilitation, institutional rehabilitation, and home-based rehabilitation. Additionally, follow-up care may include dietary management and sleep management.

[0125] Although FIG. 2 describes the steps being executed sequentially, this is merely an illustrative explanation of the technical concept of the present embodiment. A person skilled in the art to which the present embodiment belongs can modify and adapt the steps described in FIG. 2 in various ways, such as changing the order or executing them in parallel, without departing from the essential characteristics of the present embodiment. Therefore, FIG. 2 is not limited to a chronological order.

[0126] Meanwhile, in the above description, the steps described in FIG. 2 may be further divided into additional steps or combined into fewer steps according to an embodiment of the present disclosure. Additionally, some steps may be omitted as necessary, and the order of the steps may be changed.

[0127] Meanwhile, the disclosed embodiments may be implemented in the form of a recording medium that stores instructions executable by a computer. The instructions may be stored in the form of program code and, when executed by a processor, may generate a program module to perform the operation of the disclosed embodiments. The recording medium may be implemented as a computer-readable recording medium.

[0128] Computer-readable recording media include all types of recording media that store instructions that can be decoded by a computer. Examples include ROM (Read Only Memory), RAM (Random Access Memory), magnetic tape, magnetic disk, flash memory, optical data storage devices, etc.

[0129] As described above, the disclosed embodiments have been explained with reference to the attached drawings. Those skilled in the art will understand that the present disclosure may be practiced in forms different from the disclosed embodiments without changing the technical spirit or essential features of the present disclosure. The disclosed embodiments are illustrative and should not be interpreted restrictively. Explanation of the symbols

[0130] 10: Patient management device 11: Communications Department 12: Memory 13: Processor 131: Dictionary Management Module 132: Surgery / Prescription Module 133: Post-management module 20: Patient terminal

Claims

Claim 1 A patient management device for preventing disease exacerbation, comprising: a memory storing at least one process for managing a patient to prevent disease exacerbation; and a processor that performs operations based on said process, wherein the processor determines whether drug prescription and surgery are necessary based on the patient's condition, performs pre-management for different purposes according to said necessity, and when said pre-management is completed, determines whether said purpose has been achieved, and determines whether to re-perform said pre-management or proceed with drug prescription and surgery according to said achievement. Claim 2 A patient management device for preventing disease exacerbation according to claim 1, wherein the processor is set as the purpose to make the patient's condition capable of receiving the drug prescription and surgery when the drug prescription and surgery are required, and as the purpose to check whether the patient's condition improves without receiving the drug prescription and surgery when the drug prescription and surgery are not required. Claim 3 A patient management device for preventing disease exacerbation, wherein, in the case where the drug prescription and surgery are required, the processor is further configured for the purpose of confirming the expected response of the patient's body during the drug prescription and surgery. Claim 4 A patient management device for preventing disease exacerbation according to claim 1, wherein the processor determines to proceed with the drug prescription and surgery when the objective is achieved in cases where the drug prescription and surgery are necessary, and determines to re-conduct the pre-management when the objective is not achieved in cases where the drug prescription and surgery are necessary, and determines not to proceed with the drug prescription and surgery when the objective is achieved in cases where the drug prescription and surgery are not necessary, and determines to re-conduct the pre-management when the objective is not achieved in cases where the drug prescription and surgery are not necessary. Claim 5 A patient management device for preventing disease exacerbation according to claim 1, wherein the prior management includes management of at least one of exercise, diet, sleep, and lifestyle habits, and the processor sets a management method for the at least one according to the patient's condition, and modifies the management method based on performance data and result data provided from the patient's terminal as the prior management proceeds according to the management method. Claim 6 A patient management device for preventing disease exacerbation according to claim 5, wherein the processor, when it is determined to re-conduct the prior management, resets the management method for the re-conducted prior management based on the performance data and result data of the previously conducted prior management. Claim 7 A patient management device for preventing disease exacerbation according to claim 1, wherein the prior management is set for different periods for cases where the drug prescription and surgery are required and cases where the drug prescription and surgery are not required, respectively. Claim 8 In claim 1, the processor determines whether to proceed with post-care of the patient based on performance data and result data regarding the prior care, a patient management device for preventing disease exacerbation. Claim 9 A patient management method for preventing disease exacerbation, comprising: a step of determining whether drug prescription and surgery are necessary based on the patient's condition; a step of conducting pre-management for different purposes according to the said necessity; a step of determining whether the said purpose has been achieved when the said pre-management is completed; and a step of determining whether to re-conduct the said pre-management or to proceed with drug prescription and surgery according to the said achievement. Claim 10 A patient management method for preventing disease exacerbation according to claim 9, wherein, when the above drug prescription and surgery are required, the objective is set to make the patient's condition capable of receiving the above drug prescription and surgery, and when the above drug prescription and surgery are not required, the objective is set to confirm whether the patient's condition improves without receiving the above drug prescription and surgery. Claim 11 A patient management method for preventing disease exacerbation according to claim 10, wherein, in cases where the above drug prescription and surgery are required, the above purpose is further set to confirm the expected response of the patient's body during the above drug prescription and surgery. Claim 12 A method for managing a patient to prevent disease exacerbation according to claim 9, wherein the step of determining whether to re-conduct the aforementioned pre-treatment or proceed with drug prescription and surgery comprises deciding to proceed with the aforementioned drug prescription and surgery when the purpose is achieved in cases where the aforementioned drug prescription and surgery are necessary, deciding to re-conduct the aforementioned pre-treatment when the purpose is not achieved in cases where the aforementioned drug prescription and surgery are necessary, deciding not to proceed with the aforementioned drug prescription and surgery when the purpose is achieved in cases where the aforementioned drug prescription and surgery are not necessary, and deciding to re-conduct the aforementioned pre-treatment when the purpose is not achieved in cases where the aforementioned drug prescription and surgery are not necessary. Claim 13 A patient management method for preventing disease exacerbation according to claim 9, wherein the prior management includes management of at least one of exercise, diet, sleep, and lifestyle habits, and the step of performing the prior management includes: a step of setting a management method for the at least one according to the condition of the patient; and a step of modifying the management method based on performance data and result data provided from the patient's terminal as the prior management is performed according to the management method. Claim 14 A patient management method for preventing disease exacerbation according to claim 13, further comprising the step of resetting the management method for the re-conducted prior management based on performance data and result data for the previously conducted prior management when it is decided to re-conduct the prior management. Claim 15 In claim 9, the above-mentioned prior care is a patient management method for preventing disease exacerbation, wherein the aforementioned prior care is set for different periods for cases where the above-mentioned drug prescription and surgery are required and cases where the above-mentioned drug prescription and surgery are not required, respectively. Claim 16 A patient management method for preventing disease exacerbation according to claim 9, further comprising the step of determining whether to proceed with post-management of the patient based on performance data and result data regarding the prior management. Claim 17 A computer-readable recording medium that is combined with a computer, which is hardware, and stores a computer program that executes the method of any one of claims 9 to 16.

Images