RxRelay

Already shipped as ScriptTrack: sent to the chemist, accepted, ready, collected. This was not built, because it already exists under another name. Everything RxRelay describes — a prescription sent to the chemist the patient chose, the chemist accepting it, a substitution the prescriber has to decide before anything is handed over, and the dispense recorded back — is ScriptTrack, live in the product. Building it again would have meant a second prescribing surface, which is the one thing a prescriber–pharmacist app must never become. Reading it closely to be sure of that found two ids the tracking row took on trust, and those are fixed: the chemist a prescription is sent to must be in this practice’s own directory and the dispense linked back must be this practice’s own, both re-read against your own tables rather than accepted because the id existed somewhere.

RxRelay reads prescriptions, your pharmacy directory, the dispensing counter and writes nothing of its own — the ladder is ScriptTrack’s. Its data class is Full PHI. Every app works on the same patient record — nothing is copied into a silo.

It is not a separate app and adds no second place to prescribe from. It has no threaded messaging of its own: what exists is the substitution request, which is the only prescriber–pharmacist exchange in this product that changes what a patient takes, and it is decided by a clinician who is not the person who asked. A chemist outside your own directory, or a dispense belonging to another practice, is refused rather than linked.

Every record stays; only the workflow leaves.

RxRelay is in design: the surface exists and the platform underneath is ready. Join the waitlist and it moves up the build order.