How does your portal differ from the standard portal in my EHR?
An EHR portal is a standard product built 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 patient group. We write back neatly to the EHR via FHIR, but the patient 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 data (health data) and falls under NEN 7510, GDPR Article 9 and the WGBO retention obligation. From the first sprint we work within that framework: NEN 7510 risk analysis, DPIA, penetration test before go-live, sub-processor register and logging on all record actions. For larger organisations we guide the process towards a formal NEN 7510 certificate — which is issued to the organisation, not 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. For Epic and HiX we work through the agreed FHIR interfaces with the vendor; for Medicom and Promedico via their published interfaces. The portal has its own internal FHIR abstraction layer, so for your patients the difference is invisible, while 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 (PGOs). Participation in MedMij is not mandatory for an appointment portal, but it is relevant for clients who want to share their data with a PGO such as Ivido or Quli. We build the portal to be MedMij-compatible as standard, and we 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 one care line with a standard EHR integration and a limited number of questionnaires, an MVP engagement is compact. A cross-chain portal with multiple care lines, multi-EHR support, video consultations, MedMij participation and a multilingual flow is a larger engagement. We work with a fixed sprint budget and provide a concrete total price for the complete build after the planning phase: no open-ended scope, and no scope creep without your agreement.
Who pays the DigiD, MedMij and Logius costs?
The subscriptions with Logius (DigiD) and MedMij membership are arranged through your organisation, and we have no retainer or pass-through charge on them. We do advise which subscription type suits your volume, and we help with the connection application, including the privacy impact justification that Logius expects with the application.
Does this also work if we want an internal staff portal for our care teams?
Yes. The underlying stack (authentication, 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 will our secretarial staff embrace the portal?
Sprint 1 always includes a workshop with your practice secretariat. Their input shapes the flow; the design is never imposed over their heads. At handover there are two training sessions and a written user guide. We have seen that practices where the secretariat is involved from the start notice a drop in incoming phone calls within a few weeks of going live.