CRIS 2.07.12b Specific Release Notes v1.2
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 2.07.12b Specific Release Notes v1.2
Copyright
General Information
1. Contents
2. Issue Summaries
2.1 New Features
2.2 Enhancements
2.2.1Patient
2.3 Issues Resolved
2.3.1Diary
2.3.2Dictation
2.3.3Event Details
2.3.4Menu Options
2.3.5Nuclear Medicine
2.3.6Reporting
2.3.7Statistics
2.3.8Stats Scheduler
2.3.9Worklists
2.3 House Keeping
3. Trust Implementation Issues
3.1 Standard issues:
3.2 Optional, for issues by request only:
4. Change Details
4.1Diary
4.2Dictation
4.3Event Details
4.4Menu Options
4.5Nuclear Medicine
4.6Patient
4.7Reporting
4.8Statistics
4.9Stats Scheduler
4.10Worklists
5. Known Issues
5.1 Known Issue Summaries
5.1.1Database
5.1.2Diary
5.1.3Dictation
5.1.4Event Details
5.1.5Interfaces
5.1.6Login
5.1.7Other
5.1.8Patient
5.1.9Post Processing
5.1.10Reporting
5.1.11Scanning
5.1.12Setup Tables
5.1.13Statistics
5.1.14Worklists
5.2 Known Issue Details
5.2.1Database
5.2.2Diary
5.2.3Dictation
5.2.4Event Details
5.2.5Interfaces
5.2.6Login
5.2.7Other
5.2.8Patient
5.2.9Post Processing
5.2.10Reporting
5.2.11Scanning
5.2.12Setup Tables
5.2.13Statistics
5.2.14Worklists
2. Issue Summaries
The following section summarises the changes made in this version of CRIS relative to release 2.07.12b. 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.2 Enhancements
2.2.1Patient
HSS Ref / LSP Ref / Description / By Request / Trust Interest211892 / - / Continuing with name searches after an exact match is found. / - / -
2.3 Issues Resolved
2.3.1Diary
HSS Ref / LSP Ref / Description / By Request / Trust Interest211739 / - / Error in LoadRecord java.sql.SQLException: Exhausted Resultset output to the Java Console - ONLY / - / -
211657 / - / Multi exam appointment is flagged as having moved when it has not yet been made. / - / -
211758 / - / Room slot incorrectly updated when amending data in the examination summary panel / - / -
2.3.2Dictation
HSS Ref / LSP Ref / Description / By Request / Trust Interest212485 / - / Dictation confirmation defaults to yes / - / -
212505 / - / Dictation record removed before logout confirmed / - / -
212411 / - / Cannot add addendum to archived dictation / - / -
2.3.3Event Details
HSS Ref / LSP Ref / Description / By Request / Trust Interest211681 / - / It is possible to give an exam a different status from another exam with same event / - / -
2.3.4Menu Options
HSS Ref / LSP Ref / Description / By Request / Trust Interest211826 / - / Null Pointer Exception thrown in Nuclear Contamination when specifying a date and enter is pressed / - / -
2.3.5Nuclear Medicine
HSS Ref / LSP Ref / Description / By Request / Trust Interest211724 / - / Vial creation for future date and time is incorrect when the Copy Number function > 1 / - / -
2.3.6Reporting
HSS Ref / LSP Ref / Description / By Request / Trust Interest212653 / - / Inaccuracy in Printing and viewing Obs Graphs / - / -
212486 / - / Report confirmation defaults to yes / - / -
210916 / - / Verified reports with blank verified by. / - / -
211927 / - / Console error when entering a second clinician to flag as Unchecked an event in Batch Verify / - / -
2.3.7Statistics
HSS Ref / LSP Ref / Description / By Request / Trust Interest212226 / - / It is not possible to remove a Y Axis field from a total line / - / -
2.3.8Stats Scheduler
HSS Ref / LSP Ref / Description / By Request / Trust Interest212061 / - / Stopping long stats with large sql query / - / -
2.3.9Worklists
HSS Ref / LSP Ref / Description / By Request / Trust Interest212508 / - / Session Mangement fail to Import Events from a csv file. / - / -
211714 / - / Create a new session for an event generate error message while using mouse to move focus between fields Title and Type / - / -
211806 / - / Comments with carriage return in event fail the importing of event to session / - / -
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:
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.1Diary
211739 - Error in LoadRecord java.sql.SQLException: Exhausted Resultset output to the Java Console - ONLY
Reported in: 2.07.12 Fixed in: 2.07.12b Resolved by: mcarter (Mick Carter)
Description: ExhaustedResultset error is output to the Java Console (not in the application) when adding an event to the Diary using the Add to Diary function in Event Details. This places the event on the scratchpad.
Selecting the entry on the Scratch Pad and pressing Send displays the Event Details screen and the error is output in the console.
Resolution: In the diary, when send is pressed on an event yet to be created, CRIS will refrain from loading the event from the event table in the database. An event that is not yet created would be an event that has been sent straight to the diary from the event detail screen and has no status history.
211657 - Multi exam appointment is flagged as having moved when it has not yet been made.
Reported in: 2.07.12 Fixed in: 2.07.12b Resolved by: sjennings (Steven Jennings)
Description: If a multi exam appointment is added to the diary, and one of the exams is dragged to an appointment slot but the other isn't, when the exam that has been dragged is selected in the slot, a message appears informing that the other exam on the appointment has moved, when it actually has not yet even been made.
Resolution: When a multi exam event is added directly to the diary, and an appointment has been made for only one of the exams, reselecting the exam from the slot it is booked into, will not warn that the other exam on the event has moved.
211758 - Room slot incorrectly updated when amending data in the examination summary panel
Reported in: 2.07.12 Fixed in: 2.07.12b Resolved by: mcarter (Mick Carter)
Description: When an existing appointment is updated using the examination summary panel at the bottom of the screen with an unavailable time slot for the room and Save is pressed a message 'Unable to save changes. Time n in room n is not an available slot time' is correctly displayed. (N.B. The text of the message is slightly incorrect and should be changed where it says slot time to time slot.
On pressing OK on the message the exam is moved to the specified time slot and out of view and the amended time remains displayed in the exam Time field. This should not happen.
On pressing Refresh the exam is moved back to the original time slot but the exam Time field is not set back to what it was originally until the exam is selected in the room slot.
Resolution: When using the exam detail panel on the diary it should not update the exam time slot if the time slot is not valid
4.2Dictation
212485 - Dictation confirmation defaults to yes
Reported in: 2.07.12 Fixed in: 2.07.12b Resolved by: bcarroll (Ben Carroll)
Description: If you start a dictation and try to log out without saving the confirmation that appears defaults to yes.
Resolution: Default action is now the passive choice. Usually this is the 'No' option.
212505 - Dictation record removed before logout confirmed
Reported in: 2.07.12 Fixed in: 2.07.12b Resolved by: gglover (Gary Glover)
Description: If a user dictates an undictated event but attempts to logout before saving then the dictation record is deleted before they confirm the logout.
Resolution: Now whenever the user logs out either after creating a new dictation or amending an existing one, the workflow is cleared down.
When logging back in, the user starts at the main 'welcome' screen.
212411 - Cannot add addendum to archived dictation
Reported in: 2.07.12 Fixed in: 2.07.12b Resolved by: bcarroll (Ben Carroll)
Description: It is not possible to access the dictation screen when the dictation has been archived.
Resolution: Can now add addendums to archived dictations.
4.3Event Details
211681 - It is possible to give an exam a different status from another exam with same event
Reported in: 2.07.12 Fixed in: 2.07.12b Resolved by: mcarter (Mick Carter)
Description: Exam's of the same event should never be of different status. It is possible to make this happen by creating an event with two exams and using the diary to drag one exam to a slot and leaving another exam behind on the scratch pad.
Resolution: Exams of the same event should always have the same status. If an event has two exams and one is dragged on to a diary slot for today, now both exams will share the same "appointment" status.
4.4Menu Options
211826 - Null Pointer Exception thrown in Nuclear Contamination when specifying a date and enter is pressed
Reported in: 2.07.12 Fixed in: 2.07.12b Resolved by: mcarter (Mick Carter)
Description: Need to correctly configure the nuclear contamination page and check it still works.
When a date is entered in the Date field and pressed a 'Could Not Read Contamination setup - java.lang.NullPointerException is generated.
The error message has to be accepted twice for it to be cleared.
Also there is a button above the Done button which has no label and does not seem to do anything functionally.
Resolution: Now an error dialog will appear before the Nuclear Contination tab appears if there is no format (in the setup tables) set for XR.CONTAMINATION. The XR.CONTAMINATION should be set for this tab to function correctly. An example of XR.CONTAMINATION would be...
AREA=SCREEN,RECEPT,WAIT
EQUIP=SCANNER,TABLE,COMPUTER
STAFF=BS,AF,MD
AREA.SCREEN=Screening Room
AREA.RECEPT=Reception Area
AREA.WAIT=Waiting Room
EQUIP.SCANNER=Scanner
EQUIP.TABLE=Examination Table
EQUIP.COMPUTER=Screening room computer
STAFF.BS=Bob Smith
STAFF.AF=Alfred Franks
STAFF.MD=Michelle Dawson
4.5Nuclear Medicine
211724 - Vial creation for future date and time is incorrect when the Copy Number function > 1
Reported in: 2.07.12 Fixed in: 2.07.12b Resolved by: mstevenson (Matthew Stevenson)
Description: When creating Vials for a future date or time and setting the Copy Number field to > 1, causes the future date and time that is set to be ignored and sets the Creation Date / Creation Time equal to current date and or time.
Resolution: Vial date for future dates corrected when copy number function > 1.
4.6Patient
211892 - Continuing with name searches after an exact match is found.
Reported in: 2.07.12 Fixed in: 2.07.12b Resolved by: cturner (chris turner)
Description: There is an XR setting that allows CRIS to continue with the remaining name searches even after an exact match has been found. However this does not do the PAS patient searches when an exact match has been found on CRIS.
Resolution: SearchPas checks GENERAL_CONT_SEARCH_AFTER_MATCH XR setting when searching.
4.7Reporting
212653 - Inaccuracy in Printing and viewing Obs Graphs
Reported in: 06.12 Fixed in: 2.07.12b Resolved by: mwarren (Mark Warren)
Description: When printing obs graphs, it has been noted the points can appear to move in relation to the graph curves when comparing the on screen and printed graphs. Investigation has shown that the plotted point is in exactly the same place, but the lines on the graph are not in the same place when viewed on screen and when printed.
Resolution: The printing of obstetric graphs has been made more accurate.
212486 - Report confirmation defaults to yes
Reported in: 2.07.12 Fixed in: 2.07.12b Resolved by: bcarroll (Ben Carroll)
Description: If you try and access a report that is already being transcribed then the confirmation defaults to yes.
Resolution: Report confirmation messages now default to the passive option. Depending on the wording of the question this is usually 'No'.
210916 - Verified reports with blank verified by.
Reported in: 06.12 Fixed in: 2.07.12b Resolved by: gglover (Gary Glover)
Description: The report verified by value can be left blank after a report has been verified.
Two radiologists load the same report into batch verify and the second radiologist ignores the warning saying that they are doing something potentially dangerous.
Then the first radiologist modifies and verifies the report unaware of what the second radiologist is doing.
The second radiologist then modifies and verifies the report again ignoring another warning that the report has been modified by someone else.
This second save has wrongly removed the verified by code.
Resolution: With two CRIS applications (not two instances on the same PC) running and two different radiologists trying to verify the same report, the report in question is now updated from the database prior to verification. Also the database is amended correctly, showing the correct 'verified by' and 'last verified by' information.
211927 - Console error when entering a second clinician to flag as Unchecked an event in Batch Verify
Reported in: 2.07.12 Fixed in: 2.07.12b Resolved by: mcarter (Mick Carter)
Description: A console error (only) is generated - see Additional Information for error details - when attempting to flag a report as Unchecked from Batch Verify where the second clinician being entered is the same as the Reported By clinician.
Resolution: Now the correct error dialog will appear when the user selects the second clinician to be the same as the first clinician when doing an unchecked batch verify.
4.8Statistics
212226 - It is not possible to remove a Y Axis field from a total line
Reported in: 2.07.12 Fixed in: 2.07.12b Resolved by: sjennings (Steven Jennings)
Description: When trying to remove the Y axis field of a total line it appears to work, but when the stat is run or saved, the original value is still present in the field. It is possible to change the value in the field, but not remove it.
Resolution: The ability to remove an entry from the Y Axis field of a statistical report total line has been enabled once more.
4.9Stats Scheduler
212061 - Stopping long stats with large sql query
Reported in: 06.12 Fixed in: 2.07.12b Resolved by: sjennings (Steven Jennings)
Description: The query which currently gets long running stats in order to warn or stop them when they will take too long to complete, uses the gv$sql.sql_text field. This field does not always return the required full query, but only the first 1000 characters. This can mean that the text returned does not always contain all the information required, and long running stats are not always stopped.
Resolution: The query which checks for long running stats, now interrogates the full sql being run, rather than just the first 1000 characters. This allows the stat identifiers to appear anywhere in the query, and it will still be stopped, rather than the identifiers having to appear in the first 1000 characters.
4.10Worklists
212508 - Session Mangement fail to Import Events from a csv file.
Reported in: 2.07.12 Fixed in: 2.07.12b Resolved by: sjennings (Steven Jennings)
Description: Session Mangement Import function fails to import Events from a .csv file when the position of the Event_key in the file changes position.
Resolution: If a blank field is contained within a stat output, previous to the event key field, the file can still imported successfully into a session in the session management module.
211714 - Create a new session for an event generate error message while using mouse to move focus between fields Title and Type
Reported in: 2.07.12 Fixed in: 2.07.12b Resolved by: sjennings (Steven Jennings)
Description: Create a new session for an event from scratch and enter text in Title field then move the focus to Type field via mouse, an error message is generated indicating: 'Invalid session details. Session must have a title.'
Resolution: A message informing that the session does not have a title is no longer displayed, when adding an event to a new session and using the mouse to move the focus between fields on the screen.
211806 - Comments with carriage return in event fail the importing of event to session
Reported in: 2.07.12 Fixed in: 2.07.12b Resolved by: sjennings (Steven Jennings)
Description: Add some comments for an event with carriage return. Then create and save a stat to output the test event. When import the saved stat file to Session, an error message pops up with title 'Failed to Import Event to Session' and content 'java.util.NoSuchElementException'.
Resolution: The importing of events into a session now works successfully when there is data in the import file, that stretches over multiple lines, and contains speech marks.
5. Known Issues
This section provides a list of outstanding issues in this version of CRIS.
5.1 Known Issue Summaries
5.1.1Database
HSS Ref / LSP Ref / Description / By Request / Trust Interest211448 / - / Verify and remove HTML schema from the database / - / -
5.1.2Diary
HSS Ref / LSP Ref / Description / By Request / Trust Interest211764 / - / Adding an exam in the diary causes errors / - / -
211067 / - / Null Pointer Exception output to the Java Console when using Search Forward with 2 exams one of which is ignored / - / -
5.1.3Dictation
HSS Ref / LSP Ref / Description / By Request / Trust Interest211054 / - / No error message generated when deleting a dictation from dictation list after disconnecting with LAN / - / -
212376 / - / Still able to Dictate From Day List / - / -
212695 / - / Attendance Date and Time on Dictation Page / - / -
5.1.4Event Details