Breadcrumbs

Sensio 365 Integration

This article describes the eADM integration with Sensio 365, a platform for managing welfare technology devices and patient alarms in care homes. The integration handles user provisioning and role assignments between eADM and Sensio 365, and serves as the reference implementation for the eADM third-party integration framework.

Overview

Sensio 365 is used by Norwegian municipalities and care organisations to manage welfare technology devices, including patient alarms, in nursing homes and similar facilities. The eADM–Sensio 365 integration automates joiner, mover, and leaver workflows for staff accounts in Sensio 365, driven by role assignments in eADM.

The integration connects to the Sensio Partner API and synchronises users, site memberships, and group memberships. Because Sensio 365 uses a site-and-group model for access control, eADM system roles map directly to Sensio groups within specific sites.

Architecture

The integration is built on the eADM third-party integration framework, which provides:

  • A standardised reference data format for import and export between eADM and external systems

  • A mechanism for initiating an external preprocessor or postprocessor via the eADM client and sync cycle

  • Callback endpoints for centralised log entries and error reporting in eADM

The integration component runs server-side in the eADM environment. API communication with Sensio 365 uses IP whitelisting; no VPN tunnel is required.

Data Model

The table below describes how Sensio 365 objects map to eADM concepts.

Sensio object

eADM representation

Notes

Site

Reference only

Sites cannot be created or modified via the API. Used to scope group memberships.

Group

System role

Groups are imported from Sensio and synced as system roles. Groups cannot be created or deleted via the API. Naming convention: [SiteName] - [GroupName].

Employee

eADM user

Users cannot be deleted via the API; they can only be added to or removed from sites and groups.

Scope

In scope

  • Importing system roles from Sensio sites and groups

  • Creating and updating user accounts in Sensio 365 according to the sync template

  • Adding users to sites

  • Removing users from sites

  • Adding users to groups

  • Removing users from groups

  • User matching by email address, username, national identity number (pid), or externalID

  • API throttling handling in accordance with Sensio API limits

  • Configurable group and site exclusions in the syncstep configuration

  • Full server-side and client-side logging, including merge reports and object history

  • Graceful handling of connectivity issues

Out of scope

  • Deleting users in Sensio 365 (not supported by the Sensio API)

  • Creating or deleting groups in Sensio 365 (not supported by the Sensio API)

  • Creating, updating, or deleting sites in Sensio 365 (not supported by the Sensio API)

  • Initial population of existing users to roles prior to go-live

Configuration

The syncstep configuration for the Sensio 365 integration accepts the following parameters.

Parameter

Description

API credentials

Client credentials for authenticating against the Sensio Partner API.

API Base URL

Base URL for the Sensio Partner API endpoint.

API Token URL

Token endpoint URL for OAuth authentication.

Site IDs to exclude

Comma-separated list of Sensio site IDs to exclude from synchronisation.

Group IDs to exclude

Comma-separated list of Sensio group IDs to exclude from synchronisation.

OverrideMergeAttribute

Defines which attribute to use when matching eADM users to Sensio employees. Configured in the sync template.

Last updated: