SCI Store Release Notes: Version 7.0.1102

            New for this Release

System Settings

A new System Setting called 'DocumentStylesheetLocation' has been added in this release of SCI Store. This setting allows the System Administrator to define the location where style sheets associated with the Document Management Interfaces are copied to when uploaded - it defines the location where the display style sheets for SCI Store documents will be held. This replaces the ‘DocumentStylesFolder’ registry setting – which is now redundant.

By default, the value of the ‘DocumentStylesheetLocation’ will be set to C:\. If sites had a location other than the default of C:\ specified in the ‘DocumentStylesFolder’ registry setting prior to upgrading to this version of Store, they will be required to create the new ‘DocumentStylesheetLocation’ System setting and set it to the desired location of the document style sheet path.

A new System Setting called ' CumulativeDataPoints' has been added in this release of SCI Store. This setting allows the System Administrator to define the Number of columns of data to be displayed on the new ‘Ad Hoc Cumulative Reporting Screen’ which has been added in this release of SCI Store. The setting has a default value of 6 and is constrained to a lower limit of 2 and an upper limit of 10.

 

 Registry Settings

The ‘DocumentStylesFolder’ registry setting has been removed in this release of SCI Store. It has been replaced by the new 'DocumentStylesheetLocation' System Setting – as described in the System Settings section above.

 

New Functionality: -

Tracker 7743 - Automerge Process Incorrectly Allows Patients With Different Consent Values to be Merged – The Automerge functionality has been enhanced to bring its behaviour when attempting to merge / unmerge patients who have different consent values into line with the manual merging processes within SCI Store. Where candidate patients in an automerge search do not have matching patient consent status, the processing will prevent the patients being merged / unmerged when the automerge merge / unmerge process is run. Only patients who have the same consent status will be merged / unmerged. The ‘Automatic merge Report’ screen will display an appropriate error message for all merge / unmerge operations which fail due to incompatible consent.

Tracker 8156 - V7.0 Extended Document Upload Info - Modify Recipient Web Services to Process the Action Date & Document Creation Date for SAS and Supplementary Message Types – As part of the implementation of the addition of ‘Action Date’ and ‘Document Creation Date’ in the previous release of SCI Store (Build 6.1.1046) the recipient Web Services processing has been further extended to save these details to Store where they are supplied in the Gateway file formats that were not adjusted in the previous release. The processing of the following Gateway message types has now been extended to incorporate these new values: -

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

     Supplementary Messages – gateway-supplementary-v1-1.xsl

The appropriate SCI Store front end user screens have been enhanced to display these details to the users when viewing local store data and remote store data via the 4.1 and 6.0 search provider mechanisms.

 

New Ad Hoc Cumulative Reporting Screen

The new ‘Ad Hoc Cumulative Reporting’ screen has been implemented in this release of SCI Store. The new screen can be accessed via a new ‘Cumulative’ button which is displayed within the Result Set Header section of the ‘Result Details’ screen. The new functionality will only be available for Numeric results.

Permissions to access this new page is granted via the existing ‘Cumulative Report’ Module Permission - which is available via the ‘Results’ category on the Module Permissions configuration screen.

The new 'CumulativeDataPoints' System Setting determines how many columns will be displayed on the new page – as detailed in the System Settings section above. 

 

Recipient WS Version 2 Gateway Style Sheet GUID Identification Processing

A new version of the Gateway Recipient WS has been implemented in this release of SCI Store. This new version will allow the Gateway Message display style sheet to be identified by the inclusion of a GUID identifier as one of the RWS message parameters - <StylesheetGUID>.

The new ‘DocumentStylesheetLocation’ System setting will determine the location of the style sheets which can be used to associate GUID’s with within SCI Store.

Two new Maintenance pages have been created to allow System Administrators to define the association between GUID’s and the display style sheets. These are located via the General > GUID Stylesheet Association Maintenance menu item. Style Sheets may be associated with 1 or more GUID’s, but each GUID can only be associated with a single style sheet.

Access to these new administration screens is controlled via the new Module Permission titled ‘'GUID Stylesheet Association Maintenance'’ – which is available via the ‘Configuration’ category on the module permissions configuration screen.

It should be noted that the previous means of identifying style sheets via the Recipient Web Services Version 1 Web.config file will work concurrently with the new GUID driven method and should continue to do so until such times as all sites have ceased receiving Version 1 Recipient Web Services messages from Gateway.

Note: - As there are now two versions of the Recipient WS available, it has been necessary to create new references to them. The details are as follows: -

The .asmx file for version 1.0 has changed in this Build to SCIStoreRecipientWS_V1.asmx so the reference to it will change accordingly to: - “http://localhost/RecipientWebServices/SCIStoreRecipientWS_V1.asmx”

 

When version 2.0 is switched on at a site the reference will be: - “http://localhost/RecipientWebServices/SCIStoreRecipientWS_V2.asmx”

 

Revised Reference Data Upload Interface

The Reference Data Upload interface has been revised in this release of SCI Store. From this build forward, the reference data files will be processed by new File to Database and Translator services which have been added for this purpose. New ‘ReferenceFileToDatabase’ and ‘ReferenceTranslatorFromDatabase’ services have been added to the list of available Service Types to allow the new style interfaces to be created.

Each of these new services has the ability to set a ‘Time From’ and a ‘Time To’ value – which will allow users to schedule when the Reference Data Files will be processed by the Store Services component. The rules for the scheduling are as follows: -

o   The time can be set in increments of half an hour.

 

o   If the start and end times are set to the same value, the times will be displayed as 00:00 when the interface configuration is saved.  When this is the case, the service will be inactive. Any reference data files which are present in the defined upload folder or are pending for parsing by the translator service will not be processed by the Store services component.

 

o   When no time band values have been set, they are displayed as 00:00. A service defined with these time band values will be inactive. When this is the case, the service will be inactive. Any reference data files which are present in the defined upload folder or are pending for parsing by the translator service will not be processed by the Store services component.

 

o   If the ‘Time From’ is less than the ‘Time To’ (e.g. 09:00 to 12:00) then both times will apply to the current day. The store services will process any reference data files which exist in the upload folder or are pending for parsing by the translator service between these times.

 

o   If the ‘Time From’ is greater than the ‘Time To’ (e.g. 23:00 to 02:00) then the service will be active across 2 days. The store services will process any reference data files which exist in the upload folder or are pending for parsing by the translator service between these times.

 

The reference data files may also be processed manually at any time by using the ‘Test Process’ icon / Action on the interface configuration page if required.

 

Only 1 Reference Data file to Database or Translator interface can be created and active at any one time.

 

The exception handling screens have also been enhanced to allow System Administrators to access the details of the Reference Data processing in a similar manner to other input file formats.

Existing redundant ‘Reference Data Import’ services which were defined at sites will be removed by the database upgrade script. The new format Reference Data services must be manually created by the SCI Store implementation team or System Administrator following an upgrade to this version of Store.

Remote Data Source Profile Maintenance

The mechanism for assigning Remote Data Source access permissions has been revised in this release of SCI Store. The previous method of assigning permissions to individual user accounts via the ‘Web Service Permission’ screen has been replaced as follows: -

Two new screens ‘Remote Data Source Profile Maintenance’ and ‘Add Remote Data Source Profile’ have been created to allow administrators to create ‘profiles’ which can contain any of the Remote Data Sources which have been created on the Remote Data Sources Configuration screen.

These new screens are located via the ‘Security > Remote Data Source Profile Maintenance’ menu item. Permissions to access these new pages are granted via the existing ‘Remote Data Source User Configuration’ module permission. Thus any user who previously had permissions to grant access to Remote Data Sources will continue to have access to the new screens. The previous screens – ‘Remote Data Source Users’ and ‘Web Service Permission’ have been discontinued and will no longer be available.

When the profiles have been created, they can then be allocated in the following ways: -

·         They can be added to Permission Groups via a new ‘Remote Profile Name’ list control – which has been added to the Manage Permission Groups page. The permission group can then be associated with the required user accounts or Roles.

·         They can be granted to individual users accounts via a new ‘Remote Profiles’ list control – which has been added to the ‘Account Details’ section of the ‘User Maintenance’ screen. Permission groups which contain Remote Profiles can also be added to Users.

·         They can be added to Roles via a new ‘Remote Profiles’ list control – which has been added to the ‘Role Maintenance’ screen. Permission groups which contain Remote Profiles can also be added to Roles.

Record Identifier Patient Matching

The Patient Matching rules have been enhanced by adding a new category of ‘Record Identifier’ to the set of available Patient Match Criteria. This new category will provide the ability to match incoming records against existing records which contain insufficient demographics to match on a patient (e.g. records which were originally added to Store where it was not possible to obtain full demographic details – unconscious patients etc).

This new ‘Record Identifier’ matching criteria has the ability on defined interfaces to match to an existing patient using the dataset identifier (Results, Documents, ADT or Treatment Log). By matching on the ‘Record Identifier’ only, this will allow demographic updates to be made against existing patient records which would previously have had insufficient demographic data to be matched against.

It should be noted that when using the new ‘Record Identifier’ match criteria, no other matching criteria is permitted in the same match rule row.

NHS Password Standard Changes

Following an internal review of the implementation of the changes applied to the password security functionality over the previous two releases of SCI store (Builds 6.1.1042 and 6.1.1046) the following enhancements have been made in this area: -

1.      Last Access Summary – The functionality of this control has been amended to highlight part of the text in red if the number of invalid login attempts since the user’s last successful log is not equal to zero. This is intended to make it more visible to a user at login time where invalid login attempts have been generated against their account.

2.      Administrator Password Change – When the System Administrator resets a user account password via the ‘Change Password’ action on the ‘User maintenance’ screen, the user will be forced to change the password on their next log in attempt. This will only apply to accounts which are set to ‘Local’ and ‘RolesOnly’ user types.

                      

           Web Service Changes: -

A new ‘GetCumulativeReport’ web service method has been added to the Version 6.0 web services. This new web service call will allow users to access the same dataset which is available in the new Ad Hoc Cumulative Reporting screen.

Resolved Issues: -

Tracker 8113 - Performance Issue When Viewing Admin Tab - Query Timeout – An issue with the traffic lights within the Admin Tab failing to display was reported by NHS Lothian. Analysis revealed that a timeout was occurring when the stored procedure which retrieved the data from the database was running. The stored procedure has been revised in this release of SCI Store and the issue has now been resolved.

Tracker 8118 – Retire Document Error when PackageID > 30 characters - An issue was reported where users were unable to retire documents when the ‘PackageID’ value in the document metadata was greater than 30 characters in length. Investigations have revealed that this was due to incorrect sizing of the ‘PackageID’ field in the t_PatientDocumentSearchHistory’ database table. This should have been set to be able to store up to 255 characters of data (the maximum permissible size for this field as defined by the XML schema). The field was incorrectly set to a size of 30 characters.

The field size has now been amended to enable it to store 255 characters, which has resolved this issue.

Tracker 8306 - 'Error Occurring' When Performing Manual Match – NHS Dumfries & Galloway recently reported an issue when performing a Manual Match via the exceptions management screen. When performing the Action (Add Alias, Update etc) the following error was being returned - 'Error occurred performing manual match.' This has been investigated and a code fix to resolve the issue has been implemented in this release of SCI Store.

Tracker 8324 - Organisation Appearing More Than Once In View Permissions – NHS Tayside recently reported a bug whereby when searching for an organisation when trying to add a practice view permission. On occasion the same organisation was erroneously being returned twice in the search results. The cause of this issue has been investigated and a code fix to resolve it has been implemented in this release of SCI Store.

Tracker 8327 - Duplicate Results Data Being Returned in WS Version 4.1 and 6.0 ‘FindResult’ Response – An issue was found whereby when a ‘FindResult’ web service call was made which contained ‘Patient Identifier’ information, it was incorrectly returning multiple copies of the same test results. This scenario was occurring in instances where patients had a number of duplicate identifiers associated with them. Flagging the duplicate identifiers as ‘not current’ via the ‘Remove Patient Identifiers’ functionality should have prevented this from happening. However, this was not the case as the web service retrieval query was not excluding the identifiers which were marked as ‘not current’ from the returned result set – which was resulting in the multiple results being returned.

The retrieval query has now been amended to cater for this situation and the duplicate results will no longer be returned.

Tracker 8378 - Treatment Log - TRClinicalCodeSelectedTerm Column Size Issue – The Treatment Log <gen:ClinicalCodeSelectedTerm> tag is defined as having a maximum permissible length of 198 characters. It was discovered that the database field for storing this value was incorrectly sized as 50 characters. This was resulting in <gen:ClinicalCodeSelectedTerm> tag data in incoming XML files which exceeded 50 characters in length being truncated when saved to Store. This issue has been resolved in this release of SCI Store.

Tracker 8396 - Treatment Log Assessed Urgency Reason Issue – It was reported that Treatment Log records which contained an <sci:AssessedUrgencyValue> tag, but not an accompanying <sci:AssessedUrgencyReason> tag were raising a parsing error during the SCI Store file processing process. Investigations revealed that the SCI Store parsing routine was enforcing incorrect validation in this circumstance. The issue has been resolved in this release of SCI Store. The correct behaviour regarding the presence / non presence of these particular tags has been implemented and is summarised below: -

 

·         Treatment log records will be successfully processed with an <sci:AssessedUrgencyValue> tag present and either on its own, or with an <sci:AssessedUrgencyReason> supplied.

·         Treatment log records will be successfully processed with neither of the above tags present.

 

 

 

Known Issues with this Release

No known issues with this release

Version of NHSiS General Schema Supported By This Release

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

WebServices 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 2000 SP4

·         Microsoft Windows XP Professional Version 2002 SP2 (for desktop)

·         Microsoft Windows Server 2003 SP2

·         Internet Explorer 6 SP2

·         Internet Explorer 7

·         Microsoft SQLServer 2000 SP4

·         Microsoft SQLServer 2005 SP3

·         McAfee VirusScan Enterprise 8.5.0i Antivirus

·         Microsoft .NET framework v2.0 SP1

·         ClearSpan Management, BridgeForward Software, Inc, Version: 3.4.2 against SQL 2000

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

·         Windows hotfixes.

·         Internet Explorer critical Patches.

·         Gateway Message Sender (Recipient Web Services)

Referral and Discharge Schemas Supported By This Release of Recipient Web Services

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

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.