阅读说明：本技术 基于云技术的电子处方传送系统及方法 (Electronic prescription delivery system and method based on cloud technology ) 是由 洪秉鎭 徐京熙 于 2019-05-17 设计创作，主要内容包括：本发明提供一种基于云技术的电子处方传送系统及方法。包括如下步骤：在云服务器由用户终端设备接收请求电子处方的情况下,向医院服务器请求电子处方；所述医院服务器提取存储至EMRDB部的患者信息及处方信息,在API生成器中根据固有的API而变换所述处方信息；在所述医院服务器变换的处方信息中通过医院电子签名而进行认证,并对所述变换的处方信息进行加密而将电子处方发送至所述云服务器。(The invention provides an electronic prescription delivery system and method based on a cloud technology. The method comprises the following steps: requesting an electronic prescription from a hospital server in the case where the cloud server receives a request electronic prescription from the user terminal device; the hospital server extracts the patient information and prescription information stored in the EMRDB unit, and converts the prescription information in an API generator according to a specific API; the hospital server authenticates through a hospital electronic signature among the prescription information converted, and encrypts the converted prescription information to transmit an electronic prescription to the cloud server.)

1. An electronic prescription transmitting method based on cloud technology is characterized in that,

the method comprises the following steps:

requesting an electronic prescription from a hospital server in the case where the cloud server receives a request electronic prescription from the user terminal device;

the hospital server extracts the patient information and prescription information stored in the EMR DB unit, and converts the prescription information in an API generator according to a specific API;

the hospital server authenticates through a hospital electronic signature among the prescription information converted, and encrypts the converted prescription information to transmit an electronic prescription to the cloud server.

2. The cloud-technology-based electronic prescription delivery method of claim 1,

also comprises the following steps:

the cloud server generates a QR code, and temporarily stores the electronic prescription under the condition that a pharmacy is selected by user terminal equipment; and

and the cloud server transmits at least one of the QR code, the electronic prescription and pharmacy information corresponding to the selected pharmacy to a pharmacy server.

3. The cloud-technology-based electronic prescription delivery method of claim 2,

also comprises the following steps:

settling the medicine fee when the pharmacy server confirms the electronic prescription, judges whether to dispense the medicine and executes the dispensing; and

the pharmacy server requests the cloud server for settlement, and when the cloud server completes settlement through the user terminal device, the settlement is sent to the pharmacy server.

4. The cloud-technology-based electronic prescription delivery method of claim 3,

also comprises the following steps:

the pharmacy server dispenses the medicines, and under the condition that the medicines are dispensed, the cloud server is informed of the completion of the medicines dispensing, and the cloud server is informed of the completion of the medicine taking; and

the pharmacy server stores the electronic prescription, and the cloud server deletes the electronic prescription.

5. The cloud-technology-based electronic prescription delivery method of claim 1,

in the step of the API generator converting the prescription information, a data source is generated, and after a simple production of a production guide is queried through SQ L and conversion into standard data produced through the API generator, repeated verification is performed.

6. An electronic prescription delivery system based on cloud technology is characterized in that,

the method comprises the following steps:

a cloud server requesting an electronic prescription from a hospital server when the requested electronic prescription is received by the user terminal device, transmitting at least one of the generated QR code, information of the pharmacy selected by the user terminal device, and the electronic prescription to a pharmacy server when the electronic prescription is received by the hospital server, and deleting the electronic prescription when the user terminal device takes the medicine;

a hospital server that extracts patient information and prescription information from the EMR DB unit when the requested electronic prescription is received by the cloud server, converts the prescription information using an inherent API in the API generator, authenticates an electronic hospital signature in the converted prescription information, encrypts the prescription information, and transmits the electronic prescription to the cloud server;

and a pharmacy server which confirms the electronic prescription and determines whether or not to dispense the medicine when the cloud server receives at least one of the QR code, the electronic prescription, and the pharmacy information, requests settlement from the cloud server after settlement of the medicine fee, and stores the electronic prescription when receiving a notification of completion of medicine taking.

7. The electronic prescription delivery system of claim 6,

the API generator includes:

a generation module for receiving patient information and prescription information from the EMR DB unit and generating a data source;

SQ L creates a module, creates a SQ L query and transmits the query to a test module.

8. The electronic prescription delivery system of claim 6,

the cloud server includes: an electronic prescription storage part for storing the electronic prescription,

when the electronic prescription storage unit receives an electronic prescription from a hospital server, the electronic prescription is temporarily stored, and when a user terminal device takes a medicine, the stored electronic prescription is deleted.

9. The electronic prescription delivery system of claim 6,

the pharmacy server includes:

a medicine settlement unit for settling the medicine fee based on the prescription information; and

an electronic prescription confirming section for confirming the received electronic prescription and judging whether to dispense the medicine.

10. The electronic prescription delivery system of claim 9,

further comprising:

and a medicine electronic signature unit for storing the electronic pharmacy signature for the electronic prescription for pharmacy storage in the electronic prescription storage unit when the medicine taking completion notification is received.

Technical Field

The present invention relates to an electronic prescription delivery system and method based on cloud technology, and more particularly, to an electronic prescription delivery system and method based on cloud technology, which provides an electronic prescription to a user in a cloud computing environment, and the user directly selects a pharmacy on an application, thereby enabling delivery of a prescription to the pharmacy.

Background

When a prescription is directly delivered to a pharmacy with a paper prescription, the responsibility for the problem of identifying the prescription and the problem caused by the wrong prescription or dispensation recorded by a doctor is not transparent, and it is inconvenient and cumbersome from the standpoint of the patient, and therefore, an electronic prescription service has recently been proposed.

In addition, in the conventional electronic prescription service, when the electronic prescription for patient storage is transferred from a hospital to a user terminal device, the user goes to a pharmacy directly and displays the user terminal device or dispenses the electronic prescription using a QR code, which is still inconvenient. Moreover, cloud technology is required due to the closed systems of hospitals and poor information security solutions, but applicable cases are still lacking.

As a conventional patent, there is a registered patent No. 10-1329003 (a method for transferring an electronic prescription for a patient, a method for transferring a medical shop, a patient client for executing the method, and a relay device), but only a technique of generating unique information and transferring the electronic prescription to a mobile phone terminal device of the patient is disclosed.

Disclosure of Invention

Technical problem to be solved by the invention

The technical problem to be solved by the present invention is to provide an electronic prescription delivery system and method based on cloud technology, which can generate an electronic prescription through a standardized API (application programming interface) regardless of the DBMS of a hospital server and the type of a development language, and can provide the electronic prescription in a cloud computing environment.

Means for solving the problems

The electronic prescription transmitting method based on the cloud technology comprises the following steps: requesting an electronic prescription from a hospital server in the case where the cloud server receives a request electronic prescription from the user terminal device; the hospital server extracts the patient information and prescription information stored in the EMR DB unit, and converts the prescription information in an API generator according to a specific API; the hospital server authenticates through a hospital electronic signature in the converted prescription information, and encrypts the converted prescription information to transmit an electronic prescription to the cloud server.

The cloud technology-based electronic prescription delivery system of the embodiment of the present invention includes: a cloud server requesting an electronic prescription from a hospital server when the requested electronic prescription is received by a user terminal device, transmitting at least one of the generated QR code, information of a pharmacy selected by the user terminal device, and the electronic prescription to a pharmacy server when the electronic prescription is received by the hospital server, and deleting the electronic prescription when the user terminal device receives a medicine; a hospital server that extracts patient information and prescription information from the EMR DB unit when the requested electronic prescription is received by the cloud server, converts the prescription information using an inherent API in the API generator, authenticates an electronic hospital signature in the converted prescription information, encrypts the prescription information, and transmits the electronic prescription to the cloud server; and a pharmacy server which confirms the electronic prescription and determines whether or not to dispense the medicine when the cloud server receives at least one of the QR code, the electronic prescription, and the pharmacy information, and stores the electronic prescription when the cloud server requests settlement after settling the medicine fee and receives a notification of completion of the medicine dispensing.

ADVANTAGEOUS EFFECTS OF INVENTION

According to the present invention, an electronic prescription is generated by standardizing an API regardless of the kind of development language with a dual DBMS of a hospital server.

Further, according to the present invention, since the prescription is received by the user terminal device and transferred to the pharmacy, the waiting time for receiving the prescription, the dispensing time, and the medicine taking waiting time are shortened, thereby improving the user convenience. Further, the user can inquire about the settlement of the prescription and the fee through the mobile terminal device.

Drawings

Fig. 1 is a sequence diagram illustrating a cloud technology-based electronic prescription transfer method of an embodiment of the present invention;

FIG. 2 is a configuration diagram of an electronic prescription delivery system of an embodiment of the present invention;

FIGS. 3 and 4 are sequence diagrams illustrating a method of operation of an API generator in accordance with an embodiment of the present invention;

fig. 5 is a configuration diagram of an API generator according to an embodiment of the present invention.

Detailed Description

The specific configurations and functional explanations of the embodiments of the concept of the present invention disclosed in the present specification are merely examples for the purpose of illustrating the embodiments of the concept of the present invention, and the embodiments of the concept of the present invention are implemented in various forms and are not limited to the embodiments described in the present specification.

Since the conceptual embodiments of the present invention have various modifications and forms, the embodiments are illustrated in the drawings and will be described in detail in this specification. It is not intended to limit the embodiments of the inventive concept to the particular forms disclosed, and all changes, equivalents, and substitutions included in the spirit and technical scope of the invention are included.

The terminology used in the description is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. Expressions in the singular are not explicitly defined differently in the article, and include expressions in the plural. In the present specification, the terms "comprises" or "comprising" or the like specify the presence of stated features, integers, steps, operations, components, parts, or groups of features, integers, steps, operations, components, parts, and/or groups, and should be interpreted as excluding one or more other features, integers, steps, operations, components, parts, or groups of one or more other features, integers, steps, operations, components, or groups of features, integers, steps, operations.

Hereinafter, embodiments of the present invention will be specifically described with reference to the drawings in the present specification.

Fig. 1 is a sequence diagram illustrating an electronic prescription transfer method based on cloud technology according to an embodiment of the present invention.

Referring to fig. 1, the electronic prescription delivery method based on the cloud technology requests an electronic prescription to a hospital server 200 in a case where a cloud server 100 receives a request electronic prescription by a user terminal device 400 (S101).

The hospital server 200 extracts the patient information and the prescription information stored in the EMR DB unit 210 (S103), and the API generator 220 converts the prescription information according to an API (application Programming interface) (S103). in this case, the API generator 220 generates, manages, and tests an api.api generator 220 for standardizing Database information in the hospital server such as the prescription information, and operates by installing the api.api generator 220 in the hospital server, regardless of the types of the different-type DBMS (Database Management System) and the development language, but is not limited thereto, and the API generator 220 extracts the prescription information from the EMR DB unit to generate a data source, completes the SQ L query, and repeatedly performs the test to convert the prescription information.

The hospital server 200 authenticates the converted prescription information by the hospital electronic signature (S107), and encrypts the converted prescription information (S109). The hospital server 200 transmits the electronic prescription to the cloud server 100 (S111). The electronic prescription includes the transformed prescription information and patient information.

The cloud server 100 generates a QR code (S113), and temporarily stores the electronic prescription (S117) when a pharmacy is selected by the user terminal device 400 (S115). At this time, the QR code is replaced with a hash code providing location information of prescription information. The cloud server 100 transmits at least one of the QR code, the electronic prescription, and pharmacy information corresponding to the selected pharmacy to the pharmacy server 300 (S119).

The pharmacy server 300 confirms the electronic prescription (S121), determines whether or not to dispense the medicine (S123), and settles the fee for the medicine when dispensing is performed (S125).

The pharmacy server 300 requests the cloud server 100 to settle the account (S127), and when the cloud server 100 completes the account, the user terminal device 400 transmits the settlement completion to the pharmacy server 300 (S131).

The pharmacy server 300 dispenses the medicine (S133), and when the medicine dispensing is completed, notifies the cloud server 100 of the completion of the medicine dispensing (S135), the cloud server 100 notifies the pharmacy server 300 of the completion of the medicine taking (S139), the pharmacy server 300 stores the electronic prescription, and the cloud server 100 deletes the electronic prescription (S143).

Namely, the invention transmits prescription information through the cloud server, can be used whenever and wherever on the network, and deletes the electronic prescription to improve the security when the dispensing is finished on the cloud server. In addition, the system can shorten the time for receiving the prescription in the hospital, dispensing in the pharmacy, and waiting time for taking the prescription, and even settle the charge of the prescription, thereby improving the convenience of the user.

Fig. 2 is a configuration diagram of an electronic prescription delivery system according to an embodiment of the present invention.

Referring to fig. 2, the electronic prescription delivery system 10 is composed of a cloud server 100, a hospital server 200, a pharmacy server 300, and a user terminal device 400. In the case where the user terminal device 400 requests an electronic prescription, the cloud server 100 requests the electronic prescription to the hospital server 200, and the hospital server 200 transforms and encrypts prescription information using a standardized API to provide the electronic prescription to the cloud server 100. The cloud server 100 performs a dispensing/settlement function by transmitting the electronic prescription to the pharmacy server 300.

The cloud server 100 includes: an electronic prescription transmitting/receiving unit 110, a settlement unit 120, an authentication unit 130, an electronic prescription storage unit 140, a QR code generation unit 150, a communication unit 160, and a control unit 170.

In the case where the electronic prescription transmitting/receiving section 110 requests an electronic prescription from the user terminal device 400, the electronic prescription is requested from the hospital server 200. And, in case of receiving the electronic prescription by the hospital server 200, transmits to the pharmacy server 300. When the settlement unit 120 receives the request for settlement of the fee from the pharmacy server 300, the settlement service is provided to the user terminal device. In the case of completing the settlement, the completed settlement is transmitted to the drugstore server 300. The authentication unit 130 performs authentication by comparing the personal information received by the user terminal device 400 with the patient information received by the hospital server. When the electronic prescription storage unit 140 receives the electronic prescription from the hospital server 200, the electronic prescription is temporarily stored, and the user terminal device deletes the stored electronic prescription when receiving the medicine, thereby improving security. The QR code generation unit 150 generates a QR code corresponding to the received electronic prescription and transmits the QR code to the pharmacy server 300. At this time, the QR code generating unit 150 generates and provides a hash code providing the position information of the prescription information. The communication unit 160 communicates with the hospital server 200, the pharmacy server 300, and the user terminal device 400 using a wired wireless network. The control unit 170 controls each configuration of the cloud server.

The hospital server 200 includes: EMR DB unit 210, API generator 220, hospital electronic signature unit 230, encryption unit 240, communication unit 250, and control unit 260.

The EMR DB unit 210 stores patient information, medical information, prescription information, hospital information, and history information. The type of information stored in the EMB DB unit 210 is not limited.

The API generator 220 extracts patient information and prescription information from the EMR DB unit 210 and converts the prescription information and patient information using the API, that is, after generating a data source in the API generator, simply creating and converting the data into standard data generated by the API generator by querying a creation guide with SQ L, the data is repeatedly verified.

The hospital electronic signature unit 230 performs authentication by the hospital electronic signature on the converted prescription information. The encryption unit 240 encrypts the converted prescription information to improve security, the communication unit 250 transmits and receives data to and from the cloud server 100, and the control unit 260 controls each configuration of the hospital server.

The drugstore server 300 includes: a medicine settlement unit 310, an electronic prescription confirmation unit 320, a medicine electronic signature unit 330, an electronic prescription storage unit 340, a communication unit 350, and a control unit 360.

The medicine settlement unit 310 settles the medicine fee based on the prescription information and requests the cloud server 100. The electronic prescription confirming unit 320 confirms the received electronic prescription and determines whether to dispense the medicine. The electronic medicine signature unit 330 stores the electronic prescription for pharmacy in the electronic prescription storage unit 340 by performing electronic pharmacy signature. The communication unit 350 transmits and receives data to and from the cloud server 100, and the control unit controls each configuration of the pharmacy server.

Fig. 3 and 4 are sequence diagrams illustrating an operation method of the API generator according to the embodiment of the present invention.

Referring to fig. 3 and 4, the API generator constructs an application server (S301). The API is developed (S303), requesting analysis of HTTP (S305). In this case, the application server is constructed by IIS, Tomcat Tuxedo, Entra, and the like, but is not limited thereto. The API is REST API and is realized by Net ASP, Java and C languages.

Thereafter, the EMR DB receives the information to generate a data source (S307), and develops the service logic (S309), then calls SQ L, collects the query result, and creates an HTTP response (S313).

In other embodiments, the API generator sets the API tool (S401), generates the data source (S403), creates a SQ L query (S405), and performs a repeat test (S407).

Fig. 5 is a configuration diagram of an API generator according to an embodiment of the present invention.

Referring to fig. 5, the API generator 220 includes a generation module 221, a SQ L creation module 222, a test module 223, an analysis module 224, a collection module 225, and a control module 226, the generation module 221 receives patient information and prescription information among patient information, medical information, prescription information, hospital information, and history information stored in the EMR DB unit 210 to generate a data source, the SQ L creation module 222 creates a SQ L query and transmits the query to the test module 223 to execute a test, the analysis module 224 analyzes an HTTP request, the collection module 225 collects the query result and creates an HTTP response, the control module 226 controls the respective modules of the API generator 220, receives data transmitted from the EMR DB unit 210 and converts the data in an output format standardized by the API generator 220.

While the present invention has been described with reference to the embodiments shown in the drawings, which are for illustrative purposes only, it is to be understood that various modifications and other equivalent embodiments can be made by one skilled in the art. Therefore, the true technical scope of the present invention should be defined by the technical idea of the claims.