1€¦ · web viewcris release notes 2.09.10t1g specific d1.0.docx cris version 2.09.10t1g change...

CRIS Release Notes 2.09.10 T1G specific

Copyright© Healthcare Software Solutions 2014Registered Office: 3rd Floor i2 Mansfield, Hamilton Court, Oakham Business Park, Mansfield, NG18 5FB

These materials are or comprise restricted and proprietary confidential information of Healthcare Software Solutions. Disclosure to or use by the recipient shall not convey any intellectual property rights in these materials. The right to use these materials by the recipient is subject to restrictions and limitations contained in the Provision of Integrated Care Record System and Associated Services Agreement and related agreements.

ConfidentialityAll information in this document is provided in confidence for the sole purpose of adjudication of the document and shall not be used for any other purpose and shall not be published or disclosed wholly or in part to any other party without HSS prior permission in writing and shall be held in safe custody. These obligations shall not apply to information which is published or becomes known legitimately from some source other than HSS. Many of the product, service and company names referred to in this document are trademarks or registered trademarks. They are all hereby acknowledged.

Document Control

Title CRIS Release Notes 2.09.10T1G specificAuthor Helen Turner Date Created 19/01/2017File Ref. document.docxCRIS Version 2.09.10T1GChange HistoryIssue Date Author / Editor Details of ChangeD1.0 19/01/2017 Helen Turner 2.09.10 T1G initial draft.V1.0 26/01/17 Helen Turner 2.09.10 T1G V1.0V2.0 30/01/2017 Gary Glover Additional issue, CRIS-1792, included

Review Date

© Healthcare Software Solutions 2014 All Rights Reserved Commercial In ConfidenceEffective Date – 10/07/2014HSS Doc ref: document.docx of 13

Contents

1. Introduction.............................................................................................................41.1. Purpose.............................................................................................................................. 41.2. Audience............................................................................................................................ 4

2. Database..................................................................................................................52.1. Resolved Issue....................................................................................................................5

3. Diary........................................................................................................................63.1. Resolved Issue....................................................................................................................6

4. Dictation..................................................................................................................74.1. Resolved issue....................................................................................................................7

5. DTIs..........................................................................................................................85.1. New Functionality.............................................................................................................. 85.2. Resolved issue....................................................................................................................8

6. Obstetrics................................................................................................................96.1. New Feature.......................................................................................................................9

7. Event Details..........................................................................................................107.1. New Functionality............................................................................................................10

8. Vetting...................................................................................................................118.1. New Feature.....................................................................................................................118.2. Resolved Issue..................................................................................................................11

9. Worklists................................................................................................................139.1. Resolved Issue..................................................................................................................13


1. Introduction1.1. Purpose

This document will outline the functional changes made to this release. It will detail any new features, enhancements to existing functionality and list changes made due to existing functionality not working as expected.

1.2. AudienceThis document is primarily for the customer, so they have a clear understanding of what is included compared to previous releases. Internal stakeholders such as sales, product/client managers and Release Management personnel will also have visibility to this document and be involved in the review process.


2. Database2.1. Resolved Issue

CRIS-1742 Reporting xrvalue checkDescription When loading into a new report, the call to the xrvalue() function is performed six times. It is

called a further time when the report is finalized.Resolution There is only ONE database access for this XR setting. This is when CRIS is started.

From then on, the status of the XR setting is checked, but no call to the database is made to do this. Changes to any XR setting are only available if CRIS is restarted. This will enhance the overall database performance due to less database calls within reporting workflow.

Fixed in 2.09.10 T1G


3. Diary3.1.Resolved Issue

CRIS-1667 Auto commit diary printing error.Description Intermittent auto commit errors can be seen when printing a list of appointment letters from the

scratchpad in T1+ CRIS releases. Sometimes, mid printing a batch of letters the following error occurs: This stops any further letters from printing. It's also possible to click ok on the error, however if the user clicks to print and clear selection, some letters won't be printed but are lost from the scratchpad, therefore potentially the patient might not receive a letter.

Resolution A change was made to the way the storing of items is handled that have been requested to be printed. Now, when requesting the printing of letters from the Diary, the Printing thread handles the storage of the letter immediately after the successful printing of it. This avoids the conflicts that were being experienced when attempting to execute each of the storing and printing tasks on separate threads.



4. Dictation4.1.Resolved issue

CRIS-1670 Dictation list SQL containing colon in time valueDescription When a report is opened from the dictation list, the event should be removed from the list.

However this is not the case since 2.09.10S2 due to it creating incorrect SQL containing a colon in the time field.

Resolution Having ensured that the time value no longer contains a colon separating hours and minutes, the opened report for dictation has now fallen off the users dictation list and also that when another user logs in to the system, the patient is not on the dictation list to be picked up for reporting.



5. DTIs 5.1.New Functionality

CRIS-1668 Philips DTI Change – Clear down PACS when images are not availableDescription When a user opened a PACS study with an unknown accession in CRIS, and then opened a CRIS

study with a known accession in PACS. Due to the nature of multiple viewers on PACS, the studies were not cleared and switching between them didn’t keep the CRIS or PACS in context but offered a warning.

Resolution If you have a study open in PACS, unknown to CRIS (There is a warning), then in CRIS, an event is opened for reporting (known accession), it will open the corresponding images in context. If the user then switches studies in PACS, to the study images that are unknown in CRIS, CRIS validates this by doing one of 2 actions. If there’s no changes to report in CRIS that known to PACS, it clears the CRIS reporting page and leaves CRIS without any patients open. If there are changes to the report, it allows you to save report. "Are you sure you wish to clear without saving? Yes or No." And the user should follow the appropriate action. Thus they remain in context for reporting.


5.2.Resolved issue

CRIS-1755 Change the value of sync.PACSInitialize SectraDescription Intermittent failure of the DTI between CRIS and SECTRA PACS.Resolution Timeout value increased from 40 to 10000 ms.Fixed in 2.09.10 T1G


6. Obstetrics6.1. New Feature

CRIS-1624 3VT VIEW - UPDATE TO CARDIAC PROTOCOLDescription The 3VT view was added to the FASP’s fetal cardiac protocol. This brings the number of views that

sonographers have to take of the heart of the fetus to 5. This applies to every pregnant woman at the 18-20 week scan, which is when the fetus is checked for any major physical abnormalities.

Resolution 3VT field added to ANATFA, ANOMFA, DETFA, ANATNW, DETNWFixed in 2.09.10 T1G


7. Event Details7.1. New Functionality

CRIS-1444 Reading GS1 wristbands within CRISDescription CRIS to be able to read the GS1 2D datamatrix code and use the encoded

Information to verify the patient’s identification and open the patient’s event page in CRIS. Resolution Implemented a barcode analysis on the 1st 6 fields in the PatientSearch panel. When the GS1

barcode is scanned it brings up the patient events page.Fixed in 2.09.10 T1G


8. Vetting8.1.New Feature

CRIS-1736 Addition of a count field in/near the status comment when a practitioner rejects an examDescription We need a count field in/near the status comment when a practitioner rejects an exam. Currently

only 200 characters will display in the status comment and it is difficult to judge how many characters have been inputted.

Resolution As user type’s, text into the status comment (external) field, a visible counter counts down from 200. As the text length approaches the limit, the count starts to flash, as text is typed and if the limit is exceeded the background colour changes and a tool tip help is shown.


CRIS-1654 Rename Status comment and Reject Reason BoxDescription When rejecting in vetting if you enter a reason for rejection in the

Reject reason box - the text does not appear in the HL7 message (only text From the status comment box appears in the message). By accident, occasionally radiologists will enter a reason for rejection in the reject reason box, which is internal to CRIS only.

Resolution When rejecting an item during vetting, we’ve renamed the text boxes to be "Status Comment (External)" and "Additional Comment (Internal)" for clarification to the user.


8.2.Resolved Issue

CRIS-1747 Vetting Issues - delays vetting slows downDescription Each event that is vetted gets the response that the cache is dirty and it reloads the exam

protocols table and we can see this taking longer both in ms and elapsed time between the dirty comment and the next timestamp in the log.

Resolution Several changes were made, eliminating a range of exceptions and ensuring that the logs are much easier to handle. Note: Further system improvements to the vetting module will be available on 2.10.00 June 2017.



CRIS-1792 'Required by' date option not being refreshed correctly on 'Vetting' listDescription When the 'Required by' radio button option is selected in the 'Display' panel on the 'Vetting' list,

the 'Required' column is displayed in the list with the 'required by' date for each event. If the 'List' button is now selected and the list refreshed, the 'required by' date data is lost. The only way to retrieve the data is to select either one of the 'Days Wait' or 'Weeks Wait' options.

Resolution The 'List' button only uses the values entered in the filters at the bottom of the screen, it doesn't filter any data depending on the options selected in the 'Display' panel. So selecting the options will determine what columns are displayed in the table.



9. Worklists9.1.Resolved Issue

CRIS-1716 Staff list search not finding active staff as it errors as old staff thread is still runningDescription The system needs to be changed to allow the staff table in memory to be searched whilst the

thread to load inactive staff is still running as this can take quite a while in large consortiums with tens of thousands of users.

Resolution The change here is to ensure that the staff are read correctly from this data structure whilst inactive staff entries can be added concurrently on the separate thread, and the exception is prevented.



1€¦ · web viewcris release notes 2.09.10t1g specific d1.0.docx cris version 2.09.10t1g change...

Documents