Docman GP 276 - June 2026
Docman GP 276 - June 2026
This page contains details of new and amended functionality included in the software update Release 276.
Document Flag Update for Patient Records
What have we done?
(Internal Reference D10-15604)
We’ve fixed an issue where patient records were not always showing the correct document status after a patient was reimported.
Why have we done this?
To ensure patient records always correctly reflect whether documents exist, so users can reliably access patient documents.
How will you benefit?
This ensures patient records correctly show documents when they exist, making it easier to find and access patient information.
Details of the change
We’ve fixed an issue where the “has documents” flag was not always being reset correctly when a patient was reimported. This previously caused some patients to incorrectly show as having no documents. The system now correctly updates the flag so patient records always reflect the true document status.
Password-Protected PDF Filing Behaviour Fix
What have we done?
(Internal Reference D10-16050)
We’ve fixed an issue where selecting a password-protected PDF in the Filing screen would trigger a password prompt and incorrectly apply a filter, causing the document to disappear.
Why have we done this?
To ensure password-protected PDFs behave correctly and do not disappear unexpectedly during filing.
How will you benefit?
This ensures password-protected PDFs remain visible in the Filing list, preventing unexpected filtering and providing a more reliable filing experience.
Details of the change
We fixed an issue where selecting a password-protected PDF could incorrectly trigger a filter in the Filing list. The Filing screen now prevents this behaviour, ensuring password-protected PDFs remain visible and can be accessed as expected.
Task View Error Fix (Invalid Filter Value Issue)
What have we done?
(Internal Reference D10-16067)
We’ve fixed an issue where Task Views were failing due to invalid filter values being generated when creating or editing views.
Why have we done this?
To stop errors when saving or using Task Views and ensure filters work correctly.
How will you benefit?
Task Views can now be created and edited without errors, filters work as expected in Quick Filter and Task Search, and stability has been improved when using saved views.
Details of the change
We fixed an issue where empty multi-select filters were being saved as invalid values, causing Task Views to fail.
The system now correctly handles empty selections, preventing errors when creating, editing, or using Task Views.
Performance improvement
What have we done?
(Internal Reference D10-15952)
We’ve improved the document renaming process by removing unnecessary legacy processing that was still running in the background.
Why have we done this?
To improve performance and make the system run more efficiently by removing processing that is no longer required.
How will you benefit?
This results in faster, smoother document renaming and improved overall system performance with less background processing.
Details of the change
We removed a legacy database update that was still being triggered during document renaming. This update related to functionality that is no longer in use.
Desktop App Security Enhancement
What have we done?
(Internal Reference D10-15660, D10-15324, D10-15609)
We have completed a series of security enhancement to the Desktop application to strengthen the protection of the platform. These improvements focus on how the service loads and validates system components, as well as increasing the security of the service installation environment.
Why have we done this?
Following a recent security review, we identified opportunities to further strengthen the Desktop Service and implement additional safeguards.
How will you benefit?
Additional safeguards against unauthorised system changes, increased platform security and resilience, and continued alignment with recognised security best practices.
Details of the change
This includes enhancements to how the service loads trusted system components, ensuring that only approved and validated files are used during service startup. We have also strengthened controls around the service installation directory to help prevent unauthorised changes to service files.
Additional validation checks have been implemented to monitor and verify security settings, providing greater assurance that the service is operating within a secure environment.
Patient Sync Performance Improvement
This was shipped as a Hotfix prior to the release.
What have we done?
(Internal Reference D10-15722)
We’ve updated the deployment process for SCI Gateway so it is now managed through CDK across supported environments.
Why have we done this?
To provide a more consistent and reliable deployment approach and simplify the management of SCI Gateway releases.
How will you benefit?
This provides a more robust deployment process, improved consistency across environments, and greater confidence in future releases.
Details of the change
SCI Gateway deployments are now managed through CDK across all non-production environments. This ensures deployments are performed in a consistent and repeatable way while maintaining existing API functionality.
The following items were included in release 274 but were not deployed. They will now be bundled into release 276.
Password Change Security Enhancements
What have we done?
(Internal Reference: D10-15662)
We have improved the password change process to enhance security and session management. This includes ensuring users are securely logged out after updating their password, adding clear on-screen guidance during the process, and capturing password change activity within audit logs.
Why have we done this?
To strengthen account security and align with best practices by ensuring that any changes to login details are properly validated and protected.
How will you benefit?
You will benefit from improved account security and clearer guidance when updating your password, helping to ensure your access remains protected
Details of the change
These updates ensure that sessions are handled more securely, provide clearer messaging during the process, and help maintain a safe and consistent experience when managing login details.
Web App & Clinical Interaction Tool Performance Improvement
What have we done?
(Internal Reference: D10-15802)
· Made improvements to how the Web Application and Clinical Interaction Tool handles background processes.
· Enhanced key areas of the system that are used most frequently.
Why have we done this?
To support a more stable and reliable experience, particularly during periods of higher system activity
How will you benefit?
A smoother and more responsive experience when using the application.
Details of the change
The Web Application and Clinical Interaction Tool have been updated to better manage internal processing and system activity. This helps ensure tasks are handled more efficiently, resulting in improved performance.
Session Management Security Enhancements
What have we done?
(Internal Reference: D10-15663)
We have improved how session cookies are managed within the web application. This includes ensuring that session identifiers are refreshed during login and cleared upon logout to support a more secure session lifecycle.
Why have we done this?
To align with security best practices and further strengthen how user sessions are managed and protected
How will you benefit?
You will benefit from improved session security, helping to ensure your access to the system remains safe and well-managed
Details of the change
These updates ensure that sessions are refreshed appropriately, supporting a more secure and reliable experience when accessing the web application.
Xx2 Tool File Handling Enhancements
What have we done?
(Internal Reference: D10-15850)
We have improved the xx2 tool to support handling of data in .zip format. This includes enabling the tool to automatically process incoming compressed files and return the output in the same format.
Why have we done this?
You can now upload and receive data in .zip format, making the process quicker and easier without needing to manually extract or repackage files
How will you benefit?
You will benefit from improved session security, helping to ensure your access to the system remains safe and well-managed
Details of the change
The xx2 tool now accepts .zip files as input, automatically extracts the contents for processing, and then packages the output back into a .zip file once complete.
Docman 7 to Docman 10 Migration Fix
What have we done?
(Internal Reference: D10-15702)
We have resolved an issue affecting the migration process from DM7 to DM10 following recent AWS package updates. This fix ensures that migration processes complete successfully as expected.
Why have we done this?
To ensure smooth and reliable migration between DM7 and DM10 environments.
How will you benefit?
Data will now migrate successfully without interruption
Details of the change
We’ve made a fix to how migration files are handled during processing. This ensures that files are correctly named and processed in the expected format, allowing the migration pipeline to complete successfully and data to be transferred accurately from DM7 to DM10.
Sync Performance Improvements in Command Line Applications
What have we done?
(Internal Reference: D10-15260)
We’ve improved several command line applications by removing sync-over-async patterns that could impact performance under load.
Why have we done this?
To reduce the risk of performance issues and potential deadlocks when the system is under heavy use.
How will you benefit?
This provides more stable and reliable command line tools, especially when processing high volumes of requests.
Details of the change
We’ve removed sync-over-async usage across key services and controllers. These improvements have been applied to frequently used components to ensure better performance and reduce the risk of deadlocks under load.
