SCI Store Release Notes: Version 8.1.1201


            New for this Release

System Settings

The ‘DefaultResultsDisplayRange’ system setting has had its default value amended from ‘All’ to 30 days.

 

A new system setting called ‘Default DocumentDisplayRange’ has been added. This defines the global default value of the new ‘Processed Range’ filter which has been added to the ‘Documents tab of the ‘Patient Details’ page. This setting operates against the date that the documents were processed into Store. It will have a default setting of 30 Days.

Registry Settings

No changes were made in this release of SCI Store.

New Functionality: -

Tracker 6829 & 6924 & 7832 - Attribute a Status to Patient Identifiers, Names, Telecoms and Patient Test Reports in SCI Store With Full Auditing –  To facilitate the implementation of this functionality, the previous functionality which allowed users to mark patient identifiers as deleted and the associated audit report screen has been removed.

Two new mechanisms have been added to Store to allow users to search for patients and display and amend the status of their associated names, identifiers, telecoms and Test Reports and to display the audit details of status changes actioned against these items.

1.      The ‘Maintenance > Patient Information Status Update’ menu link loads the new ‘Patient Information Status Update’ search screen. By selecting patients returned from searches, the ‘Update Information Status’ screen is loaded. This screen allows the user to view and update the current status of the items which can be amended. Three status values are permitted – ‘Active’, ‘Retired’ and ‘Deleted’. Items which are changed to a status of ‘Deleted’ will no longer be visible via the Store front end.

If ‘Deleted’ data is utilised as part of the search criteria on any of the user search screens, no data will be returned. Additionally, demographic items which have been marked as ‘Deleted’ will not be taken into account by the patient matching rules.

In the case of ‘Deleted’ test results, if an update is processed which contains a result identifier which matches a deleted result, the result will be matched, the new result will be given a status of ‘Active’ and the previous ‘deleted’ result will be added to the historic results with a status of ‘Deleted’.

2.      The ‘Reporting > Patient Information Status Audit’ menu link loads the new Patient Information Status Audit report screen. This allows users to search for and display the audit details for status changes of all categories.

The names and descriptions of the module permissions associated with the new functionality are as follows: -

·         The Module permission previously named 'Patient Identifier Removal Audit Report' in the ‘Reporting and Auditing’ category has been renamed to ‘Patient Information Status Audit Report'. Its associated description has been changed to ‘Allow access to the Patient Information Status Audit report page'.

 

·         The Module permission previously named 'Patient Identifier Maintenance' in the ‘Store Maintenance’ category has been renamed to ‘Patient Information Status Maintenance'. Its associated description has been changed to ‘Allows a user to search for a patient and update the status on patient result reports and certain demographic items’.

           

Tracker 7251 - Exceptions Management Manual Match - Criteria selection – The functionality of the Manual Match exceptions screen for both Document Management and Non Document Management interfaces has been enhanced. The screen now incorporates checkboxes which enable the user to include/exclude the default criteria used to populate patient searches. Where no matches are found and an insert is required, a new ‘Insert Patient from File’ icon has been added to the toolbar to facilitate an ‘insert’ action.

Where checkboxes are enabled, this will incorporate the associated search criteria field in the any subsequent search that is run. Where checkboxes are disabled, the associated search criteria field will retain the content, but the field will be disabled and excluded from any subsequent search that is run.

When patients are returned from a search, if a match is desired the patient row should be selected. This will load a summary ‘Patient Details’ page where summary details of demographics, addresses and ID’s for the selected patient are displayed. Match types other than an ‘insert’ can be selected and auctioned from this page.

Tracker 8521 - Allow searching of CHI as well as local Store from Manual Match page – The functionality of the Manual Match screen has been enhanced to allow users to manually match against patients in the CHI database. The main changes are summarised below: -

·         An ‘Available Data Sources’ section has been added to the ‘Manual Match’ screen. If the logged in user account has been granted permission to access the CHI search provider, CHI will be available for selection as a data source which can be searched. The ‘Local’ and ‘CHI’ searches are mutually exclusive – both sources cannot be searched simultaneously.

·         When the CHI data source is selected, only the search criteria fields which relate to a CHI specific search are enabled. Records which are returned from CHI can subsequently be selected and matched with the input file – utilising the appropriate matching rule selected by the user. The sequence of events when manually matching against a CHI patient are: -

·         The selected CHI patient is added to Store and the matching rule currently configured against the ‘CHI Lookup’ interface applied to it. The input file is then matched against the CHI record that was imported and the matching rule manually selected by the user applied.

·         A ‘Test Match’ action is also available when viewing the CHI patient record to provide visibility of what action will be taken if the CHI record is imported.

Tracker 7891 – Function to list UCPN’s associated with a patient -  New functionality has been added to this release of SCI Store to extend the range of functionality associated with patient UCPN’s. The details are summarised below: -

·         A new ‘Patient Pathway’ tab has been added to the access to the 'Patient Details' screen. Access to the new tab is controlled by the new module permission 'View Patient Pathway' in the ‘Patient’ section of the module permissions screen. This tab provides a tree view representation of all UCPN numbers which have been allocated against a patient. All Test Results, Documents and Treatment Log records associated with each UCPN can be viewed by navigating the tree view.

·         The ‘Find Patient’ search screen has had the UCPN Search textbox moved from the ‘Advanced Search Options’ search criteria to the standard search criteria and a new ‘Must Have UCPN’ checkbox has been added to the standard search criteria.

·         When the ‘Must Have UCPN’ checkbox has been incorporated into a search, only patients who have a UCPN associated with them will be returned by the search. When patients returned by a search which has been restricted to only return patients with a UCPN are selected, the user will be directly navigated to the ‘Patient Pathway’ tab on the ‘Patient Details’ page. Where the search was not restricted by a ‘Must Have UCPN’ restriction, selecting a patient from the returned results will load the default tab which the user account is configured for on the ‘Patient Details’ page.

           The new ‘Patient Pathway’ tab and the ability to incorporate UCPN’s in a ‘Find Patient’ search have not been implemented for remote data source patient viewing and searching. 

 

Tracker 9247 – Changes to the CHI Number Validation Rules When Searching Against CHI Search Provider – The validation on the ‘Identifier’ field on the ‘Find Patient’ search screen has been amended when users are invoking searches against the CHI database via a Search Provider. Identifiers used in a CHI search of this type must be exactly 10 numeric digits in length. Searches invoked where this is not the case will not be permitted and the following error message returned to the user: -

 

            Identifier (CHI Number) is not valid for a CHI search - it must be a 10 digit numeric value”       

 

Tracker 9283 - v8.1 Data Partitioning: Add Filter to the Patient Document Displays – A new ‘Processed Range’ filter has been added to the ‘Documents’ tab on the ‘Patient Details’ page. The default value for this filter will be globally defined by the new Default DocumentDisplayRange’ system setting. This filter allows the user to restrict the number of documents displayed based on the date that they were added to SCI Store.

          

           Users can override the global default value by defining a personalised value via the ‘User Display Range Default’ option on the ‘My Settings’ menu.

 

           Note: This functionality has been implemented for viewing ‘local’ Store patient documents only. When viewing remote Store patients, the filter will be disabled on the ‘Documents tab.

 

           New Gateway Schemas:-

 

           Support has been added in this release for the following gateway schemas: -

          

·         Referrals - Version  2.8

·         Clinical Letters - Version 2.1

·         Discharge - Version 2.8

·         Supplementary Messages – Version 1.2.

 

           Web Service Changes: -

 

A new version of the SCI Store Web Services (Version 8.1) has been incorporated into this release. For full details please contact the SCI Store Support Team.

        

Resolved Issues: -

Tracker 8873 - ACSC Registrations - Processing Records Via Register on CHI Creating An Entry In The t14_PatientSearchAudit – NHS Greater Glasgow & Clyde raised a defect as it was discovered that viewing the details of CHI Registrations on the ACSC Registration Details screen was incorrectly adding audit entries to the t14_PatientSearchAudit table. This issue has been resolved in this release of SCI Store.

 

Tracker 9031 – Password rules allow 20 Char Password But Login Screen Password Field Restricted To 12 Characters – The login screen has been revised to accept password input of a maximum of 20 characters in response to this issue being reported by NHS Dumfries and Galloway.

 

Tracker 9133 - WS60 GetPatient Response Returns An 'Object Reference Not Set...' Exception – This issue was reported by NHS Greater Glasgow & Clyde and concerned a very particular set of circumstances where the master patient record in a merge operation had been allocated a UCPN as a result of a test result, treatment log or document being associated with them. A subsequent Compas or Homer ADT file was then loaded for the child patient in the merge. Following this the Webservice Version 6.0 ‘GetPatient’ requests were returning an error when attempting to retrieve the merged patient details. This issue has been resolved in this release of SCI Store.

 

Tracker 9145 - Patient Search Audit Report is Timing Out – NHS Tayside reported that they were having issues with the ‘Patient Search Audit’ report timing out when trying to run it. This issue has been investigated and additional indexes added to the database to resolve the issue.

 

Tracker 9207 - Saving a Change to a Remote Data Source Profile When More Than 20 Data Sources Exist Generates an Index Error – This error - which was occurring due to the ‘paging’ which was implemented on the screen - has now been resolved. It should be noted that where multiple pages of data are available on this screen, changes made to any page must be saved whilst still on the page where the change was made. The ‘Save’ icon only applies to the current page being amended.

 

Tracker 9276 - Documents Navigation Issue - NHS Lothian reported an issue when a mixture of document types were being viewed (e.g. XML and PDF) by using the forward and back buttons in the toolbar navigation control on the ‘View Document’s screen. This was sometimes resulting in an exception screen being raised and an error being written to the application event log. This seemed to predominantly occur when documents of type .pdf were being viewed. This issue has been investigated and resolved in this release of SCI Store

 

Tracker 9229 - CHI Broadcast - Unmerge/Unlink Transaction Raises Exception In SCI Store – An issue was raised by NHS Tayside where unmerge transactions received from the CHI Daily Broadcast were generating a parsing error during processing by SCI Store. This issue has been resolved in this release of SCI Store.

 


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.

SCI Store has been tested against the following:

·         Microsoft Windows Server 2003 R2 Enterprise Edition SP2

·         Internet Explorer 8

·         Microsoft SQL Server 2005 SP3

·         Microsoft SQL Server 2008 R2

·         Microsoft .NET framework v2.0 SP2

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

·         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 LettersThe 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.