Your organisation already has systems for people, operations and incidents. CaseNote's plugins and API integrations can bring agreed information from those systems into your peer support and wellbeing workflows, reducing repeated data entry while keeping each system's purpose clear.
Keep the source system. Connect the work.
An incident recorded in an operational system can become the starting point for tracking exposure and arranging support in CaseNote. A directory can supply staff account details and organisational teams. Your team agrees which system owns each field, which records should come across, and what should happen when the source changes.
The integration is scoped around your workflow and the source API. We confirm what is possible before committing to a connection, including permissions, data availability and any source-system licensing requirements.
Plugins add the capabilities your organisation needs
A plugin is an integration package that extends CaseNote. Depending on its purpose, it can add a scheduled import, an administration screen, settings, a protected lookup or a connection to another service. Plugins are made available per organisation and enabled through configuration, so your deployment uses the integrations agreed for your program.
For example, the Microsoft Entra ID directory connector can create draft staff accounts, update names, add departments as teams and remove access for disabled or deleted users. An administrator reviews and invites new accounts before they can sign in. Connecting a directory is a separate decision from configuring single sign-on.
API ingestion: from source records to useful information
A connector reads records from an agreed external API. It maps source fields to supported CaseNote records, validates the input and applies changes through CaseNote's normal write paths. Imports can run on a schedule, with an administrator able to start a run and review its status.
- Agree the scope. Identify the source, the records needed and who can authorise access.
- Map the fields. Define identifiers, matching rules and which system owns each value.
- Configure the connection. Set up the agreed API permissions, credentials and import schedule.
- Validate and record. Check incoming data, apply supported changes and audit the writes.
- Review the result. Inspect run status, record counts and failure codes, then resolve source or mapping issues.
What can be brought into CaseNote?
- Staff accounts: create draft accounts, maintain names and deactivate linked accounts when access should end.
- Teams and zones: maintain the organisational reference data used in the program.
- Incidents: bring in agreed incident identifiers, dates, zones, locations and descriptions.
- Member attendance: link existing members to incidents using agreed member identifiers, supporting exposure tracking.
These are the connector framework's current supported record types. Each source needs its own mapping and configuration. Additional data types or workflows are assessed and delivered as a scoped extension.
Keep integration access specific
Data connectors declare the external hosts they need to contact and the credentials they use. Network requests use controlled HTTPS connections with request limits. Incoming records are validated before writing, and business changes and their audit records are committed together. Run monitoring uses counts and failure codes rather than source record contents.
Imported information remains subject to CaseNote's access controls. An operational import does not grant the source system access to clinical notes. The application and its databases are hosted in Australia; the location and data handling of an external service are assessed separately as part of the integration. Read about CaseNote's privacy and security controls.
Start with the workflow you want to connect
Bring your source-system API documentation, a field list or synthetic sample, the desired update frequency and the people who manage that system. We will work through record matching, permissions, error handling and acceptance checks with your team before activation. Use synthetic examples for an initial discussion rather than personal or clinical records.