SCI Store Release Notes: Version 8.3.1301
Release Date: -30/09/2013
New for this Release
System
Settings
Three new System Settings have been added in support of the new Web Service Access to Remote Stores functionality which has been implemented against the Version 8.1 Web Services in this release of SCI Store: -
GetPatientsDocumentListMaxRequests - This defines the maximum number of patients that can be requested for the ‘GetPatientsDocumentList’ web method.
GetPatientsResultListMaxRequests - This defines the maximum number of patients that can be requested for the ‘GetPatientsResultList’ web method.
FindPatientMaxRequests - This defines the maximum number of locations that can be requested for the ‘FindPatient’ and ‘Locate Patient’ web methods.
All three are defined as Type - Integer with a range between 1 and 20 and a default value of 5
.Registry Settings
No changes were made in this release
of SCI Store.
New Functionality: -
Tracker 7942 – Extend
Browser support for full standards based HTML5 – The main user screens in the application have
been enhanced to support HTML5 standards. As a result the main user screens in
the application have been tested and verified as fully functional in the
following browsers: -
·
Internet
Explorer 8.0.6001.18702
·
Safari
(version 5.1.7 for windows)
·
Chrome
(version 27.0.1453.93 m )
·
Firefox
( version 21.0)
All of the above browser versions
were the latest available at the time of testing. It should be noted that
Internet Explorer version 6 is no longer supported.
Tracker 6255 - Extension of Translator Interface Service Definition to
Allow or Disallow Updating of Specific Demographic Information – The following service types
have been enhanced to incorporate the addition of new checkboxes which will
allow System Administrators to explicitly allow or disallow the update of demographic
information when data is imported to SCI Store: -
·
TranslatorFromDatabase
·
CHILookup
·
DocumentToDatabase
The new checkboxes added to the
configuration screens for each of the above service types: -
·
CHI
·
Patient IDs
·
Name
·
Address
·
Postcode
·
Source
Following the database upgrade for
this release, all of the new checkboxes on all existing service types of the
three types specified above will be set to a default value of ‘enabled’ – which
equates to the same update functionality for these items which was present
prior to the upgrade.
From this release forward, when any
new instances of the above three service types are created, all of the
demographic checkboxes will default to a value of ‘disabled’ on the applicable configuration screens.
Web Service Changes: -
Tracker 9517 – Access Remote
Stores Via Web Services –
SCI Store web services v8.1 has been extended to allow web service users
to query remote SCI Stores locations.
In order to facilitate this functionality, a new ‘Site Code’ field
has been added to the Remote Data Source Configuration ‘screen. This will
allow a unique ‘Site Code’ value to be defined for each Remote Data
Source. The following rules have been applied to the ‘Site Code’
field: -
·
Site
Codes must be unique
·
The maximum
permissible length is 20 characters
·
Site
Codes with a value of ‘CHI’ or ‘LOCAL’ are not
permitted
Following the upgrade to this release of SCI Store, all Site Codes will
be set to NULL values. It will be the responsibility for each site to populate
the ‘Site Code’ values appropriately.
Specific changes have been summarised below: -
·
A new
web method GetProviderLocations allows a web service user to retrieve a
list of valid sites that they can access.
·
A new
web method LocatePatients allows a web service to search multiple
locations in one web service call to determine whether a patient exists at a
location. For each location specified in the request a match will occur on
Surname, dob and CHI.
·
A new
web method GetPatientsResultList allows a user to retrieve a summary
list of results for a patient across multiple locations.
·
Extend GetResult
web method. This was enhanced to allow a result to be retrieved from a remote
location.
·
A new
web method GetPatientsDocumentList allows a user to retrieve a summary list
of documents for a patient across multiple locations.
·
Extend GetDocument
web method. This was enhanced to allow a document to be retrieved from a remote
location.
·
Extend FindPatient
web method. This was enhanced to allow a user to search for patients in remote
locations. Existing pre-defined “Local” and “CHI”
locations are preserved.
·
Extend FindResult
web method. This was enhanced to allow a user to search for results in remote
locations.
·
Extend FindDocument
web method. This was enhanced to allow a user to search for documents in remote
locations.
Resolved
Issues: -
Tracker 9150 - Merging Patients is
Incorrectly Hiding Certain Results – NHS Lanarkshire reported an issue whereby merged patients results were being
incorrectly hidden if the report identifier was the same. The issue was arising
because the report was being incorrectly flagged as a merge duplicate in Store
if the report identifier was duplicated, but the report type (discipline) was
not. They should only have been flagged as merge duplicates if both the report
identifier and report type were identical. This issue has been resolved in this
release of SCI Store
Tracker 9159 - Interface Configuration
Screens Not Refreshing Correctly When Changing and Saving Values – The following two issues were identified
during the testing of this release: -
1. The Amend Interface screen
(ServicesAmend.aspx) was not refreshing correctly when changing Status from
'off' to 'on'
2. The Amend File To Database screen (AmendFileToDatabase.aspx)
also has issues when changing values and saving:-
o
Both the
'Requires Splitting?' and 'Delete After Splitting?'
option buttons when amended and the 'Save' icon selected were not persisting
the change when the screen is refreshed. However, if you the user exits the screen and then returns to it, the amended values
have been changed.
o Similar issues were occurring when the
'Archive Directory' and 'Exception Archive Directory' fields and associated
checkboxes were amended.
All
of the above user interface issues have been resolved in this release of SCI
Store.
Tracker 9181 - Amending Splitter
Service Details Inserting a New Entry In The Database Instead Of Updating The
Existing One - The following issue
was identified during the testing of this release: -
If a user defines a
‘SplitterFromDatabase’ service, an entry is added to the
‘t14_Service table’ in the database. When the service is configured
on the 'Amend Splitter From Database Service
Definition' screen (AmendSplitterFromDatabase.aspx) an associated entry is
added to the ‘t14_SplitterFromDatabase’ table. However, it was
noted that if the service configuration is subsequently amended immediately
(without exiting the screen) and the amendment saved, new entry with the same 'ServiceID'
value was being incorrectly added to the ‘t14_SplitterFromDatabase’
table. Clearly, the original entry in the
‘t14_SplitterFromDatabase’ table should be updated under these
circumstances.
This issue has been
resolved in this release of SCI Store.
Tracker 9392 - Manage Duplicates - Match Criteria Being
Incorrectly Applied When Selected as a Candidate Filter - An issue was reported by NHS Lanarkshire
where ‘Manage Duplicates’ searches where the ‘Candidate
Filter’ DOB Range – if populated was being incorporated into the
Search Criteria incorrectly when the DOB ‘Match Criteria checkbox was
disabled. This issue has been resolved in this release of SCI Store.
Tracker 9394 - Manage Duplicates - Patients Duplicated
on Search Results List for ID Searches – An issue was reported by NHS Lanarkshire where ‘Manage
Duplicates’ searches were returning multiple instances of the same
patient when invoking searches which contain the Match Criteria of
‘Ids’. This was occurring where patients were found who had common
patient identifier values – for each identifier that was shared an
instance of the patient was being incorrectly returned by the search. This
issue has been resolved in this release of SCI Store.
Tracker 9430 – Postcode Format
Incorrect in SCI Store Database – NHS Fife reported an issue where the postcode format was being
incorrectly stored in the SCI Store database. Analysis revealed that this only
was occurring when patient notification services functionality is enabled.
Amendments have been made to the application to ensure that the correct
postcode format is stored in the SCI Store database when patient notification
services is enabled and disabled.
Tracker 9432 - Notifications
Maintenance Task Service Configuration Page Generates Script Errors When
Amended – An issue was
recorded during testing where it was discovered that a script error was being
generated when interacting with the checkboxes on the Notification Maintenance
Service configuration screen. This issue has been resolved in this release of
SCI Store.
Tracker 9482 – Address
Formatting Incorrect When Retrieving Patient Details From CHI Data source - The following defect was reported
during the testing of version 8.2.1202 of Store: -When patient demographic
details are retrieved from the CHI database via a CHI search provider
'Find patient' search, the returned address details are being incorrectly
displayed with separator characters between each address line. The issue has
been resolved in this release of Store.
Tracker 9489 - S2S Issue When
Accessing a Result That Includes Anatomical Code and Description – NHS Borders reported an
issue where the 'Access Denied' screen is displayed when accessing a particular
result via Store to Store. On further investigation, the issue occurred for both
Store41 and Store60 providers when accessing a remote result that included an
Anatomical Code and Description. This issue has now been resolved in this
release of SCI Store.
Tracker 9498 - Object Reference Error When
Clicking Documents Tab Within a Patient Record – NHS Western Isles reported an issue
where an 'Object Reference...' error was being returned when a user clicked the
Documents Tab within a patient record. In the example reported, the user
account had a large number of View Permissions (16 in total).
Investigation revealed that the Stored Proc which built the SQL string was
being truncated due to the size of the SQL string variable created by the
number of View Permissions involved. This was resulting in the execution of the
SQL raising an exception. The String variable size has now been modified by
increasing its permissible size to 4500 characters to resolve this issue and
future proof it against recurring in the future.
Tracker 9515 - XML60 Investigation Report - Sample Clinical Code Being Truncated
If > 20 Characters in Length – NHS GGC reported an issue where Test Codes at
the sample level were being truncated if > 20chars. This was from a Telepath
report, but the same issue occurs when an XML60 report is processed. This issue
has been resolved in this release of SCI Store.
Tracker 9516 - Find on CHI Search Inconsistent For Patients With
Temporary CHI Registration - NHS GGC reported an issue where a patient on CHI with a 'Temporary
CHI Registration' can be found when a ‘CHI DoB’ search is invoked
via Store, however it is not being returned when a ‘Patient
Extract’ (CHI number search) search is invoked. This issue has been
resolved in this release of SCI Store.
Tracker 9565 - Module Permission Template Page Displaying Incorrect Labels On Grid View – NHS Forth Valley reported an issue where it was noted that the ‘Last Updated’ and ‘Updated By’ data displayed on the Module Permissions Template management screens was always displaying the details of the user and creation time associated with the template creation and was not being updated when a change was made the template. When the issue was investigated, the existing behavior was confirmed as correct, but it was recognized that the labels associated with this data could be construed as misleading. The labels have now been changed to ‘Date Created’ and ‘Created By’ more accurately reflecting the current behaviour. NHS Forth Valley have been advised that if they require specific the behavior to be amended – i.e. to displayed the details of the user and time of the last change to the template, then a UCF will be required.
Tracker 9567 – Inconsistency on Date/Time check on ParseFromDbSearch.aspx page - NHS Forth Valley reported an issue where the validation regarding invoking searches where the search criteria incorporated a future ‘Date Time To’ value on the ‘Parsed Files’ and ‘Uploaded Files’ was inconsistent with that of the ‘Documents Uploaded’ and ACSC Registration’ search screens containing a future ‘Date Time To’ value. The validation on the ‘Parsed Files’ and ‘Uploaded Files’ screens have now been adjusted to make it consistent with the other two screens. Essentially, user will now be prevented from invoking searches on all of these screens if the ‘Date Time To’ field is set to a future date.
Tracker 9578 - New Match Rule Name is Changing When Rule is Edited and Saved When Name Contains Special Character – An issue was raised by NHS GGC Patient Matching Rules. The issue occurred when a new match rule was having its name changed and the rule name contained a special character (e.g. an ampersand ‘&’). After editing and saving, the rule name was being truncated after the special character. This issue has been resolved in this release of SCI Store. All special characters - with the exception of the apostrophe character can now be included in the rule name. A validation error message will be fed back to the user if the name contains an apostrophe.
Tracker 9580 - ADTs Are Displaying in Incorrect Order When Action Date /Time Is The Same For Multiple ADT's - NHS GGC reported an issue where ADT's were not displaying in chronological order - noting that the issue was caused by TRAKCARE sending the Transfer and Discharge with the same Action Date /Time. Store was processing these in the correct order but not displaying them chronologically due to the fact that the stored procedure which returns the ADT dataset was sorting on the ‘Action Date’ of the ADT’s. This issue has now been resolved – the ADT’s are now being sorted on both ‘Action Date’ and ‘Event Time’ to ensure chronological display where the ‘Action Date’ is the same for 2 or more ADT's.
Tracker 9590 - Field Permissions Not Being Applied Correctly on Recently Viewed Doc's Tab – NHS Dumfies & Galloway reported a security issue on the Recently Viewed Docs TAB relating to a user still being able to view a document from the list after a field permission data restriction was applied that should prevent access to the document. This issue has been investigated and resolved in this release of SCI Store.
Tracker 9595 - Notification Services - Notification Not Generated by Manual Document Upload – NHS Dumfries & Galloway D&G reported an issue where notifications were not generated when performing a manual document upload. This issue has been resolved in this release of SCI Store.
Tracker 9597 - Issue parsing address when Structured and Unstructured address nodes are provided in XML60 – NHS Forth Valley reported an issue where a patient address was incorrectly updated when an XML60 update file was processed which included a structured address node for the current address and an unstructured address node for a previous address. The patient was erroneously being updated with the unstructured address being shown as the ‘current’ address. This issue has been investigated and resolved in this release of SCI Store. The investigation also revealed the same issue in the XML41 interface and the same fix has been applied to resolve the issue with the XML41 interface.
Tracker 9615 – Patient and Result Audit Reports Timing Out – NHS Forth Valley reported an issue where the Patient and Result audit reports were timing out when run. Additional indexes have been added to the relevant database tables to resolve this issue.
Tracker 9616 - No Sort Order Applied to the 'User Session Admin' Report – NHS Forth Valley reported an issue where the User Session Admin report displayed the returned dataset in a random manner i.e. no SORT order was applied. When many users are on the system and the report is run, it was difficult to read, especially when looking for a specific user name. This issue has been resolved in this release of SCI Store – a sort order having been applied to the procedure which returns the dataset.
Tracker 9654 - ADT - Amendment to a Discharge not updating correctly – NHS GGC reported an issue where an ADT discharge insert and then subsequent amendment did not update the ADT correctly via XML60 interface. The affected discharge messages were associated with an admission (same episodeID), but contained incorrect info in the following fields: - Hospital, Ward and Consultant. This was causing issues with the front end display and the data being stored in the ADT database table. The issue has now been resolved in this release of SCI Store.
Tracker 9658 - HL7 ORUR01 Test Report Message Failing to Parse Due to Exclusion of Numeric Result Value – NHS Grampian reported an issue where an HL7 report was failing to parse. On further investigation, the exception was due to an OBX line being supplied for a numeric result, but where no Numeric Result Value was provided. This issue has been resolved in this release of SCI Store. The solution implemented has defined the following behaviour when this type of result is incorporated in an HL7 result file: -
1. The file will be processed ‘with warnings’ – the ‘status description’ being shown on the ‘Parsed Message’ screen as ‘Completed successfully with warning(s).’
2. The following message will be written to the ‘warning’ column of the ‘MessageParse’ table ‘Warning 1 : Field OBX Set ID 2: did not include numeric result value.’
3. The ‘Value’ for this type of result will be shown as ‘N/A’ on the ‘Result Details’ screen.
Tracker 9666 - Find Result Screen - UCPN Field Not Reset to Default Value When 'Clear' Button Clicked – During testing activities it was noticed that the 'Clear' button on the Find Result search screen 'FindResult.aspx' was not resetting the value in the UCPN search criteria field. This minor cosmetic issue has been resolved in this release of SCI Store.
Tracker 9677 – HL7 Parsing – Next of Kin Relationship Not Persisted - NHS Grampian reported an issue where the NoK Relationship was not being saved when included within the HL7 inbound message. Regardless of what code/description was provided, the relationship was always saved as 99 (not known). This has been resolved in this release of SCI Store and the NoK details are now being saved and relationships correctly maintained.
Tracker 9678 – HL7 Parsing – Next of Kin Address Saved as Historic Entry When Address Type of 'Permanent' Provided - NHS Grampian reported an issue where the NoK Address was not being saved correctly when included within the HL7 inbound message with an address type of 'Permanent'. Instead the address was being seen as historic, and therefore not output via web services. This has been resolved in this release of SCI Store and the NoK address details are now being saved as expected and correctly output via all Store ‘GetPatient’ Web Service calls.
Tracker 9681 - HL7 Parsing - PID Telecom TYPE Not Being Saved Correctly – NHS Grampian reported an issue where Patient Telecom Type was not being saved correctly when included within HL7 inbound message. Regardless of what Telecom Type was provided, it was always being as type 'Phone'. This has been resolved in this release of SCI Store and the Telecom Type details are now being saved as expected and correctly output via all Store ‘GetPatient’ Web Service calls.
Tracker 9682 - HL7 Parsing - Field Permission issue when restriction is DocumentSpecialty = 'xxxx and yyyy''– NHS Dumfries & Galloway reported an issue where they had implemented a new field permission of DocumentSpecialty = 'Drugs and Alcohol'. When applied to a user account, an object reference error was being returned when any screen involving documents was accessed. This issue has been investigated and 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
·
Internet Explorer 8
·
Microsoft SQL Server
2005 SP3
·
Microsoft .NET
framework v4.0
·
ClearSpan Management,
BridgeForward Software, Inc, Version: 3.5.0.6 against SQL 2005
·
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.