Docman GP 278 - July 2026
Docman GP 278 - July 2026
This page contains details of new and amended functionality included in the software update known as Release 278
Database Performance Improvements
What have we done?
(Internal Reference D10-16336, D10-16337, D10-16338, D10-16339, D10-16533)
We have improved how database operations are handled across the DM10 Web App, Web API, and supporting tools including DocBot and CI processes. Read and Write operations are now directed to the appropriate database clusters.
Why have we done this?
To reduce unnecessary load on the Write database cluster, improve system performance, and ensure database resources are used more efficiently.
How will you benefit?
Users will experience improved application performance and increased reliability, particularly during periods of higher system usage. Database write operations have also been reduced from 51% to 20%, improving overall efficiency.
Details of the change
Database operations across the DM10 Web App, Web API, DocBot, and CI tools have been reviewed and updated to ensure read-only requests use the read database cluster, while insert, update, and delete operations continue to use the Write cluster. Validation checks and monitoring have been completed to confirm database requests are being routed correctly and performance improvements have been achieved.
Patient Indicator into EMIS Integration Update
What have we done?
(Internal Reference D10-15844)
We’ve updated the integration with EMIS for Northern Ireland as sites move from DM7 to DM10, ensuring the correct patient identifier is sent during filing and patient information continues to be processed accurately.
Why have we done this?
To ensure patient information is transferred accurately and aligns with Northern Ireland requirements.
How will you benefit?
Sites migrating from DM7 to DM10 in Northern Ireland will have a consistent patient identification process, with DM10 supporting the required Northern Ireland patient identifier format when filing documents into the Clinical System.
Details of the change
As part of Northern Ireland sites migrating from DM7 to DM10, we have updated DM10 to follow the existing DM7 filing logic.
When sending information to the EMIS Clinical System, DM10 now sends the Northern Ireland Health and Care Number (HCN) along with the required patient number indicator, ensuring patient information continues to be processed correctly during the transition.
Desktop Application Stability Improvements
What have we done?
(Internal Reference D10-15347)
We’ve improved the DTA by removing sync-over-async patterns from frequently used forms and services.
Why have we done this?
To reduce the risk of application deadlocks and improve stability when the DTA is in use.
How will you benefit?
A more reliable and stable DTA with reduced risk of freezes or delays during everyday use.
Details of the change
We’ve updated areas of the DTA identified to remove sync-over-async usage.
These improvements help the DTA handle background operations more effectively and reduce the chance of issues occurring during normal usage.
Scotland EMIS/PCS Patient and User Sync Improvements
What have we done?
(Internal Reference D10-15852, D10-16233, D10-15671, D10-15265, D10-15672, D10-15194)
We have introduced Patient and User Sync functionality for Scotland EMIS/PCS sites. The DTA can now automatically manage synchronisation between EMIS/PCS and DM10, allowing patient and user information to be transferred and maintained without manual intervention.
Why have we done this?
To support Scotland EMIS/PCS sites by providing an automated process to synchronise patient and user information between systems.
How will you benefit?
Users will have patient and user information synchronised automatically, with clear visibility when synchronisation is running and confirmation that updates have completed successfully.
Details of the change
The DTA now checks when Patient Sync and User Sync are required and automatically starts the process when needed.
User Sync retrieves user information from EMIS/PCS and updates DM10 with the latest details, including the last successful sync date and time.
The process includes checks to prevent multiple DTAs from running the same sync at the same time. Status messages have also been added to inform users when a sync is running and advise them to keep the DTA open until completion.
Sync scheduling has been improved so that the next run time is only updated after a successful sync. If a sync fails, the next scheduled run remains unchanged so the process can retry successfully.
Scotland EMIS/PCS Patient/User Sync Monitoring and Alerting Improvements
What have we done?
(Internal Reference D10-15267, D10-16226, D10-15268, D10-16227)
We have introduced monitoring and alerting to support new Patient Sync and User Sync processes for Scotland EMIS/PCS sites. This provides visibility of sync activity and helps identify issues when synchronisation does not complete successfully.
Why have we done this?
To ensure Patient and User Sync processes are running as expected and any failures or delays are identified quickly.
How will you benefit?
Greater confidence that patient and user information is being kept up to date, with quicker identification of issues and improved support visibility when syncs do not complete successfully.
Details of the change
Patient Sync and User Sync activity will log site details, completion times, and failure information.
Monitoring and dashboards have been introduced to provide visibility of sync health, including successful runs, failures, affected sites, and failure reasons to support quicker investigation and resolution.
Document Printing fix
Released as a hotfix on Monday 6th July
What have we done?
(Internal Reference D10-16506)
We’ve fixed an issue that caused the Desktop Application to become unresponsive when printing multiple documents in succession.
Why have we done this?
To improve the reliability of document printing and ensure users can continue printing without interruption.
How will you benefit?
- Print documents continuously without interruption
- Reduced delays when printing multiple documents
Details of the change
We resolved an issue where the print confirmation message remained on screen longer than expected, causing the Desktop Application to stop responding after multiple print jobs.
The printing process has been fixed so confirmation messages close correctly and users can continue printing documents without needing to restart the Desktop Agent. This provides a more reliable printing experience when working with multiple documents.
