Patient information management system

Abstract

Disclosed is a patient information management system comprising: a transceiver; a memory storing one or more instructions; and at least one processor. The at least one processor executes the one or more instructions to cause the patient information management system to: receive electronic medical record (EHR) information from a pre-operating EHR system; receive patient information including at least one among a prescription of a patient and a medical record of the patient from a user terminal through a security session formed through at least one authentication procedure; and transmit output information to an electronic device of a medical staff side so as to output, by means of a user interface, the received patient information and the EHR information received from the EHR system.

Description

Patient Information Management System

[0001] The present disclosure relates to a patient information management system.

[0002] As active patient health management becomes more widespread, there is a growing demand for the clinical use of medical records accumulated in patient terminals, prescription images, and real-time biosignal data measured through wearable devices such as smartwatches. However, in actual clinical settings, there are cases where it is difficult to immediately incorporate external data into clinical decision-making due to complex connection procedures between patient devices and hospital systems, which reduce usability, or compatibility issues with Electronic Health Record (EHR) systems that differ from hospital to hospital.

[0003] Therefore, there is a need to develop platform technology in the form of middleware that provides various connection interfaces capable of rapidly and securely transmitting integrated medical data collected in advance of a visit at the time of treatment, and that can visualize data to assist medical staff in making decisions regardless of the hospital's existing system environment.

[0004] The main problem that the present disclosure aims to solve is to provide a system that forms a secure connection between a patient's user terminal (including wearable devices such as smartwatches) visiting the medical site and a medical staff's electronic device in an intuitive and rapid manner (e.g., proximity tagging, AR eye tracking, etc.), and integrates and safely transmits various medical data distributed on the patient's side.

[0005] Furthermore, another problem that this disclosure aims to solve is to provide a universal middleware platform that supports medical staff in easily utilizing patient information received from external sources by visualizing it in the form of independent pop-ups or layers on the EHR screen, without modifying existing Electronic Medical Record (EHR) systems that differ from one medical institution to another or without complex API integration.

[0006] The technical problems that this embodiment aims to solve are not limited to the technical problems described above, and other technical problems can be inferred from the following embodiments.

[0007] A patient information management system according to one embodiment includes a transceiver, a memory storing one or more instructions, and at least one processor, wherein the at least one processor executes one or more instructions to enable the patient information management system to receive EHR information from an existing electronic medical record (EHR) system, receive patient information including at least one of a patient's prescription and a patient's medical record from a user terminal through a secure session formed through at least one authentication procedure, and transmit output information to an electronic device on the medical staff side to output the received patient information and the EHR information received from the electronic medical record system through a user interface.

[0008] A patient information management system according to one embodiment forms a secure session based on user input received from a user terminal through a transceiver, and the secure session can be maintained for a preset period.

[0009] A user terminal according to one embodiment includes a guardian terminal used by a patient's guardian, and a patient information management system receives authentication information from the guardian terminal and determines whether the authentication is valid based on the authentication information, thereby receiving patient information stored in the guardian terminal through a secure session formed with the patient information management system.

[0010] An electronic device according to one embodiment may include an object that generates at least one of a layer and a pop-up window on a user interface of the electronic device to output patient information included in received output information, and the user interface may include an object that provides a function to transfer patient information displayed on the user interface to an input field of an electronic medical record system.

[0011] A user terminal according to one embodiment provides a pre-examination function for a patient through an interactive user interface, and can include the examination summary data generated through the pre-examination function in the patient information and transmit it to a patient information management system.

[0012] A patient information management system according to one embodiment can transmit output information to an electronic device, including at least one of verification information regarding a patient's prescription and processing information regarding a patient's medical record, after the formation of a secure session.

[0013] Patient information according to one embodiment includes a patient's medical records received through authentication from an external institution server and biosignal data collected from a wearable device linked to a user terminal, and the biosignal data may include at least one of the patient's electrocardiogram (ECG), heart rate, oxygen saturation, blood pressure, blood sugar, body temperature, sleep pattern, and activity data.

[0014] At least one processor according to one embodiment determines whether a wearable device is located within a preset distance from an electronic device based on sensing information obtained through a sensor provided in an electronic device, and if it is determined that the wearable device is located within a preset distance from the electronic device, a security session can be formed.

[0015] According to one embodiment, at least one processor can recognize a first string for at least one area of ​​a patient's prescription, extract a first keyword of a drug prescribed to the patient based on the first string, generate verification information for the patient's prescription based on at least one drug component corresponding to the first keyword, and control a transceiver to transmit the verification information to an electronic device.

[0016] A patient information management system according to one embodiment receives an image acquired through a sensor provided in an electronic device from an electronic device and can recognize a first string of characters for at least one region of the received image.

[0017] A first keyword according to one embodiment includes a first-1 keyword of a first drug and a first-2 keyword of a second drug, and at least one processor can generate verification information including information on the interaction between the first drug and the second drug based on at least one drug component corresponding to the first-1 keyword and at least one drug component corresponding to the first-2 keyword.

[0018] At least one processor according to one embodiment recognizes dosage information of a first drug, dosage information of the first drug, dosage information of a second drug, and dosage information of a second drug based on a first string, and can generate verification information including recommended dosage information of a drug based on dosage information of the first drug, dosage information of the first drug, dosage information of the second drug, and dosage information of the second drug.

[0019] At least one processor according to one embodiment can determine a first-1 string by removing special characters, strings contained within special characters, numbers, and units from a first string, and can extract a word greater than or equal to a predefined number of characters contained in the first-1 string as a first keyword. Additionally, if a pre-set abbreviation of a drug exists in the first string, the abbreviation can be changed to the full name to be recognized.

[0020] According to one embodiment, at least one processor compares a first keyword with a previously defined keyword, and if there is a keyword among the previously defined keywords that is identical to the first keyword, it can generate verification information for a patient's prescription based on at least one drug component corresponding to the first keyword.

[0021] According to one embodiment, at least one processor recognizes a second string for at least one area of ​​a patient's prescription, extracts a second keyword related to patient condition information based on the second string, generates verification information including at least one drug component corresponding to a first keyword and effect information of at least one drug component considering patient condition information based on the second keyword, and the patient condition information may include at least one of the patient's pregnancy information, the patient's breastfeeding information, the patient's kidney function information, the patient's liver function information, and the patient's age information.

[0022] At least one processor according to one embodiment can encrypt EHR information including patient treatment results and prescription history obtained from an electronic medical record system and transmit the encrypted EHR information to a user terminal through a formed secure session.

[0023] A patient information management method according to one embodiment may include the steps of: receiving EHR information from an electronic medical record system in operation; receiving patient information including at least one of a patient's prescription and a patient's medical record from a user terminal through a secure session formed through at least one authentication procedure; and transmitting output information to an electronic device on the medical staff side to output the received patient information and the EHR information received from the electronic medical record system through a user interface.

[0024] A user terminal according to one embodiment includes a transceiver; a memory storing one or more instructions; and at least one processor that executes one or more instructions. The at least one processor can form a secure session with a patient information management system that communicates with an electronic device on the medical staff side through at least one authentication procedure, and in response to the formation of the secure session, control the transceiver to transmit patient information stored according to the user's settings to the patient information management system.

[0025] According to the present disclosure, by utilizing not only the patient's user terminal but also linked wearable devices, a secure session can be immediately formed at the medical site in an intuitive and simple manner, such as near-field tagging (NFC) or augmented reality (AR), thereby ensuring both the convenience of connection between the patient and medical staff and data security.

[0026] Furthermore, according to the present disclosure, by applying a middleware method in which a medical staff's electronic device displays received patient information in the form of an independent pop-up window or layer on the screen of an existing EHR system, an environment is provided in which external data can be universally utilized immediately for medical treatment without being constrained by the EHR system environments or security policies that differ from hospital to hospital.

[0027] Furthermore, according to the present disclosure, by providing precise verification results that comprehensively consider interactions with currently prescribed medications or the patient's real-time health status based on the integrated medical information of the patient obtained in the manner described above, it is possible to prevent medication accidents and provide safer and more flexible patient-customized treatment solutions.

[0028] The effects of the invention are not limited to those mentioned above, and other unmentioned effects will be clearly understood by a person skilled in the art from the description in the claims.

[0029] FIG. 1 is a conceptual diagram showing a patient information management system according to one embodiment.

[0030] FIG. 2 is a block diagram showing the structure of a patient information management system and a device linked to the system according to one embodiment.

[0031] FIGS. 3a and 3b are drawings illustrating the process of a patient information management system and various devices interacting according to one embodiment.

[0032] FIGS. 4a to 4e are exemplary diagrams illustrating an interface in the process of exchanging a patient's prescription between a user terminal and an electronic device through a patient information management system according to one embodiment.

[0033] FIGS. 5A and 5B are exemplary diagrams illustrating a process of determining at least one region to recognize a string on a patient's prescription in a patient information management system according to one embodiment.

[0034] FIGS. 6a and FIGS. 6b are flowcharts illustrating a method for providing drug information according to one embodiment.

[0035] FIGS. 7a to 7e are exemplary drawings illustrating cases in which keywords of drugs are obtained from a patient's prescription and prescription verification information is provided in a patient information management system according to one embodiment.

[0036] FIGS. 8a and 8b are exemplary diagrams illustrating cases where there are precautions due to interactions between prescribed drug components in a patient information management system according to one embodiment.

[0037] FIG. 9 is an exemplary diagram showing an example of providing prescription verification information by considering the frequency of side effects of a prescribed drug in a patient information management system according to one embodiment.

[0038] FIG. 10 is an exemplary diagram showing an embodiment in which prescription verification information is provided by considering prescribed medication and patient pregnancy information in a patient information management system according to one embodiment.

[0039] FIG. 11 is an exemplary diagram showing an embodiment in which prescription verification information is provided by considering prescribed medication and patient feeding information in a patient information management system according to one embodiment.

[0040] FIG. 12 is an exemplary diagram showing an embodiment in which prescription verification information is provided by considering the prescribed drug and patient kidney function information in a patient information management system according to one embodiment.

[0041] FIG. 13 is an exemplary diagram showing an embodiment in which prescription verification information is provided by considering functional information between a prescribed drug and a patient in a patient information management system according to one embodiment.

[0042] FIG. 14 is an exemplary diagram showing an embodiment in which prescription verification information is provided by considering the prescribed drug and the patient's age information in a patient information management system according to one embodiment.

[0043] FIG. 15 is a flowchart illustrating the operation of a user terminal linked with a patient information management system in one embodiment.

[0044] The terms used in the embodiments have been selected to be as widely used and general as possible, taking into account their functions in the present disclosure; however, these may vary depending on the intent of those skilled in the art, case law, the emergence of new technologies, etc. Additionally, in specific cases, terms have been arbitrarily selected by the applicant, and in such cases, their meanings will be described in detail in the relevant description. Therefore, terms used in the present disclosure should be defined not merely by their names, but based on their meanings and the overall content of the present disclosure.

[0045] When a part of a specification is described as "including" a certain component, this means that, unless specifically stated otherwise, it does not exclude other components but may include additional components.

[0046] The expression "at least one of a, b, and c" described throughout the specification may include 'a alone', 'b alone', 'c alone', 'a and b', 'a and c', 'b and c', or 'a, b, and c all'.

[0047] The "terminal" mentioned below may be implemented as a computer or portable terminal capable of connecting to a server or other terminals via a network. Here, the term "computer" includes, for example, a notebook, desktop, or laptop equipped with a web browser, and the term "portable terminal" should be understood as a concept encompassing all forms of wireless communication devices that a user can carry or wear, such as smart glasses, head-mounted displays (HMDs), augmented reality (AR) and virtual reality (VR) devices, mobile devices equipped with hologram output capabilities, or screenless AI wearable devices (e.g., AI PIN) that operate via voice or projection while attached to clothing or the body.

[0048] Embodiments of the present disclosure are described below with reference to the attached drawings so that those skilled in the art can easily implement them. However, the present disclosure may be embodied in various different forms and is not limited to the embodiments described herein. Embodiments of the present disclosure are described below with reference to the drawings.

[0049] FIG. 1 is a conceptual diagram showing a patient information management system according to one embodiment.

[0050] Referring to FIG. 1, a patient information management system (100) (hereinafter referred to as the system) according to one embodiment may include an electronic device (200) used by medical staff, a user terminal (300) and a wearable device (310) on the patient side, and an electronic medical record (EHR) system (not shown) currently in operation, and these may be connected to each other through a network (150).

[0051] The system (100) can receive EHR information from an electronic medical record (EHR) system that is already in operation inside or outside the hospital. The EHR information may include existing medical records of a patient that are generated and managed inside or outside the hospital. The system (100) can form a secure session with a user terminal (300) and / or a wearable device (310) through at least one authentication procedure, and can receive patient information including at least one of a patient's prescription and a patient's medical records from the user terminal (300) through the secure session.

[0052] In one embodiment, the system (100) forms a security session based on user input received from a user terminal through a transceiver (101) to be examined below, and the security session may be maintained for a preset period. The system (100) may set the duration of the security session. The system (100) receives user settings for a session maintenance period from the user terminal (300), such as 'until the end of today's treatment,' 'for one hour,' or 'one year,' or 'three years,' and may omit additional authentication procedures if the user terminal (300) accesses it again within that period. Additionally, the system (100) may receive authentication information including a family relationship certificate, a power of attorney, or a guardian code previously registered by the patient from the patient's guardian terminal. The system (100) verifies the validity of the received authentication information by comparing it with previously stored data, and if valid, may receive patient data (prescription image, information on medication received by proxy, etc.) stored in the guardian terminal through the security session.

[0053] Patient information may include the patient's prescription, the patient's medical records, and biometric data collected from a wearable device (310). The patient's prescription and the patient's medical records may be paper prescriptions or electronic prescriptions. For example, the patient's prescription and the patient's medical records may be obtained from a program related to the patient's prescription and the patient's medical records installed on a user terminal (300) and an electronic device (200), but the scope of the present disclosure is not limited thereto. The system (100) may obtain the patient's prescription and the patient's medical records stored in memory, obtain the patient's prescription and the patient's medical records through a transceiver, and obtain the patient's prescription and the patient's medical records through an image sensor.

[0054] Specifically, the system (100) can receive an image obtained through a sensor provided in the electronic device (200) from the electronic device (200) and obtain patient information by recognizing a first string of characters for at least one area of ​​the received image. For example, if a patient visits the hospital with only a physical prescription or a bottle of medicine being taken and is unable to transmit information through a user terminal (300), the medical staff can photograph this using the electronic device (200). The system (100) can perform optical character recognition (OCR), etc., on the image received from the electronic device (200) to recognize a first string of characters corresponding to the name of the medicine or the name of the ingredient, and generate verification information for the patient's prescription based thereon.

[0055] For example, the patient's prescription and medical records may include paper prescriptions provided by the hospital to the pharmacy and paper charts related to medical records provided by the hospital. Additionally, the patient's prescription and medical records may include medical staff charts recording the patient's symptoms or diagnosis, the patient's blood test records, the patient's pathology test records, imaging test records such as CT and MRI, and all medical and health information. Furthermore, for example, the patient's prescription and medical records may correspond to images received from the user terminal (300) regarding the prescription and medical records provided by the hospital, but the patient's prescription and medical records according to the present disclosure are not limited to any specific case mentioned. The system (100) may integrate or process the received patient information and the EHR information received from the EHR system together, and transmit output information to the electronic device (200) on the medical staff side to output through a user interface.

[0056] In one embodiment, the electronic device (200) may correspond to a device used by medical staff in the process of obtaining patient information from a user terminal (300) and providing at least one of verification information regarding the patient's prescription and processing information regarding the patient's medical records. The electronic device (200) may function as a medical integration platform that integrates and provides various external solutions, data, and knowledge information necessary for medical staff to perform medical treatment. Specifically, the electronic device (200) may provide an interface that directly connects to third-party digital healthcare products or solutions via an API (Application Programming Interface), etc. Through this, the electronic device (200) can support the immediate introduction and utilization of various latest digital healthcare technologies in the clinical setting by first connecting external solutions via API to the program screen of the electronic device (200) without the complex process of directly linking with the hospital's existing EHR system, and then indirectly connecting them to the EHR system through a middleware method.

[0057] Generally, hospital EHR servers restrict direct data connections with external solutions to prevent security risks, such as hacking that may occur when external data is directly input, and to prevent impacts on the operational stability of the EHR system. Therefore, the electronic device (200) according to the present embodiment functions as middleware that safely transmits external data to an EHR input window, etc., without changing the internal logic of the EHR system, in order to resolve these technical limitations. Furthermore, the scope of the present disclosure covers not only cases where such middleware solutions are directly involved, but also methods in which different systems are linked using only a universal security authentication code (e.g., OTP, security QR code, etc.) provided by the system (100). That is, even in an environment where it is difficult for a hospital EHR system and an external startup solution to be directly linked, by utilizing the security authentication code provided by the system (100) as a common medium, a universal linkage protocol can be provided that allows for the independent and secure exchange of information regardless of the type of hospital or the type of external solution.

[0058] Additionally, the electronic device (200) may be equipped with artificial intelligence (AI) and visualization tools or provided in conjunction with the system (100) to reduce the workload of medical staff and increase the accuracy of medical treatment. For example, the electronic device (200) can perform a medical consultation assistance AI function by recognizing the voice of a conversation between a patient and a doctor input through a microphone in real time and recording it as text, and by using an AI algorithm to summarize key symptoms, complaints, and diagnostic information from the conversation and providing them in a format that can be entered into the EHR. Furthermore, the electronic device (200) can visualize blood test results, imaging test results, medical records, patient problem lists, allergy information, etc. transmitted from the user terminal (300) not merely as a list, but as a flowsheet organized according to chronological changes or importance, and display them at a glance. In this process, the AI ​​can summarize and highlight the patient's problem list or abnormal values.

[0059] In addition, the electronic device (200) can support medical staff in immediately accessing necessary medical knowledge during treatment and issuing safe prescriptions. By database-linking resident manuals, various medical textbooks, and the latest treatment guidelines for each specialty, the electronic device (200) can enable medical staff to immediately search for and refer to necessary medical knowledge on the treatment screen through internet site links, PDF file viewers, or medical-specialized AI chatbots. Furthermore, the electronic device (200) can operate an algorithm or AI-based prescription error prevention system to provide warning notifications at the prescription stage by analyzing in real time drug interactions by drug, drug safety ratings for pregnant and breastfeeding women, drug dosage adjustment guides based on liver and kidney function values ​​based on test results received from the user terminal (300), information on common side effects, and information on drugs to be cautious of the elderly. The electronic device (200) can provide customization functions that allow individual settings of screen configuration, notification sensitivity, and a list of frequently used medications according to the medical staff's specialty or personal preference, and can be expanded to include a video communication module for remote medical services or a dashboard function for prescribing and monitoring various digital therapeutics prescribed to patients.

[0060] In one embodiment, the user terminal (300) may correspond to a terminal used by the patient during the process of transmitting patient information to the system (100). Prior to transmitting patient information to the system (100), the user terminal (300) may perform the formation of a secure session for secure data transmission. To this end, the user terminal (300) may provide various authentication interfaces, such as biometric recognition (fingerprint, facial recognition, etc.), password input, NFC tagging with a medical staff device, or QR code scanning. The user terminal (300) may serve as a hub for collecting and integrating patient information to be transmitted.

[0061] Specifically, the user terminal (300) can store and manage a wide range of patient information related to the patient's health, such as the patient's medication information and dosage information, diagnostic information, blood test information, imaging test information, pathology test information, and genetic information. For example, patient information can be obtained in an electronic form from a specific hospital or external institution server, or can also be obtained by capturing or uploading paper prescriptions or test results held by the patient, or medical records in the form of PDF files, using the terminal's camera. For example, the user terminal (300) can access an external National Health Insurance Service or another hospital server to retrieve medical history, use a built-in camera to photograph paper prescriptions or test results and convert them into digital images, or collect real-time biosignal data from a wearable device (310) connected via Bluetooth, etc., to form an integrated patient information package. The user terminal (300) may have a dedicated application for this system installed to provide an AI chatbot-based pre-examination function to identify the patient's symptoms in advance before visiting the hospital, and may further perform the function of including the summary data in the patient information and transmitting it. A user terminal (300) can be linked with a wearable device (310) to collect real-time biosignal data (electrocardiogram, blood sugar, blood pressure, activity level, etc.). The wearable device (310) may include a smart watch, a smart band, a patch-type sensor, AR smart glasses, etc. The user terminal (300) transmits the collected integrated patient information to a system (100) or an electronic device (200) through a security session. At this time, the security session can be immediately formed with the medical staff's electronic device (200) not only through authentication of the user terminal (300) itself, but also through an intuitive authentication method using a wearable device (310) (e.g., a smart watch with NFC tagging function, AR glasses with eye tracking function).

[0062] The user terminal (300) can efficiently process the collected vast amount of data by utilizing artificial intelligence technology. For example, the AI ​​algorithm analyzes and summarizes the patient's blood / imaging test results, genetic test results, medical records, patient problem list, and allergy information stored within the user terminal (300), and the user terminal (300) can perform the function of providing the data in the form of a visualized report so that the patient or the medical staff receiving the data can grasp the key contents at a glance.

[0063] The user terminal (300) provides a pre-examination function for a patient through a conversational user interface and can include the examination summary data generated through the pre-examination function in the patient information and transmit it to the system (100). The user terminal (300) can be equipped with an AI chatbot function. The AI ​​chatbot can be learned based on the latest medical information, treatment guidelines, medical textbook databases, etc., or enhanced through Retrieval-Augmented Generation (RAG) technology. The chatbot can perform a pre-examination by asking and answering various questions about the patient's current symptoms before the patient visits the hospital and organize the results, or frequently record changes in symptoms that the patient is likely to forget between treatments. The symptom summary information organized through the chatbot can be included in the patient information and transmitted to the system (100). Additionally, the user terminal (300) can assist in the patient's health management while simultaneously performing a business model. For example, when displaying a medication alarm at the time of taking the prescribed medication, a function can be provided to display customized advertisements related to the patient's condition or medication (e.g., advertisements for health functional foods, related medical devices, and pharmaceuticals, etc.). Furthermore, the user terminal (300) can be utilized as a terminal for remote medical services between medical staff and patients in the future, or its function can be expanded to become a platform that generates and manages treatment data by linking with various Digital Therapeutics (DTx) applications for the treatment of specific diseases.

[0064] The user terminal (300) may include a guardian terminal used by the patient's guardian. Additionally, the system (100) may receive patient information stored in the guardian terminal through a secure session formed with the system (100) by receiving authentication information from the guardian terminal and determining whether the authentication is valid based on the authentication information. The guardian terminal may be linked with the patient's own terminal in advance, or may legally receive and store patient information in memory through a separate authentication procedure (e.g., authentication based on a family relationship certificate).

[0065] The guardian terminal may store the patient's prescription or test results, etc., taken by the guardian. For example, when a patient visits a medical institution, the system (100) may form a security session with a user terminal (300) corresponding to the guardian terminal, rather than the patient's own terminal. At this time, the system (100) may receive additional authentication information from the guardian terminal to verify its validity. The authentication information may include the guardian's biometric information (fingerprint, facial recognition), a guardian-specific PIN number, or a temporary authentication code issued after verification by medical staff on-site. The system (100) may finally approve the formation of a security session with the guardian terminal only when it is determined that the guardian's identity and proxy authority are valid based on the received authentication information. Through the formed security session, the system (100) may receive patient information (prescription, medical records, wearable data, etc.) stored in the memory of the guardian terminal and transmit it to the medical staff's electronic device (200). Through this, even in situations where the patient cannot directly provide information, the system (100) can enable medical staff to obtain the necessary past history and use it for treatment.

[0066] A system (100), an electronic device (200), and a user terminal (300) according to one embodiment can communicate with each other within a network (130). The network (130) includes a Local Area Network (LAN), a Wide Area Network (WAN), a Value Added Network (VAN), a mobile radio communication network, a satellite communication network, and combinations thereof. It is a comprehensive data communication network that enables each system component shown in FIG. 1 to communicate smoothly with each other, and may include wired internet, wireless internet, and mobile wireless communication networks. Wireless communication may include, for example, wireless LAN (Wi-Fi), Bluetooth, Bluetooth Low Energy, Zigbee, WFD (Wi-Fi Direct), UWB (ultra wideband), infrared communication (IrDA, infrared Data Association), NFC (Near Field Communication), but is not limited thereto. It will be understood by those skilled in the art related to this embodiment that other general-purpose components may be included in addition to the components shown in FIG. 1.

[0067] FIG. 2 is a block diagram showing the structure of a patient information management system and a device linked to the system according to one embodiment.

[0068] Referring to FIG. 2, the system (100), electronic device (200), user terminal (300), and wearable device (310) may include a transceiver (101), a memory (102), and a processor (203) according to one embodiment. The components of the system (100), electronic device (200), user terminal (300), and wearable device (310) shown in FIG. 2 are only those components related to the present embodiment. Therefore, it can be understood by those skilled in the art related to the present embodiment that other general components may be included in addition to the components shown in FIG. 2. For example, the system (100), electronic device (200), user terminal (300), and wearable device (310) may further include a display (not shown) for providing various interfaces to be described below to a user using the electronic device (200) and a patient using the user terminal (300).

[0069] A system (100), an electronic device (200), a user terminal (300), and a wearable device (310) according to one embodiment may include one or more transceivers (201). A transceiver (101) according to one embodiment is a device for performing wired / wireless communication, and the system (100), the electronic device (200), the user terminal (300), and the wearable device (310) can communicate with each other through the transceiver (101) and can also communicate with an external electronic device. The external electronic device may be a terminal or a server. In addition, the communication technology used by the transceiver (101) may include communication technology related to the network (130) described above.

[0070] A memory (102) according to one embodiment can store various types of information. The memory (102) can store data temporarily or semi-permanently. For example, the memory (102) of a system (100), an electronic device (200), a user terminal (300), and a wearable device (310) may store an operating program (OS) for operating the system (100), the electronic device (200), the user terminal (300), and the wearable device (310), as well as data or programs or applications for hosting websites. Additionally, examples of memory (102) may include a hard disk drive (HDD), a solid state drive (SSD), a flash memory, a read-only memory (ROM), and a random access memory (RAM).

[0071] The processor (103) can control the overall operation of the system (100), electronic device (200), user terminal (300), and wearable device (310) and process data and signals. The processor (103) may be composed of at least one hardware unit. Additionally, the processor (103) may be operated by one or more software modules generated by executing program code stored in memory (102). The processor (103) may include a processor and memory, and the processor can control the overall operation of the system (100), electronic device (200), user terminal (300), and wearable device (310) and process data and signals by executing program code stored in memory.

[0072] FIGS. 3a and 3b are drawings illustrating the process of a patient information management system and various devices interacting according to one embodiment.

[0073] Referring to FIG. 3a, a system (100) according to one embodiment may receive EHR information from an electronic medical record (EHR) system in operation at step S310. The EHR information received by the system (100) may include all medical information and health information, such as the patient's basic personal information, past in-hospital treatment history, underlying disease information, and various test information, which are stored in the database of the medical institution. The system (100) may receive or synchronize the EHR information in real time at the time when medical staff call a specific patient or begin treatment through an electronic device (200).

[0074] The system (100) may receive patient information, including at least one of the patient's prescription and the patient's medical records, from a user terminal (300) through a security session formed through at least one authentication procedure in step S320. The system (100) may receive patient identification information from the user terminal (300). Patient identification information may be transmitted from the user terminal (300) based on a request from the system (100) or the electronic device (200) or based on the patient's input, and the system (100) may receive patient identification information that has been encrypted at the user terminal (300) through a security protocol.

[0075] The patient identification information received by the system (100) may include an OTP code generated using a random number generation algorithm (e.g., HMAC-Based OTP or Time-Based OTP) based on personal information such as the patient's name, date of birth, and phone number. The OTP code may be provided as a 6-digit or 8-digit number or in a form combining numbers and alphabets, and may be validly available for a certain period of time, and may be newly generated when that time is exceeded. The system (100) may acquire the patient identification information transmitted from the user terminal (300) and verify the validity of the patient identification information using a key stored on the server. For example, the system (100) may verify the validity by checking whether the OTP code included in the patient identification information was acquired from the user terminal (300) within a certain period of time, whether it was used repeatedly, or whether it was generated based on a previously synchronized key. Depending on the verification result, the system may send a confirmation completion message to the user terminal (300) or request retransmission. When authentication is completed and a security session is formed, the system (100) can receive patient information from the user terminal (300). At this time, the system (100) may also receive patient information from a user terminal (300) used by a third party (e.g., a guardian) other than the patient. In this case, the system (100) can receive patient information obtained based on the response to the user terminal (300) requesting permission to access specific patient information based on the patient's input.

[0076] The system (100) may receive patient information from a user terminal (300), including at least one of the patient's prescription and medical records within a preset period. Here, the preset period serving as the basis for the information received by the system (100) may be determined based on the input of the patient using the user terminal (300), and may be set differently based on the types of drugs and records included in the patient's prescription and medical records. The system (100) may selectively receive only the information necessary for medical treatment, excluding past history that the patient does not personally wish to disclose. Additionally, the system (100) may receive patient information including images obtained by the user terminal (300) driving a sensor based on the patient's input to photograph the patient's prescription and medical records. The system (100) may store and analyze (such as OCR) the received images to generate verification information regarding the patient's prescription and processing information regarding the medical records.

[0077] The system (100) can transmit output information to an electronic device (200) on the medical staff side to output patient information received in step S330 and EHR information received from the electronic medical record system through a user interface. After the formation of a secure session, the system (100) can transmit output information to the electronic device (200) including at least one of verification information regarding the patient's prescription and processing information regarding the patient's medical record. In addition, the system (100) can not only receive patient information as described from the user terminal (300), but also generate updated patient information including at least one of the updated patient's prescription and the patient's medical record based on additional patient information input by the medical staff using the electronic device (200), and transmit it back to the user terminal (300). For example, the additional patient information input may include input regarding additional medical treatment details or prescription details that are not included in the patient information received by the medical staff from the user terminal (300). Through this, the system (100) can obtain updated patient information by reflecting not only the information received from the user terminal (300) but also the latest information generated during the treatment process, and by transmitting this to the user terminal (300) or other external device, secure the integrity and reliability of the data related to the patient's personal information.

[0078] Furthermore, the system (100) according to one embodiment may perform bidirectional data transmission to return the patient's treatment result information, newly recorded in the electronic medical record system, to the user terminal (300) after step S330 or at the time when treatment is completed. Specifically, the system (100) may obtain the latest EHR information, including the diagnosis name, prescription details, and test result report corresponding to each treatment, from the electronic medical record system based on the treatment history, encrypt this information, and transmit it to the user terminal (300) through a pre-established secure session. The user terminal (300) may update the individual patient's health record by accumulating and storing the received EHR information in the memory of the system, the memory of the user terminal (300), or the memory of the system (100). The treatment history accumulated and stored in the user terminal (300) through the system (100) can be utilized as objective data that allows the medical staff to immediately identify the patient's underlying diseases and medication history when the patient visits another medical institution or when an emergency situation occurs in the future. Through this, the system (100) can provide a safe and continuous medical environment through the patient terminal (300) even in an environment where the systems between hospitals are not directly linked.

[0079] Referring to FIG. 3b, the system (100) can form an intuitive security session through various interfaces including physical contact or visual recognition with a user terminal (300) or a wearable device (310) connected thereto.

[0080] The system (100) determines whether the wearable device (310) is located within a preset distance from the electronic device (200) based on sensing information obtained through a sensor equipped in the electronic device (200), and if it is determined that the wearable device (310) is located within a preset distance from the electronic device (200), it can form a security session. For example, the system (100) can form a security session by utilizing a QR code (Quick Response Code). For example, the system (100) can control the generation and display of a QR code containing one-time authentication information on the display of the electronic device (200), and a security session between the two devices can be formed as the user terminal (300) scans the QR code through a camera. Conversely, the system (100) can identify the patient and form a security session by recognizing a patient-specific QR code generated by the user terminal (300) with a scanner connected to the electronic device (200).

[0081] The system (100) can form a secure session using smart glasses equipped with augmented reality (AR) technology. If the wearable device (310) linked to the user terminal (300) is smart glasses, the system (100) can form a secure session by recognizing a specific marker or authentication code displayed on the screen of the electronic device (200) by the smart glasses, or by detecting that the user wearing the smart glasses maintains their gaze toward the code for a certain period of time (gaze tracking), and considering this as a signal of consent to provide information. These methods can provide an environment where, when a patient arrives at the medical site, data can be safely transmitted by intuitively and quickly connecting to the medical staff's system without complex operations.

[0082] The system (100) can form a secure session using near-field wireless communication (NFC) technology. For example, the system (100) can detect that a user terminal (300) or a wearable device (310) worn by the user (e.g., a smart watch, a smart band, etc.) is within a preset distance through an NFC reader or a separate NFC tagging module equipped on an electronic device (200) on the medical staff side. The system (100) can use this proximity detection signal as a trigger to perform an authentication procedure for the user terminal (300), and immediately form a secure session without a separate complex login process, thereby being ready to receive patient information.

[0083] FIGS. 4a to 4e are exemplary diagrams illustrating an interface in the process of exchanging a patient's prescription between a user terminal and an electronic device through a patient information management system according to one embodiment.

[0084] Meanwhile, for convenience of explanation, the user interface (UI) and screen configuration described in various embodiments of the present disclosure may be described as being provided or displayed by any one of the system (100), electronic device (200), or user terminal (300), but this does not limit the scope of the present disclosure to the operation of a specific device. For example, if it is described that the system (100) provides an interface, this may be interpreted as encompassing a series of processes in which the system (100) generates data or web page code to configure the interface and transmits it to the electronic device (200) or user terminal (300), and the receiving device visually outputs the interface through a display.

[0085] Conversely, even if it is stated that an electronic device (200) or a user terminal (300) displays or provides an interface, the data, layout information, or logic included in said interface may be based on information received from the system (100). Accordingly, throughout this disclosure, the subject of operations related to the provision, creation, display, and control of the interface should be interpreted organically according to the data transmission and reception and interoperability relationship between the system (100) and each terminal (200, 300), and should not be limited by a specific subject described in the text but should be understood as being included in the technical concept of this disclosure.

[0086] Referring to FIG. 4a, a user terminal (300) according to one embodiment may display an interface (401) corresponding to the main screen of an application. The interface (401) may include a button to share medication information with medical staff for sharing patient information with the system (100) or the electronic device (200) of the medical staff, and based on the input in which the user selects the button, the security session formation procedure described above (e.g., NFC tagging, QR code generation, or OTP issuance, etc.) may be initiated. Additionally, the interface (401) may summarize and display a button (410) for a list of currently taken medications stored in the user terminal (300) or collected from an external institution, and may intuitively provide information on medications requiring caution based on the patient's condition information, classified into categories such as drug interactions, caution for the elderly, and genetic caution, in the form of icons.

[0087] The user terminal (300) may display an interface (402) that allows the user to check or set their medical and medication history in detail. The interface (402) may include menu buttons for "My Medical Information History" and "My Medication Information History" to support the patient in checking medical data accumulated from the past to the present in a chronological manner. In addition, the interface (402) may provide risk information based on the patient's specific condition or medication characteristics, such as interactions, side effects, pregnancy / lactation, precautions for the elderly, and genetic precautions, in separate categories, thereby helping the patient specifically identify precautions to be taken according to their health condition.

[0088] The user terminal (300) may display an interface (403) indicating that a secure session has been formed with the system (100) or electronic device (200) and that data is being linked. The interface (403) may include icons and text that visually indicate that the drug information and patient information of the user terminal (300) are currently connected to the medical staff's system. In particular, the interface (403) may display the remaining time for the secure session to be maintained (e.g., 20 minutes 00 seconds) in a countdown format so that the user can intuitively recognize the connection maintenance time, and may support the user in manually and immediately terminating the secure session at any time they wish through a connection termination button to block data transmission and ensure security.

[0089] Referring to FIG. 4b, a user terminal (300) according to one embodiment may display an interface (407) containing information on the prescription medication currently being taken by the patient based on input, for example, selecting the current medication list button (410) examined earlier. For example, the information on the prescription medication (420) may include information such as the prescription date of the prescription medication the patient is taking, the product name of the prescription medication, the single dose amount of the prescription medication, the number of doses, the number of days of prescription, the efficacy, and the name of the ingredients. Through the interface (407) containing information on the prescription medication currently being taken by the patient (420), the patient can clearly identify the information on the medication they are taking. For example, the information on the prescription medication currently being taken by the patient (420) may correspond to the information included when the user terminal (300) transmits patient information to the electronic device (200), as examined earlier in FIG. 3a. In one embodiment, the information on the prescription medication (420) may be updated according to the patient's medication prescription status. For example, the user terminal (300) can provide an allergy warning message based on the patient's prescription drug information (420) if a drug with a risk of causing allergies is prescribed to the patient. For example, the user terminal (300) can provide an allergy warning message indicating that an allergy is expected for other drugs containing the same ingredients included in the same drug information. Through this, for example, if there is a medical record in the patient information indicating that an allergy occurs to the patient due to a specific drug, the user terminal (300) can provide an allergy warning message based on the medical record if a drug with the same ingredients is prescribed in the future.For example, if there is medical information that a specific patient develops an allergy to sulfur in an anti-inflammatory drug component such as celecoxib, the user terminal (300) may provide an allergy warning message indicating that an allergy may also occur in anti-rheumatic drugs such as sulfasalazine containing sulfur.

[0090] Referring to FIG. 4c, a user terminal (300) according to one embodiment may display an interface (405) including patient identification information (430) generated by the user terminal (300). A patient using the user terminal (300) may inform a medical staff member in a face-to-face relationship of the patient's identification information (430). For example, if the medical staff member using the electronic device (200) is the medical staff member in question, the patient's identification information (430) may be used in the process of the user terminal (300) transmitting patient information to the electronic device (200). Although FIG. 4c illustrates that an OTP code is used as the patient's identification information (430) described above, specific hospital patient registration information may also be used as the patient's identification information (430) as described above.

[0091] Referring to FIG. 4d, an interface (406) can be seen that displays patient information including a patient's prescription (442) and a patient's medical record (441) included in the patient information obtained from a user terminal (300) by a system (100) according to one embodiment. At this time, the interface (406) provided by the system (100) may be displayed in the form of a layer or a pop-up window that is independently created on the background screen of an electronic medical record (EHR) system currently in operation on an electronic device (200). That is, the electronic device (200) can display the output information received from the system (100) superimposed on the execution screen of the EHR system, thereby allowing medical staff to intuitively check patient information received from the outside without leaving the screen of the EHR system.

[0092] The system (100) can obtain a first input from a medical professional using an electronic device (200). For example, the first input from the medical professional may correspond to a user input to an input interface (450) on an interface (406). Based on the first input from the medical professional, the system (100) can obtain at least one of the verification information regarding the patient's prescription and the processing information regarding the patient's medical records, which will be described below, through an external server or a user terminal (300). That is, based on the first input from the medical professional, the system (100) can obtain at least one of the verification information regarding the patient's prescription and the processing information regarding the patient's medical records, which will be described below, without separate string recognition.

[0093] The system (100) may also recognize a string for at least one area of ​​the patient's prescription (442) based on a second input from a medical staff member using an electronic device (200) to obtain at least one of verification information for the patient's prescription and processing information for the patient's medical record. For example, the second input from the medical staff member may correspond to user input to an input interface (460) on the interface (406). Furthermore, the interface (406) may further include an object (not shown) that provides a function to transfer displayed patient information to an input field of an electronic medical record system. For example, the object may include an 'EHR input' button, a copy button, or an interface for performing a drag and drop function. When a medical professional performs a second input by selecting text or an image of a patient's prescription (442) or medical record (441) and dragging and dropping it into an input window of the electronic medical record system or clicking a specific button, the electronic device (200) can process the information by copying it to a clipboard or executing an input macro so that data is automatically entered into an input field of the electronic medical record system. The embodiment of providing patient prescription verification information in FIGS. 8a to 14, as described below, may be applicable to both cases where the medical professional's second input is entered into the electronic device (200) and where the medical professional's first input is entered into the electronic device (200).

[0094] Referring to FIG. 4e, a system (100) according to one embodiment may display an interface (407) including an area (470) representing patient prescription drug information according to a patient's prescription included in patient information obtained from a user terminal (300) based on a first input or a second input of a medical staff member as previously examined in FIG. 4d, a capture result area (480) obtained through keyword recognition based on a string as to be examined below, and an advertisement area (490). The interface (407) may also be provided in the form of a pop-up window that is overlaid on the EHR system screen as described in FIG. 4d, and may include an object that can immediately transfer the textualized drug information displayed in the area (470) to the EHR system.

[0095] According to one embodiment, the area (470) displaying patient prescription drug information may include a patient identification information input field (471) in which a user of the electronic device (200) can input the patient identification information described above. If the patient identification information entered through the patient identification information input field (471) is identical to the patient identification information (430) described in FIG. 4c, the system (100) may determine that the patient identification information (430) has been validly verified. If the system (100) determines that the patient identification information (430) has been validly verified, it may display information on the prescription drugs currently being taken by the patient on the area (470) displaying patient prescription drug information based on the patient's prescription as described in FIG. 4b. As described above, the patient prescription drug information displayed on the area (470) displaying patient prescription drug information may correspond to drug information prescribed to the patient within a pre-set period.

[0096] As previously explained, FIG. 4e illustrates that patient prescription drug information obtained based on patient identification information is displayed in area (470), and drug information obtained through keyword recognition based on strings is separately displayed in area (480). However, this is merely an example, and in reality, some of the same patient prescription drug information may be displayed redundantly in area (470) and area (480). Additionally, the patient prescription drug information displayed in area (470) and the patient prescription drug information displayed in area (480) may be displayed in a single area and may be used without limitation in the process of providing drug information in FIG. 7e to FIG. 14, as will be examined below.

[0097] In an advertising area (490) according to one embodiment, advertisements determined based on medical staff information of a medical staff member using the electronic device (200) may be displayed. In other words, the system (100) may provide advertisements determined based on medical staff information. For example, considering that the user using the electronic device (200) is a medical staff member, the medical staff information may include at least one of the user's affiliated department information, the user's affiliated hospital information, and the medical staff's prescription drug information, which are various information related to the user and are already registered on a server related to the electronic device (200). For example, the medical staff's prescription drug information may include the information in the list of prescription drugs previously prescribed by the medical staff. For example, if a medical professional has previously prescribed a hepatitis C drug such as sofosbuvir and that hepatitis C drug is included in the list of previously prescribed drugs, the advertising effect for tenofovir and hepatitis B drugs may be increased, and if a medical professional has previously prescribed an anti-rheumatic drug such as adalimumab and that drug is included in the list of previously prescribed drugs, the advertising effect for an anti-rheumatic drug such as tofacitinib may be increased, so the system (100) can decide on advertising by taking into account such information on the medical professional's prescription drugs.

[0098] User information may also include various additional information such as the size of the user's affiliated hospital, the user's affiliated country, and the user's residential area. For example, advertisements displayed in the advertising area (490) may be determined based on user information, the click-through rate of other users who have a high similarity to the user information of the user using the electronic device (200), and the purchase rate of the advertised product. Although the advertising area (490) is shown as being located at the bottom of the area (470) displaying patient prescription drug information in FIG. 4e, for example, the advertising area (490) may be displayed on the interface (407) in the form of a pop-up, or may be displayed at a location on the interface (407) according to user settings, and the embodiments according to the present disclosure are not limited to the specific cases mentioned.

[0099] FIGS. 5a and 5b are exemplary diagrams illustrating a process of determining at least one area to recognize strings on a patient's prescription in a patient information management system according to one embodiment. Referring to FIG. 5a, a system (100) included in a patient information management system according to one embodiment can determine at least one area of ​​a patient's prescription based on a second input from a medical professional using an electronic device (200), and can recognize various strings included in said at least one area. For example, the at least one area may include the entire area or a part of the patient's prescription. For example, each area included in the at least one area may be determined based on a selection input interface (520) included in an area selection interface (510). As illustrated in FIG. 5a, a medical professional using an electronic device (200) may position the area selection interface (510) overlapping the area (511) on the patient's prescription to recognize strings through the electronic device (200), and determine the area through the selection input interface (520).

[0100] Referring to FIG. 5b, a medical professional using an electronic device (200) may move the area selection interface (530) overlapping with another patient's prescription area (512) where they wish to recognize a string of characters through the electronic device (200) on the patient's prescription, and determine the corresponding area through the selection input interface (520). At least one of the area (511) and the area (512) may be configured to include the starting word of the strings as described below. Through this, the system (100) can recognize not only the entire area of ​​the patient's prescription but also only the strings included in specific areas such as the area (511) and the area (512) determined based on user input, thereby increasing the efficiency of data processing for the method of providing drug information through the recognition of strings included in the patient's prescription as described below. FIG. 5a and FIG. 5b illustrate the case of determining at least one area on the patient's prescription, but the present disclosure is not limited to the case described. For example, the system (100) can determine at least one region of an image of a pharmaceutical product included in an image obtained through a sensor as described above through the above process, and can obtain a keyword from a string through the process as described below.

[0101] FIGS. 6a and 6b are flowcharts illustrating a method for providing drug information according to one embodiment. Referring to FIG. 6a, a system (100) according to one embodiment can recognize a first string of characters for at least one area in a patient's prescription at step S610. For example, the system (100) can recognize the first string of characters through an optical character recognition (OCR) method. For example, the system (100) can obtain text information from a program related to the patient's prescription using a predetermined API (application programming interface) and recognize the first string of characters from the text information. In this case, the predetermined API may correspond to a hooking API provided by an operating system such as DOS, Windows, Linux, UNIX, or macOS. A system (100) according to one embodiment can obtain the patient's prescription from a user terminal (300) at step S610 and recognize the first string of characters from the patient's prescription.

[0102] In addition, a system (100) according to one embodiment may input a patient's prescription into an artificial intelligence model in step S610 to obtain an area regarding the medication prescribed to the patient and an area regarding the patient's diagnosis on the patient's prescription. In this case, the artificial intelligence model may correspond to an artificial intelligence model that is trained to recognize and obtain an area regarding the medication prescribed to the patient and an area regarding the patient's diagnosis on the patient's prescription, recognize a first string regarding the area regarding the medication, and recognize a second string regarding the area regarding the diagnosis. A system (100) according to one embodiment may recognize a first string regarding the area regarding the medication and a second string regarding the area regarding the diagnosis through an artificial intelligence model in step S610.

[0103] A system (100) according to one embodiment inputs a patient's prescription into an artificial intelligence model to recognize a second string of characters in an area regarding diagnostic matters and, based on the second string of characters, can recognize a first string of characters in an area regarding medication. Additionally, the system (100) inputs a patient's prescription into an artificial intelligence model to recognize a first string of characters in an area regarding medication and can recognize a second string of characters in an area regarding diagnostic matters. For example, if the patient has symptoms of rheumatoid arthritis, steroids, tacrolimus, methotrexate, naproxen, sulfasalazine, leflunomide, etc. may need to be prescribed.

[0104] A system (100) according to one embodiment may input a patient's prescription into an artificial intelligence model to recognize a second string of characters in the area regarding the diagnosis, thereby recognizing a string of characters such as steroid, tacrolimus, methotrexate, naproxen, sulfasalazine, leflunomide, etc., as a first string of characters in the area regarding the drug, based on this. Alternatively, the system (100) may input a patient's prescription into an artificial intelligence model to recognize a string of characters such as steroid, tacrolimus, methotrexate, naproxen, sulfasalazine, leflunomide, etc., as a first string of characters in the area regarding the drug, and based on this, recognize a string of characters such as rheumatoid arthritis, Rheumatoid Arthritis, or RA, an abbreviation thereof, as a second string of characters in the area regarding the diagnosis.

[0105] For example, the artificial intelligence model may be an artificial intelligence model trained to learn the relationship between a second string regarding the area of ​​the patient's diagnosis and a first string regarding the area of ​​the medication, and to recognize a specific string in the second string when the first string contains a specific string, or to recognize a specific string in the first string when the second string contains a specific string. Through this, the system (100) can use the artificial intelligence model to recognize specific prescription medication details on the patient's prescription when specific diagnosis details are recognized on the patient's prescription, and conversely, to recognize specific diagnosis details on the patient's prescription when specific prescription medication details are recognized on the patient's prescription, thereby enabling the recognition of the first string and the second string to be performed more quickly and accurately.

[0106] A system (100) according to one embodiment determines in step S610 whether there is an abbreviation of a drug previously set in a first string for a first area, and if there is an abbreviation of a drug previously set in the first string, it can recognize the changed first string by changing the abbreviation to a full name. Similarly, the system (100) recognizes a second string for a second area, determines whether there is an abbreviation regarding patient condition information previously set in the second string, and if there is an abbreviation regarding patient condition information previously set in the second string, it can recognize the changed second string by changing the abbreviation to a full name.

[0107] The relationship between the abbreviation of a previously established drug and the abbreviation and full name regarding the previously established patient condition information may be, for example, as shown in Table 1 below.

[0108] 약어전체 명칭a.cBefore meals. As in taking medicine before meals.a / g ratioAlbumin to globulin ratioACLAnterior cruciate ligamentADHDAttention deficit hyperactivity disorderADRAdverse drug reaction.AIDSAcquired immune deficiency syndromeAKAAbove the knee amputation.ADHAntidiuretic hormoneARDSAcute respiratory distress syndrome.ARFAcute renal (kidney) failureASCVDAtherosclerotic cardiovascular disease. A form of heart disease.b.i.dTwice daily. As in taking medicine twice daily.BKABelow the knee amputation.BPBlood pressureCABGCoronary artery bypass graft. A surgery involving the heart.CBCComplete blood count.CCChief complaint.CPAPContinuous positive airway pressure. Treatment for sleep apnea.COPDChronic obstructive pulmonary disease.

[0109] However, the relationship between the abbreviations and full names presented in Table 1 is merely illustrative, and the embodiments according to the present disclosure are not limited to any specific case. A system (100) according to one embodiment can extract a first keyword of a drug prescribed to a patient based on a first string in step S620. The system (100) can recognize a first-1 string by removing special characters, strings contained within special characters, numbers, and units (e.g., mg, g, ml, l) from the first string. In this case, special characters may include, for example, parentheses ((, )), square brackets ([, ]), curly brackets ({,}), and arrow brackets (<, >). The system (100) can extract a specific word contained in the first-1 string as a first keyword, and the detailed process for this is described in detail below in FIGS. 6b and FIGS. 7b.

[0110] A system (100) according to one embodiment can generate verification information for a patient's prescription based on at least one drug component corresponding to a first keyword in step S630. For example, the system (100) can compare the first keyword obtained in step S620 with a predefined keyword, and if there is a keyword among the predefined keywords that is identical to the first keyword of the drug, it can generate verification information for a patient's prescription based on at least one drug component corresponding to the first keyword and provide it through an electronic device (200).

[0111] The system (100) may extract a first keyword and compare it with a predefined keyword existing in a predetermined database. In this case, the predefined keyword may refer to a keyword defined prior to the acquisition of the first keyword in relation to the drug, and may be a keyword stored in combination with one or more drug components. For example, the predefined keyword may be determined based on the past prescription history information of other patients prior to providing prescription verification information for a specific patient, and the one or more drug components stored in combination with the predefined keyword may include drug recommended dosage information and alternative drug information provided during the process of providing prescription verification information for other patients. The predetermined database may be a structured collection that stores drug information according to drug components in a structured manner, and may store drug information according to drug components in the form of tables, columns, and rows. The drug information may include information related to the name of the drug, drug interactions, ingredients, side effects, dosage and administration, precautions, etc.; information such as drug grade, drug type, classification, drugs suitable for pregnancy, drugs suitable for breastfeeding, drug half-life, etc.; and information regarding risk information based on combinations of drugs based on characteristic information of each drug.

[0112] Additionally, the system (100) may recognize a second string related to the patient's condition information in the patient's prescription and obtain a second keyword related to the patient's condition information based on the second string. The system (100) may provide prescription verification information based on the first keyword of the drug and the second keyword regarding the patient's condition. In this case, the patient condition information may include at least one of the patient's pregnancy information, the patient's breastfeeding information, the patient's kidney function information, the patient's liver function information, and the patient's age information. Additionally, the patient condition information may include information regarding comorbidities such as myocardial infarction. Based on such various patient condition information, the system (100) may provide verification information for the patient's prescription by considering various drug information expected to be prescribed to a patient in a specific health condition.

[0113] A system (100) according to one embodiment may control a transceiver (101) to transmit verification information to an electronic device (200) in step S640. The verification information may provide prescription verification information including information on alternative drugs that can be prescribed to a patient and information on drugs expected to be prescribed to a patient, and such embodiments are described in detail below in FIGS. 9 to 14.

[0114] Referring to FIG. 6b, a system (100) according to one embodiment may recognize a first string for a first area in a patient's prescription in step S610, and then in step S620-1, recognize a first-1 string by removing special characters, strings contained within special characters, numbers, and units from the first string. In this case, the special characters may include various types of bracket characters as described in step S620 of FIG. 6a. In this case, the units may include mass and volume units as described above.

[0115] The system (100) can determine a word with a number of characters equal to or more than a predefined number of characters in the first-first string in step S620-2. More specifically, the system (100) removes predefined words (e.g., capsule, tablet, suspension, syrup, long-term tablet, day, time, injection tablet, etc.) in step S620-2, determines a word with a number of characters equal to or more than the predefined number of characters among the remaining words, and can extract the word with a number of characters equal to or more than the predefined number of characters as the first keyword. More specifically, when the system (100) determines in step S620-2 that only English exists in the first-first string, it determines whether the first word of the first-first string has a number of characters equal to or more than the predefined number of characters, and if the first word has a number of characters equal to or more than the predefined number of characters, it can extract the first word as the first keyword. When the system (100) determines that only English exists in the first-first string, it determines whether the first word of the first-first string has a number of characters equal to or more than the predefined number of characters. If the first word has a number of characters less than the predefined number of characters, it determines another word with a number of characters equal to or more than the predefined number of characters existing in the first-first string and then can extract the word with a number of characters equal to or more than the predefined number of characters as the first keyword in step S620-2.

[0116] In a case where the system (100) according to an embodiment does not determine in step S620-2 that only English exists in the first-first string (e.g., when characters of other languages such as English, Korean, and Japanese are mixed in the first-first string, or when only Korean or Japanese exists in the first-first string), it can remove predefined words (e.g., capsule, tablet, suspension, syrup, long-term tablet, day, time, injection tablet, etc.) and determine a word with a number of characters equal to or more than the predefined number of characters among the remaining words. Thereafter, the system (100) can extract the word with a number of characters equal to or more than the predefined number of characters as the first keyword. The system (100) can extract the first keyword included in various forms of the first string based on the basic information for identifying the pharmaceutical ingredient throughout the process mentioned in FIG. 6b.

[0117] FIGS. 7a to 7e are exemplary diagrams illustrating cases in which keywords of medications are obtained from a patient's prescription and prescription verification information is provided in a patient information management system according to one embodiment. Referring to FIGS. 7a and 7b, an example of a patient's prescription to which the system (100) according to one embodiment provides verification information can be observed. The system (100) according to one embodiment can recognize a first string of characters for a first area in the patient's prescription. The prescription may include a first area (701) and a second area (711). The system (100) according to one embodiment can recognize a first string of characters for the first area and a second string of characters for the second area by performing optical character recognition for each of the first area (701) and the second area (711) designated by the user, and each of the first area (701) and the second area (711) may correspond to an area designated by the user.

[0118] For example, the system (100) can perform optical character recognition for a specific first area (701) and a specific second area (711) designated by the user within the prescription, and can obtain input for at least one area designated by the user through a separate user interface as previously examined in FIG. 5a and FIG. 5b. In addition, the system (100) according to one embodiment can recognize a specific keyword through optical character recognition of the prescription, recognize a first string through optical character recognition of the first area (701), and recognize a second string through optical character recognition of the second area (711), and each of the first area (701) and the second area (711) may be an area determined based on a specific keyword.

[0119] For example, the system (100) may acquire specific keywords present on a prescription (e.g., order issuance, prescription name), distinguish upper, lower, left, and right regions centered on the specific keywords, and determine a first region (701) containing information about the medication based on predefined text information located, for example, in the lower region of the specific keywords. Similarly, the system (100) may acquire specific keywords present on a prescription (e.g., outpatient progress, findings, plan, medical record), distinguish upper, lower, left, and right regions centered on the specific keywords, and determine a second region (711) containing patient condition information based on predefined text information located, for example, in the lower region of the specific keywords. The first string for the first area in the patient's prescription may include a string mixed with Korean and English as in the example of FIG. 7a, and may include a string mixed with English and Japanese as in the first area (701-1) in the example of FIG. 7b, but the entire process of the system (100) according to the present disclosure extracting the first keyword from the first string is not limited to the specific cases mentioned.

[0120] Referring to FIG. 7c, for example, a system (100) according to one embodiment may perform the task of converting the color of the first area (701) in a patient's prescription into grayscale for the first area (701), analyze the values ​​of the color-converted pixels to determine brightness and contrast, and then recognize a first string (e.g., string (702) to string (708)) that is distinguished from the background through pixel value classification and layout analysis. As described in FIG. 7a, the first area (701) may be an area corresponding to an area designated by the user, or an area determined based on a specific keyword recognized through optical character recognition for the prescription. The system (100) may recognize the first string through optical character recognition for the first area (701), and may also obtain text information from a program related to the prescription using a predetermined API and recognize the first string from the text information.

[0121] Referring to FIG. 7d, an embodiment in which a system (100) according to one embodiment extracts a first keyword based on a first string described in FIG. 6b can be observed. For example, as seen in FIG. 7a, the system (100) can recognize a first string (e.g., string (704)) related to a drug in a patient's prescription. Subsequently, the system (100) can obtain a first-1 string (e.g., string (720)) by removing special characters (e.g., special characters (713; 714; 716; 717)), strings contained within special characters (e.g., string (715) contained within special characters (713) and special characters (714) and string (718) contained within special characters (716) and special characters (717)), numbers (e.g., number (719)), and units (e.g., unit (719-1)) from the string (704). The system (100) can determine a word with a predefined number of characters or more within the first-1 string (720) and extract the word with a predefined number of characters or more as the first keyword.

[0122] In a more specific embodiment, the system (100) can extract the first word (e.g., word (730)) of the first-1 string (e.g., string (720)) as the first keyword when only English exists in the first-1 string and the first word (e.g., word (730)) of the first-1 string (e.g., string (720)) is greater than or equal to a threshold number of characters (e.g., five alphabets in the case of English). In one embodiment, in the case of a string (722) in which the same content as the string (704) is expressed in a mixture of Korean and English, the system (100) can obtain a first-1 string (e.g., string (740)) by removing special characters (e.g., special characters (723; 724; 726; 727)), strings contained within special characters (e.g., strings (725) contained within special characters (723) and special characters (724) and strings (728) contained within special characters (726) and special characters (727)), numbers (e.g., numbers (729)), and units (e.g., units (729-1)) from the string (722). The system (100) can extract a word (e.g., word (750)) excluding the predefined words from the first-1 string (e.g., string (740)) as the first keyword when the first-1 string (740) does not contain only English (e.g., when English and Korean are mixed in the first-1 string, when only Korean is present in the first-1 string), and when there are predefined words (e.g., capsule, tablet, suspension, syrup, enteric-coated tablet, dosage unit, injection, etc.) and a Korean word that is greater than or equal to the threshold number of characters (e.g., two characters in the case of Korean) after excluding the predefined words.

[0123] In another more specific embodiment, as shown in FIG. 7b, the system (100) can recognize a first string (e.g., string (732)) in which English and Japanese are mixed. Subsequently, the system (100) removes special characters (e.g., special characters (733; 734; 736; 737)), strings included inside the special characters (e.g., string (735) included inside special character (733) and special character (734), and string (738) included inside special character (736) and special character (737)), numbers (e.g., numbers (739); numbers (739-2); numbers (739-3)) and units (e.g., unit (739-1)) from the string (732) to obtain a first-1 string (e.g., string (770)). The system (100) can determine words (770) in the first-1 string (770) that are longer than a predefined number of characters, except for the predefined words 回 and 錠, and extract the words (770) that are longer than the predefined number of characters as the first keyword. That is, the system (100) can extract a first keyword determined in a specific language through the process as described regardless of the language included in the first string existing in the first area on the prescription of the patient.

[0124] A system (100) according to one embodiment may extract a first keyword of another language bound to the first keyword of the specific language when there is no first keyword determined in a specific language among the predefined keywords. In this case, at least one pharmaceutical component corresponding to the first keyword of the other language may be identical to at least one pharmaceutical component corresponding to the first keyword determined in the specific language. For example, depending on the type of language included in a patient's prescription, keywords may be determined in different languages ​​even for drugs having the same pharmaceutical component. In this disclosure, the case where a keyword is obtained in Japanese is used as an example, but depending on various types of world characters, there may be cases where a first keyword determined in a specific language does not exist among the predefined keywords. For example, in the case of a drug such as Tylenol, if the language included in the first string existing within the first area of ​​the patient's prescription is Korean, a first keyword such as "Tylenol" may be obtained, and the first keyword of "Tylenol" may be included in the predefined keywords. However, even for the same Tylenol drug, the first keyword may be obtained as "Tylenol" in English and "タイレノル" in Japanese, depending on the entry on the patient's prescription. For example, if the system (100) obtains the first keyword as "タイレノル" and the first keyword "タイレノル" does not exist among the predefined keywords, the system (100) can extract "Tylenol" as the first keyword, which is the first keyword in Korean, another language bound to the first keyword "タイレノル". Although the present disclosure describes the case of Japanese as an example of various languages, the embodiment according to the present disclosure is not limited to the specific case mentioned, and the system (100) can extract the same keyword as the first keyword, regardless of the type of language entered on the patient's prescription, where at least one drug component corresponding to a specific keyword is the same among the predefined keywords.

[0125] Referring to FIG. 7e, the interface (701-2) provided by the system (100) according to one embodiment may include information regarding side effects resulting from interactions between drug components according to a first keyword (702-1; 703-1; 704-1) of the drug and at least one drug component (702-2; 703-2; 704-2) corresponding to the first keyword. As previously described, the interface (701-2) may also include an advertisement area (750-1) that displays an advertisement determined based on user information using the electronic device (200). With respect to FIG. 7e below, it is explained that information regarding side effects resulting from the interaction between drug components (702-2; 703-2; 704-2) corresponding to the first keyword is provided based on the illustrated first keyword (702-1; 703-1; 704-1), but as previously examined, the case of using a keyword in the area (730-1) indicating drug information prescribed to a patient within a pre-set period is also included in the embodiments according to the present disclosure.

[0126] In one embodiment, the system (100) can compare a first keyword of the drug with a predefined keyword. For example, the system (100) can compare whether there is a keyword identical to the first keyword among the predefined keywords. For example, if the first keyword is accurately obtained from the first string, it may correspond to a case where there is a keyword identical to the first keyword of the drug among the predefined keywords, and the system (100) can provide verification information for the patient's prescription based on at least one drug component corresponding to the first keyword. For example, if there is no information regarding the drug component according to the first keyword (705-1), the system (100) may provide a notification message (705-2) indicating that such information is not available. For example, if there are no serious side effects resulting from the combination of each of the searched drug components (702-2; 703-2; 704-2) by comparing the first keyword (702-1; 703-1; 704-1) of the electronic device (200) with a predefined keyword, prescription verification information (e.g., phrase (741)) can be provided through the interface (701-1) that the interaction of each of the drug components (702-2; 703-2; 704-2) included in the patient's prescription does not have a serious effect on the patient. FIG. 7e illustrates a case where prescription verification information is provided as there is no serious effect due to the interaction between the drug components regarding the drug components included in the patient's prescription, but an example of a case where there is a serious effect due to the interaction between the drug components is specifically examined below in FIG. 8a and FIG. 8b.

[0127] In one embodiment, if the first keyword of the drug does not exist among the predefined keywords, the system (100) can obtain the first-1 keyword of the drug by changing some of the characters included in the first string according to a predefined rule. That is, if the first keyword of the drug does not exist among the predefined keywords, the system (100) can obtain the first-1 keyword of the drug by changing some of the characters included in the first string according to a predefined rule, considering that there is an error in recognizing the first string on the patient's prescription (e.g., a rule to change the alphabet "q" to "g" if the first string contains the alphabet "q", a rule to change the alphabet "g" to "q" if the first string contains the alphabet "g", a rule to change the consonant "ng" to "m" if the first string contains the consonant "ng", a rule to change the consonant "ng" to "ng" if the first string contains the consonant "m", etc.). Additionally, the system (100) can provide verification information for the prescription based on the result of comparing the acquired first-1 keyword with a predefined keyword, and if the first keyword of the correct drug cannot be extracted due to misrecognition of the string, the system can accurately recognize the string after changing it according to a predefined rule, and acquire the first-1 keyword of the drug prescribed to the patient based on the changed first string to provide verification information for the prescription.

[0128] For example, if the first keyword of the drug does not exist among the predefined keywords, the system (100) provides information to the user that there is no search result for the first keyword of the drug, and can obtain the first-four keywords of the drug based on information entered through the user input interface. For example, if the first keyword of the drug (705) does not exist among the predefined keywords, the system (100) provides information (705-1) to the user that there is no search result for the first keyword of the drug (705), and can obtain the first-four keywords of the drug based on information entered through the user input interface (751). In this case, the first-four keywords can be determined based on user input. Subsequently, if the first-four keywords of the drug exist among the predefined keywords, the system (100) can provide verification information for the patient's prescription based on the drug components related to the predefined keywords.

[0129] A system (100) according to one embodiment can determine a first keyword by considering a drug expected to be prescribed to a patient based on patient condition information and provide verification information for the patient's prescription. For example, if there is no keyword identical to the first keyword of the drug among the predefined keywords, the system (100) can recognize a second string of characters for a second area in the prescription, obtain a second keyword related to patient condition information based on the second string of characters, and obtain a third keyword of the drug expected to be prescribed according to the patient condition information based on the second keyword. In this case, the second area may be an area corresponding to a user-specified area as seen in FIG. 7a, or an area determined based on a specific keyword recognized through optical character recognition of the prescription. The system (100) can recognize the second string of characters through optical character recognition of the second area, and may also obtain text information from a program related to the prescription using a predetermined API and recognize the second string of characters from the text information. The system (100) can obtain a second keyword related to patient condition information based on a second string, and based on the second keyword, obtain a third keyword of a drug expected to be prescribed according to the patient condition information, and obtain a first-to-third keyword that has the highest similarity to the first keyword among the third keywords. For example, if the system (100) determines "myocardial infarction" as the second keyword related to patient condition information, it can obtain a third keyword of aspirin, which is a drug expected to be prescribed according to "myocardial infarction," as the third keyword, and obtain a first-to-third keyword that has the highest similarity to the first keyword among these.

[0130] Subsequently, the system (100) compares the first-third keywords of the drug with predefined keywords, and if the first-third keywords of the drug exist among the predefined keywords, it can provide verification information for the patient's prescription based on the drug components corresponding to the predefined keywords. That is, even if the first keyword is not accurately obtained, the system (100) can obtain the second keyword related to the patient's condition information, then obtain the third keyword of the expected drug according to the patient's condition information, and provide prescription verification information based on the keyword with the highest similarity to the first keyword among the third keywords of the expected drug. For example, in the case of a patient with symptoms of rheumatoid arthritis, it may be necessary to prescribe immunomodulators such as sulfasalazine, leflunomide, hydrochloroquine, and tacrolimus in combination depending on the situation, based on the immunomodulator methotrexate. For example, even if the first keyword is misidentified as medhotreaxte, the system (100) can obtain the third keyword of the expected prescription drug according to the patient condition information (rheumatoid arthritis) through the patient condition information if the patient has symptoms of rheumatoid arthritis (obtain methotrexate, sulfasalazine, leflunomide, hydrochloroquine, tacrolimus), and obtain the first-third keyword methotrexate, which has the highest similarity to the first keyword medhotreaxte among the third keywords. Subsequently, the system (100) can provide verification information for the patient's prescription by comparing methotrexate with the predefined keywords.

[0131] FIGS. 8a and 8b are exemplary diagrams illustrating cases where there are precautions due to interactions between prescribed drug components in a patient information management system according to one embodiment. Referring to FIG. 8a, a system (100) according to one embodiment can recognize a first string (e.g., string (802) to string (808)) from a first area (801) included in a patient's prescription. As described in FIGS. 6a and 7a, the system (100) can perform recognition of the first string through optical character recognition. Additionally, the system (100) can obtain text information from a program related to the prescription using a predetermined API and perform recognition of the first string from the text information.

[0132] Referring to FIG. 8b, a system (100) according to one embodiment may provide prescription verification information by considering precautions regarding interactions between prescribed drug components through an interface (803-2). The system (100) may provide prescription verification information by considering information on the frequency of side effects of the prescribed drug through an interface (801-1) based on user input through an interface (809) regarding precautions regarding interactions between prescribed drug components. As previously described, the interface (803-2) may also include an advertising area (850) that displays an advertisement determined based on user information using the electronic device (200). With respect to FIG. 8b below, it is explained that information regarding side effects resulting from the interaction between drug components corresponding to the first keyword (802-1; 803-1) is provided based on the illustrated first keyword (802-1; 803-1), but as previously examined, the case of using keywords in the area (830) indicating drug information prescribed to a patient within a pre-set period is also included in the embodiments according to the present disclosure.

[0133] An interface (803-2) provided by a system (100) according to one embodiment may include a first keyword (802-1; 803-1) of a drug, at least one drug component (802-2; 803-2; 804-2) corresponding to the first keyword, combination information of some of the drugs for each of the drug components (802-2; 803-2; 804-2), interaction information (823; 824), and alternative drug information (831). That is, as shown in FIG. 8b, the first keyword may include the first-1 keyword (802-1) of the first drug and the first-2 keyword (803-1) of the second drug, and the system (100) may provide information (823) that there are side effects due to an interaction resulting from the combination of the first drug and the second drug through the interaction category (820), based on at least one drug component (802-2) corresponding to the first-1 keyword (802-1) and at least one drug component (803-2) corresponding to the first-2 keyword (803-1) in the drug component category (810), and may provide information on alternative drugs (841) through the alternative drug category (840). For example, the system (100) may provide only the interaction information (824) based on the combination information of the drug component (804-2) and the drug component (802-2) through the interaction category (820). Through this, the system (100) can provide information on the interaction and alternative drugs when side effects resulting from interactions between combinations of each drug component in a patient's prescription are identified in the drug information through predefined keywords. Additionally, the system (100) can also provide information on alternative drugs based on the mechanism of the specific drug component itself and the dosage recommendations.

[0134] Additionally, a system (100) according to one embodiment may recognize strings related to information regarding the dosage of a drug. For example, the system (100) may recognize dosage information of a first drug, information on the number of times the first drug is taken, dosage information of a second drug, and information on the number of times the second drug is taken, and may provide specific recommended dosage information and dosage information to prevent a situation in which a patient consumes the first drug and a specific second drug together by providing recommended dosage information based on the dosage information of the first drug, information on the number of times the first drug is taken, information on the dosage information of the second drug, and information on the number of times the second drug is taken. In this case, the dosage information of the first drug and the dosage information of the second drug may include information on the dosage when each of the first drug and the second drug is taken once. In this case, the information on the number of times the first drug is taken and the information on the number of times the second drug is taken may include information on the number of times each of the first drug and the second drug is taken according to time.

[0135] In addition, a system (100) according to one embodiment may extract a first keyword of a first drug and provide recommended drug dosage information including dosage information of a second drug and information on the number of times the second drug is taken based on the first keyword. For example, when a patient is prescribed methotrexate, an anti-rheumatic drug, a drug called folic acid is added to reduce side effects. In this case, regardless of the dosage or number of times methotrexate is administered, the administration of folic acid is recommended when methotrexate is administered. That is, considering the above points, the system (100) may obtain methotrexate as the first keyword of the first drug, which is a rheumatic drug, and provide recommended drug dosage information including dosage information and information on the number of times folic acid is taken as a second drug based on the keyword methotrexate.

[0136] The drug recommended dosage information provided by the system (100) according to one embodiment may be determined based on user input. For example, when a user wants to prescribe a specific disease or drug, the system (100) may obtain user input including drug recommended dosage information and supporting data for drug recommended dosage information (e.g., papers, academic presentation materials, efficacy verification data regarding a specific drug, etc.) and determine drug recommended dosage information.

[0137] A system (100) according to one embodiment may provide recommended drug dosage information according to priority based on the number of times users have prescribed and reviewed it. For example, when a user (e.g., a medical professional) intends to prescribe a specific disease or drug, the system (100) may provide recommended drug dosage information according to priority based on the number of times other users have prescribed or reviewed the recommended drug dosage information related to the disease or drug. Through this, the system (100) can improve the accuracy and speed in the process of providing patient prescription verification information, thereby enabling higher quality medical services. Additionally, a system (100) according to one embodiment may provide recommended drug dosage information according to priority based on the number of times users have prescribed and reviewed it, taking into account user information (e.g., medical professional's affiliated department information and medical professional's affiliated hospital information).

[0138] For example, the system (100) may provide recommended drug dosage information according to priority regarding the number of times prescriptions and reviews have been made by users with gastroenterology department information when the medical staff's department information corresponds to gastroenterology based on user information. For example, the system (100) may provide recommended drug dosage information according to priority regarding the number of times prescriptions and reviews have been made by users with hospital information of the said first hospital when the medical staff's hospital information corresponds to a specific first hospital based on user information. In this case, the hospital information may include information regarding hospitals affiliated with different institutions and information regarding hospitals of different levels (first-level hospital, second-level hospital, tertiary hospital), but is not limited to the specific cases mentioned in the embodiments according to the present disclosure.

[0139] A system (100) according to one embodiment may provide drug recommendation dosage information including evaluation score information based on user input. For example, the system (100) may obtain an evaluation score based on a user's evaluation of specific drug recommendation dosage information, and may provide evaluation score information when providing drug recommendation dosage information based on said evaluation score. The user may input an evaluation score based on an evaluation of high usability, need for supplementation, etc., regarding supporting materials such as papers, academic presentation materials, and efficacy verification data regarding drug recommendation dosage information stored and provided through an electronic device (200), and this may be used for future updates to said supporting materials, etc.

[0140] A system (100) according to one embodiment can determine drug recommendation dosage information based on user input and calculate a user's reward score based on evaluation score information regarding the drug recommendation dosage information. Additionally, the system (100) can determine evaluation score information based on user input and calculate a user's reward score. Through this, the system (100) can calculate a reward score related to the reward to be provided to users who input or evaluate drug recommendation dosage information and supporting data for drug recommendation dosage information, thereby enabling more active input or evaluation of supporting data by users, and ultimately improving the qualitative excellence of the patient information management method.

[0141] FIG. 9 is an exemplary diagram illustrating an embodiment in which prescription verification information is provided by considering the frequency of side effects of a prescribed drug in a patient information management system according to one embodiment. Referring to FIG. 9, the interface (901) provided by the system (100) according to one embodiment may include the frequency of side effects of a drug according to a first keyword (903; 904) of the drug and at least one drug component (903-1; 904-1; 904-2) corresponding to the first keyword. As previously described, the interface (901) may also include an advertisement area (950) that displays an advertisement determined based on user information using an electronic device (200). The system (100) may provide prescription verification information by considering the frequency of side effects of the prescribed drug through the interface (901) based on user input through the frequency of side effects of the prescribed drug interface (902). In relation to FIG. 9 below, it is explained that prescription verification information is provided by considering the frequency of side effects of the drug corresponding to the first keyword (903; 904) based on the illustrated first keyword (903; 904), but as previously examined, the case of using the keyword in the area (930) representing drug information prescribed to the patient within a pre-set period is also included in the embodiment according to the present disclosure.

[0142] An interface (901) provided by a system (100) according to one embodiment may include a first keyword (903; 904) of a drug, at least one drug component (903-1; 904-1; 904-2) corresponding to the first keyword, and information on general side effect symptoms and information on specific side effect symptoms for each of the drug components (903-1; 904-1; 904-2). In this case, information on general side effect symptoms may refer to information on side effect symptoms that generally occur when a patient consumes the drug components. In this case, information on specific side effect symptoms may refer to information on side effect symptoms that appear rarely and occur less frequently than the side effect symptoms that generally occur when a patient consumes the drug components.

[0143] For example, if only general side effect symptom information (913) related to the drug component (903-1) exists, the system (100) can provide general side effect symptom information (913) of the drug component (903-1) through the general side effect symptom category (910). For example, if specific side effect symptom information (924) of the drug component (904-1) exists, the system (100) can provide specific side effect symptom information (924) of the drug component (904-1) through the specific side effect symptom category (920). Additionally, for example, the system (100) can provide general side effect symptom information (914) of the drug component (904-2) through the general side effect symptom category (910), and if both general side effect symptom information (914) and specific side effect symptom information (925) of the drug component (904-2) exist, it can additionally provide all specific side effect symptom information (925) through the specific side effect symptom category (920). A system (100) according to one embodiment can determine whether there is information on general side effects and information on specific side effects corresponding to at least one drug component (903-1; 904-1; 904-2) corresponding to the first keyword as in FIG. 9, and can provide information that exists among such information.

[0144] A system (100) according to one embodiment may provide general side effect symptom information and specific side effect symptom information in order of priority. For example, when a user (e.g., medical staff) intends to prescribe a specific disease or drug, the system (100) may provide general side effect symptom information and specific side effect symptom information that other users have prescribed in relation to the disease or drug, or general side effect symptom information and specific side effect symptom information that has been reviewed, in order of priority, thereby improving the accuracy and speed in the process of providing patient prescription verification information and enabling higher quality medical services.

[0145] General side effect symptom information and specific side effect symptom information provided by the system (100) according to one embodiment may be determined based on user input. For example, the system (100) may allow the user to input and manage supporting materials (e.g., papers, academic presentation materials, efficacy verification data regarding specific drugs, etc.) for general side effect symptom information and specific side effect symptom information.

[0146] The general side effect symptom information and specific side effect symptom information provided by the system (100) according to one embodiment may include evaluation score information based on user input. For example, the system (100) may obtain an evaluation score based on a user's evaluation of specific general side effect symptom information and specific side effect symptom information, and may provide evaluation score information when providing general side effect symptom information and specific side effect symptom information based on the evaluation score. The user may input an evaluation score based on an evaluation of high usability, need for supplementation, etc., regarding the evidence materials such as papers, academic presentation materials, and efficacy verification data regarding the general side effect symptom information and specific side effect symptom information stored and provided through the electronic device (200), and this may be used for future updates to the evidence materials, etc.

[0147] A system (100) according to one embodiment can determine general side effect symptom information and specific side effect symptom information based on user input, and can calculate a user's reward score based on evaluation score information regarding the general side effect symptom information and specific side effect symptom information. Additionally, the system (100) can determine evaluation score information based on user input and calculate a user's reward score. Through this, the system (100) can calculate a reward score related to the reward to be provided to users who input or evaluate the evidence data of general side effect symptom information and specific side effect symptom information, thereby enabling more active input or evaluation of evidence data by users, and ultimately improving the qualitative excellence of the patient information management method.

[0148] FIG. 10 is an exemplary diagram showing an example of providing prescription verification information by considering prescribed drugs and patient pregnancy information in a patient information management method according to one embodiment.

[0149] Referring to FIG. 10, a system (100) according to one embodiment can recognize a second string related to patient condition information in a patient's prescription. The system (100) recognizes a first string related to medication in the patient's prescription described above and can recognize a second string related to patient condition information in the patient's prescription. The system (100) can perform recognition of the second string through optical character recognition similar to the recognition of the first string above. Additionally, the system (100) may obtain text information from a program related to the prescription using a predetermined API and perform recognition of the second string from the text information.

[0150] A system (100) according to one embodiment can obtain a second keyword related to patient condition information based on a second string. Similar to extracting a first keyword of a drug prescribed to a patient based on a first string, the system (100) can obtain a second keyword related to patient condition information based on a second string. A system (100) according to one embodiment can obtain text information from a program related to a prescription using a predetermined API, and then obtain a second keyword after recognizing a second string from the text information. Additionally, the system (100) can obtain patient condition information from a user terminal (300), and then obtain a second keyword after recognizing a second string from the patient condition information of the patient. Additionally, the system (100) can obtain a second keyword based on information input through a user input interface. A system (100) according to one embodiment can provide prescription verification information based on drug components related to the first keyword and patient condition information related to the second keyword. Patient status information may include at least one of the patient's pregnancy information, patient's breastfeeding information, patient's kidney function information, patient's liver function information, and patient's age information. Additionally, patient status information may include information regarding the specific symptoms of the mentioned patient, as well as information regarding the type of CYP enzyme the patient possesses, for example, among the CYP enzymes that metabolize or decompose drugs in the liver. Since variations in CYP (cytochrome) enzymes in each patient (e.g., variations that increase or decrease the function of the enzyme) can affect drug metabolism or decomposition and cause significant differences in the concentration of the drug in the blood, it is necessary to consider the type of CYP enzyme the patient possesses. More specifically, accordingly, the system (100) may provide information regarding the recommended dosage of the drug based on a second keyword related to patient status information that includes information regarding the type of CYP enzyme the patient possesses.Through this, it is possible to predict the diversity of drug responses caused by individual genetic factors, such as the establishment of individual dosage regimens for proton pump inhibitors based on CYP2C19 genotypes, and the establishment of initial dosage regimens for drugs in the psychiatric field based on genotypes such as CYP2D6 and CYP2C19, and to provide prescription verification information by taking this into account.

[0151] A system (100) according to one embodiment may obtain information on a patient's past condition and information on medications previously prescribed to the patient from a user terminal (300). In this case, the information on the patient's past condition may include information on the patient's physical condition that is not included in the second string related to the patient's condition information. The information on medications previously prescribed to the patient may include information on medications prescribed to the patient prior to the prescription of the patient's prescription subject to verification, which is not included in the first string related to medications in the patient's prescription. The system (100) may provide prescription verification information based on the information on the patient's past condition and information on medications previously prescribed to the patient obtained from the user terminal (300). The system (100) may obtain information on the patient's recent condition and recent medication prescription history through the user terminal (300), which are either entered directly by the patient or provided through information providers such as the Health Insurance Review & Assessment Service or various insurance companies. Alternatively, the system (100) can obtain the patient's personal health record (PHR) through an image of a medical record copied by the hospital or information obtained through the user terminal (300) used by the patient using the user terminal (300), and obtain information on the patient's past condition and information on medications previously prescribed to the patient.

[0152] For example, the system (100) can obtain information about the patient's past condition through the user terminal (300), such as that the patient has rheumatoid arthritis. For example, the system (100) can obtain information about the medication previously prescribed to the patient through the user terminal (300), such as that the patient has been prescribed steroids (prednisolone) and analgesic anti-inflammatory drugs (naproxen). For example, the system (100) can obtain information about the patient's condition through the user terminal (300), such as that the patient has a mutation from G to A at the 1639th position of the VKOCR1 gene. For example, the system (100) can obtain a second keyword, such as atrial fibrillation, through information included in a second string related to the patient's condition information in the prescription of a patient who visited the hospital because of heart palpitations, and can extract warfarin, a blood clot prevention drug, and diltiazem, for heart rate control, as the first keywords of the medication prescribed to the patient. Considering the interactions between the drug prescriptions for rheumatoid arthritis and the drug prescriptions for atrial fibrillation, the risk of gastrointestinal bleeding may increase due to the interaction between Prednisolone and Warfarin and the interaction between Naproxen and Warfarin. Additionally, the interaction between diltiazem and prednisolone has an enhancing effect on CYP3A4 (drug metabolizing enzyme) function, which promotes the metabolism of diltiazem metabolized by CYP3A4, thereby reducing the blood concentration of diltiazem. Consequently, the risk of poor heart rate control may increase due to the drug prescriptions for rheumatoid arthritis. Furthermore, based on the results of obtaining the patient's genetic information through the user terminal (300), since VKOCR1 1639 AA is homozygous, the blood concentration may increase unexpectedly after administering a standard dose of warfarin, which may increase the risk of bleeding.A system (100) according to one embodiment can provide alternative drug information or drug dosage information and dosage frequency information to prevent side effects based on the patient's past condition information obtained from a user terminal (300) and drug information previously prescribed to the patient, thereby providing more reliable and safe prescription verification information through linkage with an external electronic device.

[0153] Figure 10 below describes a case where a second keyword regarding the patient's pregnancy information is obtained, and prescription verification information is provided based on the first keyword of the drug and the second keyword regarding the patient's pregnancy information.

[0154] A system (100) according to one embodiment may provide prescription verification information based on a patient's pregnancy information through an interface (1001). The system (100) may provide prescription verification information based on a patient's pregnancy information through the interface (1001) based on user input through the patient's pregnancy information interface (1002). As previously described, the interface (1001) may also include an advertising area (1050) that displays an advertisement determined based on user information using an electronic device (200). Hereinafter, with respect to FIG. 10, prescription verification information based on a patient's pregnancy information is described as being provided based on the drug components corresponding to the first keyword (1003; 1004) based on the illustrated first keyword (1003; 1004); however, as previously examined, the case of using a keyword in an area (1030) indicating drug information prescribed to a patient within a preset period is also included in the embodiments according to the present disclosure.

[0155] An interface (1001) provided by a system (100) according to one embodiment may include a first keyword (1003; 1004) of a drug, at least one drug component (1003-1; 1004-1; 1004-2) corresponding to the first keyword, drug components (1003-1; 1004-1; 1004-2), drug grades considering the patient's pregnancy information, and drug safety information. In one embodiment, the drug grades considering the patient's pregnancy information may include country-specific drug grades according to the regulations of the U.S. Food and Drug Administration (FDA), the Australian Therapeutic Goods Administration (AUS-TGA), and the Korea Food and Drug Administration (KFDA). However, the mentioned country-specific drug grades are merely exemplary and are not limited to the specific cases mentioned in the embodiments according to the present disclosure. A system (100) according to one embodiment may provide drug safety information (1024) and alternative drug information when there is information that the prescription is inappropriate for a pregnant patient, taking into account the drug component (1004-1) and the drug grade (1014) that takes into account the patient's pregnancy information. A system (100) according to one embodiment may provide drug component, drug grade that takes into account the patient's pregnancy information, and alternative drug information as shown in Table 2, for example, through an interface (1001).

[0156] Drug Ingredients FDA Drug Class AUS-TGA Drug Class Alternative Drug Information Distigmine Cpyridostigmine clonidine CB3 methyldopa and guanfacine Rilmendine C methyldopa and guanfacine clarithromycin CB3 Josomycin, azithromycin, and erythromycin Midcamycin C Josomycin, azithromycin, and erythromycin deferiprone CD desferrioxamine,deferasiroxtriamcinoloneCABudesonide (for inhaled triamcinolone)beclomethasoneCB3budesonidefluticasone furoate / propionateCB3BudesonidemometasoneB3BudesonidevindesineDDvinblastineDvincristineDvinflunineDvinorelbine tartrateDvinorelbine tartratecilostazolCB3iloprostCB3treprostinilCB3dipyridamoleB~CB1betahistineBB2epoprostenolBB1sildenafil citrateBB1glyceryl trinitrateB2isoxsuprineCnicotinyl alcoholB1nitric oxideB2phenoxybenzamineB2phentolamineB1tadalafilB1vardenafilB3nonoxinol 9AoctoxinolAmethenamineAdasatinibDDerlotinibDCgefitinibDCimatinibDDlapatinibDCnilotinibDDsorafenibDDsunitinibDDacalabrutinibCafatinibCalectinibDasciminib hydrochlorideDaxitinibDbrigatinibDcrizotinibDdabrafenib mesilateDentrectinibDibrutinibDlarotrectinibDlenvatinib_DlorlatinibDmidostaurinDnintedanib esilateD,

[0157] However, drug grades and alternative drug information considering drug ingredients, patient pregnancy information, such as those in Table 2, are merely exemplary, and the embodiments according to the present disclosure are not limited to any specific case in Table 2. The alternative drug information provided by the system (100) according to one embodiment may be determined based on user input. Additionally, the system (100) may provide alternative drug information according to priority regarding the number of times users have prescribed and reviewed. The system (100) may provide alternative drug information including evaluation score information based on user input. The system (100) may determine alternative drug information based on user input and calculate the user's reward score based on the evaluation score information for the alternative drug information.

[0158] FIG. 11 is an exemplary diagram illustrating an embodiment in which prescription verification information is provided by considering prescribed medication and patient breastfeeding information in a patient information management method according to one embodiment. Hereinafter, FIG. 11 describes a case in which prescription verification information is provided based on the first keyword of the medication and the second keyword regarding the patient's breastfeeding information when a second keyword regarding the patient's breastfeeding information is obtained.

[0159] A system (100) according to one embodiment may provide prescription verification information based on the patient's breastfeeding information through an interface (1101). The system (100) may provide prescription verification information based on the patient's breastfeeding information through the interface (1101) based on user input through the patient's breastfeeding information interface (1102). As previously described, the interface (1101) may also include an advertisement area (1150) that displays an advertisement determined based on user information using the electronic device (200). With respect to FIG. 11 below, it is described that prescription verification information based on the patient's breastfeeding information is provided based on the drug components (1103-1; 1104-1; 1104-2; 1105-1) corresponding to the first keyword (1103; 1104) based on the illustrated first keyword (1103; 1104; 1105). However, as previously examined, the case of using keywords in the area (1130) representing drug information prescribed to the patient within a pre-set period is also included in the embodiments according to the present disclosure.

[0160] An interface (1101) provided by a system (100) according to one embodiment may include a first keyword (1103; 1104; 1105) of a drug, at least one drug component (1103-1; 1104-1; 1104-2) corresponding to the first keyword, drug grades considering the drug component (1103-1; 1104-1; 1104-2; 1105-1) and the patient's breastfeeding information, drug safety information, and alternative drug information. If there is information that the prescription is inappropriate for a breastfeeding patient, considering the drug component (1105-1) and the drug grade (1115) within the drug grade category (1110) considering the patient's breastfeeding information, the system (100) according to one embodiment may provide drug safety information (1125) within the safety category (1120). A system (100) according to one embodiment can provide, for example, through an interface (1101), drug ingredients such as those in Table 3, drug grades considering the patient's breastfeeding information, drug stability information, and alternative drug information.

[0161] 약제 성분약제 등급안정 정보대안 약제 정보AcebutololHigh RiskPoorly safe. Evaluate carefully.Use safer alternative or interrupt breastfeeding 3 to 7 T ½ (elimination half-lives).Read the Comment.Labetalol Hydrochloride (Safe. Compatible. Minimal risk for breastfeeding and infant.)Metoprolol (Safe. Compatible. Minimal risk for breastfeeding and infant.)Oxprenolol Hydrochloride (Safe. Compatible. Minimal risk for breastfeeding and infant.)Propranolol (Safe. Compatible. Minimal risk for breastfeeding and infant.)acitretinHigh RiskPoorly safe. Evaluate carefully.Use safer alternative or interrupt breastfeeding 3 to 7 T ½ (elimination half-lives).Read the Comment.Adalimumab (Safe. Compatible. Minimal risk for breastfeeding and infant.)Calcipotriol (Safe. Compatible. Minimal risk for breastfeeding and infant.)Certolizumab (Safe. Compatible. Minimal risk for breastfeeding and infant.)Ciclosporin (Safe. Compatible. Minimal risk for breastfeeding and infant.)Clobetasol Propionate (Safe. Compatible.Minimal risk for breastfeeding and infant.)Etanercept (Safe. Compatible. Minimal risk for breastfeeding and infant.)Infliximab (Safe. Compatible. Minimal risk for breastfeeding and infant.)Pimecrolimus (Safe. Compatible. Minimal risk for breastfeeding and infant.)Tacrolimus (topical use) (Safe. Compatible. Minimal risk for breastfeeding and infant.)Tazarotene (Possibly safe. Probably compatible. Mild risk possible. Follow up recommended. Read the Comment.)Tretinoin (topical use) (Safe. Compatible. Minimal risk for breastfeeding and infant.)Triamcinolone (topical use) (Safe. Compatible. Minimal risk for breastfeeding and infant.)UV-A and UV-B Rays (Safe. Compatible. Minimal risk for breastfeeding and infant.)Ustekinumab (Safe. Compatible. Minimal risk for breastfeeding and infant.)Acamprosate CalciumLow RiskPossibly safe. Probably compatible. Mild risk possible. Follow up recommended. Read the Comment.Naltrexone Hydrochloride (Safe. Compatible. Minimal risk for breastfeeding and infant.)AcemannanLow RiskPossibly safe. Probably compatible. Mild risk possible. Follow up recommended. Read the Comment.Lactulose (Safe. Compatible. Minimal risk for breastfeeding and infant.)AcetohexamideLow RiskPossibly safe. Probably compatible. Mild risk possible. Follow up recommended. Read the Comment.Glibenclamide (Safe. Compatible. Minimal risk for breastfeeding and infant.)Hypocaloric Diet (Safe. Compatible. Minimal risk for breastfeeding and infant.)Insulin (Safe. Compatible. Minimal risk for breastfeeding and infant.)Maternal Sport (Safe. Compatible. Minimal risk for breastfeeding and infant.)Metformin Hydrochloride (Safe. Compatible. Minimal risk for breastfeeding and infant.)Tolbutamide (Safe. Compatible. Minimal risk for breastfeeding and infant.)AbataceptLow RiskPossibly safe. Probably compatible. Mild risk possible. Follow up recommended. Read the Comment.Etanercept (Safe. Compatible. Minimal risk for breastfeeding and infant.)Infliximab (Safe. Compatible.Minimal risk for breastfeeding and infant.)AcemetacinLow RiskPossibly safe. Probably compatible. Mild risk possible. Follow up recommended. Read the Comment.Diclofenac (Safe. Compatible. Minimal risk for breastfeeding and infant.)Ibuprofen (Safe. Compatible. Minimal risk for breastfeeding and infant.)Indomethacin; Indometacin (Safe. Compatible. Minimal risk for breastfeeding and infant.)AcrivastineLow RiskPossibly safe. Probably compatible. Mild risk possible. Follow up recommended. Read the Comment.Cetirizine Hydrochloride (Safe. Compatible. Minimal risk for breastfeeding and infant.)Loratadine (Safe. Compatible. Minimal risk for breastfeeding and infant.)AbciximabLow RiskPossibly safe. Probably compatible. Mild risk possible. Follow up recommended. Read the Comment.Aspirin (Possibly safe. Probably compatible. Mild risk possible. Follow up recommended. Read the Comment.)Heparin (Safe. Compatible. Minimal risk for breastfeeding and infant.).

[0162] However, drug grades considering drug ingredients, patient breastfeeding information, drug stability information, and alternative drug information such as those in Table 3 are merely exemplary, and the embodiments according to the present disclosure are not limited to any specific case in Table 3. The alternative drug information provided by the system (100) according to one embodiment may be determined based on user input. Additionally, the system (100) may provide alternative drug information according to priority regarding the number of times users have prescribed and reviewed. The system (100) may provide alternative drug information including evaluation score information based on user input. The system (100) may determine alternative drug information based on user input and calculate the user's reward score based on the evaluation score information for the alternative drug information.

[0163] FIG. 12 is an exemplary diagram showing an embodiment in which prescription verification information is provided by considering the prescribed drug and patient kidney function information in a patient information management method according to one embodiment.

[0164] A system (100) according to one embodiment can obtain a second keyword regarding patient kidney function information based on a second string. In FIG. 12 below, the case in which prescription verification information is provided based on the first keyword of the drug and the second keyword regarding patient kidney function information when the second keyword regarding patient kidney function information is obtained is described. For example, the second string regarding the patient's kidney function information may include the names of kidney diseases such as chronic kidney disease (CKD), acute kidney injury (AKI), glomerulonephritis, polycystic kidney disease (PKD), nephrotic syndrome, interstitial nephritis, diabetic nephropathy, hypertensive nephropathy, nenal artery stenosis, renal tubular acidosis, minimal change disease, lupus nephritis, etc., and the second keyword may be obtained based on the said second string, but the method of providing prescription verification information according to one embodiment is not limited to specific cases. For example, the system (100) can obtain information on the patient's kidney function based on an image obtained from a blood test graph on the patient's prescription, and if it is determined that there is an abnormality in the patient's kidney function, it can obtain a second keyword related to kidney disease, such as an example of a creatinine level, an estimated GFR level, or a urine test.

[0165] A system (100) according to one embodiment may provide prescription verification information based on patient kidney function information through an interface (1201). The system (100) may provide prescription verification information based on patient kidney function information through the interface (1201) based on user input through the patient kidney function information interface (1202). As previously described, the interface (1201) may also include an advertisement area (1250) that displays an advertisement determined based on user information using the electronic device (200). Hereinafter, with respect to FIG. 10, it is described that prescription verification information based on patient kidney function information is provided based on drug components corresponding to the first keywords (1203; 1204; 1205) based on the illustrated first keywords (1203; 1204; 1205); however, as previously examined, the case of using keywords in an area (1230) indicating drug information prescribed to the patient within a preset period is also included in the embodiments according to the present disclosure.

[0166] An interface (1201) provided by a system (100) according to one embodiment may include a first keyword (1203; 1204; 1205) of a drug, at least one drug component (1203-1; 1204-2; 1205-3) corresponding to the first keyword, drug information when kidney function is normal, drug information when kidney function is problematic, and alternative drug information. For example, the system (100) may provide drug information (1213) when the patient's kidney function is normal through a kidney normal function category (1210) related to the drug component (1203-1). Additionally, it may provide drug information (1223) and alternative drug information (1233) when the patient's kidney function is problematic. For example, the system (100) may provide information on the drug when the patient's kidney function is normal (1214) and information on the drug when the patient's kidney function is problematic (1224) and information on alternative drugs (1234) in relation to the drug component (1204-1). For example, the information on the drug when there is a problem with kidney function included in the interface (1201) provided by the system (100) may include information on the drug dosage according to the glomerular filtration rate (GFR) related to kidney function, and for example, the information on the drug when there is a problem with kidney function may include information to reduce the drug dosage when kidney function is abnormal (e.g., GFR less than 60) compared to the drug dosage when kidney function is normal (e.g., GFR 60 or higher, usually between 90 and 100).

[0167] A system (100) according to one embodiment may provide a protocol for reducing the dosage of medication due to a decline in the patient's kidney function through medication information and alternative medication information when there is a problem with kidney function, or provide prescription verification information to prevent the use of analgesics and anti-inflammatory drugs frequently used for joint pain. A system (100) according to one embodiment may provide, for example, medication ingredients as shown in Table 4, medication information when the patient's kidney function is normal, medication information when there is an abnormality in the patient's kidney function, and alternative medication information through an interface (1201).

[0168] 약제 성분신장 기능 정상일 때의 약제 정보신장 기능에 문제가 있을 때의 약제 정보대안 약제 정보Abacavir600 mg daily in 1 or 2 divided doses20~50: Same dose as for normal renal function.10~20: Same dose as for normal renal function.<10: Same dose as for normal renal function.APD / CAPD: Unknown dialysability. Same dose as for normal renal function.HD: Unlikely to be dialysed. Same dose as for normal renal function.HDF / High flux: Not dialysed. Same dose as for normal renal function.CAV / VVHD: Unknown dialysability. Same dose as for normal renal function.AbciximabIV bolus: 250 mcg / kg then by infusion at 0.125 mcg / kg / minute for 12 hours after intervention (maximum10mcg / minute).20~50: Same dose as for normal renal function.10~20: Same dose as for normal renal function.<10: Same dose as for normal renal function. Use with caution. See ‘Other information’.APD / CAPD: Unlikely to be dialysed. Dose as in GFR<10 mL / min.HD: Unlikely to be dialysed. Dose as in GFR<10 mL / min.HDF / High flux: Unlikely to be dialysed. Dose as in GFR<10 mL / min.CAV / VVHD: Unlikely to be dialysed. Same dose as for normal renal function.Abiraterone acetate1000 mg daily20~50: Same dose as for normal renal function.10~20: Same dose as for normal renal function.<10: Same dose as for normal renal function.APD / CAPD: Unlikely to be dialysed. Same dose as for normal renal function.HD: Not dialysed. Dose as in normal renalHDF / High flux: Not dialysed. Dose as in normal renal function.CAV / VVHD: Unlikely to be dialysed. Same dose as for normal renal function.Acamprosate calcium- >60 kg: 666 mg 3 times a day- <60 kg: 666 mg at breakfast, 333 mg at midday and 333 mg at night30~50: 333 mg 3 times daily.10~30:333 mg twice daily. See 'Other information'.<10: 333 mg once daily. See 'Other information'.APD / CAPD: Dialysed. Dose as in GFR<10 mL / min.HD: Dialysed. Dose as in GFR<10 mL / min.HDF / High flux: Dialysed. Dose as in GFR<10 mL / min.CAV / VVHD: Dialysed. Dose as in GFR=10-30mL / min.Acarbose50~200 mg 3 times a day25~50: Same dose as for normal renal function.10~25: Avoid.<10: Avoid.APD / CAPD: Unknown dialysability. Avoid.HD: Unknown dialysability. Avoid. See 'Other information'.HDF / High flux: Unknown dialysability. Avoid. See 'Other information'.CAV / VVHD: Unknown dialysability. Avoid.Aceclofenac100 mg twice daily20~50: Same dose as for normal renal function but use with caution.10~20: Same dose as for normal renal function but avoid if possible.<10: Same dose as for normal renal function but only if on dialysis.APD / CAPD: Not dialysed. Same dose as for normal renal function. See‘Other information’.HD: Not dialysed. Same dose as for normal renal function. See 'Other information'.HDF / High flux: Unknown dialysability. Same dose as for normal renal function. See 'Other information'.CAV / VVHD: Not dialysed. Same dose as for normal renal function.Acenocoumarol (nicoumalone)- Initially: 2~4 mg on 1st day without a loading dose;- Loading dose: 6 mg on 1st day then 4 mg on 2nd day- Maintenance dose usually 1~8 mg daily according to INR20~50: Same dose as for normal renal function.10~20: Same dose as for normal renal function.<10: Same dose as for normal renal function.APD / CAPD: Unknown dialysability. Dose as in Unknown dialysability. Same dose as for normal renal function.HD: Unknown dialysability. Same dose as for normal renal function.HDF / High flux: Unknown dialysability. Same dose as for normal renal function.CAV / VVHD: Unknown dialysability. Same dose as for normal renal function.Aciclovir oral(ORAL)- Simplex treatment: 200~400 mg 5 times daily- Prophylaxis (immunocompromised): 200~400 mg every 6 hours- Suppression: 200 mg every 6 hours, or 400 mg every 12 hours- Zoster: 800 mg 5 times a day for 7 days25~50: Same dose as for normal renal function.10~25: Simplex: 200 mg 3-4 times daily Zoster: 800 mg every 8-12 hours<10: Simplex: 200 mg every 12 hours Zoster: 400-800 mg every 12 hoursAPD / CAPD: Not dialysed. Dose as in GFR<10 mL / min.HD: Dialysed. Dose as in GFR<10 mL / min. Give dose after dialysis.HDF / High flux: Dialysed. Dose as in GFR<10 mL / min. Give dose after dialysis.CAV / VVHD: Dialysed. Dose as in GFR=10-25 mL / min. See 'Other information'.Acipimox250 mg 2 or 3 times daily40~80: 250 mg daily.20~40: 250 mg alternate days. See 'Other information'.<20: See 'Other information'.APD / CAPD: Likely dialysability. Dose as in GFR<20 mL / min.HD: Dialysed. Dose as in GFR<20 mL / min.HDF / High flux: Dialysed. Dose as in GFR<20 mL / min.CAV / VVHD: Dialysed. Dose as in GFR=20-40 mL / min.Acitretin- Initially: 25~30 mg daily (Darier's disease 10 mg daily) for 2~4 weeks, adjusted according to response.- Ongoing: usually 25~50 mg / day (maximum 75mg) for further 6~8 weeks. (In Darier's disease and ichthyosis not more than 50 mg daily for up to 6 months.)20~50: No data available. Assume Same dose as for normal renal function. See 'Other information'.10~20: No data available. Assume dose as in normal renal function. See 'Other information'.<10: No data available. Assume Same dose as for normal renal function. See 'Other information'.APD / CAPD: Unlikely to be dialysed. Dose as in GFR<10 mL / min.HD: Not dialysed. Dose as in GFR<10 mL / min.HDF / High flux: Unlikely to be dialysed. Dose as in GFR<10 mL / min.CAV / VVHD: Unknown dialysability. Dose as in GFR=10-20 mL / min.Adalimumab- 40 mg on alternate weeks increased to weekly if monotherapy for rheumatoid arthritis- Crohn's disease and ulcerative colitis: see product literature- Psoriasis: 80 mg initially then 40 mg on alternate weeks- Other conditions: 40 mg on alternate weeks20~50: Use with caution. See 'Other information'.10~20: Use with caution. See 'Other information'.<10: Use with caution. See 'Other information'.APD / CAPD: Unlikely to be dialysed. Dose as in GFR<10 mL / min.HD: Unlikely to be dialysed. Dose as in GFR<10 mL / min.HDF / High flux: Unlikely to be dialysed. Dose as in GFR<10 mL / min.CAV / VVHD: Unlikely to be dialysed. Dose as in GFR=10-20 mL / min.Adefovir dipivoxil10 mg once daily30~50: 10 mg every 48 hours.10~30: 10 mg every 72 hours.<10: 10 mg every 72 hours. See 'Other information'.APD / CAPD: Unknown dialysability. Dose as in GFR<10 mL / min.HD: Dialysed. 10 mg weekly or after a cumulative total of 12 hours dialysis. See 'Other information'.HDF / High flux: Dialysed. Dose as in GFR<10 mL / min.CAV / VVHD: Unknown dialysability. Dose as in GFR=10-30 mL / min.epinephrine0.01~1 mcg / kg / minute20~50: Same dose as for normal renal function.10~20: Same dose as for normal renal function.<10: Dose as in normal renal function.APD / CAPD: Not dialysed. Same dose as for normal renal function.HD: Not dialysed. Same dose as for normal renal function.HDF / High flux: Unknown dialysability. Dose as in normal renal function.CAV / VVHD: Not dialysed.Same dose as for normal renal function.Afatinib40~50 mg once daily20~50: Same dose as for normal renal function.15~20: Same dose as for normal renal function.<15: Use with caution. See 'Other information'.APD / CAPD: Unknown dialysability. Dose as in GFR<15 mL / min.HD: Unknown dialysability. Dose as in GFR<15 mL / min. See 'Other information'.HDF / High flux: Unknown dialysability. Dose as in GFR<15 mL / min. See 'Other information'.CAV / VVHD: Unknown dialysability. Dose as in GFR=15-20 mL / min.Agalsidase alfa (Replagal)0.2 mg / kg, rounded to the nearer full vial every 2 weeks.Vials available as 3.5 mg.30~50: Same dose as for normal renal function.10~30: Same dose as for normal renal function.<10: Same dose as for normal renal function.APD / CAPD: Unlikely to be dialysed. Same dose as for normal renal function.HD: Unlikely to be dialysed. Same dose as for normal renal function.HDF / High flux: Unlikely to be dialysed. Same dose as for normal renal function.CAV / VVHD: Unlikely to be dialysed.Same dose as for normal renal function.Agalsidase beta (Fabrazyme)1 mg / kg, rounded to the nearest full vial every 2 weeks.Available as 5 mg and 35 mg vials.30~50: Same dose as for normal renal function.10~30: Same dose as for normal renal function.<10: Same dose as for normal renal function.APD / CAPD: Unlikely to be dialysed. Same dose as for normal renal functionHD: Unlikely to be dialysed. Same dose as for normal renal functionHDF / High flux: Unlikely to be dialysed. Same dose as for normal renal functionCAV / VVHD: Unlikely to be dialysed. Same dose as for normal renal function.

[0169] However, drug ingredients such as those in Table 4, drug information when the patient's kidney function is normal, drug information when the patient's kidney function is abnormal, and alternative drug information are merely exemplary, and the embodiments according to the present disclosure are not limited to any specific case in Table 4. Drug information when the patient's kidney function is normal, drug information when the patient's kidney function is abnormal, and alternative drug information provided by the system (100) according to one embodiment may be determined based on user input. Additionally, the system (100) may provide drug information when the patient's kidney function is normal, drug information when the patient's kidney function is abnormal, and alternative drug information, respectively, according to priority regarding the number of times users have prescribed and reviewed. The system (100) may provide drug information when the patient's kidney function is normal, drug information when the patient's kidney function is abnormal, and alternative drug information, respectively, including evaluation score information based on user input. The system (100) determines, based on user input, drug information when the patient's kidney function is normal, drug information when the patient's kidney function is abnormal, and alternative drug information, respectively, and can calculate the user's reward score based on evaluation score information for the corresponding information.

[0170] FIG. 13 is an exemplary diagram showing an embodiment in which prescription verification information is provided by considering functional information between a prescribed drug and a patient in a patient information management method according to one embodiment.

[0171] A system (100) according to one embodiment can obtain a second keyword regarding patient liver function information based on a second string. In FIG. 13 below, the case in which prescription verification information is provided based on the first keyword of the drug and the second keyword regarding patient liver function information is obtained. For example, the second string regarding patient liver function information may include the name of a liver disease or an abbreviation of the name, such as cirrhosis, liver cancer, alcoholic liver disease, liver fibrosis, hepatic encephalopathy, primary biliary cirrhosis (PBC), primary sclerosing cholangitis (PSC). Additionally, the second keyword may be obtained based on the second string, but the method of providing prescription verification information according to one embodiment is not limited to a specific case. For example, the system (100) can obtain liver function information of a patient based on an image obtained from a blood test graph on the patient's prescription, and if it is determined that there is an abnormality in the patient's liver function, it can obtain second keywords related to liver disease, such as AST / ALT, albumin levels, prothrombin time, etc., which represent liver function.

[0172] A system (100) according to one embodiment may provide prescription verification information based on patient function information through an interface (1301). The system (100) may provide prescription verification information based on patient function information through the interface (1301) based on user input through the patient function information interface (1302). As previously described, the interface (1301) may also include an advertisement area (1350) that displays an advertisement determined based on user information using an electronic device (200). In relation to FIG. 13, it is described below that prescription verification information based on patient function information is provided based on the drug components (1303-1; 1304-1; 1304-2) corresponding to the first keyword based on the illustrated first keyword (1303; 1304); however, as previously examined, the case of using a keyword in an area (1330) indicating drug information prescribed to a patient within a preset period is also included in the embodiments according to the present disclosure.

[0173] An interface (1301) provided by a system (100) according to one embodiment may include a first keyword (1303; 1304) of a drug, at least one drug component (1303-1; 1304-1; 1304-2) corresponding to the first keyword, and drug dosage suggestion information when there is a problem with liver function. A system (100) according to one embodiment may provide a drug dosage reduction protocol according to the patient's liver function decline through the drug dosage suggestion information when there is a problem with liver function. For example, the system (100) may provide drug dosage suggestion information (1310) when there is a problem with the patient's liver function in relation to the drug component (1304-1).

[0174] A system (100) according to one embodiment may provide information on drug components and drug dosage suggestions when the patient's liver function is abnormal, such as those in Table 5, for example, through an interface (1301).

[0175] 약제 성분약제 용량 제안 정보AcetaminophenUse extreme caution; avoid use as much as possible; limit therapy to short-term use at doses not to exceed 2 g / day|AllopurinolDose reduction 50%AlmotriptanInitial: 6.25 mg PO|Not to exceed 12.5 mg / day|AmitriptylineStarting at 50% of normal dose and maintenance dose adjusted according to clinical effect and adverse effectsAmlodipineLower initial dose may be required for patients with hepatic impairment|Consider starting with 2.5 mg / day PO|AnagrelideModerate: Start with 0.5 mg / day for at least 1 week; increase PRN no more frequently than 0.5 mg / day / week|Severe (Child-Pugh C): Contraindicated|AtomoxetineMild (Child-Pugh class A): No dosage adjustment necessary|Moderate (Child-Pugh class B): Decrease initial and target dosage by 50%|Severe (Child-Pugh class C): Decrease initial and target dosage by 75%|AxitinibMild (Child-Pugh A): No adjustment of initial dose is required|Moderate (Child-Pugh B): Decrease initial dose by ~50%; subsequent doses can be increased or decreased based on individual safety and tolerability|Severe (Child-Pugh C): Not studied|BortezomibModerate-to-severe (bilirubin >1.5x ULN): Reduce to 0.7 mg / m² in the first cycle; consider dose escalation to 1 mg / m² or further dose reduction to 0.5 mg / m² in subsequent cycles based on tolerability|BosutinibMild to severe (Child-Pugh A to C): 200 mg PO qDay|There are no clinical data for efficacy at 200-mg / day |Brexpiprazole|Moderate-to-severe hepatic impairment (Child-Pugh 7)|MDD: Not to exceed 2 mg / day|Schizophrenia: Not to exceed 3 mg / day||BrivaracetamAll stages: Decrease starting dose to 25 mg BID and do not exceed 75 mg BID (150 mg / day)|CabazitaxelMild (total bilirubin [TB] >1 to <1.5x ULN or AST >1.5x ULN): Administer at a dose of 20 mg / m 2|Moderate (TB >1.5 to 3x ULN and any AST): Reduce dose to 15 mg / m 2 ; based on tolerability; efficacy of this dose is unknown|Severe (TB >3x ULN): Contraindicated|.

[0176] However, drug information and drug dosage suggestion information when the patient's liver function is abnormal, such as those in Table 5, are merely exemplary, and the embodiments according to the present disclosure are not limited to any specific case in Table 5. Each of the drug information and drug dosage suggestion information when the patient's liver function is abnormal, provided by the system (100) according to one embodiment, may be determined based on user input. Additionally, the system (100) may provide each of the drug information and drug dosage suggestion information when the patient's liver function is abnormal according to priority regarding the number of times users have prescribed and reviewed. The system (100) may provide each of the drug information and drug dosage suggestion information when the patient's liver function is abnormal, including evaluation score information based on user input. The system (100) may determine the drug information and drug dosage suggestion information when the patient's liver function is abnormal based on user input, and may calculate the user's reward score based on the evaluation score information for each of the said information.

[0177] FIG. 14 is an exemplary diagram illustrating an embodiment in which prescription verification information is provided by considering the prescribed drug and the patient's age information in a patient information management method according to one embodiment. A system (100) according to one embodiment can obtain a second keyword regarding patient age information based on a second string. Hereinafter, FIG. 14 describes a case in which prescription verification information is provided based on the first keyword of the drug and the second keyword regarding patient age information when the second keyword regarding patient age information is obtained.

[0178] A system (100) according to one embodiment may provide prescription verification information based on patient age information through an interface (1401). The system (100) may provide prescription verification information based on patient age information through the interface (1401) based on user input through a patient age information interface (1402). As previously described, the interface (1401) may also include an advertisement area (1450) that displays an advertisement determined based on user information using an electronic device (200). Hereinafter, with respect to FIG. 14, it is described that prescription verification information considering patient age information of a drug component (1403-1; 1404-1) corresponding to the first keyword is provided based on the illustrated first keyword (1403; 1404); however, as previously examined, the case of using a keyword in an area (1430) indicating drug information prescribed to a patient within a preset period is also included in the embodiments according to the present disclosure.

[0179] An interface (1401) provided by a system (100) according to one embodiment may include a first keyword (1403; 1404) of a drug, a drug component (1403-1; 1404-1) that compares the first keyword to a predefined keyword, drug recommendation information considering patient age information, and basis information for drug recommendation. For example, based on a second keyword regarding patient age information, if the patient is an elderly patient requiring caution in prescription, the system (100) may provide drug recommendation information (1414) and basis information for drug recommendation (1424) based on the drug component (1404-1). In one embodiment, drug recommendation information that the system (100) may additionally provide through the interface (1401) according to the drug component may be as shown in the following table.

[0180] 약제 성분약제 추천 정보ChlorpheniramineAvoid, Change to 2nd anti-Histamine (Ebastine, Fexofenadine, Levocetirizine, Loratadine. Etc)HydroxyzineAvoid, Change to 2nd anti-Histamine (Ebastine, Fexofenadine, Levocetirizine, Loratadine. Etc)TriprolidineAvoid, Change to 2nd anti-Histamine (Ebastine, Fexofenadine, Levocetirizine, Loratadine. Etc)NitrofurantoinAvoid in individuals with CrCl <30 mL / min or for long-term suppression.AspirinAvoid initiating aspirin for primary prevention of cardiovascular disease.DoxazosinAvoid use as an antihypertensive. (for BPH management, change to tamsulosin, Silodosin, Naftopidil)PrazosinAvoid use as an antihypertensive. (for BPH management, change to tamsulosin, Silodosin, Naftopidil)TerazosinAvoid use as an antihypertensive. (for BPH management, change to tamsulosin, Silodosin, Naftopidil)ClonidineAvoid, as first-line treatment for hypertension.GuanfacineAvoid, as first-line treatment for hypertension.DigoxinAvoid this rate control agent as first-line therapy for atrial fibrillation.Avoid as first-line therapy for heart failure. If used for atrial fibrillation or heart failure.Avoid dosages >0.125 mg / day.AmitriptylineAvoid, for Depression (change to SSRI(Escitalopram, Sertaline...), SNRI(Duloxetine..) or Mirtazapine. for Neuropathic pain (chage to SNRI(Duloxetine..), Gabapentin, or Pregabalin)DiazepamAvoid (Tapering and Stop). Change to shor-term (Lorazepam, Alprazolam)DuloxetineGFR < 30 ml / min: Avoid,GabapentinGFR < 60 ml / min: reduced dose,LevetiracetamGFR < 80 ml / min: reduced dose,PregabalinGFR < 60 ml / min: reduced dose,TramadolGFR < 30 ml / min: Immediate release: reduce dose / Extended-release: avoidCimetidineGFR < 50 ml / min: reduced dose, Change to Famotidine, RebamipideFamotidineGFR < 50 ml / min: reduced dose,NizatidineGFR < 50 ml / min: reduced dose,ColchicineGFR < 30 ml / min: reduced dose,ProbenecidGFR < 30 ml / min: Avoid.

[0181] However, drug ingredients and drug recommendation information such as those in Table 6 are merely exemplary, and the embodiments according to the present disclosure are not limited to any specific case in Table 6. Each of the drug ingredients and drug recommendation information provided by the system (100) according to one embodiment may be determined based on user input. Additionally, the system (100) may provide each of the drug ingredients and drug recommendation information according to priority regarding the number of times users have prescribed and reviewed. The system (100) may provide each of the drug ingredients and drug recommendation information including evaluation score information based on user input. The electronic device (200) may determine each of the drug ingredients and drug recommendation information based on user input and calculate the user's reward score based on the evaluation score information for said information.

[0182] FIG. 15 is a flowchart illustrating the operation of a user terminal linked with a patient information management system in one embodiment.

[0183] Referring to FIG. 15, a user terminal (300) according to one embodiment may form a secure session with a patient information management system (100) that communicates with an electronic device (200) on the medical staff side through at least one authentication procedure in step S1510. Specifically, when a patient visits a medical institution, the user terminal (300) may initiate an authentication procedure by receiving an authentication request signal from the system (100) or the electronic device (200), or by responding to an input in which the user presses a connect button on the terminal. At this time, the user terminal (300) may form a secure session by utilizing a linked wearable device (310) to receive an authentication token generated when the wearable device (310) is tagged to a near-field communication (NFC) reader of the electronic device (200) and transmitting it to the system (100). The user terminal (300) can activate the camera to scan a one-time QR code displayed on the screen of the electronic device (200) and, based on the connection information obtained by interpreting it, form a secure session with the system (100). If the user is a guardian rather than the patient, the user terminal (300) (guardian terminal) can form a secure session by transmitting pre-registered family relationship verification information or an agent authentication code to the system (100) to have its validity verified.

[0184] In step S1520, the user terminal (300) can control the transceiver to transmit stored patient information to the system (100) according to the user's settings in response to the formation of a secure session. The stored patient information transmitted here may include medical and medication history data that the user terminal (300) usually scrapes from and integrates from external agency servers (e.g., National Health Insurance Service), image files of paper prescriptions or medical records uploaded by the user directly through a camera, and biosignal data (electrocardiogram, blood glucose, activity level, etc.) collected in real-time from a wearable device (310). The user terminal (300) can transmit only selected information to the system (100) by encrypting it based on the 'information provision scope' (e.g., providing only the last 3 months of history, excluding psychiatric records, etc.) or provision period (e.g., maintaining the connection only until the end of treatment) that the user has set in advance. Before transmitting patient information to the system (100), the user terminal (300) can maximize the efficiency of medical staff by performing a brief preliminary inquiry to the user regarding their current chief complaint through a built-in AI chatbot, and by including the inquiry summary data generated as a result in the patient information and transmitting it together. Even after transmission is completed, the user terminal (300) can receive updated prescription information or precautions (such as medication instructions) based on the treatment results from the system (100), store them in memory, and provide them to the user in the form of a notification to support continuous health management.

[0185] The electronic device according to the embodiments described above may include a processor, memory for storing and executing program data, permanent storage such as a disk drive, a communication port for communicating with an external device, and user interface devices such as a touch panel, a key, a button, etc. Methods implemented as software modules or algorithms may be stored on a computer-readable recording medium as computer-readable code or program instructions executable on the processor. Here, computer-readable recording media include magnetic storage media (e.g., ROM (read-only memory), RAM (random-access memory), floppy disks, hard disks, etc.) and optical reading media (e.g., CD-ROM, DVD (Digital Versatile Disc)). The computer-readable recording medium may be distributed across networked computer systems, allowing computer-readable code to be stored and executed in a distributed manner. The medium may be readable by a computer, stored in memory, and executed by a processor.

[0186] The present embodiment may be represented by functional block configurations and various processing steps. These functional blocks may be implemented by various numbers of hardware and / or software configurations that execute specific functions. For example, the embodiment may employ integrated circuit configurations such as memory, processing, logic, look-up tables, etc., which can execute various functions by the control of one or more microprocessors or other control devices. Similar to how components may be implemented as software programming or software elements, the present embodiment may be implemented in programming or scripting languages ​​such as C, C++, Java, assembler, etc., including various algorithms implemented as combinations of data structures, processes, routines, or other programming configurations. Functional aspects may be implemented as algorithms executed on one or more processors. Additionally, the present embodiment may employ prior art for electronic configuration, signal processing, and / or data processing. Terms such as "mechanism," "element," "means," and "configuration" may be used broadly and are not limited to mechanical and physical configurations. The above terms may include the meaning of a series of software processes (routines) in conjunction with processors, etc.

[0187] The aforementioned embodiments are merely examples, and other embodiments may be implemented within the scope of the claims set forth below.

Claims

1. In the patient information management system, transceiver; Memory storing one or more instructions; and It includes at least one processor, and the at least one processor executes the one or more instructions to cause the patient information management system: Receive EHR information from an existing electronic medical record (EHR) system, and Receiving patient information including at least one of a patient's prescription and a patient's medical record from a user terminal through a secure session formed through at least one authentication procedure, and Transmitting output information to an electronic device on the medical staff side to output the received patient information and EHR information received from the electronic medical record system through a user interface, Patient Information Management System.

2. In Paragraph 1, The patient information management system forms the security session based on user input received from the user terminal through the transceiver, and The above security session is maintained for a preset period, Patient Information Management System.

3. In Paragraph 1, The above user terminal includes a guardian terminal used by the patient's guardian, and The above patient information management system receives authentication information from the guardian terminal, and Receiving the patient information stored in the guardian terminal through a secure session formed with the patient information management system by determining whether the authentication is valid based on the above authentication information, Patient Information Management System.

4. In Paragraph 1, The electronic device generates at least one of a layer and a pop-up window on the user interface of the electronic device to output the patient information included in the received output information, and The above user interface includes an object that provides a function to transfer the patient information displayed on the above user interface to an input field of the above electronic medical record system. Patient Information Management System.

5. In Paragraph 1, The above user terminal is, Providing a pre-examination function for the said patient through an interactive user interface, and including the examination summary data generated through the said pre-examination function in the said patient information and transmitting it to the said patient information management system. Patient Information Management System.

6. In Paragraph 1, The above patient information management system is, After the formation of the above security session, the output information including at least one of verification information for the patient's prescription and processing information for the patient's medical record is transmitted to the electronic device. Patient Information Management System.

7. In Paragraph 1, The above patient information is, It includes the patient's medical records received through authentication from an external agency server and biosignal data collected from a wearable device linked to the user terminal, The above biosignal data includes at least one of the patient's electrocardiogram (ECG), heart rate, oxygen saturation, blood pressure, blood glucose, body temperature, sleep pattern, and activity level data. Patient Information Management System.

8. In Paragraph 7, The above-mentioned at least one processor is, Based on sensing information obtained through a sensor provided in the electronic device, determining whether the wearable device is located within a preset distance from the electronic device, and When it is determined that the wearable device is located within a preset distance of the electronic device, the security session is formed. Patient Information Management System.

9. In Paragraph 1, The above-mentioned at least one processor is, Recognizing a first string for at least one area of ​​the above patient's prescription, and Based on the above first string, extract the first keyword of the drug prescribed to the patient, and Generating verification information for the patient's prescription based on at least one drug component corresponding to the first keyword, and Controlling the transceiver to transmit the above verification information to the electronic device, Patient Information Management System.

10. In Paragraph 9, The above patient information management system is, An image acquired through a sensor provided in the electronic device is received from the electronic device, and Recognizing a first string for at least one region of the received image, Patient Information Management System.

11. In Paragraph 9, The above first keyword is, Includes the 1-1 keyword of the first drug and the 1-2 keyword of the second drug, and The above at least one processor generates the verification information including information on the interaction between the first drug and the second drug, based on at least one drug component corresponding to the first-1 keyword and at least one drug component corresponding to the first-2 keyword. Patient Information Management System.

12. In Paragraph 11, The above-mentioned at least one processor is, Based on the above first string, the dosage information of the first drug, the dosage information of the first drug, the dosage information of the second drug, and the dosage information of the second drug are recognized, and Generating the verification information including recommended drug dosage information based on the dosage information of the first drug, the dosage frequency information of the first drug, the dosage information of the second drug, and the dosage frequency information of the second drug. Patient Information Management System.

13. In Paragraph 9, The above-mentioned at least one processor is, Determine the 1-1 string by removing special characters, strings contained within the special characters, numbers, and units from the above 1 string, and Extracting words with a predefined number of characters or more included in the above 1-1 string as the above 1 keyword, Patient Information Management System.

14. In Paragraph 9, The above-mentioned at least one processor is, Determining whether there is an abbreviation of a drug previously set in the first string above, and If the abbreviation of the previously set drug exists in the first string above, the abbreviation is changed to the full name and the changed first string is recognized. Patient Information Management System.

15. In Paragraph 9, The above-mentioned at least one processor is, Compare the above first keyword with the previously defined keyword, and If there is a keyword identical to the first keyword among the previously defined keywords, verification information for the patient's prescription is generated based on at least one drug component corresponding to the first keyword. Patient Information Management System.

16. In Paragraph 15, The above-mentioned at least one processor is, If there is no keyword among the previously defined keywords that is identical to the first keyword of the above drug, a first-1 keyword is extracted by changing some of the characters included in the first string according to a predefined rule, and Comparing the above-mentioned 1-1 keyword with a previously defined keyword, and if there is a keyword among the previously defined keywords that is identical to the above-mentioned 1-1 keyword, generating verification information for the patient's prescription based on at least one drug component corresponding to the above-mentioned 1-1 keyword. Patient Information Management System.

17. In Paragraph 15, The above-mentioned at least one processor is, If, among the keywords previously defined above, there is no keyword identical to the first keyword of the above drug, Recognizing a second string for at least one area of ​​the above patient's prescription, and Based on the above second string, a second keyword related to patient condition information is extracted, and Based on the second keyword above, a third keyword of the expected prescription drug according to the patient condition information is extracted, and Extract the 1st-3rd keyword with the highest similarity to the 1st keyword among the 3rd keywords above, and Compare the 1st-3rd keywords of the above drug with the previously defined keywords, and If the first to third keywords of the above-defined drug exist among the above-defined keywords, generating verification information for the patient's prescription based on drug information corresponding to the above-defined keywords, Patient Information Management System.

18. In Paragraph 9, The above-mentioned at least one processor is, Recognizing a second string for at least one area of ​​the above patient's prescription, and Based on the above second string, a second keyword related to patient condition information is extracted, and Based on at least one drug component corresponding to the first keyword and the second keyword, the verification information including effect information of the at least one drug component considering the patient's condition information is generated, and The above patient status information is, including at least one of the patient's pregnancy information, the patient's breastfeeding information, the patient's kidney function information, the patient's liver function information, and the patient's age information, Patient Information Management System.

19. In Paragraph 1, The above-mentioned at least one processor is, Encrypting EHR information including the patient's treatment results and prescription history obtained from the electronic medical record system, and transmitting the encrypted EHR information to the user terminal through the formed security session. Patient Information Management System.

20. Regarding patient information management methods, A step of receiving EHR information from an existing electronic medical record system; A step of receiving patient information including at least one of a patient's prescription and a patient's medical record from a user terminal through a secure session formed through at least one authentication procedure; and A step comprising transmitting output information to an electronic device on the medical staff side to output the received patient information and the EHR information received from the electronic medical record system through a user interface. Patient Information Management Methods 21. A user terminal that forms a secure session with a patient information management system, Transceiver; Memory storing one or more instructions; and It includes at least one processor that executes one or more of the above instructions, and The above-mentioned at least one processor forms a secure session with a patient information management system that communicates with an electronic device on the medical staff side through at least one authentication procedure, and Controlling the transceiver to transmit the stored patient information to the patient information management system according to the user's settings in response to the formation of the above security session, User terminal.

Images