CRIS 2.09.10P6 Specific Release Notes V1.0

CRIS 2.09.10p6 Specific Release Notes v1.0

Copyright

General Information

This release replaces all previous major, minor and emergency releases. All changes included in a major release will also be included in a minor release. There is no downtime needed to install a release unless specifically mentioned in the Trust Implementation Issues section. All sites can be upgraded to this release of CRIS. No changes are included in a release until the change passes all tests and that change has no known issues or has caused any new known issues at the time of release. Each release of CRIS is not normally released with any known major issues unless specifically mentioned in the know issues section.

1. Contents

CRIS 2.09.10p6 Specific Release Notes v1.0

General Information

1. Contents

2. Issue Summaries

2.1 New Features

2.2 Enhancements

2.2.1Interfaces

2.3 Issues Resolved

2.3.1Interfaces

2.3.2Reporting

2.3.3Printing

2.3.4Setup Tables

2.3.5Requests

2.3.6Other

2.3.7Audit

2.4 House Keeping

3. Trust Implementation Issues

3.1 Standard issues:

3.2 Optional, for issues by request only:

4. Change Details

4.1Interfaces

4.2Reporting

4.3Printing

4.4Setup Tables

4.5Requests

4.6Other

4.7Audit

2. Issue Summaries

The following section summarises the changes made in this version of CRIS relative to release 2.09.10p6. Changes are divided into new features and issues resolved. Details of each change are provided later in the document in "Change Details". Navigation is best achieved by searching the document for the relevant "HSS Ref" number.
Notes on the following tables:
HSS Ref. - this relates to internal HSS change numbers. HSS are currently using two software tools to monitor change requests. The ‘old’ Mantis tool with 6/7-figure issue numbers and the ‘new’ Jira tool using a combination of ‘Project Code/Issue Number’, eg CRIS PX/PX17.
LSP Ref. - this relates to LSP Incident, Problem or RFC reference numbers.
By Request - these changes can only be activated by HSS on a specific request by a Trust.
Trust Interest - these changes are deemed to be of significance to trusts either because they impact end users, require trust action or are desirable new features/fixes, which trusts are most likely to take advantage of.

2.1 New Features

2.2 Enhancements

2.2.1Interfaces

HSS Ref / LSP Ref / Description / By Request / Trust Interest
253877 / - / Implementation of the latest Synapse 4.1 DTi / - / -

2.3 Issues Resolved

2.3.1Interfaces

HSS Ref / LSP Ref / Description / By Request / Trust Interest
253520 / - / Populate ORG^O20 With Application Error Message / - / -
253846 / - / BMI - appointment booking issue / - / -

2.3.2Reporting

HSS Ref / LSP Ref / Description / By Request / Trust Interest
253516 / - / Possible to delete an exam and still add a verified report to It / - / -
253284 / - / Batch expires warning will show twice / - / -
CRIS PX/PX-17 / ‘Reported by’ value not persisted through reporting session.
CRIS PX/PX-24 / Wrong ‘reported_by’ used before reporting session created.

2.3.3Printing

HSS Ref / LSP Ref / Description / By Request / Trust Interest
253094 / - / Cris Batch Print filtering / - / -

2.3.4Setup Tables

HSS Ref / LSP Ref / Description / By Request / Trust Interest
253274 / - / NullPointerException thrown when closing UserDictationary setup table / - / -
253138 / - / Every site is automatically assigned to a new user within the 'SiteCodesSetup' table. / - / -
0253342 / USER ID validation fail when trying to save ID below the minimun count

2.3.5Requests

HSS Ref / LSP Ref / Description / By Request / Trust Interest
240772 / - / Request / Wating List room label / - / -

2.3.6Other

HSS Ref / LSP Ref / Description / By Request / Trust Interest
253536 / - / CRIS Integration with Synapse / - / -

2.3.7Audit

HSS Ref / LSP Ref / Description / By Request / Trust Interest
253549 / - / New log reason required for iCRIS user id search / - / -

2.4 House Keeping

House keeping is reserved for general code tidying which may provide minor improvements in efficiency or cosmetic changes that do not relate to issues resolved nor add new functionality.

3. Trust Implementation Issues

This section details issues which must be addressed by the Trust before a release or, where they are for issues which are only by request, before a particular feature is activated.

3.1 Standard issues:

3.2 Optional, for issues by request only:

None.

4. Change Details

This section provides further details of each change.
HEAD refers to the development and unreleased testing versions of CRIS. Changes reported in HEAD are either new features not in any previous version of CRIS or issues that have only been introduced or discovered during development or testing of the next release of CRIS. Issues reported in a particular release, HEAD or otherwise, may also be pertinent to other releases of CRIS.

4.1Interfaces

253520 - Populate ORG^O20 With Application Error Message
Reported in:2.09.10p6 Fixed in: 2.09.10p6
Description: The application error to be contained in the MSA:3 field.
Or
The application error to be contained within a ERR segment.
The reason for the change is to give the trust a greater visibility over why the messages are returning application errors.
Resolution: Below are the circumstances that cause a return value of AE in MSA:1 and message that will be displayed in MSA:3. (1) Sending an invalid exam code - "Exam code invalid" (2) Order control SC but event does not exist - "Could not find event in order to attend" (3) Order control CA but event does not exist - "Could not find event in order to cancel" (4) An exception with a message is thrown - the message (5) An exception with no message is thrown - "An unexpected error has occurred"
253846 - BMI - appointment booking issue
Reported in:2.09.10p6Fixed in:2.09.10p6
Description: When an appointment is booked via the interfaced system to CRIS, and the examination is subsequently changed, the change is only reflected in the examination table. The status record remains at the original examination requested.
Interface coding requires a change to take this into account and fully update the event so that the data is consistent throughout.
Resolution: -Event contains updated exam so exam summary will be updated correctly.

253877 - Implementation of the latest Synapse 4.1 DTi
Reported in: 2.09.10p6 Fixed in: 2.09.10p6
Description: Updating of FUJI's Synapse DTi software to version 4.1.
Resolution: The implementation of the latest Synapse 4.1 DTi software is now ready for deployment.

4.2Reporting

253516 - Possible to delete an exam and still add a verified report to it
Reported in:2.09.10p6Fixed in:2.09.10p6
Description: An incident occurred at a trust whereby a Radiologist had loaded a double exam event in order to report it, and during the time he was reporting, another user loaded the same event and removed the first examination.
This resulted in the report being added to the event, but subsequently being unavailable to users, with no evidence that it was reported.
This issue was exasperated by the fact that the radiologist had a lock on the report for over half an hour, indicating it was probably loaded and then left on screen for a while, before being completed. The user who loaded the event and removed the examination did so with a minute of the report being locked, so it's entirely possible they had no visual notification of the report being locked already.
We should really be either warning the user in the form of a message that another user has locked the report, or the system should run a sanity check upon saving the report so as to validate the examinations which the report is against.
Resolution: User is now asked for confirmation when requesting to change an event containing a report lock.

253284 - Batch expires warning will show twice
Reported in: 2.09.10p6 Fixed in: 2.09.10p6
Description: In report screen, add a batch which is expired.
The 'Batch has expired' warning message is displayed twice.
Close the warning message. Add the same batch again. The warning won't show.
Resolution: If the chosen batch has expired, only one warning message dialog is now displayed.

CRIS PX/PX-17 – ‘Reported_by’ value not persisted through reporting session

Reported in: 2.9.10p6 Fixed in: 2.09.10p6
Description:The 'reported_by' value is populated correctly on the first reported event of a session. All other reports in the same session have the 'reported_by' value missing.

Resolution:The 'reported_by' value is now stored throughout the reporting session.

CRIS PX/PX-24 – Wrong ‘Reported_by’ used before reporting session created

Reported in: 2.9.10p6 Fixed in: 2.09.10p6
Description: If a new report is opened within the report editor, then the user opens the F12 viewer. The user now selected a dictated report and listens to the dictation. The viewer is now closed. If the user finishes the new report, the reporting session details from the report opened via the viewer are copied into the current reporting session.

Resolution:When the local reporting session is ‘blank’ and the user finishes the new report, a message is displayed asking the user to verify that the 'reported_by' value is correct. This will force the user to make sure that, in this scenario, the correct ‘reported_by’ value is saved against the new report.

4.3Printing

253094 - Cris Batch Print filtering
Reported in:2.09.10p6Fixed in:2.09.10p6
Description: Before verifying a report if the radiologist selects the urgency option when creating a report and sets the urgency field to C then verifies the report.
Resolution: The 'Urgency' value can now be filtered upon.

4.4Setup Tables

253274 - NullPointerException thrown when closing UserDictationary setup table
Reported in:2.09.10p6Fixed in2.09.10p6
Description: In setup table, attempt to close other->reports->UserDictionary.
A NullPointerException will be thrown.
Resolution: The 'UserDictionary' setup table can now be closed without error.

253138 - Every site is automatically assigned to a new user within the 'SiteCodesSetup' table.
Reported in: 2.09.10p Fixed in: 2.09.10p6
Description: If a new user is added to the 'Staff' table and is assigned a 'Clinician','Secretary', 'Radiographer', or 'Clerical' code, when the 'SiteCodesSetup' table is loaded, that new user is configured to be available at every site within the trust. Ideally, he should only be available at the site(s) that are configured in the 'Staff' table.
Resolution: Implementation notes. 'Staff' table -> 'SiteCodesSetup' table mapping: Adding a new user to the 'Staff' table: When a new user is added and assigned a site(s), that site(s) will be selected on the appropriate tab(s) within the 'SiteCodesSetup' table. If a new user is added with no site(s) assigned, no sites will be selected in the appropriate tab(s) within the 'SiteCodesSetup' table. Changing an existing user within the 'Staff' table: After the upgrading all existing user data will remain the same, so what was ticked/unticked before will be ticked/unticked now. The chances are that the sites selected in the appropriate tab(s) within the 'SiteCodesSetup' table will not 'match' the site(s) assigned to the existing users in the 'Staff' table. Once, however, the site(s) assigned to an existing user change, these changes will be reflected in the appropriate tab(s) within the 'SiteCodesSetup' table. So, far example, before the upgrade, user 'AUSER' may have 'HSS01' assigned to them within the 'Staff' table and all the local trust sites selected in the 'SiteCodesSetup'. After the upgrade, nothing will have changed, but once changes are made to the 'Staff' table against 'AUSER' ,i.e. site 'HSS02' is added, the 'SiteCodesSetup' table will reflect this change and only 'HSS01' and 'HSS02' will be selected. Changing the selected sites within the 'SiteCodesSetup' table: Selecting/deselecting a site(s) within the table will NOT update the corresponding record within the 'Staff' table. Any changes to the 'Staff' table with regards to the site(s) assigned could overwrite any manual changes made to the 'SiteCodesSetup' table. 'FilmLocations' table -> 'Film Locations' tab in 'SiteCodesSetup' table mapping Adding a new location to the 'FilmLocations' table: When a new location is added and assigned a site, that site will be selected in the 'Film Locations' tab within the 'SiteCodesSetup' table. If a new location is added with no site assigned, no sites will be selected in the 'Film Locations' tab within the 'SiteCodesSetup' table. Changing an existing location within the 'FilmLocations' table: After the upgrading all existing film location data will remain the same, so what was ticked/unticked before will be ticked/unticked now. If a site is added or a different site assigned to the location record, this change will be mirrorred in the 'Film Locations' tab within the 'SiteCodesSetup' table.

253342 – USER ID validation fail when trying to save ID below the maximum count
Reported in: 2.09.10p Fixed in: 2.09.10p6
Description: The staff table flags a message when a user ID code of greater than 10 is entered. When the user ID code is then edited to be less than 10 and the record is saved CRIS is still giving the message of 'Could not update Staff table' and is remembering the original count in the user ID field.
Resolution: Moved 'User ID' validation routine from the 'Save' button to loss of focus from the 'User ID' field. This ensures 'user id' value is valid before the new staff record is saved.

4.5Requests

240772 - Request / Wating List room label
Reported in: 2.09.10p6 Fixed in:2.09.10p6
Description: Some lists display the room label even if they do not have a room filter.
This has no affect on the data displayed in a list.
Resolution: The 'room' label will now only appear if:

1) The list contains a 'room' filter.

2) There is a value in the 'room' filter field.

4.6Other

253536 - CRIS Integration with Synapse
Reported in: 2.09.10pFixed in:2.09.10p6
Description: Updated Synapse DTi. - Utilised the class hss.utils.WebBrowser to handle the launching of Internet Explorer. Correct behaviour established for Windows XP.
Resolution: Changed DTI to launch IE directly via API call rather than via command line shell.

4.7Audit

253549 - New log reason required for iCRIS user id search
Reported in:Fixed in:
Description: Due to a the new iCRIS search facility based on user id, a new log reason is required to be defined.
Resolution: - Appropriate log reason is now available.

Last Updated: HSS 27/11/2018 Healthcare Software Systems – Commercial in Confidence Page 1 of 13