Custom Nedap integration development
Appfront builds custom integrations with Nedap ONS, the leading EHR in the Netherlands. Via the official Ons API we connect the client record, planning, staff and billing data with your own care application, client portal, scheduling tool or BI dashboard. This way your care team works in one familiar environment, and client and staff data stays up to date everywhere, securely, in line with GDPR and NEN 7510.
What is a Nedap integration?
Nedap ONS is the electronic client record and care administration platform from Nedap, used by over a thousand care organisations in the Netherlands. ONS brings together the client record, care plans, reporting, planning and billing. Many organisations in home care, care for people with disabilities, mental health care and community nursing run their daily care processes 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 planning and rosters on to an external tool, making billing data available to your invoicing system, and retrieving reports for a BI dashboard. The integration fits your actual care and administrative processes.
Appfront builds according to the official Nedap Ons API documentation and the OWASP ASVS security standard. Because medical and special category personal data is involved, we work with data minimisation and scoped access, and go through the Nedap connection and review process so the integration goes live reliably and compliantly.
Client record at the centre
The client record, care plans and reporting remain central in Nedap ONS. The integration exposes exactly the data your application needs, no more, so care providers work with the same up-to-date information wherever they are.
Clients & staff in sync
Client details, care relationships and staff information stay synchronised between ONS and your systems. Changes in the EHR flow through to your application, without double entry and without mismatched records.
Planning & billing
Pass planning and rosters on to external tools and make billing data available to your invoicing system. This way the administrative process aligns seamlessly with the care that has actually been delivered.
Our development process for Nedap integrations
We work to a proven methodology that removes uncertainty early and delivers a stable integration. From an initial analysis of your care processes, record flows and the Nedap connection process, through to go-live and ongoing management, 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 member, planning or billing), which systems to connect and which data is truly 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.
Controlled go-live with data validation and a safety net, followed by ongoing management 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 most often deliver for care organisations and care technology suppliers who want to integrate with Nedap ONS EHR.
Client & file sync
Synchronise client details, care relationships and file information between Nedap ONS and your own care application. Changes flow through without double entry, with scoped access so only the required fields are exposed.
Planning and rostering integration
Pass planning and rosters from ONS to an external scheduling tool, or write planning from your own application back into it. This way care staff work from one up-to-date agenda and staffing stays accurate everywhere.
Declarations & invoicing
Make declaration data from Nedap ONS available to your invoicing or accounting system. Care delivered flows through to financial administration, with traceable data flows and checks for completeness.
Client portal
Powering a client portal or family-carer app with information from the file: appointments, care plan and report access. Clients and their relatives gain secure, controlled access to exactly the data intended for them.
Domotics & care technology
Integrations between ONS and care technology or home automation: connecting signals, sensors and alerts with client data and scheduling. This brings remote care together with the client record in one workable whole.
BI dashboards
Retrieve reports and core data from Nedap ONS for a BI dashboard in, for example, Power BI. Management and quality teams gain insight into output, staffing and care quality, built on reliable source data.
Typical use cases in practice
A Nedap integration looks quite different from one care organisation to the next. We often see a number of recurring patterns, and for each of them we have a working setup that pays close attention to data minimisation, the Nedap onboarding process and the right authorisation.
Residential and home-care organisations
Nursing homes, residential care homes and home care providers that use ONS for records, scheduling and billing. An integration with a proprietary app or client portal keeps client and staff data up to date everywhere, without double data entry. See also our API integrations.
Care for people with disabilities
Disability care organisations with intensive, long-term care relationships. Integrating care plans, reporting and scheduling from ONS with support worker apps and assistive software means support workers can work close to the client with up-to-date record information.
Mental health institutions
Mental health providers that manage client records, treatment plans and reporting in ONS. With strict data minimisation, an integration exposes only the necessary data to treatment applications, questionnaires or a client portal.
Home care
Home care organisations with on-site care and changing routes. Integrating scheduling, client data and reporting from ONS with mobile apps and route planning means staff can safely access the right, up-to-date record information while on the move.
Technology we use
We build Nedap integrations using the official ONS API, described through an OpenAPI specification, combined with the backend stack that suits you. The precise choice depends on the endpoints you need, authorisation and adjacent systems, so that your own team can manage or further develop the integration.
Why choose Appfront for your Nedap integration?
Appfront has extensive experience building API integrations for a wide range of organisations in the Netherlands. We always begin with a thorough analysis of your existing systems and processes. An integration must not only work technically, 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 any future supplier, can understand and manage it. No black box, just 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. This keeps communication short, prevents misunderstandings and speeds up decisions when choices need to be made during development.
See also our wider services around API integrations, middleware, custom software development and web app development.
- Experience with the Nedap ONS API and the EHR data model
- Specialists in integrations between ONS and proprietary care applications
- Familiar with client, record, planning and billing 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
- Comprehensive logging and monitoring from day one
- Clear documentation your team can read and manage
- A fixed point of contact, no account managers passed around
- Ongoing maintenance and proactive further development
Security and privacy in Nedap integrations
Data from Nedap ONS includes medical and special category personal data, the most sensitive category under the GDPR. That is why security comes first in every integration. Appfront works to strict data minimisation: we expose only the fields your application genuinely 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 tightly separated permissions for each integration.
We work through the Nedap onboarding and assessment process, which documents the functional and technical design of the integration with explicit attention to data minimisation. We document the data flows so that your record of processing activities is complete and you can demonstrate compliance with the GDPR. That way, control over client data stays with your care organisation.
More on our security approach: 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 are asked most often about integrations with Nedap ONS.
A Nedap integration is a technical link between Nedap ONS, the electronic client record (EHR) and care administration platform, and another system, such as a bespoke care application, client portal, scheduling tool, billing system or BI dashboard. Data on clients, care records, staff, scheduling and billing is exchanged securely through the official Ons API. 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 social care sector, including residential care for the elderly, care for people with disabilities, mental health care and home care, that want to manage client records, care plans, reporting, scheduling and billing in one platform. For hospital EHRs such as HiX, or for non-care administration, other systems are often a better fit. Not sure whether Nedap ONS suits your situation? During an intake we'll work out together which integration will deliver the most value.
The lead time depends on the scope. A simple integration, such as synchronising client and staff data via the Ons API, takes less time than an extensive integration with real-time record data, passing on scheduling, billing flows and a BI dashboard. Nedap also has an onboarding 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, staff and scheduling endpoints. We build the back end in the stack that suits you, whether Node.js, Python, PHP or .NET. For reporting we connect to BI tools such as Power BI, and for care technology to domotics integrations. Everything is set up in line with NEN 7510 and the Nedap onboarding process.
The cost is driven by the complexity of the data flows, the number of systems to connect, the required synchronisation frequency and the amount of custom business logic. The Nedap onboarding 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 includes medical and special category personal data, so security and privacy come first. We work on the principle of 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 demonstrate GDPR compliance.
Yes. Appfront regularly takes over existing Nedap ONS integrations, including those originally set up by another party. We review the API integrations, authorisation, error handling and data flows, document the current setup and propose improvements. From that point 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 residential care for older people, care for people with disabilities, mental health care and home care, as well as suppliers of complementary care software and healthtech that want to integrate with the EHR. Typical use cases include synchronising client and staff data, feeding a client portal, passing on planning and rosters, making billing data available and building reports in a BI dashboard. For hospital EHRs such as Cure, we will 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 make available, and which application, planning tool or BI environment the EHR should connect to. We are happy to help you think through scope, authorisation and the Nedap onboarding process. A no-obligation first conversation will give you a clear picture of what is possible within half an hour.