Custom Caress integration with your own care application
Appfront builds the integration between Caress and the software your staff actually work with. We retrieve clients, care plans and assessments, translate the codes into your own fields, write reports and hours delivered back, and show for each message whether it arrived. Rejected lines end up in a work queue that your administrator resolves themselves. So nobody has to type the same client data in twice any more.
What is a Caress integration with your own care application?
Caress, also known as mijnCaress, is the electronic client record from PinkRoccade Care that many organisations in elderly care and disability care use. A Caress integration is the link between that record and your other software: planning, rosters, financial administration, a care app or a custom portal. The integration retrieves clients, assessments, care plans and staff, and writes reports, appointments and hours delivered back to the record.
Without an integration, things go wrong at the handover. A new client is created in the record, but the planner enters the same name, location and assessment again in the planning board, and the finance team turns it into a third entry. If the assessment is later increased, only the record knows about it. The result is a month-end close that nobody can explain.
We build custom because your landscape isn't set up like anyone else's. The codes for care types, locations and teams are configured differently at your organisation than at your neighbour's, and the rules about who may see what differ per organisation. We follow your code tables, your team structure and your agreements with the care office. A standard connector doesn't know any of that and delivers fields that mean nothing to you.
Retrieve clients and assessments
The integration reads clients, assessments, care decisions and care plans from Caress and keeps them up to date in your own software, including changes such as moves, assessment changes and discharges.
Write back reports and hours
What staff record in your app or portal goes back to the record: reports, hours delivered, appointments and alerts, with a check beforehand so nothing is rejected because of a missing field.
Translation table and work queue
We translate codes for care type, location and team into your own structure. Anything that fails the check lands in a work queue where your administrator corrects the line and resubmits it.
How we build your Caress integration with your own care application
We start with a single client who is in Caress today and needs to show up in your planning and billing tomorrow.
Together we go through which data comes from Caress, which data has to go back, who owns which field and where people are currently retyping things by hand. This gives you a short list of messages.
We set up clients, locations, teams, staff and care types, and record for each code what it means in your own software. You then manage that table yourself, without us.
We build the screens your people work in: the work queue with rejected lines, the overview per client and the check on hours that have been logged but not billed.
We take the integration live in a test environment, run it alongside a real period, compare the results with the client record and then take over maintenance and alerts.
What a Caress integration with your own care application actually does
The components below appear in almost every Caress integration. Which ones you need depends on which systems are involved and whether you also write data back to the client record.
Client synchronisation
Clients, addresses, care assessments and care plans come in automatically and stay up to date, including admission, moves and discharge, without anyone retyping anything.
Writing reports back
Reports and alerts from your app or portal go to the client record, with source and timestamp, so the care worker finds everything in one place.
Time registration and billing
Hours delivered are linked to the right care assessment and funding decision, so the month-end close is accurate and hours without coverage become visible in advance.
Mapping table for codes
We translate care types, locations, teams and roles into your own structure. You manage the table yourself and add new codes without a new release.
Work queue and error handling
Every message that fails validation gets a readable notification and a place in the work queue. Fixed and resubmitted, without us.
Logging per client
For each client you can see which message was sent when, who changed it and what the record reported back. Useful for questions from the client council or an audit.
Who we build a Caress integration with your own care application for
The software is intended for care organisations that use Caress as their client record and also run their own software, scheduling and billing alongside it.
Elderly care and nursing homes
Many locations, plenty of changes in care assessments and admissions. Synchronising clients and care assessments is the core here, so that scheduling and the care record stay aligned.
Disability care
Long-running care pathways with several funding types per client. Translating care types and funding decisions into your own structure does most of the work here.
Home care and community nursing
Staff register on the move. Writing reports and hours delivered back from the app to the record prevents the evening from ending in paperwork.
Care groups with multiple systems
Record, scheduling and payroll are separate. The work queue and logging per client matter here, because otherwise errors only surface at the close.
Technology and integrations
This page is about integrations with Caress and the systems around it. If you also work with other care software, see a Nedap integration, a VECOZO integration or a care app, and NEN 7510 compliant software for the requirements on management and access. You can read about our approach on building custom software.
Why Appfront for your Caress integration with your own care application?
An integration is only as good as the day something goes wrong. That is what we build for: readable notifications, a work queue and an administrator who can fix it themselves.
You don't need to call us for a new code
You manage care types, locations and teams in a table in the software itself. Adding a new location or funding type is something your administrator does, not a request to us.
Every message can be traced
For each client and each period, you can see what was sent, what the record reported back and who changed something. When an auditor or regulator asks questions, that makes the difference.
Run alongside first, then switch
We let the integration run alongside your current way of working for a period and compare the results line by line with the record, before anyone throws away their Excel file.
Security and privacy for a Caress integration with your own care application
This integration contains client data, care assessments, reports and sometimes medical notes. We set up access per role: a planner sees different fields from an administrator or a practitioner. Every view and change is logged by name. We comply with the requirements of the GDPR and NEN 7510 and define for each type of data how long it is retained and when it is purged.
The software runs in a European data centre, with encrypted storage and daily backups. Integrations with Caress, planning and the financial administration use their own keys, which can be revoked per integration.
Frequently asked questions about a Caress integration with your own care application
Questions healthcare organisations ask before getting started.
The integration retrieves clients, care assessments, care plans and staff from Caress and places them in your own software. What your people record there, such as reports, appointments and hours delivered, goes back to the record. For each message you can see whether it arrived, and rejected lines go into a work queue.
Yes, provided your licence and configuration allow it. We agree with your supplier which data may be written back and by which route, and we build in the checks up front: missing fields and incorrect codes are stopped before the message is sent, so you are not left fixing individual rejections afterwards.
The message stays in place with a readable notice attached, not a technical error code. Your administrator sees in the work queue which client it concerns and what is missing, and can correct the line and resubmit it. If that doesn't work, a notification goes to our team.
No. We record your care types, locations, teams and roles in a mapping table, alongside what they mean in your own software. If something changes in how the record is configured, you adjust the table yourself. Adding a new code does not require a new release.
We let the integration run alongside your current way of working for a period and compare the results with the record for each client and each hours line. We investigate any differences before you switch over. Afterwards, a control screen remains in place that shows discrepancies between the record and your own software.
That's up to you. Many organisations take on functional management themselves, keeping the mapping table and the work queue in their own hands, and leave technical management and notifications to us. You receive documentation for every message and access to the logging, so you are not dependent on one person.
Check that first. For standard flows such as referrals, data exchange with other care providers or a certified planning solution, integrations exist, and these are almost always the better choice. Custom work makes sense when you have your own app, portal or administration that doesn't fit into them, or use codes that the standard message doesn't recognise.
Want to enter client data only once?
Tell us which version of Caress you use, which systems currently sit alongside it and where your people retype data every day. We'll show you what the client synchronisation, the translation table and the work queue for rejected messages look like.