SCI Store Main - Release Notes

SCI Store Release Notes: Version 8.4.1401

Release Date: - 29/08/2014

New for this Release

System Settings

No changes were made in this release of SCI Store.

Registry Settings

No changes were made in this release of SCI Store.

New Functionality: -

There has been no new functionality introduced in this release of SCI Store. The main purpose of this release was to develop 64 bit components of the application in order to support the installation of the application on the following platforms: -

Windows 2008R2 / SQL Server 2012

Windows 2012 / SQL Server 2012

NOTE: The 32 bit components for installation on the platform of Windows 2003 / SQL 2015 are also still available for this release.

Redundant Functionality: -

Tracker 9783 – Remove Providers 2.3 & 4.1 from The SCI Store Application – The version 2.3 and 4.1 Search Provider mechanisms have been removed from this version of SCI Store. This is due to the fact that they are no longer in use at user sites – having been superseded by the version 6.0 Search Provider.

If any user sites still have any of the version 2.3 and 4.1 Providers defined as a remote data source on the Remote Data Sources Configuration page (‘General > Remote Data Sources’ menu item), the database upgrade script will amend the definition of these sources to the version 6.0 Provider. This will have no functional effect upon the behaviour of the existing Providers, other than that they will now have access to the enhanced remote search features of the version 6.0 Provider which were not available in the older versions (Documents and Treatment Log details).

ClearSpan Management, BridgeForward Software: - This functionality will not be supported in the 64 bit environment. This is due to the fact that the Clear Span software cannot be run in the environment which the 64 bit applications

are run.

Web Service Changes: -

No changes were made in this release of SCI Store.

Resolved Issues: -

Tracker 7383 – HCP record created with a NULL GMCCode value – NHS Dumfries & Galloway raised the following issue: -

For V2.3 of the Document Upload interface, the ‘OriginatingHCP’ and ‘AttestingHCP’ tags are mandatory, however the sub tags within these are not. If no sub tags are specified, a new entry is being incorrectly created within the t14_HealthcareProfessional table with a GMCCode of NULL. Processing another document with no HCP sub tags will create another identical t14_HealthcareProfessional record. This issue has been investigated and has been resolved in this release of SCI Store.

Tracker 9375 - Web Services - Find Document Returns Error When Dates Are Less Than 2000 - An issue was reported with the ‘Find Document’ web service where an error was being returned if the document date searched for was prior to the year 2000 (i.e. the ‘Date From’ and ‘Date To’ search criteria were populated with dates prior to 2000. This issue has been investigated and resolved for all versions of the SCI Store Web Services in this release of SCI Store.

Tracker 9423 – Investigate DateLastEncountered update for t14_PersonalName – NHS Forth Valley reported an issue with the ‘Last Encountered’ date for the ‘previous current name’ being incorrectly updated when a name update occurs. This issue has been investigated and has been resolved in this release of SCI Store.

Tracker 9576 - CHI Refresh After Patient Merge Sometimes Removes References to CurrentDemog's - An issue was reported by NHS Forth Valley where it was noted that following a patient merge transaction the Current Demographics details were being removed from the ‘Master’ patient within the Merge, resulting in an ‘Access Denied’ message being displayed when trying to view the patient. Investigation has determined that this issue was being caused by selecting the child patient from the ‘'PMManageMerges.aspx'’ page immediately after processing a manual merge and then processing a ‘Refresh Demographics from CHI’ transaction operation from the ‘Patient Details’ screen when it loads. Selecting the ‘child’ patient in this way was incorrectly assigning the ‘child’ StoreID when attempting to run the CHI Refresh against the ‘Master’ patient. (in the case of merged patients, the ID of the ‘Master’ patient should always be used when loading) any of the patients involved in the merge. This issue has been resolved in this release of SCI Store.

Tracker 9838 - CHI Refresh after Patient Merge Removes References to CurrentDemog's if Patient Details Page loaded from FindMerges.aspx Page – This issue was found as a result of the testing activities carried out against Tracker 9576 (as described above). Basically, the same issue was being encountered when a CHI refresh was invoked against a patient when the ‘Patient Details’ page has been loaded by selecting the ‘child’ patient in a merge via the following navigation methods: -

a) FindMerges.aspx page (by clicking on the 'View ID's hyperlink)

b) FindMerges.aspx page > Select master/ child patients to load the 'PatientMergesDetail.aspx page > click on the 'Name Changed' link.

This issue has been resolved in this release of SCI Store.

Tracker 9741 - XML60 Merge Transaction Issue - An issue was reported by NHS Forth Valley where XML6.0 merge transactions were failing – the error message ‘Cannot merge a patient to itself’ being returned. Analysis revealed that the root cause of this issue is due to data quality in the PAS system. As several instances of the same patient can exist within PAS whereas generally only one instance exists within Store. Thus when PAS performs a merge, the merge message is sent on to Store, which can result in this type of merge error occurring. The method of handling this type of scenario has been revised in this release of SCI Store to prevent this issue from occurring.

Tracker 9782 - The Results of Child Merged Patients Who Have a Different Registered Practice Than Their Master Patient Cannot Be Viewed- An issue was reported by NHS Lanarkshire where the results of Child merged patients who have a different registered practice than their master patient cannot be viewed, if the user has a view permission restricting them to only see patients registered to the master patient's practice. This issue has been resolved in this release of SCI Store.

Tracker 9800 – User Session Report Sort Order Corrupt When Multiple Grid View Pages Exist – NHS Forth Valley reported an issue when running the User Session report. If multiple pages of results are returned, the first page is sorted correctly (in descending order), but all subsequent pages are sorted in ascending order. This issue has been investigated and resolved in this release of SCI Store.

Tracker 9801 – Duplicate Names and Telecoms Displayed When Patients Are Merged – NHS Forth Valley reported an issue where duplicate names and telecoms were being displayed when a patient is merged, however, only distinct addresses are displayed. The Names and Telecoms tabs should work the same as the address tab in that only unique details are displayed. This issue has been investigated and resolved in this release of SCI Store.

Tracker 9802 – Find Result - Requestor Location Selection Has Leading Characters Removed When Org Code is Less Than 5 Digits – NHS Forth Valley reported an issue with the ‘Find Results’ search screen when selecting a requestor location that has a local code of 4 characters or less. When this occurred the Organisation name had leading characters removed when displayed within the ‘Requestor Location’ text box. This issue has been investigated and resolved in this release of SCI Store.

Tracker 9807 – Current Address Sometimes Gets Overwritten When XML60 Includes Multiple Addresses \ Names – NHS Forth Valley reported an issue where after a XML60 patient update, the patient record was being left without a current address. The issue occurs when the XML60 message includes two identical addresses in the inbound XML and where the same XML message is sent for a second time. This issue has been investigated and resolved in this release of SCI Store.

Tracker 9808 – NS Maintenance Task Does Not Run Even Though It Is Correctly Configured and Scheduled – NHS Forth Valley reported an issue with the NS Maintenance Task service – which was failing to run despite the fact that it been configured correctly and scheduled to run. This issue has been investigated and resolved in this release of SCI Store.

Tracker 9810 – CHI Registration Service Only Processes 1 Registration Regardless of Batch Size – NHS Greater Glasgow and Clyde reported that ACSC registrations were not clearing. On further analysis, it was noticed that each time the CHI Registration service ran, it only processed 1 Registration rather than the quantity defined by the batch size. This issue has been investigated and resolved in this release of SCI Store.

Tracker 9812 – The Green Tick to Indicate Current Name/ Address Sometimes Does Not Display When Patients Are Merged – NHS Forth Valley reported an issue where after merging two patients, and then looking at the demographics within Store, neither the Name Tab or Address Tab had a green tick to indicate which entry was current. This issue has been investigated and resolved in this release of SCI Store.

Tracker 9816 - Performance Issue with s_PatientADT_SelectByTransIDSource – NHS Greater Glasgow & Clyde reported a performance issue when the s_PatientADT_SelectByTransIDSource stored procedure runs. A missing Index on the PatientADT table has been identified as the cause. This issue has been resolved by adding an appropriate new index to the table in this release of SCI Store.

Tracker 9836 - Find Result Search - Timeouts When Using Any Of The Sample Date Ranges - Missing Indexes – NHS Forth Valley reported a performance issue when invoking ‘Find Result’ searches which incorporated any of the ‘Sample Date’ fields as part of the search criteria – ‘Time Outs’ were being experienced. Analysis revealed that missing Indexes on the ‘Sample Date / Time’ fields in the t14_Sample’ table are the reason for this behaviour. This issue has been resolved by adding appropriate new indexes to the table in this release of SCI Store.

Tracker 9837- Performance Issue With prc_PatientDocumentNotes_sel - Missing Index – NHS Greater Glasgow & Clyde reported a performance issue when invoking the ‘prc_PatientDocumentNotes_sel’ stored procedure. This issue has been resolved by adding an appropriate new index (as advised by GG & C) in this release of SCI Store.

Tracker 9842- Document Navigation Issues When Retired Document Exists – NHS Highland reported an issue regarding users having the ability to view Retired documents when using the Previous/Next navigation buttons on the View Document screen. This issue has 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.0

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