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.