Method for preventing drug misuse and abuse by visually impaired and electronic device performing same

Abstract

A drug administration management method according to one embodiment disclosed herein may comprise the steps of: receiving identification information of a first drug from a pharmacist terminal; transmitting permission information corresponding to the identification information of the first drug to the pharmacist terminal; receiving customized medication guidance, in which the permission information is personalized according to patient profile information of a patient, from the pharmacist terminal, and storing the customized medication guidance in a patient information database; receiving identification information of a drug from a patient terminal and searching for the identification information of the drug in an internal database; and generating a customized administration schedule for the patient according to administration schedule information of the first drug included in the customized medication guidance if the searched identification information of the drug is the identification information of the first drug.

Description

Method for preventing misuse of medicines by visually impaired persons and electronic device for performing the same

[0001] The present invention relates to a system, an electronic device, and a control method for preventing the misuse of medicines by visually impaired individuals. It supports visually impaired individuals in safely and accurately verifying prescription information and taking medication, and improves the consistency and safety of medication intake through medication guidance and management.

[0002]

[0003] Access to medication and safe medication management for the visually impaired are emerging as critical social issues. Because the visually impaired find it difficult to accurately perceive medication information, they are at a high risk of health problems resulting from incorrect medication use and the dangers of misuse. In particular, they struggle to correctly understand complex prescription information and adhere to medication schedules, which limits their ability to lead independent daily lives and maintain their health.

[0004] Traditionally, medication information for the visually impaired has been provided through Braille labels or simple voice guidance, but these methods have limitations. Statistically, Braille usage is low, and issues regarding information accessibility arise because the visually impaired often find it difficult to read Braille or are frequently not provided with sufficient medication information. Due to these problems, the visually impaired struggle to accurately determine when to take their medication and manage it independently, which leads to drug misuse and abuse.

[0005] To address these issues, it is necessary to develop a system that provides medication information by linking with smartphones via wireless communication methods such as RFID tags. Visually impaired individuals can automatically receive medication information through relatively simple methods like RFID tags, while simultaneously enabling independent medication management.

[0006] Furthermore, there is a need to establish an AI model-based platform that goes beyond simply providing medication information to analyze the medication data of visually impaired individuals, predict the likelihood of disease occurrence, and recommend visits to hospitals or pharmacies when necessary. This would create a digital healthcare environment where the visually impaired can manage their health more systematically and safely.

[0007]

[0008] One objective of the present invention is to provide a system and a control method that automatically provide medication information by linking an RFID tag with a smartphone so that visually impaired individuals can independently understand prescription information and take medication safely, thereby enabling visually impaired individuals to accurately recognize the timing and method of medication and preventing drug misuse by improving information accessibility.

[0009] One objective of the present invention is to support independent health management and a safe medication environment for the visually impaired by building a platform that analyzes the medication patterns of the visually impaired using an artificial intelligence model based on collected medication data and provides customized health management functions, such as disease prediction and recommendations for visiting medical institutions.

[0010] The problems that the present invention aims to solve are not limited to those described above, and problems not mentioned will be clearly understood by those skilled in the art from this specification and the attached drawings.

[0011]

[0012] In one embodiment of the present disclosure, a drug administration management method may be provided. The drug administration management method may include the steps of: receiving identification information of a first drug from a pharmacist terminal; transmitting authorization information corresponding to the identification information of the first drug to the pharmacist terminal; receiving personalized medication instructions from the pharmacist terminal that personalize the authorization information corresponding to the patient's profile information and storing the personalized medication instructions in a patient information database; receiving identification information of a drug from a patient terminal and searching for the identification information of the drug in the internal database; generating a personalized administration schedule for the patient according to the administration schedule information of the first drug included in the personalized medication instructions when the searched identification information of the drug is the identification information of the first drug; transmitting the personalized medication instructions and the personalized administration schedule to the patient terminal; receiving an administration record of the first drug from the patient terminal; analyzing the administration record to update the personalized administration schedule; and transmitting administration notification information according to the updated personalized administration schedule to the patient terminal.

[0013]

[0014] According to one embodiment, the system of the present invention has the effect of preventing drug misuse by enabling visually impaired individuals to automatically receive medication information through RFID tags and smartphones, thereby recognizing the accurate timing and method of medication administration. Through this, visually impaired individuals can increase their independence in medication management, and accessibility to medication information can be significantly improved.

[0015] According to one embodiment, the present invention has the effect of enabling personalized health management and disease prediction by collecting medication data and analyzing medication patterns using artificial intelligence. Visually impaired individuals can receive personalized guidance, such as recommendations to visit a hospital when necessary, thereby enabling them to manage their health more systematically and safely.

[0016] According to one embodiment, the present invention can contribute to establishing a medical data-based medication support service and enhancing the safety of medicines for socially vulnerable groups by providing a specialized medication management platform for the visually impaired. This has the effect of increasing the accessibility of medical information for the visually impaired and supporting a safe and reliable medication environment.

[0017] The effects of the present invention are not limited to the effects described above, and unmentioned effects will be clearly understood by those skilled in the art from this specification and the accompanying drawings.

[0018]

[0019] FIG. 1 is a diagram illustrating the configuration of a system for preventing the misuse of medicines by visually impaired people according to one embodiment.

[0020] FIG. 2 is a diagram illustrating the configuration of a server according to one embodiment.

[0021] FIG. 3 is a diagram illustrating the configuration of a user terminal according to one embodiment.

[0022] FIG. 4 is a diagram illustrating the operation method of a system for preventing the misuse of medicines by visually impaired people according to one embodiment.

[0023] FIG. 5 is a diagram illustrating a method for generating medication information and managing a user's medication history according to one embodiment.

[0024] FIGS. 6 and 7 are drawings illustrating a method for a user terminal to obtain medication information from an RFID tag on which medication information is recorded, according to one embodiment.

[0025] FIG. 8 is a diagram illustrating a method of providing an alarm to a user based on medication information according to one embodiment.

[0026] FIG. 9 is a diagram illustrating a method for a user terminal to provide an alarm suggesting a time to visit a pharmacy according to one embodiment.

[0027] FIGS. 10 and FIGS. 11 are drawings for explaining a method for constructing an artificial intelligence model according to one embodiment.

[0028] FIG. 12 is a system configuration diagram for explaining the configuration and operation of a drug administration management system according to some embodiments of the present disclosure.

[0029] FIG. 13 is a signal flowchart for explaining the operation of a drug administration management method according to some embodiments of the present disclosure.

[0030] FIG. 14 is a drawing illustrating a user interface screen for registering a pharmaceutical product according to some embodiments of the present disclosure.

[0031] FIG. 15 is a diagram illustrating an operation of receiving identification information of a drug according to some embodiments of the present disclosure.

[0032] FIG. 16 is a flowchart for explaining the operation of obtaining authorization information according to some embodiments of the present disclosure, described with reference to FIG. 13.

[0033] FIG. 17 is a drawing illustrating an example of a drug information template according to some embodiments of the present disclosure.

[0034] FIG. 18 is a detailed flowchart for explaining the operation of a drug administration management method according to some embodiments of the present disclosure, described with reference to FIG. 13.

[0035] FIG. 19 is a detailed flowchart for explaining the operation of a drug administration management method according to some embodiments of the present disclosure, described with reference to FIG. 13.

[0036] FIG. 20 is a detailed flowchart for explaining the operation of a drug administration management method according to some embodiments of the present disclosure, described with reference to FIG. 13.

[0037] FIG. 21 is a detailed flowchart for explaining the operation of a drug administration management method according to some embodiments of the present disclosure, described with reference to FIG. 13.

[0038] FIG. 22 is a detailed flowchart for explaining the operation of a drug administration management method according to some embodiments of the present disclosure, described with reference to FIG. 13.

[0039] FIG. 23 is a detailed flowchart for explaining the operation of a drug administration management method according to some embodiments of the present disclosure, described with reference to FIG. 13.

[0040] FIG. 24 is a detailed flowchart for explaining the operation of a drug administration management method according to some embodiments of the present disclosure, described with reference to FIG. 13.

[0041] FIG. 25 is a drawing illustrating an example of a user interface screen displayed on a patient terminal according to some embodiments of the present disclosure.

[0042] FIG. 26 illustrates an exemplary computing device capable of implementing systems according to some embodiments of the present disclosure.

[0043]

[0044] The aforementioned objectives, features, and advantages of the present application will become more apparent from the following detailed description in conjunction with the accompanying drawings. However, as the present application is subject to various modifications and may have various embodiments, specific embodiments are illustrated in the drawings and described in detail below.

[0045] Throughout the specification, identical reference numbers generally represent identical components. Additionally, components with identical functions within the same scope of concept appearing in the drawings of each embodiment are described using the same reference numeral, and redundant descriptions thereof are omitted.

[0046] If it is determined that a detailed description of known functions or configurations related to this application could unnecessarily obscure the essence of this application, such detailed description is omitted. Furthermore, numbers used in the description of this specification (e.g., First, Second, etc.) are merely identifiers to distinguish one component from another.

[0047] Furthermore, the suffixes "module" and "part" for components used in the following embodiments are assigned or used interchangeably solely for the ease of drafting the specification, and do not inherently possess distinct meanings or roles.

[0048] In the following examples, singular expressions include plural expressions unless the context clearly indicates otherwise.

[0049] In the following embodiments, terms such as "include" or "have" mean that the features or components described in the specification are present, and do not preclude the possibility that one or more other features or components may be added.

[0050] In the drawings, the size of components may be exaggerated or reduced for convenience of explanation. For example, the size and thickness of each component shown in the drawings are arbitrarily depicted for convenience of explanation, and the present invention is not necessarily limited to what is illustrated.

[0051] Where an embodiment can be implemented differently, the order of a particular process may be performed differently from the order described. For example, two processes described consecutively may be performed substantially simultaneously or proceed in the reverse order of the description.

[0052] In the following embodiments, when components are described as being connected, the case includes not only instances where the components are directly connected but also instances where components are indirectly connected by interposing them in between.

[0053] For example, when it is stated in this specification that components, etc. are electrically connected, it includes not only cases where the components, etc. are directly electrically connected, but also cases where components, etc. are interposed in between and are indirectly electrically connected.

[0054]

[0055] Hereinafter, with reference to the drawings, a system and electronic device for preventing the misuse of medicines by visually impaired people and a method for controlling them will be described.

[0056]

[0057] FIG. 1 is a diagram illustrating the configuration of a system for preventing the misuse of medicines by visually impaired people according to one embodiment.

[0058] Referring to FIG. 1, a system for preventing misuse of medicines by visually impaired people according to one embodiment may include a server (100), a hospital terminal (200), a pharmacy terminal (300), and a user terminal (400).

[0059] The server (100) is a central control unit that monitors medication information collected from user terminals and analyzes medication patterns for each user to provide customized alarms. The hospital terminal (200) records the patient's prescription information and, based on this, generates an electronic prescription to manage in conjunction with the server (100) or the pharmacy terminal (300). The pharmacy terminal (300) generates medication information according to the prescription and performs the function of recording medication information on an RFID tag and providing it along with the medicine. The user terminal (400) may be a mobile device used by a visually impaired person and can assist in medication management by scanning the RFID tag to check medication information and providing an alarm.

[0060] The configuration of the system for preventing the misuse of medicines by the visually impaired is described as a server (100), a hospital terminal (200), a pharmacy terminal (300), and a user terminal (400), but is not limited thereto, and some components may be added or omitted as needed.

[0061] For example, some of the functions performed by the server (100) may be configured to be performed by the user terminal (400), and the operations described as being performed by the server (100) in the present invention may be interpreted as being performed identically by the user terminal (400). Accordingly, the functions and operations of the system can be flexibly applied to the arrangement and roles of each component.

[0062]

[0063] FIG. 2 is a diagram illustrating the configuration of a server according to one embodiment.

[0064] Referring to FIG. 2, a server (100) according to one embodiment may include at least one processor (110), a communication interface (120), and a memory (130).

[0065] The processor (110) is a central processing unit capable of performing various tasks and data processing. The processor (110) can process various tasks and data by executing at least one instruction stored in memory (130). The processor (110) can process and analyze medication data collected from multiple user terminals in real time, and can execute algorithms for medication reminders and personalized health management services.

[0066] The communication interface (120) may be a wireless communication device responsible for transmitting and receiving data between the server (110) and an external device. It may be responsible for transmitting and receiving data between the hospital terminal (200), the pharmacy terminal (300), and the user terminal (400) by utilizing various communication technologies. The communication interface (120) may include short-range wireless communication devices such as RFID, NFC, and WIFI, so that data can be transmitted and received quickly over a short distance. In addition, data can be exchanged in real time over a long distance with the hospital terminal (200) or the user terminal (400) through mobile communication methods such as LTE and 5G.

[0067] The memory (130) may be a storage device that stores data processed by the server and stores software and data necessary for system operation. The memory (130) may include RAM that temporarily stores data necessary for generating medication alarms and medication pattern analysis algorithms executed by the processor (110), and non-volatile memory that stores long-term data such as medication records, user information, and prescription history.

[0068]

[0069] FIG. 3 is a diagram illustrating the configuration of a user terminal according to one embodiment.

[0070] Referring to FIG. 3, a user terminal (400) according to one embodiment may include at least one processor (410), a communication interface (420), a memory (430), an input interface (440), an output interface (450), and a GPS module (460).

[0071] The processor (410) is a central processing unit of the user terminal (400) and can perform medication information processing and respond to user commands. The processor (410) can process various tasks and data by executing at least one instruction stored in memory (430).

[0072] The communication interface (420) may be a wireless communication device that enables the user terminal (400) to transmit and receive data with the server (100) and the pharmacy terminal (300). Data can be exchanged in real time with the server via a wireless internet connection such as Wi-Fi or LTE, and information can be exchanged with the pharmacy terminal or drug tag via a short-range wireless communication method such as RFID or NFC.

[0073] The memory (430) is a data storage device of the user terminal and can store data such as medication history, user settings, and medication alarms. It may be composed of RAM for storing medication information and programs executed in the processor (410), and non-volatile memory for storing long-term data.

[0074] The input interface (440) is a device that allows a user to directly input commands into the terminal, and may be a variety of known input devices, mainly a touchscreen or button, or a voice recognition function. It is designed to be easy for a visually impaired person to use, and can perform actions such as registering whether medication has been taken, setting an alarm, and navigating menus.

[0075] The output interface (450) is a device that conveys medication information and alarms to a user and may include a display screen, a speaker, an LED, a vibration motor, etc. Through the output interface (450), a voice guidance function for the visually impaired is provided to provide medication information in voice and to convey important medication alarms in vibration or sound.

[0076] The GPS module (460) is a device capable of tracking the location of a user terminal and can be used to set a medication location or to link with location-based services. For example, the GPS module (460) can provide a pharmacy visit notification when the user approaches a pharmacy, and in case of an emergency, it can transmit the user's location to the server (100) to enable quick action. In addition, it can provide various information necessary for medication based on the user's location.

[0077]

[0078] FIG. 4 is a diagram illustrating the operation method of a system for preventing the misuse of medicines by visually impaired people according to one embodiment.

[0079] Referring to FIG. 4, a system according to one embodiment can be implemented through interconnected operation between a server (100), a hospital terminal (200), a pharmacy terminal (300), and a user terminal (400).

[0080] The server (100) can aggregate and manage data transmitted from an external device. The server (100) can collect and monitor medication data transmitted from a user terminal (400) to analyze medication patterns for each user. Through this, the server (100) can send customized alarms to the user to induce a visit to a pharmacy when medication is depleted or to encourage medication management. The server (100) can monitor multiple user terminals simultaneously and can provide more personalized medication support by setting alarms tailored to each user's medication habits.

[0081] The hospital terminal (200) may be a device in which a doctor records patient information and inputs a prescription at a hospital. The hospital terminal (200) can generate an electronic prescription based on the patient's diagnostic information and the doctor's prescription, and can be linked with the server (100), and can provide electronic prescription data accessible to users and pharmacies. The electronic prescription generated by the hospital terminal (200) can be used to set medication information at pharmacies and can provide basic data necessary for managing the patient's medication.

[0082] The pharmacy terminal (300) can perform the function of generating medication information based on a prescription and recording the information on an RFID tag. The pharmacy terminal (300) can assist a pharmacist in manufacturing medicine based on the medication information and can assist in enabling communication with a user terminal by providing medicine with an RFID tag attached to a visually impaired person. Here, the RFID tag contains information such as the dosage, medication cycle, and precautions, and can support scanning the medication information with a user terminal (400).

[0083] The user terminal (400) may be a smartphone or mobile device used by a visually impaired person. The visually impaired person can check medication information by scanning an RFID tag through the user terminal (400) and receive medication alarms and precautions via voice or vibration. Additionally, the user terminal (400) can assist the server (100) in analyzing medication patterns and providing customized alarms by updating the server (100) whether medication has been completed.

[0084]

[0085] FIG. 5 is a diagram illustrating a method for generating medication information and managing a user's medication history according to one embodiment.

[0086] Referring to FIG. 5, medication information can be generated and the user's medication history can be managed through the following steps: a pharmacy terminal recording medication information on an RFID tag based on a prescription (S10); a user terminal acquiring medication information recorded on an RFID tag (S20); the user terminal providing a guidance message or alarm to the user based on medication information (S30); and a server managing the medication history for each user (S40).

[0087] A pharmacy terminal (300) can generate medication information based on a prescription and record the data on an RFID tag. A pharmacist can print out an RFID tag with the medication information recorded on it, attach it to a medicine bag (medicine pouch), etc., and provide it to a patient. Afterward, the patient can check the recorded medication information by scanning the RFID tag.

[0088] The pharmacy terminal (300) can record medication information not only on RFID tags but also on NFC-based tags. Although the present invention is described with a focus on RFID tags, it is not limited thereto, and various known short-range wireless communication technologies, such as NFC-based tags, can be applied in the same way.

[0089]

[0090] FIGS. 6 and 7 are drawings illustrating a method for a user terminal to obtain medication information from an RFID tag on which medication information is recorded, according to one embodiment.

[0091] Referring to FIGS. 6 and 7, the user terminal (400) can obtain medication information recorded on an RFID tag. The user terminal (400) can obtain medication information recorded on an RFID tag attached to a medicine bag by scanning it through an RFID reader function.

[0092] The user terminal (400) can activate the RFID reader function and prepare for a connection with an RFID tag attached to a medicine bag. The user terminal (400) detects an RFID tag signal at a close distance, and when the RFID tag is recognized, it can transmit and receive data through the communication interface (420).

[0093] The user terminal (400) can analyze medication information and extract necessary data. The user terminal (400) can obtain patient information and prescription drug information from the medication information. The user terminal (400) can extract data from the medication information such as the name of the drug, dosage, medication cycle, method of administration, time of administration (e.g., morning, noon, evening, etc.), start date of administration, end date of administration, storage and preservation method, and precautions for administration. The user terminal (400) can extract patient information (e.g., patient's personal details, patient's health status, etc.) from the medication information.

[0094] The user terminal (400) can manage the acquired data by synchronizing it with the server (100). Through real-time synchronization with the server (100), the medication history for each user can be updated, and this can be used to track and analyze the user's medication habits and patterns.

[0095]

[0096] FIG. 8 is a diagram illustrating a method of providing an alarm to a user based on medication information according to one embodiment.

[0097] Referring to FIG. 8, a user terminal (400) according to one embodiment can perform an operation (S31) of determining the time of medication based on medication information, an operation (S32) of outputting an alarm before the time of medication or a predetermined time before the time of medication, an operation (S33) of determining whether medication is completed based on user input regarding the alarm, and an operation (S34) of updating medication information and transmitting the updated data to a server.

[0098] The user terminal (400) can determine the timing of medication based on data obtained from an RFID tag or a server (100). Here, the timing of medication can be set to an exact time or a specific period at which the user must take the medication, and the user terminal (400) can schedule an alarm based on the timing of medication. Additionally, the user terminal (400) can adjust the frequency of the alarm by taking into account the user's lifestyle pattern.

[0099] The user terminal (400) can output an alarm at the time of taking medication or a predetermined time before the time of taking medication. The user terminal (400) can output an alarm to the user when the time of taking medication approaches, and the type of alarm can be provided in a manner suitable for the visually impaired, such as voice guidance, vibration, or visual notification. The predetermined time can be determined based on user input. For example, if the user sets the alarm time to 5 minutes before, 10 minutes before, etc., the user terminal (400) can provide an alarm based on this.

[0100] The user terminal (400) can determine whether medication has been completed based on user input regarding an alarm that induces medication. The user terminal (400) can record the completion of medication based on button input or voice commands through the input interface (440), thereby recording whether the user has actually taken the medication.

[0101] The user terminal (400) can determine whether medication has been completed and update medication information based on this. The user terminal (400) can transmit the updated medication information to the server (100), and the server (100) can monitor the user's medication history based on this. The server (100) can analyze the user's medication pattern based on the updated medication information and suggest an optimized medication alarm method for the future.

[0102]

[0103] FIG. 9 is a diagram illustrating a method for a user terminal to provide an alarm suggesting a time to visit a pharmacy according to one embodiment.

[0104] Referring to FIG. 9, a user terminal (400) according to one embodiment can perform the operation of monitoring the user's medication history based on updated medication information (S41), the operation of determining the user's remaining medication amount based on the medication history (S42), and the operation of outputting an alarm suggesting a time to visit a pharmacy to the user when the remaining medication amount falls below a predetermined value (S43).

[0105] The user terminal (400) can continuously monitor the medication history based on whether the medication has been taken and the latest medication information entered by the user. The user terminal (400) can record and analyze data such as medication time, medication dosage, and whether the medication has been taken, and based on this, can determine whether the user is complying with the prescribed medication plan.

[0106] The user terminal (400) can calculate the amount of remaining medication in real time based on medication history data. When the user terminal (400) determines that medication is completed, it can calculate that the dosage taken at the time of medication is automatically deducted, and based on this, determine the current remaining amount of medication. Based on the remaining amount of medication, the user terminal (400) can predict how long the user can take the medication and determine the remaining medication period.

[0107] The user terminal (400) can output an alarm suggesting a time to visit a pharmacy to the user when the remaining amount of medication falls below a predetermined value. The user terminal (400) can output an alarm, such as voice or vibration, when the remaining amount of medication falls below a preset minimum threshold value. Furthermore, the user terminal (400) can provide information about nearby pharmacies based on the user's location information, and can also provide an alarm during business hours by considering the operating hours of the pharmacies.

[0108]

[0109] FIGS. 10 and FIGS. 11 are drawings for explaining a method for constructing an artificial intelligence model according to one embodiment.

[0110] Referring to FIGS. 10 and 11, a server (100) according to one embodiment can acquire data accumulated from a user terminal (400) and train an artificial intelligence model based thereon. Here, the artificial intelligence model can train the accumulated user medication data to support personalized medication management and health management. The trained artificial intelligence model can predict the likelihood of medication failure and provide personalized medication guides, such as recommended medication timing, methods for providing personalized alarms, and personalized drug recommendations, based on the user's lifestyle patterns and medication history. Additionally, by analyzing long-term medication data to predict diseases that the user may develop, it can assist in enabling preventive health management.

[0111] The server (100) can train an artificial intelligence model using behavioral data as training data. Here, the behavioral data may include at least one of prescription data extracted from the medication information, medication pattern data reflecting the user's medication pattern, and notification response data in which the user's response to an alarm related to the medication information is recorded.

[0112] The server (100) can provide customized information to the user based on a learned artificial intelligence model. The server (100) can predict the user's medication intake pattern based on an artificial intelligence model. The server (100) can predict the user's likelihood of medication failure based on an artificial intelligence model.

[0113] More specifically, the server (100) can train an artificial intelligence model using data on the user's medication pattern (e.g., prescription information, the user's medication time and interval) and alarm response data including the user's alarm response (e.g., ignoring alarms, delayed medication, etc.). The server (100) can predict whether the user consistently takes medication, whether medication failure occurs at specific times, etc., through the trained artificial intelligence model.

[0114] The server (100) can generate a user-customized medication guide based on an artificial intelligence model. Here, the user-customized medication guide may include at least one of a user-customized recommended medication timing based on behavioral data, a user-customized alarm provision method, and a user-customized recommended drug.

[0115] More specifically, the server (100) can identify situations where medication failure is likely to occur based on data such as the user's lifestyle patterns, schedule, and medication times, and can suggest measures if a high probability of failure is predicted by analyzing past medication failure patterns. For example, if the server (100) determines that the user is likely to fail to take medication at a specific time, it can provide a more intense alarm or provide alarms at a faster frequency. Additionally, the server (100) can determine the time when the user is generally free through an analysis of the user's lifestyle patterns and determine the recommended time for taking medication based on this. The server (100) can determine the user's preferences and provide alarms in the alarm method preferred by the user based on this.

[0116] The server (100) can predict diseases that may occur in the long term based on an artificial intelligence model. The server (100) can generate customized medication and health management solutions based on an artificial intelligence model.

[0117]

[0118] The server (100) can collect data in real time from multiple user terminals and analyze it to comprehensively monitor medication information for each user. The server (100) receives behavioral data collected from user terminals (400), such as whether medication has been completed, the time of medication, and the response to medication alarms (e.g., time of medication completion after receiving the alarm), and can manage medication history for each user.

[0119] The server (100) can monitor medication habits, such as whether the user is following the prescribed medication schedule and whether there are any times when medication failure occurs, by analyzing the individual user's medication patterns based on collected data. It can also provide customized alarms to users expected to fail to take medication or generate recommendations to adjust the timing of medication, thereby supporting more effective medication management.

[0120]

[0121] Hereinafter, a drug administration management system according to another embodiment will be described in detail with reference to FIGS. 12 to 26.

[0122] FIG. 12 is a system configuration diagram for explaining the configuration and operation of a drug administration management system according to some embodiments of the present disclosure.

[0123] Referring to FIG. 12, the drug administration management system (10) can provide personalized drug administration management services to patients. The drug administration management system (10) may include a service server (11) and an internal database (12). The drug administration management system (10) can transmit and receive data with a patient terminal (20) and a pharmacist terminal (30).

[0124] The service server (11) can operate as a central control unit of the drug administration management system (10). The service server (11) can transmit and receive data to and from the patient terminal (20) and the pharmacist terminal (30) via a network. The service server (11) can perform various data processing and computation functions based on information stored in the internal database (12).

[0125] The service server (11) can receive identification information of the first medicine from the pharmacist terminal (30). The service server (11) can transmit authorization information corresponding to the received identification information to the pharmacist terminal (30). In addition, the service server (11) can receive personalized medication guidance based on the patient profile, and generate a customized administration schedule based thereon and provide it to the patient terminal (20). The service server (11) can receive and analyze administration records from the patient terminal (20) and dynamically update the administration schedule.

[0126] The service server (11) may include a pre-trained artificial intelligence model. If specific drug information does not exist in the internal database (12), the service server (11) may use the artificial intelligence model to generate approval information for the corresponding drug. Additionally, the service server (11) may input patient symptom data received from the patient terminal (20) into the artificial intelligence model and provide information recommending drugs that have a high similarity to the symptoms.

[0127] The internal database (12) can store and manage various information related to drug administration management. The internal database (12) can store data or respond to query requests by linking with the service server (11). The internal database (12) may include a patient information database and a drug information database.

[0128] A patient information database can store personalized information for each patient. For example, the database can store the patient's personal information, a list of prescribed medications, medication schedules, and medication completion records. Additionally, the patient information database can support personalized services by storing accessibility option information, such as preferred language settings, font size, and voice guidance speed.

[0129] The drug information database can systematically store detailed information regarding drugs. The drug information database may include information on the drug name, ingredients, efficacy, dosage, precautions, side effects, and interactions of drugs collected from credible institutions. The service server (11) can query the latest information from the drug information database through an Application Programming Interface (API) and provide it to a patient terminal (20) or a pharmacist terminal (30).

[0130] The patient terminal (20) may be a user device for a patient to use a drug administration management service. The patient terminal (20) may provide an interface that can be easily used by all patients, including visually impaired, low-vision, or low-literacy users. The patient terminal (20) may communicate with the service server (11) to receive drug information and transmit medication records.

[0131] The patient terminal (20) may include a function to scan a Radio-Frequency Identification (RFID) tag attached to the medicine. Based on the scanned information, the patient terminal (20) may provide voice guidance on the medicine information received from the service server (11) using Text-to-Speech (TTS) technology. Additionally, the patient terminal (20) may perform functions such as managing the medication schedule, recording whether the medication has been taken, and receiving personalized medication notifications.

[0132] The patient terminal (20) can provide a User Interface (UI) and User Experience (UX) to maximize user accessibility. For example, the patient terminal (20) can support high-contrast colors, large text, screen zoom in and out functions, and vibration feedback. The screen configuration of the patient terminal (20) can be simplified to increase usability and can be designed in compliance with Web Content Accessibility Guidelines (WCAG).

[0133] In one embodiment of the present disclosure, the patient terminal (20) may be various electronic devices equipped with a Near Field Communication (NFC) function. For example, the patient terminal (20) may be a smartphone, a tablet computer, a smart watch, a Personal Digital Assistant (PDA), a wearable device, smart glasses, or a Portable Multimedia Player (PMP). However, the present disclosure is not limited thereto.

[0134] The pharmacist terminal (30) may be a device used by a pharmacist to manage pharmaceutical information and input information to be provided to patients. The pharmacist terminal (30) may communicate with the service server (11) to query pharmaceutical information or generate and transmit customized medication instructions for each patient. The pharmacist terminal (30) may contribute to increasing the operational efficiency of the pharmacy.

[0135] The pharmacist terminal (30) may include a function for inputting and storing drug information into an RFID tag. The pharmacist terminal (30) can automatically search for drug information by scanning a prescription document or a QR code and simplify the input process. Additionally, the pharmacist terminal (30) may provide a function to search for the latest drug information by linking with a central database and to check information on drug interactions or side effects.

[0136] In one embodiment of the present disclosure, the pharmacist terminal (30) may be a computing device of various forms. For example, the pharmacist terminal (30) may be a desktop computer, a laptop computer, a tablet computer, a Point of Sale (POS) system, an industrial personal digital assistant (PDA), a kiosk, or a smartphone. However, the present disclosure is not limited thereto.

[0137] FIG. 13 is a signal flowchart for explaining the operation of a drug administration management method according to some embodiments of the present disclosure.

[0138] Referring to FIGS. 12 and 13, the drug administration management method can be performed by a drug administration management system (10), a patient terminal (20), and a pharmacist terminal (30).

[0139] In step S100, the pharmacist terminal (30) may receive identification information of the first medicine. For example, the pharmacist terminal (30) may scan a Radio Frequency Identification (RFID) tag or a Near Field Communication (NFC) tag attached to the medicine container. The pharmacist terminal (30) may obtain identification information of the first medicine through scanning. However, the present disclosure is not limited thereto.

[0140] In step S200, the pharmacist terminal (30) can transmit identification information of the first medicine to the drug administration management system (10). The pharmacist terminal (30) can communicate with the service server (11) of the drug administration management system (10) via a network. The pharmacist terminal (30) can transmit identification information to the service server (11).

[0141] In step S300, the drug administration management system (10) can obtain authorization information corresponding to the first drug. The drug administration management system (10) can search for the identification information of the received first drug in the internal database (12). The drug administration management system (10) can obtain authorization information for the first drug through the search results. For example, the authorization information may relate to dosage and administration, precautions, side effects, drug interactions, storage methods, contraindications, ingredient information, and pharmaceutical company information. However, the present disclosure is not limited thereto.

[0142] In step S400, the drug administration management system (10) can transmit authorization information to the pharmacist terminal (30). The drug administration management system (10) can convert the acquired authorization information into a format that the pharmacist terminal (30) can display. The drug administration management system (10) can transmit the authorization information in the converted format to the pharmacist terminal (30).

[0143] In step S500, the pharmacist terminal (30) can generate customized medication instructions. The pharmacist can refer to the patient's patient profile information through the pharmacist terminal (30). The pharmacist can consider the patient's age, gender, medical history, allergy information, etc. Based on the considered information, the pharmacist can personalize the received authorization information.

[0144] In step S600, the pharmacist terminal (30) can transmit personalized medication instructions to the drug administration management system (10). The pharmacist terminal (30) can transmit personalized medication instructions, personalized by the pharmacist, to the service server (11).

[0145] In step S700, the drug administration management system (10) can store customized medication instructions in a patient information database. The drug administration management system (10) can link the received customized medication instructions with the corresponding patient's profile. The drug administration management system (10) can store the linked customized medication instructions in the patient information database within the internal database (12).

[0146] In step S800, the patient terminal (20) can transmit identification information of the medicine to the drug administration management system (10). The patient can use the patient terminal (20) to scan the RFID tag attached to the container of the medicine to be administered. The patient terminal (20) can transmit the scanned identification information of the medicine to the drug administration management system (10).

[0147] In step S900, the drug administration management system (10) can generate a customized administration schedule. The drug administration management system (10) can search for identification information of a drug received from a patient terminal (20) in a patient information database. If the identified information of the drug found is the identification information of the first drug, the drug administration management system (10) can generate a customized administration schedule for the patient according to the administration schedule information included in the stored customized medication instructions.

[0148] In step S1000, the drug administration management system (10) can transmit customized medication instructions and a customized administration schedule to the patient terminal (20). The patient terminal (20) can display the received information on a screen. Alternatively, the patient terminal (20) can provide voice guidance on the received information using Text-to-Speech (TTS) technology.

[0149] In step S1100, the patient terminal (20) can generate an administration record. The patient can input whether the administration of the medicine has been completed through the user interface of the patient terminal (20). The patient terminal (20) can generate an administration record based on the input information.

[0150] In step S1200, the patient terminal (20) can transmit the administration record to the drug administration management system (10). The patient terminal (20) can transmit the generated administration record to the service server (11) via a network. The service server (11) can store the transmitted administration record in a patient information database.

[0151] In one embodiment of the present disclosure, the drug administration management system (10) can determine the time when the administration of the first drug is completed. The drug administration management system (10) may use information on the time when it receives identification information of the drug from the patient terminal (20). Alternatively, the drug administration management system (10) may use information on the time when the smart pill container in which the first drug is stored is opened or closed.

[0152] In step S1300, the drug administration management system (10) can update the customized administration schedule. The drug administration management system (10) can evaluate the patient's medication adherence by analyzing the received administration records. The drug administration management system (10) can perform updates based on the analysis results. For example, the drug administration management system (10) can adjust the customized administration schedule. Additionally, the drug administration management system (10) can change the notification method.

[0153] In one embodiment of the present disclosure, the drug administration management system (10) can transmit administration error notification information to the patient terminal (20) if, as a result of analyzing the administration record, the first drug is administered in excess of the recommended dosage within the scheduled administration interval.

[0154] In one embodiment of the present disclosure, the drug administration management system (10) may transmit administration error notification information to the patient terminal (20) if there is no record of completion of administration of the first drug until the scheduled administration time included in the customized administration schedule has elapsed.

[0155] In one embodiment of the present disclosure, the drug administration management system (10) may transmit administration notification information according to a customized administration schedule to a patient terminal (20) when the administration schedule compliance rate included in the administration record is greater than or equal to a preset threshold. Additionally, the drug administration management system (10) may transmit positive feedback information including statistical information regarding the administration schedule compliance rate.

[0156] In step S1400, the drug administration management system (10) can transmit administration notification information to the patient terminal (20). The drug administration management system (10) can transmit administration notification information to the patient terminal (20) at a scheduled administration time according to an updated customized administration schedule. For example, the administration notification information may be a push notification, Short Message Service (SMS), Multimedia Messaging Service (MMS), email, voice guidance, vibration notification, or screen pop-up. However, the present disclosure is not limited thereto.

[0157] FIG. 14 is a drawing illustrating a user interface screen for registering a pharmaceutical product according to some embodiments of the present disclosure.

[0158] Referring to FIG. 14, the screen configuration (300) displayed on the pharmacist terminal (30) may include a drug search (301), RFID tag registration (302), and a list of registered drugs (303). The screen configuration (300) may be a user interface for a pharmacist to register and manage drug information in a system. The pharmacist can identify a specific drug through the screen configuration (300). The pharmacist can assign unique identification information to the corresponding drug through the screen configuration (300). The pharmacist can check the registered details through the screen configuration (300).

[0159] The drug search (301) may be an area where a pharmacist searches for a drug to be registered in the system. The pharmacist can search for drug information stored in the database by entering the name of the drug into the search box. The search results may be displayed including detailed information such as the drug name, manufacturer, and active ingredient. Through this, the pharmacist can accurately select the drug to be registered.

[0160] A pharmacist can select a first drug through a drug search (301). The pharmacist can transmit identification information of the selected first drug to a drug administration management system (10). For example, if the pharmacist selects 'Tylenol 500mg' from the search results, the unique code or name of the corresponding drug can be transmitted to the service server (11) as identification information. The service server (11) can look up the authorization information of the corresponding drug in the internal database (12) based on the received identification information. The service server (11) can send the retrieved authorization information to the pharmacist terminal (30).

[0161] In one embodiment of the present disclosure, the drug search (301) function may utilize barcode scanning or Optical Character Recognition (OCR) technology in addition to a text input method. A pharmacist may automatically input identification information by scanning a barcode printed on the drug packaging or by photographing the name of the drug. This method can minimize human error that may occur during the manual input process. This method can improve the speed and accuracy of the registration procedure.

[0162] RFID tag registration (302) may be an area for linking a physical RFID (Radio-Frequency Identification) tag to a medicine selected through medicine search (301). A pharmacist can register the RFID tag to be attached to the medicine packaging in the system by scanning it. Additionally, the pharmacist can enter and save customized medication instructions to be provided to the patient, such as dosage, efficacy, etc., into the input fields of the area.

[0163] During the RFID tag registration (302) process, the pharmacist can generate customized medication instructions that take into account the patient's specific condition based on standard authorization information received from the service server (11). For example, the pharmacist can adjust the dosage or precautions for administration in response to patient profile information such as the patient's age, underlying diseases, and history of allergic reactions. When the pharmacist selects the 'Register to RFID Tag' button, the generated customized medication instructions and the RFID tag ID can be mapped. The mapped information can be transmitted to the service server (11). The transmitted information can be stored in the patient information database.

[0164] In one embodiment of the present disclosure, an NFC (Near Field Communication) tag may be used in place of or together with an RFID tag during RFID tag registration (302). An NFC tag has high compatibility with general-purpose devices such as smartphones, which can improve patient accessibility. A pharmacist can bring an NFC tag close to a pharmacist terminal (30) to automatically recognize the tag ID. The pharmacist can simplify the registration process by writing personalized medication instructions directly on the tag or linking it to a server.

[0165] The list of registered medicines (303) may be an area displaying a list of medicines that have been successfully registered through the RFID tag registration (302) procedure. The pharmacist can check the names and registration status of the registered medicines at a glance through the list of registered medicines (303). Through this, the pharmacist can clearly recognize whether the registration process has been completed. If necessary, the pharmacist can perform follow-up management, such as viewing or modifying the registered information.

[0166] The service server (11) can receive identification information of a drug from a patient terminal. The service server (11) can search for the received identification information of the drug in the patient information database. If the searched identification information of the drug is the identification information of the first drug, the service server (11) can generate a customized administration schedule for the patient according to the administration schedule information of the first drug included in the customized medication guidance. The service server (11) can transmit the generated customized medication guidance and customized administration schedule to the patient terminal.

[0167] The service server (11) can receive a record of administration of the first drug from the patient terminal. The service server (11) can analyze the received administration record and update a customized administration schedule. The service server (11) can transmit administration notification information according to the updated customized administration schedule to the patient terminal.

[0168] In one embodiment of the present disclosure, the analysis of the administration record may utilize a machine learning algorithm. For example, the service server (11) may analyze the administration record in conjunction with the patient's biosignal data, activity data, diet data, sleep pattern data, Electronic Health Record (EHR) data, genomic data, or environmental data. However, the present disclosure is not limited thereto. The service server (11) may dynamically adjust a customized administration schedule based on the analysis results. The service server (11) may also transmit a warning to a medical professional.

[0169] FIG. 15 is a diagram illustrating an operation of receiving identification information of a drug according to some embodiments of the present disclosure.

[0170] Referring to FIG. 15, a user interface screen (40) displayed on a pharmacist terminal (30) can visually guide the process of receiving identification information of a medicine. The user interface screen (40) can support the pharmacist in easily obtaining identification information by tagging an RFID (Radio-Frequency Identification) tag or NFC (Near Field Communication) tag attached to the medicine to the pharmacist terminal (30). The user interface screen (40) may include a tag notification screen (41) and a scan notification screen (42).

[0171] The tag notification screen (41) may be an interface area that guides the user on how to scan the medicine tag. The tag notification screen (41) may provide intuitive guidance, including a text message such as "Please place the medicine on the back of the mobile phone" and a medicine icon. Following the guidance of the tag notification screen (41), the user may bring the RFID tag attached to the medicine close to a specific area of ​​the pharmacist terminal (30). The pharmacist terminal (30) may initiate communication with the RFID tag and prepare to receive identification information.

[0172] The scan notification screen (42) may be an interface area that displays the progress status while the pharmacist terminal (30) reads identification information from the RFID tag. When the pharmacist terminal (30) successfully recognizes the RFID tag, the scan notification screen (42) may output a visual indicator indicating the progress status along with a message such as "Scanning...". When the scan is completed, the pharmacist terminal (30) can obtain the unique identification information of the first medicine stored in the RFID tag. The obtained identification information may be transmitted to the service server (11) of the drug administration management system (10).

[0173] The service server (11) can receive identification information of the first medicine from the pharmacist terminal (30). The service server (11) can transmit authorization information corresponding to the identification information of the first medicine to the pharmacist terminal (30). The service server (11) can receive personalized medication guidance from the pharmacist terminal (30) that personalizes the authorization information corresponding to the patient's patient profile information. The service server (11) can store the received personalized medication guidance in a patient information database.

[0174] In one embodiment of the present disclosure, personalized medication guidance may include information on the administration schedule of the first drug, precautions for administration, information on side effects, information on other drugs with potential interactions, warnings related to the patient's specific disease, information on allergic reactions, or precautions for pregnant women. However, the present disclosure is not limited thereto.

[0175] The service server (11) can receive identification information of a drug from a patient terminal. The service server (11) can search for the received identification information of the drug in the patient information database. If the searched identification information of the drug is the identification information of the first drug, the service server (11) can generate a customized administration schedule for the patient according to the administration schedule information of the first drug included in the customized medication guidance. The service server (11) can transmit the customized medication guidance and the customized administration schedule to the patient terminal.

[0176] The service server (11) can receive a record of administration of the first drug from the patient terminal. The service server (11) can analyze the administration record and update a customized administration schedule. The service server (11) can transmit administration notification information according to the updated customized administration schedule to the patient terminal.

[0177] In one embodiment of the present disclosure, the pharmacist terminal (30) may be a smartphone, a tablet PC (Personal Computer), or a dedicated terminal with a built-in RFID reader function. When a user places a medicine at the pharmacist terminal (30) in accordance with the instructions on the tag notification screen (41), the pharmacist terminal (30) can activate the tag by transmitting radio waves to the RFID tag through a built-in antenna. The activated RFID tag can transmit stored identification information back to the pharmacist terminal (30). The pharmacist terminal (30) can convert the received information into digital data and transmit it to the service server (11). This process can minimize human error that may occur during the process of a pharmacist manually entering medicine information. In addition, this process can improve the speed and accuracy of the medicine registration procedure.

[0178] FIG. 16 is a flowchart for explaining the operation of obtaining authorization information according to some embodiments of the present disclosure, described with reference to FIG. 13.

[0179] Referring to FIGS. 13 and FIGS. 16, the operation of obtaining permission information can be performed by a service server (11).

[0180] In step 410, the service server (11) may obtain authorization information by searching a drug information database. The service server (11) may use the identification information of the first drug received from the pharmacist terminal (30) as a query. The service server (11) may search an internal database (12) or an external authorized drug information database using the query. The authorization information obtained through the search may include comprehensive data related to the first drug. For example, the authorization information may include information on the active ingredient of the drug, efficacy and effects, dosage and administration, possible side effects, interactions with other drugs, storage methods, precautions for administration, contraindications for specific patient groups, information regarding pregnant and breastfeeding women, pharmacokinetic characteristics, drug interaction mechanisms, and non-clinical test data. However, the present disclosure is not limited thereto.

[0181] In step 420, the service server (11) can transmit a drug information template to the pharmacist terminal (30). The service server (11) can automatically input the authorization information obtained in step 410 into a drug information template of a predefined structure. The drug information template can be configured to improve the readability of the information and to ensure that the pharmacist does not omit essential information. The drug information template with the authorization information entered can be transmitted to the pharmacist terminal (30) via a security protocol.

[0182] In one embodiment of the present disclosure, the step of transmitting authorization information may include the step of obtaining authorization information by searching for identification information of a first drug in a drug information database, and the step of inputting authorization information into a drug information template and transmitting the drug information template containing the authorization information to a pharmacist terminal (30). The service server (11) may query the database using a product code, ingredient code, or standard code corresponding to the identification information of the first drug. As a result of querying the database, the service server (11) may extract detailed information including authorization information, insurance code, dosage form, manufacturer information, etc., for the first drug. The drug information template may be divided into items such as dosage instructions, major side effects, interacting drugs, storage conditions, etc. The service server (11) may complete the template by mapping authorization information corresponding to each item. The pharmacist terminal (30) may display the received template on a user interface screen to support the pharmacist in checking and modifying the content.

[0183] FIG. 17 is a drawing illustrating an example of a drug information template according to some embodiments of the present disclosure.

[0184] Referring to FIG. 17, the drug information template (60) may include authorization information (61). The drug information template (60) may be in the form of a user interface that visually provides drug-related information received from the service server (11) to a pharmacist or patient. The drug information template (60) may be displayed on a display device of a pharmacist terminal (30) or a patient terminal (20). The drug information template (60) can improve readability for the user by systematically organizing information such as the name, usage, dosage, efficacy, and precautions of the drug.

[0185] The service server (11) can input the authorization information (61) obtained from the drug information database into the drug information template (60). The service server (11) can transmit the drug information template (60) with the authorization information (61) input to the pharmacist terminal (30). The pharmacist can check the basic information of the drug through the drug information template (60) displayed on the pharmacist terminal (30), and create customized medication instructions by modifying or adding information according to the patient's characteristics. For example, the pharmacist can adjust the dosage or precautions for taking the drug by considering the patient's age, underlying diseases, allergic reactions, etc., and directly input the relevant content into the drug information template (60).

[0186] In one embodiment of the present disclosure, the drug information template (60) may include a function to activate a separate input window for entering patient profile information. When a pharmacist selects a specific button on the drug information template (60), a user interface for entering or modifying the patient's personal information may be provided in the form of a popup. Through this, the pharmacist can more efficiently create and manage customized medication guidance for each patient.

[0187] Authorization information (61) may refer to specific drug-related data displayed within the drug information template (60). Authorization information (61) may consist of multiple items such as drug description, dosage, number of doses, and detailed description. Each item may contain essential information necessary for the user to take the drug safely and accurately. For example, the drug description item may provide an overview of the active ingredients and efficacy of the drug, and the dosage and number of doses item may specify the single dose and daily administration frequency.

[0188] The service server (11) can obtain authorization information (61) by searching for identification information of the first drug in the drug information database. In one embodiment of the present disclosure, the identification information of the first drug may be the name of the drug, ingredient code, product code, barcode, QR code, Radio-Frequency Identification (RFID) tag information, or Near Field Communication (NFC) tag information. However, the present disclosure is not limited thereto. The service server (11) can input the obtained authorization information (61) into a drug information template (60). The service server (11) can transmit the drug information template (60) into which the authorization information (61) has been input to a pharmacist terminal (30). Through this, the pharmacist can omit the process of manually inputting drug information and ensure the accuracy of the information.

[0189] FIG. 18 is a detailed flowchart for explaining the operation of a drug administration management method according to some embodiments of the present disclosure, described with reference to FIG. 13.

[0190] Referring to FIGS. 13 to 18, the operation of the service server (11) after receiving identification information of the medicine from the patient terminal (20) can be described.

[0191] In one embodiment of the present disclosure, the step of searching for identification information of a drug in a patient information database may include: determining the drug as a preferred drug when the identification information of the drug is received more than a reference number of times; transmitting notification information recommending the registration of the preferred drug to a patient terminal (20); and updating the patient information database in response to receiving feedback information from the patient terminal (20) regarding the notification information.

[0192] In step S810, the service server (11) can determine that a drug is a preferred drug. The service server (11) can determine whether the identification information of a specific drug received from the patient terminal (20) exceeds a preset threshold number. For example, the service server (11) can analyze records of the patient continuously taking a drug of the same ingredient. The threshold number may be set variably depending on the type of drug, the prescription period, or the characteristics of the disease.

[0193] In step S811, the service server (11) may transmit notification information. If a specific medicine is determined to be a preferred medicine, the service server (11) may transmit notification information recommending the registration of the medicine to the patient terminal (20). The notification information may include content suggesting that the medicine the patient is taking is ineffective in improving symptoms or that there is a possibility of other underlying diseases. The notification information may include a message recommending consultation with a medical professional, such as a doctor or pharmacist. The service server (11) may induce a re-evaluation of the patient's health condition through the consultation recommendation message.

[0194] In step S812, the service server (11) can update the patient information database. The service server (11) can receive feedback information regarding notification information from the patient terminal (20). The feedback information may include consent or refusal regarding the registration of preferred medications. Based on the received feedback information, the service server (11) can update the patient profile within the patient information database. For example, if the patient consents to the registration of preferred medications, the service server (11) can add the relevant medication information to the patient's personal medication list to improve the convenience of management.

[0195] In one embodiment of the present disclosure, the feedback information may include consent, refusal, or withholding of the registration of a preferred drug. The service server (11) may receive feedback information including a refusal from the patient terminal (20). In response to the refusal, the service server (11) may update the patient information database to stop recommending the registration of a preferred drug for the same drug for a certain period. Alternatively, the service server (11) may send an additional message to the patient terminal (20) inquiring about the reason for the refusal. For example, the reason for refusal may be the occurrence of side effects, insufficient efficacy, cost issues, preference for other drugs, results of consultation with a doctor or pharmacist, poor medication adherence, or personal beliefs. However, the present disclosure is not limited thereto.

[0196] FIG. 19 is a detailed flowchart for explaining the operation of a drug administration management method according to some embodiments of the present disclosure, described with reference to FIG. 13.

[0197] Referring to FIGS. 13 and 19, the step of searching for identification information of a drug in the patient information database (12) can be performed by a service server (11).

[0198] In step S820, the service server (11) can receive text data. For example, a patient can convey their symptoms and health status by voice through a patient terminal (20). The patient terminal (20) can convert the patient's voice into text data using Speech-to-Text (STT) technology. The patient terminal (20) can transmit the converted text data to the service server (11).

[0199] In step S821, the service server (11) can obtain identification information for the second drug. The service server (11) can search for the received text data in the patient information database (12). During the search process, the service server (11) can analyze the similarity between the text data and the previously stored symptom information. The service server (11) can obtain identification information for the second drug in which the similarity is greater than or equal to a pre-set threshold as a result of the analysis.

[0200] In step S822, the service server (11) can transmit information regarding the name of the medicine corresponding to the identification information of the second medicine. The service server (11) can generate information including the name of the medicine mapped to the acquired identification information of the second medicine. The service server (11) can transmit the generated information to the patient terminal (20). Through this, the patient can receive information about the medicine previously taken without having to directly mention the name of the medicine.

[0201] In one embodiment of the present disclosure, the step of searching for identification information of a drug in a patient information database (12) may include receiving text data regarding the patient's symptoms and health status from a patient terminal (20). Additionally, the step of searching for identification information of a drug in a patient information database (12) may include searching for text data in the patient information database (12) and obtaining identification information of a second drug in which the similarity between the text data and the symptom information is greater than or equal to a threshold value. Furthermore, the step of searching for identification information of a drug in a patient information database (12) may include transmitting information regarding the name of the drug corresponding to the identification information of the second drug to the patient terminal (20).

[0202] FIG. 20 is a detailed flowchart for explaining the operation of a drug administration management method according to some embodiments of the present disclosure, described with reference to FIG. 13.

[0203] Referring to FIGS. 13 to 20, in step S830, the service server (11) can receive text data and store it in a patient information database. The service server (11) can receive text data regarding the patient's symptoms and health status from the patient terminal (20). The patient terminal (20) can convert the patient's voice input into text data and transmit it to the service server (11). The service server (11) can store the received text data in the patient information database to continuously manage the patient's health status.

[0204] In step S831, the service server (11) can obtain authorization information corresponding to the identification information of the second drug. The service server (11) can search for stored text data in the patient information database. As a result of the search, the service server (11) may not find any drugs with a similarity to the text data that is greater than or equal to a threshold value. In this case, the service server (11) can input the text data into a pre-trained artificial intelligence model. The pre-trained artificial intelligence model can obtain authorization information corresponding to the identification information of the second drug that has the highest similarity to the text data and symptom information.

[0205] In step S832, the service server (11) can transmit authorization information corresponding to the identification information of the second drug. The service server (11) can transmit the acquired authorization information to the patient terminal (20). The patient terminal (20) can display the received authorization information through a user interface so that the patient can check the drug information.

[0206] In one embodiment of the present disclosure, a pre-trained artificial intelligence model can recommend a drug by analyzing symptom and health status information included in text data. For example, the pre-trained artificial intelligence model may be a Natural Language Processing (NLP) model, a Transformer-based model, a Recurrent Neural Network (RNN) model, a Convolutional Neural Network (CNN) model, a Deep Neural Network (DNN) model, a Support Vector Machine (SVM) model, or a Random Forest model. However, the present disclosure is not limited thereto. The pre-trained artificial intelligence model can determine the drug with the highest correlation as a second drug by comparing the patient's text data with symptom information from a drug database.

[0207] FIG. 21 is a detailed flowchart for explaining the operation of a drug administration management method according to some embodiments of the present disclosure, described with reference to FIG. 13.

[0208] Referring to FIG. 21 together with FIG. 13 to 20, the steps illustrated in FIG. 21 can be performed by a service server (11).

[0209] In step S1200, the service server (11) can calculate the weight difference. The service server (11) can compare the weight at the time the smart pill container in which the first medicine is stored is opened with the weight at the time the smart pill container is closed. The smart pill container can measure weight in real time by including a weight sensor inside. The service server (11) can receive weight data from the smart pill container via a communication network.

[0210] In step S1210, the service server (11) can determine the number of tablets administered. If the weight difference calculated in step S1200 is greater than or equal to a preset threshold, the service server (11) can compare the weight difference with the unit dosage of the first medicine. Based on the comparison result, the service server (11) can calculate the actual number of tablets administered. For example, if the unit dosage of one tablet of the first medicine is 0.5 grams and the weight difference is calculated to be 1.0 grams, the service server (11) can determine that two tablets of the medicine have been administered.

[0211] In one embodiment of the present disclosure, a preset threshold may be set to filter out weight changes in cases where the medicine is not actually administered. For example, the preset threshold may be set to a value greater than the value of minute weight changes that may occur due to simple repositioning of the smart medicine container, external impact, measurement error, humidity change, temperature change, atmospheric pressure change, or vibration, and less than the weight of the minimum unit dose of the first medicine. However, the present disclosure is not limited thereto.

[0212] In step S1230, the service server (11) can map the time of administration completion and the number of tablets administered and store them in the administration record. The service server (11) can determine the time when the smart pill container is closed as the time of administration completion of the first medicine. The service server (11) can map the determined time of administration completion and the number of tablets administered determined in step S1210 to each other. The service server (11) can create and manage an accurate administration record by storing the mapped information in a patient information database.

[0213] In one embodiment of the present disclosure, the step of receiving a administration record may be performed based on a change in weight of a smart pill container in which a first medicine is stored. A service server (11) may compare the weight of the smart pill container at the time the smart pill container in which the first medicine is stored is opened with the weight of the smart pill container at the time the smart pill container is closed. The service server (11) may calculate the weight difference through comparison. If the weight difference is greater than or equal to a pre-set threshold, the service server (11) may determine the number of tablets administered. The service server (11) may determine the number of tablets administered by comparing the weight difference with the unit dosage of the first medicine. The service server (11) may determine the time of closing the smart pill container as the time of completion of administration of the first medicine. The service server (11) may map the time of completion of administration to the number of tablets administered. The service server (11) may store the mapped information in the administration record.

[0214] FIG. 22 is a detailed flowchart for explaining the operation of a drug administration management method according to some embodiments of the present disclosure, described with reference to FIG. 13.

[0215] With reference to FIG. 22, together with FIG. 12 to 21, the step (S1300) of updating a customized administration schedule can be performed by a service server (11).

[0216] In step S1310, the service server (11) may compare at least one of the patient's sleep pattern data, meal time data, activity data, and location information data with the administration record. The service server (11) may collect data related to the patient's lifestyle habits from the patient terminal (20) or a wearable device linked to the patient. For example, sleep pattern data may be information including the patient's wake-up time, bedtime, total sleep time, REM sleep time, deep sleep time, number of awakenings during sleep, sleep efficiency score, etc. However, the present disclosure is not limited thereto. For example, meal time data may be information including the patient's breakfast time, lunch time, dinner time, snack time, meal duration, meal menu, calorie intake, etc. However, the present disclosure is not limited thereto. For example, activity data may be information including the patient's daily step count, distance traveled, type of exercise, exercise time, exercise intensity, calories burned, heart rate change amount, etc. However, the present disclosure is not limited thereto. For example, location information data may include information such as the patient's current location, home location, workplace location, radius of main activity, time spent at a specific location, travel route, and type of place visited. However, the present disclosure is not limited thereto. The service server (11) can analyze the correlation between a specific lifestyle pattern and administration compliance by comparing the collected data with the patient's administration records.

[0217] In step S1311, the service server (11) can derive a first time zone. Based on the comparative analysis results of step S1310, the service server (11) can identify a time zone where the probability of no omission of administration of the first drug occurs is greater than or equal to a preset threshold. For example, the service server (11) can discover a pattern where the administration compliance is 95% or higher when the patient is at home within 30 minutes after dinner. In this case, the service server (11) can set the 'time spent at home within 30 minutes after dinner' as the first time zone with a low probability of omission of administration. The first time zone may consist of multiple candidate time zones optimized for the patient's lifestyle rhythm.

[0218] In step S1312, the service server (11) can adjust the administration notification time to a second time zone. The service server (11) can determine the optimal time as the second time zone that satisfies both the derived first time zone and the recommended administration interval of the first drug. For example, if the first drug must be administered at 12-hour intervals and the morning administration is completed at 8:00 AM, the next administration may need to be done at 8:00 PM. The service server (11) can determine that the period between 7:00 PM and 9:00 PM corresponds to the first time zone based on the analyzed patient's lifestyle pattern. The service server (11) can set 8:00 PM, which satisfies both the recommended administration interval and the first time zone, as the second time zone and adjust the notification time of the customized administration schedule. Through this, the service server (11) can flexibly respond to changes in the patient's lifestyle pattern and continuously increase administration compliance.

[0219] In one embodiment of the present disclosure, the step of updating a customized administration schedule may include comparing at least one of the patient's sleep pattern data, meal time data, activity data, and location information data with the administration record. As a result of the comparison, the method may include deriving a first time period in which the probability of no missed administration of the first drug occurring is greater than or equal to a preset threshold. The method may include adjusting the administration notification time included in the customized administration schedule to a second time period in which the first time period and the recommended administration interval of the first drug are satisfied.

[0220] FIG. 23 is a detailed flowchart for explaining the operation of a drug administration management method according to some embodiments of the present disclosure, described with reference to FIG. 13.

[0221] With reference to FIG. 23, together with FIG. 13 to 22, the detailed operation of the step (S1300) of updating the customized administration schedule can be performed by the service server (11).

[0222] In step S1320, the service server (11) can obtain the frequency of missed administration. The service server (11) can analyze the administration records stored in the patient information database. Through the analysis, the service server (11) can calculate the number of times the administration of the first drug was missed. For example, the service server (11) can compare the scheduled administration time set in the customized administration schedule with the actual administration completion record. Through the comparison, the service server (11) can calculate the frequency of missed administration during a specific period.

[0223] In step S1321, the service server (11) can obtain a biosignal change rate. The service server (11) can receive the patient's biosignal data from the patient terminal (20) or a wearable device linked to the patient terminal (20). The service server (11) can calculate the change rate of the received biosignal data. For example, the biosignal data may be heart rate data, blood pressure data, blood glucose data, body temperature data, oxygen saturation data, activity level data, and sleep pattern data. However, the present disclosure is not limited thereto. The service server (11) can calculate the change rate by comparing the biosignal data at a reference point in time with the biosignal data at the current point in time.

[0224] In step S1322, the service server (11) can identify abnormal signs. The service server (11) can determine whether the frequency of missed administration exceeds a preset threshold. Additionally, the service server (11) can determine whether the rate of change in the biosignal exceeds a preset threshold range. If both conditions are met, the service server (11) can identify that an abnormal sign has occurred in the patient.

[0225] In step S1323, the service server (11) may store data regarding abnormal signs in a patient information database. The service server (11) may record information related to the identified abnormal signs in the database. The data regarding abnormal signs may include the time at which the abnormal signs were identified, the frequency of missed administration at that time, and biosignal data values ​​exceeding a reference range. The stored data may be used in the future for monitoring the patient's health status or for diagnosis by medical professionals.

[0226] In one embodiment of the present disclosure, the step of updating a customized administration schedule may include obtaining the frequency of missed administration of a first drug from an administration record, obtaining the rate of change in the patient's biosignal using the patient's biosignal data, identifying an abnormal sign when the frequency of missed administration exceeds a preset threshold and the rate of change in the biosignal exceeds a preset threshold range, and storing data regarding the abnormal sign in a patient information database.

[0227] FIG. 24 is a detailed flowchart for explaining the operation of a drug administration management method according to some embodiments of the present disclosure, described with reference to FIG. 13.

[0228] Referring to FIGS. 12 to 24, the step (S1300) of updating the customized administration schedule can be performed by the service server (11).

[0229] In step S1330, the service server (11) can receive trigger data. The service server (11) can receive trigger data from the patient terminal (20) that triggers the start time for administering the first medicine. The trigger data can be used as reference information to flexibly adjust the administration schedule according to changes in the patient's daily life patterns. The service server (11) can detect the patient's lifestyle events. The service server (11) can dynamically set the starting point of the administration schedule through the detected lifestyle events.

[0230] In one embodiment of the present disclosure, the trigger data may include lifestyle events calculated by analyzing data obtained from a patient's smart device. For example, the trigger data may be lifestyle events calculated by analyzing at least one of image data, message data, activity data, sleep pattern data, heart rate data, weight data, and blood pressure data. However, the present disclosure is not limited thereto. For example, the service server (11) may recognize the time when the patient wakes up in the morning and uses the smartphone for the first time as the wake-up time. The service server (11) may utilize the recognized time as trigger data to set the first administration start time.

[0231] In step S1331, the service server (11) can determine the scheduled administration time. The service server (11) can apply the recommended administration interval of the first drug based on the received trigger data. The service server (11) can sequentially calculate the next administration time. The service server (11) can determine the scheduled administration time based on the calculated time. The service server (11) can generate a flexible administration schedule tailored to the patient's lifestyle pattern.

[0232] In one embodiment of the present disclosure, the service server (11) may apply a recommended administration interval for the first drug based on the time when trigger data occurs. The service server (11) may determine a scheduled administration time based on the applied administration interval. For example, it may be assumed that the first drug is to be administered at 8-hour intervals and that trigger data is received at 7:00 AM. The service server (11) may determine the scheduled administration times as 7:00 AM, 3:00 PM, and 11:00 PM. The service server (11) may provide administration management that is more aligned with the patient's actual life cycle than a method of providing notifications at fixed times.

[0233] In step S1332, the service server (11) can generate an administration notification schedule. The service server (11) can generate a schedule for transmitting administration notification information to the patient terminal (20) in accordance with the determined scheduled administration time. The generated administration notification schedule can be registered in the scheduling module of the service server (11). The scheduling module can automatically perform the notification transmission operation at the specified time.

[0234] In one embodiment of the present disclosure, the service server (11) may generate an administration notification schedule that transmits administration notification information of a first drug to a patient terminal (20) at a first time included in the scheduled administration time. The administration notification schedule may be configured to send a notification at each scheduled administration time. The administration notification schedule may include a function to send a preliminary notification a few minutes before the scheduled administration time according to the patient's settings.

[0235] FIG. 25 is a drawing illustrating an example of a user interface screen displayed on a patient terminal according to some embodiments of the present disclosure.

[0236] Referring to FIG. 25, an example of a user interface screen displayed on a patient terminal (20) may be illustrated. The patient terminal (20) may provide the patient with a user interface including an administration schedule (140), an administration completion schedule (141), and a settings screen (142).

[0237] The administration schedule (140) may be a user interface screen that visually provides the patient with a customized administration schedule generated by the service server (11). Through the administration schedule (140), the patient can intuitively check information such as the type of medication to be administered on a specific date and the time of administration. The administration schedule (140) can improve medication adherence by supporting the patient in easily recognizing and managing their medication plan.

[0238] The service server (11) can obtain authorization information by searching for the identification information of the first drug in the drug information database. The service server (11) can input the obtained authorization information into a drug information template. The service server (11) can transmit the drug information template with the authorization information input to the pharmacist terminal (30).

[0239] In one embodiment of the present disclosure, the identification information of the first drug may be the name of the drug, an ingredient code, a standard code, manufacturer information, a product number, barcode information, or QR code (Quick Response code) information. However, the present disclosure is not limited thereto.

[0240] The service server (11) can generate a customized administration schedule by combining the customized medication guidance received from the pharmacist terminal (30) and the patient's lifestyle pattern data. The patient terminal (20) can receive the customized administration schedule from the service server (11) and display it on the screen in the form of an administration schedule (140). After completing administration for each medication item displayed in the administration schedule (140), the patient can select a completion button to create an administration record.

[0241] In one embodiment of the present disclosure, the administration schedule (140) may include a voice output function for users who have difficulty accessing visual information. For example, when a patient activates the 'listen to schedule voice' function, the patient terminal (20) may provide voice guidance for the entire administration schedule for the corresponding date using Text-to-Speech (TTS) technology. Additionally, the administration schedule (140) may enable integrated drug management by providing a function to add over-the-counter medications or nutritional supplements that the patient takes at will.

[0242] The administration completion schedule (141) may be a user interface area that displays the history of medications that a patient has completed administering. The administration completion schedule (141) may record the name of the medication that has been administered and the time information of the actual administration. Through this, the patient can clearly track their medication history and easily check whether any administrations have been missed.

[0243] When a patient records the completion of administration in the administration schedule (140), the information can be automatically added to the administration completion schedule (141). The information recorded in the administration completion schedule (141) may constitute part of the administration record transmitted from the patient terminal (20) to the service server (11). The service server (11) can analyze this administration record to calculate the administration schedule compliance rate or use it to dynamically update the customized administration schedule.

[0244] The settings screen (142) may be a user interface provided to allow the patient to adjust various functions of the application to suit their convenience. Through the settings screen (142), the patient can personalize various user experience elements, including the method of delivering administration notification information. The settings screen (142) may provide accessibility enhancement functions, such as changing voice speed, font size, and language, particularly for users who have difficulty accessing information.

[0245] The patient can adjust the speed at which administration notifications or medication information are provided via voice through the 'Voice Speed ​​Setting' item on the settings screen (142). Additionally, readability can be ensured by changing the size of all text displayed on the screen to suit the patient's eyesight through the 'Font Size Setting' item. The 'Language Setting' item supports a multilingual environment, allowing the user to receive information in the language most comfortable for them.

[0246] In one embodiment of the present disclosure, the setting screen (142) may additionally include a function to set details of the notification. For example, the patient may distinguish the medication by specifying a special notification sound for a specific medication or by setting a different vibration pattern. Additionally, the patient may use a function to set their sleep time or the time of an important meeting as a 'do not disturb time' so that the administration notification does not sound during that time.

[0247] Hereinafter, with reference to FIG. 26, an exemplary computing device (1000) capable of implementing a system according to some embodiments of the present disclosure will be described.

[0248] FIG. 26 illustrates an exemplary computing device capable of implementing systems according to some embodiments of the present disclosure. The computing device (1000) of FIG. 26 may include one or more processors (1100), a system bus (1600), a communication interface (1200), a memory (1400) for loading a computer program (1500) executed by the processor (1100), and a storage (1300) for storing the computer program (1500). For example, the computing device of FIG. 22 may be a service server (11) described with reference to FIG. 12.

[0249] The processor (1100) controls the overall operation of each component of the computing device (1000). The processor (1100) may perform operations on at least one application or program for executing the method / operation according to various embodiments of the present disclosure. The memory (1400) stores various data, instructions and / or information. The memory (1400) may load one or more computer programs (1500) from the storage (1300) to execute the method / operation according to various embodiments of the present disclosure. The storage (1300) may store one or more computer programs (1500) non-temporarily. The computer program (1500) may include one or more instructions in which the method / operation according to various embodiments of the present disclosure is implemented. When a computer program (1500) is loaded into memory (1400), the processor (1100) can perform methods / operations according to various embodiments of the present disclosure by executing one or more of the instructions.

[0250] The computer program (1500) may be a program for managing drug administration methods.

[0251] In some embodiments, the computer program (1500) may include instructions for performing operations such as receiving identification information of a first drug from a pharmacist terminal, transmitting authorization information corresponding to the identification information of the first drug to the pharmacist terminal, receiving personalized medication instructions from the pharmacist terminal that personalize the authorization information corresponding to the patient's patient profile information and storing the personalized medication instructions in a patient information database, receiving identification information of a drug from a patient terminal and searching for the identification information of the drug in the patient information database, generating a personalized administration schedule for the patient according to the administration schedule information of the first drug included in the personalized medication instructions when the searched identification information of the drug is the identification information of the first drug, transmitting the personalized medication instructions and the personalized administration schedule to the patient terminal, receiving an administration record of the first drug from the patient terminal, analyzing the administration record to update the personalized administration schedule, and transmitting administration notification information according to the updated personalized administration schedule to the patient terminal.

[0252] In some embodiments, the computing system described with reference to FIG. 26 may be configured using one or more physical servers included in a server farm based on cloud technology, such as a virtual machine. In this case, at least some of the components shown in FIG. 26, such as the processor (1100), memory (1400), and storage (1300), may be virtual hardware, and the communication interface (1200) may also be configured as a virtualized networking element, such as a virtual switch.

[0253]

[0254] The features, structures, effects, etc. described in the embodiments above are included in at least one embodiment of the present invention and are not necessarily limited to only one embodiment. Furthermore, the features, structures, effects, etc. exemplified in each embodiment may be combined or modified and implemented in other embodiments by a person skilled in the art to which the embodiments belong. Accordingly, details regarding such combinations and modifications should be interpreted as being included within the scope of the present invention.

[0255] Furthermore, although the embodiments have been described above, this is merely illustrative and does not limit the invention. Those skilled in the art will understand that various modifications and applications not exemplified above are possible within the scope of the essential characteristics of the embodiments. In other words, each component specifically shown in the embodiments may be modified and implemented. Differences related to such modifications and applications should be interpreted as being included within the scope of the invention as defined in the appended claims.

Claims

1. In a method performed by a drug administration management system, A step of receiving identification information of a first medicine from a pharmacist terminal; A step of transmitting authorization information corresponding to the identification information of the first medicine to the pharmacist terminal; A step of receiving personalized medication guidance from the pharmacist terminal that personalizes the authorization information in correspondence with the patient's patient profile information, and storing the personalized medication guidance in a patient information database; A step of receiving identification information of a drug from a patient terminal and searching for the identification information of the drug in an internal database; If the identification information of the searched drug is the identification information of the first drug, a step of generating a customized administration schedule for the patient according to the administration schedule information of the first drug included in the customized medication guidance; A step of transmitting the customized medication guidance and customized administration schedule to the patient terminal; A step of receiving a record of administration of the first drug from the patient terminal; A step of updating the customized administration schedule by analyzing the above administration records; and The method includes the step of transmitting administration notification information according to the updated customized administration schedule to the patient terminal. Methods for managing drug administration.

2. In Paragraph 1, The step of transmitting the above permission information is, A step of obtaining the approval information by searching the identification information of the first drug in a drug information database; and A method comprising the step of inputting the above-mentioned approval information into a drug information template and transmitting the drug information template with the inputted approval information to the pharmacist terminal. Methods for managing drug administration.

3. In Paragraph 1, The step of searching for the identification information of the above-mentioned medicine in the above-mentioned patient information database is, A step of determining the above-mentioned drug as a preferred drug when the identification information of the above-mentioned drug is received more than a standard number of times; A step of transmitting notification information recommending the registration of the preferred medicine to the patient terminal; and A step comprising updating the patient information database in response to receiving feedback information from the patient terminal regarding the above notification information, Methods for managing drug administration.

4. In Paragraph 1, The step of searching for the identification information of the above-mentioned medicine in the above-mentioned patient information database is, A step of receiving text data regarding the patient's symptoms and health status from the patient terminal; A step of searching the above text data in the above patient information database and obtaining identification information of a second drug in which the similarity between the above text data and symptom information is greater than or equal to a threshold; and A method comprising the step of transmitting information regarding the name of a drug corresponding to the identification information of the second drug to the patient terminal. Methods for managing drug administration.

5. In Paragraph 1, The step of searching for the identification information of the above-mentioned medicine in the above-mentioned patient information database is, A step of receiving text data regarding the patient's symptoms and health status from the patient terminal and storing it in the patient information database; A step of searching the above text data in the patient information database, and if no drug with a similarity to the above text data above a threshold is found, inputting the above text data into a pre-trained artificial intelligence model and obtaining approval information corresponding to the identification information of a second drug with the highest similarity to the above text data and symptom information; and A step comprising transmitting authorization information corresponding to the identification information of the second drug to the patient terminal. Methods for managing drug administration.

6. In Paragraph 1, The step of receiving the above administration record is, A step comprising determining the time of completion of administration of the first drug using information on the time of receiving identification information of the drug from the patient terminal or information on the time of opening and closing of the smart pill container in which the first drug is stored. Methods for managing drug administration.

7. In Paragraph 1, The step of receiving the above administration record is, A step of calculating the weight difference by comparing the weight of the smart pill container at the time when the smart pill container in which the first medicine is stored is opened with the weight of the smart pill container at the time when the smart pill container is closed; If the weight difference is greater than or equal to a preset threshold, a step of determining the number of tablets administered by comparing the weight difference with the unit dosage of the first drug; and The method comprises the step of determining the closing time of the smart pill dispenser as the completion time of administration of the first drug, mapping the completion time of administration to the number of administered tablets, and storing the result in the administration record. Methods for managing drug administration.

8. In Paragraph 1, The step of updating the customized administration schedule above is, If the administration schedule compliance rate included in the administration record is greater than or equal to a preset threshold, the method comprises the step of transmitting administration notification information according to the customized administration schedule to the patient terminal and transmitting positive feedback information including statistical information regarding the administration schedule compliance rate. Methods for managing drug administration.

9. In Paragraph 1, The step of updating the customized administration schedule above is, A step of comparing at least one of the patient’s sleep pattern data, meal time data, activity data, and location information data with the administration record; A step of deriving a first time period in which, as a result of the above comparison, the probability that the omission of administration of the first drug will not occur is greater than or equal to a preset threshold; and A step comprising adjusting the administration notification time included in the above customized administration schedule to a second time period in which the first time period and the recommended administration interval of the first drug are satisfied. Methods for managing drug administration.

10. In Paragraph 1, The step of updating the customized administration schedule above is, A step of obtaining the frequency of missed administration of the first drug from the above administration record; A step of obtaining the rate of change in the patient's biosignal using the patient's biosignal data; A step of identifying as an abnormal sign when the above-mentioned frequency of missed administration exceeds a preset threshold and the above-mentioned rate of change in biological signals exceeds a preset threshold range; and A step comprising storing data regarding the above abnormal signs in a patient information database, Methods for managing drug administration.

11. In Paragraph 1, The step of updating the customized administration schedule above is, The method includes the step of transmitting administration error notification information to the patient terminal when, as a result of analyzing the administration record, the first drug is administered in excess of the recommended dosage within the scheduled administration interval. Methods for managing drug administration.

12. In Paragraph 1, The step of updating the customized administration schedule above is, If there is no record of completion of administration of the first drug until the scheduled administration time included in the customized administration schedule has elapsed, the method includes the step of transmitting administration error notification information to the patient terminal. Methods for managing drug administration.

13. In Paragraph 1, The step of updating the customized administration schedule above is, A step of receiving trigger data from the patient terminal that triggers the start time of administration of the first drug; Based on the above trigger data, a step of determining a scheduled administration time by applying the recommended administration interval of the first drug; and A method comprising the step of generating an administration notification schedule for transmitting administration notification information of the first drug to the patient terminal at a first time point included in the scheduled administration time, Methods for managing drug administration.

14. In Paragraph 13, The above trigger data is, A lifestyle event calculated by analyzing at least one of image data, message data, activity data, sleep pattern data, heart rate data, weight data, and blood pressure data acquired from the patient's smart device, Methods for managing drug administration.

15. Communication interface; Memory where a computer program is loaded; and The computer program described above includes one or more processors on which it is executed, The above computer program is, The operation of receiving identification information of a first medicine from a pharmacist terminal; The operation of transmitting authorization information corresponding to the identification information of the first medicine to the pharmacist terminal; The operation of receiving personalized medication guidance from the pharmacist terminal that personalizes the authorization information in correspondence with the patient's patient profile information, and storing the personalized medication guidance in a patient information database; The operation of receiving identification information of a drug from a patient terminal and searching for the identification information of the drug in the internal database; If the identification information of the searched drug is the identification information of the first drug, the operation of generating a customized administration schedule for the patient according to the administration schedule information of the first drug included in the customized medication guidance; The operation of transmitting the customized medication guidance and customized administration schedule to the patient terminal; The operation of receiving a record of administration of the first drug from the patient terminal; The operation of analyzing the above administration record to update the above customized administration schedule; and Instructions including the operation of transmitting administration notification information according to the updated customized administration schedule to the patient terminal, Drug administration management system.

Images