Medication management method, and device for performing method
Patent Information
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-02-12
- Publication Date
- 2026-08-13
Smart Images

Figure KR2025002026_13082026_PF_FP_ABST
Abstract
Description
Method for managing medication and a device for performing such a method
[0001] The present invention relates to a medication management method and an apparatus for performing such a method. More specifically, it relates to a medication management method for adaptively performing medication management based on user information and an apparatus for performing such a method.
[0002] The digital healthcare industry is growing rapidly due to the development of Fourth Industrial Revolution technologies, such as non-face-to-face technology, artificial intelligence, and big data, as well as increasing interest in personal health. The digital (smart) healthcare industry is a convergence of medical care and ICT (information and communication technology). It provides intelligent services based on medical data to monitor and manage individual patients' health conditions in real time, and enables optimized, customized medical services by analyzing health information and disease states; it is also referred to as the 'smart healthcare industry.'
[0003] The paradigm of the medical industry is changing as medical institutions evolve from traditional treatment-centered medical services to 4P (Personalized, Predictive, Preventive, Participatory)-driven healthcare services, which incorporate IT, BT, and NT technologies for the purpose of not only patient diagnosis but also disease prevention and management.
[0004] The ICT-based digital healthcare industry of the Fourth Industrial Revolution is evolving into services such as the management of diseases, health, and dietary habits for patients and the general public using medical IT devices and service apps, as the methods of accessing and securing medical data are changing due to the convergence of medicine and ICT.
[0005] Based on this, personalized treatment services and digital healthcare services, such as precision medicine, telemedicine, and monitoring services that can manage the entire life cycle, are expected to expand.
[0006] With current data alone, which lacks information on patients' actual drug use, it is possible to prevent unnecessary increases in medical costs caused by inappropriate drug use. A representative factor contributing to these unnecessary increases in medical costs is drug side effects. Since the domestic drug side effect reporting system was established, the number of drug side effect cases in Korea has increased rapidly and ranks 2nd to 4th among countries.
[0007] As this can place a significant burden on society as a whole, a strategic approach to innovatively reduce it is required, and the development of systems for managing related drug safety is urgently needed. The emergence of digital healthcare based on pharmacy and pharmaceutical information—encompassing the reduction of drug misuse and abuse, medication guidance for chronic disease patients, and chronic disease prediction—is expected to contribute to the advancement of national health management and the efficiency of health insurance finances across various fields.
[0008] Modern users take various medicines and health functional foods, and adaptive medication management is required depending on the user.
[0009] The present invention aims to solve all of the aforementioned problems.
[0010] In addition, the present invention aims to perform adaptive medication management for each user based on user information (user age, gender, medication information, etc.).
[0011] In addition, the present invention aims to perform medication management by linking various medical services provided to the user through the anonymization of personal information and integration with an API (application interface).
[0012] A representative configuration of the present invention for achieving the above objective is as follows.
[0013] According to one embodiment of the present invention, a medication management method may include the step of a drug information collection and processing unit of a digital healthcare device collecting and standardizing drug information, the step of a user information input unit of the digital healthcare device receiving user information, and the step of a medication management unit of the digital healthcare device performing medication management based on the user information and the drug information.
[0014] Meanwhile, the above drug information can be standardized based on global codes and standardized databases.
[0015] In addition, the above medication management unit may be implemented to check for drug interactions, duplicate drugs, side effects and allergies, and dosages.
[0016] According to another embodiment of the present invention, a digital healthcare device for performing medication management may include a drug information collection and processing unit implemented to collect and standardize drug information, a user information input unit implemented to receive user information, and a medication management unit implemented to perform medication management based on the user information and the drug information.
[0017] Meanwhile, the above drug information can be standardized based on global codes and standardized databases.
[0018] In addition, the above medication management unit may be implemented to check for drug interactions, duplicate drugs, side effects and allergies, and dosages.
[0019] According to the present invention, medication management can be performed adaptively for each user based on user information (user age, gender, medication information, etc.).
[0020] In addition, according to the present invention, medication management can be performed by linking various medical services provided to the user through the anonymization of personal information and API (application interface) integration.
[0021] FIG. 1 is a conceptual diagram showing a digital healthcare device according to an embodiment of the present invention.
[0022] FIG. 2 is a conceptual diagram showing the operation of a medication management unit according to an embodiment of the present invention.
[0023] FIG. 3 is a conceptual diagram illustrating a method for collecting and processing pharmaceutical information and health functional food information according to an embodiment of the present invention.
[0024] Figure 4 is a screen provided by the medication management unit according to an embodiment of the present invention.
[0025] FIG. 5 is a conceptual diagram showing the interaction check section of the medication management section according to an embodiment of the present invention.
[0026] FIG. 6 is a conceptual diagram showing the operation of the side effect and allergy check unit of the medication management unit according to an embodiment of the present invention.
[0027] FIG. 7 is a conceptual diagram showing the operation of the contraindication and caution drug inspection unit of the medication management unit according to an embodiment of the present invention.
[0028] FIG. 8 is a conceptual diagram showing the operation of the duplicate drug check unit of the medication management unit according to an embodiment of the present invention.
[0029] FIG. 9 is a conceptual diagram showing the operation of the health functional food recommendation unit of the medication management unit according to an embodiment of the present invention.
[0030] FIG. 10 is a conceptual diagram showing the operation of the health functional food information providing unit of the medication management unit according to an embodiment of the present invention.
[0031] FIG. 11 is a conceptual diagram showing the operation of the drug information providing unit of the medication management unit according to an embodiment of the present invention.
[0032] FIG. 12 is a conceptual diagram illustrating a method of performing medication management through linkage between a digital healthcare device and an external device according to an embodiment of the present invention.
[0033] FIG. 13 is a conceptual diagram illustrating a method of performing medication management through linkage between a digital healthcare device and an external device according to an embodiment of the present invention.
[0034] FIG. 14 is a conceptual diagram illustrating a method for identifying the components of a pharmaceutical product and creating a database of the components according to an embodiment of the present invention.
[0035] FIG. 15 is a conceptual diagram showing the operation of an interaction check unit according to an embodiment of the present invention.
[0036] FIG. 16 is a conceptual diagram illustrating the operation of performing duplicate drug checks according to an embodiment of the present invention.
[0037] The following detailed description of the invention refers to the accompanying drawings, which illustrate specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. It should be understood that various embodiments of the invention are different but need not be mutually exclusive. For example, specific shapes, structures, and characteristics described herein may be modified from one embodiment to another without departing from the spirit and scope of the invention. It should also be understood that the location or arrangement of individual components within each embodiment may be modified without departing from the spirit and scope of the invention. Accordingly, the following detailed description is not meant to be limiting, and the scope of the invention should be understood to encompass the scope claimed by the claims and all equivalents thereof. Similar reference numerals in the drawings indicate identical or similar components across various aspects.
[0038] Hereinafter, in order to enable a person skilled in the art to easily practice the present invention, various preferred embodiments of the present invention will be described in detail with reference to the attached drawings.
[0039]
[0040] FIG. 1 is a conceptual diagram showing a digital healthcare device according to an embodiment of the present invention.
[0041] Figure 1 discloses a digital healthcare device for processing drug information and performing customized medication management for a user.
[0042] Referring to FIG. 1, the digital healthcare device may include a drug information collection and processing unit (100), a user information input unit (110), a medication management unit (120), an external system linkage unit (130), and a processor (140).
[0043] The drug information collection and processing unit (100) may be implemented to collect and process drug information. The drug information may include information regarding the ingredients, effects, side effects, etc. of standardized drugs. The drug information collection and processing unit (100) may collect drug information and manage the ingredients, effects, side effects, etc. of drugs as standardized information through processing that standardizes the collected drug information.
[0044] The user information input section (110) can be implemented to receive user information. The user information may include various information necessary to provide and recommend health functional food information to the user. The user information may include information about the user's gender, age, etc., user medication information, user health functional food intake information, user health checkup information, user genetic information, etc.
[0045] The medication management unit (120) may be implemented to manage the user's medication based on user information. The medication management unit (120) may include an interaction check unit, a duplicate drug check unit, a side effect and allergy check unit, a contraindication and caution drug check unit, a dosage check unit, a health functional food recommendation unit, a drug information provision unit, and the like. The specific operation of the medication management unit (120) will be described later.
[0046] The external system linkage unit (130) can be implemented to link the user's medication information with the outside. The external system linkage unit (130) can be implemented to de-identify user information through user de-identification and to provide an API to check the user's medication information in a separate medical system (e.g., a remote medical system).
[0047] The processor (140) can be implemented to control the operation of the drug information collection and processing unit (100), user information input unit (110), medication management unit (120), and external system linkage unit (130).
[0048]
[0049] FIG. 2 is a conceptual diagram showing the operation of a medication management unit according to an embodiment of the present invention.
[0050] In Fig. 2, an operation to perform medication management for the user is initiated in the medication management unit.
[0051] Referring to FIG. 2, the medication management unit may include an interaction check unit (200), a duplicate drug check unit (210), a side effect and allergy check unit (220), a contraindication and caution drug check unit (230), a dosage check unit (240), a health functional food recommendation unit (250), a drug information provision unit (260), and a health functional food information provision unit (270).
[0052] The interaction check unit (200) may be implemented to check for interactions between pharmaceuticals and / or health functional foods. The interaction check unit (200) may be implemented to check for interactions based on standardized pharmaceutical information and health functional food information. For example, the interaction check unit (200) may determine whether an interaction occurs between active ingredients based on the active ingredients of the pharmaceuticals and the active ingredients of the health functional foods.
[0053] The duplicate drug check unit (210) may be implemented to check for duplication between pharmaceuticals and / or health functional foods. The duplicate drug check unit (210) may be implemented to determine duplicate ingredients based on standardized pharmaceutical information and health functional food information. For example, the duplicate drug check unit (210) may make a determination on whether duplication occurs between active ingredients based on the active ingredients of the pharmaceuticals and the active ingredients of the health functional foods.
[0054] The side effect and allergy check unit (220) may be implemented to perform a check for side effects and allergies that may occur when taking pharmaceuticals and / or health functional foods. The side effect and allergy check unit (220) may perform a check for side effects and allergies that may occur through an interaction check and a duplicate drug check for pharmaceuticals and / or health functional foods. The side effect and allergy check unit (220) may additionally perform a check for side effects and allergies by considering user information.
[0055] The contraindication and caution drug check unit (230) may be implemented to perform checks on contraindication and caution drugs. The contraindication and caution drug check unit (230) may be implemented to check contraindicated drugs / health functional foods and drugs / health functional foods that require caution based on user information, taking into account user information.
[0056] The dosage check unit (240) may be implemented to check for ingestion of an overdose of a specific active ingredient that may occur when taking a medicine and / or health functional food. The dosage check unit (240) may check for ingestion of an overdose based on the intake information (intake amount, intake time, etc.) of the medicine and / or health functional food.
[0057] The health functional food recommendation unit (250) can be implemented to recommend health functional foods based on user information. User information may include information about the user's gender, age, etc., user medication information, user health functional food intake information, user health checkup information, user genetic information, etc.
[0058] The drug information providing unit (260) may be implemented to provide information about the user's ingested medicine. The drug information providing unit (260) may provide information about the dosage, side effects, etc. of the medicine the user is taking.
[0059] The health functional food information provision unit (270) may be implemented to provide information about the health functional food consumed by the user. The health functional food information provision unit (270) may provide information about the dosage, side effects, etc. of the health functional food that the user consumes.
[0060]
[0061] FIG. 3 is a conceptual diagram illustrating a method for collecting and processing pharmaceutical information and health functional food information according to an embodiment of the present invention.
[0062] Figure 3 discloses a data structure diagram for processing and standardizing information on pharmaceuticals / health functional foods.
[0063] Referring to Fig. 3, information on pharmaceuticals and health functional foods by country can be collected through the country-specific drug library (300).
[0064] As information on pharmaceuticals and health functional foods by country, not only product names and ingredient names, but also country-specific approval details, drug prices and codes, public notices / review guidelines, identification / packaging images, distribution data such as distributors, and patent data can be entered.
[0065] These country-specific drug information and health functional food information can be standardized based on global codes (305) and standardization databases (310, 320, 330). The standardization databases (310, 320, 330) may include a drug ingredient name database (310), a side effect term database (320), and a disease name term database (330). The standardization databases (310, 320, 330) can perform standardization of drug ingredient names, side effect terms, and disease name terms by taking into account global code information.
[0066] The drug ingredient name database (310) may include a drug ingredient name database for single-ingredient products and a drug ingredient name database for combination products. The drug ingredient name database (310) is a database for processing standardized drug ingredient names for single-ingredient products and combination products.
[0067] The side effect term database (320) can be implemented to standardize side effects related to pharmaceuticals and health functional foods. The side effect term database (320) may include a representative term database and a natural language database, and can standardize side effects for pharmaceuticals and health functional foods based on the representative term database and the natural language database.
[0068] A disease name term database (330) can be implemented to standardize disease names related to pharmaceuticals and health functional foods. The disease name term database (330) may include a representative term database and a natural language database, and can standardize disease names related to pharmaceuticals and health functional foods based on the representative term database and the natural language database.
[0069] Drug management and health functional food recommendations can be performed based on these standardized databases (310, 320, 330). As ingredient information data, interaction data, medication guidance data pictograms, efficacy and effect data, contraindication data (pregnant women, age, etc.), dosage data by patient characteristics, allergy warning data, etc. can be generated.
[0070] In addition, ADR data, which is drug side effect data, is managed separately and can be utilized for drug management and health functional food recommendations.
[0071]
[0072] Figure 4 is a screen provided by the medication management unit according to an embodiment of the present invention.
[0073] Referring to Fig. 4, the medication management unit can register the user's prescription data based on OCR.
[0074] Medication notes are registered based on prescription data, and based on this, medication reminders can be delivered to the user and information on medication adherence can be provided.
[0075]
[0076] FIG. 5 is a conceptual diagram showing the interaction check section of the medication management section according to an embodiment of the present invention.
[0077] Referring to Fig. 5, the interaction check unit can provide a safe medication management service after prescription based on an interaction algorithm associated with the drug.
[0078] The interaction check section can provide information on interactions such as drug-drug, drug-food, drug-alcohol / smoking, drug-health functional food, and drug-test results.
[0079]
[0080] FIG. 6 is a conceptual diagram showing the operation of the side effect and allergy check unit of the medication management unit according to an embodiment of the present invention.
[0081] Referring to Fig. 6, the side effect and allergy check unit can register the user's side effects, manage the side effects, provide guidance on the side effects, and provide an alarm on the side effects.
[0082] More specifically, the side effect and allergy check section can provide a drug allergy warning alarm, a warning alarm for side effects of the same ingredient, a warning alarm for side effects of the same class, an alarm providing statistical information on side effects by drug, and a side effect reporting alarm.
[0083]
[0084] FIG. 7 is a conceptual diagram showing the operation of the contraindication and caution drug inspection unit of the medication management unit according to an embodiment of the present invention.
[0085] Referring to Fig. 7, the contraindication and caution drug check unit can provide contraindication and caution alarm services for prescription drugs and over-the-counter drugs. Based on input user information, an alarm service can be provided to help the user safely take the medicine through warnings regarding contraindications, cautions, overdose, etc.
[0086] Information regarding precautions and contraindications for pregnant women, age restrictions, gender restrictions, and precautions based on patient (user) characteristics can be provided as an alarm service.
[0087]
[0088] FIG. 8 is a conceptual diagram showing the operation of the duplicate drug check unit of the medication management unit according to an embodiment of the present invention.
[0089] Referring to Fig. 8, the duplicate drug check unit can be implemented to provide a duplicate ingredient notification service for prescription drugs and over-the-counter drugs. It can check for duplicate products and duplicate ingredients of drugs that the user has been prescribed or is taking. Through this, the user's medical expenses can be reduced and the user's safety can be enhanced.
[0090] More specifically, the duplicate drug check department performs a judgment on identical ingredients and identical efficacy, and can perform a judgment on identical ingredients / duplicate ingredients, identical products, and duplicate ingredients with identical efficacy.
[0091]
[0092] FIG. 9 is a conceptual diagram showing the operation of the health functional food recommendation unit of the medication management unit according to an embodiment of the present invention.
[0093] Referring to Fig. 9, the health functional food recommendation unit can be implemented to recommend health functional foods based on user data or to provide information such as dosage checks and interactions.
[0094] The health functional food recommendation section can provide nutrient recommendations / nutrient information and provide health functional food recommendations / health functional food information.
[0095]
[0096] FIG. 10 is a conceptual diagram showing the operation of the health functional food information providing unit of the medication management unit according to an embodiment of the present invention.
[0097] Referring to Fig. 10, the health functional food information provider can refine and process basic information of the health functional food and provide visualized information.
[0098] The health functional food information provision department can classify the raw materials / ingredients, main ingredients / auxiliary ingredients of health functional foods and provide information.
[0099]
[0100] FIG. 11 is a conceptual diagram showing the operation of the drug information providing unit of the medication management unit according to an embodiment of the present invention.
[0101] Referring to FIG. 11, the drug information provider may be implemented to provide information about the drug being taken to the user.
[0102] The drug information provider can deliver medication guidance and information content curated to suit user information through the institution's PHR (personal health record) app and KakaoTalk.
[0103] Medication information content may include short-form videos, medication instruction videos, articles, health information card news, etc.
[0104] Medication information content may be provided considering gender, age, disease, drug name, literacy level, etc.
[0105]
[0106] FIG. 12 is a conceptual diagram illustrating a method of performing medication management through linkage between a digital healthcare device and an external device according to an embodiment of the present invention.
[0107] In Fig. 12, medication management can be performed through the linkage between a digital healthcare device and an external device.
[0108] Referring to Fig. 12, user information is anonymized, and the function of the medication management unit provided by the digital healthcare device can be provided through an application interface (API).
[0109] For example, if a user visits Hospital A, this may occur when additional medication is provided based on anonymized user information and the user's existing medication management information.
[0110] For the anonymization of user information, name data acting as an identifier is deleted and a user number is assigned; among quasi-identifiers, age, which is important for the intended purpose, may be subject to a lower category and level of categorization. However, a higher level of categorization may be applied to gender and address to reduce the risk of re-identification.
[0111] The aforementioned drug interaction checks, duplicate drug checks, side effect / allergy checks, contraindication and caution drug checks, and dosage and route of administration checks can be provided via API.
[0112]
[0113] FIG. 13 is a conceptual diagram illustrating a method of performing medication management through linkage between a digital healthcare device and an external device according to an embodiment of the present invention.
[0114] FIG. 13 discloses a method for performing medication management through interoperability between devices of various external institutions.
[0115] Referring to Fig. 13, medication management can be performed at hospitals, rehabilitation centers / nursing homes, pharmacies, homes, etc.
[0116] Based on the aforementioned anonymized user information, it can be linked with hospital information systems and telemedicine systems, mobile EMRs, multi-drug management pharmacy programs, TV apps, AI speaker PHR apps, wearable devices, etc., to control the prescription of medicines and consumption of health functional foods tailored to the user.
[0117]
[0118] FIG. 14 is a conceptual diagram illustrating a method for identifying the components of a pharmaceutical product and creating a database of the components according to an embodiment of the present invention.
[0119] FIG. 14 discloses a method for assigning an identifier to a pharmaceutical ingredient.
[0120] Referring to FIG. 14, an identifier can be assigned to each of the various ingredients by considering ingredient information. The ingredient information may include various information about the ingredients, such as functional information, raw material information, physiological function information, and appropriate dosage information.
[0121] An identifier for a component is generated by considering information regarding each component data. For example, assuming that an identifier is generated based on functional information, raw material information, physiological function information, and appropriate dosage information, a first vector (functional information) corresponding to the functional information of the component, a second vector (raw material information) corresponding to the raw material information of the component, a third vector (physiological function information) corresponding to the physiological function information of the component, and a fourth vector (appropriate dosage information) corresponding to the appropriate dosage information of the component are defined, and a component identifier (1420) can be generated based on a component vector (1400) based on the first vector (functional information), the second vector (raw material information), the third vector (physiological function information), and the fourth vector (appropriate dosage information). A vector including such a first vector (functional information), a second vector (raw material information), a third vector (physiological function information), and a fourth vector (appropriate dosage information) is a component vector (1400), and a component identifier (1420) can be determined based on the component vector (1400).
[0122] If there is no identical component vector (1400), a component identifier (1420) is generated based solely on the component vector (1400). Conversely, if there is an identical component vector (1400) for a component of another drug, a component identification identifier is added as an additional vector to determine the component vector (1400), and a component identifier (1420) can be generated based on the component vector (1400).
[0123] In addition, the sub-vectors constituting the component vector (the aforementioned first vector, second vector, third vector, fourth vector, etc.) can be determined based on the similarity of information. For example, assuming a first vector (functional information) corresponding to the functional information of a component, the more similar the functionality, the more similar the first vector can be set. For example, the higher the relative similarity between Function A and Function B, the more similar the first vector value (functional information) corresponding to Function A and the first vector value (functional information) corresponding to Function B may be.
[0124] In addition, the stronger the functionality, the larger the value may be set to have within the corresponding sub-vector. If the range of the first vector value (functional information) for Function A is a to b, the stronger the functionality, the larger the value may be set to have within the range of the first vector value (functional information) for Function A.
[0125] A pharmaceutical product may contain multiple components, and multiple component identifiers (1420) for each of the multiple components may correspond to a pharmaceutical product identifier (1470). That is, the pharmaceutical product identifier (1470) may correspond to multiple component identifiers (1420) for each of the multiple components constituting the pharmaceutical product.
[0126] In other words, a single pharmaceutical product may contain multiple components, and each of the multiple components may have a plurality of component vectors (1400). A pharmaceutical vector (1450) containing multiple component vectors (1400) corresponding to each of the multiple components included in the pharmaceutical product may be defined. That is, a single pharmaceutical product corresponds to a single pharmaceutical vector (1450), and a single pharmaceutical vector (1450) may contain multiple component vectors (1400).
[0127] In an embodiment of the present invention, instead of the entire composition of the drug, a specific component is determined as the target component to determine the component vector (1400), component identifier (1420), drug vector (1450), and drug identifier (1470).
[0128] More specifically, in order to check for interactions between a drug and other drugs or health functional foods, and to determine overlapping drugs, side effects, and allergies, a target component among the drug ingredients can be determined for evaluation.
[0129] The target component of a drug can be determined by first considering the functionality of the components included in the drug.
[0130] The functionality of an ingredient can be determined based on its health effects. For example, consider a scenario where Ingredient A, Ingredient B, and Ingredient C are included in a pharmaceutical product. Ingredient C may be an ingredient intended to enhance flavor rather than a functional health ingredient. In this case, Ingredients A and B, excluding Ingredient C, can be selected as candidate target ingredients.
[0131] Next, among the candidate target ingredients, those judged to have minimal health effects based on their dosage, those judged not to interact with other ingredients, and those judged not to cause side effects or allergies may be further filtered out and ultimately selected as the target ingredients.
[0132] For example, if it is determined that among candidate target ingredients (Ingredients A, B, and C), the dosage of Ingredient C falls below the critical dosage, and thus no effective health effects or effective interactions with other ingredients will occur, Ingredient C may be excluded from the candidate target ingredients, and Ingredients A and B may be determined as the target ingredients. The size of this critical dosage may be set differently for each ingredient of the health functional food.
[0133] Alternatively, according to an embodiment of the present invention, the target component may be adaptively set by considering the sensitivity to interaction checks and judgments regarding duplicate drugs, side effects, and allergies.
[0134] If the sensitivity for checking interactions and judging duplicate drugs, side effects, and allergies is set relatively high, the threshold component dose for determining the target component may be set relatively low. If the sensitivity for checking interactions and judging duplicate drugs, side effects, and allergies is set relatively low, the threshold component dose may be set relatively high.
[0135] In other words, depending on the sensitivity setting, different components in the drug are determined as target components, and drug interaction checks, duplicate drug checks, and side effect and allergy checks can be performed based on the target components.
[0136]
[0137] FIG. 15 is a conceptual diagram showing the operation of an interaction check unit according to an embodiment of the present invention.
[0138] In FIG. 15, the operation of an interaction check unit based on a component vector constituting a drug is initiated.
[0139] Referring to FIG. 15, for interaction checking, an interaction check map (1500) for interaction checking based on component vectors can be defined.
[0140] The interaction check map (1500) may be a map for checking the interaction between component vectors included in the drug vector of the drug.
[0141] Information regarding interactions between component vectors may be included in the interaction check map (1500). The interaction check map (1500) is generated by component or by component group, and can perform checks on interactions between one component and another component, and checks on interactions between one component group and another component group.
[0142] The area on the interaction check map (1500) of a specific component is divided into sub-map areas considering the interaction with other components, and information about the interaction can be displayed on the divided sub-map areas based on numerical values.
[0143] The sub-maps can be classified into cases where functionality is enhanced upon interaction (first interaction type (1510)), cases where there is no interaction (second interaction type (1520)), cases where functionality is reduced upon interaction (third interaction type (1530)), and cases where side effects occur upon interaction (fourth interaction type (1540)).
[0144] If the submap is of the first interaction type (1510), the degree of improvement in function can be indicated by a mapping value greater than 1. For example, if an interaction check map of component A is assumed, a component vector area corresponding to a component that improves function when acting together with component A can be set as the submap (1510) of the first interaction type.
[0145] If the submap is of the second interaction type (1520), the mapping value of '1' may indicate that no interaction occurs. For example, if an interaction check map of component A is assumed, the component vector area corresponding to the component that does not interact with component A when acting together with component A may be set as the submap of the second interaction type (1520).
[0146] If the submap is of the third interaction type (1530), it may indicate that the interaction occurs in a direction in which the functionality of the component decreases with a mapping value greater than 0 and less than 1. For example, if an interaction check map of component A is assumed, a component vector area corresponding to a component that interacts with component A when acting together with component A and has a negative effect on the function of component A may be set as the submap of the third interaction type (1530).
[0147] If the submap is of the fourth interaction type (1540), it may indicate that an interaction occurs in a negative direction with a mapping value less than '0'. For example, if an interaction check map of component A is assumed, when acting together with component A, if a side effect occurs due to interaction with component A, the component vector area corresponding to the component indicating the side effect through a negative value may be set as the submap of the fourth interaction type (1540).
[0148] In this way, an interaction check map can be formed for each component.
[0149] First, after an interaction check map is created at the component level, the component-level interaction check maps can be combined to generate a component group-level interaction check map.
[0150] For example, a first component and a second component with similar component vectors may be located adjacently on a component vector map. If the first interaction check map of the first component and the second interaction check map of the second component are identical or similar, the first component and the second component may be grouped into a component group, and the first interaction check map and the second interaction check map may be combined and used as the interaction check map of the component group.
[0151] Whether the first interaction check map and the second interaction check map of the second component are identical or similar can be determined based on whether the sub-maps corresponding to the first interaction type, the second interaction type, the third interaction type, and the fourth interaction type are identical, and the similarity of the mapping values of each sub-map.
[0152] For the first interaction type, the similarity of the mapping values can be judged by setting a relatively wide range for similarity judgment, but for the third and fourth interaction types that reduce functionality or cause side effects, the similarity judgment range can be judged by setting a relatively narrow range.
[0153] A pharmaceutical product may have multiple interaction check maps corresponding to multiple components and / or groups of multiple components, and a pharmaceutical interaction check map may exist as a concept encompassing these multiple interaction check maps. Through the pharmaceutical interaction check map, interactions between a specific pharmaceutical product and other pharmaceutical products or health functional foods can be determined.
[0154]
[0155] FIG. 16 is a conceptual diagram illustrating the operation of performing duplicate drug checks according to an embodiment of the present invention.
[0156] In FIG. 16, a duplicate drug check operation of the duplicate drug check unit based on the component vector constituting the drug is initiated.
[0157] Referring to Fig. 16, the duplicate drug check unit can check for duplicate drugs through a duplicate drug check map based on component vectors.
[0158] The duplicate drug check map can be determined by considering the user's medication intake times.
[0159] The duplicate drug check map may include information on the component vectors contained in the drug, the amount of the component corresponding to the component vector, the time it takes for the component to be eliminated from the body, the amount remaining in the body, and the critical amount harmful to the human body.
[0160] When a user takes pharmaceuticals and / or health functional foods, a duplicate drug check map is generated at the time of intake, and based on duplicate or overlapping duplicate drug check maps, it may be possible to determine whether a duplicate drug exceeding a critical amount harmful to the human body is taken at a specific time when a specific ingredient is consumed.
[0161] Based on this duplicate drug check map and information on essential medicines, information on the appropriate time interval for consuming health functional foods can be provided to each user.
[0162] The duplicate drug check map can basically be divided into a non-duplicate area where excessive amounts of the component vector do not cause problems, and a duplicate judgment area where excessive amounts cause problems.
[0163] A judgment regarding duplication may be performed only on the duplication judgment area. A separate judgment may be performed on the duplication judgment area depending on the degree of problem to the human body caused by the duplication. The duplication judgment area may be classified into a first duplication judgment area through an nth duplication judgment area depending on the degree of relatively large problem to the human body.
[0164] As one moves toward higher overlapping judgment areas, such as the first overlapping judgment area to the nth overlapping judgment area, the judgment regarding the appropriate time interval for consumption is performed more strictly, so the range of the appropriate time interval can be set relatively narrowly.
[0165]
[0166] The embodiments according to the present invention described above may be implemented in the form of program instructions that can be executed through various computer components and recorded on a computer-readable recording medium. The computer-readable recording medium may include program instructions, data files, data structures, etc., either individually or in combination. The program instructions recorded on the computer-readable recording medium may be those specifically designed and configured for the present invention or those known and available to those skilled in the art of computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes; optical recording media such as CD-ROMs and DVDs; magneto-optical media such as floptical disks; and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, and flash memory. Examples of program instructions include machine code, such as that generated by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc. Hardware devices may be modified into one or more software modules to perform processing according to the present invention, and vice versa.
[0167] Although the present invention has been described above with reference to specific details such as specific components, limited embodiments, and drawings, this is provided only to aid in a more comprehensive understanding of the invention, and the invention is not limited to the above embodiments, and a person skilled in the art to which the invention belongs can make various modifications and changes from this description.
[0168] Accordingly, the scope of the present invention should not be limited to the embodiments described above, and all scopes equivalent to or equivalently modified from the claims set forth below, as well as the claims set forth below, shall be considered to fall within the scope of the concept of the present invention.
Claims
1. The method of medication management is, A step in which the drug information collection and processing unit of a digital healthcare device collects and standardizes drug information; A step in which a user information input unit of the digital healthcare device receives user information; and A method characterized by including a step in which a medication management unit of the digital healthcare device performs medication management based on the user information and the drug information.
2. In Paragraph 1, A method characterized by the above-mentioned drug information being standardized based on a global code and a standardized database.
3. In Paragraph 2, A method characterized by the above-mentioned medication management unit being implemented to check for drug interactions, duplicate drugs, side effects and allergies, and dosage.
4. A digital healthcare device that performs medication management is, A drug information collection and processing unit implemented to collect and standardize drug information; A user information input unit implemented to receive user information; and A digital healthcare device characterized by including a medication management unit implemented to perform medication management based on the above user information and the above drug information.
5. In Paragraph 4, A digital healthcare device characterized by the above-mentioned pharmaceutical information and above-mentioned health functional food information being standardized based on a global code and a standardized database.
6. In Paragraph 5, A digital healthcare device characterized by the above-mentioned medication management unit being implemented to check for drug interactions, duplicate drugs, side effects and allergies, and dosage.