METHOD AND SYSTEM FOR PROVIDING NON-FACE-TO-FACE ELECTRONIC PRESCRIPTION SERVICE

Abstract

Proposed is a method and system for providing a non-face-to-face electronic prescription service, where a hospital server provides a prior agreement for a non-face-to-face electronic prescription service to a user terminal, and the user terminal applies for the prescription service based on the agreement and transmits the confirmed matters to the hospital server and a cloud server; the hospital server and the cloud server store whether a patient has applied for the prescription service by storing the confirmed matters based on a user ID; when the user requests payment to the cloud server, the cloud server requests payment to the hospital by executing a payment API; the hospital server stores details of payment, extracts prescription information from an EMR, and transmits the prescription information to the cloud server; and the cloud server creates prescriptions for patient and a pharmacy when the prescription information is received from the hospital.

Description

CROSS REFERENCE TO RELATED APPLICATION

The present application is a PCT national stage of PCT/KR2021/007757 filed Jun. 21, 2021, which claims priority to Korean Patent Application No. 10-2020-0076394, filed Jun. 23, 2020, the entire contents of which are incorporated herein for all purposes by this reference.

BACKGROUND

Field

The present disclosure relates to a method and system for providing a non-face-to-face electronic prescription service, particularly, a method and system for providing a non-face-to-face electronic prescription service, the method and system transmitting an electronic prescription through a mobile to minimize contact between unrelated people until compounding after medical examination and treatment by changing a prescription issuance procedure into a non-face-to-face type.

Related Art

Demands for a non-face-to-face medical service are increasing with the prevalence of new types of contagious diseases. Recently, due to COVID-19, the Korean government has given temporal permission for patients to transmit a prescription, which is issued after medical examination and treatment, to pharmacies in the whole country through a mobile application without an additional procedure. Considering the tendency of the contagious disease, this measure is not expected to end as a temporal measure and the need for a non-face-to-face electronic prescription service will further increase.

Meanwhile, an existing electronic prescription service has many inconveniences because when a hospital transmits an electronic prescription for patient to a user terminal, the user has to go to a pharmacy in person and show the user terminal or uses a QR code for compounding of a medicine, and has a problem in that the service is limited, depending on the state of a patient terminal, the payment type for medical expenses, whether an electronic prescription issuance has been agreed upon, etc.

As a prior patent, there is Korean Patent No. 10-1989474 (System and method for transmitting electronic prescription based on cloud computing), but this discloses only a technology about an standardized API for creating electronic prescription regardless of the DBMS of hospital servers and the kinds of developing languages.

SUMMARY

An objective of the present disclosure is to provide a method and system for providing a non-face-to-face electronic prescription service, the method and system being able to issue an electronic prescription through a mobile to minimize contact between unrelated people till reception of a medicine after medical examination and treatment of a patient who confirmed a prior consent.

A method of providing a non-face-to-face electronic prescription service according to an embodiment of the present disclosure includes: a step in which a hospital server provides a prior agreement for a non-face-to-face electronic prescription service to a user terminal, and the user terminal applies for a non-face-to-face electronic prescription service on the basis of the received prior agreement and transmits the confirmed matters in the agreement to the hospital server and a cloud server; a step in which the hospital server and the cloud server store whether a patient has applied for the non-face-to-face electronic prescription service in the storage unit by storing the agreement confirmed matters on the basis of a user ID; a step in which when the user terminal requests payment to the cloud server by executing a payment service, the cloud server requests payment to the hospital server by executing a payment API; a step in which the hospital server stores details of payment, extracts prescription information from an EMR, and transmits the prescription information to the cloud server; and a step in which the cloud server creates a prescription for patient and a prescription for a pharmacy when the cloud server receives the prescription information from the hospital server.

A system for providing a non-face-to-face electronic prescription service of the present disclosure includes: a hospital server providing a prior agreement for a non-face-to-face electronic prescription service to a user terminal, storing confirmed matters in the prior agreement on the basis of a user ID when receiving the confirmed matters in the prior agreement from the user terminal, and extracting prescription information from an EMR and transmitting the prescription information to a cloud server when the user terminal requests payment; the user terminal agreeing with the prior agreement for an electronic prescription, and receiving a prescription for patient from the cloud server and requesting compounding of a medicine when requesting payment; and the cloud server creating a prescription for patient and a prescription for a pharmacy by receiving the prescription information from the hospital server, and transmitting the prescription for patient to the user terminal and transmitting the prescription for a pharmacy to the pharmacy server when there are requests from the user terminal and the pharmacy server.

According to the present disclosure, it is possible to minimize movement of a patient in a hospital and reduce the time for compounding a medicine at a pharmacy by requesting prior compounding of a medicine by transmitting an electronic prescription in a non-face-to-face type.

Further, when a medicine starts to be compounded at a pharmacy, the original version of the electronic prescription is controlled, so other pharmacies are set not to compound a medicine, so it is possible to prevent repetitive compounding at other pharmacies.

Further, the electronic prescription that is provided to a pharmacy is the same in form as existing paper prescriptions, so there is no difficulty in coping with the electronic prescription and work efficiency can be increased at the pharmacy.

BRIEF DESCRIPTION OF THE DRAWINGS

FIGS. 1 and 2 are flowcharts illustrating a method and system for providing a non-face-to-face electronic prescription service according to an embodiment of the present disclosure.

FIG. 3 is a configuration diagram of a system for providing a non-face-to-face electronic prescription service according to an embodiment of the present disclosure.

FIG. 4 is a diagram showing a prior agreement for a non-face-to-face electronic prescription service according to an embodiment of the present disclosure.

FIG. 5 is a configuration diagram of a pharmacy daemon program according to an embodiment of the present disclosure.

FIG. 6 is a use state diagram of a non-face-to-face electronic prescription service according to an embodiment of the present disclosure.

DESCRIPTION OF EXEMPLARY EMBODIMENTS

Specific structural and functional description about embodiments according to the concept of the present disclosure disclosed herein is exemplified only to describe the embodiments according to the concept of the present disclosure and the embodiments according to the concept of the present disclosure may be implemented in various ways and are not limited to the embodiments described herein.

Embodiments described herein may be changed in various ways and various shapes, so specific embodiments are shown in the drawings and will be described in detail in this specification. However, it should be understood that the exemplary embodiments according to the concept of the present disclosure are not limited to the specific examples, but all of modifications, equivalents, and substitutions are included in the scope and spirit of the present disclosure.

Terms used in the present invention are used only in order to describe specific exemplary embodiments rather than limit the present invention. Singular forms are intended to include plural forms unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” or “have” used in this specification, specify the presence of stated features, numbers, steps, operations, components, parts, or a combination thereof, but do not preclude the presence or addition of one or more other features, numerals, steps, operations, components, parts, or a combination thereof.

The non-face-to-face type stated in the present disclosure means all types of medical examination and treatment without meeting a doctor in person such as telemedicine, video medicine, and telephone medicine.

Hereafter, various embodiments of the present disclosure are described in detail with reference to the accompanying drawings.

FIGS. 1 and 2 are flowcharts illustrating a method and system for providing a non-face-to-face electronic prescription service according to an embodiment of the present disclosure.

Referring to FIGS. 1 and 2, according to a method of providing a non-face-to-face electronic prescription service of the present disclosure, first, a hospital server 200 provides a prior agreement for a non-face-to-face electronic prescription service to a user terminal 300 (S100). The user terminal 300 can apply for a non-face-to-face electronic prescription service by selecting agreement in the received prior agreements. The user terminal 300 transmits the confirmed matters in the agreement to the hospital server 200 (S 103). Further, the user terminal 300 transmits the confirmed matters in the agreement to a cloud server (S104).

The hospital server 200 stores whether a patient has applied for the non-face-to-face electronic prescription service by storing the confirmed matters in the agreement on the basis of a user ID (S105). Further, the cloud server 100 stores whether the patient has applied for the non-face-to-face electronic prescription service by storing the confirmed matters in the agreement on the basis of a user ID (S106).

When the user terminal 300 executes a payment service and requests payment to the cloud server 100, the cloud server 100 requests payment to the hospital server by executing a payment API.

The hospital server 200 stores the details of the payment (S115), extracts prescription information based on the user ID from an EMR of the hospital server and transmits the prescription information to the cloud server 100 (S119).

When the cloud server 100 receives the prescription information from the hospital server 200, the cloud server 100 creates a prescription for patient and a prescription for a pharmacy on the basis of the prescription information (S121). The cloud 100 transmits the prescription for patient to the user terminal 300 (S123). The user terminal 300 checks the received prescription for patient and requests compounding of a medicine to the cloud server (S 127). When receiving the request for compounding of a medicine from the user terminal 300, the cloud server 100 executes a prescription API (S129) and requests compounding of a medicine to a pharmacy server 400 (S131).

When the pharmacy server 400 receives the request for compounding of a medicine from the cloud server 100 (S131), the pharmacy server 400 requests prescription information from the cloud server by executing a pharmacy daemon program. The pharmacy daemon program can perform at least one function of client registration, receipt request, receipt cancelation, compounding completion, in-compounding, reception completion. The pharmacy daemon program is operated with a pharmacy manager program. When a medicine starts to be compounded at a pharmacy, the original of the electronic prescription is controlled, so other pharmacies can be set not to compound a medicine. It is possible to inform the patient of the states of receipt request, receipt confirmation, compounding completion, and reception completion through the user terminal using the pharmacy manager program. A pharmacy desk PC can transmit prescription data to the pharmacy manager program, perform encoding/decoding with an external interface, and transmit QR code data using a virtual serial port.

The cloud server 100 informs the user terminal whether prior compounding is possible, and when the user terminal requests prior compounding to the pharmacy server, the pharmacy server transmits whether prior compounding has been permitted to the user terminal.

The pharmacy server requests certificate information of the hospital issuing the electronic prescription from the hospital server (S415), and when the hospital server 200 transmits the certificate information of the hospital issuing the electronic prescription to the pharmacy server 400, the pharmacy server 400 receives the certificate information and performs a medicine compounding service. In this case, the electronic prescription that is provided to the pharmacy includes an image of an existing paper prescription and an electronic signature and is the same in form as the paper prescription, so there is no difficulty in coping with the electronic prescription and work efficiency can be increased at the pharmacy. In this case, when the QR in the prescription transmitted to the pharmacy server is clicked, a compounding program is opened and it is possible to immediately input prescription data. The pharmacy server includes a function of converting and transmitting a QR code, and when medicine information is clicked, the site that provides the medicine is connected, so it is possible to check the medicine information.

When a medicine finishes being compounded and the user terminal 300 displays the QR code and is brought into contact with a pharmacy reader prepared at the pharmacy, the pharmacy server 400 performs authentication by recognizing the QR code. When authentication is finished, the compounded medicine can be handed over to the patient. The pharmacy server stores an electronic signature of the pharmacy and the electronic prescription for a pharmacy (S157). In this case, the pharmacy server 400 can transmit and store an electronic prescription including the electronic signature of the pharmacy to a certified e-document authority server 500.

In the present disclosure, electronic prescriptions are encoded and transmitted in all procedures, can be opened only through the hospital server and the pharmacy server, and are automatically deleted after the available periods, so they are highly secure. Depending on embodiments, a service for applying an actual medical expense insurance for the pharmacy cost may also be operated.

FIG. 3 is a configuration diagram of a system for providing a non-face-to-face electronic prescription service according to an embodiment of the present disclosure.

Referring to FIG. 3, a system 10 for providing a non-face-to-face electronic prescription service is composed of a cloud server 100, a hospital server 200, a user terminal 300, a pharmacy server 400, and a certified e-document authority server 500.

The cloud server 100 is composed of a prescription creator 110, a user authenticator 120, an API unit 130, a communication unit 140, a storage unit 150, and a controller 160.

When the prescription creator 110 receives prescription information from the hospital server 200, the cloud server 100 creates a prescription for patient and a prescription for a pharmacy on the basis of the prescription information (S121). The created prescription for patient and prescription for a pharmacy are temporarily stored in the storage unit, and are deleted when prescription is finished.

The user authenticator 120 stores whether a patient has applied for the non-face-to-face electronic prescription service in the storage unit by storing confirmed matters in an agreement on the basis of a user ID. When the user terminal requests payment, the user authenticator 120 performs authentication on the basis of the user ID.

The API unit 130 includes a payment API and a prescription API. The API unit includes several API modules such as a push API, an actual medical expense API, and a mobile API, but they are not described in detail herein. When the user terminal calls out a payment service or a prescription service, the API unit can perform the called service by loading an API matched to the called service.

The communication unit 140 can transmit and receive data to and from the hospital server 200, the user terminal 300, and the pharmacy server 400 through a wired/wireless communication module. The storage unit 150 receives the confirmed matters in the agreement and stores whether a patient has applied for the electronic prescription service. The storage unit 150 temporarily stores the prescription for patient and the prescription for a pharmacy created by the prescription creator and deletes the prescriptions when prescription is finished. The controller 160 controls the components of the cloud server.

The hospital server 200 is composed of a storage unit 210, an extractor 220, an EMR 230, and a communication unit 240. The storage unit 210 stores whether agreement has been made on the basis of a user ID when receiving confirmed matters in a prior agreement for an electronic prescription from the user terminal 300. The storage unit 210 stores details of payment. When the hospital server 200 transmits hospital certificate information to the pharmacy server 400, the hospital server 200 does not issue a corresponding electronic prescription in cooperation with an electronic prescription original control a pharmacopoeia program when another pharmacy requests electronic prescription information. Accordingly, the hospital server 200 can prevent repeated issuance of an electronic prescription.

The extractor 220 extracts the prescription information from the EMR on the basis of the user ID. Patient information, examination and treatment information, prescription information, hospital administration information, and history information may be stored in the EMR 230. The kind of the information that is stored in the EMR 230 is not limited. The communication unit 100 can transmit and receive data to and from the cloud server 100, the user terminal 300, and the pharmacy server 400 through a wired/wireless communication module.

The pharmacy server 400 is composed of a daemon program unit 410, a QR recognition unit 420, and a storage unit 43. The demon program unit 410 performs a server demon function and can perform a medicine compounding service in cooperation with a pharmacy manager program. When the QR in the prescription transmitted to the pharmacy server is clicked, a compounding program is opened and it is possible to immediately input prescription data through the daemon program unit 410. The pharmacy server includes a function of converting and transmitting a QR code, and when medicine information is clicked, the site that provides the medicine is connected, so it is possible to check the medicine information.

The demon program unit 410 can process data using at least one of a method of applying class search for a normal prescription and an electronic prescription to a prescription class, a method of applying an item for checking where the initial reception has come from, a method of searching for a prescription reception period, a method of enabling a function of checking the current state of a prescription, a method of applying a function of checking a receipt state, a method of applying color correction in a system program in accordance with a classification state, and a method of transmitting a prescription message to a patient by applying a function of adding boilerplates. The demon program unit 410 can inform a user terminal that compounding of a medicine is started and finished. The QR recognition unit 420 can recognize a QR displayed on the user terminal through a QR reader. The storage unit 430 can store an electronic signature of the pharmacy and the electronic prescription for a pharmacy.

The certified e-document authority server 500 can receive and store the electronic prescription including the electronic signature of the pharmacy from the pharmacy server.

FIG. 4 is a diagram showing a prior agreement for a non-face-to-face electronic prescription service according to an embodiment of the present disclosure.

Referring to FIG. 4, it is an exemplary image of a prior agreement for a non-face-to-face electronic prescription service that is provided by an exclusive application. It is possible to fill out the prior agreement by inputting a patient name, a patient number, a phone number, whether to agree, an applicant signature. FIG. 4 shows an example, and a prior agreement may be prepared in offline and a patient can fill out the prior agreement.

FIG. 5 is a configuration diagram of a pharmacy demon program according to an embodiment of the present disclosure.

Referring to FIG. 5, a pharmacy demon program performs a server demon function and the server demon function can perform at least one function of client registration, receipt request, receipt cancelation, compounding completion, in-compounding, reception completion. Further, the pharmacy demon program can be operated in cooperation with a pharmacy manager program. The pharmacy demon program can perform at least one function of client registration, receipt request, receipt cancelation, compounding completion, in-compounding, reception completion. The sever demon function and the manager program can transmit and receive data to and from each other.

When a medicine starts to be compounded at a pharmacy, the original of the electronic prescription is controlled, so other pharmacies can be set not to compound a medicine. It is possible to inform the patient of the states of receipt request, receipt confirmation, compounding completion, and reception completion through the user terminal using the pharmacy management program. A pharmacy desk PC includes a QR reader, and can transmit prescription data to the pharmacy manager program, perform encoding/decoding with an external interface, and transmit QR code data using a virtual serial port.

FIG. 6 is a use state diagram of a non-face-to-face electronic prescription service according to an embodiment of the present disclosure.

Referring to FIG. 6(a), it is an image showing a QR code that is prepared in a hospital so that patients fill out a prior agreement for an electronic prescription using a user terminal. Not only a QR code, but a URL may be provided to fill out a prior agreement.

Referring to FIG. 6(b), an exclusive application may be provided to subscribe an electronic prescription service. Prior agreement is required to subscribe an electronic prescription service and the image can be changed to a page requesting prior agreement.

Although the present disclosure has been described with reference to the exemplary embodiments illustrated in the drawings, those are only examples and may be changed and modified into other equivalent exemplary embodiments from the present disclosure by those skilled in the art. Therefore, the technical protective range of the present disclosure should be determined by the scope described in claims.

Claims

1-6. (canceled)

7. A method of providing a non-face-to-face electronic prescription service, the method comprising:

a step in which a hospital server provides a prior agreement for a non-face-to-face electronic prescription service to a user terminal, and the user terminal applies for a non-face-to-face electronic prescription service on the basis of the received prior agreement and transmits the confirmed matters in the agreement to the hospital server and a cloud server;

a step in which the hospital server and the cloud server store whether a patient has applied for the non-face-to-face electronic prescription service in the storage unit by storing the agreement confirmed matters on the basis of a user ID;

a step in which when the user terminal requests payment to the cloud server by executing a payment service, the cloud server requests payment to the hospital server by executing a payment API;

a step in which the hospital server stores details of payment, extracts prescription information from an EMR, and transmits the prescription information to the cloud server;

a step in which the cloud server creates a prescription for patient and a prescription for a pharmacy when the cloud server receives the prescription information from the hospital server;

a step in which when the cloud server transmits the created prescription for patient and prescription for a pharmacy to the user terminal, the user terminal checks the prescription for patient and requests compounding of a medicine to the cloud server;

a step in which the cloud server executes a prescription API and requests compounding of a medicine to a pharmacy server when receiving the request for compound of a medicine from the user terminal;

a step in which the pharmacy server requests prescription information from the cloud server by executing a pharmacy demon program when receiving the request for compounding of a medicine from the cloud server;

a step in which the cloud server informs the user terminal whether prior compounding is possible, and when the user terminal requests prior compounding to the pharmacy server, the pharmacy server transmits whether prior compounding has been permitted to the user terminal;

a step in which the pharmacy server requests and receives certificate information of a hospital issuing the electronic prescription from the hospital server, and performs a medicine compounding service; and

a step in which the user terminal displays a QR code and is brought into contact with a pharmacy reader, the pharmacy server recognizes the QR code and stores an electronic signature of a pharmacy and the electronic prescription,

wherein the pharmacy server can transmit and store an electronic prescription including the electronic signature of the pharmacy to a certified e-document authority server,

wherein the pharmacy daemon program is operated with a pharmacy manager program, when a medicine starts to be compounded at a pharmacy, the original of the electronic prescription is controlled, so other pharmacies can be set not to compound a medicine, inform the patient of the states of receipt request, receipt confirmation, compounding completion, and reception completion through the user terminal using the pharmacy manager program, a pharmacy desk PC can transmit prescription data to the pharmacy manager program, perform encoding/decoding with an external interface, and transmit QR code data using a virtual serial port.