A cloud-based electronic prescription transmission method comprising the steps of: requesting (S101) an electronic prescription from a hospital server, when a cloud server receives a request for the electronic prescription from a user terminal, by the cloud server; extracting (S103) patient information and prescription information stored in an EMR DB, by the hospital server; converting (S105) the prescription information according to a unique API, by an API builder unit which is included in the hospital server; authenticating (S107) the converted prescription information through an electronic signature of the clinic, encrypting (S109) the converted prescription information, and transmitting (S111) the electronic prescription to the cloud server, by the hospital server, creating (S113) a QR code, and temporarily storing the electronic prescription when a drugstore is selected by the user terminal, by the cloud server; transmitting (S119) at least one among the QR code, the electronic prescription, and drugstore information on the selected drugstore to a drugstore server, by the cloud server, confirming (S121) the electronic prescription, by the drugstore server, and storing (S141) the electronic prescription by the drugstore server, deleting (S143) the temporarily stored electronic prescription from the cloud server when reception of medicine is informed from the user terminal, wherein at the step of converting (S105) the prescription information by the API builder unit, the API builder unit converts the prescription information by creating a data source, conveniently creating an SQL query through an SQL query creation guide, converting the data source into a standard data through an API builder, and repeatedly verifying the data. requesting (S101) an electronic prescription from a hospital server, when a cloud server receives a request for the electronic prescription from a user terminal, by the cloud server; extracting (S103) patient information and prescription information stored in an EMR DB, by the hospital server; converting (S105) the prescription information according to a unique API, by an API builder unit which is included in the hospital server; authenticating (S107) the converted prescription information through an electronic signature of the clinic, encrypting (S109) the converted prescription information, and transmitting (S111) the electronic prescription to the cloud server, by the hospital server, creating (S113) a QR code, and temporarily storing the electronic prescription when a drugstore is selected by the user terminal, by the cloud server; transmitting (S119) at least one among the QR code, the electronic prescription, and drugstore information on the selected drugstore to a drugstore server, by the cloud server, confirming (S121) the electronic prescription, by the drugstore server, and storing (S141) the electronic prescription by the drugstore server, deleting (S143) the temporarily stored electronic prescription from the cloud server when reception of medicine is informed from the user terminal, wherein at the step of converting (S105) the prescription information by the API builder unit, the API builder unit converts the prescription information by creating a data source, conveniently creating an SQL query through an SQL query creation guide, converting the data source into a standard data through an API builder, and repeatedly verifying the data. <EOS>