Release Notes SpeechReport 3.3

New functionalities
Data control: 

Purging completed documentsMore and more we receive questions about the retention of our data in our database. Until now we hold all data in our database. There are plans to implement various ways to give more control about the data in the database to our customers. The purging of completed document is the first step towards this.

Using extra coding schemes in Structured reporting documents.

Rejection of incomplete PV1.3 in Standard integration.

The PV1.3 segment on the SIU message holds the location of the patient or the appointment. If the first field of this segment is empty, the record was stored in the database anyway. This results in not properly starting of the Client application. In SpeechReport 3.2.1 we made an improvement in handling the PV1.3 segment so that the Client does not crash anymore however this is not the actual support of the HL7 standard.In the documentation of the standard integration the PV1.3.1 field has the status of being mandatory. This means that if this field is not filled the message should be rejected and not stored in the database.This rejection is now part of the distribution coming with this release.

Suspending via PACS/EPD: “suspend for me“ instead of “suspend for all”.

When the application receives a trigger to suspend a document from a PACS or EPR front-end integration, the document should become available in the general worklist instead of being suspended for the logged in user.When a document is 'suspended for me', only that particular user is able to proceed with the document. A colleague will not be able to pick up the document, as the document is blocked for everyone else. Users are not always aware that there are two different ways to suspend a document and the user normally selects the default setting (which is now suspend for me).

For more information please contact your G2 Speech Account Manager!