Renewed Health Pharmacy

The demo models common digital pharmacy workflows: finding products, distinguishing prescription-only items, selecting a branch, submitting a prescription for pharmacist review, following an order, and coordinating inventory and point-of-sale operations. The project does not claim measured customer demand or a specific buyer's operational results.

• Present a searchable pharmacy catalogue with synthetic demo products and branch context.
• Separate over-the-counter browsing from prescription-only medicine workflows.
• Demonstrate prescription submission and pharmacist review before dispensing prescription-only items.
• Represent stock by branch and track batches through receiving, FEFO allocation, quarantine, and inter-branch transfer workflows.
• Demonstrate customer order follow-up and staff fulfilment paths.
• Provide role-separated pharmacist, cashier, inventory, fulfilment, and owner workflows.
• Show a browser-based Tele-Pharmacist video consultation workflow that requires camera and microphone access.
• Keep demo data synthetic and defer buyer-specific managed database and service-provider choices until buyer requirements are known.

• The seeded catalogue, inventory, branch, patient, prescription, and staff records are synthetic demonstration data; they are not a live pharmacy feed.
• The repository documents a local disk-backed SQLite server. Durable database behavior for the Vercel-hosted demo has not been verified, and no buyer-selected managed database is connected.
• The WebRTC consultation path includes browser video and WebSocket signalling code, but an external TURN relay is not configured and an end-to-end remote call has not been validated.
• No load, latency, availability, or production-scale benchmark evidence is recorded.
• A live clinical service would require buyer-specific licensed staffing, clinical governance, privacy, regulatory, support, and operational configuration.
• No buyer-specific identity, payments, or external pharmacy-system integration is configured in the demo.

The code separates the customer storefront from role-protected operational workspaces. The storefront supports catalogue search, category and OTC/POM filters, branch selection, prescription submission, and order follow-up. The server code supplies Express API routes and WebSocket events for application workflows. SQLite is used by the documented local demo server; a PostgreSQL/Supabase schema file is present as a migration option, not as a connected buyer database. The Tele-Pharmacist path uses browser WebRTC media with WebSocket signalling and now requires camera and microphone access rather than falling back to audio-only. Demo limitations are documented instead of being presented as production integrations.

• Responsive customer storefront with a seeded synthetic medicine catalogue.
• Product search by brand, generic name, or therapeutic class.
• Category, over-the-counter (OTC), and prescription-only medicine (POM) filters.
• Branch selection for Airport Residential and Osu Oxford Street sample branches.
• Branch-specific sample stock visibility.
• Product details with strength or pack selection where available.
• Prescription submission flow with pharmacist review, approval, rejection, and revised-quotation paths.
• Customer order tracking and delivery or collection workflow fields.
• Pharmacist workspace for prescription and Tele-Pharmacist request handling.
• FEFO batch allocation using expiry dates, with stock receiving, quarantine, and inter-branch transfer workflows.
• Cashier point-of-sale workflow with cash tender/change calculation, shift records, and printable thermal receipts.
• Role-separated staff operations for pharmacist, cashier, inventory, fulfilment, and owner/admin roles.
• WebSocket signalling and real-time client update code in the server repository.
• Browser video consultation UI with local and remote video elements, camera/microphone controls, and a pharmacist request queue; camera and microphone are required.
• Synthetic pharmacist and patient profiles with emergency-care disclaimers.

• Source code uses server-side staff-session checks and role-restricted route middleware; this case study is not an independent security audit.
• The documented staff roles separate pharmacist, cashier, inventory, fulfilment, and owner/admin actions.
• The README documents branch isolation, session expiry, rate limiting, and audit logging for staff workflows.
• Prescription-only workflow requires pharmacist review; the demo does not use AI to diagnose, prescribe, or approve medicines.
• The repository documents formula-injection-safe CSV exports and audit records for operational actions.
• Seeded identities and operational records are synthetic demo data; no real patient dataset is claimed.
• Video consultation requires camera and microphone access; the interface includes an emergency-care disclaimer.

No load, latency, uptime, or scalability measurements are recorded, so no performance or production-capacity claims are made. The documented disk-backed SQLite setup is the local single-server demo model. The public Vercel demo's durable backend persistence has not been verified; final database, hosting, and scale design should follow the buyer's requirements.

The customer path places medicine search, branch selection, prescription submission, order tracking, and the video-consultation request near the storefront. Staff workflows are separated by role and accessed through a hidden keyboard-revealed gate with server-side authorization. GHS currency, Accra branches, and synthetic Ghana-localized demo records are represented. The interface identifies demo profiles and includes emergency notices.

Development

The codebase models a broad pharmacy workflow—from customer catalogue and prescription review through inventory and point of sale—while keeping the portfolio environment synthetic. The local SQLite runtime and included PostgreSQL schema are implementation options in the repository, not evidence of a buyer's production database connection. Tele-Pharmacist is a video workflow in the source, but external TURN setup and end-to-end remote call testing remain prerequisites before presenting it as a live service.