Docman GP 266 - February 2026
Docman GP Release 266
This page contains details of new and amended functionality included in the software update known as Release 266.
Update JavaScript Libraries in Docman Apps
What have we done?
(Internal Reference D10-13709)
Updated Java Script libraries in the Docman Apps dashboard.
Why have we done this?
To comply with security requirements
How will you benefit?
There will be no change to end users
Details of the change
Relevant JS libraries updated
Clear DTA logs at DTA Start Up
What have we done?
(Internal Reference D10-13913)
When DTA starts on a local machine, clear logs remaining from previous session/s
Why have we done this?
For security & performance reasons. DTA logs are already cleared on each release
How will you benefit?
There will be no change to end users
Details of the change
DTA logs are cleared when DTA is started
Unrestricted File Upload in Document Library
What have we done?
(Internal Reference D10-15173)
Enforced white list control of document types being uploaded
Why have we done this?
To remediate a HIGH penetration testing issue raised in Nov 2025
How will you benefit?
Security improvement, no change to end user
Details of the change
Files which are not in the approved list of file types – file extension and file preamble will be verified – will not be able to be uploaded in Docman
Security Patch: Improper Access Control: Out of Office
What have we done?
(Internal Reference D10-13381)
Updated the software to prevent the interception and update of Out of Office
URLs. This was only possible via specific interception methodologies.
Why have we done this?
Penetration testing found a potential compromise where an out of office message could be intercepted, using specific methodologies, and changed from that user to another user.
How will you benefit?
Improved security
Details of the change
Software change to remove the vulnerability
DM10 | "Start Clinical Coding immediately after filing" tickbox intermittingly not working
What have we done?
(Internal Reference D10-15029)
Fixed a defect report by one user – intermittent occurrence
Why have we done this?
When the “Start Clinical Coding immediately after filing” tick box was checked (on), there was an intermittent issue where it was not recognised and coding task did not get initiated.
How will you benefit?
Clinical coding should be initiated every time that the “Start Clinical Coding immediately after filing” tick box is checked (on)
Details of the change
Added some extra checking around the tick box to ensure the value is picked up
Multi Factor Authentication – Information Only
What have we done?
(Internal Reference D10-13387) Deployed in Release 263 to PS2 and PS3 sites
Introduction of Multi Factor Authentication using OneAdvanced Identity integration into the Docman platform. This allows organizations to enhance security via additional authentication through OneAdvanced's identity provider. MFA is not yet “switched on”, so sites cannot currently activate it after this release.
Why have we done this?
To adhere to ICO guidelines which state MFA should be used to protect sensitive information and data.
How will you benefit?
Each site will have the ability to choose to activate MFA for their user base to provide additional level of security and compliance
Details of the change
Please refer to our HelpDocs page for further information on OneAdvanced Identity, this has links to email and authenticator app instructions, plus FAQs.
Full screen flows will be provided when the feature is activated.
Retain Organisation Code on Login Page
What have we done?
(Internal Reference D10-15243)
Updated the Login screen following MFA activation to retain the Organisation code. Organisation code was always retained/pre-populated prior to MFA.
Why have we done this?
The MFA changes in Rel 263 had removed the pre-population of the Organisation Code on the log in screen. This has been reinstated.
How will you benefit?
Organisation code will not need to be re-typed at every log in
DDE Tool Update - DDE Tool Documents and Attachments and Markup Data
What have we done?
(Internal Reference D10-13595/D10-14493 and D10-14963/D10-11591)
The DDE tool has been updated to return the latest version of a document with
any annotation, redaction or other mark-up baked into the document image.
• Annotation types included are Rectangle, Highlight, Ellipse, Stamp, Text, Line, Redact and Erase
The tool has also been updated to run with controlled batch sizes, so that it runs efficiently and without failure
Why have we done this?
To comply with NHS England Data Migration Standards
How will you benefit?
There is no change to end users, this tool is used by One Advanced Support team
Details of the change
DDE tool updates
DDE Tool: Include User Name and Secured Document Status in DDE Extract
What have we done?
(Internal Reference D10-15271)
Updated the DDE tool to return the User name and Secured document status in the Document extract, and the User name in the Audit extract
Why have we done this?
To conform with the NHS data Migration Standard
How will you benefit?
There is no change to end users, this tool is used by One Advanced Services team
Details of the change
Update the DDE tool to include the Docman user name (as well as the Docman User ID) and include the secured document status in the relevant extracts.
Scotland Defect 1378: Docman 10 - DM7 to DM10 Migration - Custom Actions & Comments not copying over
What have we done?
(Internal Reference D10-15129 & D10-15203)
Ensured that Custom Actions and Comments are moved across when migrating from DM7 to DM10
Why have we done this?
Resolve defect with migration
How will you benefit?
Custom actions and comments will be copied when moving from DM7 to DM10
Details of the change
In Settings >> Tasks, “comments” and “task templates” will include comment
and actions from DM7
• Pre-defined messages and replies can be seen under Settings> Tasks > Task
templates and Comments.
• Pre-defined messages and replies can also be seen under Click on any task >
Can be seen under quick steps
Scotland GP2GP Logging for Export Timing
What have we done?
(Internal Reference D10-15151)
Added logging at all steps in the GP2GP process
Why have we done this?
To verify how long each step takes so that we can pinpoint any slow steps
How will you benefit?
Potential to improve speed if steps are identified and can be changed
Details of the change
Logging included
Scotland Defect 1410: GP2GP Export Button Text Change
What have we done?
(Internal Reference D10-15134)
Changed button name from “GPToGP Export Patient“ to “GP2GP Export”
Why have we done this?
Request from NSS
How will you benefit?
Button name updated as requested – no change to function
Details of the change
Button name changed
Scotland Defect 1404: Unable to link a Docman 10 user to a Vision user in LAN
What have we done?
(Internal Reference D10-15135)
Changed DM10 to use Vision 10 when linking user/s
Why have we done this?
To resolve a reported defect for Scotland
How will you benefit?
Vision LAN Clinical System can be linked to DM10 user
Details of the change
Clinical System logic now includes Vision LAN, as well as Vision
Scotland: Intellisense Templates on Migration
What have we done?
(Internal Reference D10-15116)
Updated the migration tool from DM7 to DM10, to accommodate specific SQL requirements
Why have we done this?
To ensure the migration process moves/sets up all the required Intellisense templates when a site moves from DM7 to DM10
How will you benefit?
Intellisense templates will be set up (if none exist already) or moved (if already exist)
Details of the change
SQL change
Scotland Defect 1407 – Patient Export
What have we done?
(Internal Reference D10-15018)
Amended the patient export process so that the pop up error message about restricted documents only shows when a patient has restricted documents.
Why have we done this?
The popup about restricted documents should only display if restricted documents exist for the patient being exported
How will you benefit?
The popup will accurately indicate restricted documents
Details of the change
Bug fixed which was showing the popup for all documents, not just restricted documents.
Scotland Defect SCI Gateway: Pre-Signed URLs GET action returning 502 Error
What have we done?
(Internal Reference D10-15212)
Update the GET action of the SCI Gateway
Why have we done this?
To resolve reported defect
How will you benefit?
SCI Gateway will handle different file sizes as expected
Details of the change
Change to check for the payload size to match lambda hard limit size
Scotland Defect SCI Gateway: Pre-Signed URLs GET action returning 403 error
What have we done?
(Internal Reference D10-15202)
Amended the SCI Gateway API to resolve an issue with AWS limitations
Why have we done this?
AWS had restrictions with $ characters been in URLs as this is a special character
within their system. This was causing the GET function to fail with a 403 error.
How will you benefit?
GET function for Pre-Signed URLs will work correctly
Details of the change
Changed the API Gateway to use a proxy input
Scotland Defect #1416 - Incorrect patient names appearing in User Activity report
What have we done?
(Internal Reference D10-15061)
Amended User Activity report to only show details of patients that user worked on
Why have we done this?
Phantom entries were appearing in the User Activity report
How will you benefit?
The report information will be correct
Details of the change
Query statement amended
Scotland DFCT0011332: Error when attaching document in EMIS PCS
What have we done?
(Internal Reference D10-14314)
Resolved an issue caused by a permission setting
Why have we done this?
To facilitate the functionality of attaching documents in EMIS PCS when the checkbox "Add Document link to EMIS PCS" is selected
How will you benefit?
Expected functionality will now work, specifically the ability to attach a document to the patient record and add the corresponding document link to EMIS PCS
Details of the change
Share API on tenant updated
Scotland Defect 1390: GP2GP Import/Export report not populated correctly
What have we done?
(Internal Reference D10-14893)
Updated the GP2GP report logic for Scotland, to use the CHI Number
Why have we done this?
GP2GP Report not showing patient names on Import. This is because the patient ID is not available after a GP2GP import so Patient names cannot be retrieved.
How will you benefit?
GP2GP report will show patient names
Details of the change
Amended the query to use CHI number instead of Patient ID
Deletion Tool - Patient Deletion Process API: Creation & Validation
What have we done?
(Internal Reference D10-13612)
Created an API which can initiate, track and audit a request to delete a patient. This will be run by OneAdvanced.
Why have we done this?
To adhere to NHS Framework GPITF requirements that states that at a clinicians request we must provide a way to remove documents from the Document Management system, with the solution supporting the physical deletion of records or parts of records in response to court orders or other legislative circumstances.
How will you benefit?
Further development items will follow, which will use the API for patient deletion
Details of the change
Internal API for patient deletion initiation – this will not be functional until further feature change work is completed
Transferring SNOMED Data via Docman to Improve Coding Quality
We’re currently piloting this feature with Manchester. Once we’ve gathered feedback, we’ll roll it out more widely.
What have we done?
(Internal References DCMC-4786/DCMC-4789)
Docman connect have added new Onset Date field to the API. When SNOMED coded information is sent into Docman10, 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 practices, with plans for wider rollout following feedback
