Service · Software development

Custom pharmacy software.

Custom software for community pharmacies, hospital pharmacies, out-of-hours pharmacies, online pharmacies and pharmacy chains. A patient portal, an automated baxter flow, a logistics layer around refrigeration and the safe, group-level reporting or integrations with LSP, Vecozo and your EHR. We don't replace your pharmacy information system (AIS) — we build what the AIS doesn't do.

LSP integrationNEN 7510Baxter flowPatient portal

Custom software alongside your existing AIS.

The Dutch pharmacy market has a handful of established pharmacy information systems (AIS) — Pharmacom from CGM, Aposys, Aposoft, Lauren from Mediq, Pharmasys, Promedico, Synaeda. For small-scale and standard work they do an excellent job, and we don't build a replacement for them. It's a different story once your workflow falls outside the standard: a patient portal with real-time baxter status, a logistics layer for refrigeration and the safe with lot traceability, a central module that manages multiple branches, or a clinical pharmaceutical application in a hospital pharmacy.

Since 2015 we have been building custom healthcare software, for hospitals, mental health organisations and laboratories, among others. Our approach for pharmacies is the same: we work closely with your pharmacists and IT department, integrate with the systems already in place (G-Standaard, Z-Index, LSP, Vecozo, the AIS itself, possibly an EHR), and deliver an environment that complies with NEN 7510 and the GDPR for medical data. No all-in-one platform promise — just a precise piece of software that does what your current stack struggles with.

Whether you are a community pharmacy with a customer base that wants more digital service, a hospital pharmacy with compounding flows the standard AIS doesn't support, an out-of-hours pharmacy formula with evening and weekend peaks, an online pharmacy that relies heavily on logistics, or a chain such as Mediq, BENU or Service-Apotheek with central management requirements: the architecture we put in place acknowledges that the AIS is already there and builds around it. No rip-and-replace, but an extension that fits your working process.

Three patterns in which we build pharmacy software.

Not every project looks the same. Below are the most common forms — which one fits, we determine in the first conversation.

Compact project · fixed sprint budget

Patient portal or app

A secure, private environment in which patients see their medication overview, request repeat prescriptions, track baxter roll status and schedule deliveries. Login via DigiD or magic link, connected to your AIS through a thin integration layer. Often the first step for pharmacies that want to take patient communication off the phone and email. Push notifications for a new roll or for a delay on chronic medication. For pharmacy chains, the portal can work across multiple branches: a patient can choose their preferred pharmacy and collect or have their medication delivered there.

DigiD loginRepeat prescription flowBaxter statusDelivery schedulingPush notifications
Mid-sized project · fixed sprint budget

Logistics layer for dispensing and stock

For pharmacies with serious logistical complexity — refrigerated medication, opiates in a safe, baxter roll production, automated dispensing via a robot picker. A layer around your AIS for FEFO stock, lot traceability (so a recall can be carried out in minutes instead of hours) and integration with your automation. Including temperature logging for refrigeration (audit-required for some medication), safe protocols for opiates with dual authorisation, and a planning module for baxter production that takes changeover days and urgent requests into account.

FEFO stockLot traceabilityRobot picker integrationSafe and refrigeration flowTemperature log
Larger project · fixed sprint budget

Group or hospital pharmacy platform

For pharmacy chains and hospital pharmacies with clinical pharmacy, oncology compounding or parenteral nutrition. A central platform that manages local branches, with integrations to EHRs (HiX, Epic, Nexus, ChipSoft), claims flows and MDR reporting. A dedicated role model for hospital pharmacist, clinical pharmacist, assistant and physician; audit log as standard; and region-specific flows within a single group. For chains such as Mediq, BENU or Service-Apotheek, we often also build a group reporting layer on top of the local pharmacy information system (AIS) installations, so finance and purchasing get one consolidated view without the individual pharmacy losing its local autonomy.

EHR integrationsMulti-branchClinical pharmacyMDR reportingGroup dashboard

What you get at the end.

A working production environment plus everything around it to manage it within your own pharmacy. No black box.

  • The pharmacy software itselfProduction and staging environments, running in a Dutch cloud (GCP, AWS Frankfurt or Azure West Europe) or on your own infrastructure if you prefer.
  • Codebase and documentationFull source code in your own Git repository, with build and deployment instructions and an architecture overview. No vendor lock-in.
  • Integrations with G-Standaard, LSP, Vecozo and the AISWhere the scope touches them, we deliver the integrations working with test data from your AIS supplier and the Z-Index/G-Standaard medication database.
  • NEN 7510 and GDPR packageDPIA document, a data processing agreement, audit log built in as standard, and encryption in transit and at rest. Ready for an external security audit.
  • Training for pharmacists and assistantsTwo sessions for key users in your pharmacy, plus a short video tutorial you can replay for new staff or when a new branch joins.
  • Support contract (optional)Monitoring, backups, security patches and ongoing development. A fixed monthly fee with four different response-time levels, depending on how critical the system is to your pharmacy operations.

When custom is the right choice.

Four signals that typically lead to us being called in. If you recognise one in your pharmacy, we'd be glad to talk it through.

Patient communication

Phone and email are overwhelmed

Repeat prescriptions, questions about baxter rolls and deliveries eat up assistants' time. A client portal or app takes over the bulk and gives patients insight into their medication overview and delivery schedule. Your assistants can focus on the conversations that do deserve personal contact.

Logistics

Stock, refrigeration and the safe become complex

You work with refrigerated medication, opiates, baxter roll production and perhaps a robot picker. The standard stock module in your AIS can't get a grip on FEFO or the lot traceability you need during a recall. A separate logistics layer, integrated with your AIS, solves that structurally.

Scale

Multi-branch group

You run a pharmacy chain or out-of-hours pharmacy formula and want to manage stock, claims and reporting flows centrally. Local autonomy where it matters, a shared layer where it makes sense, without every branch having to give up its own AIS installation.

Clinical pharmacy

Hospital pharmacy with compounding

Oncology compounding, parenteral nutrition, clinical pharmacy: flows that a regular AIS doesn't support, or only with difficulty. Often integrated with the hospital's EHR, with dedicated roles for hospital pharmacist, assistant and physician, and with MDR reporting for the medication safety committee.

Online pharmacy

Scale calls for automation

An online pharmacy relies heavily on order management, shipping flow and patient self-service. Standard pharmacy information system (AIS) front ends aren't built for web scale. A custom ordering front end, with a thin integration layer to your AIS, gives you the UX control you need.

Compliance

NEN 7510 audit coming up

You're heading towards recertification or an external audit, and your current tools (especially the home-built Excel flows and SharePoint folders) won't hold up. A built-in audit log as standard, plus a structured role model, saves a lot of work in the audit room later.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

How a pharmacy software project works.

1

Introduction

A conversation in which we map out your current stack: which AIS you use, which integrations are in place, which compliance requirements apply (NEN 7510, MDR, BIG register), and exactly where the pain lies. No sales deck, just concrete questions for your pharmacists and your IT lead.

2

Scope workshop and pharmacist interviews

A workshop with your team, plus short sessions with a few pharmacists and assistants in the pharmacy itself, not just management. At the end you have a concrete scope, a plan per sprint, and the first screen flows of the portal or the logistics layer. For hospital pharmacies we also involve the pharmaceutical safety committee and the EHR team.

3

Building in sprints

Every two weeks, a working build you can test in a staging environment with real test data from your AIS. A few sprints for a first client portal, or a multi-sprint project for a logistics layer or multi-site group platform. You decide per sprint whether we continue, scale up or adjust the scope.

4

Pen test, rollout and maintenance

An external pen test in the final sprint, audit log verified, and integrations with LSP, Vecozo and Z-Index/G-Standaard formally tested. Then a phased rollout to your locations or patient population, with ongoing maintenance covering security patches, monitoring, backups and further development. No big-bang go-live, just a calm phasing that doesn't disrupt your pharmacy operations.

Frequently asked questions.

What pharmacy owners, hospital pharmacists and group IT teams usually want to know first.

Do you replace Pharmacom or another AIS?
Not for small, standard pharmacy work. Pharmacom from CGM, Aposys, Aposoft, Lauren from Mediq, Pharmasys, Promedico and Synaeda handle the regular pharmacy process well, and we don't build a replacement for them; that would be a multi-year project and many times the investment, and it would never pay for itself. We build custom software when your flow falls outside that standard: a client portal, a logistics layer, a group module, an online pharmacy front end, or a clinical pharmacy application. The AIS remains the source of medication data and claims; we add what's missing around it.
Can you integrate with LSP, Vecozo and Z-Index?
Yes. We have experience with the Landelijk Schakelpunt (LSP) for medication exchange, with Vecozo for claims and insurer flows, and with Z-Index and the G-Standaard for medication monitoring, interactions and contraindications. For LSP, your pharmacy must be connected via an approved gateway; we work within those rules and can support you with the connection if you don't have one yet. For EHR integrations (HiX, Epic, Nexus, ChipSoft) we use HL7 FHIR standards wherever possible instead of proprietary protocols, for long-term sustainability.
Does the software comply with NEN 7510 and the GDPR?
Built in as standard. NEN 7510 for information security in healthcare and the GDPR for patient and medication data are the foundation of every pharmacy project. In practice that means: a DPIA at the start, a data processing agreement between you and us, encryption in transit and at rest, an audit log as standard, and an external pen test in the final sprint. For hospital pharmacies we also carry through MDR reporting and clinical audit requirements, plus alignment with the hospital's medication safety committee. Data centres are always in the Netherlands or in a European region covered by the GDPR; no US cloud regions for patient data.
How does the baxter flow work in your custom software?
A baxter (pharmacy-prepared multi-dose medication roll) flow typically runs from medication monitoring (interactions, contraindications, dosage) through production planning (which rolls are produced when, often in cooperation with a central baxter facility) to dispensing and delivery to the patient. We build this as a layer on top of your pharmacy information system (AIS), not as a replacement: your AIS remains the source of the medication overview and billing, and we add the workflow and patient-visibility side. Production status often appears in real time in a client portal, so the patient or informal carer can see when the next roll is ready and when delivery is expected. For pharmacies that outsource baxter production (for example to Brocacef or Mosadex), we build the integration with the external production environment.
Does this work for a pharmacy chain or out-of-hours pharmacy formula?
Yes, and it is one of our most common patterns. A central layer above your branches, for group reporting, shared stock visibility, a single customer database and a single billing flow, while each branch keeps its own AIS installation and local autonomy. We have done this before for multi-location healthcare chains, so the architecture is proven. For out-of-hours pharmacy formulas, patient self-service in the evenings and at weekends is often added: an online intake plus delivery scheduling, so the assistant no longer has to handle every call manually during the busy hours.
What determines the cost?
Scope, integrations and compliance. A client portal with DigiD login and a single AIS integration is a different project from a hospital pharmacy platform with EHR integration, oncology compounding and MDR reporting. We always work with a fixed sprint budget per phase, so you can decide per sprint what to include or drop. No open-ended contracts, no unforeseen extra costs. For concrete figures for your situation, we provide a substantiated estimate per phase after the first conversation.
How quickly can we go live?
A first tier, for example a working client portal for a single branch, can be up and tested with a small group of patients within a few sprints. A full group platform or a hospital pharmacy application with multiple EHR integrations is a project spanning multiple sprints. We don't commit to hard dates until the scope is fixed; in healthcare that is a promise you'd rather not hear and one we'd rather not make.
Do you work with our current AIS supplier and IT department?
Almost always. We hand over knowledge in the final sprint, deliver a runbook for incidents, and agree clear responsibilities for maintenance. With the AIS supplier (Pharmacom, Aposys, Promedico or another) we liaise on integration specifications and test data; if they have a formal integration route we use it, and if not we work from documentation or a reverse-engineered integration that we agree with you beforehand.

Talk to us about your pharmacy software.

A no-obligation introductory call of half an hour. Tell us what your current AIS is struggling with, whether that is a missing client portal, a manual logistics flow, a missing group layer or a clinical pharmacy application, and we'll give you direction. For broader context, see also our pages on custom healthcare software, smart API integrations and enterprise software; for adjacent domains, mental healthcare software and laboratory software.

Edit content