SCI Store Release Notes: Version 8.0.1104


            New for this Release

System Settings

The 'AllowSubscribers' System Setting has been renamed to 'NSEnableEventGeneration'. The functionality associated with the setting has not been altered – it allows the system administrator to enable or disable the generation of notification events.

 

A new setting called ‘NSSubscriptionSearchLimit’ has been added. This setting allows the System Administrator to restrict the number of records returned by subscription searches on the Notification Services management screens.

 

The following new System Settings have been added in support of the configuration of the new Administration sub tabs ‘Notification Creation’ and ‘Notification Consumption’: -

 

·         NSManagementDataCacheTime

·         NSManagementAmberEventCount

·         NSManagementRedEventCount

·         NSManagementAmberEventMinutes

·         NSManagementRedEventMinutes

·         NSUnConsumedAmber

·         NSUnConsumedRed

·         NSMinsSinceConsumptionAmber

·         NSMinsSinceConsumptionRed

 

Full details of their functionality can be found in the Store Administrators guide.

 

The ‘NSDeleteEventDays’ System Setting has been removed, as it has been replaced by functionality which has been incorporated into the configuration of the new ‘NotificationsMaintenanceTask’ service.

The ‘NSGenerateResultTestEvents’ System Setting has been removed as it is no longer required in the application.

Registry Settings

No changes were made in this release of SCI Store.

New Functionality: -

Notification Services Changes / Enhancements: -

           Full documentation for the modifications in this area can be obtained from the SCI Store Support Team. A summary of the main changes made in this area is provided below.

·         The SQL 2005 Notification Services component has been removed from the application as it is no longer required. Patient, Result and Treatment Log notifications are now handled by SCI Store – with no dependence on SQL Server Notifications components.

·         Four new Service Types have been created to facilitate the Notification Services Functionality: -

PatientNotificationGeneration Service – Handles the generation of ‘Patient’ notifications.

ResultNotificationGeneration Service - Handles the generation of ‘Result’ notifications.

TreatmentLogNotificationGeneration Service - Handles the generation of ‘Treatment Log’ notifications.

NotificationsMaintenanceTask Service – Allows the system administrator to configure the deletion of ‘Patient’, ‘Result’ and ‘Treatment Log’ events and ‘Notification History Messages’. This service can be configured to run between specified time periods.

·         Two new fields have been added to the ‘Account Details’ section of the ‘User Maintenance’ screen to allow user accounts to be configured for Notification Service functionality: -

The ‘Active For Notifications’ field is used to enable or disable user account notification generation.

The ‘NS Subscription Edit Mode’ field is used to determine whether user account subscriptions are be maintained via the Store front end maintenance screens or via the Store Web Services.

·         The following screens have been added / amended to allow ‘Patient’, ‘Result’ and ‘Treatment Log’ subscriptions to be managed via the Store front end: -

Treatment Log Subscription Search

Patient Subscription Search

Result Subscription Search

All of the above screens are accessed via the ‘Notifications’ Menu item.

·         Two new sub tabs have been added to the ‘Administration’ Tab on the ‘Homepage’: -

The ‘Notification Creation’ tab provides a ‘dashboard’ view of the status of events awaiting processing and the time elapsed since the last event was processed for each notification type.

The ‘Notification Consumption’ tab provides a ‘dashboard’ view of the status of notifications awaiting processing and the time elapsed since the last notification was consumed for each notification type.

            

           Web Service Changes: -

 

No changes were made in this release of SCI Store.

        

Resolved Issues: -

Tracker 7930 - CHI Daily Broadcast - Title Removal Transaction Also Removes Other Information – An issue was reported where it was discovered that CHI daily broadcast files which contained a ‘Title’ removal was, in addition to removing the patient title details inadvertently removing other data from the database. The affected fields were: -

 

·         MaritalStatus

·         LocationDeath

·         EthnicGroup

·         Religion

·         The ‘time’ portion of the DateOfDeath value - if there was one present.

 

This issue has now been resolved in this release of SCI Store. The receipt of this type of file will now only remove the ‘title’ details from the patient record.

 

Tracker 8868 – WS ‘FindResult’ Request With A Patient Identifier Does Not Take Merged Patients Into Account – An issue was reported where the ‘FindResult’ web service using the patient CHI details was failing to return the combined result set of patients who were associated by being merged.  Only the results of the patient(s) who directly match the Patient Identifier value specified in the search criteria were being returned.

This issue has been resolved in this build for the Version 4.1, 6.0 and 7.1 ‘FindResult’ Web Service.

 

Tracker 8882 – Inbound XML21 Not Parsing Requesting HCP – NHS Lothian recently reported an issue with incoming XML Version 2.1 files whereby the ‘Requesting HCP’ details were not being processed by the SCI Store parser. This issue has been investigated and the cause identified to be due to the fact that the files contained an HCP <gen:IdScheme></gen:IdScheme> tag which had a value of ‘Trak’ – which the parser was failing to handle correctly. The code logic has been amended to enable the XML Version 2.1 parser to handle this correctly. As a result this issue has been resolved in this release of SCI Store.

 

Tracker 8887 – Patient Phone Numbers Not Being Passed to LabelTrace – NHS Greater Glasgow & Clyde recently reported that although patient phone number is listed as an available field within the label trace raw data, Store never passes out this information. Investigation into the issue revealed that the original specification for the LabelTrace output did not specify that this value would be output. However, the functionality has now been enhanced to allow this data to be output from this release of SCI Store forward. It will now be possible to print the following telephone types on the labels produced by the LabelTrace functionality: -

 

·         Where the telecom type is defined as ‘Voice’, Home’ or is not specified, the telephone details will be output in the LabelTrace ‘phone’ parameter.

·         Where the telecom type is defined as ‘Work’, the telephone details will be output in the LabelTrace ‘phonework’ parameter.

·         Where the telecom type is defined as ‘Mobile’, the telephone details will be output in the LabelTrace ‘phonemobile’ parameter.

 

Where multiple entries exist for any category, the one with the most recent ‘CurrentAt’ date in the Store database (i.e. the most recently added) will be output.

 

The following additional enhancement has also been made: -

 

Where patients have NHS number identifiers, they will be output in the ‘nhsnumber’ variable. If multiple NHS numbers exist, they will be output in a comma separated list.

 

 


Known Issues with this Release

No known issues with this release


Version of NHSiS General Schema Supported By This Release

Web Services Version 2.1 and 2.2 Incoming and Outgoing support Version 2.1.1b of the NHSiS General Schema.

Web Services Version 2.3 Outgoing supports Version 2.5 of the NHSiS General Schema.

Version of Outpatients Tested Against For This Release

Outpatients Version 2.5.2.4

SCI Store has been tested against the following:

·         Microsoft Windows Server 2003 R2 Enterprise Edition SP2

·         Internet Explorer 6 SP2

·         Internet Explorer 7

·         Microsoft SQL Server 2005 SP3

·         McAfee Virus Scan Enterprise 8.5.0i Antivirus

·         Microsoft .NET framework v2.0 SP2

·         ClearSpan Management, BridgeForward Software, Inc, Version: 3.5.0.6 against SQL 2005

·         Windows hot fixes.

·         Internet Explorer critical Patches.

·         Gateway Message Sender (Recipient Web Services)

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 and 2.7 discharge schemas, ‘gateway-dischargeEDIS_1.xsl’

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

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

     Clinical Letters - version 1.1 schema.

      Supplementary Messages – Version 1.1

      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. Currently the Discharge 2.6 and 2.7, supplementary messages and clinical letters 1.1 do not have a valid style sheet currently specified. Until they are available, they should not be uploaded to SCI Store. When they become available, the Recipient Web Services Web.Config file will require amendment before they can be successfully uploaded.