Also need to add functionality for resending of post processing message Resolution Post processed data can now be locked down with XR setting set to but can be overridden if the user has the ‘POSTEXAM.LockdownPostProcessing’ ‘Yes’ security setting. ‘GENERAL.OVER_PPROC_LOC’ in 2.09.10t1 Printing Resolved Issue CRIS-1097 Printed Documents stored on the server results in NullPointer Error Description It is possible that if a user attempts to a document a null pointer exception will be generated, this occurs when using HTTP not FTP Resolution When storing printed documents, a previously closed data transaction is trying to be closed leading to the error message seen. The error is no longer thrown and additional debug is added to inform the user when it is attempting to close an already closed transaction. Fixed in 2.09.10t1 Reporting New Functionality CRIS-958 Obstetrics reporting with external report interface Description Where the report editor is restricted to read only, it must be possible to configure at modality level which of the modalities this restriction applies to such that an event of modality 'O' is still reportable in CRIS. Possible solutions: Using the CRISMODL table to include extra field to enable an override of report, if report is set to read only. XR Setting If it's required to be site/trust specific then does it make more sense to add an XR setting? We could have it so that, for anything at all to be reported, the user must still have GENERAL.CREATE_REPORT/GENERAL.CHANGE_REPORT. But then, if they have an addition XR setting, e.g. Report.ModalitiesForReporting, set then only the modalities listed in this
Also need to add functionality for resending of post processing message Resolution Post processed data can now be locked down with XR setting ‘POSTEXAM.LockdownPostProcessing’ set to ‘Yes’ but can be overridden if the user has the ‘GENERAL.OVER_PPROC_LOC’ security setting. in 2.09.10t1 Printing Resolved Issue CRIS-1097 Printed Documents stored on the server results in NullPointer Error Description It is possible that if a user attempts to a document a null pointer exception will be generated, this occurs when using HTTP not FTP Resolution When storing printed documents, a previously closed data transaction is trying to be closed leading to the error message seen. The error is no longer thrown and additional debug is added to inform the user when it is attempting to close an already closed transaction. Fixed in 2.09.10t1 Reporting New Functionality CRIS-958 Obstetrics reporting with external report interface Description Where the report editor is restricted to read only, it must be possible to configure at modality level which of the modalities this restriction applies to such that an event of modality 'O' is still reportable in CRIS. Possible solutions: Using the CRISMODL table to include extra field to enable an override of report, if report is set to read only. XR Setting If it's required to be site/trust specific then does it make more sense to add an XR setting? We could have it so that, for anything at all to be reported, the user must still have GENERAL.CREATE_REPORT/GENERAL.CHANGE_REPORT. But then, if they have an addition XR setting, e.g. Report.ModalitiesForReporting, set then only the modalities listed in this
HSS_CRIS_Release_Notes_2_09_10t1_specific_D5.0.docx