Docman GP 281 - August 2026
Release 281 Release Notes - August 2026
This page contains details of new and amended functionality included in the software update Release 281.
Scotland GP2GP Options
What have we done?
(Internal Reference D10-15481)
We updated GP2GP functionality so that GP2GP Import and Export options are only available to Scotland organisations.
Why have we done this?
To ensure GP2GP options are shown only where they are applicable.
How will you benefit?
Users in England, Wales and Northern Ireland will no longer see GP2GP options that do not apply to their organisation, while Scotland users will continue to have access to the existing GP2GP functionality.
Details of the change
GP2GP Import and Export options are now restricted to Scotland organisations across the Filing, Patient Viewer and Reports areas.
For non-Scotland organisations, the options are displayed as Import Patient Documents and Export Patient where the relevant features are assigned. Scotland organisations continue to use the existing GP2GP Patient Import and GP2GP Patient Export options.
Docman 10 – Revision Upload Error
What have we done?
(Internal Reference D10-15629)
We have fixed an issue where a “Capture Document Failed” message was incorrectly displayed when adding a revised document.
Why have we done this?
To ensure revised documents can be uploaded without an incorrect error message being displayed.
How will you benefit?
Users can add revised documents without receiving an error when the upload has completed successfully.
Details of the change
The issue was caused by an incorrect response being passed back after the revision was uploaded. This has been corrected so the system correctly identifies a successful revision upload.
Uploading an unchanged document will continue to display the appropriate message, while edited or renamed revisions can be uploaded successfully without an error.
Clinical Interaction Save Error fix
What have we done?
(Internal Reference D10-15656)
We have fixed an issue that could cause Clinical Interactions to fail when saving patient visibility information.
Why have we done this?
To make sure Clinical Interactions can be saved successfully when patient visibility information is not provided.
How will you benefit?
Users will be able to save Clinical Interactions without errors when using patient visibility settings.
Details of the change
The issue was caused when the patient visibility setting was left blank instead of being set to Yes or No. The system has been updated to safely handle this and treat a blank setting as No.
Scotland GP2GP Import Window Fix
What have we done?
(Internal Reference D10-15886)
We have fixed an issue where the GP2GP Import window could open behind the Docman 10 application or minimise unexpectedly.
Why have we done this?
To make sure the GP2GP Import window is clearly visible when users need to complete an import.
How will you benefit?
Users will be able to easily find and use the GP2GP Import window without having to search for it behind Docman 10 or in the taskbar.
Details of the change
The GP2GP Import window now stays visible and in focus over Docman 10 until the user selects Import, Cancel or X.
Users can still minimise or maximise the window using the standard window controls.
DM10 Filing – Document Loading Issue
What have we done?
(Internal Reference D10-15984)
We have fixed an issue where certain documents in the Filing section could remain stuck on “Document Loading”, preventing users from accessing the document or right-hand menu.
Why have we done this?
To ensure documents can be opened and managed correctly, including deleting documents where required.
How will you benefit?
Users will be able to access documents in Filing as expected. If a document cannot be loaded, a clear message will be shown instead of leaving the screen stuck.
Details of the change
Documents that cannot be loaded correctly are now identified and handled with a standard error message. The message includes the document reference to help Support investigate the issue.
Monitoring will also be added to track document loading failures and support ongoing monitoring.
Internet Connect API 401 Error Fix
What have we done?
(Internal Reference D10-16115)
We have changed the Internet Connect API to prevent 401 errors occurring when the API consumer whitelist is changed.
Why have we done this?
To ensure changes to the API consumer whitelist do not interrupt access to the Internet Connect API.
How will you benefit?
Users will be able to continue using the Internet Connect API when new practices are added or existing whitelist settings are updated, without experiencing unexpected service interruptions.
Details of the change
The Internet Connect API now identifies when it is operating as an Internet-facing service and handles authentication accordingly. This prevents valid Internet API access from being rejected following whitelist changes, while the existing checks remain in place for non-Internet-facing services.
Usual GP Name Display
What have we done?
(Internal Reference D10-16217)
We have changed the Usual GP field to display the GP’s full name as part of the move to DM10.
Why have we done this?
To ensure the Usual GP information is presented in the expected format for Scotland sites using DM10.
How will you benefit?
The Usual GP field will display the GP’s name clearly, making it easier to identify the patient’s usual GP.
Details of the change
The Usual GP field now uses the GP’s full name when displaying the patient’s usual GP information.
Document Audit Information Update
What have we done?
(Internal Reference D10-16252)
We have updated the document audit information shown when documents are moved or copied between patient records.
Why have we done this?
To support Information Governance requirements by ensuring patient names from other records are not displayed in the document audit history.
How will you benefit?
Document audit information will provide the relevant activity without displaying patient names from another patient record, helping to protect patient information.
Details of the change
The document audit timeline no longer displays the patient name associated with a move or copy action. The audit entries now show “Document Moved” or “Document Copied” without identifying the other patient. This also applies to existing audit entries.
Scotland Patient Sync – Home Telephone Number
What have we done?
(Internal Reference D10-16259)
We have made changes to Patient Sync to ensure the patient’s home telephone number is saved correctly in Docman 10 when received from the clinical system.
Why have we done this?
To ensure patient demographic information received through Patient Sync is stored correctly in Docman 10.
How will you benefit?
Patient records in Docman 10 will contain the latest available home telephone number from the clinical system.
Details of the change
Patient Sync now saves the home telephone number to the patient record when demographic information is synchronised from the clinical system.
PFS Clinical Interaction Monitoring
What have we done?
(Internal Reference D10-16381)
We have improved monitoring for PFS Clinical Interaction to provide clearer visibility of processing activity and errors by ODS code.
Why have we done this?
To make it easier to monitor PFS activity and understand the specific reasons when processing fails.
How will you benefit?
Support and technical teams will have clearer information when investigating PFS issues, making it easier to identify affected sites and understand what has gone wrong.
Details of the change
PFS activity is now logged in a structured format so that run summaries, history, status and errors can be reviewed by ODS code. Errors are also grouped by specific failure type, with clearer messages added to explain what has happened. This provides better visibility of successful and failed runs and supports quicker investigation of issues.
Scotland Folder Structure Updates
What have we done?
(Internal Reference D10-16820)
We have updated the folder structure setup for Scotland sites migrating from Docman 7 to Docman 10 to ensure folders follow the agreed Scotland National folder structure. Folder names are also handled consistently where there are minor differences in formatting.
Why have we done this?
To ensure folders are set up correctly during migration and support successful document handling through SCI Gateway.
How will you benefit?
Scotland sites migrating to Docman 10 will have a consistent folder structure that supports the successful transfer and handling of documents.
Details of the change
The migration process checks folders against the agreed Scotland National folder structure and ensures they are assigned the appropriate unique identifier. Where a folder from Docman 7 does not match an existing standard folder, it is brought across with a new unique identifier.
This ensures the folder structure in Docman 10 is correctly configured and compatible with SCI Gateway.
PCN Settings – User Interface Alignment
What have we done?
(Internal Reference D10-16115)
We have updated the PCN Settings page to correct layout and alignment issues affecting the page following previous user interface changes.
Why have we done this?
To ensure the PCN Settings page displays consistently and provides a clear and usable experience.
How will you benefit?
The PCN Settings page will be easier to use, with the page elements and user dropdown displayed correctly and the page scrolling as expected.
Details of the change
The PCN Settings page layout has been updated to ensure the page elements are correctly aligned, including the user dropdown. Page scrolling has also been corrected to provide the expected behaviour.
PCN Migration – Update Existing Users
What have we done?
(Internal Reference D10-16760)
We have changed the PCN migration process so that existing users are checked and their details are updated when they differ from the latest information held by the practice.
Why have we done this?
To ensure user information within a PCN reflects the latest practice data when a practice is migrated into a PCN.
How will you benefit?
Users will have the latest available information when practices are migrated into a PCN, without making unnecessary updates where user details have not changed.
Details of the change
During a PCN migration, new users continue to be added as before. Existing users are now checked against the latest practice information, and their details are updated where changes are identified. Users whose details have not changed are left unchanged. Migration results also record the number of users added, updated and unchanged, supporting clearer visibility of the migration process.
The following Desktop Application improvements were released as a hotfix on 5th August
Desktop Application Security Improvement
What have we done?
(Internal Reference D10-16819)
Added additional checks to the Desktop Application to validate COM components before they are loaded.
Why have we done this?
To strengthen application security and ensure components are loaded safely from trusted locations.
How will you benefit?
The Desktop Application now provides an additional layer of protection, helping to maintain a secure and reliable user experience.
Details of the change
The Desktop Application now verifies COM component locations before use, ensuring only expected and trusted components are loaded. This reduces the risk of unauthorised components being used to affect application behaviour.
(Scotland) GP2GP Import Fixes
What have we done?
(Internal Reference D10-16424)
Fixed issues that could cause GP2GP imports to fail and incorrectly remove import files.
Why have we done this?
To make GP2GP imports more reliable and make it easier to recover from failed imports.
How will you benefit?
You will experience fewer GP2GP import failures, failed import files will remain available for retry, and the behaviour now matches Docman 7.
Details of the change
The import process now skips missing HL7 Present fields, matching the behaviour in Docman 7. We've also changed the import process so files are only deleted after a successful import. If an import fails, the files remain in the import folder so they can be retried or investigated.
(Scotland) GP2GP Export XML Fix
What have we done?
(Internal Reference D10-16255)
Fixed an issue where exporting the same patient multiple times before eLinks processed the first export caused the XML file to overwrite previous attachment references.
Why have we done this?
To ensure all exported attachments remain referenced until eLinks processes the export.
How will you benefit?
- All attachments are included in the export XML
- Multiple exports work as expected
- Behaviour matches Docman 7
Details of the change
The export process identifies existing XML files within the Export folder and adds new attachment details without removing existing references. This ensures all attachments from pending exports are retained until they are successfully processed by eLinks.
