KR102172364B1 - Prescription delivery system using two-channel in cloud computing environment and the control method thereof - Google Patents

Abstract

In an embodiment according to the present invention, a pharmacy member 400 installed in a pharmacy that dispenses drugs according to a prescription issued from the medical institution member 100, and a request for issuing a prescription from a plurality of medical institution members 100 through an external network Upon receipt, the cloud member 200 having a drug code 600 including drug data and a cloud management terminal 210 that generates an electronic prescription divided into the patient's personal information and the cloud management terminal 210 through an external network ) To receive and store the drug code 600 from the user terminal 300, and the pharmacy member 400 is a reader terminal 420 and a reader that receives the drug code 600 received from the user terminal 300 A cloud including a pharmacy terminal 410 that requests personal information matching the drug code 600 received from the terminal 420 to the cloud member 200 to complete an electronic prescription including drug data and patient personal information It is possible to provide a two-channel prescription delivery system in a computing environment.

Description

Two-channel prescription delivery system in a cloud computing environment and its control method {PRESCRIPTION DELIVERY SYSTEM USING TWO-CHANNEL IN CLOUD COMPUTING ENVIRONMENT AND THE CONTROL METHOD THEREOF}

The present invention relates to a two-channel prescription delivery system in a cloud computing environment and a control method thereof.

Conventionally, if a patient was issued a paper-type prescription from a hospital, he could go to a pharmacy and submit the prescription to receive a prescription.

Since such paper prescriptions are not easy to store, there is a risk of loss or damage. In addition, basically, hospitals issue prescriptions for patient storage and prescriptions for pharmacy submissions to patients, so there is a problem that paper is used unnecessarily. For this reason, if the hospital issues only prescriptions for pharmacy submissions to patients, patients For me, it can be difficult to get information about the prescription history once the prescription has been submitted to the pharmacy.

In order to solve this problem, electronic prescriptions have recently been used. The doctor writes the prescription details in an electronic document at the time of treatment and transmits the electronic prescription to the external electronic prescription authorized storage server, and the pharmacy visited by the patient connects to the electronic prescription authorized storage server to inquire the patient's electronic prescription to dispense drugs. I can.

However, there is a risk of hacking in the process of transmitting the electronic prescription containing the patient's personal information to an external server through the network. Also, in the event of an exceptional situation such as modification or reissuance of the electronic prescription in the hospital, the paper prescription In comparison, the processing procedure can be cumbersome.

Accordingly, by making it possible to easily issue a prescription and present it to a pharmacy using a mobile device held by a patient, the loss, damage, and environmental problems of the paper prescription can be solved, and by not going through an external server. There is a demand for a technology to protect the patient's personal information by blocking the possibility of hacking.

In addition, conventionally, a kiosk that can be linked with a prescription issuing system of a medical institution has been installed in a pharmacy for issuing and receiving electronic prescriptions, and an electronic prescription of a patient who has designated a pharmacy can be directly received at the pharmacy, but the kiosk terminal is expensive. The installation cost can be increased accordingly.

Moreover, the receipt of a prescription through the terminal of the kiosk is possible to issue an electronic prescription only when the patient has designated a pharmacy, and most of the patients print out a paper prescription, so that the utility is less than the price.

Korean Patent Publication No. 10-1811789 (2017.12.18)

The present invention was devised to solve the conventional problem, and the object of the present invention is to replace all prescriptions with electronic prescriptions, manage prescription drug information and patient personal information in a cloud computing environment, and separate them into two channels. It is to provide a two-channel prescription delivery system in a cloud computing environment that can prevent leakage of personal information by providing it to patients (or agents) and pharmacies.

In addition, another object of the present invention is to provide an automatic drug order management system using a two-channel prescription delivery system in a cloud computing environment capable of calculating the inventory status of a pharmacy and automatically placing an order in connection with a two-channel prescription delivery system in a cloud computing environment. .

In addition, another object of the present invention is a two-channel cloud computing environment that can automatically correct errors in prescriptions by converting prescriptions of multiple medical institutions into big data, and guide pharmacies that can be dispensed through inventory status of each pharmacy. It is to provide a prescription delivery system and an automatic drug order management system using the same.

Therefore, the present invention may include the following embodiments to achieve the above object.

An embodiment of the present invention is a pharmacy member installed in a pharmacy that dispenses drugs according to a prescription issued from a member of a medical institution, and a drug code including drug data when a request for issuing a prescription is received from a plurality of member of the medical institution through an external network. And a cloud member having a cloud management terminal that generates an electronic prescription divided into patient's personal information, and a user terminal that receives and stores drug codes from the cloud management terminal through an external network, and the pharmacy member receives from the user terminal Cloud computing environment including a reader terminal receiving the drug code and a pharmacy terminal that requests personal information matching the drug code received from the reader terminal in the absence of the cloud to complete an electronic prescription containing drug data and patient's personal information It can provide a two-channel prescription delivery system.

The present invention provides a drug code including drug data and personal information separately from a user and a pharmacy in a two-channel method, and the leakage of personal information is prevented by managing the patient's personal information in a cloud computing environment. have.

In addition, the present invention can deliver an electronic prescription as a QR code and a POS terminal capable of detecting it, so that a paper prescription can be completely replaced, and there is an effect that can be installed at low cost.

In addition, in the present invention, it is possible to prepare for a failure of a user terminal or an error in a drug code according to a network environment, thereby minimizing user inconvenience caused by transmission and reception of electronic prescriptions, thereby improving safety.

In addition, the present invention manages electronic prescriptions and pharmacy inventory status in a cloud computing environment, thereby facilitating inventory management of pharmacies, and providing information on pharmacies that can be dispensed for each prescription to patients, thereby improving patient convenience. .

1 is a block diagram showing a two-channel prescription delivery system and a control method in a cloud computing environment according to the present invention.
Figure 2 is a block diagram showing a medical institution member of the present invention.
3 is a block diagram of an unmanned terminal.
4 is a block diagram of a cloud management terminal.
5 is a block diagram of a user terminal.
6 is a diagram showing an example of a QR code.
7 is a diagram showing another example of a QR code.
8 is a block diagram of a pharmacy terminal.
9 is a flowchart illustrating a control method of a two-channel prescription delivery system in a cloud computing environment according to the present invention.
10 is a flow chart showing step S220.
11 is a flow chart showing step S300.
12 is a flow chart showing step S230.
13 is a flowchart illustrating step S440.

Terms and words used in this specification and claims are not limited to the usual or dictionary meanings, and the inventor is based on the principle that the concept of terms can be appropriately defined in order to describe the user's invention in the best way. It should be interpreted as a meaning and concept consistent with the technical idea of the present invention.

Throughout the specification, when a part "includes" a certain component, it means that other components may be further included rather than excluding other components unless specifically stated to the contrary. In addition, “… Wealth”, “… Ki”, “… However, terms such as "," "module", and "device" mean a unit that processes at least one function or operation, which may be implemented by a combination of hardware and/or software.

User terminals described herein include mobile phones, smart phones, laptop computers, digital broadcasting terminals, personal digital assistants (PDAs), portable multimedia players (PMPs), navigation systems, and slate PCs. , Tablet PC, ultrabook, wearable device, e.g., smartwatch, glass-type terminal (smart glass, HMD (head mounted display)), electronic card, etc. May be included.

In addition, the communication unit and the network described in the present specification are any one or a combination of two or more of known communication devices enabling wired/wireless communication networks and wired/wireless LAN, WiFi, Bluetooth, infrared, RF, and NFC communication by a communication service provider. One or several may be combined depending on the device, location and purpose. As such communication devices are generally known technologies, the name of the installed device and the communication unit are collectively referred to, and detailed descriptions thereof are omitted.

And the external network environment described in this specification includes wireless communication that performs communication according to various communication standards such as IEEE, Zigbee, 3rd Generation (3G), 3rd Generation Partnership Project (3GPP), and Long Term Evoloution (LTE). I can.

Hereinafter, a two-channel prescription delivery system and a control method for a cloud computing environment according to the present invention will be described in detail with reference to the accompanying drawings.

1 is a block diagram showing a two-channel prescription delivery system in a cloud computing environment according to the present invention.

Referring to FIG. 1, the two-channel prescription delivery system of the cloud computing environment according to the present invention receives the patient's personal information and prescription from the medical institution member 100 and the medical institution member 100 to issue a prescription, A user terminal 300 that receives a cloud member 200 for issuing a prescription and a drug code 600 (see FIGS. 6 and 7) including drug data and an authentication key from the cloud member 200, and a user terminal A pharmacy member 400 for completing an electronic prescription and dispensing prescription drugs by combining the patient's personal information from the drug code 600 of 300 and the cloud member 200, and drugs according to the order of the pharmacy member 400 It includes a supplier terminal 500 that supplies.

The medical institution member 100 refers to a medical institution capable of issuing a prescription, such as a hospital, a clinic, or a health book. Here, the medical institution member 100 transmits the patient's personal information, the patient's agent information, the medicine prescribed to the patient, and data and codes indicating the diagnosis name to the cloud member 200.

The cloud member 200 includes a database 220 storing medical institution, pharmacy, and prescription information, and a cloud that generates an electronic prescription and transmits the drug code 600 and personal information to the user terminal 300 and the pharmacy member 400. It includes a management terminal 210.

The database 220 includes medical institution-specific information (e.g., address, medical subject, doctor, phone number, etc.), patient and/or patient agent information, user terminal information, and a medical institution DB 221 that stores prescriptions, etc. , It may include a pharmacy DB 222 in which the location of the pharmacy and the inventory status of the drug and/or pharmacist information is stored, and a prescription DB 223 that accumulates and stores and classifies prescriptions.

Here, the prescription DB 223 may convert prescriptions issued before and after into big data (BIG-DATA), and then classify and store prescription drug data and drug codes according to diagnosis names or diagnosis codes. That is, the cloud member 200 converts prescription information according to symptoms into big data.

In addition, the cloud management terminal 210 converts prescriptions received from a plurality of medical institution members 100 into big data, and generates an electronic prescription according to the prescription.

The electronic prescription is transmitted through different channels by dividing medicine data consisting of codes or information designating prescribed medicines and personal information of patients. Accordingly, the cloud member 200 transmits the drug code 600 including the prescribed drug data to the user terminal 300 and transmits the patient's personal information to the pharmacy member 400.

Here, it is preferable that the personal information transmitted to the pharmacy member 400 is encrypted.

In addition, the drug code 600 is issued including drug data, identification information identifying the patient himself and/or his/her agent and/or a decryption key capable of releasing encrypted personal information, issuance information of the drug code, and period of use. At least one of information and a one-time authentication key may be included. More preferably, the drug code 600 may be provided to the user terminal 300 as a QR code.

That is, in the present invention, the prescription drug information required for the prescription and the patient's personal information are provided separately from each other, thereby replacing the paper prescription and preventing leakage of the patient's personal information.

The user terminal 300 receives and outputs the medicine code 600 received from the cloud member 200. Here, the user corresponds to a mobile terminal registered by either the patient himself or an agent designated by the patient, and the information of the user terminal 300 may be registered in the cloud member 200 through the medical institution member 100.

The pharmacy member 400 includes a reader terminal 420 that receives the drug code 600 from the user terminal 300, and a one-time authentication key and/or issued information included in the drug code 600 of the reader terminal 420 It includes a pharmacy terminal 410 for outputting an electronic prescription by requesting the patient's personal information from the cloud management terminal 210 and a dispensing terminal 430 for outputting the electronic prescription. That is, the pharmacy member 400 completes an electronic prescription by combining the drug data and personal information received through two channels, and prepares the drug accordingly.

The medical institution member 100 described above will be described in detail with reference to FIGS. 2 and 3.

2 is a block diagram showing a member of a medical institution according to the present invention, and FIG. 3 is a block diagram of an unmanned terminal.

2 and 3, the medical institution member 100 includes a treatment terminal 110 for inputting prescription drugs and personal information, an institution server 120 for maintaining and managing the internal network environment of the medical institution member, and a prescription application And an unmanned terminal 130 requesting registration of the user terminal 300.

The treatment terminal 110 registers prescription drugs and personal information of patients by doctors and/or related staff (nurse or administrative staff). The treatment terminal 110 may be driven by a separate information input program for this purpose.

The institution server 120 maintains and manages the internal network environment, and mediates access to the external network environment. In addition, the institutional server 120 may receive and store drug prescriptions, patient personal information, and storage and reception information between the medical treatment terminal 110 and the unmanned terminal 130, and may perform cost payment in connection with the financial server.

In addition, the institution server 120 transmits to the cloud management terminal 210 in response to a request (eg, a prescription issuance request) from the unmanned terminal 130 or the treatment terminal 110. In addition, the institutional server 120 may receive and store drug information that can be dispensed for each pharmacy received from the cloud management terminal 210 and provide it to the unmanned terminal 130 and/or the treatment terminal 110.

The unmanned terminal 130 proceeds to receive treatment, search for a pharmacy, receive geographic information, and register the user terminal 300 through, for example, a selection instruction input as a kiosk and information received from the institution server 120. .

Specifically, the unmanned terminal 130 communicates with the unmanned terminal control unit 131 that controls to input and output information according to the selection command, the institution server 120 and the treatment terminal 110 and/or the cloud management terminal 210 It includes an unmanned terminal communication unit 132 and an unmanned terminal display 133 that outputs information according to a user's selection command.

Among them, the unmanned terminal display 133 is a touch-type display and outputs a plurality of menus and results according to the menu selection.

The unmanned terminal communication unit 132 communicates with the institution server 120 and the treatment terminal 110 and/or the cloud management terminal 210 under the control of the unmanned terminal control unit 131. Alternatively, the unmanned terminal communication unit 132 communicates with a server of a financial institution in order to receive expenses. Here, the unmanned terminal communication unit 132 refers to a device in which short-range wireless communication with a user terminal and wired and wireless communication devices for communication with a cloud management terminal and/or a medical treatment terminal are combined. This corresponds to a combination of known communication devices, and thus a detailed description thereof has been omitted.

However, the unmanned terminal communication unit 132 is characterized in that any one of an NFC recording device, Bluetooth, and infrared communication device is further included so as to record a one-time authentication key to be described later on the user terminal 300.

The unmanned terminal control unit 131 communicates with a reception module 131a for generating patient reception information, a pharmacy search module 131b for searching pharmacies that can be dispensed by geography and prescription of a pharmacy, and a financial server (not shown). The storage module 131c for paying the cost through the method, the geographic information module 131d for outputting geographic information of the selected region, the prescription application module 131e for outputting a prescription request signal, and information of the user terminal 300 It includes an information registration module (131f) for registering.

The reception module 131a generates a patient's reception and medical records and transmits them to the treatment terminal 110. That is, when a patient or a patient's agent (hereinafter collectively referred to as a user) applies for medical treatment through the unmanned terminal display 133, the reception module 131a generates the patient's reception record and provides the institution through the unmanned terminal communication unit 132. It is transmitted to the server 120 or the treatment terminal 110.

The geographic information module 131d outputs geographic information of the selected area through the unmanned terminal display 133. That is, the geographic information module 131d outputs an electronic map.

The pharmacy search module 131b is linked with the geographic information module 131d to display a pharmacy corresponding to the keyword input by the user on the electronic map provided by the geographic information module 131d and output to the unmanned terminal display 133. have.

Here, the pharmacy search module 131b may guide a pharmacy capable of preparing a prescription drug prescribed to a corresponding user received from the cloud management terminal 210.

To this end, the cloud management terminal 210 holds information on the status of medicines held in all registered pharmacies, and may provide it to the unmanned terminal 130.

Such drug holding status information is provided in real time to the unmanned terminal 130 through the institution server 120, or transmitted from the cloud management terminal 210 according to a real-time request from the unmanned terminal 130.

For example, the pharmacy search module 131b checks the prescription information associated with the user and requests pharmacy information that can prepare the corresponding drug to the cloud management terminal 210 and/or the institution server 120. In addition, the pharmacy search module 131b outputs pharmacy information for preparing the received prescription to the unmanned terminal display 133.

The receiving module 131c calculates and receives the payment cost of the user through the treatment terminal 110 and/or the institution server 120. To this end, the storage module 131c may be connected to an external financial server (not shown).

When a prescription selection command is input through the unmanned terminal display 133, the prescription application module 131e requests the user's prescription from the cloud management terminal 210. Here, the prescription request may include medicines and personal information included in the prescription created from the treatment terminal 110 and information on the user terminal 300 registered by the information registration module 131f.

The information registration module 131f requests the cloud management terminal 210 to register information of the user terminal 300. Here, the user terminal 300 information may include whether the patient himself or herself or the patient's agent, and a phone number.

In addition, the information registration module 131f may request the user terminal 300 to issue a one-time authentication key when the user terminal 300 is registered with the cloud management terminal 210. The one-time authentication key is to enable the issuance of an electronic prescription for the patient in case of a failure to receive the drug code 600 due to an error in the user terminal 300 or an external network environment, damage to the drug code, or in an emergency situation. .

Therefore, the one-time authentication key may be received from the cloud management terminal 210 in the unmanned terminal 130 and directly transmitted to the user terminal 300. This can be implemented by adding a short-range wireless communication device (eg, Bluetooth, WiFi, NFC) to the unmanned terminal communication unit 132.

For example, the unmanned terminal communication unit 132 includes an NFC recording device, and the user terminal includes an NFC receiving device, respectively. And the information registration module (131f) records the one-time authentication key received from the cloud management terminal 210 in the user terminal 300 tagged to the NFC recording device.

The one-time authentication key may be transmitted from the cloud management terminal 210 to the user terminal 300. It is preferable that the one-time authentication key is automatically deleted according to a set condition or a response according to whether the cloud management terminal 210 is received after one use.

In addition, the information registration module 131f may generate identification information and include it in a prescription for a corresponding patient. Here, the identification information may be divided into a patient code assigned to the patient and a patient agent code indicating a patient agent.

For example, if the patient identification code is a code in which a total of eight numbers are combined, the identification code of the patient agent may be assigned an agent code indicating the agent in addition to the patient identification code. Therefore, through such identification information, pharmacies can identify whether they are the person or a legitimate agent, so that normal users can be identified.

Such a patient ID code and a patient agent code may be generated when the user terminal 300 is registered through the information registration module 131f of the unmanned terminal 130 and transmitted to the cloud member 200 together with a prescription.

Alternatively, the identification information may be collectively generated in the cloud member 200 and included in the drug code 600. The generation of identification information corresponds to any one of various embodiments and does not limit the subject in the present invention.

In addition, the unmanned terminal control unit 131 as described above may be installed in the treatment terminal 110. That is, in the present invention, reception, pharmacy search, receipt, geographic information, prescription application, and registration of the user terminal 300 are possible in the unmanned terminal 130 or the treatment terminal 110, which can be selectively applied.

4 is a block diagram of a cloud management terminal.

Referring to FIG. 4, the cloud management terminal 210 includes a management terminal control unit 211 that performs control according to a request between a medical institution member 100, a user terminal 300, and a pharmacy member 400, and a medical institution member 100. ), and a management terminal communication unit 212 performing communication with the user terminal 300 and the pharmacy member 400, and a management terminal display 213.

The management terminal communication unit 212 communicates with the medical institution member 100, the pharmacy member 400, and the user terminal 300. An external network environment is established for this, and description thereof is omitted as this is a known configuration.

The management terminal control unit 211 includes an error correction module 211a for searching for and correcting errors in the prescription drug code 600, an output control module 211b for transmitting and outputting the searched information by searching the database 220, and electronic An electronic prescription generation module 211c for generating a prescription, a code division module 211d for dividing the drug code 600, an encryption module 211e for encrypting personal information and generating a decryption key, and a one-time authentication key It includes an authentication key generation module (211f) for generating.

The error correction module 211a compares the drug data (code) received from the institution server 120 and/or the unmanned terminal 130 with prescription information stored in the database 220 to determine whether the received drug data (code) is an error. Check and correct.

The output control module 211b searches the database 220, and information set in the user terminal 300, the unmanned terminal 130, and the pharmacy terminal 410 (e.g., pharmacy information available for each prescription, drug code ( 600), one-time authentication key, personal information).

For example, the output control module 211b searches the database 220 to search for pharmacy information, drug code 600, and patient personal information that can be dispensed of drugs included in the prescription. Here, the pharmacy information that can be dispensed may be processed and transmitted at the request of the unmanned terminal 130 and/or the institutional server 120 or may be transmitted to the user terminal 300 after receiving a prescription request.

In addition, when the drug code 600 is received from the pharmacy member 400, the output control module 211b searches for the patient's personal information matched with the drug code 600 from the medical institution DB, Send.

In addition, when the one-time authentication key is received, the output control module 211b may retrieve the associated personal information and drug code 600 and retransmit it to the user terminal 300 or transmit it to the pharmacy terminal 410. Here, when the one-time authentication key is received, the output control module 211b responds to the reception of the one-time authentication key to the user terminal 300 set in association.

The electronic prescription generation module 211c checks the prescription information received through the institution server 120 and/or the unmanned terminal 130 to generate an electronic prescription. Here, the electronic prescription is divided into personal information and a drug code 600. Among them, the drug code 600 may include at least one of drug data, a decryption key, identification information including whether the patient himself or herself or an agent, issuance information, and a one-time authentication key.

Among them, the issuance information may include an issuance number of the drug code 600 linked to the personal information, and an available period.

In addition, the drug code 600 is a QR code, which may be implemented in various embodiments as shown in FIGS. 6 and 7.

Of these, referring to Figure 6, the drug code 600 according to the present invention is a QR code that is different for each data (eg, drug data, decryption key, identification information, issue information, or one-time authentication key). It can be generated as codes 611 to 614. Alternatively, drug data, decryption key, issue information, one-time authentication key or identification information may all be included in one QR code 610.

Here, the decryption key is a code for decrypting the encrypted personal information, and the one-time authentication key is the deletion of the drug code 600 due to a non-reception of the drug code 600 or an error in the user terminal 300 according to the external network environment. As a preparation for damage, it may be included in the drug code 600 or may be separately transmitted when registering in the user terminal 300 of the unmanned terminal 130.

As shown in FIG. 7, the code dividing module 211d divides the corresponding QR codes 621 and 622 when a plurality of data is stored in one QR code, and the connection points (a, b, and) of the divided QR codes c, d) generate information. The connection point (a, b, c, d) information may correspond to coordinate information of a dividing line arbitrarily set in the complete QR code. That is, the QR code can be divided and assembled in the same manner as a puzzle through the connection points (coordinate information) (a, b, c, d). In addition, the connection point may be linked to either of the issued information and the identification information.

For example, one of the divided QR codes is transmitted to the user terminal 300, and the remaining one is stored in the database 220. Therefore, when the divided QR code received from the user terminal 300 is received from the pharmacy member 400, the divided QR code having the connection point (a, b, c, d) information matching the corresponding QR code is searched and the drug code Generates 600.

In this way, the incomplete drug code 600 is transmitted to the user terminal 300, and the drug code 600 is received by receiving the incomplete drug code 600 from the pharmacy member 400 in the cloud management terminal 210. It will be completed.

Therefore, the output control module 211b receives the incomplete drug code 600, searches for the drug code 600 on the other half, completes the drug code 600, and stores patient personal information matching the drug code 600. It can be retrieved and transmitted to the pharmacy member 400 together with the drug code 600. That is, the code splitting module 211d is proposed to increase the security of the drug code 600.

The encryption module 211e encrypts the patient's personal information generated by the electronic prescription generating module 211c and generates a decryption key capable of decrypting the encrypted personal information.

That is, the cloud management terminal 210 transmits the encrypted personal information to the pharmacy member 400, and the pharmacy member 400 decrypts the encrypted personal information through the decryption key obtained from the user terminal 300. Information leakage is fundamentally prevented. Preferably, personal information is encrypted every time an electronic prescription is generated, and a decryption key is generated accordingly.

The authentication key generation module 211f generates a one-time authentication key. Here, it is preferable that the one-time authentication key is automatically deleted from the user terminal 300 after one use, or a period of use is set. In addition, the one-time authentication key is issued only to the user terminal 300 registered in the unmanned terminal 130, and may be included in the drug code 600 or transmitted separately.

5 is a block diagram of a user terminal.

Referring to FIG. 5, the user terminal 300 includes a user terminal control unit 310, a user terminal communication unit 320, and a user terminal display 330.

Here, the user terminal communication unit 320 includes both remote and short-range wireless devices. In particular, the user terminal communication unit 320 may include at least one of an NFC receiving device, a Bluetooth, and an infrared communication device so as to receive a one-time authentication key through short-range wireless communication with the unmanned terminal communication unit 132.

The user terminal control unit 310 includes a medicine code receiving module 311 for receiving and storing the medicine code 600 received through the user terminal communication unit 320, and a one-time authentication key storage module storing a one-time authentication key ( 312).

The medicine code receiving module 311 outputs the medicine code 600 received through the user terminal communication unit 320 on the user terminal display 330. Here, it is preferable that the drug code receiving module 311 automatically deletes the drug code 600 when a set period/time has elapsed regardless of whether or not it is used.

The one-time authentication key storage module 312 stores the one-time authentication key and transmits it to the pharmacy member 400 through a short-range wireless communication device (eg, NFC communication) of the user terminal communication unit 320. Here, the one-time authentication key storage module 312 may automatically delete the one-time authentication key when a response from the cloud management terminal 210 or a set period elapses after use.

8 is a block diagram of a pharmacy terminal.

Referring to FIG. 8, the pharmacy terminal 410 includes a pharmacy terminal control unit 411 for completing and outputting an electronic prescription using a drug code 600 received from a reader terminal 420, a cloud management terminal 210, and It includes a pharmacy terminal communication unit 412 communicating with the reader terminal 420, a pharmacy terminal display 413 for outputting inventory information and an electronic prescription, and an inventory DB 414 for storing inventory information.

The pharmacy terminal communication unit 412 communicates with the reader terminal 420 through an internal network and the cloud management terminal 210 through an external network. Since the internal and external networks are generally known technologies, detailed descriptions are omitted.

The pharmacy terminal display 413 outputs various information by the pharmacy terminal controller 411 such as electronic prescriptions, inventory status information, and order form. Here, the pharmacy terminal display 413 may share output information with the dispensing terminal 430.

Here, the dispensing terminal 430 may output an electronic prescription to a pharmacist as a terminal installed in, for example, a dispensing room, and transmit input dispensing information to the pharmacy terminal 410. Dispensing information includes the type and quantity of drugs used in this prescription.

In addition, the dispensing terminal 430 and the pharmacy terminal 410 may be installed as the same.

The inventory DB 414 stores inventory status information. Here, the inventory status information is updated in real time by the inventory management module 411e, and may be transmitted to the cloud management terminal 210 when a set time period or when a specific drug is insufficient.

The pharmacy terminal control unit 411 includes a reading information receiving module 411a for receiving the drug code 600 received from the reader terminal 420 and an information requesting module 411b for requesting personal information from the cloud management terminal 210 And, an electronic prescription output module 411c that completes and outputs an electronic prescription, an information management module 411d that transmits information on dispensable drugs, an inventory management module 411e that monitors inventory status and shortage of stock, and stock It includes an order form generating module 411f for generating and transmitting an order form for insufficient medicines.

The reading information receiving module 411a receives the drug code 600 of the reader terminal 420 received through the internal network, and includes drug data, a decryption key, and identification information included in the drug code 600, At least one of the one-time authentication keys is output.

For example, the reader terminal 420 reads the QR code output on the display 330 of the user terminal 300 as a POS terminal that detects the QR code and transmits it to the pharmacy terminal control unit 411.

Therefore, the reading information receiving module 411a receives this, extracts a plurality of pieces of data included in the QR code, and checks whether the QR code can be used. Here, the availability of the QR code may be recorded in the QR code itself as data or text including, for example, an issue number and/or a usage period.

The information request module 411b checks the identification information extracted from the reading information receiving module 411a and controls the pharmacy terminal communication unit 412 to request the cloud management terminal 210 for personal information matching the identification information.

Here, when the information request module 411b receives the unfinished medicine code 600 (divided QR code 621), it checks the issuance information of the divided QR code and transfers personal information and completed medicine data to the cloud management terminal 210 ).

Alternatively, when the one-time authentication key is received, the information request module 411b transmits the authentication information included in the one-time authentication key to the cloud management terminal 210, and the drug code 600 and personal information matched with the authentication information Request.

Alternatively, the information request module 411b may request retransmission of the medicine code 600 to the user terminal 300.

That is, in the present invention, the drug code 600 is requested to be retransmitted to the user terminal 300 using a one-time authentication key, or the drug code 600 and personal information are transferred from the pharmacy terminal 410 to the cloud management terminal 210. You can request it directly.

The electronic prescription output module 411c receives the encrypted personal information received from the pharmacy terminal communication unit 412, decrypts the encryption key with the decryption key included in the drug code 600, and combines it with the drug data to complete the electronic prescription. The completed electronic prescription is transmitted to the dispensing terminal 430 through the pharmacy terminal communication unit 412. Alternatively, the electronic prescription may be output on the pharmacy terminal display 413.

The information management module 411d checks drug inventory status information in real time and transmits drug information that can be dispensed to the cloud management terminal 210. That is, the information management module 411d transmits inventory status information to the cloud management terminal 210 in real time, for each set period, and for each event (exhaustion of specific drugs).

The inventory management module 411e generates inventory status information and updates inventory status information in real time by adding or subtracting pharmaceuticals used due to pharmaceutical preparation from the inventory quantity. Here, the inventory management module 411e may update the current inventory status information by checking the type and quantity of each drug included in the electronic prescription, or update the inventory status information through the dispensing information received from the dispensing terminal 430.

In addition, the inventory management module 411e alerts the occurrence of an event as a message when a shortage of inventory of a specific medicine is detected. Such event occurrence information is transmitted to the cloud management terminal 210 through the information management module 411d. The cloud management terminal 210 determines that a prescription through the drug is impossible when a drug that is out of stock in the drug is generated. Therefore, the cloud management terminal 210 can guide the user terminal 300 and/or the unmanned terminal 130 to the user terminal 300 and/or the unmanned terminal 130 excluding the corresponding pharmacy from information on the pharmacy that can be dispensed according to the prescription.

The order form generation module 411f generates an order form according to the occurrence of an event of the inventory management module 411e. Here, the order form is output on the pharmacy terminal display 413, and the order form may be completed with a previously automatically set quantity, or the order form may be completed through manually inputted information.

That is, the order form generation module 411f sets the order quantity for each drug and information (eg, email address, fax number) of the supplier terminal 500, and automatically sets when an out of stock event occurs for the drug. An order form for ordering quantity is generated and can be automatically transmitted to the supplier terminal 500.

Alternatively, the order form generation module 411f completes the order form through information according to the manual input of the manager, and transmits the order form to the selected supplier terminal 500.

The two-channel prescription delivery system of the cloud computing environment according to the present invention includes the above configuration, and a control method of the two-channel prescription delivery system of the cloud computing environment according to the present invention will be described below.

9 is a flowchart illustrating a control method of a two-channel prescription delivery system in a cloud computing environment according to the present invention.

Referring to FIG. 9, the present invention includes step S100 of registering user information and registering prescriptions in the absence of a medical institution, storing prescriptions and user information in the cloud member 200 (S210), and generating an electronic prescription to generate a user terminal 300. ) And the pharmacy member 400, step S200 of separately transmitting, and step S300 of receiving the drug code 600 from the user terminal 300, and the drug code of the user terminal 300 in the pharmacy member 400 ( 600) and requesting personal information from the cloud member 200 (S420) by reading (S410) to complete and output the electronic prescription (S430).

Among them, step S100 is a step of registering user information. Here, the user information is the patient's personal information input through the treatment terminal 110, the user terminal 300 information (e.g., patient's phone number, agent's phone number), reception and medical records, payment and payment information At least one of them may be included. The patient personal information of the treatment terminal 110 is transmitted to the cloud member 200 through the institution server 120.

In addition, the unmanned terminal 130 performs payment in connection with the financial server when the user selects the payment of medical expenses through the unmanned terminal 130 after treatment, and registers the user terminal 300 information.

Here, the unmanned terminal 130 requests and receives a one-time authentication key from the cloud member 200 when registering and/or issuing a prescription for the user terminal 300 and transmits the request to the user terminal 300. The one-time authentication key is transmitted to the user terminal 300 by the NFC recording device of the unmanned terminal 130. Alternatively, the one-time authentication key may be transmitted together with the drug code 600.

The step S200 includes a step S210 of storing personal information of the medical institution member 100, the user terminal 300, and a prescription in the cloud member 200, and a step S220 of generating an electronic prescription and transmitting it through two channels.

Step S210 is a step of classifying and storing prescriptions, patient personal information, and user terminal 300 information received from the plurality of medical institution members 100 in the cloud management terminal 210. Here, the cloud management terminal 210 classifies and stores prescription drugs for each diagnosis, converts them into big data, and stores them. In addition, the cloud management terminal 210 generates a one-time authentication key when registering the user terminal 300 and transmits it directly to the unmanned terminal 130 or the user terminal 300.

In step S220, when a prescription request is received, an electronic prescription in which the drug code 600 and personal information are separated is generated, and transmitted to the user terminal 300 and the pharmacy terminal 410 as two channels. This step S220 will be described with reference to FIG. 10.

10 is a flow chart showing step S220.

Referring to FIG. 10, step S220 includes steps S221 of checking and correcting errors, step S222 of generating an encryption and decryption key for personal information, step S223 of generating and transmitting a drug code 600, and a pharmacy terminal 410 Step S224 of determining whether a request for personal information from) is received, step S225 of transmitting encrypted personal information, step S226 of storing personal information transmission history information, and step S227 of determining whether a one-time authentication key is received And, including the step S228 of determining whether to transmit the drug code 600 and/or personal information to the pharmacy terminal 410 and/or the user terminal 300 by checking the issuance record of the prescription matching the disposable authentication key do.

In step S221, the cloud management terminal 210 checks an error in the received prescription and corrects it. Here, the output control module 211b searches and compares the drug data (code) or diagnostic code stored in the database 220 that matches the drug data (code) included in the received prescription and/or the diagnostic code indicating the diagnosis name. Print the result. Therefore, the error correction module 211a checks whether or not there is an error through the search result of the output control module 211b and corrects the error.

Here, the prescription may include a diagnosis name (diagnosis code) and drug data including drugs, identification information (patient or agent identification) of the user terminal 300, and personal information.

Step S222 is a step of encrypting the patient's personal information confirmed through the prescription corrected in the cloud management terminal 210 and generating a decryption key capable of canceling the encryption. The encryption module 211e encrypts the personal information of the patient stored in the prescription or the database 220, and generates a decryption key that can decrypt it. Here, since the patient's personal information is encrypted every time a prescription is issued, a new decryption key is also generated.

Step S223 is a step of generating the drug code 600 in the cloud management terminal 210. Here, the electronic prescription generation module 211c generates the drug data, identification information, decryption key and issue information as QR codes as different QR codes or generates the drug code 600 as one QR code, and in step S222 Link encrypted personal information.

Alternatively, the drug code 600 may further include a one-time authentication key generated by the authentication key generation module 211f. Here, the one-time authentication key may be transmitted to the user terminal 300 together with the drug code 600 or separately transmitted to the user terminal 300 through the unmanned terminal 130.

In addition, the electronic prescription generating module 211c transmits the drug code 600 to the registered user terminal 300 after establishing linkage between the drug code 600 and personal information as described above.

Step S224 is a step of determining whether the cloud management terminal 210 requests personal information from the pharmacy terminal 410. Here, the pharmacy terminal 410 may request personal information from the cloud management terminal 210 through issuance information included in the drug code 600 recognized by the reader terminal 420.

In step S225, when the request for personal information is received in step S224, the cloud management terminal 210 transmits the encrypted personal information linked to the issued information of the drug code 600.

Here, the issued information includes an issue number and/or an available period for identifying the associated personal information. Therefore, the output control module 211b does not transmit the personal information when the personal information is not matched with the publication information received together with the request for personal information, the publication information registered in the database 220, and the usage setting period, and the pharmacy terminal 410 ), send an error message.

S226 is a step of recording and storing whether personal information is transmitted or an error message is transmitted.

Step S227 is a step of determining whether a one-time authentication key is received.

S228 is a step of searching for the user terminal 300 and prescription information associated with the corresponding one-time authentication key when a one-time authentication key is received, and confirming whether a previous issuance or not. Here, when the one-time authentication key is received from the pharmacy terminal 410, the output control module 211b checks the information of the user terminal 300 to which the corresponding one-time authentication key is issued. Then, the output control module 211b retransmits the medicine code 600 by searching for electronic prescription information set in association with the disposable authentication key.

Alternatively, the output control module 211b may transmit the drug code 600 and personal information linked to the disposable authentication key to the pharmacy terminal 410.

Retransmission of the drug code 600 to the user terminal 300 and whether or not to transmit the drug code 600 and personal information of the pharmacy terminal 410 may be selectively performed. For example, it may be set to transmit both personal information and drug code 600 to the pharmacy terminal 410 through a user's verification process through a call with a counselor or through ARS according to a rule set in the cloud management terminal 210 .

Alternatively, as described above, it is possible to retransmit the drug code 600 to the user terminal 300 and proceed to the process after step S223.

The S300 terminal is a step of transmitting the one-time authentication key and/or the drug code 600 to the pharmacy terminal 410 in communication with the reader terminal 420 from the user terminal 300. Here, the reader terminal 420 may correspond to a device that detects a QR code as a POS scanner.

This step S300 will be described with reference to FIG. 11.

11 is a flow chart showing step S300.

Referring to FIG. 11, step S300 includes steps S310 of receiving and storing a one-time authentication key, step S320 of receiving an encryption key and drug code 600, and step S330 of determining whether or not the drug code 600 has an error. Wow, when an error of the drug code 600 occurs, step S340 of outputting a one-time authentication key, step S350 of deleting the one-time authentication key after outputting the one-time authentication key, and output if the drug code 600 is normal It includes step S360.

Step S310 is a step of receiving a one-time authentication key from the unmanned terminal 130 or the cloud management terminal 210. For example, after a user requests for issuance of a prescription through the unmanned terminal 130, the user terminal 300 is connected to the NFC recording device belonging to the unmanned terminal communication unit 132 according to the guide output on the unmanned terminal display 133. Tag on. Therefore, the unmanned terminal 130 transmits the one-time authentication key received from the cloud management terminal 210 to the user terminal 300 through the NFC recording device.

Therefore, the user terminal control unit 310 stores this in the one-time authentication key storage module 312. At this time, the one-time authentication key may include at least one of identification information of the user (patient or agent information) and issue information (issue number and period of use, prescription information).

Here, the unmanned terminal 130 can be replaced with the treatment terminal 110, and the one-time authentication key may also be directly received from the cloud management terminal 210, and in the above description, the one-time authentication key is used when a prescription is issued It has been described as being generated and received, but is not limited thereto.

For example, the user terminal 300 is selected by the user every time a treatment is received by the treatment terminal 110 and/or the unmanned terminal 130 as the patient's initial treatment reception or additional registration is possible afterwards. Therefore, the one-time authentication key may be generated every time a treatment is received and transmitted from the unmanned terminal 130 and the treatment terminal 110 and/or the cloud management terminal 210 to the user terminal 300.

In addition, the cloud management terminal 210 generates and transmits a one-time authentication key linked to the patient's personal information at the request of the unmanned terminal 130 and/or the institution server 120 every time a user's treatment is received, and the user The terminal 300 receives and stores through the treatment terminal 110 and/or the unmanned terminal 130.

Step S320 is a step of receiving the drug code 600 from the cloud management terminal 210 in the user terminal 300. Here, the drug code 600 is issued information including drug data, a decryption key capable of releasing the encrypted personal information, identification information identifying a patient or agent, and the issuance number and usage period of the drug code 600 At least one or more of them are included.

Step S330 is a step of determining whether the drug code 600 has an error. For example, a user visits a nearby pharmacy and selects and outputs the drug code 600 on the display 330 of his user terminal. At this time, as the drug code 600 is received through external network communication between the cloud management terminal 210 and the user terminal 300, the received drug code 600 may be damaged due to a communication error or other cause.

Accordingly, the user terminal controller 310 may determine whether an error has occurred by checking whether the drug code 600 is damaged.

Step S340 is a step of outputting a one-time authentication key to the user terminal display 330 when an error occurs in the drug code 600 in the user terminal control unit 310. Here, it is preferable that the one-time authentication key is provided as a QR code. That is, the drug code receiving module 311 checks whether the drug code 600 is damaged, and then, when an output command of the drug code 600 is input, sends a one-time authentication key to the user terminal display 330 with a guide message. Automatically print.

Step S350 is a step of deleting the one-time authentication key in the user terminal control unit 310. Here, the one-time authentication key storage module 312 may delete a response from the cloud management terminal 210 after the output of the one-time authentication key is received.

For example, the one-time authentication key is output to the pharmacy terminal 410 through the reader terminal 420, and the pharmacy terminal 410 transmits the one-time authentication key to the cloud management terminal 210, and the associated drug code ( 600) may be requested to be retransmitted to the user terminal 300, or the drug code 600 and personal information may be requested directly to the pharmacy terminal 410.

Therefore, when the information request or retransmission is requested through the one-time authentication key, the cloud management terminal 210 drives the output control module 211b to transfer the one-time authentication key to the user terminal 300 set in connection with the one-time authentication key. Respond to reception.

Therefore, the one-time authentication key storage module 312 of the user terminal 300 deletes the one-time authentication key, and then receives and stores the newly generated one-time authentication key upon receiving a medical treatment or requesting issuance of a prescription.

Alternatively, the one-time authentication key storage module may perform short-range wireless communication (for example, any one of Bluetooth, RF, WiFi, infrared communication, and NFC) with the set time after output, whether the use period has elapsed, or with the reader terminal 420. It is also possible to be automatically deleted through.

Step S360 is a step of outputting the drug code 600 to the user terminal display 330 if an error does not occur in step S330. Here, the drug code receiving module 311 outputs the stored drug code 600 when a selection command is input through the user terminal display 330.

Step S400, referring to FIG. 9, step S410 of receiving the drug code 600 of the user terminal 300 from the reader terminal 420 of the pharmacy member 400, and personal information according to the drug code 600 And a step S420 of requesting and step S430 of outputting an electronic prescription.

Step S410 is a step of receiving the drug code 600 output from the user terminal 300 from the reader terminal 420 of the pharmacy member 400. Here, the reader terminal 420 is preferably a POS terminal capable of recognizing a QR code. That is, the present invention can be installed at low cost by using an inexpensive POS terminal instead of an expensive kiosk installed in a conventional pharmacy.

Step S420 is a step of checking the drug code 600 received from the user terminal 300 in the pharmacy member 400 and requesting personal information of the patient set in connection therewith. The pharmacy terminal 410 checks the validity of the drug code 600 through the issued information and identification information included in the drug code 600, and requests the patient's personal information from the cloud management terminal 210.

In step S430, the pharmacy member 400 checks the personal information received from the cloud management terminal 210 and combines the drug data included in the drug code 600 to generate an electronic prescription. Here, the pharmacy terminal 410 releases the encrypted personal information as the decryption key included in the drug code 600 and completes the electronic prescription. Such an electronic prescription is output to the dispensing terminal 430 to prepare medicines according to the prescription.

Here, the present invention collects the inventory status of each pharmacy in the cloud management terminal 210 and provides pharmacy information that can be manufactured for each prescription, and by adding or subtracting the drugs used for dispensing from the drug inventory status of the pharmacy terminal 410 It may further include a step S440 of automatically ordering exhausted medicines by updating the inventory status in real time.

Of these, step S230 will be described with reference to FIG. 12 and step S440.

12 is a flow chart showing step S230.

Referring to FIG. 12, the cloud management terminal 210 includes steps S231 of collecting inventory status information from pharmacy terminals 410, step S232 of searching and storing pharmacies that can be dispensed for each prescription, and It includes a step S233 of transmitting the pharmacy information to the unmanned terminal 130 and the treatment terminal 110 and/or the user terminal 300.

Step S231 is a step in which the cloud management terminal 210 receives inventory status information from the pharmacy terminal 410 in real time or by event and stores it in the pharmacy DB of the database 220. Here, the event corresponds to the exhaustion and order information of a specific drug previously held by the pharmacy.

Here, the cloud management terminal 210 updates the inventory status information of the corresponding pharmacy through the completion of warehousing of the drug after an event occurs in a specific pharmacy, and updates the dispensable pharmacy information generated and transmitted in steps S232 and S233. can do.

Step S232 is a step of generating pharmacy information that can be dispensed for each prescription by using the prescription information converted to big data in the cloud management terminal 210. Here, the cloud management terminal 210 compares inventory status information of each pharmacy with big data of prescriptions to generate pharmacy information that can be dispensed for each prescription.

Step S233 is a step of transmitting pharmacy information that can be dispensed for each prescription from the cloud management terminal 210 to the treatment terminal 110, the unmanned terminal 130, the institution server 120, and/or the user terminal 300. The dispensable pharmacy information may be transmitted for each set period, or may be transmitted whenever a prescription is requested.

13 is a flowchart illustrating step S440.

Referring to FIG. 13, the step S440 includes steps S441 of generating and updating inventory status information in the pharmacy terminal 410, step S442 of transmitting the inventory status information to the cloud management terminal 210, and S443 of determining whether or not to order. It includes a step, step S445 of transmitting the order form to the supplier terminal 500, and step S446 of adding information about the medicine received.

In step S441, the pharmacy terminal 410 generates inventory status information including the type and quantity of drugs in stock, and updates the inventory status information by checking the type and quantity of drugs used by the dispensing terminal 430.

Step S442 is a step in which the pharmacy terminal 410 transmits inventory status information to the cloud management terminal 210 in real time and/or event occurrence information including whether or not a specific medicine is exhausted or stocked. Here, when the inventory quantity of a specific drug corresponds to a set condition, the pharmacy terminal 410 generates event information including a shortage of the quantity of the drug and whether or not the specific drug is in stock.

In addition, the pharmacy terminal 410 updates the change in the inventory quantity of medicines in real time, and transmits inventory status information to the cloud management terminal 210 in a set period and/or in real time. In this case, the inventory status information may include event information or may be transmitted separately.

In step S443, the pharmacy terminal 410 determines whether or not a drug with insufficient inventory quantity is generated.

Step S444 is a step in which the pharmacy terminal 410 automatically generates an order for insufficient medicine and transmits it to the set supplier terminal 500. Here, the order form may be automatically generated with medicines that are insufficient in stock and a previously set quantity.

Step S445 is a step of registering whether new drugs or drugs with insufficient inventory quantities are stocked and the quantity. The pharmacy terminal 410 stores the type and quantity of medicines ordered in the supplier terminal 500, and stores them. Such wearing information is included in the inventory status information through step S441.

According to the present invention, as described above, drug data and personal information are separated by two channels and transmitted to a user and a pharmacy, and the leakage of personal information can be prevented as the personal information is encrypted. In particular, the present invention can provide the drug code 600 as a QR code, thereby implementing an electronic prescription delivery system as an inexpensive POS terminal rather than an expensive kiosk.

That is, according to the present invention, delivery of an electronic prescription can be implemented at a lower cost compared to the prior art, and a useful effect of improving patient convenience and preventing the leakage of personal information can be obtained.

The embodiments of the present invention described above are merely exemplary, and those of ordinary skill in the art to which the present invention belongs will appreciate that various modifications and other equivalent embodiments are possible.

Therefore, it will be appreciated that the present invention is not limited to the form mentioned in the detailed description above. Therefore, the true technical protection scope of the present invention should be determined by the technical spirit of the appended claims. In addition, the present invention is to be understood as including the spirit of the present invention as defined by the appended claims and all modifications, equivalents and substitutes within the scope thereof.

100: medical institution member 110: treatment terminal
120: institution server 130: unmanned terminal
131: unmanned terminal control unit 131a: reception module
131b: pharmacy search module 131c: storage module
131d: geographic information module 131e: prescription application module
131f: information registration module 132: unmanned terminal communication unit
133: unmanned terminal display 200: no cloud
210: cloud management terminal 211: management terminal control unit
211a: error correction module 211b: output control module
211c: electronic prescription generation module 211d: code division module
211e: encryption module 211f: authentication key generation module
212: management terminal communication unit 213: management terminal display
220: database 221: medical institution DB
222: pharmacy DB 223: prescription DB
300: user terminal 400: absence of a pharmacy
410: pharmacy terminal 411: pharmacy terminal control unit
411a: reading information receiving module 411b: information requesting module
411c: electronic prescription output module 411d: inventory management module
411e: order form generation module 412: pharmacy terminal communication unit
413: pharmacy terminal display 414: inventory DB
420: reader terminal 430: dispensing terminal
500: supplier terminal 600, 610, 621, 622: drug code
a, b, c, d: connection point

Claims (7)

A pharmacy member 400 installed in a pharmacy for dispensing drugs according to a prescription issued from the medical institution member 100;
When a request for issuing a prescription is received from a plurality of medical institution members 100 through an external network, a cloud management terminal 210 that generates an electronic prescription divided into a drug code 600 including drug data and the patient's personal information is provided. Cloud member 200 provided; And
Including; a user terminal 300 for receiving and storing the drug code 600 from the cloud management terminal 210 through an external network,
The pharmacy member 400
A reader terminal 420 for receiving the medicine code 600 received from the user terminal 300; And
Including; a pharmacy terminal 410 that requests personal information matching the drug code 600 received from the reader terminal 420 to the cloud member 200 to complete an electronic prescription containing the drug data and the patient's personal information. and,
Medical institution member 100
An unmanned terminal 130 for requesting at least one of the registration of the user terminal 300 capable of receiving the drug code 600 by linking with each other for treatment reception, payment of medical treatment, prescription request, and prescription to the cloud management terminal 210; Including,
The unmanned terminal 130
When registering the user terminal 300, an electronic prescription for the patient can be issued in case of a failure to receive the drug code 600 due to an error of the user terminal 300 or an external network environment, damage to the drug code, or in an emergency situation. Unmanned terminal control unit 131 for requesting and receiving a one-time authentication key; And
NFC recording device for recording a one-time authentication key in the user terminal 300 under the control of the unmanned terminal control unit 131; Including,
The user terminal 300
Whenever a prescription is issued, a one-time authentication key that can replace the drug code 600 is received and stored from the medical institution member 100 when the drug code 600 is not received, the drug code is damaged, or in an emergency. Automatically deletes according to a response or set condition according to whether the cloud management terminal 210 is received,
The pharmacy terminal 410
A two-channel prescription delivery system of a cloud computing environment, characterized in that; sending a one-time authentication key to the cloud management terminal 210 to request a drug code 600 and personal information.
The method of claim 1, wherein the cloud management terminal 210
Divide the drug code 600 consisting of a QR code including at least one of drug data including the type and quantity of drugs, identification information identifying whether a patient or agent, and publication information including an issue number and period of use To transmit one of them to the user terminal 300,
In the dividing line of the divided QR codes (621, 622), the connection point (a, b, c, d) information corresponding to the coordinate information is generated, stored, and transmitted to the user terminal 300, and received from the pharmacy member 400 Generates a drug code 600 by searching the divided QR code matched with the connected point information,
Reader terminal 420 is a two-channel prescription delivery system of a cloud computing environment, characterized in that the POS terminal for detecting a QR code.
The method of claim 1, wherein the cloud management terminal 210
A two-channel prescription delivery system of a cloud computing environment, characterized in that the error is corrected by comparing the prescription information converted into big data with the drug data for each diagnosis included in the prescription received from the medical institution member 100.
The method of claim 1, wherein the personal information is encrypted,
The drug code 600 is a two-channel prescription delivery system of a cloud computing environment, characterized in that it includes a decryption key for decrypting the encrypted personal information.
The method of claim 1, wherein the unmanned terminal 130
A two-channel prescription delivery system in a cloud computing environment, characterized in that when the user terminal 300 requests registration, the identification information including whether the patient himself/herself or an agent is generated and transmitted to the cloud management terminal 210.
delete The method of claim 1, wherein the pharmacy terminal 410
Generates the inventory status information of the drug in possession and transmits it to the cloud management terminal 210,
The cloud management terminal 210
Two-channel prescription in a cloud computing environment, characterized in that the information on the inventory status received by each pharmacy terminal 410 and the prescription information converted into big data are combined to generate pharmacy information that can be dispensed for each prescription and provide it to the user terminal 300 Delivery system.

Images