Custom Nedap integration development
Appfront builds custom integrations with Nedap ONS, the leading EHR in Dutch healthcare. Through the official Ons API, we connect client records, scheduling, staff and billing data to your own care application, client portal, rostering tool or BI dashboard. Your care team works in one familiar environment, and client and staff data stays up to date everywhere, securely and in line with GDPR and NEN 7510.
What is a Nedap integration?
Nedap ONS is Nedap's electronic health record and care administration platform, used by more than a thousand care organisations in the Netherlands. ONS brings together client records, care plans, reporting, scheduling and billing. Many organisations in elderly care, disability care, mental health care and home care run their daily care process on it.
In practice, a custom integration means: synchronising client and staff data between ONS and your own application, feeding a client portal with up-to-date record information, passing scheduling and rosters on to an external tool, exposing billing data to your invoicing system, and retrieving reports for a BI dashboard. The integration is built around your actual care and administrative processes.
Appfront builds according to the official Nedap Ons API documentation and the OWASP ASVS security standard. Because this involves medical and special-category personal data, we work with data minimisation and scoped access, and we go through the Nedap onboarding and review process so that the integration goes live reliably and in compliance.
Client record at the centre
The client record, care plans and reporting remain the source of truth in Nedap ONS. The integration exposes exactly the data your application needs, and no more, so care professionals everywhere work with the same, up-to-date information.
Clients and staff in sync
Client data, care relationships and staff information stay synchronised between ONS and your systems. Changes in the EHR flow through to your application, with no double entry and no diverging records.
Scheduling and billing
Pass scheduling and rosters on to external tools and expose billing data to your invoicing system. This way, the administrative process lines up seamlessly with the care that was actually delivered.
Our development process for Nedap integrations
We work with a proven approach that removes uncertainty early and delivers a stable integration. From an initial analysis of your care processes, record flows and the Nedap onboarding process through to go-live and ongoing support, every step is aimed at an integration your team can understand and trust.
We map out which data from Nedap ONS you want to expose (client, record, staff, scheduling or billing), which systems will be connected and which data is genuinely needed, following the principle of data minimisation.
We design the integration architecture, set up authorisation via OAuth and API credentials, and define an error-handling strategy, in line with NEN 7510 and the Nedap onboarding process.
Implementation with automated tests, structured logging and monitoring. You see working builds along the way.
A controlled go-live with data validation and a safety net, followed by ongoing maintenance and further development.
What a Nedap integration delivers in practice
Every Nedap integration is tailored to your care process, your type of organisation and the surrounding systems. Below are the features we deliver most often for care organisations and care-tech vendors looking to integrate with the Nedap ONS EHR.
Client and record sync
Synchronise client data, care relationships and record information between Nedap ONS and your own care application. Changes flow through without double entry, with scoped access so that only the required fields are exposed.
Scheduling and rostering integration
Pass scheduling and rosters from ONS on to an external rostering tool, or write scheduling from your own application back to ONS. Care professionals work from one up-to-date calendar, and staffing levels stay accurate everywhere.
Billing and invoicing
Expose billing data from Nedap ONS to your invoicing or accounting system. Delivered care flows through to the financial administration, with traceable data flows and completeness checks.
Client portal
Feed a client portal or informal-carer app with information from the record: appointments, care plan and access to reports. Clients and their relatives get secure, controlled access to exactly the data intended for them.
Home automation and care tech
Integrations between ONS and care technology or home automation: connecting signals, sensors and alerts with client data and scheduling. This brings remote care and the client record together in one workable whole.
BI dashboards
Pull reports and key data from Nedap ONS into a BI dashboard, for example in Power BI. Management and quality teams get insight into output, staffing levels and quality of care, built on reliable source data.
Typical use cases in practice
A Nedap integration looks very different for each care organisation. We see a number of patterns come up again and again — and for each one we have a working setup that pays attention to data minimisation, the Nedap onboarding process and the right authorisation.
Elderly care organisations
Nursing homes, residential care homes and home care providers that use ONS for records, scheduling and invoicing. An integration with your own app or client portal keeps client and staff data up to date everywhere, without double entry. See also our API integrations.
Disability care
Disability care organisations with intensive, long-term care relationships. Connect care plans, reporting and scheduling from ONS to support worker apps and supporting software, so support workers can work close to the client with up-to-date record information.
Mental health institutions
Mental health care providers that manage client records, treatment plans and reporting in ONS. An integration exposes only the data that is needed, with strict data minimisation, to treatment applications, questionnaires or a client portal.
Home care
Home care organisations with care delivered on location and changing routes. Connect scheduling, client data and reporting from ONS to mobile apps and route planning, so staff on the move can securely access the right, up-to-date record information.
Technology we use
We build Nedap integrations with the official Ons API, described via an OpenAPI specification, combined with the backend stack that suits you. The exact choice depends on the endpoints you need, authorisation and adjacent systems — so that your own team can manage or further develop the integration.
If your organisation records medication and administrations in Axiom nCare and you want that data alongside the EHR in your own overview, take a look at our Axiom nCare integration.
If your organisation uses Caress from PinkRoccade instead of Nedap Ons, take a look at our Caress integration.
Why Appfront for your Nedap integration?
Appfront has extensive experience building API integrations for a wide range of organisations in the Netherlands. We always start with a thorough analysis of your existing systems and processes — an integration must not only be technically correct, but also add practical value to your care and administrative processes.
For every integration we write clear documentation and make sure your own team — or a future supplier — can understand and manage it. 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.
- Experience with the Nedap Ons API and the EHR data model
- Specialist in integrations between ONS and custom care applications
- Familiar with client, record, scheduling and invoicing flows
- Secure by default — scoped access, OAuth and data minimisation
- Working in line with NEN 7510, ISO 27001 and the Nedap onboarding process
- Structured error handling and retry mechanisms
- Extensive logging and monitoring from day one
- Clear documentation that your team can read and maintain
- A single point of contact, no passing you between account managers
- Ongoing maintenance and proactive further development
Security and privacy in Nedap integrations
Data from Nedap ONS consists of medical and special category personal data — the most sensitive category under the GDPR. That is why security comes first in every integration. Appfront applies strict data minimisation: we expose only the fields your application really needs, with scoped access via OAuth and API credentials. We build in line with OWASP ASVS, NEN 7510 and ISO 27001, with encryption in transit and at rest, audit logging and sharply separated permissions per integration.
We go through the Nedap onboarding and assessment process, in which the functional and technical design of the integration is documented with explicit attention to data minimisation. We document the data flows so that your record of processing activities is complete and you can demonstrably comply with the GDPR. This keeps control over client data with your care organisation.
More about our approach to security: information security policy and CVD policy.
- Data minimisation and scoped access to the record
- GDPR-compliant processing of special category personal data
- In line with NEN 7510 and ISO 27001
- Encryption in transit (TLS 1.2+) and at rest
- Role-based access and least-privilege principles
- Audit logs with traceable data flows
- Monitoring and alerting for anomalies
- Documentation for your record of processing activities
Frequently asked questions about Nedap integrations
Answers to the questions we get asked most often about integrations with Nedap ONS.
A Nedap integration is a technical integration between Nedap ONS, the electronic health record (EHR) and care administration platform, and another system, such as a custom care application, client portal, scheduling tool, billing system or BI dashboard. Through the official Ons API, data on clients, care records, staff, scheduling and claims is exchanged securely. An integration can be simple (periodically synchronising client data) or extensive (real-time record data, passing on scheduling and retrieving reports).
Nedap ONS suits care organisations in the care sector — long-term care, disability care, mental health care and home care — that want to manage client records, care plans, reporting, planning and billing in a single platform. For cure and hospital EHRs such as HiX, or for non-care administration, other systems are a better fit. Not sure whether Nedap ONS suits your situation? In an intake session we'll work out together which integration delivers the most value.
The lead time depends on the scope. A simple integration — for example synchronising client and employee data via the Ons API — is ready sooner than an extensive integration with real-time record data, planning, billing flows and a BI dashboard. Nedap also applies a connection and review process for new integrations. After an intake meeting we'll give you a realistic estimate.
We work with the official Nedap Ons API, described via an OpenAPI specification, with authorisation through OAuth and API credentials. Depending on your situation, we connect client, record, employee and planning endpoints. We build the backend in the stack that suits you — Node.js, Python, PHP or .NET. For reporting we connect to BI tools such as Power BI, and for care technology to home automation integrations. Everything is set up in line with NEN 7510 and the Nedap connection process.
The cost is determined by the complexity of the data flows, the number of systems to be integrated, the required synchronisation frequency and the amount of custom business logic. The Nedap connection and review process, ongoing maintenance, monitoring and support also affect the total investment. We always provide a clear quote after a no-obligation analysis of your situation.
Yes. Client data from Nedap ONS consists of medical and special-category personal data, so security and privacy come first. We apply data minimisation: only the data that is truly needed, with scoped access via OAuth and API credentials. Appfront builds in line with NEN 7510, ISO 27001 and the OWASP ASVS, with encryption in transit and at rest, audit logging and separate permissions per integration. We document the data flows so your record of processing activities stays complete and you can demonstrably comply with the GDPR.
Yes. Appfront regularly takes over the maintenance of existing Nedap ONS integrations, even if they were originally set up by another party. We review the API integrations, authorisation, error handling and data flows, document the current setup and draw up improvement proposals. From then on we can handle changes, extensions and monitoring — including timely rotation of API credentials.
A Nedap integration suits care organisations that use Nedap ONS — particularly in long-term care, disability care, mental health care and home care — and suppliers of supplementary care software and care tech who want to integrate with the EHR. Typical use cases: synchronising client and employee data, feeding a client portal, passing on planning and rosters, exposing billing data and building reports in a BI dashboard. For cure or hospital EHRs, we'll look together at whether another system is a better fit.
Ready to build your Nedap integration?
Tell us which data from Nedap ONS you want to expose and which application, planning tool or BI environment the EHR needs to connect to — we're happy to advise on scope, authorisation and the Nedap connection process. A no-obligation first conversation gives you a clear picture of the possibilities within half an hour.