Healthcare
Software engineering for Pharmacy
Software for community and online pharmacies, dispensing, prescription management, EPS integration and stock, built by senior engineers who understand that a labelling error is a clinical event, not a bug ticket.
Why the domain matters
Pharmacy is one of the few software domains where a defect can directly harm a patient. A wrong dose on a label, a controlled drug that is not reconciled, a clinical interaction that is not flagged, or a repeat prescription dispensed against a discontinued item: each of these is a real-world event with a real-world consequence, and each of them is shaped by the software the pharmacy runs. We build for community pharmacies, online and distance-selling pharmacies, and the operations behind them, and we treat that responsibility as the first constraint on the work rather than an afterthought bolted on at the end.
The UK adds a second layer of difficulty on top of the clinical one: the NHS. Most of the value a pharmacy delivers flows through NHS infrastructure: the Electronic Prescription Service, the Spine, GP prescribing systems, and the reimbursement machinery behind them, and that infrastructure is gated, standards-bound and slow to integrate with. It is not a public API you sign up for on a Tuesday. Any credible pharmacy platform has to reconcile modern product expectations (an app for repeat prescriptions, a fast online checkout with a clinical check behind it) with connectivity to systems that were designed for safety and auditability rather than developer convenience.
We are a senior-led consultancy, and we operate what we build. That matters here more than in most sectors: dispensing software runs every hour the pharmacy is open, controlled-drugs records have to be right at close of business, and an outage during a busy afternoon is lost dispensing and frustrated patients. We would rather tell you plainly which parts of a build are hard, which are gated behind NHS assurance, and which are genuinely quick, than sell you a timeline that ignores the parts we do not control.
The challenges in pharmacy
Clinical safety is not a feature. It is the whole system
Dispensing, labelling and clinical checks have to be correct under load, on the worst day, with a tired pharmacist and a queue. The failure modes (wrong drug, wrong dose, missed interaction, missed allergy), are patient-harm events. That changes how you design validation, how you handle edge cases, and what “good enough to ship” means.
EPS and NHS integration is the gated, hard part
Connecting to the Electronic Prescription Service and the Spine is not a weekend integration. It involves NHS assurance, conformance testing, endpoint accreditation, Smartcard or modern authentication, and standards (increasingly FHIR-based) that must be implemented exactly. This is usually the longest pole in any pharmacy build, and it is not something you can rush.
Controlled drugs demand a perfect audit trail
CD stock has to be recorded, reconciled and auditable to the unit, with running balances, witnessed destructions and register entries that stand up to inspection. Software that treats controlled drugs like ordinary stock will fail the pharmacy at exactly the moment scrutiny arrives.
Online pharmacy is a regulated clinical service, not e-commerce
A distance-selling or online pharmacy looks like a shop and is regulated like a healthcare provider. Every order needs an appropriate clinical check, prescriber or pharmacist oversight, and safeguards against inappropriate supply. A generic checkout with no clinical gate is both non-compliant and unsafe.
Stock, expiry and reimbursement all have to reconcile
Pharmacies run on thin margins. Stock has to be accurate against dispensing, expiry has to be managed, wholesaler ordering has to be timely, and what you dispensed has to match what you claim for reimbursement. When these drift apart, the pharmacy loses money quietly and finds out late.
Patient data is special-category and multiply regulated
Prescription and dispensing records are health data (special-category under UK GDPR), and sit under NHS information-governance expectations on top. Access has to be controlled, logged and justified, and data has to be held and shared only where there is a lawful basis. Getting this wrong is both a regulatory and a trust failure.
What we build for pharmacy
The systems this sector most often needs, built by engineers who understand the domain, not just the code.
Online and distance-selling pharmacy platforms
Patient-facing ordering with a real clinical check behind it: questionnaires and triage, prescriber or pharmacist review queues, appropriateness and quantity limits, and safe-supply safeguards, not a checkout that ships medicines on payment alone. Built to sit correctly under GPhC and distance-selling rules.
Dispensing and PMR (patient medication record) systems
The core operational system: prescription capture, dispensing workflow, accurate labelling, interaction and allergy checking, endorsement, and a patient medication record that gives the pharmacist the history they need at the point of dispensing.
EPS and NHS systems integration
Connecting your platform to the Electronic Prescription Service and the Spine (token and message handling, nomination, dispense notifications and claims), implemented against the current standards and taken through the assurance and conformance process rather than faked around.
Controlled-drugs and stock management
CD register and running balances, witnessed actions, expiry and shortage tracking, wholesaler ordering, and reconciliation between what was received, dispensed, destroyed and claimed, designed so an inspection is a non-event.
Patient apps for repeat prescriptions
Apps and portals that let patients request repeats, nominate a pharmacy, track order and dispensing status, and get notified when items are ready, connected to the dispensing system so the status a patient sees is the real one, not a guess.
Pharmacy back-office automation
The unglamorous work that saves real hours: reimbursement reconciliation, endorsement checking, ordering and returns, MDS/compliance-aid preparation support, and reporting, automating the repetitive parts while keeping a human decision where a human decision belongs.
Where we help
Online pharmacy with a clinical gate that actually works
A distance-selling pharmacy where each order flows through triage and a pharmacist or prescriber review before supply, with quantity and frequency limits, interaction checks against the patient record, and a clear audit of who approved what and why, so growth in volume does not quietly erode clinical safety.
EPS-connected dispensing at the counter
A community pharmacy pulling nominated prescriptions from EPS, dispensing against them with clinical checks and accurate labelling, sending dispense notifications and claims back, and keeping the patient medication record current, all through one workflow the team can run at pace.
Controlled-drugs register that survives an inspection
Running CD balances that reconcile to the physical stock, witnessed destructions recorded properly, discrepancies surfaced immediately rather than at year end, and a register a responsible pharmacist and an inspector can both trust.
Repeat-prescription app tied to real dispensing status
A patient requests a repeat, the request routes through the correct GP/EPS path, the dispensing system updates as items are processed, and the patient is notified when their prescription is ready, cutting phone calls and counter queries because the status the patient sees is accurate.
How we build for pharmacy
We start from the clinical and legal failure modes, not the happy path. Before we design a dispensing or online flow, we map what must never happen (wrong drug, wrong dose, missed interaction, inappropriate supply, an unreconciled controlled drug), and we design the system so those outcomes are hard to produce, easy to catch, and always auditable. The pleasant version of the workflow is the easy part; the safety of the unpleasant version is the work.
We are honest about sequencing. On almost every pharmacy build, EPS and NHS integration is the longest pole, because it is gated behind assurance and conformance that we do not control the pace of. We plan around that reality: we build and prove the parts we can move quickly on, we start the NHS-facing work early, and we do not present a timeline that pretends the accreditation steps are instant. If a genuinely useful first version can ship without full EPS connectivity, we will tell you, and we will tell you what it can and cannot do.
We keep a human in the loop where a human belongs. Automation is genuinely useful for reconciliation, ordering, endorsement checking and status updates: the repetitive, high-volume work. It is not a substitute for a pharmacist’s clinical judgement, and we design so the system supports the pharmacist rather than quietly overriding them. Where we use automation or models to assist triage or flagging, we make the reasoning visible and keep the final clinical decision with the professional who is accountable for it.
We operate what we build. Dispensing software is not a project you hand over and forget; it runs every hour the pharmacy is open. We stay close to the running system, we monitor the parts that matter, and we treat an outage during a busy dispensing period as the serious operational event it is, because for the pharmacy, it is.
Regulation and compliance
Pharmacies and their software sit under the General Pharmaceutical Council (GPhC). The GPhC’s standards for registered pharmacies govern how a pharmacy operates, and its guidance on providing pharmacy services at a distance sets specific expectations for online and distance-selling models, including that supply is safe and appropriate, that clinical checks happen, and that certain higher-risk medicines are handled with additional safeguards. Software that supports these services has to make the compliant path the default path, not an optional one a busy team can skip.
On the NHS side, dispensing NHS prescriptions means operating within the NHS pharmacy contractual framework and its requirements, and connecting to NHS systems means passing the relevant assurance and conformance processes rather than simply pointing at an endpoint. This is deliberately gated: it protects patients and the integrity of the prescribing and reimbursement chain, and it is a fixed cost in time on any build that touches EPS or the Spine.
Controlled drugs are governed by the Misuse of Drugs Regulations and associated safe-custody and record-keeping requirements. In practice that means accurate registers, running balances, witnessed destructions, and records that stand up to inspection: obligations the software must enforce and evidence, not merely allow.
Where the work touches medicines supply more broadly, or medical devices, the Medicines and Healthcare products Regulatory Agency (MHRA) is relevant, for example around the classification and advertising of medicines, and around software that meets the definition of a medical device. We are blunt about this boundary: if a feature would make the software a regulated medical device, that is a decision to take deliberately, with the obligations understood, not to stumble into.
Finally, prescription and patient data is special-category personal data under UK GDPR, and pharmacies operate within NHS information-governance expectations on top of the general law. Lawful basis, data minimisation, access control, retention and the ability to evidence all of it are baseline requirements, not enhancements. We treat compliance as something the architecture demonstrates, and we will always tell you where you need your own pharmacist, information-governance or legal sign-off rather than implying our build removes that need.
Integration and interoperability
The Electronic Prescription Service and the NHS Spine are the centre of gravity. EPS integration covers prescription retrieval against a patient’s nomination, dispense and claim notifications, and the message and token handling behind them: implemented against the current NHS standards, which are increasingly FHIR-based, and taken through the assurance and conformance process. This is the part of a pharmacy build that most rewards experience and most punishes optimism: the standards are exact, the testing is real, and there is no shortcut through the accreditation.
GP systems matter because prescriptions originate there, and because the repeat-prescription journey a patient experiences depends on the path between the GP, the NHS infrastructure and the pharmacy working cleanly. We design app and portal flows around how that journey actually behaves (including its delays and its failure cases), rather than around an idealised version of it.
Wholesalers and suppliers are the other integration frontier. Ordering, availability, shortages, returns and pricing all move between the pharmacy and its suppliers, and the quality of those integrations directly affects whether the right stock is on the shelf and whether margins hold. We connect to the ordering and supply systems the pharmacy actually uses.
Stock systems tie it together. Dispensing, controlled-drugs records, expiry, ordering and reimbursement only stay honest if the stock picture is a single reconciled truth rather than several drifting copies. We design so that what was received, dispensed, destroyed and claimed all reconcile against one another, because when they do not, the pharmacy loses money and confidence at the same time.
Security and data protection
Prescription and dispensing records identify a person and describe their health. This is special-category data, and it deserves handling that reflects that. Access is controlled by role and justified by need, sensitive actions are logged, and the log is one you can actually use to answer “who saw this, and why” rather than a box ticked and forgotten. For a pharmacy, the audit trail is not overhead; it is part of being trustworthy.
Authentication and access to NHS-connected functions follow the NHS’s own requirements (Smartcard-based or the modern authentication approaches NHS systems now support), and we implement them properly rather than bolting on a weaker parallel path for convenience. The same discipline applies to controlled-drugs actions, where who did what, and who witnessed it, has to be captured reliably.
We minimise what we hold and how widely it moves. Patient data is shared only where there is a lawful basis and an operational need, encrypted in transit and at rest, and retained against a defined policy rather than accumulating indefinitely. Third parties are brought in only where they earn their place, and where they do, their handling of health data is part of the assessment, not an afterthought.
We are candid about the boundary of our responsibility. Good architecture makes a pharmacy’s security and information-governance obligations easier to meet and easier to evidence, but it does not discharge them: the pharmacy remains the data controller, and some sign-off is yours to give. We would rather name that clearly than let a well-built system create a false sense that compliance is entirely handled in code.
What changes
Safer dispensing under real pressure
Clinical checks, accurate labelling and clear workflows that hold up on the busy afternoon, not just in the demo, reducing the chance of the errors that matter most.
Reconciliation you can trust
Controlled drugs, stock, dispensing and reimbursement that reconcile against one another, so discrepancies surface early and inspections and audits stop being stressful.
Hours back to the pharmacy team
Back-office automation on the repetitive work (endorsement checking, reconciliation, ordering, status updates), freeing pharmacists and staff for the clinical and patient-facing work only they can do.
What we build for pharmacy
From a first platform to modernising what you already run. The disciplines this sector draws on most.
How we deliver
- 01
Discover
We map the system, the constraints and the business it serves, including the parts nobody documented.
Architecture brief
- 02
Architect
Decisions get made, written down and defended before a line of production code exists.
Decision records
- 03
Build
Short cycles against working software. You see progress in the product, not in a status deck.
Shipping increments
- 04
Operate
Monitoring, incident response and iteration. The system is alive, so the engagement is too.
Runbooks & SLOs
Building something for pharmacy?
Tell us the problem and the constraints you are working under. A senior engineer will give you a straight view on what it would take, and say so plainly if we are not the right team for it.
Technologies we work in
Chosen per problem, not per fashion. A selection of the stack we most often reach for.
Why teams in pharmacy choose us
We treat clinical safety as the brief, not a caveat
We design from the failure modes that harm patients, and we build so those outcomes are hard to produce and always auditable. In pharmacy, that is the job. Everything else is secondary to it.
We are honest about the NHS-gated parts
We will tell you that EPS and Spine integration is the longest pole, that assurance and conformance take real time, and that no one can shortcut them, and we plan the build around that truth instead of hiding it in a hopeful timeline.
Senior engineers who operate what they ship
No juniors learning on your dispensing system. The people who design it run it, monitor it, and treat an outage during dispensing hours as the serious event it is for the pharmacy and its patients.
We say where your own sign-off is needed
We build to make compliance demonstrable, and we are clear about where you need your own pharmacist, information-governance or legal judgement rather than implying our software removes that responsibility.
Related sectors
Part of Healthcare. Adjacent sectors we also know.
Common questions
Can you integrate our pharmacy platform with EPS and the NHS Spine?
Yes. It is core to what we do, and it is also the part we are most careful to set expectations on. EPS and Spine integration means implementing the current NHS standards exactly, handling authentication the NHS way, and passing the relevant assurance and conformance steps. Those steps are gated and take real time we do not control the pace of. We start that work early, we are honest about the timeline, and we do not pretend the accreditation is instant.
We are launching an online pharmacy. How do you handle the clinical check?
By treating it as a clinical service rather than e-commerce. Orders flow through triage and a pharmacist or prescriber review before supply, with appropriateness checks, quantity and frequency limits, interaction and allergy checks against the patient record, and safeguards for higher-risk medicines: all auditable. A checkout that supplies medicines on payment alone is both unsafe and non-compliant under GPhC distance-selling expectations, and we will not build one.
Will the system keep controlled-drugs records inspection-ready?
That is a design goal from the start. We build CD registers with running balances that reconcile to physical stock, witnessed destructions recorded properly, and discrepancies surfaced immediately rather than at year end. The aim is that an inspection is a non-event because the records are simply correct and evidenced, not reconstructed under pressure.
Can AI help with triage, checking or reconciliation?
Selectively and transparently. Automation is genuinely useful for high-volume, repetitive work (reconciliation, endorsement checking, flagging), and can assist triage by surfacing information for the pharmacist. What it does not do is replace clinical judgement: the final decision stays with the accountable professional, and where a model contributes we keep its reasoning visible. We will not sell you an “AI pharmacist”, because that is neither safe nor honest.
Who is responsible for data protection and compliance. You or us?
Both, at different levels. We build so that access control, audit, minimisation and retention are demonstrable, which makes your obligations much easier to meet and to evidence. But the pharmacy remains the data controller and the regulated entity: some information-governance, pharmacist and legal sign-off is yours to give. We name that boundary clearly rather than letting good engineering create a false impression that compliance is entirely handled in the code.
Building for pharmacy?
Tell us what the system has to do and what it cannot get wrong. A senior engineer reads it, and if pharmacy is not a domain we know well enough to be useful in, we will say so rather than learn it on your budget.
- 01A senior engineer reads it. Not a form queue, and not an account manager.
- 02We reply either with questions or with a straight answer that we are not the right fit.
- 03If it looks like a fit, a technical call with the person who would actually run the delivery.
- 04Then scope, effort and risk in writing, before anyone signs anything.