Docman Connect 2.247.0 – May 2025

Gary Watkins Updated by Gary Watkins

247 Release Notes

This page contains details of new and amended functionality included in the software update deployed on <date>.

 

Increase Visibility of Clinical Codes

What have we done?

Increased the visibility of clinical codes which are sent with documents via the Connect API.

Why have we done this?

To ensure that Docman Connect senders can review the codes they have sent.

How will you benefit?

By increasing the visibility of clinical codes, Docman Connect senders will be able to review the codes they have sent and carry out quality assurance activities to improve their sending practices.

Details of the change

Currently, Docman Connect senders can input clinical codes within the metadata fields of any documents sent via the Connect API. However, up until now, there has been no way for a sender to review the codes that they have sent previously. We have now surfaced any clinical codes which have been sent via the Connect API in the Connect Console.

To review the codes they have sent, senders can go to a sent document in the Connect Console and the Document Details page. In the Metadata tab, they will see a breakdown of each code which was sent with that document including a collapsible pane which details the code scheme, description and other key data points.

Increase Visibility of Original Rejection Reason

What have we done?

Increased the visibility of the original rejection reason for documents which have been updated and resent.

Why have we done this?

To ensure that Docman Connect senders can review the original rejection reasons, even after a document has been updated and resent.

How will you benefit?

Docman Connect senders can now carry out further investigation and quality assurance by reviewing the reasons why their documents are being rejected.

Details of the change

When a document is rejected in Docman Connect, it is returned to the original sender in ‘Rejected’ status. Docman Connect senders can use the ‘Update & Resend’ functionality in the Connect Console to update some of the document fields and send the document on to a new endpoint. However, in doing so, the original rejection reason is lost.

We have introduced a new column within the Document List Export called ‘Original Rejection Reason’. This column will be populated with the original REJ rejection reason code to indicate why the document was rejected. This column will be populated, even after the document has been updated and resent on to another endpoint.

How did we do?

Docman Connect 2.245. - 2nd to 14th April 2025

Contact