Skip to main content

2025.6.1 release notes

This release adds rich text formatting for audits and enhanced DataHub integration with Access People Planner.

F
Written by Florin Brasovan
Updated yesterday

Overview

This release introduces professional rich text formatting for audit templates in the Access Care Compliance module. Audit administrators can now create well-formatted templates with emphasis, lists, and colours in audit descriptions and questions. All changes maintain full compatibility with existing plain text templates.

We've also added integration flexibility with the Access People Planner product

What’s new

1. Rich Text Formatting for Audit Templates

Where it works:

Audit Type Descriptions

  • Path: Admin → Manage Audits → Add audit or Edit an existing audit

Audit Questions

  • Path: Admin → Manage Audits → Add audit or Edit an existing audit → Add/Edit Question

Formatting options available:

  • Bold, italic, and underline text

  • Text colours (foreground and background)

  • Bullet and numbered lists

  • Emoticons for visual emphasis

Key benefits:

  • Create professional, well-structured audit

  • Emphasise critical information using formatting

  • Structure complex questions with lists

  • Improve comprehension and reduce errors

Security:

  • Automatic XSS protection on all rich text content

  • Existing plain text templates continue to work

  • Mix formatted and plain text in same template

2. Enhanced DataHub Integration Configuration

New configuration option: "Datahub Integration Use Only DatahubId As Identifier" for integration with the Access People Planner product.

Access: This setting is only accessible by Provider Support users through Application Settings under Admin

Current Behaviour (Default/When Disabled)

How DataHub matching currently works:

  1. System first attempts to match records using DatahubId

  2. If no match is found by DatahubId, system then attempts to match using:

    • EmployeeIdentifier (for Employees)

    • UniqueIdentifier (for Service Users)

  3. This two-step matching process has been the standard behaviour in ACC for DataHub integration

This default behaviour works well for most organisations and will continue unchanged unless the new option is enabled.

New Behaviour (When Enabled)

What changes when enabled:

Record Matching:

  • Uses DatahubId exclusively for matching records

  • Ignores EmployeeIdentifier/UniqueIdentifier for matching purposes

  • Creates new records if not matched by DatahubId

First Import:

  • Sets EmployeeIdentifier/UniqueIdentifier to the DatahubId value

Subsequent Imports:

  • Preserves manually modified identifiers by users via UI

  • Only updates records matched by DatahubId

Why This Matters

The current default behaviour works well for most organisations. However, when local identifiers (EmployeeIdentifier/UniqueIdentifier) diverge from external system values, the two-step matching process can sometimes create duplicate records.

The new configuration option provides an alternative matching strategy for organisations that need stricter control over record matching using DataHub IDs exclusively.

Key benefits:

· Accommodate varied record-keeping practices

· Prevent duplicate records when identifiers diverge

· Maintain data integrity during transfers

· Greater control without code changes

· Choose the matching strategy that fits your workflow

To enable this setting: Please contact Provider Support if you require this configuration for your organisation.

How this version will be made available

This update will be automatically rolled out to all customers on 4th of December.

Related Articles
2025.1 release notes
2025.3.1 release notes
2025.5 release notes
2025.6 release notes
Did this answer your question?