Docman Connect 266 - February 2026

Thomas Burton Updated by Thomas Burton

Docman Connect Release 266 

This page contains details of new and amended functionality included in the software update known as Release 266. 

Return Metadata Items For A Single Document

What have we done?

We have added a new API that lets you get all metadata for a single document using its Document GUID. This works for all documents, including those resent via the front end.

Why have we done this?

This makes it easier for the system sending the documents to identify and handle rejected items automatically.

How will you benefit?

You can quickly find, and process rejected or resent documents without manual checking, saving time and reducing errors.

Details of the change

· New API endpoint returns all metadata for a document using its Document GUID.

· Works with rejected and resent documents.

· Metadata includes patient and destination details for better tracking and processing.

Improved Performance and Workflow Optimisation

What have we done?

We have made ongoing improvements to the system’s performance.

Why have we done this?

We have done this to improve overall performance and make the system easier to use.

How will you benefit?

You will benefit from smoother and more efficient day-to-day tasks.

Details of the change

This update includes general performance enhancements and workflow updates across the system..

Improvements to our NHS Mail Collection

What have we done?

We’ve improved how Docman collects and processes emails from NHS Mail, making the overall experience smoother and more reliable.

Why have we done this?

In the past, issues with individual emails could sometimes slow things down or cause delays. This update helps Docman handle emails more effectively as they arrive.

How will you benefit?

Documents are now processed more reliably, with fewer delays or interruptions. This means a more stable document flow and quicker access to the information your practice needs.

Details of the change

Change to NHS Mail processing

Transferring SNOMED Data via Docman to Improve Coding Quality

We’re currently piloting this feature with selective sites. Once we’ve gathered feedback, we’ll roll it out more widely.

What have we done?

We’ve added a new Onset Date field to our API. When SNOMED-coded information is sent into Docman, this date will automatically appear as the Event Date on the Task screen in Docman 10.

Why have we done this?

Patient care relies on accurate information in GP records. Important details like diagnoses often come through hospital letters and discharge summaries, but they can be hard to spot and time-consuming to code. Because of this, and differences in time, training, and resources across practices, important clinical information isn’t always added to GP records. Evidence shows that up to half of key clinical details can be missed, which means some patients don’t always get the follow-up care they need.

How will you benefit?

This makes filing and coding faster and simpler. The correct date is already filled in, reducing manual effort and the risk of errors. Most importantly, it helps ensure important clinical information is captured properly, supporting better ongoing care for patients.

Details of the change

A new Onset Date field has been added to the API for SNOMED-coded data.

· When SNOMED-coded information is transferred into Docman 10, the Onset Date is automatically populated as the Event Date on the Task screen.

· This works for clinical information coming from hospital letters and discharge summaries.

· The feature is currently being piloted with selective sites, with plans for wider rollout following feedbac

How did we do?

Docman Connect 261 - November 2025

Contact