Electronic Prescription Workflow for Remote Pharmacy Compounding
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing electronic prescription services require patients to physically visit a pharmacy for medicine compounding, which is inconvenient and limited by factors such as the state of the patient terminal and payment type, and existing technologies do not effectively address non-face-to-face prescription needs.
Innovation Solution
A system and method for providing a non-face-to-face electronic prescription service that includes a hospital server providing a prior agreement for a non-face-to-face electronic prescription service to a user terminal, allowing automatic storage and processing of payment and prescription information through a cloud server, generating prescriptions, and enabling remote medicine compounding through a pharmacy server, with real-time updates and QR code authentication.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If a patient visits a pharmacy in person to show the user terminal or use a QR code for medicine compounding, then the medicine can be compounded, but the patient has to physically move and spend time traveling to the pharmacy
Solution Approach 1:
The patent introduces a pharmacy daemon program as an intermediary that runs locally at the pharmacy and communicates with the hospital server and user terminal. This daemon enables automatic prescription transmission and QR code generation without requiring the patient to physically visit the pharmacy, thus resolving the contradiction between ease of operation and time loss
Solution Approach 2:
The patent replaces the mechanical system of physical patient movement and manual prescription presentation with an electronic communication system. The user terminal automatically transmits prescription data through the cloud server to the pharmacy server, and the pharmacy daemon program handles the compounding process electronically, eliminating the need for patient travel
2Device complexity
If the hospital server directly transmits prescription information to the pharmacy server, then the process is simple, but the system lacks flexibility for different payment types and terminal states
Solution Approach 1:
The patent introduces a cloud server as an intermediary between the hospital server and pharmacy server. This cloud server acts as a flexible mediator that can adapt to different payment types and terminal states, processing prescriptions through various pathways depending on the specific conditions, thus resolving the contradiction between simplicity and adaptability
Solution Approach 2:
The patent implements a dynamic prescription transmission system where the transmission path and processing method can change based on terminal state and payment type. The system dynamically selects between direct transmission and cloud-mediated transmission, and between different compounding modes (prior compounding, real-time compounding), achieving both simplicity and versatility
3Reliability
If the system requires prior agreement confirmation from the patient, then security and consent are ensured, but the service setup process becomes more complex
Solution Approach 1:
The patent implements prior agreement confirmation as a preliminary action that is performed once during service setup. The patient's consent is obtained and stored in advance, allowing subsequent prescription transmissions to proceed automatically without repeated confirmations, thus resolving the contradiction between reliability and complexity
Data Source
AI summary
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.


