Sector · Healthcare

Appointment portal for clients. Custom-built, GDPR-secure, integrated with your EHR.

We build patient portals that fit how your practice or organisation actually works. Online booking, smart reminders, video consultations, questionnaires in advance and direct access to records, with DigiD, FHIR and NEN 7510 built in from the first sprint.

ForGPs & out-of-hours services
ForPhysiotherapy & allied health
ForMental health care & psychology
ForDental care & hearing aid dispensers
ForHospital outpatient clinics

Dutch primary and secondary care in numbers.

~5.000
GP practices in the Netherlands
~7.000
Physiotherapy practices
~280
Hospital sites & clinics
17,9M
Residents entitled to digital access to their records

Source: NIVEL Figures 2024, CBS population counter, Nictiz MedMij Annual Report 2024.

Standard portals are built for the average practice.

Most healthcare providers use a patient portal that comes as a by-product of the EHR: an appointments module in Medicom, a my-environment in HiX, a widget from MijnQuarant. The basics work, such as booking an appointment and receiving a confirmation, but as soon as a practice wants more than that, it runs into the fact that the portal was never designed for your line of care.

A GP practice wants open-calendar booking for repeat consultations but telephone triage for acute complaints. A physiotherapist wants questionnaires in advance so the first fifteen minutes in the treatment room aren't spent on a paper PSK form. A mental health organisation wants video consultations alongside face-to-face, with the same record context. A hospital outpatient clinic wants multidisciplinary appointments where radiology, the surgeon and the intake nurse all fit into a single day.

A custom booking portal solves this differently: the flow for each line of care is exactly what it should be, the client arrives prepared for the consultation, and your front desk doesn't lose time on phone calls that could have been handled in two taps. For the broader technical context of healthcare apps, see our page on building custom healthcare software.

Experience shows us that the benefit of your own portal isn't only about efficiency. It also lies in client satisfaction and continuity of care. A client who can book an appointment online while the practice is closed, a parent who books for two children at once, a chronic patient who gets a repeat consultation the same afternoon after a repeat prescription request: these are the small differences a practice builds its reputation on in the neighbourhood. For multi-location healthcare providers there is the added benefit that a single portal working across all sites prevents each location from building its own channel, which would later need migrating or consolidating anyway.

A portal that fits every line of care.

Each discipline has its own flow, its own integrations and its own privacy requirements. Under each tab you'll find an idea of what we typically build: not a one-size-fits-all template, but a shared technical foundation.

GP care

This is where the biggest volume sits: repeat prescriptions, repeat consultations, public health service (GGD) referrals and annual check-ups for the chronic care chains (T2DM, COPD, CVRM). An appointment portal for a GP practice has to distinguish between what patients can book themselves and what requires triage, without making them click through seven screens first.

Our module set for GP care includes a DigiD login for BSN-based identification, a calendar layer that only shows freely bookable slots per appointment type, a repeat prescription flow with direct FHIR forwarding to Medicom or Promedico, and a reminder module with SMS and push notifications for annual check-ups.

  • DigiD via LogiusBSN-based identification without creating a separate account.
  • Appointment-type-aware calendarAcute, regular, repeat and chronic appointments each get their own slots.
  • Repeat prescription flowFHIR forwarding to Medicom or Promedico, with pharmacy routing.
  • Chronic care remindersT2DM, COPD and CVRM annual check-ups via SMS and push.

Built to healthcare's strictest standards.

Compliance is not optional, and it is not something to bolt on afterwards. An appointment portal touches the whole of the Wbsn-Z (Dutch Healthcare Citizen Service Number Act), GDPR, NEN 7510, MedMij rules and the WGBO (Dutch Medical Treatment Contracts Act) retention obligation. We work within that framework from the first sprint. For more technical detail, see our page on building NEN 7510-compliant software.

NEN 7510: healthcare information security

Deliberate risk management

Our patient portals are built in line with NEN 7510-2:2017. That means a risk analysis of data flows, access rights, logging and a pen test before go-live. For large care chains, we bring in an accredited auditor for the formal certificate.

GDPR & UAVG

Privacy by design

Every project includes a DPIA under Art. 35 GDPR. Data flows, legal basis (performance of the treatment agreement under Art. 6(1)(b) and Art. 9(2)(h)), retention periods and data subject rights are documented for the data protection officer (DPO).

WGBO and GDPR retention period

20-year retention obligation

The WGBO retention obligation for medical records and the adjusted timeframes for deletion requests are built into the retention policy. Patients can exercise their rights through the portal: access, a copy, correction and requests for destruction.

BSN access via DigiD

Wbsn-Z-compliant identification

BSN-based authentication via DigiD (assurance level Substantial or High, depending on the care context). The integration runs via Logius and is approved for healthcare portals. No "self-created account": that doesn't meet the requirements for a BSN integration.

MedMij / FHIR

Personal health environment

The portal complies with the MedMij set of agreements, so patients can share their data with their own PHR (such as Ivido, Quli or MedMij Drugref). FHIR R4 is the interface and Nictiz health information building blocks (Zorginformatiebouwstenen) are the data model. Onboarding via MedMij is guided, and we arrange participation as part of the project.

eIDAS: electronic signature

Signing treatment agreements

For informed consent forms, treatment agreements and questionnaires that require a signature, we support eIDAS-compliant signing (advanced or qualified, depending on the use).

EU AI Act

Responsible AI in triage

For AI features such as intake triage or free-text classification of a questionnaire, we make the risk classification explicit, document the governance process and stay below the threshold that the EU AI Act applies to healthcare applications.

Seamlessly integrated with the EHR you already use.

The portal does not replace your EHR. It sits alongside it, reading and writing through a secure integration layer. We have working integrations with the systems you see below. For the broader context of patient record apps, see building an electronic health record app.

Medicom
GP EHR (PharmaPartners)
Promedico-ASP / VDF
GP EHR
OmniHis Scipio
GP EHR
HiX
Hospital EHR (ChipSoft)
Epic
Hospital EHR (university medical centres)
MijnQuarant
Allied health / physio
HC&H / Intramed
Allied health & dental care
Centric Zorg / Procura
Care, mental health & primary care

No one-off integrations per project.

We have standardised the integrations above across multiple healthcare projects. For a new project, we set up the integration using the same abstraction layer: an internal FHIR canonicalisation, so that a GP practice and a physiotherapy practice can use the same portal front end on top of different EHRs. That means fewer bugs, a faster turnaround, and ongoing management sits with your IT supplier or DPO, not with us.

For custom middleware, older SOAP services or a hospital-specific HL7 bus, we build an adapter case by case. This takes a little extra time in the planning phase, but it avoids the familiar integration debt later on: a working integration that has never been tested against new versions of the EHR.

The portal can also be used as a pure booking layer on top of a calendar system for healthcare providers that don't yet have a full EHR. See our work on building a booking system for the underlying booking architecture.

The technical building blocks under the hood.

No black box. We document the entire stack so that your IT team, DPO and accountant can see exactly what runs where, and how we can be replaced without disruption.

Backend

PostgreSQL + Node.js

EU hosting with an NEN 7510-certified provider. Encryption at rest with keys held in an EU HSM. No data leaves the EEA, and no sub-processors outside Europe.

Identification

DigiD via Logius

BSN-based authentication in line with the Wbsn-Z (Dutch Healthcare Client Identification Act), at assurance level Substantial or High. For healthcare staff, a UZI card or a qualified alternative via eHerkenning.

Interoperability

FHIR R4 + ZIBs

Your own FHIR server on top of the EHR for a standardised read and write layer. Nictiz health information building blocks (Zorginformatiebouwstenen) as the data model. Compatible with the MedMij set of agreements.

Video consultation

Our own WebRTC or Whereby

End-to-end encrypted video consultations, optionally with server-side recording that lands in your EHR. No external party in the chain if the care context requires it.

Notifications

SMS, email & push

Multi-channel reminders via an EU SMS provider and our own push server. Clients choose their channel in the portal; no tracking pixels in emails.

Questionnaires

FHIR Questionnaire

Standard questionnaires (PSK, PHQ-9, GAD-7, SF-36) and custom questionnaires as FHIR Questionnaire resources, with automated scoring and forwarding to the EHR.

Multi-language

NL, EN, AR, TR, PL

A multilingual portal as standard for neighbourhoods and primary-care practices serving a broad language audience. Translations are done by healthcare translators, not by a raw LLM.

Accessibility

WCAG 2.2 AA

Keyboard navigation, screen reader labels, contrast and a large-text mode as standard. Mandatory for public healthcare institutions under the Dutch Temporary Digital Accessibility Act.

Management & phase-out

Open-source stack

We use open-source components wherever possible and hand over the source code plus deployment documentation. No lock-in: if you want a different partner tomorrow, you can.

From intake to go-live in clear steps.

Implementing a healthcare portal has its own rhythm. Five phases come back in every project, whether it's a GP practice or an outpatient clinic.

01 · Audit

Workflow and EHR mapping

Half a day at your practice with a GP, practice manager and assistant. Result: current flows mapped, EHR interfaces defined, and a first DPIA outline ready.

02 · Design

Scope per care line

For each discipline: which flow goes into the portal, which integrations take priority and which questionnaires run by default. NEN 7510 risk analysis on the scope.

03 · Build

Two-week sprints

One working flow delivered every sprint. Practice staff test alongside us from day one, and the first flow typically goes live on a test environment within a few sprints.

04 · Cutover

Phased go-live

One care line first, then the next. With each rollout: training for the front desk, written work instructions and a handover to your practice manager or DPO.

05 · Maintenance

Ongoing

We help with every EHR update, GDPR guidance change and MedMij version bump. Fixed monthly price, first-line incident response in line with your NEN 7510 requirements.

Work for healthcare providers.

GP chain · Randstad

Portal for self-booking repeat consultations

DigiD login, FHIR integration with Medicom, and automatic SMS reminders for chronic-care annual check-ups across multiple practices.

−61%
incoming call minutes
9 practices
merged into a single portal
Physiotherapy chain · North Holland

Pre-appointment questionnaires & video consultation

PSK, NPRS and a custom intake questionnaire as a FHIR Questionnaire, integrated with MijnQuarant. Video consultation for follow-ups via our own WebRTC.

−42%
paper intake
11.000+
clients with an active account
Outpatient clinic · Secondary care

Multidisciplinary appointment portal

Three care lines on the same day in a single appointment flow: surgeon, anaesthetist, intake nurse. Integration with HiX via the agreed FHIR layer.

3 care lines
in a single booking flow
SUS 84
client satisfaction

Trusted in healthcare.

Nictiz MedMij Annual Report 2024

"The emergence of dedicated appointment portal suppliers is accelerating the use of MedMij among care providers who don't want to rely solely on the EHR portal."

LHV Practice Perspective 2024

"GPs who have introduced self-scheduling for repeat consultations report noticeably fewer incoming phone calls and higher satisfaction among regular patient groups."

Client survey, mental health institution

"The video consultation portal has noticeably reduced our no-shows for intake appointments. Clients particularly appreciate being able to view their treatment plan directly."

Answers for the care manager who is going digital.

The questions we hear most from practice managers, data protection officers and IT coordinators.

How does your portal differ from the standard portal in my EHR?
An EHR portal is a standard product for "all GPs", designed to work for as many practices as possible. Our custom portals start from your care line, your consultation types, your questionnaires and your client target group. We write back to the EHR neatly via FHIR, but the client experience is fully tailored to your practice. For a detailed comparison with records apps, see Building an EHR app.
Does it comply with NEN 7510 and the GDPR?
Yes, that is non-negotiable. An appointment portal handles special category personal data (health) and falls under NEN 7510, GDPR Art. 9 and the WGBO retention obligation. We work within that framework from the very first sprint: NEN 7510 risk analysis, DPIA, pen test before go-live, sub-processor register and logging of all record actions. For large organisations, we support the process towards a formal NEN 7510 certificate. That certificate is issued to the organisation, not to the software, but our software supports the audit process.
How does the DigiD integration work?
The DigiD integration runs via Logius. Connecting requires the care provider to submit a connection request to Logius, plus a SAML integration at assurance level Substantial or High. We guide the application, supply the technical connector and make sure the entire flow complies with the Wbsn-Z (the Dutch act on the use of the citizen service number in healthcare). Clients log in with the DigiD app, SMS or ID verification via the DigiD app, and the portal links the BSN to the correct record in your EHR.
Do you work with Medicom, HiX or Promedico?
With all three, and with OmniHis, MijnQuarant, HC&H/Intramed, Centric Zorg, Procura and Epic. With Epic and HiX we work via the agreed FHIR interfaces with the supplier; with Medicom and Promedico via their published interface. The portal has its own internal FHIR abstraction layer, so the difference is invisible to your clients, and for your IT team it delivers a reusable integration layer.
What is MedMij and do I need to take part?
MedMij is the Dutch framework of agreements for data exchange between care portals and personal health environments (PHEs). Participating in MedMij is not mandatory for an appointment portal, but it is relevant for clients who want to share their data with a PHE such as Ivido or Quli. We build the portal to be MedMij-compatible as standard; we also complete the participation process during the cutover phase.
How do you handle video consultations and privacy?
We offer two variants: a custom WebRTC stack on EU hosting with end-to-end encryption (no traffic via US servers), or an embedded Whereby Embedded integration where the care context allows it. Recordings, if required, land directly in your EHR; the video stream itself doesn't pass through a third party in the chain if the NEN 7510 classification rules that out.
How much does an appointment portal cost?
For a single care line with a standard EHR integration and a limited number of questionnaires, an MVP project is compact. A chain-wide portal with multiple care lines, multiple EHRs, video consultation, MedMij participation and a multilingual flow is a larger project. We work with a fixed sprint budget and give you a concrete total price for the complete build after the planning phase: no open-ended costs, and no scope creep without your approval.
Who pays the DigiD, MedMij and Logius costs?
The subscriptions with Logius (DigiD) and MedMij participation go through your organisation. We charge no retainer or pass-through on them. We do advise which subscription type suits your volume and help with the connection application, including the privacy impact justification that Logius expects with the application.
Does it also work if we want an internal employee portal for our care teams?
Yes. The underlying stack (auth, FHIR layer, calendar) is equally suited to an internal portal for the care team. For the broader context of internal employee environments, see our page on building an employee portal.
How do our administrative staff embrace the portal?
Sprint 1 always includes a workshop with your practice's front-desk team. Their input shapes the flow, so nothing gets designed over their heads. On delivery, you get two training sessions and a written work instruction. We see that practices whose front desk is involved from the start notice the volume of incoming calls dropping within a few weeks of going live.
Share LinkedIn Email

Ready to future-proof your appointment portal?

A half-hour introduction with the practice manager and one healthcare professional. We listen, ask questions about your EHR and care line, and give you an initial direction. No obligation.

Edit content