Docman GP 259 - October 2025

Thomas Burton Updated by Thomas Burton

Release 259 Release Notes - October 2025

This page contains details of new and amended functionality included in the software update scheduled for 12th to 20th October 2025, known as Release 259.

API Token Expiry in Minutes

What have we done?

(Internal Reference D10-13599)

API token expiry is currently held in days duration, the duration has been amended to be held in minutes.

Why have we done this?

To enable token expiry to be more precisely managed, in line with NHS Digital standards.

How will you benefit?

There will be no change at this time, as all “day” values will be converted to their “minutes” equivalent.

Details of the change

The screen and database have been changed to manage duration in minutes, not days.

Scotland DFCT001327: EMIS Error message appears when using DM10 Vision linked account

What have we done?

(Internal Reference D10-14312)

Fixed a bug

Why have we done this?

While using Vision (InPS) Docman 10 account, EMIS error messages appear when uploading a document to Docman 10 and viewing document history.

How will you benefit?

The Audit history shows irrelevant information for the document for NSS.

Details of the change

Logic to validate EMIS was missing.

Coding Search Screen Enhancement

What have we done?

(Internal Reference D10-13575)

The coding search will use the text at the bottom of the search screen in the code browser.

Why have we done this?

To make the code search more joined up.

How will you benefit?

Searching will be quicker and easier to use.

Details of the change

When the Clinical code search was used (value input in “Search clinical code browser” field, this would open the Clinical Code Browser, but require the user to re-input the search term. Now the search term will be taken from the “Search clinical code browser” field into the Clinical Code Browser and present the appropriate search results immediately.

Client Side Exception Message Handling

What have we done?

(Internal Reference D10-14014) A client side error is being reported in the exception logs. The error is informational, and has no impact on end user experience. This is to resolve the exception instances.

Why have we done this?

To reduce exceptions in the log for better clarity of potentially “real” issues.

How will you benefit?

There will be no change to end users.

Details of the change

Fixed logic to remove the exception occurrence

Prevent Sites Removing/Deactivating Last System Administrator

What have we done?

(Internal Reference D10-13987)

Prevented sites from deleting or deactivating a user as a System Administrator if that user is the last System Administrator for the site, and a message to be shown with the reason.

Note: This is the same functionality as that already in place to prevent deletion/deactivation of the last Privacy Officer

Why have we done this?

All Sites should have a System Administrator, to fulfil specific functions in the application, otherwise a clinical risk is present.

How will you benefit?

Sites will not be left with no System Administrators

Details of the change

If a Site attempts to remove a user or deactivate a user who is the last System Administrator for that site, this warning message will be shown and the action to delete/deactivate will not be allowed.

NHS England SNOMED International Description Length Change

What have we done?

(Internal Reference D10-13404)

The SNOMED International database table has been updated to facilitate the change in maximum length of Fully Specified Name and Synonym Description fields from 255 to 4096 characters.

Why have we done this?

NHS England are extending the length of the Fully Specified Name and Synonym Description fields from 255 to 4096 characters in April 2026 for SNOMED International.

How will you benefit?

There will be no change to end users.

Details of the change

Database updated to accommodate the new field lengths.

Error Log Exception Handling

What have we done?

(Internal Reference D10-14834)

An information error is being reported in the exception logs. The error is informational, and has no impact on end user experience. This is to resolve the exception

Why have we done this?

To reduce exceptions in the log for better clarity of potentially “real” issues

How will you benefit?

There will be no change to end users

Details of the change

Fixed logic to remove the exception occurrence

How did we do?

Docman GP 257 - September 2025

Contact