Docman GP 272 - April 2026
Release 272 Release Notes - April 2026
This page contains details of new and amended functionality included in the software update Release 272.
Docuvieware Upgrade
(Internal Reference D10-15370, D10-14072, D10-15854)
What have we done?
Upgraded the version of DocuVieware used in Docman 10 and updated the associated license keys. Docuvieware is used to render PDF, TIF, DOCX and .DOC documents in Docman 10.
Why have we done this?
To maintain stability of the application, but applying the latest version.
How will you benefit?
There will be no change to end users.
Details of the change
Upgrade from version 3.0.0.9 to version 3.2.90.0.
The upgrade has resolved defect D10-14072 (Scotland DFCT0011294: Docman 10 – When converting/reverting a document to enable annotations, the system becomes unresponsive)
Update AWS SDK libraries to v4
(Internal Reference D10-15718, D10-15648)
What have we done?
Updated AWS SDK libraries to v4 for the following repos:
• ahc-docman-10 repo
Why have we done this?
AWS SDK for .Net v3.x will only receive critical bug fixes and security updates from March 1st 2026, and will move to end of support on June 1st 2026 (after which it will no longer receive updates or releases).
How will you benefit?
The application will run supported versions of the libraries, which will be updated with bug fixes and security updates available.
Details of the change
Updated the AWS libraries to v4 for projects within each repo.
GP2GP Export Improvement – Handling of Active and Inactive Patient Records (Scotland only)
(Internal Reference D10-15804)
What have we done?
We’ve made some improvements to the GP2GP export process in Docman10 to better handle patients who may exist as active and/or inactive records.
Why have we done this?
Following a previous change, we identified that GP2GP exports could fail in certain scenarios, particularly when working with restored documents or inactive patient records. This update helps smooth out those edge cases and ensures the process behaves more consistently.
How will you benefit?
You won’t see any changes to the way you use the system, but GP2GP exports should now feel more reliable, especially when dealing with patients who have been previously transferred or restored.
Details of the change
Where inactive records are involved, the system now allows exports to proceed when appropriate, while still respecting existing constraints around HL7 Extracts. In situations where multiple records exist for the same patient, the system will
automatically prioritise the most recently created record. This helps ensure the most up-to-date information is used, regardless of which record the export is started from.
Where both active and inactive records exist, the system behaves more intuitively, allowing exports from active records while preventing invalid exports from inactive ones. Overall, these changes help reduce unexpected failures and make the export process more robust in real-world scenarios.
Multiple Document Restore Functionality
(Internal Reference D10-15644)
(Scotland Reference 1432)
What have we done?
Enhanced Docman10 to allow Admin users to restore multiple documents at the same time, while keeping the existing single document restore functionality unchanged.
Why have we done this?
To improve efficiency for admin users restoring large volumes of documents, reducing the need to restore documents one at a time.
How will you benefit?
Admin users can now restore multiple documents in a single action, saving time and improving usability, while still having the same experience for single document restores.
Details of the change
Single Document Restore
- No changes have been made to existing functionality. Admin Users can select a single document and click Restore Document. A free text box is displayed to capture the reason for restore. On clicking Restore, the document is restored and an entry is added to the audit log.
Multiple Document Restore
- Admin users can now select multiple documents using Select All and Deselect All options. Admin users can refine their selection after using Select All, with the Restore Document option remaining available.
- When multiple documents are selected and Restore Document is clicked, a free text box is displayed to capture the reason for restore. On clicking Restore, a message is displayed stating “Documents are being restored”. All selected documents are restored, excluding any already present on the patient record, and each restored document is recorded in the audit log. If the admin user clicks Cancel, no documents are restored, no audit log entries are created, and the user is returned to the selection screen with their previous selections retained.
Amend XML Schema Definition on DM10 GP2GP
(Internal Reference D10-15831)
(Scotland Reference 1490)
What have we done?
We have made a small update to the GP2GP export within Docman10 to better align with existing expectations and ensure consistency.
Why have we done this?
These changes ensure compatibility with external systems, specifically aligning the export format with what is expected by Medex and maintaining consistency with previous Docman versions.
How will you benefit?
There is no impact to how admin users interact with the system. These updates happen in the background and help ensure exports continue to work smoothly and reliably.
Details of the change
We have updated the field names used in the GP2GP export XML so that they now match those used in Docman 7. The fields previously named DOC_COUNT and DOC_SKIPPED have been updated to COUNT and SKIPPED.
We have also updated the company name referenced in the export to reflect the current branding, changing it from “© PCTI Solutions ltd” to “© OneAdvanced.”
This is a Scotland-only change and applies to the data transfer (DTA) process only. It has been designed to be backwards compatible with earlier versions and will not impact existing GP2GP import functionality.
Resolved Clinical Code selection issue
(Internal Reference D10-15351)
(Scotland Reference 1451)
What have we done?
Changed the DM10 code to rectify invalid symbols which prevented the clinical code browser functioning correctly
Why have we done this?
The Clinical Code browser was not showing all code results, when the user clicked on a code category with no codes - selecting another code category which should have code results was showing no results.
How will you benefit?
Clinical Code browser will display results correctly
Details of the change
Site had read codes which contained hat symbol (^). This was not getting removed when in the clinical code browser, this has been remedied.
