Royal Drugs ePrescribe medication order view with line items, quantities, and order status Royal Drugs ePrescribe prescriptions list with search, filters, and per-row status Royal Drugs ePrescribe edit prescription form with medication, dispensing, and limited use coverage criteria
Client Royal Drugs
Sector Pharmaceutical Distribution
Scope Custom .NET Web Application
Case study

A custom ordering platform for a pharmacy distributor

Royal Drugs, formerly MPGL, needed a way for clinics to order medication and supplies online instead of by phone, fax, and paper. We designed and built ePrescribe, a custom .NET web portal that turned a manual process into a self-service system.

The challenge: a manual process under pressure

Clinics ordered from MPGL through a manual process that was slow and easy to get wrong. To stay competitive and meet what customers expected, the business needed a portal clinics could use on their own: quicker to order through, harder to make mistakes in, and better to work with day to day. It also had to be something MPGL's own team could run after launch.

What we built: a role-based ordering portal

We built a custom web application in .NET, structured in clear layers so the interface was decoupled from the business logic and the system could grow later, including toward a mobile app, without a rebuild. The portal was organized around the people who use it: clinic admins, physicians, and pharmacy assistants for day-to-day ordering, and portal and super admins for managing the catalogue, accounts, and permissions. The interface was built mobile-friendly so it worked on the devices clinic staff actually reach for.

The build was handed over as a complete, documented system so the Royal Drugs team could run and extend it in-house. This is the kind of custom platform work our web and platform team takes on for life sciences clients.

Platform Build

  • .NET
  • C#
  • ASP.NET
  • Entity Framework
  • jQuery
  • Bootstrap
  • Layered Architecture
  • Role-Based Access
How it works

From a clinic's order to a pharmacy's fulfillment

Each clinic orders the medication and supplies it needs from the pharmacy it is tied to. A clinic admin builds the prescriptions, a physician signs them, and the clinic orders from its own catalogue of medications and supplies. The pharmacy receives that order and fulfills it. The screens above follow that path: a medication order, the prescriptions behind it, and the detail behind a single prescription.

Capabilities

What the platform does

ePrescribe is more than an order form. It runs the day-to-day work of a pharmacy distributor, with role-based access and a full audit trail, records are hidden rather than deleted, so every action stays traceable.


Catalogue ordering

Clinics order medications and supplies from their own catalogue online, replacing phone, fax, and paper with a self-service cart.

Prescriptions & Limited Use coverage

Clinic admins build prescriptions with medication, dispensing, and Limited Use (LU) coverage criteria; physicians review and sign before anything is ordered.

PDF documents

Orders and prescriptions render to clean, print-ready PDFs for records, sign-off, and fulfillment.

Automated email notifications

A templated email queue, processed by a background service, keeps clinics, physicians, and pharmacies updated as orders move through the workflow.

Reporting & Excel export

Built-in reports and one-click Excel exports give the team the numbers they need without leaving the portal.

Consignment stock tracking

Allocate and count consignment stock so inventory stays accurate across the clinics and pharmacies on the portal.

How we built it

Built to hand over, and to grow

We built the portal in .NET across clear layers, with the presentation layer kept separate from the business logic. That separation keeps sessions on the server and leaves room to add another interface later, such as a mobile app, without reworking the core. The interface is responsive, so it holds up on the devices clinic and pharmacy staff actually reach for.

Delivery ran as eight two-week sprints against the client's own development and staging environments, with a testing pass at the end of each one. At handover we provided a complete, documented system so the Royal Drugs team could install, run, and extend it in-house. Security and privacy shaped the build throughout, from role-scoped access to keeping clinic and pharmacy connections isolated. This is the kind of custom platform work our web and platform team takes on for life sciences clients.

Handover was the start of a long-term partnership. Over the years we have continued extending the system, which has gone through three major updates and several smaller ones, each adding capabilities and keeping the platform current. That continuity is what keeps a custom system valuable and dependable well beyond launch.

0+
Hours (2 devs, 1 designer)
0K
Lines of code (estimate)
0+
Version releases
.NET
C#, ASP.NET, SQL Server
Next Project
Dexcom Deep Dive →