CRIS 2.09.10P7 Specific Release Notes V1.0

CRIS 2.09.10p7 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.10p7 Specific Release Notes v1.0 1

General Information 1

1. Contents 1

2. Issue Summaries 1

2.1 New Features 1

2.2 Enhancements 1

2.2.1Interfaces 1

2.3 Issues Resolved 1

2.3.1Flexible Forms 1

2.3.2Interfaces 1

2.3.3Nuclear Medicine 1

2.3.4Obstetrics 1

2.3.5Patient 1

2.3.6Post Processing 1

2.3.7Printing 1

2.3.8 Reporting 1

2.3.9 Scanning 1

2.3.10 Setup Tables 1

2.3.11 Stats 1

2.3.12 Voice Recognition 1

2.3.13 Widgets 1

2.3.14 Vetting 1

2.4 House Keeping 1

3. Trust Implementation Issues 1

3.1 Standard issues: 1

3.2 Optional, for issues by request only: 1

4. Change Details 1

4.1Interfaces 1

4.2Flexible forms 1

4.3Nuclear Medicine 1

4.4Obstetrics 1

4.5Patient 1

4.6 Post Processing 1

4.7Printing 1

4.8 Reporting 1

4.9 Scanning 1

4.10 Setup tables 1

4.11 Stats 1

4.12 Voice Recognition 1

4.13 Vetting 1

2. Issue Summaries

The following section summarises the changes made in this version of CRIS relative to release 2.09.10p7. 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
PX-106 / - / Fuji DTI changes. / - / -

2.3 Issues Resolved

2.3.1Flexible Forms

HSS Ref / LSP Ref / Description / By Request / Trust Interest
PX-50 / - / Flexible fields won’t save. / - / -

2.3.2Interfaces

HSS Ref / LSP Ref / Description / By Request / Trust Interest
PX-56 / - / Report that does not appear on IMPAX / - / -
PX-32 / - / Trigger order issue

2.3.3Nuclear Medicine

HSS Ref / LSP Ref / Description / By Request / Trust Interest
PX-37 / - / Shift-click with Nuclear Medicine / - / -

2.3.4Obstetrics

HSS Ref / LSP Ref / Description / By Request / Trust Interest
PX-34 / - / Labelling of Graph Centiles / - / -

2.3.5Patient

HSS Ref / LSP Ref / Description / By Request / Trust Interest
PX-53 / - / Incorrect status change.
PX-59 / - / Ability to have a blank site as a default on a user list. / - / -

2.3.6Post Processing

HSS Ref / LSP Ref / Description / By Request / Trust Interest
PX-115 / - / Blank ‘Intended Clinician’ field in post-processing screen. / - / -

2.3.7Printing

HSS Ref / LSP Ref / Description / By Request / Trust Interest
PX-36 / - / Cannot print a replaced document. / - / -
PX-42 / - / Batch print count incorrectly with ‘Report Start’ and ‘Report End’ filters by Date/Time.

2.3.8 Reporting

HSS Ref / LSP Ref / Description / By Request / Trust Interest
PX-51 / - / Filter by secretary code on the report info list. / - / -
PX-60 / - / Auto verify of Auto report.

2.3.9 Scanning

HSS Ref / LSP Ref / Description / By Request / Trust Interest
PX-35 / - / Scan document tick box. / - / -

2.3.10 Setup Tables

HSS Ref / LSP Ref / Description / By Request / Trust Interest
PX-16 / - / USER ID validation fail when trying to save ID below the maximum count. / - / -

2.3.11 Stats

HSS Ref / LSP Ref / Description / By Request / Trust Interest
PX-47 / - / Stats within Session. / - / -
PX-57 / - / Calls to CrisMethods should be changed back to StatsMethods.
PX-46 / - / Long Running Stats - CAM

2.3.12 Voice Recognition

HSS Ref / LSP Ref / Description / By Request / Trust Interest
PX-58 / - / Reversal of ‘Start Report’ change. / - / -

2.3.13 Widgets

HSS Ref / LSP Ref / Description / By Request / Trust Interest
PX-43 / - / Radiologist Widget slow to load. / - / -

2.3.14 Vetting

HSS Ref / LSP Ref / Description / By Request / Trust Interest
PX-120 / - / ‘Intended Clinician’ is not being saved in ‘Vetting’ screen. / - / -

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

PX-106 – Fuji DTI changes
Reported in: 2.09.10p6 Fixed in: 2.09.10p7
Description: The following changes are required to make the Fuji Synapse 4 DTI safe for use:

• Implement close of synapse viewer on close of report or abort of report
• Remove implementation of ‘comparison study’ in CRIS, and always open first exam in an event.
• Enable configuration of studies folder called, rather than it being hardcoded Name of folder rather than ‘all studies’ should be part of the OPTIONS.SYNAPSE4 configuration
• Warn users that accession number is not found when API returns that error
Enhancements
• In the F12 view integration, then call a different synapse window name in order to trigger a separate PACS view of those images to not move away from images opened for reporting. Should use a different folder as well (‘all studies’) or other user definable folder rather than the defined reporting folder.

Resolution:

1. The close report and abort report requirement had been handled by work done in response to a previous issue.

2. The comparison study implementation has been removed and the first exam is always opened in an event.

3. The default value for the reportFolder is still "All Images", but for the viewerFolder (used for F12 integration) the default is now "Alternative_Images". Both reportFolder and viewerFolder can be configured via the OPTIONS.SYNAPSE4 settings.

4. A user warning has been added when the code fails to find an accession number.

5. The window name used for F12 integration is hard coded as "Alternative Viewer".

PX-56 Report that does not appear on IMPAX

Reported in: 2.09.10p6 Fixed in: 2.09.10p7

Description: Re-sending Obs report messages does not re-trigger an interface message

Can resend normal reports (creates new trigger), however seems as though any exam that uses obs - you can mark the trigger as unprocessed and the interface will resend the message (going to suggest this as a workaround). However you cannot right click and resend the interface message. A new trigger will not be created.

Resolution: Right-click, resend report message will now create a new VERIFY trigger for obs reports as well as other kinds of reports.

PX-31 Trigger Order issue

Reported in: 2.09.10p6 Fixed in: 2.09.10p7

Description: It is possible for triggers to be processed by the interfaces in the wrong order. This can be due to both the triggers being inserted in the wrong order and inconsistency when triggers are selected from the database.

This causes issues, in particular, when an event is cancelled. Several triggers are created, including a CANCEL trigger, and this trigger should be inserted and selected last to ensure the cancel message is the last one received by third parties.

Changes to be made:

(1) Within any action in CRIS that creates multiple triggers, the order the triggers are inserted into the inttodo table should be changed so that CANCEL triggers are always inserted last.

(2) When inserting the triggers in a specific order, the milliseconds part of the time_due string should be used to ensure time_due is different for each of the triggers, and is in increasing order of insertion. To do this, the milliseconds part should be initially zeroed and should be incremented by one for each inserted trigger. E.g. If three triggers are inserted at 15:30 and 17 seconds their time_dues should be 153017001, 153017002 and 153017003.

(3) When selecting the triggers for processing they should be ordered by date_due and then time_due.

Resolution: When several triggers are inserted into the database at the same time, CANCEL triggers are now always inserted last. It is also ensured that the triggers are selected in the same order that they are inserted.

4.2Flexible forms

PX-50 Flexible fields won’t save.
Reported in: 2.09.10p6 Fixed in: 2.09.10p7
Description: If you try to enter a new row into the FlexibleFields table (other > flexiblefields > FlexibleFields) you get the following error while trying to save:

java.sql.SQLException: ORA-00904: "TYPE": invalid identifier.

The reason for this is because the field names in the FLEXFLD table in the database have changed and the application is still referencing the old version.

Resolution: New and updated flexible field records now save without error.

4.3Nuclear Medicine

PX- 37 Shift-Click on Vials table
Reported in: 2.09.10p6 Fixed in: 2.09.10p7

Description: In Nuclear Medicine the radiation symbol icon is used by the Trust to put on their daily vials received each morning. In the old version (2.09.10d) they disposed of the previous day's vials first by clicking on one vial and then pressing 'shift' and picking up the last vial to dispose of. The fields would all turn blue and they could then press dispose and all those vials would disappear. The 'shift' button does not work now. Shift-click on the last vial selects just that vial.

Resolution: We can select records contiguously (Shift/Select) and non-contiguous lists (Control/Select) for all copy/dispose/delete actions.

4.4Obstetrics

PX-34 Labelling of Graph Centiles
Reported in: 2.09.10p6 Fixed in2.09.10p7
Description: The values shown on the charts are the 5th, 50th and 95thpercentiles, displayed as the lower (red), middle (black) and upper (red) lines respectively."

Resolution: The user, via the XR settings, can now select one of the three common centile ranges.
The range chosen will be displayed on both the UI and printed graphs.
This mechanism can be turned on/off using the 'REPORT.ObsShowSDCentiles'.

New normal table – ‘CENTILES’. This tables provides the options for the ‘REPORT.ObsSDValue’ XR setting.

4.5Patient

PX-59 Ability to have a blank site as a default on user lists
Reported in: 2.09.10p6 Fixed in: 2.09.10p7
Description: The waiting/orders/request lists should be configured such that blank site could be saved as the default. Currently this is not the case, which means that events put on a waiting list at one site won't be seen at another site unless the user changes hospital or clears the default site from the site field at the bottom. The other filters can be blank - e.g. date, modality etc.

Resolution: With the 'SPINE.RestrictSitesToTrust' XR setting set to 'Yes' the value entered in the 'Site' field on all worklist will be saved to a 'user preference' including when the field is blank. If the field is blank and the list refreshed, only the appropriate events for that trust will be returned.
Only sites from the local trust will be available for selection.

With the 'SPINE.RestrictSitesToTrust' XR setting set to 'No' the value entered in the 'Site' field on all worklist will NOT be saved to a 'user preference'
When a worklist is first loaded, the default value obtained from the 'LOCATION.Hospital' XR setting will populate the 'Site' field. If the 'Site' field is blank and the list is refreshed, appropriate events from all trusts will be returned.
Sites from any trust will be available for selection.

PX-53 Incorrect Status Change
Reported in: 2.09.10p6 Fixed in: 2.09.10p7
Description: If a user has an event with multiple exams, and deletes an exam at the same time as performing an 'Undo attend', the status of the deleted exam is not correctly updated, and causes the event to remain on the request list.

Resolution: Users are now forced to save / cancel if one or more exams are deleted from an event, before being allowed to undo an attendance.

4.6 Post Processing

PX-115 Blank ‘Intended Clinician’ field in post processing screen
Reported in: 2.09.10p6 Fixed in: 2.09.10p7
Description: Manually entered 'Intended Clinician' value is not being saved during 'post processing' workflow.
Resolution: The user interface now reflects the true state of the 'Intended Clinician' field on the post processing screen, which is only accepted after pressing return.