What is SwiftyRx ================= Overview -------- SwiftyRx is a SaaS solution to manage the intake and frontend processing of prescriptions at high volumes (think tens of thousands of prescriptions per day) with a high degree of accuracy and quality. It is built using modern software architectures, and brings NLP and LLM technologies to the prescription processing world. SwiftyRx is designed to be used by pharmacy hubs and virtual pharmacy operations that are responsible for receiving, pre-processing, and assessing prescriptions for correctness, benefits, formularies and other program specific items before transferring a prescription to a fulfillment pharmacy for dispensing. SwiftyRx is flexible by design to support various business models. It is an API first based solution with a UI that can be deployed as a Web Application, Windows Desktop Application, Mac Desktop Application, iOS Tablet App, or Android Tablet App, depending on the target customer's needs and preferences. It has a flexible workflow engine with prebuilt tasks that can be extended via simple Python based scripting. Prescription Processing Flow ---------------------------- The following diagram shows the high level, happy path flow that a prescription goes through in SwiftyRx, and where interaction with the frontend portal, prescriber EMR and dispensing pharmacy Pharmacy Management System occur. .. figure:: _static/images/high_level_prescription_processing_flow_2.png Note that while this diagram primarily shows the states and flows for SwiftyRx, it also depicts the points at which communications occur with external systems such as the prescriber's EMR, the front end portal, and the dispensing pharmacy's Pharmacy Management System. Prescription States And Sub-states ---------------------------------- Within a given prescription state, there can be multiple sub-states that further clarify where it is in the overall flow within SwiftyRx. The following diagram shows these sub-states for each of the main states. .. figure:: _static/images/prescription_states_and_transitions.png Note that we use the term PV0™ here, which is not a standard pharmacist verification term like PV1 or PV2, but is related. We created the term PV0™ to indicate that an initial prescription review has been performed (instructions, days supply, quantity at a minimum, with potential additional checks for DUR, benefits and alternate therapies). However, **PV0™ is not considered to be a legal replacement for PV1**, but it is intended to move most of this costly checking further upstream before it gets to the final dispensing pharmacy. The dispensing pharmacy is still legally required to perform a PV1. Our goal is to send highly accurate and properly clarified prescriptions to the dispensing pharmacy so that PV1 for them is much simpler and should require few to no additional clarifications or fixes to the prescription. System Interaction Diagram -------------------------- SwiftyRx is meant to interact with other systems in the prescription pharmacy ecosystem. Most notably, a frontend patient prescription portal that is responsible for patient registration and the commerce functions of prescription procurement, and backend pharmacies that will do dispensing. SwiftyRx integrates with `Surescripts `_ for electronic prescription communications and fax services like `Faxage `_ for fax based communications. .. figure:: _static/images/high_level_system_interaction.png