1.12.2

New Features

Adding new endpoints to support internal functionality.

1.12.1

This release contains internal changes only and has no external impact

1.13.0-pre

Bug Fixes

GET /time-off/adjustments no longer returns a server error when paginating (e.g. ?limit=100&page=0) for accounts that have no time-off adjustments; it now returns an empty result with the correct total count.
PATCH /users no longer errors if regions being assigned to a user are already assigned

1.12.0

New Features

We are now able to block/disable outbound webhooks. If your webhooks are blocked, then these will appear as disabled and you can contact support to turn these on again.

1.11.0

Deprecations

The integer format for the roleId parameter on GET /users/roles/{roleId} and PATCH /users/roles/{roleId} is now deprecated. When the single_role_assignment feature flag is enabled, use UUID identifiers instead.
Bug Fixes
Fixes an issue where some appointment instance creation events issued when a note is added via the Empower mobile app were not correctly being passed through to webhooks

1.10.3

This release contains internal changes only and has no external impact

1.10.2

This release contains internal changes only and has no external impact

1.10.1

This release contains internal changes only and has no external impact

1.10.0

New Features

For clients, the emergencyRating can now be modified.
Improvements
We have detailed that this API is for our customers, not for general consumption.
Deprecations
Since deleting time off types without the time off module being enable cannot be completed, the 405 Method Not Allowed will become a 404 Not Found.
Bug Fixes
Correcting finance rate selection for Payment/Invoice Groups supporting split rates. Listing rates endpoints now return multiple rates in the scenario where a group supporting split rates is applied to an appointment where the actual times recorded crosses multiple rates.

1.9.1

This release contains internal changes only and has no external impact

New Features

For clients, the emergencyRating can now be modified.
Improvements
We have detailed that this API is for our customers, not for general consumption.
Deprecations
Since deleting time off types without the time off module being enable cannot be completed, the 405 Method Not Allowed will become a 404 Not Found.
Bug Fixes
Correcting finance rate selection for Payment/Invoice Groups supporting split rates. Listing rates endpoints now return multiple rates in the scenario where a group supporting split rates is applied to an appointment where the actual times recorded crosses multiple rates.
PATCH /medication-administrations/{id}: Fixed a bug where edited administrations were storing the outcome's base identifier instead of its revision identifier. As a result, subsequent GET requests for any PATCH-edited administration were joining on the wrong value and could return a null or incorrect outcome and outcomeVersion. Note: administrations edited before this fix retain the incorrect stored value and will continue to return incorrect outcome data until the underlying records are corrected.
PATCH /medication-administrations/{id} and POST /medication-administrations: Fixed a bug in duplicate detection where, if the medication had been revised since an administration was recorded, a genuinely duplicate submission could bypass the 409 conflict check. Genuine duplicates will now correctly return 409.
PATCH /medication-administrations/{id}: Fixed a bug where the medication version stored on edited administrations was being overwritten with the medication's current live version rather than preserving the version on the record.

1.9.0

Improvements

Internal security updates.
The carer status warning context now includes a carerUuid field identifying the carer.
Increase the stability of PDF conversion
Bug Fixes
Fix activity log wording when changing carer slots on appointments.

1.8.0

Improvements

Improvements to validity of the OpenAPI Spec.

Bug fixes

Adds validation to the POST and PATCH medication-administrations endpoints to return a 400 Bad Request if either outcome or outcomeVersion are set to a value of 0. 0 is not a valid value and currently the API erroneously returns a 500 Internal Server Error - this change ensures that the correct HTTP status code is returned instead to provide more meaningful feedback to the consumer

1.7.1

Bug Fixes

Prevent duplicate Medication Administrations being recorded

1.7.0

New Features

Added optional roleType field to role responses with possible values: carer, admin, carer_admin, client. When creating a parent role via POST /users/role, you can now specify a roleType to determine the role's base permissions. The roleType field is only included in responses when set (omitted when null for backwards compatibility)
Role UUIDs can be used as a filter on the /users endpoint

Bug Fixes

The DELETE: /medications/{medicationUuid} endpoint now returns a 409 Conflict response with the message "Cannot delete a medication that has administrations recorded against it" if the medication has any administration records. Previously, the endpoint returned 204 No Content and deleted the medication even when administrations existed, which orphaned the administration data.
- Impact to API consumers:
  - Any workflow that deletes medications which have been administered will now receive a 409 Conflict instead of 204 No Content.
  - Medications with no administrations are unaffected and will continue to return 204 No Content as before.

Improvements

Adding Production and Pre-production server urls to API documentation
Adding Rate Limits overview to API documentation
When selecting a single finance rate and multiple rates are tied with the same top score, the system now resolves the tie by matching against past experience.
Improved supply chain security.

1.6.1

Bug Fixes

Fixed an issue where paginating through GET /finance/timesheets could return duplicate records or skip records when multiple timesheets shared the same start date. Pagination results are now deterministic regardless of page size.