A method of providing a non-face-to-face electronic prescription service, the method comprising:
- a step in which a hospital server provides, over a wireless network via a graphical user interface (GUI), a prior agreement for a non-face-to-face electronic prescription service to a wireless user terminal, and the wireless user terminal applies, via a GUI, 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 automatically store whether a remote patient has applied for the non-face-to-face electronic prescription service in a storage unit by storing the agreement confirmed matters on the basis of a user ID;
- a step in which when the wireless user terminal requests payment to the cloud server by executing a payment service, the cloud server automatically requests payment to the hospital server by executing a payment API;
- a step in which the hospital server automatically stores details of payment, extracts prescription information from an EMR, and automatically transmits the prescription information to the cloud server;
- a step in which the cloud server automatically generates a prescription for the remote 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 automatically generated prescription for the remote patient to the wireless user terminal, the wireless user terminal, via a GUI, checks the prescription for the remote patient and requests compounding of a medicine to the cloud server;
- a step in which the cloud server automatically executes a prescription API and automatically requests compounding of a medicine to a pharmacy server when receiving the request for compound of a medicine from the wireless user terminal;
- a step in which the pharmacy server automatically requests prescription information from the cloud server by automatically 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 automatically informs the wireless user terminal whether prior compounding is possible, and when the wireless user terminal requests, via a GUI, the prior compounding to the pharmacy server, the pharmacy server automatically transmits whether the prior compounding has been permitted to the wireless user terminal;
- a step in which the pharmacy server automatically requests and receives certificate information of a hospital issuing the electronic prescription from the hospital server, and automatically instructs a pharmacy to perform a medicine compounding service;
- and
- a step in which the wireless user terminal automatically displays, via a GUI, a QR code, the pharmacy server automatically recognizes the QR code and automatically stores an electronic signature of the pharmacy and the electronic prescription,
- wherein the pharmacy server automatically transmits and stores an electronic prescription including the electronic signature of the pharmacy to a certified e-document authority server,
- wherein a pharmacy daemon program is automatically operated with a pharmacy manager program, when a medicine starts to be compounded at the pharmacy, the original of the electronic prescription is controlled to prevent other pharmacies from compounding the medicine based on the electronic prescription, automatically inform the remote patient, in real time, of the states of receipt request, receipt confirmation, compounding completion, and reception completion through a GUI of the wireless user terminal using the pharmacy manager program, a pharmacy desk PC automatically transmits prescription data to the pharmacy manager program, automatically performs encoding/decoding with an external interface, and automatically transmits QR code data using a virtual serial port,
- wherein the prescription information is automatically converted into standardized prescription information by an API builder, regardless of a heterogeneous database management system (DBMS) of the hospital server, so that the hospital server is permitted to store the prescription information in a non-standardized format dependent on a hardware and a software platform used by the hospital server.