SCI Store Release Notes: Version 8.5.1501

Release Date: - 22/05/2015

            New for this Release

System Settings

A new System Setting called ‘RecentCreatedRangeDays’ has been created in conjunction with the changes detailed in Tracker 9934 below. The setting determines the maximum number of days that a user can set when defining the value of any of the ‘Recently Created’ Homepage tabs. The setting will have a default value of 60 days and can be configured to operate between a range of 1 and 250 days.

Registry Settings

No changes were made in this release of SCI Store.

New Functionality: -

As part of this release of SCI Store, some changes have been implemented to improve the overall performance of the application. In the main, the changes will have no effect upon the functionality of the application; however there were a few areas where functional changes were made to boost performance in specific areas. The details of these changes are detailed below: -

 

 

Tracker 9933 - SCI Store Improvements IT2 - Homepage Recently Viewed Tabs Functional Changes: - To increase the performance of these tabs, the underlying queries have been rewritten and optimized. One slight change has been made to remove the applying of user restrictions to the population of the tabs. Previously, with regards to data which had been previously viewed, and the user had subsequently been revoked security permissions for any reason, the data would not have been present on the tab the next time it was loaded. However, from now on, the data will still be displayed on the tab. If the user selects the data they will not be permitted to view it (the data restrictions now being applied when selecting the data rather than every time that the tab is loaded). In this circumstance, the user will be re-directed to the generic security error page.

 

Tracker 9934 - SCI Store Improvements IT2 - Homepage Recently Created Tabs Functional Changes: - The functionality of the Homepage ‘Recently Created’ tabs has been amended slightly to boost performance. The changes are summarized below: -

 

When configuring the tab settings on the ‘User Customisation’ page, users will no longer be able to set the values to ‘Weeks’, ‘Months’ or ‘Years’ as these values have been removed from the dropdowns. For the remaining options the behaviour will be as follows: -

 

·         When ‘Hours’ are selected, the user will be constrained to selecting values between 1 and 24  – as previously, if a value of 0 (zero) is selected, the tab will be disabled.

·         When ‘Days’ are selected, the user will be constrained to selecting values between 1 and the current value of the new ‘RecentCreatedRangeDays’ System Setting – as previously, if a value of 0 (zero) is selected, the tab will be disabled.

 

 

Redundant Functionality: -

 

N/A

 

           Web Service Changes: -

 

No changes were made in this release of SCI Store.

 

 

        Resolved Issues: -

Tracker 9845 – ISD Upload Parsing Exception- "Unexpected Reference File Upload Error: Please Check GPREF File. Parsing Error Occurred at Line Number 3. Process Aborted For This File."– NHS Highland raised this issue which was occurring   when the uploading ISD Reference files. Investigation revealed that the issue was occurring when records in the t14_HealthcareProfessional table  which had a ‘SchemeID’ value of NULL were being associated with records in the GPREF and MEDDEN import files. This issue has been resolved in this release of SCI Store.

Tracker 9847– CHI Lookup in Match Rule Does Not Parse Date of Death Details– NHS Greater Glasgow and Clyde raised this issue. When CHI Lookup is included within a match rule, if the patient is deceased on CHI, the Deceased information is ignored while processing the update/insert. If the patient already exists as’ Deceased’ on Store, the impact being that  the ‘Deceased’ information was being erroneously removed from Store when the CHI Lookup update is processed. This issue has been resolved in this release of SCI Store.

Tracker 9869 - Telepath Results Issue - ASCII File Separator Control Char Allowed In But Causes Exception When Extracted Via Web Services – An issue was reported by NHS Greater Glasgow & Clyde where a Telepath results issue was identified. The input files contained an ASCII file separator control char which was causing no issues when the file was parsed and displayed on the Store front end. However, results which contained the character were raising an exception when being retrieved via Web Services. This issue has been resolved in this version of SCI Store. The offending ASCII character is now being ignored during the file parsing process and results of this type can now be successfully retrieved by all versions of the SCI Store Web Services

Tracker 9879 – ISD Reference Translator - File Names Are Case Sensitive, Exception Will Occur if Physical File Names Have Different Character Case from Those in TFDB Interface– NHS Forth Valley raised this issue which was occurring when uploading ISD Reference files. Investigation revealed that ISD have changed the case sensitivity of the reference files – which was causing a mismatch between the names defined in the Reference Data Translator and the actual file names and resulting in an error being generated.  Simply changing the definition of the file names in the Translator Service to match the case of those provided by ISD has allowed the upload to be carried out at sites. However, a code change has been implemented in this release of SCI Store to make the case of the names of the files defined in the translator and those of the actual upload files the same during the comparison phase of the operation. This will ensure that if the case of the files is changed in future that this type of issue will not re-occur.

Tracker 9881 - ACSC Registration Requests Are Made by Store Even When the CHI Number is Invalid – The CHI Support Team in Dundee reported a number of exceptions being detected on the CHI application due to attempts made by Store to register a note of interest using invalid CHI numbers. This was causing issues on CHI as log files grew to large sizes. Some changes in the functionality of the ACSC Registration process in SCI Store has been implemented in this release to address this issue. From this release forward, if an attempt to register an invalidly formatted CHI number is made, a new error status of ‘Invalid CHI’ will be set against the record in the ACSC registration queue and an error description of ‘’Patient not registered – CHI number has an invalid format’ associated with it. The ACSC Registration screen has been enhanced to incorporate the new status into the ‘Status’ dropdown to allow filtering to be performed on the search screen.

Tracker 9913 - Manage Duplicates - Keyboard 'Enter' Key Navigates to Home Page Rather Than Performing Search – NHS Forth Valley reported the following issue with the ‘Manage Duplicates’ page: - Selecting 'Enter’ on the keyboard, following the selection of the matching criteria, navigates to the ‘Home’ page rather than invoking the search. This has been resolved in this release of SCI Store. When the user selects the ‘Enter’ key when on this page, the search will now be invoked – making the page behaviour consistent with other pages in the application.

Tracker 9924 – Recipient Web Services - Object Reference Exception When Using Match Rules in Web.Config - NHS Highland reported an issue where Gateway messages were failing to xfer via the RWS when a Style Sheet match rule was set up but where the Gateway message did not include the XML Node defined within the match rule. This resulted in a Gateway Dead Message (message not transferred to Store) and an 'Object reference not set to an instance of an object' exception being written to the Store event log. This issue has been resolved in this release of SCI Store.

Tracker 9929 – NS Issue When Performing manual Match from Document Exceptions Page – NHS Lothian reported an Issue where Event Log entries were being created when document exceptions were being manually matched and Patient Notifications existed for the patients who were being matched.

Investigations revealed that when a Document Exception was manually matched, the event log entry was being erroneously created. In addition, when performing the document manual match, a patient event was correctly being created, but the contents were wrong - rather than indicating the source of the notification to be documents, and the ‘RecordKey’ containing the ‘PatientDocumentSearchID’, the notification was incorrectly indicating that the source was a demographic interface, and the ‘RecordKey’ contained the ‘PatientID’. This issue has been resolved in this release of SCI Store.

 

 

Known Issues with this Release

No known issues with this release

SCI Store has been tested against the following:

·         Microsoft Windows Server 2003 R2 Enterprise Edition / Microsoft SQL Server 2005 SP3

·         Microsoft Windows Server 2008 R2 Enterprise Edition / Microsoft SQL Server 2012

·         Microsoft Windows Server 2012 Enterprise Edition / Microsoft SQL Server 2012

·         Internet Explorer 8

·         Microsoft .NET framework v4.5.2 (64 bit platforms) v4.0 (32 Bit platform)

·         ClearSpan Management, BridgeForward Software, Inc, Version: 3.5.0.6 against SQL 2005 (only against Microsoft Windows Server 2003 R2 Enterprise Edition / Microsoft SQL Server 2005 SP3 platform)

·         Windows hot fixes.

·         Internet Explorer critical Patches.

Referral and Discharge Schemas Supported By This Release of Recipient Web Services (Versions 1 & 2)

Discharge Messages –The 2.3, 2.4, 2.5, 2.6, 2.7 and 2.8 discharge schemas, ‘gateway-dischargeEDIS_1.xsl’

Referral Messages – The 2.3, 2.4, 2.6, 2.7 and 2.8 referral schemas - including the ability to define multiple style sheets for each referral schema.

Scottish Ambulance Service - sas-eprf-v1-0.xsl

     Clinical Letters – The version 1.1 and 2.1 schemas.

      Supplementary Messages – The version 1.1 and 1.2 schemas.

      Advice Messages - 'Advice-Request-v1-0’ and 'Advice-Response-v1-0'

All of the above are subject to sites having access to the supporting style sheets. Details of the supporting stylesheets should be added to the Recipient Web Services Web.Config file to facilitate the successful uploading and viewing of Gateway documents.