Method and apparatus for eletronic recommendation and sales management of health functional foods
An electronic platform for managing and selling health functional foods addresses inefficiencies in doctor recommendations by providing standardized information and a one-click payment system, improving patient compliance and enabling data-driven product development and distribution.
Patent Information
- Application Number
- KR1020250124741
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2025-09-03
- Publication Date
- 2026-11-06
- Estimated Expiration
- 2045-09-03
AI Technical Summary
The inefficiency and inaccuracy of verbally recommending health functional foods by doctors, the inconvenience in purchasing these foods for patients, the difficulty in tracking consumption, and limitations in distribution channels for manufacturers and distributors are significant challenges in the current system.
A platform that electronically manages and sells health functional foods, using a server to generate and transmit standardized recommendation information to patients' terminals, integrating a one-click payment system, and providing a reliable distribution channel for manufacturers and distributors.
Patients receive accurate product information and dosage instructions electronically, doctors can track and manage consumption, and manufacturers benefit from data for new product development and marketing strategies, enhancing patient compliance and operational efficiency.
Smart Images

Figure 112025101214864-PAT00007_ABST
Abstract
Description
Technology Field
[0001] The present disclosure relates to a platform linked with a system that recommends, manages, and sells electronic health functional foods. Background Technology
[0002] With the recent increase in interest in health and the growing emphasis on the importance of preventive medicine, the consumption of health functional foods—not only for treating diseases but also for promoting and maintaining health—is surging. In particular, doctors (or medical staff) in hospitals and clinics frequently recommend the intake of health functional foods containing specific nutrients or functional ingredients based on a patient's health condition or test results. This is part of a functional medicine approach and is widely utilized as an adjunctive therapy to address patients' fundamental health issues.
[0003] However, the conventional method in which medical staff verbally recommend health functional foods to patients and the patients purchase the recommended foods directly can lead to various problems.
[0004] First, the inefficiency and inaccuracy of information delivery can be problematic. For instance, even if a doctor verbally recommends a specific product or ingredient, patients may find it difficult to accurately remember that information the moment they leave the consultation room. In other words, there is a high likelihood that patients will forget the complex product name recommended by the doctor or confuse it with similar products, leading to an incorrect purchase; furthermore, important information such as consumption methods or precautions may be omitted or conveyed in a distorted manner.
[0005] Secondly, patients may experience inconvenience during the purchasing process and abandon the purchase of health functional foods recommended by their doctors. For example, patients may face the hassle of having to visit a pharmacy or drugstore separately to purchase a product recommended by a doctor, or having to search for and buy the specific recommended product themselves from among numerous options on online shopping malls. This inconvenience in the product search and purchasing process can ultimately lead to patients abandoning their purchase, and consequently, the doctor's recommendation for health functional foods may not lead to actual consumption and health improvement.
[0006] Thirdly, there may be limitations to doctors' recommendations of health functional foods. From a doctor's perspective, even if a specific health functional food is recommended, it may be difficult to track or manage whether the patient actually purchases and consumes it. Additionally, there may be a psychological burden associated with directly recommending products from a specific company. Consequently, doctors may find it difficult to actively recommend health functional foods from the perspective of functional medicine nutrition recommendations.
[0007] Fourth, there may be limitations to the distribution channels of health functional food manufacturers and distributors. Although manufacturers or distributors have secured highly credible expert channels such as hospitals and clinics, they may face difficulties in establishing an active distribution system because they rely on health functional foods recommended verbally by doctors.
[0008] Recently, in order to overcome these problems, there is a growing need for a new system to link doctors' recommendations for health functional foods with patients' actual purchase and consumption. The problem to be solved
[0009] The various embodiments disclosed in this document aim to generate information on health functional foods recommended by a doctor in a hospital or clinic to a patient in the form of standardized electronic information and transmit it to the patient's communication terminal.
[0010] In addition, the various embodiments disclosed in this document aim to integrate a one-click payment system that allows a patient to purchase the relevant health functional food (or product) without a separate search process through received electronic recommendation information.
[0011] Furthermore, the various embodiments disclosed in this document aim to establish a platform that systematically supports physicians' recommendation activities for health functional foods, provides a foundation for intake management and effect analysis through patient purchase data, and offers a highly reliable distribution channel to manufacturers or distributors of health functional foods. means of solving the problem
[0012] Various embodiments disclosed in this document may include a method performed by a server that manages electronic recommendation information and provides sales linkage information, comprising the steps of: receiving recommendation information including recommended product information from a hospital terminal; generating electronic recommendation data including a user identifier based on the recommendation information; generating payment gateway information used for payment of recommended products based on the electronic recommendation data; generating an electronic recommendation message including electronic recommendation data and payment gateway information; and transmitting the electronic recommendation message to a patient terminal.
[0013] Various embodiments disclosed in this document include a management server that manages electronic recommendation information and provides sales linkage information, comprising at least one transceiver, at least one processor communicatively coupled to at least one transceiver, and at least one memory communicatively coupled to at least one processor to store instructions, wherein the instructions are executed individually or in any combination by at least one processor, so that the management server: receives recommendation information including recommended product information from a hospital terminal, generates electronic recommendation data including a user identifier based on the recommendation information, generates payment gateway information used for payment of recommended products based on the electronic recommendation data, generates an electronic recommendation message including the electronic recommendation data and the payment gateway information, and transmits the electronic recommendation message to a patient terminal.
[0014] Various embodiments disclosed in this document may include, in a method performed by a hospital terminal, the steps of inputting recommendation information including recommended product information and transmitting said recommendation information to a management server, wherein the recommendation information is associated with electronic recommendation data including a user identifier, and the recommendation information includes medication guidance information corresponding to patient information and recommended product information, and may receive recommended product information for each patient predicted using a deep neural network from the management server, receive intake compliance information for each product predicted using a deep neural network from the management server, and receive information regarding similar products predicted using a deep neural network from the management server.
[0015] Various embodiments disclosed in this document include a method performed by a patient terminal, comprising the steps of receiving from a management server electronic recommendation data including a user identifier and an electronic recommendation message including payment gateway information, and transmitting to the management server product purchase information corresponding to the electronic recommendation message, wherein the electronic recommendation data is based on recommendation information including recommended product information entered by a hospital terminal, and the payment gateway information is used for payment of the recommended product, and the electronic recommendation message includes URL information of a landing page accessible to the patient terminal, wherein the URL information is dynamically generated based on identification information and electronic recommendation data corresponding to the patient terminal, and the electronic recommendation message may be received through a messaging gateway. Effects of the invention
[0016] According to various embodiments of the present disclosure, a patient can receive recommendations via an electronic recommendation message from a doctor without having to remember the doctor's recommendations, and can check accurate product information and dosage instructions at any time.
[0017] According to various embodiments of the present disclosure, a physician can provide recommendations in a standardized and professional form, going beyond the limitations of verbal explanations. Additionally, the physician can use purchase and consumption data of products purchased by the patient through electronic recommendations (e.g., health functional foods) to predict the patient's compliance with intake and as a basis for tracking and managing health improvement effects.
[0018] According to various embodiments of the present disclosure, a platform linked with a system that electronically manages recommendations for health functional foods proposed in the present disclosure and sells them can provide a distribution channel, such as hospitals and clinics, to manufacturers or distributors of health functional foods.
[0019] According to various embodiments of the present disclosure, data accumulated on a platform linked to a system that electronically manages recommendations for health functional foods and sells them can be used by manufacturers or distributors of health functional products for new product development, inventory management, and establishing marketing strategies. Additionally, the accumulated data can be used in the future for artificial intelligence (AI)-based personalized product recommendation services for patients.
[0020] The effects according to the technical concept of the present disclosure are not limited to those mentioned above, and other unmentioned effects will be clearly understood by a person skilled in the art from the description below. Brief explanation of the drawing
[0021] FIG. 1 illustrates a system for recommending and selling health functional foods according to one embodiment of the present disclosure. FIG. 2 illustrates a system for linking the recommendation and sale of health functional foods according to one embodiment of the present disclosure. FIG. 3 illustrates an example of a user interface provided by a hospital terminal according to one embodiment of the present disclosure. FIG. 4 illustrates an example of a user interface provided by a patient terminal according to one embodiment of the present disclosure. FIG. 5 illustrates an example of a user interface provided by a patient terminal according to one embodiment of the present disclosure. FIG. 6 is a flowchart of a system linking the recommendation and sale of health functional foods according to one embodiment of the present disclosure. FIG. 7 is a flowchart of a system linking the recommendation and sale of health functional foods according to one embodiment of the present disclosure. FIG. 8 is a flowchart illustrating the operation of a management server according to one embodiment of the present disclosure. FIG. 9 is a flowchart illustrating the operation of a hospital terminal according to one embodiment of the present disclosure. FIG. 10 is a flowchart illustrating the operation of a patient terminal according to one embodiment of the present disclosure. FIG. 11 illustrates the structure of a server according to one embodiment of the present disclosure. FIG. 12 illustrates the structure of a terminal according to one embodiment of the present disclosure. In relation to the description of the drawings, the same or similar reference numerals may be used for identical or similar components. Specific details for implementing the invention
[0022] Various aspects of the claimed subject matter are described with reference to the drawings, in which similar reference numerals are used to denote similar elements. In the following description, for the purpose of explanation, a number of specific details are described to provide a sufficient understanding of one or more embodiments. However, it may be apparent that the embodiments can be practiced without these specific details.
[0023] The terms used in this disclosure are used merely to describe specific embodiments and are not intended to limit the scope of other embodiments. A singular expression may include a plural expression unless the context clearly indicates otherwise. Terms used herein, including technical or scientific terms, may have the same meaning as generally understood by those skilled in the art described in this disclosure. Terms used in this disclosure that are defined in a general dictionary may be interpreted as having the same or similar meaning as they have in the context of the relevant technology, and are not to be interpreted in an ideal or overly formal sense unless explicitly defined in this disclosure. In some cases, even terms defined in this disclosure are not to be interpreted to exclude the embodiments of this disclosure.
[0024] In addition, when describing with reference to the attached drawings, identical components are assigned the same reference numeral regardless of drawing symbols, and redundant descriptions thereof are omitted. When describing the embodiments, if it is determined that a detailed description of related prior art could unnecessarily obscure the essence of the embodiments, such detailed description is omitted.
[0025] Various embodiments of the present disclosure are described herein in relation to wireless terminals. A wireless terminal may refer to a device that provides voice and / or data access to a user. A wireless terminal may be connected to a computing device, such as a laptop computer or a desktop computer, or may be a self-contained device, such as a personal digital assistant (PDA). A wireless terminal may also be referred to as a system, subscriber unit, subscriber station, mobile station, mobile, mobile device, remote station, remote terminal, access terminal, user terminal, terminal, wireless communication device, user agent, user device, or user equipment. A wireless terminal may be a subscriber station, wireless device, cellular phone, PCS phone, wireless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), a portable device with wireless access capability, or other processing device connected to a wireless modem.
[0026] Hereinafter, the hospital terminal described in this disclosure may also be referred to as a doctor's terminal that can be used by a doctor (or medical staff) within a hospital or clinic.
[0028] FIG. 1 illustrates a system (100) for recommending and selling health functional foods according to one embodiment of the present disclosure.
[0029] Referring to FIG. 1, the system may include a hospital terminal (110), a management server (120), and a patient terminal (130).
[0030] According to one embodiment of the present disclosure, a hospital terminal (110) may be configured as a PC, tablet, etc. installed within a hospital or clinic and may provide a user interface (hereinafter UI) that allows viewing or registering patient information through a secure login. Additionally, the hospital terminal (110) may search for and select health functional foods by ingredients, functionality, and category through a product selection UI, input dosage instructions and delivery memos (e.g., precautions) through an electronic recommendation creation UI, and transmit electronic recommendation information to a management server (120) through a recommendation transmission button.
[0031] According to one embodiment of the present disclosure, a hospital terminal (110) may be a terminal of a hospital or clinic matched according to the results of the AI-based medical questionnaire performed by a user of a patient terminal (130) through the patient terminal (130). The AI medical questionnaire may include a function that receives information such as symptoms, lifestyle habits, and health concerns from a user of the patient terminal, analyzes the health status through a symptom-based algorithm, and recommends an optimal hospital or clinic by considering the user's region and necessary medical specialties based on the analyzed results. Through this, hospitals and clinics can attract a large number of potential customers who previously lacked access to medical information or had difficulty choosing a hospital or clinic as new patients, and consequently, hospitals and clinics can expand their market size by connecting with verified new patients. Therefore, the AI medical questionnaire can perform the core function of providing customized medical information to patients and efficiently matching new patients suitable for the hospital or clinic.
[0032] Furthermore, when a user of a patient terminal receives a recommendation for a hospital or clinic through an AI medical questionnaire and a match is made, the patient terminal and the hospital terminal can interact to perform the payment procedure for confirming the user's reservation. Specifically, the patient terminal provides a user interface (UI) for paying a predetermined amount as a reservation deposit to confirm a visit to the matched hospital or clinic, and this deposit payment can function as a condition for the hospital or clinic to confirm the reservation. The reservation deposit is processed by being deducted from the medical fee or fully refunded upon the actual visit, thereby ensuring that no actual financial burden is placed on the patient. This structure effectively prevents the risk of so-called "no-shows," which is one of the major operational problems faced by hospitals and clinics. By securing patients with a reliable intention to visit in advance, hospitals and clinics can significantly improve the reliability of the reservation system and operational efficiency.
[0033] The management server (120) is a core component of the system and may include a communication unit, a control unit, and a storage unit. Additionally, the control unit may include an electronic recommendation management module, a user management module, a data analysis module, a payment management module, and a deep neural network, and the storage unit may include a user database and a product database. The management server (120) may generate a sales page exclusively for patients based on electronic recommendation information received from a hospital terminal (110) and send a link (uniform resource locator, URL) containing a unique identifier in the form of a message to the patient terminal (130).
[0034] The patient terminal (130) may be composed of a smartphone or the like owned by the patient, and can access a sales page containing product details and payment functions through a link included in the received message. Through this, the patient can check the electronic recommendation sent by the doctor and conveniently order and pay for the health functional food.
[0035] In this way, the present system can automate and streamline the recommendation and sales process of health functional foods by linking the hospital terminal (110), the management server (120), and the patient terminal (130) through a network.
[0037] FIG. 2 illustrates a system for linking the recommendation and sale of health functional foods according to one embodiment of the present disclosure.
[0038] Referring to FIG. 2, the system (200) may include a hospital terminal (110), a management server (120), a patient terminal (130), and a pharmacy terminal (140).
[0039] The hospital terminal (110) is a computer device used by a doctor in a hospital or clinic, capable of selecting a health functional food suitable for the patient's condition and generating electronic recommendation information. The generated electronic recommendation information can be transmitted to a management server (120) via a network.
[0040] The management server (120) receives and stores electronic recommendation data and can perform functions such as sending guidance messages to patients or creating sales pages based on the electronic recommendation information. In addition, the management server (120) can also transmit the electronic recommendation information to a pharmacy terminal (140).
[0041] A pharmacy terminal (140) is installed in an offline pharmacy and can be used to check electronic recommendation information received from a management server and to sell the corresponding health functional food directly to patients. Through this, patients can have the option to purchase health functional food by visiting the pharmacy in person, in addition to making message-based online orders.
[0042] The patient terminal (130) is a personal device such as a smartphone or tablet, which can check product information through messages received from the management server and access an online sales page through a web browser.
[0043] Therefore, the present system (200) can provide a more flexible and convenient distribution channel for health functional foods by linking the information transmission and product purchasing processes between hospitals, clinics, patients, and pharmacies into a single integrated flow.
[0045] FIG. 3 illustrates an example of a user interface provided by a hospital terminal (or doctor terminal) according to one embodiment of the present disclosure.
[0046] Referring to FIG. 3, a hospital terminal can provide a user interface (UI) that checks patient information, selects a health functional food to recommend to the patient, and generates and transmits electronic recommendation information.
[0047] In (A) of FIG. 3, the hospital terminal may be provided with an input window for entering and modifying the patient's basic information, such as the patient's name, gender, date of birth, and contact information. At this time, the patient's basic information entered and modified can be used as data to generate patient-customized electronic recommendation information.
[0048] In addition, the hospital terminal may display a UI with a filtering tab and a product list that allows searching and selecting health functional foods classified by function or ingredient. In one example, a doctor can select a health functional food suitable for a patient's health condition while checking information such as the image, product name, and price of each product through the UI. For example, products such as 'ABCD Folic Acid', 'EFGH Vitamin', 'IGKL Vitamin Complex', and 'MNOP Active' may be displayed on the hospital terminal's display in the 'Multivitamin' category. In this case, when a medical professional clicks to select 'ABCD Folic Acid' and 'EFGH Vitamin', the corresponding product information may be automatically reflected in the electronic recommendation creation area shown in (B) of Fig. 3.
[0049] According to one embodiment of the present disclosure, a hospital terminal may receive patient-customized health functional food recommendation information predicted based on a deep neural network (DNN) from a management server. The management server may recommend a product deemed suitable for the current patient by comprehensively analyzing various factors such as the patient's past consumption history, preferred ingredients, disease information, age group, and gender.
[0050] The product information recommended in this manner can be displayed on the UI of hospital terminals as a separate area or visual emphasis element. For example, recommended products can be visualized using 'Recommended Product' tags, accent borders, or separate colors to distinguish them from the general product list, and medical staff can prioritize reviewing the recommended products or select them as is to reflect them in the electronic recommendation information.
[0051] In addition, supporting information for the recommended products (e.g., similarity to existing patients, past medication adherence rates, satisfaction, etc.) is displayed alongside the product, serving as supplementary material to aid medical professionals in their decision-making. This enables medical staff to generate more scientific and personalized recommendations that reflect AI-based data analysis, rather than relying on simple manual selection.
[0052] Such recommendation features can contribute to simultaneously enhancing the convenience of medical staff and patient satisfaction with medication, and the UI of hospital terminals can be configured in various ways to intuitively convey this predictive information and recommendation data.
[0053] In Fig. 3 (B), a confirmation window may be displayed as a UI on the hospital terminal, which allows the patient to check the product list and medication instructions selected from the user interface of Fig. 3 (A) before transmitting them to the patient. In one example, the product name and ingredient name are organized in a list format, and medication instructions including dosage instructions for each product (e.g., taking one tablet once a day) may be automatically generated and displayed.
[0054] By pressing the 'Send' button at the bottom of (B) of Fig. 3, the electronic recommendation content can be sent in the form of a message to a terminal (e.g., a smartphone) connected to the patient's contact. This allows the patient to conveniently receive and purchase information on health functional foods recommended by the doctor, even without remembering the doctor's recommendation content themselves.
[0055] In one example, when a doctor selects multiple products, a medication instruction area can be activated to enter the names of the selected products and the method of administration, as shown in (B) of FIG. 3. In the medication instruction, information regarding the frequency, amount, and timing of intake can be automatically entered or manually entered, and the corresponding electronic recommendation information can then be transmitted to a management server via a 'transmit' button.
[0056] As described above, the UI illustrated in FIG. 3 is merely an example, and in actual implementation, various forms of user interfaces may be provided depending on the hospital's treatment methods, product categories, patient types, etc. For instance, the product search method, medication instruction input method, etc., can be freely changed according to the treatment environment within the hospital.
[0057] Consequently, this system can enable the generation and transmission of patient-customized electronic recommendation information by providing various functions in an integrated manner through a hospital terminal.
[0059] FIG. 4 illustrates an example of a user interface provided by a patient terminal according to one embodiment of the present disclosure.
[0060] Referring to FIG. 4, the patient terminal receives an electronic recommendation message regarding electronic recommendation information generated from the hospital terminal through a management server, and a user interface including a URL that allows access to a product information verification and purchase page (or landing page) through the electronic recommendation message may be provided.
[0061] Figure 4 (A) illustrates an example of an electronic recommendation message received by a patient terminal. The electronic recommendation message is generated based on the results of health functional food consultation and recommendation conducted on a patient, transmitted from a hospital or clinic via a hospital terminal, and may include a link (e.g., URL) that allows access to a landing page based on electronic recommendation data and payment gateway information.
[0062] In one example, a user of a patient terminal can access a customized landing page illustrated in (B) of FIG. 4 by clicking a link (URL) included in an electronic recommendation message. The landing page may be dynamically generated based on user identifiers and product information included in the electronic recommendation data and may include identification information corresponding to a specific patient terminal.
[0063] Figure 4 (B) illustrates an example of a user interface displayed after a user of a patient terminal clicks a link to a landing page included in the electronic recommendation message of Figure 4 (A). In one example, the user of the patient terminal may perform an identity verification procedure by entering their name and the last four digits of their phone number. At this time, identity verification is a step to ensure security for personalized product recommendation information, and once verification is complete, a user interface containing subsequent information such as a recommended product list, medication instructions, and a payment screen may be provided to the patient terminal in stages.
[0064] As described above, the patient terminal receives an electronic recommendation message from the management server and can check personalized health functional food information and select or pay for a product by accessing the URL provided through the received recommendation message. Through this, users of the patient terminal can conveniently access product information and purchasing procedures in a web-based environment without the need to install a separate application or go through a registration process for a specific site.
[0065] However, the user interface displayed on the patient terminal is not limited to FIG. 4 and can be implemented in various forms depending on the patient's age, digital literacy, type of recommended product, payment method, etc. For example, a voice guidance UI for the elderly, a medication schedule calendar-linked UI, and a purchase history-based reminder notification UI may be optionally provided, and can be modified and expanded in a customized form according to the policies of each hospital or platform operator.
[0067] FIG. 5 illustrates an example of a user interface provided by a patient terminal according to an embodiment of the present disclosure. Specifically, FIG. 5 may be a user interface displayed after the user of the patient terminal has entered their name and phone number on the landing page of FIG. 4 (B) and identity verification is completed.
[0068] Referring to FIG. 5, the user interface displayed on the patient terminal can be configured based on a list of health functional foods selected by medical staff on the hospital terminal (e.g., the hospital terminal of FIG. 3). For example, the products selected in FIG. 3 are linked with patient identifiers and recommendation information and included in electronic recommendation messages, and can be automatically displayed on a customized sales page such as FIG. 5.
[0069] Each product may be provided as a user interface arranged with a product image, product name, price, and medication instructions (e.g., take 1 tablet once a day or take 2 capsules once a day), and individual purchase buttons for each product may be placed at the bottom so that the patient can select the desired product and make a payment.
[0070] Clicking the purchase button allows for a secure connection to the payment page via payment gateway information generated by the management server. This enables patients to conveniently purchase health supplements tailored to their needs remotely, along with the medication regimen recommended by medical professionals.
[0071] In this way, the user interface of Fig. 5 can provide patients with an intuitive and reliable purchasing environment based on electronic recommendation information established by the hospital.
[0072] Furthermore, the following effects can be expected through this user interface.
[0073] First, patients can improve compliance by conveniently checking and purchasing customized health functional foods based on medical staff recommendations without the need to revisit the hospital or search for product information separately.
[0074] Second, since electronic recommendation data based on user identifiers is linked with the payment gateway, the possibility of incorrect orders or misuse by others can be minimized.
[0075] Third, by utilizing purchase history and intake data received through patient terminals, it can contribute to the advancement of deep neural network-based personalized recommendation algorithms in the future, thereby enabling expansion into a continuous and systematic health management platform.
[0077] FIG. 6 is a flowchart of a system for linking the recommendation and sale of health functional foods according to one embodiment of the present disclosure. Specifically, FIG. 6 shows a system for linking the recommendation and sale of health functional foods in which electronic recommendations are generated and transmitted through interaction between a hospital terminal, a management server, a patient terminal, and a pharmacy terminal, and a process linked to product purchase can be performed step by step.
[0078] According to one embodiment of the present disclosure, prior to step 610, a user of a patient terminal performs an AI medical questionnaire through the patient terminal, and the hospital terminal of FIG. 6 may be used as a terminal of a hospital or clinic matched according to the results of the AI medical questionnaire. The AI medical questionnaire may include a function that receives information such as symptoms, lifestyle habits, and health concerns from the user of the patient terminal, analyzes the health status through a symptom-based algorithm, and recommends an optimal hospital or clinic by considering the user's region and necessary medical specialties based on the analyzed results. Through this, a large number of potential customers who previously lacked access to medical information or had difficulty selecting a hospital or clinic can be attracted as new patients, and consequently, hospitals and clinics can expand their market size by connecting with verified new patients. Therefore, the AI medical questionnaire can perform the core function of providing customized medical information to patients and efficiently matching new patients suitable for the hospital or clinic.
[0079] Furthermore, when a user of a patient terminal receives a recommendation for a hospital or clinic through an AI medical questionnaire and a match is made, the patient terminal and the hospital terminal can interact to perform the payment procedure for confirming the user's reservation. Specifically, the patient terminal provides a user interface (UI) for paying a predetermined amount as a reservation deposit to confirm a visit to the matched hospital or clinic, and this deposit payment can function as a condition for the hospital or clinic to confirm the reservation. The reservation deposit is processed by being deducted from the medical fee or fully refunded upon the actual visit, thereby ensuring that no actual financial burden is placed on the patient. This structure effectively prevents the risk of so-called "no-shows," which is one of the major operational problems faced by hospitals and clinics. By securing patients with a reliable intention to visit in advance, hospitals and clinics can significantly improve the reliability of the reservation system and operational efficiency.
[0080] Referring to FIG. 6, in step 610, medical staff can select a health functional food suitable for the patient's condition from a hospital terminal (e.g., 110 in FIG. 1, 110 in FIG. 2) and create electronic recommendation information including instructions on how to take the medicine and precautions. The electronic recommendation information may include data such as a patient identifier, product name, intake amount, and time of intake. In step 620, the hospital terminal (e.g., 110 in FIG. 1, 110 in FIG. 2) can transmit the electronic recommendation information created in step 610 to a management server (e.g., 120 in FIG. 1, 120 in FIG. 2).
[0081] In step 630, the management server may generate electronic recommendation data including a user identifier and payment gateway information based on electronic recommendation information received from a hospital terminal, and generate an electronic recommendation message including the generated electronic recommendation data. In one example, the electronic recommendation message may include the following information.
[0082] - Electronic Recommendation Data: Electronic recommendation data may include recommended product information, medication guidance information, patient identifiers, etc., entered by a doctor. For example, electronic recommendation data may include the product name, dosage, frequency of intake, time of intake (before / after meals), duration of use, precautions, etc., for multiple health functional foods.
[0083] - Payment gateway information: To enable patients to directly purchase recommended products, payment gateway information linked with a payment module may be included. This information may consist of product price, product ID, PG company integration information, payment token, validity period, etc.
[0084] - URL of the landing page: To allow the patient to easily access it from a patient terminal such as a smartphone (e.g., 130 in FIG. 1, 130 in FIG. 2), the electronic recommendation message may include a unique URL that leads to a landing page. This URL is dynamically generated based on the patient's identification information and recommended product information, and may include a security token (e.g., an encrypted unique key) accessible to only one patient.
[0085] - Hospital / Doctor Information: The message may also include basic information such as the name of the hospital or doctor who performed the product recommendation, which can contribute to instilling trust in the patient and clarifying that the recommendation is based on medical authority.
[0086] - Message Template Elements: The message format can be configured to match the messaging gateway format, such as MMS or KakaoTalk, and may be in the form of a template consisting of greetings, announcements, important notes, product lists, etc.
[0087] In step 640, the management server can transmit the electronic recommendation information received from the hospital terminal in step 620 to the pharmacy terminal. Specifically, in step 640, the electronic recommendation information can be transmitted to the pharmacy terminal to support an offline purchase route in preparation for cases where a patient wishes to visit an actual pharmacy to purchase health functional foods directly rather than purchasing them online.
[0088] In one example, a management server may receive inventory information regarding recommended products included in electronic recommendation information from a pharmacy terminal. Accordingly, based on the received inventory information, the management server may transmit the inventory status of the recommended products or information on alternative products to a patient terminal.
[0089] In step 650, the management server can send the generated electronic recommendation message to the patient terminal through the messaging gateway.
[0090] In step 655, the patient terminal can view the electronic recommendation message received from the management server and access the product information and purchase page through the URL of the landing page included in the electronic recommendation message.
[0091] In step 660, the user of the patient terminal can perform identity authentication by entering information such as name and phone number. Through this authentication, the identity of the recipient of the electronic recommendation can be verified.
[0092] In step 665, after the authentication performed in the aforementioned step 660 is completed, the user of the patient terminal can check product information, medication instructions, prices, etc. on the landing page and complete the purchase of the product through the payment gateway.
[0093] In step 670, the patient terminal may transmit product purchase information to the management server. This information may include the patient, product, payment status, etc. In one example, the product purchase information transmitted from the patient terminal to the management server may include the following information.
[0094] - Patient identification information: Information used to identify who led to the purchase via the electronic recommendation message, which may include a unique user ID, phone number (which can be masked), and authentication tokens included in the recommendation message.
[0095] - Recommendation Unique ID: May include a unique recommendation number or hash value to link the purchase to the recommendation information of which hospital / clinic terminal.
[0096] - Product Information: Product name, product ID or SKU (stock keeping unit), quantity purchased, unit price, total payment amount; if there are multiple products, items for each product may be included in an array format.
[0097] - Medication guidance information: Optionally, the product purchase information may include medication guidance information at the time of purchase (e.g., taking 2 capsules once a day). The stored medication guidance information is stored on a management server and can be used to analyze the patient's product purchase data.
[0098] - Payment information: May include payment method (credit card, simple payment, etc.), payment approval number, PG company code, payment date and time and status (successful / failed / canceled, etc.).
[0099] - Delivery information: May include recipient name, delivery address, contact information, desired delivery date, etc.
[0100] - Purchased Device and Connection Information: Optionally, the type of device used for the purchase (e.g., iPhone, Android), browser type, IP address, etc., may be included. This information may be used for security verification.
[0101] In step 680, the management server can store product purchase information received from the patient terminal in step 670 in conjunction with electronic recommendation data.
[0102] In step 685, the management server can process product purchase data.
[0103] In one example, the management server can internally process product purchase data based on product purchase information received from a patient terminal and simultaneously transmit the purchase and delivery information to a logistics server (or delivery management system) to perform the delivery procedure. For instance, the management server can automatically initiate the dispatch process by transmitting product purchase information to the logistics server via a delivery request API or a message queue (MQ). Subsequently, once a delivery tracking number is generated, it can be sent to the patient as a notification message or added to the history stored in the system.
[0104] In one example, the stored purchase information can be further processed by an analysis module or recommendation algorithm, and utilized for patient-customized product recommendations, prediction of intake compliance, suggestion of similar products, etc. For instance, the management server can further process the purchase information stored in step 680 through various analysis and recommendation algorithms. Step 685 may be a data processing step that goes beyond simple purchase history recording to provide AI-based intelligent services, such as patient-customized health functional food recommendations, prediction of individual medication tendencies, and analysis of similar products.
[0105] The operation of processing specific product purchase data of the management server will be described below in FIG. 7.
[0106] As described above, the series of steps illustrated in FIG. 6 demonstrates that electronic recommendation information input into a hospital terminal is transmitted to patient terminals and pharmacy terminals via a management server, and that the entire process, from the patient's product purchase and payment to delivery and data analysis, can be organically linked. Through this, patients can easily verify and purchase more reliable information on health functional foods, and doctors can track actual purchase and medication history following the recommendation. Furthermore, purchase data is processed by a deep neural network-based analysis algorithm, which can be expanded into intelligent services such as personalized product recommendations, medication compliance prediction, and suggestions for similar products. This system structure for linking the recommendation and sale of health functional foods illustrated in FIG. 6 goes beyond simple information provision and realizes technical effects as a personalized health management platform combining medical care and commerce.
[0108] FIG. 7 is a flowchart of a system for linking the recommendation and sale of health functional foods according to one embodiment of the present disclosure. Specifically, FIG. 7 shows a system for linking the recommendation and sale of health functional foods in which electronic recommendations are generated and transmitted through interaction between a hospital terminal, a management server, a patient terminal, and a pharmacy terminal, and a process linked to product purchase can be performed step by step.
[0109] Referring to FIG. 7, in step 705, medical staff can select a health functional food according to the patient's health condition on a hospital terminal (e.g., 110 in FIG. 1, 110 in FIG. 2) and create electronic recommendation information including a method of administration (amount, frequency, timing) and precautions. The electronic recommendation information may consist of patient information (e.g., patient identifier), recommended product information (e.g., product code (stock keeping unit, SKU), medication instructions, unique recommendation ID, etc.).
[0110] According to one embodiment of the present disclosure, prior to step 710, a user of a patient terminal performs an AI medical questionnaire through the patient terminal, and the hospital terminal of FIG. 7 may be used as a terminal of a hospital or clinic matched according to the results of the AI medical questionnaire. The AI medical questionnaire may include a function that receives information such as symptoms, lifestyle habits, and health concerns from the user of the patient terminal, analyzes the health status through a symptom-based algorithm, and recommends an optimal hospital or clinic by considering the user's region and necessary medical specialties based on the analyzed results. Through this, a large number of potential customers who previously lacked access to medical information or had difficulty selecting a hospital or clinic can be attracted as new patients, and consequently, hospitals and clinics can expand their market size by connecting with verified new patients. Therefore, the AI medical questionnaire can perform the core function of providing customized medical information to patients and efficiently matching new patients suitable for the hospital or clinic.
[0111] Furthermore, when a user of a patient terminal receives a recommendation for a hospital or clinic through an AI medical questionnaire and a match is made, the patient terminal and the hospital terminal can interact to perform the payment procedure for confirming the user's reservation. Specifically, the patient terminal provides a user interface (UI) for paying a predetermined amount as a reservation deposit to confirm a visit to the matched hospital or clinic, and this deposit payment can function as a condition for the hospital or clinic to confirm the reservation. The reservation deposit is processed by being deducted from the medical fee or fully refunded upon the actual visit, thereby ensuring that no actual financial burden is placed on the patient. This structure effectively prevents the risk of so-called "no-shows," which is one of the major operational problems faced by hospitals and clinics. By securing patients with a reliable intention to visit in advance, hospitals and clinics can significantly improve the reliability of the reservation system and operational efficiency.
[0112] In step 710, the hospital terminal (e.g., 110 in FIG. 1, 110 in FIG. 2) can transmit the electronic recommendation information created in step 610 to a management server (e.g., 120 in FIG. 1, 120 in FIG. 2).
[0113] In step 715, the management server may generate electronic recommendation data based on electronic recommendation information received from a hospital terminal and store it in a database within the management server. In one example, the electronic recommendation data may include a user identifier, a product list, medication information, an expiration date, etc.
[0114] In step 720, the management server can generate a landing page for selling customized products exclusively for patients based on the electronic recommendation data generated in step 715. In one example, the landing page can be automatically configured to include patient identification information (e.g., last four digits of phone number, internal user ID, etc.), recommended product information (SKU, product name, method of administration), medication instructions, price information, etc. For example, the management server can link with a product information database to reflect the latest price, image, and stock status of the recommended product, and medication instructions entered by a doctor can also be displayed.
[0115] The generated product sales landing page is dynamically created with a unique URL, and the URL contains an encrypted token or patient terminal identifier, providing a secure environment accessible only to the corresponding patient.
[0116] Additionally, in step 720, the management server can generate payment gateway information linked with domestic payment gateway companies (e.g., Kakao Pay, Naver Pay, credit card companies, etc.) through an internal e-commerce module to configure payment methods that can be used on the page, and map it to the landing page. In one example, the payment gateway information may include the amount per product, order number, available payment methods, payment validity period, and payment gateway request parameters. When a patient clicks to pay, this information is automatically called up, and the system can immediately switch to the payment window.
[0117] In step 725, the management server may link with an external message transmission service (MMS, AlimTalk, etc.) through an internal messaging gateway module to transmit the generated electronic recommendation message to the patient terminal. At this time, the recipient of the electronic recommendation message is the patient's registered mobile phone number linked from the hospital terminal or the user management module, and the content of the electronic recommendation message may include the patient's name, hospital name, recommendation date, product summary information, medication instructions, and a URL for accessing a landing page.
[0118] In one example, when integrating with a messaging gateway, the management server can perform the following functions:
[0119] - Message format conversion (configured to fit formats such as MMS, KakaoTalk, SMS, etc.)
[0120] URL Shortening Process
[0121] - Specify sender information and save transmission history
[0122] - Apply retry policy on transmission failure
[0123] - Save logs of transmission success and reception time
[0124] This messaging integration can maximize the user experience (UX) by delivering information accurately and quickly to patients and allowing them to access the landing page immediately without installing an app.
[0125] In step 730, the management server can transmit the electronic recommendation information received from the hospital terminal in step 710 to the pharmacy terminal. Specifically, in step 730, the electronic recommendation information can be transmitted to the pharmacy terminal to support an offline purchase route in preparation for cases where a patient wishes to visit an actual pharmacy to purchase health functional foods directly rather than purchasing them online.
[0126] In one example, a management server may receive inventory information regarding recommended products included in electronic recommendation information from a pharmacy terminal. Accordingly, based on the received inventory information, the management server may transmit the inventory status of the recommended products or information on alternative products to a patient terminal.
[0127] In step 735, the management server can send the generated electronic recommendation message to the patient terminal through the messaging gateway.
[0128] In step 740, the patient terminal can view the electronic recommendation message received from the management server and access the product information and purchase page through the URL of the landing page included in the electronic recommendation message.
[0129] In step 745, the user of the patient terminal can perform identity authentication by entering information such as name and phone number. Through this authentication, the identity of the recipient of the electronic recommendation can be verified.
[0130] In step 750, after the authentication performed in the aforementioned step 745 is completed, the user of the patient terminal can check product information, medication instructions, prices, etc. on the landing page and complete the purchase of the product through the payment gateway.
[0131] In step 755, the patient terminal may transmit product purchase information to the management server. This information may include the patient, product, payment status, etc. In one example, the product purchase information transmitted from the patient terminal to the management server may include the following information.
[0132] - Patient identification information: Information used to identify who led to the purchase via the electronic recommendation message, which may include a unique user ID, phone number (which can be masked), and authentication tokens included in the recommendation message.
[0133] - Recommendation Unique ID: May include a unique recommendation number or hash value to link the purchase to the recommendation information of which hospital / clinic terminal.
[0134] - Product Information: Product name, product ID or SKU (stock keeping unit), quantity purchased, unit price, total payment amount; if there are multiple products, items for each product may be included in an array format.
[0135] - Medication guidance information: Optionally, the product purchase information may include medication guidance information at the time of purchase (e.g., taking 2 capsules once a day). The stored medication guidance information is stored on a management server and can be used to analyze the patient's product purchase data.
[0136] - Payment information: May include payment method (credit card, simple payment, etc.), payment approval number, PG company code, payment date and time and status (successful / failed / canceled, etc.).
[0137] - Delivery information: May include recipient name, delivery address, contact information, desired delivery date, etc.
[0138] - Purchased Device and Connection Information: Optionally, the type of device used for the purchase (e.g., iPhone, Android), browser type, IP address, etc., may be included. This information may be used for security verification.
[0139] In step 760, the management server can generate order information based on the received purchase information. In one example, this order information may consist of a product name, SKU, quantity, price, payment status (approval status), recipient information, shipping address, time of order, order number, etc. Additionally, the generated order information is stored in an internal order database (DB) and can be used as reference data for subsequent delivery and analysis processes. Furthermore, the order information may include a unique recommendation ID or patient identifier to clarify the association with the corresponding recommendation.
[0140] In step 765, the management server transmits the generated product order information to the logistics server (or affiliated shipping management system) to process the actual product dispatch and delivery process. In one example, the product order information transmitted to the logistics server may include the following items:
[0141] - Recipient's name, contact information, shipping address
[0142] - Product List (SKU, Quantity), Order Number
[0143] - Desired delivery date, delivery requests (e.g., leave at the door if not home)
[0144] Subsequently, the logistics server can perform tasks such as receiving delivery requests, issuing invoice numbers, and processing shipments based on the received information.
[0145] In step 770, the management server can generate product purchase data by linking the electronic recommendation data generated in step 715 with the product order information generated in step 760. Specifically, the management server can generate product purchase data as direct linkage information between recommendation and purchase by mapping the stored order information one-to-one with the existing electronic recommendation data.
[0146] In step 775, product purchase data linked (or mapped) with electronic recommendation data and product order information can be stored in a database within the management server. For example, product purchase data may include a recommendation ID, user ID, product name, purchase quantity, payment date and time, order status, hospital ID, doctor ID, medication instruction information, etc.
[0147] In one example, the stored product purchase data can be utilized by the management server as structured data for analysis in the future, and can serve as a basis for comprehensively understanding purchase responses by patient, product, and doctor.
[0148] In step 780, the management server can perform AI-based prediction and recommendation analysis (e.g., deep neural network (DNN)) based on product purchase data linked (or mapped) with stored electronic recommendation data and product order information.
[0149] According to one embodiment of the present disclosure, a management server can analyze a specific patient's preference for health functional foods from product purchase data. For example, preference trends can be identified based on the functional categories (e.g., immunity enhancement, gut health, blood circulation improvement, etc.), ingredient groups (e.g., omega-3, probiotics, vitamin D, etc.), price range, and purchase repetition cycle of products previously purchased by the patient. These analysis results can be used to recommend appropriate products to the same patient during follow-up treatment or to increase patient satisfaction.
[0150] According to another embodiment of the present disclosure, a management server can identify a group with a purchase history similar to that of a specific patient based on a number of patient purchase data, and learn from the data of the group to predict recommended products.
[0151] The management server utilizes a deep neural network (DNN)-based AI model to use patient preferences, purchase history, and repurchase cycles as input values, and by deriving products frequently recommended and purchased within similar groups from this, it can automatically recommend similar products to the corresponding patient.
[0152] According to another embodiment of the present disclosure, a management server can predict a patient's compliance with the intake of a specific product based on stored product purchase data and satisfaction survey results. For example, if a patient has purchased multiple products but does not repeatedly purchase only a specific product, or if the patient evaluates the intake as difficult in the satisfaction response, the data can be learned to classify it as a "product with low likelihood of continued intake." In this case, the deep neural network used learns based on the time of discontinuation, intake frequency, and changes in satisfaction scores, thereby contributing to recommending products with a high likelihood of continued intake in the future.
[0153] According to another embodiment of the present disclosure, a management server may compare and analyze information on multiple product ingredients repeatedly recommended to the same patient to propose a new product with similar ingredients or functionality. In this process, a deep neural network analyzes the combination of ingredients and uses of product families with a high recommendation history and derives other products with high similarity scores, which can then be provided as alternative product information to hospital terminals or patient terminals in the future.
[0154] As described above, the management server utilizes an AI model to comprehensively analyze patients' product purchase history, recommendation information, and satisfaction responses, thereby performing various intelligent functions such as identifying individual patient product preferences, providing recommendations based on similar groups, predicting intake compliance, and suggesting similar products. These analysis results are provided in real-time to hospital or patient terminals, supporting personalized recommendations and encouraging repurchase. Furthermore, this serves as a technical foundation to expand the electronic recommendation-based health functional food distribution system into a more sophisticated and sustainable personalized healthcare platform.
[0155] In step 785, the management server transmits the AI analysis results performed in step 780 to hospital terminals, thereby enabling medical staff to establish more sophisticated product recommendations and recommendation strategies for patients.
[0156] More specifically, the management server may transmit to the hospital terminal the following information predicted by a deep neural network model:
[0157] - Patient-Tailored Recommended Product List: Product categories with high purchase rates or satisfaction among groups with similar age, gender, and health goals (e.g., boosting immunity, improving fatigue, etc.).
[0158] - Prediction results of intake compliance by product: Expected likelihood of continued use, possible discontinuation point, frequency of missed doses, etc. for a specific product
[0159] - Information on Substitute Products: Recommendations for alternative products with the same ingredients but better intake compliance or competitive pricing.
[0160] The results of these AI analyses can be displayed on the electronic recommendation creation screen within the hospital terminal or in a separate section of the patient chart, and medical staff can refer to the information to supplement or change recommended products.
[0161] As a result, the provision of information at level 785 can have a technical effect of improving the quality of medical care by enabling recommendation decisions based on quantitative and qualitative evidence derived from the patient's health status, past purchase history, and similar group analysis.
[0162] In addition, the management server may transmit product purchase data stored in step 775, prior to analysis using an AI model, to the hospital terminal. In this case, the management server can directly provide quantitative purchase information (e.g., product name, quantity, payment date and time, purchase channel, payment method, etc.) configured based on a specific patient's actual purchase history to the hospital terminal, thereby enabling medical staff to intuitively check the patient's previous recommended product purchase status and medication history. For example, history such as "Previous recommended product: EFGH Vitamin - Purchase completed on 2024.01.12" or "Unfulfilled purchase: ABCD Folic Acid - Unpaid within 5 days of receiving message" may be displayed on the hospital terminal UI, which allows medical staff to adjust recommendations or suggest new products based on actual medication adherence.
[0163] As described above, the series of steps illustrated in FIG. 7 demonstrates that electronic recommendations input into a hospital terminal are transmitted to patient and pharmacy terminals via a management server, and that the entire process, from the patient's product purchase and payment to delivery and data analysis, can be organically linked. Through this, patients can easily verify and purchase more reliable information on health functional foods, and medical staff can track actual purchase and medication history following the recommendation. Furthermore, purchase data is processed by a deep neural network-based analysis algorithm, which can be expanded into intelligent services such as personalized product recommendations, medication compliance prediction, and suggestions for similar products. This system structure linking the recommendation and sale of health functional foods illustrated in FIG. 7 goes beyond simple information provision and realizes technical effects as a personalized health management platform combining medical care and commerce.
[0165] FIG. 8 is a flowchart illustrating the operation of a management server according to one embodiment of the present disclosure.
[0166] Referring to FIG. 8, in step 810, the management server may receive recommendation information including recommended product information from a hospital terminal. At this time, the recommendation information may further include patient information and medication guidance information corresponding to the recommended product information. However, the information included in the recommendation information is not limited thereto and may also include a unique recommendation ID.
[0167] In step 820, the management server may generate electronic recommendation data including a user identifier based on the received recommendation information. In one example, the electronic recommendation data may include an identifier to indicate a unique electronic recommendation for each patient in addition to the recommendation information. The generated electronic recommendation data may be unique data that can only be used on the patient's patient terminal.
[0168] In step 830, the management server can generate payment gateway information used for payment of recommended products based on electronic recommendation data. In one example, the payment gateway information can be configured to generate a landing page URL optimized for a specific patient based on recommended product and user identifier information included in the electronic recommendation data, and to automatically link a payment module to that URL. For example, payment methods such as KakaoPay, NaverPay, credit cards, and virtual accounts may be presented. In another example, the management server can enable the patient to complete payment with a single click by configuring the payment gateway information to automatically reflect product-specific price information.
[0169] At this time, payment gateway information is automatically inserted into a landing page included in an electronic recommendation message transmitted to a patient terminal, and the patient's unique identifier or token value is included within the URL of the landing page, so that security can be set so that only the corresponding patient can access it.
[0170] In step 840, the management server can generate an electronic recommendation message containing electronic recommendation data and payment gateway information.
[0171] In one example, the electronic recommendation message may include URL information of a landing page accessible by the patient terminal. The URL information of the landing page may be dynamically generated based on identification information and electronic recommendation data corresponding to the patient terminal, and may include a unique encryption token to prevent external exposure.
[0172] In step 850, the management server may send the generated electronic recommendation message to the patient terminal. In one example, the electronic recommendation message may be sent to the patient terminal via a messaging gateway. For example, the electronic recommendation message may be sent to the patient terminal via means such as MMS (multimedia message), KakaoTalk notifications, or text messages (SMS). Accordingly, the recipient (i.e., the user of the patient terminal) can access a personalized landing page directly by clicking a link within the message without a separate login or app installation.
[0173] According to one embodiment of the present disclosure, a management server may transmit recommendation information received in step 810 to a pharmacy terminal. Through this, the management server may receive inventory information regarding recommended products included in the recommendation information from the pharmacy terminal. Based on the received inventory information regarding recommended products, the management server may additionally transmit the inventory status of the recommended products or information on alternative products to a patient terminal. Through this, the management server may enable the patient to know the pharmacy's inventory in advance before visiting the pharmacy in person to purchase the recommended products.
[0174] According to one embodiment of the present disclosure, a management server may subsequently receive product purchase information corresponding to an electronic recommendation message from a patient terminal. Based on the received product purchase information, the management server may initiate a product delivery procedure by transmitting delivery request information to a logistics server. Additionally, the management server may utilize the product purchase information for managing patient-specific purchase history and for future data analysis by mapping and storing the product purchase information with electronic recommendation data.
[0175] According to one embodiment of the present disclosure, a management server may automatically send a message for a satisfaction survey to a patient terminal after receiving delivery completion information from a logistics server, for example, after 7 or 14 days have elapsed. The message may be sent in the form of MMS or KakaoTalk notifications, and may include a survey link (URL) that allows for evaluating satisfaction with a specific product. Users of the patient terminal may evaluate the product's effectiveness, ease of consumption, packaging condition, and intention to repurchase on a web page accessed via the link, and these responses may be transmitted back to the management server and stored in a database within the management server based on individual patient response information and product-specific data. The stored satisfaction information may be reflected in future product improvements, the establishment of marketing strategies, or personalized recommendation algorithms. In one example, the management server may provide the stored product-specific satisfaction data as training data to a deep neural network (AI model). In addition to the patient's satisfaction score, the training data may also include information such as the time of consumption termination, whether regular purchases were made, and the purchase interval.
[0176] Based on this data, deep neural networks learn the consumption continuation patterns, frequency of discontinuation, and reasons for discontinuation observed in specific product groups or patient populations. Through this process, they can calculate an 'adherence rate' that predicts how consistently a patient is likely to consume recommended products in the future. This predicted adherence rate information is then transmitted to hospital terminals, enabling medical staff to consider the patient's medication adherence when making future recommendations, thereby facilitating the selection of more appropriate products or the provision of additional counseling.
[0177] According to one embodiment of the present disclosure, a management server can automatically identify cases where the same product is recommended multiple times among a plurality of recommendation information received from a hospital terminal. For example, if 'Multivitamin A' is selected by the same patient two or more times, the ingredient information (e.g., Vitamin C, D3, zinc) and functionality (e.g., immunity enhancement) of the product can be extracted as metadata and input into a deep neural network model. The deep neural network can analyze the association with other products having a structure similar to the input main ingredients and functionality (e.g., combination products with similar ingredients, alternative products from distribution brands, etc.) and derive a product group having a high degree of similarity to the duplicate recommended product. This information on similar products can be provided to the hospital terminal to enable medical staff to present more effective or price-competitive products to patients as alternatives within the same ingredient group, and can also be utilized for personalized recommendations based on patient allergies or consumption preferences.
[0179] FIG. 9 is a flowchart illustrating the operation of a hospital terminal according to one embodiment of the present disclosure.
[0180] According to one embodiment of the present disclosure, the hospital terminal described in FIG. 9 may be a terminal of a hospital or clinic matched based on the results of an AI-based medical questionnaire performed by a user of a patient terminal through the patient terminal. The AI medical questionnaire may include a function that receives information such as symptoms, lifestyle habits, and health concerns from the user of the patient terminal, analyzes the health status through a symptom-based algorithm, and recommends an optimal hospital or clinic based on the analyzed results, taking into account the user's region and required medical specialties. Through this, hospitals and clinics can attract a large number of potential customers as new patients who previously lacked access to medical information or had difficulty selecting a hospital or clinic, and consequently, hospitals and clinics can expand their market size by connecting with verified new patients. Therefore, the AI medical questionnaire can perform the core function of providing customized medical information to patients and efficiently matching new patients suitable for the hospital or clinic.
[0181] Furthermore, when a user of a patient terminal receives a recommendation for a hospital or clinic through an AI medical questionnaire and a match is made, the patient terminal and the hospital terminal can interact to perform the payment procedure for confirming the user's reservation. Specifically, the patient terminal provides a user interface (UI) for paying a predetermined amount as a reservation deposit to confirm a visit to the matched hospital or clinic, and this deposit payment can function as a condition for the hospital or clinic to confirm the reservation. The reservation deposit is processed by being deducted from the medical fee or fully refunded upon the actual visit, thereby ensuring that no actual financial burden is placed on the patient. This structure effectively prevents the risk of so-called "no-shows," which is one of the major operational problems faced by hospitals and clinics. By securing patients with a reliable intention to visit in advance, hospitals and clinics can significantly improve the reliability of the reservation system and operational efficiency.
[0182] Referring to FIG. 9, in step 910, the hospital terminal can input recommendation information including recommended product information. Specifically, the user of the hospital terminal can input recommendation information including recommended product information through the user interface (UI) of the hospital terminal.
[0183] In one example, the user interface of a hospital terminal may consist of a patient selection area where medical staff can select a patient by name or search for a patient by EMR number, and a product selection area where a list of multiple health functional foods is provided, classified by function, ingredient, or recommendation purpose. Medical staff can select one or more health functional foods on the UI of the hospital terminal and enter details such as the number of times per day to be consumed, the time of consumption (before / after meals), the period of consumption, and specific notes for each product.
[0184] In addition, according to one embodiment of the present disclosure, the user interface of a hospital terminal may display patient-specific recommended product information or alternative product information received in real time from a management server. This recommended product information may be the result of AI analysis regarding, for example, other products within the same ingredient group, products with excellent price-to-performance ratios, or products that have shown high satisfaction or compliance in patient groups similar to the patient's past history of use. Through the UI displaying this additional information, medical staff may compare and review recommended products or alternative products in addition to the recommended products intended to be entered by default, and select some of them to include in the recommended product list.
[0185] In step 920, the hospital terminal can transmit the input recommendation information to the management server. The recommendation information transmitted at this time may include the entire recommendation history, such as patient information, a list of selected health functional foods, the method of intake (use and dosage) for each product, an input memo, and whether the recommended product was selected. The recommendation information can then be converted into electronic recommendation data along with a user identifier by the management server and transmitted to the patient terminal.
[0187] FIG. 10 is a flowchart illustrating the operation of a patient terminal according to one embodiment of the present disclosure.
[0188] Referring to FIG. 10, in step 1010, the patient terminal may receive electronic recommendation data containing a user identifier and an electronic recommendation message containing payment gateway information from a management server. In one example, the electronic recommendation message may be transmitted through various messaging gateways such as text messages (SMS, LMS), multimedia messages (MMS), and KakaoTalk. In addition, in one example, the electronic recommendation message may include URL information of a landing page custom-generated for the patient. At this time, since the URL information of the landing page is dynamically generated based on the encrypted identifier and electronic recommendation data, it may be secure so that a third party other than the patient cannot view the recommendation content.
[0189] In one example, when a patient terminal user clicks the message, they can be automatically connected to a personalized product information page via a mobile web browser without the need for a separate application installation or login procedure. This landing page may visually display detailed information about the recommended health functional food (product name, ingredients, functional content, method of consumption, etc.) along with basic information such as the hospital name, attending medical staff, and recommendation date.
[0190] In addition, when multiple products are recommended together, additional information such as 'synergistic effects when taken together' and 'products purchased by other users' can be visually presented, and patients can make purchasing decisions based on this.
[0191] In step 1020, the patient terminal can transmit product purchase information to the management server in response to an electronic recommendation message. Specifically, the user of the patient terminal enters the payment process via a 'Buy Now' button on the landing page and can input delivery information, such as a shipping address, contact information, and recipient information, as well as a payment method (credit card, simple payment, etc.). In one example, when a purchase is completed, the purchase information can be automatically mapped to electronic recommendation data and transmitted to the management server. This information may include an order number, product-specific SKU code, quantity, payment amount, and delivery request details. The transmitted product purchase information can then be utilized as basic data for various subsequent processes within the server, such as order processing, logistics requests, and recommendation system training.
[0193] FIG. 11 illustrates the structure of a management server (1100) according to one embodiment of the present disclosure. The configuration exemplified in FIG. 11 can be understood as the configuration of the management server (1100). Terms such as '...part', '...unit' used below refer to a unit that processes at least one function or operation, and this may be implemented in hardware or software, or a combination of hardware and software.
[0194] The management server (1100) is a core component that controls the entire system, including the generation of electronic recommendations, message transmission, product sales integration, payment processing, data analysis, and provision of recommendation information.
[0195] Referring to FIG. 11, the server may include a communication unit (1110), a control unit (1120), and a storage unit (1130). In the present disclosure, the control unit (1120) may be defined as a circuit or an application-specific integrated circuit or at least one processor. In this case, the server may correspond to at least one of a computing server, an application server, or a data network configuration server.
[0196] The communication unit (1310) can transmit and receive signals with other network entities. The communication unit (1310) can transmit and receive information with, for example, another server through a specific interface.
[0197] According to one embodiment of the present disclosure, the communication unit (1110) can perform data transmission and reception with external devices such as a hospital terminal, a patient terminal, a pharmacy terminal, and a logistics server. For example, it may receive recommendation information from a hospital terminal, transmit an electronic recommendation message to a patient terminal, and transmit product purchase history and AI analysis information back to the hospital terminal.
[0198] The control unit (1120) can control the overall operation of the server according to an embodiment of the present disclosure. For example, the control unit (1120) can control the signal flow between each block to perform operations according to the flowchart described above.
[0199] According to one embodiment of the present disclosure, the control unit (1120) performs core operations within the management server and may include an electronic recommendation management module (1121), a user management module (1123), a data analysis module (1125), a payment management module (1127), and a deep neural network model (1129). However, the control unit (1120) may include other modules, not limited thereto.
[0200] The electronic recommendation management module (1121) can generate electronic recommendation data based on recommendation information received from a hospital terminal and generate an electronic recommendation message including a unique landing page URL and payment gateway information by linking with a user identifier.
[0201] The user management module (1123) manages authentication information and account information of system users, such as hospitals, doctors, and patients, and can perform user identification and authorization functions.
[0202] The data analysis module (1125) collects and analyzes product purchase history, patient-specific purchase patterns, satisfaction response results, etc., and can perform patient-specific product recommendation information, intake compliance prediction, and similar product suggestions in conjunction with a deep neural network (1129).
[0203] The payment management module (1127) can perform payment by linking with the payment gateway for product purchase requests occurring on the landing page and can generate product order information and delivery request information.
[0204] The deep neural network (1129) model is an AI-based prediction algorithm that learns patient-specific purchase history and product preference data to predict future recommendations and information to be used for recommendations. The information analyzed using the deep neural network (1129) may include, but is not limited to, recommended products for each patient, predicted compliance with product intake for each patient, and predicted similar product information.
[0205] The storage unit (1130) can store at least one of the information transmitted and received through the communication unit (1110) and the information generated through the control unit (1330).
[0206] According to one embodiment of the present disclosure, the storage unit (1130) is responsible for storing information of the entire system, and the storage unit (1130) may include a user database (1131) and a product database (1133). However, it is not limited thereto.
[0207] The user database (1131) can store accounts, authentication history, identifiers, etc. of users such as hospitals, medical staff, and patients to support user-based recommendation integration and analysis.
[0208] The product database (1133) stores detailed information such as product names, ingredients, instructions for use, prices, and stock of functional foods, health functional foods, etc., and can be used as basic data for electronic recommendation configuration and recommendation calculation.
[0209] In this way, the management server (1100) implements an electronic recommendation-based health functional food recommendation and sales linkage system by performing organically through each module, and can provide technical effects that improve both the recommendation convenience for medical staff and the purchase accessibility for patients.
[0211] FIG. 12 illustrates the structure of a terminal (1200) according to one embodiment of the present disclosure.
[0212] The configuration exemplified in FIG. 12 can be understood as a configuration of a terminal (1200). Terms such as '...part', '...unit' used below refer to a unit that processes at least one function or operation, and this can be implemented as hardware or software, or a combination of hardware and software.
[0213] In one example, the terminal (1200) of FIG. 12 may be the aforementioned hospital terminal (110 of FIG. 1, 110 of FIG. 2), patient terminal (130 of FIG. 1, 130 of FIG. 2), or pharmacy terminal (140 of FIG. 2). However, it is not limited thereto.
[0214] Referring to FIG. 12, the terminal (1200) may include a communication unit (1210), a control unit (1220), and a storage unit (1230).
[0215] The communication unit (1210) performs functions for transmitting and receiving signals. For example, the communication unit (1210) performs a conversion function between a baseband signal and a bit sequence according to the physical layer specifications of the system. For example, when transmitting data, the communication unit (1210) generates complex symbols by encoding and modulating the transmitted bit sequence. Also, when receiving data, the communication unit (1210) restores the received bit sequence by demodulating and decoding the baseband signal. Additionally, the communication unit (1210) upconverts the baseband signal into an RF band signal and transmits it through an antenna, and downconverts the RF band signal received through the antenna into a baseband signal. For example, the communication unit (1210) may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc.
[0216] Additionally, the communication unit (1210) may include a plurality of transmission and reception paths. Furthermore, the communication unit (1210) may include an antenna unit. The communication unit (1210) may include at least one antenna array composed of a plurality of antenna elements. In terms of hardware, the communication unit (1210) may be composed of digital circuits and analog circuits (e.g., RFIC (radio frequency integrated circuit)). Here, the digital circuits and analog circuits may be implemented as a single package. Additionally, the communication unit (1210) may include a plurality of RF chains. The communication unit (1210) may perform beamforming. The communication unit (1210) may apply beamforming weights to the signal to be transmitted or received in order to impart directionality according to the settings of the control unit (1220).
[0217] The communication unit (1210) can transmit and receive signals. To this end, the communication unit (1210) may include at least one transceiver.
[0218] Additionally, the communication unit (1210) may include different communication modules to process signals of different frequency bands. Furthermore, the communication unit (1210) may include multiple communication modules to support multiple different wireless access technologies. For example, different wireless access technologies may include Bluetooth Low Energy (BLE), Wi-Fi (Wireless Fidelity), WiGig (WiFi Gigabyte), cellular networks (e.g., LTE (Long Term Evolution), NR (new radio), etc.).
[0219] The communication unit (1210) transmits and receives signals as described above. Accordingly, all or part of the communication unit (1210) may be referred to as a 'transmitter', a 'receiver', or a 'transmitter / receiver'. Furthermore, in the following description, transmission and reception performed via a wireless channel are used to mean that processing as described above is performed by the communication unit (1210).
[0220] In one example, the communication unit (1210) can perform data transmission and reception between a hospital terminal and a management server. For example, it can transmit recommendation information for a patient to the management server and receive recommendation product information, intake compliance information, and similar product information for each patient from the management server.
[0221] The control unit (1220) can control the overall operations of the terminal (1200). For example, the control unit (1220) can transmit and receive signals through the communication unit (1210). Additionally, the control unit (1220) can write and read data from the storage unit (1230). Furthermore, the control unit (1220) can perform the functions of the protocol stack required by the communication standard. To this end, the control unit (1220) may include at least one processor. The control unit (1220) may include at least one processor or microprocessor, or may be part of a processor. Additionally, part of the communication unit (1210) and the control unit (1220) may be referred to as CP. The control unit (1220) may include various modules for performing communication. According to various embodiments, the control unit (1220) can control the terminal to perform operations according to various embodiments.
[0222] According to one embodiment of the present disclosure, the control unit (1220) controls the overall operation of the terminal and, in particular, may include an electronic recommendation management module (1221). For example, the electronic recommendation management module (1221) may support functions such as searching for and selecting recommended products (health functional foods, etc.) after selecting a patient, functions for inputting detailed recommendation information such as dosage instructions, intake period, and precautions for the selected product, and functions for structuring the input recommendation information into electronic recommendation data and transmitting it to a management server. Additionally, the electronic recommendation management module (1221) may support medical staff in establishing a more sophisticated recommendation strategy by outputting AI-based product recommendation information, intake compliance information, similar product information, etc., received from the management server onto the UI.
[0223] The storage unit (1230) can store data such as basic programs, application programs, and setting information for the operation of the terminal (1200). The storage unit (1230) may be composed of volatile memory, non-volatile memory, or a combination of volatile memory and non-volatile memory. Additionally, the storage unit (1230) can provide the stored data upon a request from the control unit (1220).
[0224] According to one embodiment of the present disclosure, the storage unit (1230) is responsible for storing information within a hospital terminal and may include a patient database (1231) and a product database (1233). However, it is not limited thereto.
[0225] The patient database (1231) stores basic information, medical history, and previous recommendation history of patients currently receiving treatment, and can be used as reference material when creating electronic recommendations.
[0226] The product database (1233) stores product lists, ingredients, uses, and medication guidance information of health functional foods synchronized from the management server, and allows for real-time product search and selection on the recommendation UI.
[0227] Meanwhile, the embodiments of the present invention disclosed in this specification and drawings are merely specific examples provided to facilitate the explanation of the technical content of the present invention and to aid in understanding the invention, and are not intended to limit the scope of the invention. That is, it is obvious to those skilled in the art that other variations based on the technical concept of the present invention are possible. Furthermore, each of the above embodiments may be combined and operated together as needed.
[0229] As described above, a method performed by a server that manages electronic recommendations and provides sales linkage information according to various embodiments disclosed in this document may include: receiving recommendation information including recommended product information from a hospital terminal; generating electronic recommendation data including a user identifier based on the recommendation information; generating payment gateway information used for payment of recommended products based on the electronic recommendation data; generating an electronic recommendation message including the electronic recommendation data and the payment gateway information; and transmitting the electronic recommendation message to a patient terminal.
[0230] According to various embodiments disclosed in this document, the method may further include the steps of receiving product purchase information corresponding to an electronic recommendation message from a patient terminal, transmitting delivery request information based on the product purchase information to a delivery logistics server, and mapping and storing the product purchase information with electronic recommendation data.
[0231] According to various embodiments disclosed in this document, the recommendation information may include medication guidance information corresponding to patient information and recommended product information.
[0232] According to various embodiments disclosed in this document, an electronic recommendation message includes URL information of a landing page accessible to a patient terminal, the URL information is dynamically generated based on identification information and electronic recommendation data corresponding to the patient terminal, and the electronic recommendation message may be transmitted to the patient terminal through a messaging gateway.
[0233] According to various embodiments disclosed in this document, the method may further include the steps of: analyzing product preference information and product purchase history information for each patient based on product purchase information mapped with electronic recommendation data; inputting product preference information and product purchase history information for each patient into a deep neural network; learning data of a group with a purchase history similar to that of the patient based on the input information to predict recommended product information for each patient; and transmitting the predicted recommended product information for each patient to a hospital terminal.
[0234] According to various embodiments disclosed in this document, the method may include the steps of: receiving delivery completion information from a delivery logistics server, sending a satisfaction survey request message to a patient terminal after a specific period, receiving a satisfaction survey response message from the patient terminal, and storing product-specific satisfaction data based on the satisfaction survey response message.
[0235] According to various embodiments disclosed in this document, the method may further include the steps of inputting product-specific satisfaction data stored in a deep neural network, the deep neural network learning the time, frequency, or change in satisfaction of a patient based on the input data to predict the level of consumption compliance for each product, and transmitting the predicted level of consumption compliance for each product to a hospital terminal.
[0236] According to various embodiments disclosed in this document, the method may further include, when recommendation information received from a hospital terminal is multiple, a step of identifying a recommended product that is recommended two or more times in the recommended product information within the multiple recommendation information; a step of inputting ingredient or usage information of the identified recommended product into a deep neural network; a step of the deep neural network analyzing the relationship between the identified recommended product and other products having similar ingredients or usage and predicting a product having a high degree of association with the recommended product; and a step of transmitting information regarding the predicted similar product to the hospital terminal.
[0237] According to various embodiments disclosed in this document, the method may further include the steps of transmitting the recommendation information to a pharmacy terminal, receiving inventory information for a recommended product included in the recommendation information from the pharmacy terminal, and transmitting the inventory status of the recommended product or information on a substitute product to a patient terminal based on the inventory information.
[0238] According to various embodiments disclosed in this document, the method may further include, prior to the step of receiving recommendation information including recommended product information from a hospital terminal, the step of receiving patient symptoms, condition, or preference information based on a deep neural network-based medical history system from a patient terminal; the step of matching hospitals and clinics by analyzing patient symptoms, condition, or preference information using a deep neural network; the step of providing a reservation interface for the matched hospitals and clinics to the patient terminal and outputting a deposit payment request to confirm the user's reservation; the step of receiving deposit payment information from the patient terminal and transmitting reservation confirmation information to the hospital terminal based on said payment information; and the step of setting the deposit payment information to be processed in such a way that it is deducted or refunded by the hospital or clinic upon treatment.
[0239] As described above, in a management server that manages electronic recommendations and provides sales linkage information according to various embodiments disclosed in this document, the management server comprises at least one transceiver, at least one processor communicatively coupled to at least one transceiver, and at least one memory communicatively coupled to one processor to store instructions, wherein the instructions are executed individually or in any combination by at least one processor, and the management server may: receive recommendation information including recommended product information from a hospital terminal, generate electronic recommendation data including a user identifier based on the recommendation information, generate payment gateway information used for payment of recommended products based on the electronic recommendation data, generate an electronic recommendation message including the electronic recommendation data and the payment gateway information, and transmit the electronic recommendation message to a patient terminal.
[0240] As described above, a method performed by a hospital terminal according to various embodiments disclosed in this document may include the steps of inputting recommendation information including recommended product information and transmitting said recommendation information to a management server, wherein the recommendation information is associated with electronic recommendation data including a user identifier, and the recommendation information includes medication guidance information corresponding to patient information and recommended product information, and may receive recommended product information for each patient predicted using a deep neural network from the management server, receive intake compliance information for each product predicted using a deep neural network from the management server, and receive information regarding similar products predicted using a deep neural network from the management server.
[0241] As described above, a method performed by a patient terminal according to various embodiments disclosed in this document comprises the steps of receiving from a management server an electronic recommendation message including electronic recommendation data including a user identifier and payment gateway information, and transmitting to the management server product purchase information corresponding to the electronic recommendation message, wherein the electronic recommendation data is based on recommendation information including recommended product information entered by a hospital terminal, and the payment gateway information is used for payment of the recommended product, and the electronic recommendation message includes URL information of a landing page accessible by the patient terminal, and the URL information is dynamically generated based on identification information and electronic recommendation data corresponding to the patient terminal, and the electronic recommendation message may be received through a messaging gateway.
Claims
Claim 1 A method performed by a server that manages electronic recommendation information and provides sales linkage information, comprising: receiving recommendation information from a hospital terminal including patient information, recommended product information, and medication guidance information corresponding to the recommended product information; generating electronic recommendation data including a user identifier based on the recommendation information; generating payment gateway information used for payment of the recommended product based on the electronic recommendation data; dynamically generating URL information of a landing page accessible to the patient terminal based on identification information corresponding to the patient terminal and the electronic recommendation data; generating an electronic recommendation message including the electronic recommendation data, the payment gateway information, and the URL information; transmitting the electronic recommendation message to the patient terminal through a messaging gateway; receiving identity authentication information from the patient terminal that has accessed the landing page corresponding to the URL information, and authenticating whether the recipient of the electronic recommendation message is the same person based on the identity authentication information; if the authentication is completed, providing the recommended product information, medication guidance information, and payment gateway information to the patient terminal through the landing page; and receiving product purchase information corresponding to the electronic recommendation message from the patient terminal. A method comprising the step of mapping and storing the product purchase information above to the electronic recommendation data. Claim 2 The method of claim 1, wherein the method further comprises the step of transmitting delivery request information based on the product purchase information to a delivery logistics server. Claim 3 delete Claim 4 delete Claim 5 The method of claim 2 further comprises: a step of analyzing product preference information and product purchase history information for each patient based on product purchase information mapped to the electronic recommendation data; a step of inputting the product preference information and product purchase history information for each patient into a deep neural network; a step of predicting recommended product information for each patient by having the deep neural network learn data of a group having a purchase history similar to that of the patient based on the input information; and a step of transmitting the predicted recommended product information for each patient to a hospital terminal. Claim 6 The method of claim 2 comprises the steps of: sending a satisfaction survey request message to a patient terminal after a specific period when delivery completion information is received from the delivery logistics server; receiving a satisfaction survey response message from the patient terminal; and storing product-specific satisfaction data based on the satisfaction survey response message. Claim 7 The method of claim 6 further comprises: a step of inputting the stored product-specific satisfaction data into a deep neural network; a step of the deep neural network learning the patient's intake discontinuation time, frequency, or satisfaction change based on the input data to predict the intake compliance level for each product; and a step of transmitting the predicted intake compliance level information for each product to a hospital terminal. Claim 8 The method of claim 1 further comprises: a step of identifying a recommended product that is recommended two or more times in the recommended product information within the plurality of recommended information when the recommendation information received from the hospital terminal is plurality of; a step of inputting ingredient or use information of the identified recommended product into a deep neural network; a step in which the deep neural network calculates a similarity between the ingredient or use of the identified recommended product and the ingredient or use of another product, and predicts a product in which the similarity is greater than or equal to a preset threshold value as a similar product; and a step of transmitting information regarding the predicted similar product to the hospital terminal. Claim 9 The method of claim 1, further comprising: transmitting recommendation information to a pharmacy terminal; receiving stock information for a recommended product included in the recommendation information from the pharmacy terminal; and transmitting the stock status of the recommended product or information on a replaceable product to a patient terminal based on the stock information. Claim 10 The method of claim 1 further comprises, prior to the step of receiving recommendation information including recommendation product information from the hospital terminal, the step of receiving patient symptoms, condition, or preference information based on a deep neural network-based medical history system from the patient terminal; the step of matching hospitals and clinics by analyzing the patient symptoms, condition, or preference information using a deep neural network; the step of providing a reservation interface for the matched hospitals and clinics to the patient terminal and outputting a deposit payment request for the user's reservation confirmation; the step of receiving deposit payment information from the patient terminal and transmitting reservation confirmation information to the hospital terminal based on said payment information; and the step of setting the deposit payment information to be processed in such a way that it is deducted or refunded at the hospital or clinic during treatment. Claim 11 In a management server that manages electronic recommendation information and provides sales linkage information: at least one transceiver; at least one processor communicatively coupled to said at least one transceiver; and includes at least one memory that is communicationally coupled to the at least one processor and stores instructions, wherein the instructions are executed individually or in any combination by the at least one processor, and the management server: receives recommendation information from a hospital terminal including patient information, recommended product information, and medication guidance information corresponding to the recommended product information; generates electronic recommendation data including a user identifier based on the recommendation information; generates payment gateway information used for payment of the recommended product based on the electronic recommendation data; dynamically generates URL information of a landing page accessible to the patient terminal based on identification information corresponding to the patient terminal and the electronic recommendation data; generates an electronic recommendation message including the electronic recommendation data, the payment gateway information, and the URL information; transmits the electronic recommendation message to the patient terminal through a messaging gateway; receives authentication information from the patient terminal that has accessed the landing page corresponding to the URL information; authenticates whether the recipient of the electronic recommendation message is the same person based on the authentication information; and when the authentication is completed, the recommended product information and the medication A management server that provides map information and payment gateway information to the patient terminal, receives product purchase information corresponding to the electronic recommendation message from the patient terminal, and stores the product purchase information by mapping it to the electronic recommendation data. Claim 12 A method performed by a hospital terminal, comprising: a step of inputting recommendation information including patient information, recommended product information, and medication guidance information corresponding to the recommended product information; and a step of transmitting the recommendation information to a management server, wherein the recommendation information is associated with electronic recommendation data including a user identifier, and the recommendation information includes patient information and medication guidance information corresponding to the recommended product information, and receiving recommended product information for each patient predicted using a deep neural network from the management server, receiving information on intake compliance for each product predicted using the deep neural network from the management server, and receiving information regarding similar products predicted using the deep neural network from the management server. Claim 13 A method performed by a patient terminal, comprising: receiving from a management server an electronic recommendation message including electronic recommendation data including a user identifier and payment gateway information; accessing a landing page using URL information included in the electronic recommendation message; transmitting personal authentication information to the management server through the landing page; receiving recommended product information, medication guidance information, and payment gateway information through the landing page when personal authentication is completed; and transmitting product purchase information corresponding to the electronic recommendation message to the management server, wherein the electronic recommendation data is based on recommendation information including patient information, recommended product information, and medication guidance information corresponding to the recommended product information entered by a hospital terminal, and the payment gateway information is used for payment of the recommended product, the electronic recommendation message includes URL information of a landing page accessible to the patient terminal, and the URL information is dynamically generated based on identification information corresponding to the patient terminal and the electronic recommendation data, and the electronic recommendation message is received through a messaging gateway.
Citation Information
Patent Citations
Method for providing user-customized health functional food and system for providing the same
KR1020220036723A
Device for recommending and selling medical supplies through user's medical information
KR102285820B1
Reservation service system using big data
KR102374126B1
Personalized health management method and system based on artificial intelligence
KR102767001B1
Pharmaceutical Matching and Sales System Using Artificial Intelligence
KR102806944B1
