ASAbsence reporting (SIVI)
HoorayHR to occupational health service via SIVI: sickness dossiers and their phases from HoorayHR to the health service
With an integration between HoorayHR and the occupational health service, every sickness dossier from HoorayHR goes to the health service automatically as a SIVI absence report, with every new sick phase as a change and the recovered phase as a recovery report. Employee and employment data go along beforehand, so the health service already knows the employee at the first sick notification.
What the integration does
Organisations that record absence in HoorayHR then report a sick employee again in the health service portal. HoorayHR lists no health service on its integrations page, so a partial recovery or the recovery date is transferred by hand.
- Every night KoppelHet prepares employees and employments per entity at the health service, with an employee ID instead of the citizen service number.
- A few times a day KoppelHet reads all sickness dossiers and compares them with what has already been reported.
- A new dossier becomes a sick notification; every new sick phase a change of the percentage.
- The recovered phase becomes a recovery report with the recovery date.
- Return and processing messages from the health service show in the KoppelHet platform.
What to watch for with HoorayHR and Arbodienst (SIVI)
- A sickness dossier in HoorayHR consists of phases: reported sick, recovery reported and recovered. A recovery the employee reports themselves still has to be confirmed by a colleague. KoppelHet only sends the recovery report at the recovered phase, so the health service gets no recovery HR has not yet seen.
- HoorayHR's absence endpoints have no filter on date or change. KoppelHet therefore reads all dossiers in every run and uses the dossier's modification date, which also changes when a phase changes, to only send new or adjusted cases to the health service.
- A phase in HoorayHR has a notes field, where employees sometimes describe what is wrong with them. SIVI does have a free text field. KoppelHet leaves it empty and only sends dates, percentages and codes, so no medical information reaches the health service through the integration.
- SIVI asks for the number of contract hours per week on the employment. HoorayHR records the work schedule as minutes per day, separately for even and odd weeks. KoppelHet adds both weeks up and divides by two, so someone who works an extra day every other week appears at the health service with the right average.
- An entity in HoorayHR only has a name, while the health service expects an employer identifier and connection number. KoppelHet records per entity which connection number belongs to it, so employees of two employers in one HoorayHR environment land on the right connection.
- A phase in HoorayHR can start halfway through the day, with an end time for the first day. For the health service the date counts: KoppelHet sends the start date of the first sick phase as the first day of absence, even if the employee worked that morning.
- The HoorayHR API key has an expiry date that the administrator chooses when creating it. If the key expires, the absence flow stops too. KoppelHet warns the administrator well before that date, so sick notifications do not pile up.
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
Does HoorayHR not have its own health service integration?
HoorayHR's integrations page lists no health service. Absence registration is a feature of its own there; the report to the health service runs through this integration.
Does the citizen service number go to the health service?
No. SIVI works with an employee ID; we use the employee number from HoorayHR, provided it is never reissued.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- HoorayHR REST API on api.hoorayhr.io (OpenAPI) with an administrator's API key as Bearer token, with chosen scopes and an expiry date - GET /sick-leave-dossiers (userId, updatedAt, phases) and /sick-leave-phases (status REPORTED_SICK, REPORTED_RECOVERY or RECOVERED, percentage, startDate, startDateEndTime, expectedReturn, calculatedEndDate, notes), without filters; /users (employeeNumber, entityId, birthdate, gender, address, companyStartDate, companyEndDate) and /entities (id, name).
- SIVI absence standard for employers and health services (XML with an XSD per message) - Dienstverbanden (DV-), Werknemersgegevens (WN-) and Verzuimmeldingen (VZ-), with return and processing messages back. Rules include one open absence case per employment, and at percentage zero a recovery date and end reason. Version and transport to be agreed per health service.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in HoorayHR | Field in Arbodienst (SIVI) | Notes |
|---|---|---|
entityId | Werkgeverskenmerk en aansluitnummer | Table per entity |
employeeNumber | Identificatie werknemer | |
birthdate, gender, addressStreet, addressNumber, zipcode, city | Werknemergegevens en Straatadres Nederland | |
companyStartDate, companyEndDate | Dienstverband ingangsdatum en einddatum | |
Werkrooster (minuten per dag, even en oneven weken) | Aantal contracturen per week | |
sick-leave-dossier id | Verzuimgeval identificatie | |
startDate van de eerste fase REPORTED_SICK | Datum eerste verzuimdag | |
percentage per fase | Percentage verzuim | |
expectedReturn | Datum verwacht herstel | |
Fase RECOVERED | Datum hersteld en Einde verzuim J/N |
Related
HoorayHR → Active Directory
HoorayHR to Active Directory integration: domain account from the personnel file
HoorayHR → Microsoft Entra ID
HoorayHR to Entra ID integration: Microsoft 365 account on the start date from HoorayHR
HoorayHR → Google Workspace
HoorayHR to Google Workspace integration: a Google account from the start date
HoorayHR → Okta
HoorayHR to Okta integration: HoorayHR as HR source for Okta users and groups