CRIS Release Notes 1.06.12k specific changes v 1.1
Copyright
© Healthcare Software Systems 2004 Registered Office: Priory Road, Mansfield-Woodhouse, Nottinghamshire, NG19 9LP.
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 Release Notes 1.06.12k specific changes v 1.1
Copyright
General Information
1. Contents
2. Issue Summaries
2.1 New Features
2.1.1 Interfaces
2.2 Enhancements
2.3 Issues Resolved
2.3.1 Database
2.3.2 Diary
2.3.3 Interfaces
2.3.4 Nuclear Medicine
2.3.5 Patient
2.3.6 Printing
2.3.7 Reporting
2.3.8 Statistics
2.3.9 Worklists
2.3 House Keeping
3. Trust Implementation Issues
3.1 Standard issues:
3.2 Optional, for issues by request only:
4. Change Details
4.1 Database
4.2 Diary
4.3 Interfaces
4.4 Nuclear Medicine
4.5 Patient
4.6 Printing
4.7 Reporting
4.8 Statistics
4.9 Worklists
5. Known Issues
5.1 Known Issue Summaries
5.1.1 Diary
5.1.2 Dictation
5.1.3 Other
5.1.4 Reporting
5.1.5 Voice Recognition
5.2 Known Issue Details
5.2.1 Diary
5.2.2 Dictation
5.2.3 Other
5.2.4 Reporting
5.2.5 Voice Recognition
2. Issue Summaries
The following section summarises the changes made in this version of CRIS relative to release 1.06.12j. 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.
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.1.1 Interfaces
HSS Ref / LSP Ref / Description / By Request / Trust Interest207259 / - / send date request was received on the pacs interface / - / -
2.2 Enhancements
2.3 Issues Resolved
2.3.1 Database
HSS Ref / LSP Ref / Description / By Request / Trust Interest206862 / - / Blank verified status / Yes / -
2.3.2 Diary
HSS Ref / LSP Ref / Description / By Request / Trust Interest207707 / - / Slow First Diary load / - / Yes
207394 / - / Refreshing exams in diary does not work for attended appointments. / - / Yes
2.3.3 Interfaces
HSS Ref / LSP Ref / Description / By Request / Trust Interest207775 / - / STATUS messages sometimes fail on order comms system / - / -
207499 / - / Exams inbound interface & PAS interface create duplicate records at BMI / - / -
207216 / - / CRIS status messages fail when enabled on the PAS outbound interface / - / -
2.3.4 Nuclear Medicine
HSS Ref / LSP Ref / Description / By Request / Trust Interest207586 / - / Patient demographics do not display when adding a nuclear med injection via daylist / - / -
2.3.5 Patient
HSS Ref / LSP Ref / Description / By Request / Trust Interest207785 / - / XR setting RECEPT.RestrictChangePatPas does not work for CRIS patients linked to multiple PAS records / - / Yes
207456 / - / Patient Num of Events Counter not updating / - / Yes
200334 / - / Navigation from DOD cursor disappears / - / -
2.3.6 Printing
HSS Ref / LSP Ref / Description / By Request / Trust Interest207779 / - / Fife obstetric reports with CRL only do not print CRL graph (06.12k) / - / Yes
207780 / - / Obstetric graphs print current date line rounded to nearest week (06.12k) / - / Yes
2.3.7 Reporting
HSS Ref / LSP Ref / Description / By Request / Trust Interest207628 / - / Reports saved with blank "reported_by" / - / Yes
2.3.8 Statistics
HSS Ref / LSP Ref / Description / By Request / Trust Interest207611 / - / STATUS.Comment and EVENTS.Comment fields causes stat to error / - / Yes
207514 / - / Selection criteria on REPORTS.REPORTED_BY / - / -
2.3.9 Worklists
HSS Ref / LSP Ref / Description / By Request / Trust Interest207574 / - / Dialog box needs removing from orders list / - / -
207615 / - / Unreported list automatically refreshed from database when dictating / - / -
2.3 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:
206862 - Blank verified status
Required Trust Action: Request this patch is run to update database config.
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.1 Database
206862 - Blank verified status
Reported in: 06.12 Fixed in: 06.12k Resolved by: shodson (simon hodson)
Description: It is possible to create a report with no verification status. This means the report does not appear on the unverified report list because it does not have the status of unverified.
Resolution: Database column cris_reports_tbl.verified is now defaulted to 'N' by the database if it is left blank by the application. No client software change required for this fix. A small database patch required to be run. No downtime required for this patch to be installed but it is recommended that this is run at a quiet time outside of normal working hours.
Trust Implementation Issues: Request this patch is run to update database config.
4.2 Diary
207707 - Slow First Diary load
Reported in: 06.12 Fixed in: 06.12k Resolved by: dhall (David Hall)
Description: The first time the diary is opened after CRIS has been started can be slow if the user opens the diary without telling the diary what sort of exam to use as the basis for the diary layout by using the add to diary function.
Without knowing what sort of exam setup should be displayed the diary will load all exams and rooms for every site on the system which could take quite a while to download.
None of this data will be displayed until a room or exam type is chosen, at which point CRIS will re-load this data again.
Resolution: Stopped CRIS querying for exams that will not be displayed if the diary is created without an exam template being selected with the "Add To Diary" function.
The exams will still be queried as soon as a room or exam is selected in the same way as before.
207394 - Refreshing exams in diary does not work for attended appointments.
Reported in: 06.12 Fixed in: 06.12k Resolved by: sjennings (Steven Jennings)
Description: The refreshing of the exams in the diary when they are selected, does not work for attended appointments. When selected, they still just show in the diary as appointments rather than attendances, and they can therefore be moved and rebooked, until the whole diary page has been refreshed manually.
Resolution: The refreshing of the appointments in the diary when they are selected, is now applied to the attended flag successfully, so that an appointment will now show as an attendance when it is selected, if it has been attended since the diary page was loaded.
4.3 Interfaces
207775 - STATUS messages sometimes fail on order comms system
Reported in: 06.12 Fixed in: 06.12k Resolved by: ashields (Alan Shields)
Description: When CRIS STATUS triggers are configured to be sent via the order comms interface the message will fail if there are multiple exams on an event
Resolution: Status triggers were failing when multiple exams existed on an event because the interface was looping through all exams and re using the same cache entry. This caused a cache exception on the second (and subsequent) exams because the cached exam (the first exam) did not match the second etc.
There is actually no need to loop through the exams as a separate STATUS trigger is produced for each exam so now the interfaces just generate a single message for the exam stated in the trigger.
207499 - Exams inbound interface & PAS interface create duplicate records at BMI
Reported in: 06.12 Fixed in: 06.12k Resolved by: ashields (Alan Shields)
Description: The ultragenda system at BMI does not send patient registration messages at the time that a patient is registered but holds on to them until a radiology request is created. It then sends the registration and the event message together.
Since the incoming events interface at BMI is configured to create a patient if one does not exist the interaction between the two interfaces means that sometimes one interface will query for a patient after the other interface has already queried and made the decision to create a new patient but before the new patient is created.
Resolution: Added configurable patient lock functionality for PAS interface. If LockPatientCreate is set to true patient updates are syncronized to a public variable in the PAS interface.
This functionality is only required at sites where more than one interface can write to the same PAS patient mirror table and is currently only required on BMI sites.
207259 - send date request was received on the pacs interface
Reported in: 06.12 Fixed in: 06.12k Resolved by: ashields (Alan Shields)
Description: Additional functionality required for the PACS ( and other outbound HL7 interfaces) to send the date the request was received on outbound order and result messages.
Resolution: send the request received date in ORC:15
207216 - CRIS status messages fail when enabled on the PAS outbound interface
Reported in: 06.12 Fixed in: 06.12k Resolved by: ashields (Alan Shields)
Description: If the PAS outbound interface has generation of HL7 status messages as a result of CRIS status events enabled these triggers fail during processing.
Resolution: changed ExamBean.getEvent to set the examsLoaded state.
4.4 Nuclear Medicine
207586 - Patient demographics do not display when adding a nuclear med injection via daylist
Reported in: 06.12 Fixed in: 06.12k Resolved by: cking (Chris King)
Description: If a patient is highlighted from the daylist and 'nuc med' injection is selected, the patient demographics do not appear. It is possible to continue and assign the injection, without being able to confirm patient details.
Resolution: The patient demographics are now displayed when adding a nuclear medicine injection via the daylist.
4.5 Patient
207785 - XR setting RECEPT.RestrictChangePatPas does not work for CRIS patients linked to multiple PAS records
Reported in: 06.12 Fixed in: 06.12k Resolved by: aslack (Alexander Slack)
Description: The XR setting RECEPT.RestrictChangePatPas is used to control whether users are allowed to add events to patients who are not linked to a PAS patient at their hospital. If this setting is turned on then users are sometimes not allowed to add events to patients who are linked to a PAS record. This issue only happens if the patient is linked to more than one PAS record at different trusts and their PAS record is not the first in the list.
Resolution: The XR setting now works correctly for all trusts when a CRIS patient is linked to multiple HIS records at different trusts.
207456 - Patient Num of Events Counter not updating
Reported in: 06.12 Fixed in: 06.12k Resolved by: aslack (Alexander Slack)
Description: The number of events field in the patient record is not being incremented when a new event is created unless the event is created as an attendance.
This field is not actively used in CRIS to control any CRIS behaviour and is for user information only.
Resolution: Now fixed in 0612h and head
200334 - Navigation from DOD cursor disappears
Reported in: HEAD Fixed in: 06.12k Resolved by: cking (Chris King)
Description: When you Tab, or arrow from Date of Death field the cursor disappears.
Resolution: The tab, enter or arrow keys can now be used to navigate to and from the DOD field on the patient details screen.
4.6 Printing
207779 - Fife obstetric reports with CRL only do not print CRL graph (06.12k)
Reported in: Fixed in: 06.12k Resolved by: aslack (Alexander Slack)
Description: At Fife, early scans with a CRL but no other measurements do not print the CRL graph, but instead the four others without any data points.
Resolution: Fife Obstetric reports with CRL set will now print the CRL graph.
207780 - Obstetric graphs print current date line rounded to nearest week (06.12k)
Reported in: 06.12 Fixed in: 06.12k Resolved by: aslack (Alexander Slack)
Description: The event date on printed obstetric graphs is represented by a solid vertical line though the latest data point. However, since 06.12, this line only goes though the start of the week of the event, not the current day.
Resolution: Graphs now correctly place the current date line in obstetric graphs.
4.7 Reporting
207628 - Reports saved with blank "reported_by"
Reported in: 06.12 Fixed in: 06.12k Resolved by: aslack (Alexander Slack)
Description: Some reports have been saved with blank reported by value. This only occurs if the event has multiple exams AND the user enters a blank report with blank lines for one of the exams AND they have more than one copy of CRIS open AND the both copies of CRIS have not had the reporting session set to the same reporter value.
Resolution: When using multiple CRIS windows and entering blank reports as a secretary, CRIS will no longer save the report with a blank Reported By value for the report.
4.8 Statistics
207611 - STATUS.Comment and EVENTS.Comment fields causes stat to error
Reported in: 06.12 Fixed in: 06.12k Resolved by: sjennings (Steven Jennings)
Description: If the old EVENTS.Comment field from the 06.04 version of software is used when running an old stat (first run in 06.04), the stat fails to run. The same is true for the STATUS.Comment field.
Resolution: If a stat had used the EVENTS.COMMENT field successfully in 06.04, the stat will now work with same field. Previously this field had to be removed, and the new EVENTS.COMMENT field had to be re-selected. The STATUS.Comment field will also now work successfully again.
207514 - Selection criteria on REPORTS.REPORTED_BY
Reported in: 06.12 Fixed in: 06.12k Resolved by: sjennings (Steven Jennings)
Description: If the REPORTS.REPORTED_BY field is used as a value in the selection criteria of a stat (dragged and dropped into box rather than added with a double click), the query generated is invalid.
Resolution: Having a selection criteria in a statistical report, where the value is the REPORTS.REPORTED BY field, now no longer gives an error and causes the stat to fail.
4.9 Worklists
207574 - Dialog box needs removing from orders list
Reported in: 06.12 Fixed in: 06.12k Resolved by: aslack (Alexander Slack)
Description: When creating an event from an order for a HIS patient not already linked to a CRIS patient, a dialog appears asking if the user is sure they want to create a new CRIS patient.
This new dialog has been added in 6.12 and is not necessary and should be removed. i.e. CRIS should always link to an existing CRIS patient or create a new patient when an order is selected for a PAS patient who is not linked to a CRIS patient without the user needing to confirm this action.
Resolution: New patients are now created automatically if there is not an appropriate existing CRIS patient for linking.
207615 - Unreported list automatically refreshed from database when dictating
Reported in: HEAD Fixed in: 06.12k Resolved by: bcarroll (Ben Carroll)
Description: A full database refresh is being performed when dictating from the unreported tab of the report info list. When the dictation is finished the list should be updated with the dictation icon but a database refresh should not be preformed unless the user manually refreshes the list.
Resolution: Database refresh removed, list is updated with a dictation icon but no database queries are executed on the list itself.
5. Known Issues
This section provides a list of outstanding issues in this version of CRIS.
5.1 Known Issue Summaries
5.1.1 Diary
HSS Ref / LSP Ref / Description / By Request / Trust Interest200278 / - / Simultaneous Diary searching forward. / - / -
5.1.2 Dictation
HSS Ref / LSP Ref / Description / By Request / Trust Interest206229 / CSC Ref - 194345 / Order Comments on Dictation screen / - / -
5.1.3 Other
HSS Ref / LSP Ref / Description / By Request / Trust Interest200505 / - / Application Update Issues / - / -
5.1.4 Reporting
HSS Ref / LSP Ref / Description / By Request / Trust Interest204541 / - / Unverifying during batch verify session for obstetric exams / - / -
5.1.5 Voice Recognition
HSS Ref / LSP Ref / Description / By Request / Trust Interest206299 / - / Assigned Dragon VR User Changing. / - / -
5.2 Known Issue Details
5.2.1 Diary
200278 - Simultaneous Diary searching forward.
Reported in: 06.04
Description: If users on separate screens select auto search forward on different PC's at same time for same type of exam then too many of the diary slots can be set as allocated.
5.2.2 Dictation
206229 - Order Comments on Dictation screen
Reported in: 06.12
Description: The Event comments and clinical history text are not displayed on the dictation page if the exams have come from an order.
Incident No. CSC Ref - 194345
5.2.3 Other
200505 - Application Update Issues
Reported in: 06.04
Description: On a limited number of PC's during a software update the altered CRIS startup script, cris.jnlp, does not download to the PC. This can cause CRIS to not function correctly after an update. However uninstalling and re-installing CRIS does successfully download all parts of the update.
5.2.4 Reporting
204541 - Unverifying during batch verify session for obstetric exams
Reported in:
Description: When using batch verify on obstetric exams the user cannot undo the verify action on an obstetric exam by using the right click option on the verify list.
5.2.5 Voice Recognition
206299 - Assigned Dragon VR User Changing.
Reported in:
Description: Occasionally a CRIS users assigned Dragon id seems to change to someone elses.
Last Updated: HSS 24/05/2019 Healthcare Software Systems – Commercial in Confidence Page 1 of 13