Custom Medicore integration development
Appfront builds custom integrations between the Medicore EHR and your own application, client portal or back office. Through Medicore's API platform, we expose client records, calendar appointments, claims and care communication, so you no longer have to re-key data. You stay in control of privacy-sensitive healthcare data, because we work in line with the GDPR and the NEN 7510 and ISO 27001 healthcare standards.
What is a Medicore integration?
Medicore is a Dutch EHR for healthcare, with a strong position in mental health care and specialist medical care. Care providers use it to record client and patient files, schedule appointments in the calendar, process claims and communicate around treatment. Medicore also offers an API platform that allows the system to exchange data with other applications.
In practice, a custom integration means making data from Medicore available in a controlled way within your own environment — for example a client portal, a reporting or management environment, another care system or an administrative process. Depending on the interfaces available, this covers record data, calendar appointments, billing information, questionnaire or ROM outcomes and documents, in one or both directions.
Because this involves medical and special-category personal data, Appfront builds every integration in line with the GDPR and the care standards NEN 7510 and ISO 27001. We align data flows, error handling and logging with your actual care process and apply data minimisation, so that only strictly necessary data is exchanged and the integration remains reliable and demonstrably secure.
Client record made accessible
Make record data from Medicore available in your own application or portal, with strict data minimisation. Only the fields you need are exchanged — encrypted and with full logging of who requests what.
Calendar synchronised
Keep appointments and calendar data in line between Medicore and your own system or client portal. Changes stay consistent, so practitioners and clients work with the same schedule without duplicate entry.
Secure & GDPR-compliant
We build every integration involving medical data in line with NEN 7510, ISO 27001 and the GDPR: encrypted connections, strict access control, audit logging and a documented processing register, so you can demonstrably meet your obligations.
Our development process for Medicore integrations
We follow a proven methodology that removes uncertainty early and delivers a stable, secure integration. From an initial analysis of your care process, the available Medicore interfaces and the privacy requirements through to go-live and ongoing maintenance — every step is aimed at an integration your organisation can understand and trust.
We map out which data you want to exchange, which systems need to be integrated, which Medicore interfaces are available and which privacy and care requirements apply.
We design a secure integration architecture in line with NEN 7510, choose the right authentication and encryption, and draw up an error-handling strategy.
Implementation with automated tests, audit logging and monitoring, with data minimisation as the starting point. You get to see working builds along the way.
A controlled go-live with data validation and a safety net, followed by ongoing maintenance, monitoring and further development.
What a Medicore integration delivers in practice
Every Medicore integration is set up specifically for your care process, the available interfaces and the neighbouring systems. Below are the features we most often deliver for care organisations that want to connect Medicore to other applications.
API integration with Medicore
A stable integration with Medicore's API platform, so that data flows in a controlled way between the EHR and your own application, portal or administration. With authentication, encryption and clear agreements on which systems may access which data.
Client and patient record data
Make record data from Medicore accessible to a client portal, reporting environment or other care system. We apply strict data minimisation and exchange only the fields needed for the purpose of the integration — encrypted and with full audit logging.
Agenda and appointments
Synchronise calendar and appointment data between Medicore and your own scheduling system, client portal or communication channel. Changes stay consistent, so practitioners and clients work with the same appointments without duplicate entry or retyping.
Billing (VECOZO)
Make billing and administrative data from Medicore available to your own process. Billing traffic in healthcare generally runs via VECOZO; during the analysis phase we determine which interfaces are available and how billing information reaches your administration securely.
ROM & questionnaires
Make questionnaire and ROM (Routine Outcome Monitoring) outcomes from Medicore available to a client portal, treatment dashboard or reporting environment. This keeps outcome measurements visible within the system your practitioners work in.
Care communication & documents
Make documents and care communication around treatment available or exchange them, so letters, reports and attachments end up in the right place. We set up the flows so information moves between Medicore and your systems in a traceable and secure way.
Typical use cases in healthcare
A Medicore integration turns out differently for each organisation. Below are a number of sectors in which Medicore is widely used — for each of them, we look at the specific data flows, privacy requirements and adjacent systems involved.
Mental health institutions
Outpatient and inpatient mental healthcare organisations that use Medicore for client records, treatment and administration. An integration makes record, calendar or ROM data available to a client portal or management information, with privacy and NEN 7510 as the starting point. See also our API integrations.
Independent treatment centres & clinics
Independent treatment centres (ZBCs) and clinics that use Medicore for patient records, scheduling and claims. An integration aligns appointment data and administration with your own systems, so planning and claims processing run more smoothly without duplicate data entry.
Medical specialists
Medical specialist practices that use Medicore for the EHR, calendar and claims. An integration connects the record to your own applications or a referral and communication process, so specialists work with up-to-date, reliable data without retyping anything manually.
Allied health practices
Allied health practices and care providers that use Medicore for record keeping and administration. An integration makes treatment and appointment data available to your own portal, reporting or a partner, each time with data minimisation and appropriate security.
Technology we use
We build Medicore integrations on the Medicore API platform, combined with the backend stack that suits you. The exact choice depends on the available interfaces and your existing systems — always with encryption, audit logging and the healthcare standards NEN 7510 and ISO 27001 as the starting point, so your organisation can manage the integration.
If you don't use Medicore but the MicroHIS GP information system, and you want to use practice data in your own application or overview, take a look at our MicroHIS integration.
Why Appfront for your Medicore integration?
Appfront has extensive experience building API integrations for a wide range of organisations in the Netherlands, including in healthcare. We always begin with a thorough analysis of the existing systems, processes and privacy requirements — an integration involving medical data must not only be technically correct, but also demonstrably secure and of practical value.
For every integration we write clear documentation and make sure your own team, or a future supplier, can understand and manage the integration. No black box, but transparent code and clear agreements on monitoring, alerting and maintenance.
You work with a dedicated point of contact who understands both the technical and the functional side. That keeps communication lines short, prevents miscommunication and speeds up decisions when choices have to be made during the build.
Also take a look at our broader services around API integrations, middleware, custom software and web app development. Do you work with several healthcare systems? We also build integrations with VECOZO, Zorgmail, Intramed and Incura, among others, or browse all our integrations.
- Experience with API integrations for healthcare organisations in the Netherlands
- Works in line with GDPR, NEN 7510 and ISO 27001 for medical data
- Data minimisation and strict access control by design
- Secure by default — encryption, secrets management, scoped permissions
- Structured error handling and retry mechanisms
- Extensive audit logging and monitoring from day one
- Clear documentation that your organisation can read and manage
- A single point of contact, no passing you between account managers
- Ongoing maintenance and proactive further development
- An approach tailored to your existing healthcare and IT landscape
Security and privacy in Medicore integrations
An integration with an EHR involves medical and special category personal data, the most sensitive category under the GDPR. That is why Appfront builds with privacy and security as the starting point: data minimisation, encryption in transit and at rest, strict role-based access, audit logging and clear agreements on processor roles. This way we exchange only the data that is strictly necessary, and every data flow remains traceable.
In healthcare, the NEN 7510 and ISO 27001 information security standards apply on top of the GDPR. We set up the integration to align with them, document the data flows for your record of processing activities and tailor the security measures to your policy. We make no medical claims and do not store or process any data beyond what the integration requires.
More about our approach to security: information security policy and CVD policy.
- GDPR-compliant processing of special category personal data
- Alignment with NEN 7510 and ISO 27001
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access and least-privilege principles
- Data minimisation and audit logs with traceable data flows
- Automatic retry and dead-letter queues
- Secrets management following best practices
- Documentation for your record of processing activities
Frequently asked questions about Medicore integrations
Answers to the questions we are asked most often about integrations with the Medicore EHR.
A Medicore integration is a technical connection between the Medicore EHR and another system, for example your own application, client portal, administration system or a data warehouse. Through Medicore's API platform you exchange data on client records, calendar appointments, claims and documents, so information no longer has to be retyped by hand. The integration can be simple (reading out a single data flow) or extensive (two-way synchronisation with multiple systems).
Medicore is mainly used in mental healthcare, independent treatment centres, by medical specialists and in allied health practices. An integration is worthwhile as soon as you want to combine Medicore data with your own application, a client portal, a reporting environment or another healthcare system. Together with you, we look at which data flows add value and how they can be exposed securely and in compliance with the GDPR.
Depending on your situation and the available API capabilities, this often involves client and patient data from the record, calendar and appointment data, claims and administrative information, questionnaire or ROM (routine outcome monitoring) results and documents. Together we determine which fields are strictly necessary and apply data minimisation, so that only the data you actually need for the purpose of the integration is exchanged.
Claims traffic in healthcare generally runs via VECOZO. In an integration, we can expose billing and administrative data from Medicore and make it available in your own process or administration. Whether a direct VECOZO flow is possible depends on the available interfaces and your connection; we map this out in concrete terms during the analysis phase before we build anything.
A simple integration, for example reading out a single data flow, can be up and running relatively quickly. More extensive scenarios with two-way synchronisation, multiple systems and strict healthcare requirements take more time, partly because care and privacy weigh heavily here. After an intake conversation and an analysis of the available interfaces, we will give you a realistic estimate.
Yes. Because it involves medical and special category personal data, we build in line with the GDPR and the healthcare standards NEN 7510 and ISO 27001. That means encrypted connections, strict access control, data minimisation, audit logging and a documented record of processing activities. We make clear agreements on processor roles and document the data flows, so you can demonstrably meet your obligations.
Yes. Appfront regularly takes over the management of existing integrations, including those originally built by another party. We review the data flows, error handling, logging and security, document the current setup and draw up improvement proposals. From that point on, we can handle changes, extensions, monitoring and maintenance.
We start with a conversation about your goal: which systems do you want to integrate, what data is needed and what should happen on the other side? Together with you and, where relevant, your Medicore administrators, we then map out which API options and access are available. Based on that, we draw up a secure architecture and a clear quote, without you having to work everything out in detail beforehand.
Ready to build your Medicore integration?
Tell us which systems you want to connect to Medicore and what data is involved. We're happy to advise on the architecture, the privacy requirements and a secure, manageable integration. Book a no-obligation consultation; within half an hour you'll have a clear picture of what's possible.