ScriptQ

📋 Patient Intake Forms — ScriptQ makes it easy to add a patient, capture their details, and record the request in a structured way so the right information is attached to the right job from the start. That reduces confusion and keeps the queue useful as volume rises.

• Capture patient details and dispensing context in one place
• Keep intake consistent across staff and public submissions
• Move from patient request to operational progress without losing detail

🔄 Live Queue Tracking — Every prescription moves through a defined workflow, with statuses such as Future, Queued, In progress, Ready, Collected, and Cancelled. The dashboard updates automatically so staff can see the current operational picture without rechecking manual lists.

• See all active work in one live queue
• Recognise delays before they become visible to customers
• Keep the team aligned on what's happening now

⏱️ Wait Time Estimation — The queue uses a dispensary pipeline capacity model rather than guessing from queue length alone: approximately three minutes for work in progress and four minutes for each queued prescription, compared with active expected-back times. Overdue work adds a buffer, later-today returns join the estimate within 60 minutes, and an idle queue shows no current wait.

• Estimate completion windows in real time
• Track how far each job is from expected completion
• Help OTC and dispensary teams communicate more clearly

📱 QR Code Check-in — Patients can submit a request through a pharmacy-specific QR code or public link, which makes the first intake step easy and friction-free. There is no customer app to install, but the work still lands in the same operational queue as a staff-created request.

• Customers scan once and submit a request
• Work enters the same queue as in-store requests
• Pharmacy can respond without extra admin overhead

🖥️ Patient Kiosk — A shared counter tablet can run a touch-friendly ScriptQ kiosk for walk-in intake. It uses the same queue and wait estimate as public check-in, then shows a neutral confirmation and resets automatically without exposing a patient status link or retaining the previous request in the browser.

• Designed for a shared pharmacy counter screen
• Neutral confirmation protects the next patient's privacy
• Automatic reset after submission

🔍 Search & Task Views — Staff can search active and archived work and switch between All, Queued, Future, Awaiting Stock, Recently Changed, and Archive. This keeps the interface practical when volume rises without splitting OTC and dispensary work into separate dashboards.

• Find the right patient without scanning the whole queue
• Focus on current work, future returns, stock delays, recent changes, or history
• Support better daily service during busy periods

📊 7-Day Analytics Dashboard — ScriptQ is not only operational but also informative. The analytics layer summarises processed prescriptions, patient additions, and seven-day trends so the pharmacy can review real patterns instead of relying on memory alone.

• Track activity across the last seven days
• Spot peaks, quiet periods, and service trends
• Support smarter staffing and pharmacy decisions

👨‍⚕️ Pharmacist Requests — Pharmacist requests use a separate action and remain visible until resolved, without automatically reordering prescription work. This gives the team a clear signal while leaving prioritisation to pharmacy staff.

• Unresolved requests stay visible in operational views
• Pharmacy staff retain control of prioritisation
• Staff can act without losing the request context

📦 Stock, Storage & Collection Tracking — ScriptQ keeps stock work separate from the main prescription status. Staff can record Not checked, In stock, Awaiting stock, or Partially available, along with an expected arrival date, supplier order status, patient contact status, shelf location, and final collection or cancellation.

• Update stock quickly without changing patient or return-time details
• Track expected stock arrival, supplier ordering, and patient contact
• Close the loop cleanly when a patient collects or cancels

🔐 Data Retention Policies — Live queue details and sent-message history are normally deleted 30 days after their scheduled expiry, collection, or cancellation point. Pharmacies approve this hosted retention during onboarding and remain responsible for exports and other copies they create.

• Normal 30-day cleanup for live patient queue details
• Managed backup expiry is handled under the hosted service terms
• Pharmacies remain responsible for printouts, downloads, and exports they retain

🌙 Hosted service continuity — The hosted service uses managed database backups and documented recovery procedures. Health and readiness endpoints support service checks, but the current single-host, Single-AZ deployment is not highly available.

• Separate health checks for application and database readiness
• Managed encrypted database backups and documented recovery procedures
• No high-availability or zero-downtime claim

📡 Privacy-safe service monitoring — Owner monitoring reports application resource use, latency, errors, and database-pool health. It does not retain patient names, contact details, prescription information, notes, or status tokens.

🛡️ Privacy controls — Public requests are protected with CSRF validation, IP and phone rate limits, honeypot detection, sanitised input, no-cache responses for dynamic patient data, random status tokens, and idempotent retries that help prevent duplicate queue entries.

• Public check-in and private status routes remain separate from staff operations
• Kiosk submissions use neutral confirmation rather than exposing a status link
• Each pharmacy remains responsible for access controls, retention, backups, privacy notices, and regulatory obligations