Control method of electronic device and computer readable recording medium storing a program for executing the method

Abstract

A control method for an electronic device and a computer-readable recording medium storing a program for executing the method are provided. The control method for an electronic device can send a payment request for a drug to an external device, receive medication information for the drug from the external device in response to the payment request, store the medication information for the drug, and provide a medication warning for the drug to a user based on the stored medication information.

Description

Technical Field

[0001] The present disclosure relates to a method of an electronic device and a computer-readable recording medium storing a program for executing the method. More specifically, the present disclosure relates to a method of controlling an electronic device that receives medication information from an external device and provides a medication warning to a user and a computer-readable recording medium storing a program for executing the method. Background Art

[0002] As the aging population increases, the number of patients with chronic diseases is increasing. Since patients with chronic diseases must take medications at designated times, it is very important for patients with chronic diseases to manage their medications.

[0003] Generally, pharmacists instruct users about the types of oral medicines, when to take the medicines, and how to take the medicines. However, in this case, since the users take the medicines according to their memory, many users take the medicines by mistake. Therefore, the duration of taking the medicines is increased, which has an adverse effect on health and increases the cost of the medicines.

[0004] Usually, the user is accustomed to inputting medication information into an electronic device such as a smart phone, or photographing a barcode of a prescription to obtain medication information. In this case, the user must directly input medication information or photograph the prescription.

[0005] Therefore, there is an increasing need to more easily obtain medication information on electronic devices and provide medication warnings to users based on the obtained medication information. Summary of the invention

[0006] Technical issues

[0007] The present disclosure aims to solve the above-mentioned problems, and the present disclosure receives medication information while paying, and provides medication warnings based on the received medication information, thereby providing a method for controlling an electronic device that can provide users with more convenient and accurate medication management services, and a computer-readable recording medium that stores a program for executing the method.

[0008] Technical Solution

[0009] According to an embodiment of the present disclosure, a method for controlling an electronic device includes: sending a payment request for a drug to an external device; receiving medication information for the drug from the external device in response to the payment request; storing the medication information for the drug; and providing a medication warning for the drug to a user based on the stored medication information.

[0010] According to an embodiment of the present disclosure, a computer-readable recording medium storing computer executable instructions for executing a method for controlling an electronic device includes: sending a payment request for a drug to an external device; storing medication information for the drug based on medication information received from the external device in response to the payment request; and providing a medication warning for the drug to a user based on the stored medication information.

[0011] Effects of the Invention

[0012] According to the embodiments of the present disclosure as described above, the electronic device can obtain medication information without a separate user operation and provide a medication warning based on the medication information. Therefore, a more convenient and accurate medication management service can be provided to the user. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1 is a conceptual diagram showing a method for providing a medication warning service according to an embodiment of the present disclosure;

[0014] Figure 2 is a diagram showing a system for providing a medication warning service according to an embodiment of the present disclosure;

[0015] Figure 3 is a block diagram showing a configuration of an electronic device according to an embodiment of the present disclosure;

[0016] Figures 4 to 9 is a diagram showing an embodiment of acquiring medication information from a pharmacy system according to various embodiments of the present disclosure;

[0017] Fig.10 is a diagram showing an embodiment of providing a medication warning according to a device used by a user according to an embodiment of the present disclosure;

[0018] Fig.11 is a diagram showing an embodiment of providing a medication warning according to medication time according to an embodiment of the present disclosure; and

[0019] Fig.12 is a flowchart illustrating a method of controlling an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0020] According to the following description in conjunction with the accompanying drawings, the above and other aspects, features and advantages of some embodiments of the present disclosure will be more clear. However, it should be understood that the present disclosure is not limited to the specific embodiments described below, but includes various modifications, equivalents and / or substitutions of the embodiments of the present disclosure. With regard to the description of the accompanying drawings, similar reference numerals may be used for similar components.

[0021] The terms “having”, “may have”, “including” and “may include” used in the exemplary embodiments of the present disclosure indicate the existence of corresponding features (for example, elements such as values, functions, operations or components), and do not exclude the existence of other features.

[0022] In this specification, the term "A or B", "at least one of A or / and B", or "one or more of A or / and B" may include all possible combinations of the items listed together. For example, the term "A or B" or "at least one of A and / or B" may specify: (1) at least one A, (2) at least one B, or (3) both at least one A and at least one B.

[0023] As used herein, the expressions "1st", "2nd", "first" or "second" may modify various elements regardless of their order and / or importance, and are only used to distinguish one element from another. Therefore, the corresponding elements are not limited.

[0024] When one element (eg, a first element) is “operably or communicatively coupled” or “connected” to another element (eg, a second element), the element may be directly coupled to the other element or may be coupled through another element (eg, a third element).

[0025] In this specification, in some cases, the term "configured to" may be changed to, for example, "suitable for", "capable of...", "designed for", "suitable for", "made for", or "capable of". The term "configured to (set to)" does not necessarily mean "specially designed to" at the hardware level. In some cases, the term "device configured to..." may refer to a device that is "capable of" doing something with another device or component. For example, "a sub-processor configured to (or configured to) perform A, B, and C" may refer to a general-purpose processor (e.g., a central processing unit (CPU) or an application processor) that is capable of performing corresponding operations by executing one or more software programs stored in a storage device, or a dedicated processor (e.g., an embedded processor) that performs corresponding operations.

[0026] The electronic device according to various exemplary embodiments may include at least one of the following: for example, a smart phone, a tablet PC, a mobile phone, a video phone, an e-book reader, a desktop PC, a laptop PC, a netbook computer, a workstation, a server, a PDA, a portable multimedia player (PMP), an MP3 player, a medical device, a camera, or a wearable device. For example, the wearable device may include at least one of the following: an ornament (e.g., a watch, a ring, a bracelet, an anklet, a necklace, glasses, contact lenses, or a head-mounted device (HMD)), clothing or apparel (e.g., electronic apparel), a body attachment type (e.g., a skin patch or a tattoo), or a bio-implanted circuit.

[0027] The pharmacy system according to various embodiments of the present disclosure may include at least one of the following: a desktop PC, a laptop PC, a netbook computer, a workstation, a server, various medical devices, a self-service machine, a beacon server, and a beacon transmitter included in the pharmacy.

[0028] Hereinafter, the present disclosure will be described in detail with reference to the accompanying drawings.

[0029] Figure 1 is a view showing a method for providing a medication warning service according to an example embodiment. First, the pharmacy system 40 may obtain medication information of the patient. At this time, the pharmacy system 40 may obtain medication information of the patient from an external hospital server, obtain medication information by photographing a barcode (or QR code, etc.) included in a prescription provided by a user, or obtain medication information directly input by a pharmacist.

[0030] The electronic device 100 may request payment from the pharmacy system 40. In this case, the electronic device 100 may transmit a payment token to a payment terminal connected to the pharmacy system 40 through a first communication module (eg, a magnetic secure transmission (MST) communication module) included in the electronic device 100.

[0031] The pharmacy system 40 may send a payment request to the financial server 30 based on the payment token acquired through the payment terminal. The financial server 30 may approve the payment in response to the payment request and send a payment approval signal to the pharmacy system 40. In this case, the financial server 30 may send the payment approval signal to the electronic device 100 together.

[0032] When the payment approval signal is received, the pharmacy system 40 may provide the medication information to the electronic device 100. In this case, the electronic device 100 may receive the medication information through a second communication module (eg, an NFC communication module).

[0033] In addition, the electronic device 100 may perform a validity check on the received medication information. For example, the electronic device 100 may compare the user information stored in the electronic device 100 with the user information included in the medication information, or compare the payment information received by the electronic device 100 with the payment information included in the medication information to perform a validity check. When the validity of the medication information is verified, the electronic device 100 may set a medication warning based on the medication information. For example, the electronic device 100 may set a medication warning based on information about medication time, drug type, and medication method included in the medication information.

[0034] The electronic device 100 may provide a medication warning. Specifically, the electronic device 100 may provide a medication warning at a warning time set based on the medication time included in the medication information. In this case, the medication warning may include information about the type of medication and how to take the medication, and may provide the medication warning using at least one of a visual message, an auditory message, and a tactile message.

[0035] Figure 2 1 is a diagram showing a system for providing a medication warning service according to an embodiment of the present disclosure. The system 10 may include a financial server 30, a pharmacy system 40, a payment terminal 50, and an electronic device 100.

[0036] The financial server 30 may receive a signal obtained from the payment terminal 50. Specifically, when the electronic device 100 contacts the payment terminal 50 so that the payment terminal 50 receives a payment token from the electronic device 100 through a near field communication module (e.g., an MST communication module, an NFC communication module, etc.), the financial server 30 may receive a payment request based on the payment token from the payment terminal 50.

[0037] The financial server 30 may transmit a payment approval signal to the payment terminal 50 in response to the payment request. In addition, the financial server 30 may transmit the payment approval signal to the electronic device 100 and the payment terminal 50. In this case, the payment approval signal may include information on payment details.

[0038] The pharmacy system 40 can provide payment services, medication information provision services, and manufacturing services based on the pharmacy application (or software).

[0039] Specifically, the pharmacy system 40 can obtain medication information. In particular, the pharmacy system 40 can obtain the patient's medication information from an external hospital server. Alternatively, when identification information such as a barcode or QR code included in a prescription owned by the patient is photographed by a pharmacist, the pharmacy system 40 can obtain the patient's medication information. Alternatively, the pharmacy system 40 can obtain the medication information by having the pharmacist directly input the medication information according to the type of medicine included in the prescription. In this case, the medication information may include information about the medicines taken by the patient, information about the time of taking the medicine, information about the number of times the medicine is taken, information about how to take the medicine, and the like.

[0040] When the medication information is acquired, the pharmacy system 40 may enter a payment mode. During the payment mode, the pharmacy system 40 may send a payment preparation signal to the connected payment terminal 50. While maintaining the payment mode, the pharmacy system 40 may wait for a medication information providing mode.

[0041] When the payment is approved by the financial server 30, the pharmacy system 40 may send the medication information to the electronic device 100. In this case, the pharmacy system 40 may send the medication information to the electronic device 100 using a near field wireless communication module. However, the pharmacy system 40 may provide the medication information to the electronic device 100 using a communication module (e.g., an NFC communication module) different from the communication module (e.g., an MST communication module) by which the electronic device 100 sends a payment token for payment.

[0042] The payment terminal 50 can be connected to the pharmacy system 40 to perform a payment function for the patient's medicine. Specifically, the payment terminal 50 can receive a payment token from the patient's electronic device 100 using a near field communication module (e.g., an MST communication module), and send a payment request to the financial server 30 based on the received payment token. In addition, when a payment approval signal is received from the financial server 30, the payment terminal 50 can send a payment approval signal to the pharmacy system 40.

[0043] The electronic device 100 can provide medication services to users through various applications such as payment applications, medication applications, etc. In particular, the electronic device 100 can use a payment application that uses a near field communication module to perform drug payment. For example, the electronic device 100 can use an MST communication module (or an NFC communication module) to send a payment token to the payment terminal 50. In this case, the electronic device 100 can drive the medication application to provide medication information, and activate near field wireless communication (e.g., NFC communication module) in a receiving standby state.

[0044] When the payment is approved, the electronic device 100 may receive medication information from the pharmacy system 40. In this case, the medication information may include information about the medicine to be taken by the patient, information about the medication time, information about the number of medications, information about how to take medication, etc.

[0045] In particular, the electronic device 100 may check the validity of the medication information based on the user information or payment information included in the medication information. Specifically, the electronic device 100 may compare the user information stored in the electronic device 100 with the user information included in the medication information, or compare the payment information received by the electronic device 100 with the payment information included in the medication information.

[0046] When the validity of the medication information is verified, the electronic device 100 can set a medication warning based on the received medication information. In this case, the electronic device 100 can send the received medication information or information about the medication warning to an external device (e.g., an IOT device) connected to the electronic device 100.

[0047] In addition, the electronic device 100 can provide a set medication warning. In particular, the electronic device 100 can provide a medication warning based on the medication time included in the medication information. In particular, the electronic device 100 can provide a medication warning by determining the medication time in different ways according to whether the time is before or after a meal. This will be described in detail later.

[0048] According to the embodiments of the present disclosure described above, medication information for medication warning can be provided to users at the same time as payment, thereby receiving a more convenient and accurate medication information providing service.

[0049] Figure 3 is a block diagram showing a configuration of an electronic device according to an embodiment of the present disclosure. Figure 3 As shown, the electronic device 100 may include a communicator (eg, including a communication circuit) 110, a display 120, a speaker 130, a memory 140, an input interface 150, a sensor 160, and a processor 170. Figure 3 The configuration shown is an exemplary view for implementing the embodiment of the present disclosure shown. The electronic device 100 may also include appropriate hardware / software configurations that are obvious to those skilled in the art, or may omit the hardware / software configurations. Figure 3 Configuration shown.

[0050] The communicator 110 may be configured to communicate with various external devices using wireless signals. In particular, the communicator 110 may include a near field communication module for receiving payment information and medication information. In this case, the communicator 110 may include a first communication module 111 for sending a payment token to the payment terminal 50. The first communication module 111 may be implemented as an MST communication module. The MST communication module sends magnetic credit card information to the external payment terminal 50 via a root antenna and may be implemented as a separate chip. In addition, the communicator 110 may include a second communication module 113 for receiving medication information. The second communication module 113 may be implemented as an NFC communication module. In other words, the NFC communication module is a contactless near field wireless communication module that uses the 13.56MHz frequency band as one of the electronic tags (RFID), and can transmit data between terminals within a short distance of 10cm.

[0051] Meanwhile, in the above-mentioned embodiment, it has been described that the communicator 110 uses a plurality of near field communication modules to perform the payment function and the medication information receiving function, but this is only an embodiment, and one near field communication module may be used to provide the payment function and the medication information receiving function. For example, an NFC communication module capable of two-way communication may be used to perform the payment function and the medication information receiving function. Specifically, when the electronic device 100 including the NFC communication module is close to the payment terminal 50, the electronic device 100 may use the NFC communication module to send a payment token to the payment terminal 50, and when the payment is approved, medication information may be received from the payment terminal 50 connected to the pharmacy system 40.

[0052] The communicator 110 can perform communication with various types of external devices according to various types of communication methods and the above-mentioned near field communication module. The communicator 110 may include a wireless fidelity (Wi-Fi) chip, a Bluetooth chip, etc. In addition, the communicator 110 may use a long-distance communication module to provide a payment function and a medication information receiving function. This will be described below with reference to the accompanying drawings.

[0053] In addition, the communicator 110 may transmit the medication information received from the pharmacy system 50 to an external device (eg, an IOT device).

[0054] The display 120 may provide various screens. In particular, the display 120 may provide a UI screen for providing medication warnings. In this case, the UI screen may include information about the medicines taken by the patient, the method of taking the medicine, etc.

[0055] The speaker 130 may output an audio signal. In particular, the speaker 130 may provide information about a medication warning audibly. For example, when it is time to take a medication, the speaker 130 may provide an auditory feedback (e.g., a voice message, a beep, etc.) indicating a medication warning. In this case, the speaker 130 may be provided in the electronic device 100, but this is only an embodiment, and the speaker 130 may be electrically connected to the electronic device 100.

[0056] The memory 140 may store instructions or data related to at least one of the other elements of the electronic device 100. In particular, the memory 120 may be implemented as a non-volatile memory, a volatile memory, a flash memory, a hard disk drive (HDD), a solid state drive (SDD), etc. The memory 120 may be accessed by the processor 170, and read, record, correct, delete, update, etc. may be performed. According to an embodiment of the present disclosure, the term "memory" may include the memory 140, a read-only memory (ROM) (not shown) and a random access memory (RAM) (not shown) within the processor 170, and a memory card (not shown) (e.g., a micro secure digital (SD) card or a memory stick) connected to the electronic device 100.

[0057] In particular, the memory 140 may store a payment application and a medication application. In this case, the payment application is an application for performing a payment function, and may send a payment token to an external payment terminal through a near field communication module. In addition, the medication application may provide a medication warning based on medication information received from the pharmacy system 40 through the communicator 110.

[0058] The input interface 150 can receive various user inputs and send them to the processor 170. In particular, the input interface 150 may include a touch sensor, a (digital) pen sensor, a pressure sensor, a button, or a microphone. The touch sensor may, for example, use at least one of an electrostatic type, a pressure-sensitive type, an infrared type, and an ultraviolet type. The digital pen sensor may be, for example, a part of a touch panel or include an additional sheet for identification purposes. The button may, for example, include a physical button, an optical button, or a keypad. In particular, the input interface 150 may obtain an input signal based on a user input for executing only an artificial intelligence program.

[0059] The sensor 160 can detect various environmental information. Specifically, the sensor 160 may include various sensors for acquiring biometric information of the user (e.g., a glucose enzyme sensor, a non-invasive glucose sensor, a calorie sensor, a blood pressure sensor, etc.). In addition, the sensor 160 may include an image sensor (i.e., a camera) for photographing the surrounding environment of the electronic device 100.

[0060] Meanwhile, the sensor 160 may be included in the electronic device 100 , but this is merely an embodiment, and the sensor 160 may be connected to the electronic device 100 through a communication interface (eg, Bluetooth).

[0061] The processor 170 is electrically connected to the communicator 110, the display 120, the speaker 130, the memory 140, the input interface 150, and the sensor 160 to control the overall operation and function of the electronic device 100. In particular, when the payment is approved through the first communication module 111, the processor 170 can receive medication information about the drug from an external device (e.g., the pharmacy system 40 or the payment terminal 50) through the second communication module 113. In addition, the processor 170 can store the medication information about the drug in the memory 140, and provide a medication warning to the user based on the stored medication information.

[0062] In particular, the processor 170 may compare the user information stored in the electronic device 100 with the user information included in the medication information, or compare the payment information received by the electronic device 100 with the payment information included in the medication information, to check the validity of the medication information. When the validity of the medication information is verified, the processor 170 may set a medication warning for the drug based on the medication information, and if the validity of the medication information is not verified, the processor 170 may output a message indicating a verification failure.

[0063] In addition, the processor 170 may identify the warning time based on the medication time included in the medication information, and provide a medication warning at the identified warning time. In particular, when the medication time is after a meal, the processor 170 may identify whether the warning time has been reached. When the warning time is reached, the processor 170 may identify whether the user has had a meal, and when it is identified that the user has had a meal, the processor 170 may provide a medication warning after a predetermined time. In addition, when it is identified that the user has not had a meal, the processor 170 may provide a message suggesting a meal and suggesting medication to the user. In this case, the processor 170 may identify whether the user has had a meal based on at least one of the following: image information taken by the electronic device 100 or an IoT device connected to the electronic device 100, biometric information of the user acquired by the sensor 160 included in the electronic device 100, and card payment information received by the electronic device 100. At the same time, when the medication time is before a meal, the processor 170 may provide a medication warning at the default medication time included in the warning time. In this case, the default medication time may be pre-stored when the medication application is installed, and may be changed by user settings. Furthermore, the processor 170 may collect meal times of the user of the electronic device 100 and provide a medication warning at a time updated based on the collected meal times.

[0064] In the following, reference will be made to Figures 4 to 9 Various embodiments for obtaining information from a pharmacy system are described.

[0065] Figure 4 2 is a diagram showing an embodiment of acquiring medication information using two communication modules according to an embodiment of the present disclosure.

[0066] The pharmacy system 40 may enter a payment mode (S405). Specifically, when the patient's medication information is acquired from an external server or medication information is acquired from a prescription, the pharmacy system 40 may enter a payment mode for paying for the medicine.

[0067] While maintaining the payment mode, the pharmacy system 40 may request the payment terminal 50 to wait for payment (S410). In this case, the pharmacy system 40 may wait for the medication information to be sent.

[0068] The electronic device 100 can drive the payment application (S415) according to the user input. In this case, the payment application is an application that can perform payment using the first communication module (e.g., MST communication module) 111. In this case, while running the payment application, the electronic device 100 can also run the drug application. In this case, the drug application can be executed in the background, and when the drug application is executed, the electronic device 100 can activate the second communication module (e.g., NFC communication module) 113 together. At the same time, as described above, this is only an embodiment of running the drug application while the payment process is ongoing, and the drug application can be run after the drug payment is approved. Alternatively, the electronic device 100 can use GPS information, network connection information, etc. included in the electronic device 100 to identify the location of the electronic device 100, and when it is identified that the electronic device 100 is in a hospital or a pharmacy, the electronic device 100 can run the drug application. In this case, when running the drug application, the electronic device 100 can run the payment application together. In other words, the drug application can be operated in association with the payment application.

[0069] The electronic device 100 may perform user authentication for payment (S420). In this case, user authentication may be performed using user biometric information (eg, iris, fingerprint, face, etc.) or based on a password input by the user.

[0070] When the electronic device 100 approaches the payment terminal 50 after performing user authentication, the electronic device 100 may transmit a payment token using the first communication module 111 (S425). In this case, the payment token may include information about credit card information arbitrarily assigned for security.

[0071] When receiving the payment token, the payment terminal 50 may request payment from the financial server 30 ( S430 ).

[0072] When the payment is approved based on the information included in the payment token, the financial server 30 may send a payment approval signal to the payment terminal 50 (S435). In this case, the payment approval signal may include information about the payment details. The payment terminal 50 may send the payment approval information to the pharmacy system 40 (S440). At the same time, when the payment approval information is sent to the payment terminal 50 or the pharmacy system 40, the payment terminal 50 or the pharmacy system 40 may output a message to keep the electronic device 100 in contact with the payment terminal 50. In this case, the message may be output through a display included in the payment terminal 50, but this is merely an embodiment, and the message may be output through a speaker included in the payment terminal 50 or the pharmacy system 40.

[0073] In addition, the financial server 30 may send a signal for notifying the completion of payment to the electronic device 100 (S445). In this case, information about the payment details may also be included in the signal for notifying the completion of payment. When the signal for notifying the completion of payment is sent, the electronic device 100 may deactivate the first communication module 111 for payment (S450).

[0074] The pharmacy system 40 may send the medication information to the payment terminal 50 (S455). In this case, the pharmacy system 40 may send the medication information to the payment terminal 50 after the payment is completed, but this is only an embodiment, and the pharmacy system 40 may send the medication information to the payment terminal 50 before the payment is completed.

[0075] The payment terminal 50 may send medication information to the electronic device 100 using the second communication module 113 (S460). In this case, the medication information may include information about the patient, information about payment details, information about the medicine, information about the medication time, information about the number of medications, and information about how to take the medicine. Meanwhile, when the electronic device 100 is not close to the payment terminal 50 to send the medication information through the second communication module 113, the payment terminal 50 may output a message requesting the electronic device 100 to approach.

[0076] Meanwhile, in the above-mentioned embodiment, it has been described that the pharmacy system 40 sends the medication information to the electronic device 100 through the payment terminal 50 , but this is only an embodiment, and the pharmacy system 40 may directly send the medication information to the electronic device 100 .

[0077] The electronic device 100 may check the validity of the received medication information (S465). Specifically, the electronic device 100 may compare the information about the patient (e.g., the patient's name, etc.) included in the medication information with the information about the user (e.g., the user name for logging into the medication application) stored in the electronic device 100 to check the validity of the medication information. Alternatively, the electronic device 100 may compare the payment details included in the medication information with the payment details included in the payment completion notification sent from the financial server 30 to the electronic device 100 to check the validity of the medication information.

[0078] When the validity of the medication information is verified, the electronic device 100 can set a medication warning for the drug based on the medication information (S470). Specifically, the electronic device 100 can set the time to take the medication based on the information about the medication time included in the medication information, and set the medication warning to provide the medication warning at the set time. However, if the validity of the medication information is not verified, the electronic device 100 can output a message indicating that the verification failed. In other words, the electronic device 100 can request to resend the medication information or output a message that the medication information verification failed.

[0079] When the medication warning is set, the electronic device 100 may send a completion response to the payment terminal 50 (or the pharmacy system 40) (S475). At this time, the electronic device 100 may output a message guiding that the medication information has been acquired through a speaker or a display.

[0080] Figure 5 2 is a diagram showing an embodiment of acquiring medication information using one communication module according to an embodiment of the present disclosure. Operations S505 to S520 are the same as operations S405 to S420, and thus repeated descriptions thereof are omitted.

[0081] When the electronic device 100 approaches the payment terminal 50 after performing user authentication, the electronic device 100 may transmit a payment token (S525). In this case, the electronic device 100 may transmit the payment token using a communication module capable of two-way communication such as an NFC communication module.

[0082] When receiving the payment token, the payment terminal 50 may request payment from the financial server 30 ( S530 ).

[0083] If the payment is approved based on the information included in the payment token, the financial server 30 may send a payment approval signal to the payment terminal 50 (S535). In this case, the payment approval signal may include information about payment details. The payment terminal 50 may then send the payment approval information to the pharmacy system 40 (S540).

[0084] In addition, the financial server 30 may send a signal for notifying the completion of payment to the electronic device 100 (S545). In this case, information about the payment details may also be included in the signal for notifying the completion of payment. Meanwhile, in the above-mentioned embodiment, it has been described that the signal for notifying the completion of payment from the financial server 30 is directly sent to the electronic device 100, but this is only an embodiment, and the financial server 30 may send a signal for notifying the completion of payment to the electronic device 100.

[0085] The pharmacy system 40 may send the medication information to the payment terminal 50 (S550). At this time, the pharmacy system 40 may send the medication information to the payment terminal 50 after the payment is completed, but this is only an embodiment, and the pharmacy system 40 may send the medication information to the payment terminal 50 before the payment is completed.

[0086] The payment terminal 50 may transmit the medication information to the electronic device 100 (S555). In this case, the payment terminal 50 may transmit the medication information using a communication module (eg, NFC communication module) that previously transmitted the payment token.

[0087] The electronic device 100 may check the validity of the received medication information (S560). When the validity of the medication information is verified, the electronic device 100 may set a medication warning for the drug based on the medication information (S565). However, if the validity of the medication information is not verified, the electronic device 100 may output a message indicating that the verification failed. In other words, the electronic device 100 may request to resend the medication information or output a message indicating that the medication information verification failed.

[0088] When the medication warning is set, the electronic device 100 may send a completion response to the payment terminal 50 (or the pharmacy system 40 ) ( S570 ).

[0089] Figure 6 2 is a diagram showing an embodiment of providing medication information using a self-service machine according to an embodiment of the present disclosure.

[0090] The self-service machine 60 may receive the prescription (S605). In this case, the self-service machine 60 may receive the prescription by photographing identification information such as a QR code, a barcode, etc. included in the prescription. In another embodiment, the self-service machine 60 may receive the prescription from an external server (e.g., a server present in a hospital) based on patient information input by the patient.

[0091] The self-service machine 60 may enter a payment mode (S610). During the payment mode, the self-service machine 60 may generate medication information based on information about the medicines included in the input prescription. In addition, the self-service machine 60 may generate payment details based on the information about the medicines included in the prescription and wait for payment.

[0092] At the same time, the electronic device 100 may run a payment application (S615). In this case, the electronic device 100 may run a payment application based on a user input, but this is only an embodiment, and the payment application may be automatically run based on an application currently executed on the electronic device 100 (e.g., a medication application) or the location of the electronic device 100.

[0093] The electronic device 100 may perform user authentication for payment (S620).

[0094] When the electronic device 100 approaches the area where the communication module included in the self-service machine 60 is located, the electronic device 100 may send a payment token (S625). In this case, the payment token may be sent through a near field communication module such as an NFC communication module.

[0095] When receiving the payment token, the self-service machine 60 may request payment from the financial server 30 (S630).

[0096] When the payment is approved based on the information included in the payment token, the financial server 30 may send a payment approval signal to the self-service machine 60 (S635). In this case, the payment approval signal may include information about the payment details. In addition, the self-service machine 60 may send a signal to the electronic device 100 for notifying that the payment is completed (S640).

[0097] The self-service machine 60 may send a payment completion signal and dispensing information (S645) to the pharmacy system 40. In this case, the pharmacy system 40 may automatically dispense the medicine based on the dispensing information, or may display the dispensing information on a display so that a pharmacist can dispense the medicine.

[0098] In addition, the self-service machine 60 may send the acquired medication information to the electronic device 100 (S650). In this case, the medication information may include information about the patient, information about payment details, information about the medicine, information about medication time, information about medication frequency, and information about medication method.

[0099] The electronic device 100 may check the validity of the received medication information (S655).

[0100] When the validity of the medication information is verified, the electronic device 100 can set a medication warning for the medication based on the medication information (S660). Specifically, the electronic device 100 can set the medication time based on the information about the medication time included in the medication information, and set the medication warning to provide the medication warning at the set time.

[0101] The self-service machine 60 may print the medication instructions (S665). Specifically, the self-service machine 60 may print the medication instructions including medication information and provide it to the user. The self-service machine 60 may send a drug delivery completion response signal to the pharmacy system 40 (S670).

[0102] Figure 7 2 is a diagram showing an embodiment of providing medication information using a beacon server according to an embodiment of the present disclosure.

[0103] The pharmacy system 40 may enter a payment mode (S705). Specifically, when the patient's medication information is acquired from an external server or medication information is acquired from a prescription, the pharmacy system 40 may enter a payment mode for paying for the medicine.

[0104] While maintaining the payment mode, the pharmacy system 40 may request the payment terminal 50 to wait for payment (S710). In this case, the pharmacy system 40 may wait for the medication information to be sent through the beacon server 70.

[0105] The electronic device 100 may execute the medicine application (S715). In this case, the electronic device 100 may execute the medicine application according to the user input, but this is only an embodiment, and the medicine application may be automatically executed based on the location information of the electronic device 100.

[0106] The payment terminal 50 may receive a payment request (S720). In this case, when a normal credit card is detected, the payment terminal 50 may receive a payment request. However, this is only an embodiment, and the payment terminal 50 may receive a payment request through an input of a pharmacist or a payment token received from the electronic device 100.

[0107] The payment terminal 50 may request payment from the financial server 30 ( S725 ).

[0108] When the payment is approved based on the information included in the payment token, the financial server 30 may send a payment approval signal to the payment terminal 50 (S730). In this case, the payment approval signal may include information about the payment details. The payment terminal 50 may send the payment approval signal to the pharmacy system 40 (S735). At the same time, the financial server 30 may send payment information including the payment details to the electronic device 100 (S745). In this case, the financial server 30 may send the payment information including the payment details as a text message.

[0109] The pharmacy system 40 may send the medication information to the beacon server 70 (S740). In this case, the pharmacy system 40 may send the medication information to the beacon server 70 after the payment is completed, but this is only an embodiment, and the pharmacy system 40 may send the medication information to the beacon server 70 before the payment is completed.

[0110] The beacon transmitter 80 may transmit a beacon universal unique identifier (UUID) (S750). In this case, the beacon transmitter 80 may transmit the beacon UUID at a predetermined time period (eg, once per second), and the electronic device 100 may receive the beacon UUID received from the beacon transmitter 80.

[0111] When the beacon UUID is received, the electronic device 100 may transmit payment information to the beacon server 70 in response to the beacon UUID (S755). In this case, the payment information may include information on the payment date and time and the payment amount.

[0112] The beacon server 70 checks the medication information corresponding to the payment information based on the payment information received from the electronic device 100 (S760). In other words, the beacon server 70 may check the medication information corresponding to the payment details transmitted by the electronic device 100 in the medication information transmitted by the pharmacy system 40.

[0113] The beacon server 70 may transmit the medication information to the electronic device 100 (S765).

[0114] As reference Figure 4 As described, the electronic device 100 may check the validity of the medication information (S770) and set a medication warning (S775).

[0115] Figure 8 2 is a view showing another embodiment of providing medication information using a beacon server according to an embodiment of the present disclosure.

[0116] The pharmacy system 40 may enter a payment mode (S805). Specifically, when the patient's medication information is acquired from an external server or medication information is acquired from a prescription, the pharmacy system 40 may enter a payment mode for paying for the medicine.

[0117] While maintaining the payment mode, the pharmacy system 40 may request the payment terminal 50 to wait for payment (S810). In this case, the pharmacy system 40 may wait for the medication information to be sent.

[0118] In addition, the pharmacy system 40 may request the beacon server 70 to wait for payment (S815). In this case, the beacon server may wait for the execution of drug payment. In this case, the pharmacy system 40 may send information about the user ID of the application and drug payment information to the beacon server 70 together.

[0119] At the same time, the electronic device 100 may run the medicine application (S820). In this case, the medicine application may be run by a user input, but this is only an embodiment, and the medicine application may be run based on the location of the electronic device 100.

[0120] The beacon transmitter 80 may transmit the beacon UUID (S825). In this case, information about the beacon server may be stored in the beacon UUID.

[0121] The electronic device 100 may execute the payment application based on the beacon UUID (S830). In this case, the payment application and the medication application may be logged in using the same user ID.

[0122] In addition, the electronic device 100 may transmit user information to the beacon server 70 (S835). In this case, the user information may include information on a user ID of the application.

[0123] The beacon server 70 may transmit payment details to the electronic device 100 based on the user information (S840).

[0124] The electronic device 100 may send a payment request to the beacon server 70 (S845). In this case, the payment request may include payment details and information for initiating payment (eg, user ID).

[0125] The beacon server 70 may send the payment details to the payment terminal 50 ( S850 ).

[0126] The payment terminal 50 may request payment from the financial server 30 (S855). In this case, the payment terminal 50 may send information about payment details to the financial server 30 together.

[0127] The financial server 30 may send a payment approval signal to the payment terminal 50 (S860). In this case, the payment approval signal may include information about payment details. The payment terminal 50 may send the payment approval information to the pharmacy system 40 (S865). The pharmacy system 40 may send medication information to the beacon server 70 (S870). In this case, the pharmacy system 40 may send the medication information to the beacon server 70 after the payment is completed, but this is only an embodiment, and the medication information may be sent to the beacon server 70 before the payment is completed.

[0128] The beacon transmitter 80 may transmit a beacon universal unique identifier (UUID) (S875). In this case, the beacon transmitter 80 may transmit the beacon UUID at a predetermined time period (eg, once per second), and the electronic device 100 may receive the beacon UUID received from the beacon transmitter 80.

[0129] When the beacon UUID is received, the electronic device 100 may transmit user information to the beacon server 70 in response to the beacon UUID (S880). In this case, the user information may include a user ID.

[0130] The beacon server 70 identifies medication information corresponding to the payment information based on the user information transmitted by the electronic device 100 (S885). In other words, the beacon server 70 may identify medication information corresponding to the user information transmitted by the electronic device 100 among medication information transmitted by the pharmacy system 40.

[0131] The beacon server 70 may transmit the medication information to the electronic device 100 (S890).

[0132] As reference Figure 4 As described above, the electronic device 100 may check the validity of the medication information (S895) and set a medication warning (S897).

[0133] Fig. 9 2 is a diagram showing an embodiment in which medication information is directly input by a user.

[0134] The pharmacy system 40 may enter a payment mode (S905). Specifically, when the patient's medication information is acquired from an external server or medication information is acquired from a prescription, the pharmacy system 40 may enter a payment mode for paying for the medicine.

[0135] While maintaining the payment mode, the pharmacy system 40 may request the payment terminal 50 to wait for payment (S910).

[0136] The payment terminal 50 may receive a payment request (S915). In this case, when a normal credit card is detected, the payment terminal 50 may receive a payment request. However, this is only an example, and the payment terminal 50 may receive a payment request through an input of a pharmacist or a payment token received from the electronic device 100.

[0137] The payment terminal 50 may request payment from the financial server 30 ( S920 ).

[0138] When the payment is approved based on the information included in the payment token, the financial server 30 may transmit a payment approval signal to the payment terminal 50 (S925). In this case, the payment approval signal may include information on payment details.

[0139] The financial server 30 may transmit the payment information to the electronic device 100 (S930). In this case, the financial server 30 may transmit the payment information including the payment details through a short message service (SMS) or a multimedia message service (MMS).

[0140] The electronic device 100 can identify whether to run the medication application (S935). Specifically, the electronic device 100 can identify whether to run the medication application based on the payment information received from the financial server 30 and the location information of the electronic device. For example, when the text "pharmacy" and "hospital" are included in the payment information, and the payment amount is greater than or equal to the threshold, the electronic device 100 can run the medication application. In addition, if the current location of the electronic device 100 is identified as a hospital or a pharmacy based on the GPS and the connected network information, the electronic device 100 can run the medication application. Alternatively, if the location information of the electronic device is identified as "hospital" or "pharmacy" after purchasing the medicine, the electronic device can run the medication application when returning home and provide the user with a UI for inputting medication information.

[0141] When the medication application is running, the electronic device 100 may display a medication information input request screen (S940). In this case, the medication information input request screen may include UI elements for inputting the type of medicine, medication time (before or after meals), medication method, etc. Alternatively, the medication information input request screen may include a guide message for guiding the user to take a QR code, a barcode, etc. of a prescription including medication information.

[0142] The electronic device 100 may obtain medication information through the medication information input request screen (S945). Specifically, the electronic device 100 may obtain medication information through user input, and when the QR code or barcode of the prescription is photographed, the electronic device 100 may obtain medication information based on pre-stored medication information.

[0143] The electronic device 100 may set a medication warning based on the acquired medication information (S950).

[0144] As in the above-mentioned embodiments, the electronic device 100 may acquire medication information through various methods, and may provide a medication warning based on the acquired medication information.

[0145] In particular, the electronic device 100 can provide a medication warning according to the user's condition. Specifically, the electronic device 100 can provide a medication warning according to the type of device used by the user.

[0146] Fig.10 2 is a view showing an embodiment of providing a medication warning according to a device used by a user according to an embodiment of the present disclosure.

[0147] The electronic device 100 may detect the occurrence of a medication warning event (S1010). Specifically, when a warning time determined based on medication information is reached, the electronic device 100 may detect the occurrence of a medication warning event.

[0148] The electronic device 100 may identify whether the user is carrying the electronic device 100 (S1020). Specifically, the electronic device 100 may identify whether the user is using the electronic device 100, whether the movement of the electronic device 100 is detected, whether biometric information is detected by the sensor 160 included in the electronic device 100, etc.

[0149] If it is recognized that the user carries the electronic device 100 (S1020-Yes), the electronic device 100 may provide a medication warning using the electronic device 100 (S1030). Specifically, the electronic device 100 may provide a message warning medication through the display 120, and may provide a warning message through the speaker 130. Alternatively, the electronic device 100 may provide vibration feedback for the medication warning using a vibration unit.

[0150] If it is identified that the user does not carry the electronic device 100 (S1020-No), the electronic device 100 may identify whether the external device connected to the electronic device 100 is used (S1040). Specifically, the electronic device 100 may identify whether the external device is used by identifying the user's position photographed by a camera of the external device connected to the electronic device 100 and whether a user command is input to the external device. In particular, when the user does not carry the electronic device 100, the electronic device 100 may identify whether the external device is used by sending a query to the external device to inquire whether the user has used the external device.

[0151] When it is recognized that the user is using the external device 100 (S1040-Yes), the electronic apparatus 100 may transmit information about the medication warning to the external device that the user is using (S1050). Therefore, the external device may provide the user with the medication warning.

[0152] When it is identified that the user is not using the external device 100 (S1040-No), the electronic device 100 may determine the location of the electronic device 100 (S1060). In this case, the electronic device 100 may identify the location where the electronic device 100 is currently located based on a GPS included in the electronic device 100 or information about a network connected to the electronic device 100.

[0153] The electronic device 100 may provide a preset medication warning according to the identified location (S1070). Specifically, when the electronic device 100 is implemented as a mobile terminal or a wearable device, if the electronic device 100 is identified as being outdoors, the electronic device 100 may preferentially provide a medication warning through the electronic device 100. However, if the electronic device 100 is identified as being indoors, the electronic device 100 may provide a medication warning through a preset device (e.g., a robot, an electronic device, etc.).

[0154] Fig.112 is a view showing an embodiment of providing a medication warning according to a medication time according to an embodiment of the present disclosure.

[0155] The electronic device 100 may identify the medication time (S1105). Specifically, the electronic device 100 may identify whether the medication is taken before or after a meal based on the medication time included in the medication information.

[0156] When the medication time is after a meal (S1110-Yes), the electronic device 100 can set a warning time (S1115). Specifically, the electronic device 100 can set a morning time (e.g., 7 to 9 o'clock), a lunch time (e.g., 11 to 13 o'clock), and an evening time (e.g., 18 to 20 o'clock).

[0157] In addition, when the warning time is reached (S1120-Yes), the electronic device 100 can identify whether the user has eaten (S1125). In this case, the electronic device 100 can identify whether the user has eaten based on at least one of the following: image information captured by the electronic device 100 or an IoT device connected to the electronic device 100, biometric information of the user acquired by the sensor 160 included in the electronic device 100, and card payment information received by the electronic device 100. For example, when the electronic device 100 is smart glasses or the external device connected to the electronic device 100 is a robot, the electronic device 100 can analyze the image captured by the smart glasses or the robot to identify whether the user is eating. Alternatively, the electronic device 100 can identify whether the user has eaten by using a continuous blood glucose measurement sensor to identify whether the blood glucose has risen above a preset value for a predetermined time. Alternatively, the electronic device 100 can recognize whether a meal has been eaten by detecting changes in blood sugar via a PPG sensor, an optical sensor, an electromagnetic sensor, an impedance sensor, etc., by detecting whether the body temperature has increased via metabolic thermal conformation (MHC), and by measuring a certain amount of tears or sweat. Alternatively, if "restaurant" or the like is included in the card payment details sent to the electronic device 100, the electronic device 100 can recognize that the user has eaten.

[0158] When the user has eaten (S1125-Yes), the electronic device 100 can provide a medication warning (S1130). When the user has not eaten (S1125-No), the electronic device 100 can provide meal suggestions and medication information. In particular, when the warning time has expired and the user has not eaten, the electronic device 100 can suggest eating to take medicine, and provide medication information based on the meal. For example, if it is past 13 o'clock and you have not eaten during lunch time (11 o'clock to 13 o'clock), the electronic device 100 can provide meal suggestions and medication information.

[0159] Meanwhile, when the medication time is not after a meal (e.g., the medication time is before a meal or has nothing to do with whether or not a meal is taken) (S1110-No), the electronic device 100 may set a default medication time (S1140). For example, the electronic device 100 may set a general meal time (e.g., breakfast is 9 a.m., lunch is 1 p.m., and dinner is 6 p.m.) as the default medication time.

[0160] After setting the default medication time, the electronic device 100 may collect the meal time (S1145). In other words, as described above, the electronic device 100 may identify whether the user has eaten and collect the identified meal time.

[0161] The electronic device 100 can update the medication time based on the collected meal time (S1150). For example, if it is identified that the user usually eats breakfast at 8 am, lunch at 12:30 pm, and dinner at 7 pm, the electronic device 100 can update the medication time to 8 am, 12:30 pm, and 7 pm respectively.

[0162] In addition, the electronic device 100 may provide a medication warning at the updated time (S1155).

[0163] Fig.12 is a flowchart illustrating a method of controlling an electronic device according to an embodiment of the present disclosure.

[0164] The electronic device 100 may send a payment request for the medicine (S1210). In this case, the electronic device 100 may request payment from the financial server 30 through the payment terminal 50 using the first communication module 111 (eg, MST communication module).

[0165] The electronic device 100 may receive medication information for the drug (S1220). Specifically, when payment is approved from the financial server 30 in response to the payment request, the electronic device 100 may receive medication information from the pharmacy system 40 using the second communication module 113 (e.g., NFC communication module) through the payment terminal 50.

[0166] The electronic device 100 may store the received medication information (S1230). In this case, the electronic device 100 may check the validity of the received medication information to store the medication information.

[0167] The electronic device 100 may provide a medication warning based on the medication information (S1240). Specifically, the electronic device 100 may provide a medication warning at a medication time identified based on the medication time included in the medication information.

[0168] The various example embodiments described above may be implemented as an S / W program including instructions stored on a machine-readable (e.g., computer-readable) storage medium. A machine is a device that is capable of calling stored instructions from a storage medium and operating according to the called instructions, and may include an electronic device (e.g., electronic device A) according to the example embodiments described above. When an instruction is executed by a processor, the processor may directly execute the function corresponding to the instruction, or may use other components to execute it under the control of the processor. A command may include code generated or executed by a compiler or interpreter. A machine-readable storage medium may be provided in the form of a non-transitory storage medium. Here, the term "non-transitory" only means that the storage medium does not include a signal but is tangible, and does not distinguish between a case where data is semi-permanently stored in a storage medium and a case where data is temporarily stored in a storage medium.

[0169] According to an embodiment of the present disclosure, the method according to the above various embodiments may be provided as part of a computer program product. The computer program product may be traded between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., a compact disk read-only memory (CD-ROM)), or may be downloaded through an application store (e.g., PlayStore). TM ) Online distribution. In the case of online distribution, at least a part of the computer program product may be at least temporarily stored or temporarily generated on a storage medium such as a manufacturer's server, an application store's server, or a memory of a relay server.

[0170] The various components (e.g., modules or programs) according to various exemplary embodiments may include a single entity or multiple entities, and some of the corresponding subcomponents described above may be omitted, or another subcomponent may be added to the various exemplary embodiments. Alternatively or additionally, some components (e.g., modules or programs) may be combined to form a single entity that performs the same or similar functions as the corresponding elements before the combination. The operations performed by the modules, program modules, or other components according to various exemplary embodiments may be sequential, parallel, or both, performed repeatedly or heuristically, or at least some operations may be performed in different orders, omitted, or other operations may be added.

Claims

1. A control method performed by an electronic device, the control method comprising: sending a payment request for the medicine to a first external device; receiving medication information for the drug from the first external device in response to receiving a signal for notifying completion of payment for the payment request; checking the validity of the medication information by comparing the payment information included in the received signal with the payment information included in the medication information; Based on the validity of the medication information being verified, automatically storing the received medication information and setting a medication warning for the drug according to the medication information; Setting a warning time based on the medication time included in the medication information and identifying whether the medication is taken before or after a meal; determining whether the warning time has been reached; When it is determined that the warning time has been reached, if the medicine is taken after a meal, identifying whether the user has eaten a meal based on at least one of image information captured by the electronic device or an IoT device connected to the electronic device, biometric information of the user acquired by a sensor included in the electronic device, or card payment information received by the electronic device; as well as When it is recognized that the user has eaten, a medication warning for the drug is provided to the user, and when it is recognized that the user has not eaten, a message suggesting a meal and medication is provided to the user, When it is identified that the user has eaten, it is identified whether the movement of the electronic device is detected. When it is recognized that the motion of the electronic device is detected, providing the medication warning through the electronic device, When it is identified that the motion of the electronic device is not detected, identifying whether the second external device is used by sending a query to the second external device to query whether the user uses the second external device, When it is recognized that the user is using the second external device, information about the medication warning is sent to the second external device being used by the user, so as to provide the medication warning through the second external device. When it is identified that the user is not using the second external device, identifying the current location of the electronic device based on a GPS included in the electronic device, When the electronic device is identified as being outdoors based on the location, the medication warning is preferentially provided through the electronic device, and When the electronic device is identified as being indoors based on the location, the medication warning is provided through a preset device.

2. The control method according to claim 1, further comprising: Sending the payment request information to the first external device using a magnetic secure transmission (MST) communication module including a communication circuit; as well as The medication information for the drug is received from the first external device using a near field communication (NFC) communication module including a communication circuit.

3. The control method according to claim 1, further comprising: Sending the payment request information to the first external device using an NFC communication module including a communication circuit; as well as The medication information for the drug is received from the first external device using the NFC communication module including a communication circuit.

4. The control method according to claim 1, further comprising: The validity of the medication information is checked by comparing the user information stored in the electronic device with the user information included in the medication information.

5. The control method according to claim 1, further comprising: Based on the fact that the validity of the medication information is not verified, a message indicating a verification failure is output.

6. The control method according to claim 1, wherein: The medication warning is a first medication warning, and The control method further comprises: Based on the received medication information including that the medication time for the drug is before a meal, a second medication warning is provided at the default medication time included in the warning time, Wherein, the electronic device is configured as: collecting meal times of users of the electronic device, and The second medication warning is provided at a time updated based on the collected meal times.

7. A computer-readable recording medium storing computer-executable instructions, wherein when the computer-executable instructions are executed, the electronic device executes a control method, the control method comprising: sending a payment request for the medicine to a first external device through a first communication module including a communication circuit; In response to receiving a signal for notifying completion of payment for the payment request, receiving medication information for the drug from the first external device through a second communication module including a communication circuit; checking the validity of the medication information by comparing the payment information included in the received signal with the payment information included in the medication information; Based on the validity of the medication information being verified, automatically storing the received medication information and setting a medication warning for the drug according to the medication information; Setting a warning time based on the medication time included in the medication information and identifying whether the medication is taken before or after a meal; determining whether the warning time has been reached; When it is determined that the warning time has been reached, if the medicine is taken after a meal, identifying whether the user has eaten a meal based on at least one of image information captured by the electronic device or an IoT device connected to the electronic device, biometric information of the user acquired by a sensor included in the electronic device, or card payment information received by the electronic device; as well as When it is recognized that the user has eaten, a medication warning for the drug is provided to the user, and when it is recognized that the user has not eaten, a message suggesting a meal and medication is provided to the user, When it is identified that the user has eaten, it is identified whether the movement of the electronic device is detected. When it is recognized that the motion of the electronic device is detected, providing the medication warning through the electronic device, When it is identified that the motion of the electronic device is not detected, identifying whether the second external device is used by sending a query to the second external device to query whether the user uses the second external device, When it is recognized that the user is using the second external device, information about the medication warning is sent to the second external device being used by the user, so as to provide the medication warning through the second external device. When it is identified that the user is not using the second external device, identifying the current location of the electronic device based on a GPS included in the electronic device, When the electronic device is identified as being outdoors based on the location, the medication warning is preferentially provided through the electronic device, and When the electronic device is identified as being indoors based on the location, the medication warning is provided through a preset device.

8. The computer-readable recording medium according to claim 7, in, The payment request information is sent to the first external device using a magnetic secure transmission (MST) communication module including a communication circuit, and The medication information for the drug is received from the first external device using a near field communication (NFC) communication module including a communication circuit.

9. The computer-readable recording medium according to claim 7, in, The payment request information is sent to the first external device using an NFC communication module including a communication circuit, and The medication information for the drug is received from the first external device using the NFC communication module including a communication circuit.

10. The computer-readable recording medium according to claim 7, wherein: The control method further includes checking validity of the medication information by comparing user information stored in the electronic device with user information included in the medication information.

11. The computer-readable recording medium according to claim 7, wherein: The control method further comprises: Based on the fact that the validity of the medication information is not verified, a message indicating a verification failure is output.

Images