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.