ASAbsence reporting (SIVI)
Oracle HCM to the occupational health service via SIVI: sickness from Absence Management without portal work
With an integration between Oracle HCM Cloud and the occupational health service, sickness reports, changes and recovery of employees of the Dutch legal employer go from Absence Management to the health service automatically, as a SIVI message. An open-ended sickness absence without an end date stays an ongoing absence case at the health service until HR enters the end date in Oracle.
What the integration does
Organisations that use Oracle HCM Cloud worldwide and have an occupational health service for their Dutch employees often copy a sickness report from Absence Management into the health service portal by hand. A recovery or a withdrawal in Oracle then only reaches the health service when someone in the Netherlands remembers.
- A new assignment at the Dutch legal employer goes to the health service as employment and employee, so it already knows the employee at the first sickness report.
- Employee, manager or HR records sickness in Oracle, without an end date where needed.
- KoppelHet fetches changed absences, only takes approved sickness of the Dutch legal employer and sends the sickness report to the health service.
- A partial return to work goes as a change with the new percentage; when HR enters the end date, the recovery report follows.
- The health service's return notification shows in the KoppelHet platform. A rejected report or a withdrawn absence becomes a task for HR in the Netherlands.
What to watch for with Oracle HCM Cloud and Arbodienst (SIVI)
- Every absence in Oracle belongs to a legal employer, and that field is mandatory. KoppelHet filters on it, so only sickness of the Dutch employer reaches the health service and absence of colleagues in other countries stays in Oracle.
- Oracle has an absence status, such as submitted or withdrawn, plus an approval status. The health service only receives a sickness report after approval. If someone withdraws an absence that was already reported, HR gets a task instead of a silent withdrawal at the health service.
- An absence in Oracle can be open-ended, submitted without an end date. That is how long-term absence starts. KoppelHet then keeps the absence case open and only sends the recovery report once the end date is in Oracle, with the next day as the recovery date.
- Oracle records a separate duration for the first and the last day of each absence, in days or hours. Someone who goes home sick halfway through the day therefore gets a first day of absence with the right portion at the health service, and one hundred percent on the following days.
- With a linkage rule Oracle can link a new sickness to an earlier absence. KoppelHet still sends a linked relapse as its own sickness report with its own first day; how the health service counts combined absence is agreed with the health service at the start.
- An absence in Oracle can have a reason and comments, up to two thousand characters. These can contain a complaint or diagnosis, so the integration does not read those fields. The health service only gets dates, percentage and a cause code without a diagnosis.
- Someone with two assignments at the Dutch employer has one person number in Oracle. That becomes the employee number at the health service, and each assignment its own employment, so sickness belongs to the right contract.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Do we need a separate sickness type for the Netherlands in Oracle?
Not necessarily. The integration already filters on the Dutch legal employer. It must be clear which absence types are sickness, and a field is added for the safety net.
Do the reason and comments from Oracle go along?
No. Those fields stay in Oracle, because they can contain medical information.
Can the same integration also report to our absence insurer?
That can be added later as an extension. SIVI has its own message for the insurer; the Oracle side stays the same.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- Oracle HCM Cloud through the absences REST resource (/hcmRestApi/resources/11.13.18.05/absences) with fields including personNumber, assignmentNumber, legalEntityId, absenceTypeId, absenceStatusCd, approvalStatusCd, openEndedFlag, startDate, endDate, startDateDuration, endDateDuration, duration, unitOfMeasure and lastUpdateDate. Child resource linkedAbsences for linked absences. Employments through the employee Atom feeds (newhire, termination) and the workers resource.
- The SIVI messages Employments, Employee data and Absence reports go to the health service, with processing code new, changed or correction and Vangnet J/N (mandatory). Transport under the SIVI 2025 interface specification (REST endpoint at the health service, XML in Base64 inside JSON, OAuth 2.0); the health service sends a return and processing message back.
- An integration user in Oracle with read access to absences and workers of the Dutch legal employer.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in Oracle HCM Cloud | Field in Arbodienst (SIVI) | Notes |
|---|---|---|
personNumber | Identificatie werknemer | No citizen service number |
assignmentNumber | Identificatie dienstverband | |
personAbsenceEntryId | Verzuimgeval identificatie | |
startDate | Datum eerste verzuimdag | |
duration, startDateDuration en endDateDuration ten opzichte van het rooster | Percentage verzuim | Calculated by KoppelHet |
endDate + 1 dag | Datum hersteld en Einde verzuim J/N | Empty while openEndedFlag is true |
Afdeling van de assignment op de eerste ziektedag | Organisatie-eenheid, code | |
Descriptive flexfield voor Nederland | Vangnet J/N | Oracle has no safety net concept |
Related
Ashby → Oracle HCM Cloud
Ashby to Oracle HCM integration: an accepted offer on an opening becomes a pending worker
Bullhorn → Oracle HCM Cloud
Bullhorn to Oracle HCM integration: an approved placement of an employee becomes a pending worker
Carerix → Oracle HCM Cloud
Carerix to Oracle HCM integration: successful placement as a pending worker in Oracle HCM Cloud
Greenhouse → Oracle HCM Cloud
Greenhouse to Oracle HCM integration: accepted offer as a pending worker in Oracle HCM Cloud