CRIS Release Notes 2.09.10r2 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.10r2 specific
Author
Gary Glover
Date Created
01/11/2014
File Ref.
CRIS Release Notes 2.09.10r2 specific D1.0.docx
CRIS Version 2.09.10r2
Change History
Issue
Date
Author / Editor
Details of Change
D1.0
01/11/2014
Gary Glover
2.09.10r1 changes only, initial review.
Review Date
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 2 of 22
Contents
1. Introduction .......................................................................................................... 4
Purpose ............................................................................................................................... 4
Audience.............................................................................................................................. 4
2. Advanced Billing - Reporting.................................................................................. 5
Issues Resolved ................................................................................................................... 5
3. Core ....................................................................................................................... 6
Issues resolved .................................................................................................................... 6
4. Diary ...................................................................................................................... 7
Issues resolved. ................................................................................................................... 7
5. Event details .......................................................................................................... 8
Issue resolved ...................................................................................................................... 8
6. GUI ........................................................................................................................ 9
Enhancements ..................................................................................................................... 9
7. Interfaces ............................................................................................................ 11
New functionality .............................................................................................................. 11
Enhancement .................................................................................................................... 12
Issues resolved .................................................................................................................. 12
8. Orders ................................................................................................................. 13
Issue resolved .................................................................................................................... 13
9. Patients ............................................................................................................... 14
Enhancement .................................................................................................................... 14
10.
Reporting .......................................................................................................... 17
Issue resolved. ................................................................................................................... 17
11.
Requests ........................................................................................................... 18
Issues resolved .................................................................................................................. 18
12.
Setup Tables ..................................................................................................... 19
Issues Resolved ................................................................................................................. 19
13.
Vetting .............................................................................................................. 20
Enhancements ................................................................................................................... 20
Issues Resolved. ................................................................................................................ 20
14.
Work lists .......................................................................................................... 22
Issues Resolved ................................................................................................................. 22
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 3 of 22
1. 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 – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 4 of 22
2. Advanced Billing - Reporting
Issues Resolved
CRIS-458
Description
Resolution
Fixed in
Problems with reporting fee
When using multiple exams from the same event, if the reporting fee's are within the same cost
party, it generates an error regarding array index.
Invoice fees can now be processed without an error being thrown
2.09.10r2
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 5 of 22
3. Core
Issues resolved
CRIS-495
Description
Resolution
Fixed in
Date is displayed as ‘UNKNOWN’ on appointments
It was found that the date was not correctly displayed once an appointment was saved to the
diary. When the CRIS record is refreshed (F5>>F9) the value of 'Unknown' is displayed on the
events tab.
Changes made to capture the correct date from the Event Details page, and to populate the relevant
fields. The Events List page will now display the appropriate date for the new event upon refresh.
2.09.10r2
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 6 of 22
4. Diary
Issues resolved.
CRIS-502
Description
Resolution
Fixed in
Appointments – Incorrect Room or Previous date produce null pointer errors
If the user creates an appointment with either an incorrect room or a previous date i.e. a date prior
to today's date, a ‘null’ pointer exception is thrown.
Validation has been placed around these two fields to ensure on valid data is accepted.
2.09.10r2
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 7 of 22
5. Event details
Issue resolved
CRIS-561
Description
Resolution
Fixed in
Screen ‘focus’ is lost during exam validation workflow.
During the exam validation workflow, if the user decides not to proceed, i.e.selects 'No' to an option
dialog, the focus should remain in the current screen. However, once the dialog is closed focus is
not returned thus preventing the user from clearing the workflow.
Reset the focus after the dialog box asking if an appointment should be made special or not.
2.09.10r2
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 8 of 22
6. GUI
Enhancements
CRIS-386
Description
Field for Clinical Intervention type
Create a new field in the Event Details page that allows for selection of Clinical Intervention Type.
Use the following values for lookup, and default value is -44 Diagnostic Imaging
Field must be able to output the numerical code as part of the DID extract
CLINICAL INTERVENTION TYPE:
01 Anaesthetic Service
02 Anti-Cancer Drug Cycle
03 Anti-Cancer Drug Fraction
04 Anti-Cancer Drug Programme
05 Anti-Cancer Drug Regimen
06 Brachytherapy Treatment Course
07 Contraceptive Service
08 Dental Haemorrhage Service
09 Dental Treatment
10 Drug Dosage and Administration
11 Drug Treatment
12 Emergency Treatment Service
13 Endocrine Therapy
14 Fraction
15 Hip Replacement Surgery
16 Imaging or Radiodiagnostic Event
17 Immunisation Dose Given
18 Joint Replacement Surgery
19 Knee Replacement Surgery
20 Labour And Delivery
21 Lithotripsy Course Attendance
22 Maternity Medical Service
23 Minor Surgery Procedure
24 Pathology Laboratory Investigation
25 Patient Procedure
26 Post Mortem
27 Radiotherapy Treatment Course
28 Screening Test
29 Teletherapy Treatment Course
30 Test Of Immunity
31 Therapy After Discharge
32 Thrombo Prophylaxis Regime
33 Unsealed Source Treatment Course
34 Vaccination Service
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 9 of 22
Resolution
Fixed in
35 Vasectomy Performed
36 Clinical Investigation **
36 Clinical Investigation
37 Systemic Anti-Cancer Drug Cycle
38 Systemic Anti-Cancer Drug Programme
39 Systemic Anti-Cancer Drug Regimen
40 Chemotherapy
41 Cytotoxic Chemotherapy
42 Hormone Therapy
43 Immunotherapy
44 Diagnostic Imaging
Field implemented.
2.09.10r2
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 10 of 22
7. Interfaces
New functionality
CRIS-270
Description
CRIS to store NHS verification staus
Allow for the verification status of NHS numbers to be stored in CRIS. This information is received
inbound from the PAS interface in the NHS no repetition for PID:3.2. E.g. number present and
verified: 444 444 4444^01^^NHS^NH.
The possible codes and their descriptions should be configured in a normal table. The descriptions
should appear to the right of the NHS no field in the Patient Details screen. If the value is 01, display
the NHS no in the patient banner in black as it is currently shown. If it's any other value, display it in
grey and if it's blank (i.e. no code sent or number added manually in the GUI) then use the same
colour as the label. There is no need for the code itself to be displayed in the GUI.
If an invalid code is sent into CRIS, log a warning but save the code and show the number in grey as
with other non-verified codes.
Resolution
Fixed in
For outbound interface message from CRIS, add an attribute to only send messages when the NHS
no has verification status 01. So if the attribute is set then, if it's any other value or blank, it will not
be included. If the NHS no isn't being sent due to the attribute, ensure something is written to the
server log to indicate this. The verification status should be included in outbound messages.
CRIS will now store NHS verification statuses sent into CRIS from 3rd parties. The text relating to the
code (configured in the normal table 'CRISNHSV') will be displayed beside the NHS no on the patient
details page and in the NHS no's hover help on the patient banner. The colour of the NHS no in the
patient banner will now be displayed in black if the code is 01, grey if it's a value other than 01 and
the blue label colour if it's blank. The status itself is not displayed in the GUI and cannot be altered
manually, although changing the patient's NHS number manually will blank this code as it will no
longer be valid for the new number.
For outbound messages from CRIS, if the attribute SendVerifiedNHSNumOnly is set to true (default
false) then the NHS number repetition will only be included in the message if the verification code
is set to 01. If the NHS no repetition is included then the verification code will be placed in PID:3.2.
2.09.10r2
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 11 of 22
Enhancement
CRIS-471
Description
Resolution
Configuration option for NHS verification status field.
A new attribute is required to allow for the NHS verification status to be taken from PID:32 instead
of PID:3.2. An attribute with the same name should also be added for any outbound interface
sending this value. The default should be PID:3.2.
Add another new attribute to wrap around all outbound messages to enable switching off sending
the NHS verification status. Default false, i.e. don't send.
Two new attributes have been added: NhsVerStatusInIDReliabilityCode and SendNhsVerStatus.
SendNhsVerStatus
is
for
outbound
only
(PACS/PAS/OCS/Query)
whereas
NhsVerStatusInIDReliabilityCode is also for inbound PAS.
For inbound, NhsVerStatusInIDReliabilityCode determines whether the interface code checks for
the verification status in PID:3.2 (if false) or PID:32 (if true). The default is false, i.e. PID:3.2 is checked
by default.
Fixed in
For outbound, the verification status will only be sent along with the NHS no if SendNhsVerStatus is
set to true (default false). If it is to be sent then NhsVerStatusInIDReliabilityCode determines
whether it is sent in PID:3.2 (if false) or PID:32 (if true). The default is false (PID:3.2) on the outbound
also.
2.09.10r2
Issues resolved
CRIS-507
Description
Resolution
Fixed in
PID3.2 attribute using wrong position.
An outbound message that contains an event sets the status code in the wrong position:
The nhs status code actual position is next to the CRIS number.
The issue was that the NHS verification status, 01 in this case, was appearing in the CRIS repetition
instead of the NHS repetition. This is because the attribute IdentifierOrder was set to NHS, which
means the order of the PID repetitions was changed so that NHS was 1st and CRIS 2nd instead of
the other way around. The swapping of PID:3.2 was not performed, which is why 01 was still
appearing in the 2nd repetition with the CRIS no instead of moving to the first with the NHS no.
A change has now been made to ensure the NHS verification status appears in the NHS repetition
as expected.
2.09.10r2
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 12 of 22
8. Orders
Issue resolved
CRIS-378
Description
Resolution
Fixed in
Order ‘notes’ appear twice in the ‘Event Comment’ field.
When loading an order with text saved in the notes field, this text will be displayed twice in the
Event Comment field. Saving the order as an event will then save the text twice against the event.
Text is no longer duplicated in the event comment field.
2.09.10r2
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 13 of 22
9. Patients
Enhancement
CRIS-441
Description
New ‘Consent Type’ setup table.
New database and setup table required for configuring consent type - e.g. patient consent for data
sharing, patient consent for texting:
* Code
* Description
* Document for consent
* Document for dissent
* Document for not asked
* XDS Document for consent
* XDS Document for dissent
* XDS Document for not asked
Resolution
Fixed in
CRIS-442
Description
Allow for the configuration of the documents in the printing setup that can be referenced in the
non-XDS document fields. The documents for consent and dissent should be mandatory, while the
document for not asked is optional. The XDS document fields should be free text. The Description
field should also be mandatory as this will be what is displayed on the Consent tab.
It is now possible to add consent types to the new ConsentType table, located in Setup tables ->
other -> consent. To view this table the user must have the security setting VIEWS.CONSENT_TYPES.
The fields Consent Document, Dissent Document and Not asked Document can be populated using
the F4 popup, allowing values taken from the normal table CONSDOCS. Entries to this normal table
will also be selectable from the Name field in the Print Setup table, prefixed with "Consent:". This
allows users to configure the document in the usual manner.
2.09.10r2
New ‘Consent’ page.
Add a button in the 'Patient Details' page that opens a new 'Consent' tab. This should display a form
consisting of a list of Consent Types based upon the setup table along with radio buttons labelled
'Not asked', 'Consent' and 'Dissent'.
Below this list should be a button to 'Save and print forms'. Selecting this should save new rows in a
new 'Consent' database table to store the selected value for each type. On reloading the patient's
consent page, the radio buttons should reflect the last saved values.
Resolution
As well as storing the data, clicking the 'Save and print forms' button should print the appropriate
document as configured in the Consent Types table. E.g. if 'Consent' is selected for Image sharing
then, on saving, the 'Document for consent' for the image sharing consent type should be printed.
As with other printed documents, a pdf copy of the letter should be stored.
A new consent page has been created, allowing users to add and amend consent information for
the patient. This is accessible via a button from the Patient details page, which is only enabled if the
patient has been saved as a CRIS patient. Once the user selects the save button, the information is
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 14 of 22
Fixed in
CRIS-443
Description
Resolution
saved and the relevant consent documents as configured in the consent type table (see issue CRIS441) are printed. These printed documents will be stored as PDFs in the background, and the new
AVData store AVDATAMANAGER.PRINTDCONS should be configured in the XR settings as with other
AVData types.
2.09.10r2
Scanning signed forms.
Add a 'Signed form scan' button below the 'Save and print forms' button on the 'Consent' page.
Selecting this should allow you to select which type of Consent document you are scanning and then
scan the form. The form should be stored and the text beside the radio buttons should be changed
to 'Verified' whenever the signed form for that type has been scanned in.
A new [Signed form scan] button has been added to the 'Consent Details' page. It will be enabled
whenever there are unverified consent items, meaning a consent document has been printed for
the item. The document can then be signed and scanned back in by clicking the button, selecting
the appropriate option in the popup and pressing the [SCAN] button. A warning will be displayed to
ask the user to ensure the document for the correct type has been signed before it is scanned in.
After scanning one document, the user may scan any further available documents, or they may click
the [DONE] button to close the popup window. Once the popup has closed, the consent page will
be updated and rows that have now been scanned in will display green "VERIFIED" text in place of
the red "UNVERIFIED" text.
The [Signed form scan] button will be disabled if there are no unverified items or if an item has been
changed but not saved. If the button is disabled then the reason for this will be displayed in the
hover text.
Fixed in
CRIS-444
Description
Resolution
In order for the scanned documents to be stored, a new document type SCANDCONS should be
configured in the usual way in the XR settings, i.e. AVDATAMANAGER.SCANDCONS.Store.
SCANDCONS will also appear in the 'Document Type' combo box on the 'Scanner Setup' page, and
should be configured in the same way as usual scanned documents. If the scanning fails for any
reason then the consent item should remain unverified.
2.09.10r2
Displaying consent documents.
A section should be added to the consent page to display stored consent documents. This should
include the original printed document and the scanned signed forms. This section should display
rows in reverse chronological order displaying: Type, Date, Time, User, State and Doc type
(draft/signed). Selecting a row should load the document, either directly on the page or in a new
window.
A complete history of consent changes is now displayed at the bottom of the Consent Details page.
Rows are shown in reverse chronological order and display the consent type, date, time, user, state
(Not asked/Consent/Dissent) and doc type (Signed/Draft/blank).
For rows with a doc type of Draft or Signed, double-clicking on the row will load the printed or
scanned document respectively in a separate window. Double-clicking on the document again will
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 15 of 22
close it and it will be possible to zoom in and out within the document window. Double-clicking on
a row with blank doc type will display a message that no document is available.
Fixed in
CRIS-472
Description
Resolution
Fixed in
Whenever the [Save and print forms] button is clicked or the scan popup is closed, the table is
refreshed in order for the latest consent rows to be displayed.
2.09.10r2
New buttons on the ‘Consent Details’ page.
The [Save and print forms] button on the 'Consent Details' page should be replaced with two buttons
labelled [Save and print changed] and [Save and print all]. Clicking the [Save and print changed]
button should only save and print rows that are currently unsaved. This means that all other rows,
both verified and unverified, will remain current and a new draft row to the consent document table
will not be added for these. If the user wishes to print documents for all rows, including reprinting
documents for currently saved rows, the user can select the [Save and print all] button, which will
work in the same way as the old [Save and print forms] button.
The user is now able to only print the consent items that have changed by clicking the [Save and
print changed] button. To print all forms as before, the user should select [Save and print all]. The
[Save and print changed] button will only be enabled when there are unsaved changes, whereas
[Save and print all] will always be enabled. To make it easier to see what has changed, the
Verified/Unverified text to the right of each row will only become grey if that row has changed.
2.09.10r2
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 16 of 22
10. Reporting
Issue resolved.
CRIS-539
Description
Resolution
Fixed in
Cannot add an addendum to a previously verified report, by the same user.
Addendum to a verified report cannot be saved/verified by the same user.
A message is displayed indicating that the report is locked and cannot be changed.
Local changes to a verified report can now be saved without erroneous warning message being
displayed.
2.09.10r2
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 17 of 22
11. Requests
Issues resolved
CRIS-509
Description
Reject event – Reject reason Text Box
Resolution
Fixed in
The event is now refreshed once the page is loaded, thus enabling the reject reason text.
2.09.10r2
The reject reason free text box on Reject Event tab is disabled on first load. The user has to select
the 'Rejected' radio button to enable the feed.
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 18 of 22
12. Setup Tables
Issues Resolved
CRIS-494
Description
Resolution
Fixed in
Database error message ‘unable to delete’ showing when saving in Setup Tables with blank fields.
When saving in some setup tables, i.e. ‘stock’ and ‘Consent’ - an error message is shown 'Database
update error' - *'Unable to delete records that are referenced in CRIS data'*
This is shown when mandatory fields are not filled out.
The correct error message is now displayed when attempting to save blank values into database
fields with a non-null constraint. The message will now read "The <fieldname> field cannot be
blank." for both oracle and postgres databases.
2.09.10r2
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 19 of 22
13. Vetting
Enhancements
CRIS-161
Description
Resolution
Fixed in
CRIS-339
Description
Resolution
Fixed in
CRIS-434
Description
Resolution
Fixed in
CRIS-445
Description
Resolution
Fixed in
Protocol missed from ‘Assigned Protocols’ category if using ‘Lock text’.
If multiple protocols are to be assigned, subsequent selections should be Control-Clicked to add the
protocol
to
the
selection,
otherwise
it
will
de-select
it.
Locking text does not equate to selecting the protocol.
Both protocols now appear in the assigned protocols section
2.09.10r2
Vetting Module Improvements – create a field for reject/cancel reason.
Create a field for reject/cancel reason that can be included into the letter for the referrer as to why
the event will not be booked. This should be another box below Status Comment appearing on the
Event Cancel, Reject Event and Cancel Order pages. It should also appear on the Add Request page
but should only be editable if the selected status has type 'RJ'.
The cancel/reject reason can now be configured on the relevant letters.
2.09.10r2
Vetting Module Improvements – Exam room validation.
When changing exam codes on appointments, validation should be carried out to ensure the room,
date and time are still valid for this code. If not, a warning should be displayed to the user, asking
them if they wish to continue. If they select no, the exam codes should remain as they were. If they
select yes, the appointment should be changed to a 'special booking' to allow for the fact it no longer
fits into a diary slot.
Exams that no longer fit into the previous appointment slot will be given special booking should the
user choose to proceed
2.09.10r2
New Protocol Setup – Trust, Site, Vetting & User Groups Display
During group protocol setup that once a selection had been made in Site, Trust, User or Vetting
fields, the selection would be displayed on the line below the selection box.
trust, site user info labels are now displayed on the same line as the selection
2.09.10r2
Issues Resolved.
CRIS-250
Description
Resolution
Fixed in
Protocol appears twice under one modality for multi-exams events
If an event is created that has multiple exams for the same body part, i.e. CCHES and XCHES, the
protocol appears twice under the ‘Relevant Protocols>Radiology>Chess’ node. There should be two
‘Relevant Protocol’ nodes, one for the CT and one for the Radiology.
The protocol now appears twice for each modality.
2.09.10r2
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 20 of 22
CRIS-446
Description
Resolution
Fixed in
CRIS-449
Description
Resolution
Fixed in
Protocol Setup – Document field enabled when should be read-only.
When viewing a newly created protocol with a user who only has read-only permissions. It was
found that the document field would allow the user to select a document from a local drive and
display the path after selection. If the user navigated away from the protocol, then reselected at a
later time the document would be restored to its original state i.e. blank.
Document field is no longer enabled when use has read only permissions.
2.09.10r2
New message workflow is not presented when changing an exam via the Vetting list.
When executing the new Exam validation workflow, if an appointment that had a valid room,
date/time was changed to an exam that did not have a room. The room from the first exam is
populated when the Protocol screen is selected.
Exam room validation is now applied when going through the vetting list.
2.09.10r2
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 21 of 22
14. Work lists
Issues Resolved
CRIS-498
Description
Resolution
Fixed in
Future data not saving correctly in ‘Preferences’.
If a date is saved from a work list into a preference, any date added in the future will not save
correctly. After a future date is added, when reloading the list the date will show the day before.
A method calculating date differences was providing inconsistent results if the first date came after
the second. This method has now been amended to handle this scenario correctly.
2.09.10r2
© Healthcare Software Solutions 2014
Effective Date – 01/11/2014
HSS Doc ref: Document1
All Rights Reserved
Commercial In Confidence
Page 22 of 22