CRIS Release Notes 2.09.10t1a specific
Copyright
© Healthcare Software Solutions 2014
Registered 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.
Confidentiality
All 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.10t1a specific
Author
Gary Glover
Date Created
18/09/2015
File Ref.
CRIS Release Notes 2.09.10t1a specific D1.0.docx
CRIS Version 2.09.10t1a
Change History
Issue
Date
Author / Editor
Details of Change
D1.0
18/09/2015
Gary Glover
2.09.10t1a first draft
Review Date
© Healthcare Software Solutions 2014
Effective Date – 18/09/2015
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 2 of 8
Contents
Introduction .......................................................................................................... 4
Purpose ............................................................................................................................... 4
Audience.............................................................................................................................. 4
Interfaces .............................................................................................................. 5
New Functionality ............................................................................................................... 5
Reporting............................................................................................................... 6
Enhancement ...................................................................................................................... 6
Resolved Issues ................................................................................................................... 6
Vetting................................................................................................................... 7
Resolved Issues ................................................................................................................... 7
Worklists ............................................................................................................... 8
Resolved Issue ..................................................................................................................... 8
© Healthcare Software Solutions 2014
Effective Date – 18/09/2015
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 3 of 8
Introduction
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.
Audience
This 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.
© Healthcare Software Solutions 2014
Effective Date – 18/09/2015
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 4 of 8
Interfaces
New Functionality
CRIS-1284
Description
Resolution
Fixed in
CRIS-1293
Description
Resolution
Fixed in
Ability to send alarms and risks outbound on a A08 message.
It should be possible to send patient alarms on patient update messages to PACS. These should be
sent in AL1 segments and the sending of these should be configurable via an attribute. In addition,
an XR setting is required to determine whether or not an UPDATE trigger should be created when
alarm information has changed.
Alarm information will now be included in A08 messages to PACS whenever the new attribute
'SendAlarms' is set to 'true' (default 'false'). Such messages can be triggered in the usual way, i.e.
changing a patient's demographics, or by adding, changing or removing a patient alarm whenever
the user has the XR setting 'GENERAL.UpdateMessageOnAlarmChange' set to 'yes' (default 'no').
The following fields will be set in the AL1 segment:
* AL1:1 - segment number: 1, 2 etc.
* AL1:2 - alarm type (W = Warning, R = Reaction, I = Info, S = Special Case)
* AL1:3.2 - alarm text1
* AL1:3.5 - alarm text2
* AL1:5 - alarm code
2.09.10t1a
Ability to send request category to PACS
It should be possible to send an event's request category in messages to PACS. This should be sent
in OBR:11 and whether or not to send it should be controllable via an attribute.
The event's request category is now sent across the interfaces in OBR:11 whenever the attribute
SendRequestCat is set to true (default false). This will go out on all OMG/ORM and ORU messages
to PACS.
2.09.10t1a
© Healthcare Software Solutions 2014
Effective Date – 18/09/2015
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 5 of 8
Reporting
Enhancement
CRIS-1292
Description
Resolution
Fixed in
Should not be possible to verify reports for non-reportable modalities.
A new XR setting was added in T1 (CRIS-958) that allows certain modalities to be reported but not
others. If the user is allowed to create/change reports and the XR setting
REPORT.ModalitiesForReporting is set to one or more modalities, the report screen will be noneditable for any other modalities.
If there is an existing unverified report for a modality not configured in the setting, e.g. a report sent
in from an external system, although it is not possible to change the report text, it is possible to
verify this text. This should not be possible as the user should only be able to verify modalities
configured in REPORT.ModalitiesForReporting.
Changes were made to ensure that the Verify button on the Report screen and the Verify tick-box
on the Finished page are only available if all the exam-modalities associated with this event are
verifiable. The only way to verify reports in cases of mixed-modalities (some of which aren't
verifiable) is via the right-click option for each verifiable section, as required.
2.09.10t1a
Resolved Issues
CRIS-1281
Description
Resolution
Fixed in
CRIS-1327
Description
Resolution
Fixed in
Error thrown on ‘batch verify’ when ordering by batch.
If a user attempts to load a batch from within the batch verify screen with Order set to 'Batch', it is
possible for an error to be thrown and for no events to show. This only occurs if the setting
GENERAL.SingleResourceGroupPerEvent (added in T1 - CRIS-1154) is set to 'Yes'. If this setting is set
to 'No' or the batch is ordered by anything else then no errors are thrown and the list of events is
displayed as expected.
The batch now loads completely without error.
2.09.10t1a
Prevent F12 report Viewer locking events
Ensure that the locking of events that had been occurring on the F12 Report Viewer page, is
prevented.
Changes were made to ensure that the locking of events previously added is not invoked from the
F12 Report Viewer.
2.09.10t1a
© Healthcare Software Solutions 2014
Effective Date – 18/09/2015
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 6 of 8
Vetting
Resolved Issues
CRIS-1320
Description
Events with multiple exams may not have the correct vetting status.
When creating events with multiple exams, it is possible for the vetting status to be set incorrectly.
This occurs when there is a mix of exams that require vetting and exams that do not require vetting.
The vetting status is taken from the last exam added to the event, which means the vetting status
could be different depending on the order the exams were added.
If any one of the event's exams requires vetting then the event's vetting status should be set 'VW'
(awaiting vetting). The status should only be set to 'VN' (vetting not required) if none of the exams
require vetting.
Resolution
Fixed in
E.g. Exam1 does NOT require vetting, Exam2 does require vetting:
Event1: Exam1, Exam2 - vetting status set to awaiting vetting as Exam2 was added last.
Event2: Exam2, Exam1 - vetting status set to vetting not required as Exam1 was added last.
Both events should be set to awaiting vetting.
The vetting status is now set correctly regardless of the order the exams are added. The vetting
status will be set to awaiting vetting as long as at least one of the exams requires vetting.
2.09.10t1a
© Healthcare Software Solutions 2014
Effective Date – 18/09/2015
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 7 of 8
Worklists
Resolved Issue
CRIS-1321
Description
Resolution
Fixed in
Allocating multiple event in the 'Verified' screen to a Resource Group.
An error can be thrown when allocating a resource group from a worklist. The error occurs when
the XR setting General.SingleResourceGroupPerEvent = 'Yes' and the user right-clicks on multiple
events, including one with multiple resource groups, and selects 'Allocate event(s) to resource
group'. After selecting a resource group and selecting 'OK', the following warning should be
displayed: "Some exam(s) already have multiple groups allocated. Overwrite them?" Instead an
error is displayed and the events are not updated with the selected resource group.
An error was thrown due to the incorrect java library being referenced. After updating the reference
the error no longer occurs and the resource group is allocated as expected.
2.09.10t1a
© Healthcare Software Solutions 2014
Effective Date – 18/09/2015
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 8 of 8