Docman GP 255 - August 2025
Release 255 Release Notes
This page contains details of new and amended functionality included in the software update scheduled for 17th to 24th August 2025, known as Release 255.
API Consumer Disablement
What have we done?
(Internal Reference D10-13986)
The system will automatically disable any API Consumers which have not been used for 1 month or more and write this to the Cloudwatch audit.
Why have we done this?
To ensure all API claims are current and relevant.
How will you benefit?
There should be no change to end user system.
Details of the change
API Consumers not used for 1 month or more will be disabled.
Print Annotations fix
What have we done?
(Internal Reference D10-13324/14276)
Enabled printing annotations.
Why have we done this?
To fix a bug.
How will you benefit?
Annotations will be printed, if requested.
Details of the change
When selecting to Print a document, and selecting the option to Include annotations with Printing TIF files, annotations will be included on the printed output.
Forward and Save is preventing workflows from being finished
What have we done?
(Internal Reference D10-13701/14275)
Forward & Save should allow a workflow to be completed
Why have we done this?
When user was filing a document with a review level task for another User, and uses Forward & Save (rather than Forward & Finish), the workflow is remaining as Under Review. This is showing on the Workflow Tracker Report with the status of Waiting for Tasks. When the document is viewed, is shows as Under Review.
How will you benefit?
Workflows will not be left Under Review.
Details of the change
Workflow will display as Completed once all open tasks have been finished – as it does if Forward & Finish is used.
Document Audit Text Change for PFS Visibility
What have we done?
(Internal Reference D10-14305)
Changed the document audit text around PFS visibility.
Why have we done this?
To make the PFS Visibility status clearer to the Customer
How will you benefit?
Clarity on the PFS Visibility status
Details of the change
When a document is filed and sent for review, the current wording Document has not been set as viewable to the patient in EMIS Web has been amended to Document Visibility has not yet been set. The document is Provisional in EMIS.
The text change will take effect for historical and new entries in document audit.
Allow documents in Filing to be deleted if the document does not exist
What have we done?
(Internal Reference D10-13995)
When a document cannot be opened, the Delete Documents option will be replaced with a Corrupt Document Delete option. This will be on the Filing Screen and the Patient Screen. this will allow the user to soft delete the document.
Why have we done this?
Some documents cannot be opened.
How will you benefit?
Able to soft delete the corrupt documents.
Details of the change
When a document cannot be opened, the Delete Documents option will be replaced with a Corrupt Document Delete option. This will be on the Filing Screen and the Patient Screen.
GP2GP – Provide Notification of Duplicate Patient Import
What have we done?
(Internal Reference D10-6839)
Each GP2GP import will set a flag for a patient that has been imported, so that the system can notify the user is a duplicate patient import is done.
Why have we done this?
To reduce errors with GP2GP import process and provide better clarity to users.
How will you benefit?
Improved visibility.
Details of the change
The following message will be shown:
A GP2GP Import has already been performed for this patient. Do you want to continue?
If the GP2GP import has already been done for that patient.
Scotland: Clinical Bulk Insert Processor settings for Vision
What have we done?
(Internal Reference D10-12099/D10-14335)
Updated the Clinical Bulk Insert processor within Docbot to use specific settings
for Scotland (for Vision).
Why have we done this?
To prepare for Scotland migration to DMGP.
How will you benefit?
There will be no change to end user system.
Details of the change
Updated Docbot for Vision.
Scotland GP2GP Report Fix
What have we done?
(Internal Reference D10-14075)
The GP2GP report has been refreshed so that the filters all work and show the correct information and the report runs successfully.
Why have we done this?
The report filters and information were not working correctly.
How will you benefit?
Ability to view an audit of GP2GP activity
Details of the change
New Menu to Access Report: GpToGp Export/Import > Import Export Report
New Scotland READ2 Code Table
What have we done?
(Internal Reference D10-14190)
Created and populated a new table for Scotland use of READ2 codes.
Why have we done this?
Scotland use a distinct READ2 code list for clinical coding.
How will you benefit?
On migration from DM7 to DM10, Scotland users will have the READ2 codes for Scotland available for clinical coding.
Details of the change
New table created and populated.
Scotland DFCT0011343 GP2GP Import files deletion
What have we done?
(Internal Reference D10-14408)
Resolved an issue in Scotland testing of GP2GP – specifically that when a patient from Docman 7 practice(OR D10 Practice) is exported and imported to a Docman10 practice, relevant import files are not getting deleted from the import folder.
Why have we done this?
To facilitate Scotland testing for their DM7 to DM10 migration.
How will you benefit?
Testing can proceed.
Details of the change
DTA change to delete relevant files.
Scotland DFCT0011340 GP2GP Import attachments
What have we done?
(Internal Reference D10-14410)
Resolved an issue in Scotland testing of GP2GP – specifically that when a patient from Docman 10 practice is exported and imported to a Docman 7 practice, the attachments are not imported into Docman7 and fails the import.
Why have we done this?
To facilitate Scotland testing for their DM7 to DM10 migration.
How will you benefit?
Testing can proceed.
Details of the change
DTA change to import attachments.
Release 253.2 Hotfix : Resolve 100% CPU Utilisation Issue
This has already been released as a hotfix to Release 253 and is listed here for information purposes only.
What have we done?
(Internal Reference D10-14412)
Some request deadlocks are causing server instances to reach and remain at 100%, causing performance issues.
Why have we done this?
To remove deadlock issues and alleviate performance issues resulting from them.
How will you benefit?
There should be no change to end user system.
Details of the change
Docman GP web application change to resolve deadlocks.
