SCI Store Release Notes: Version 7.1.1103
New for this
Release
System Settings
A new System Setting called ‘CloseLogin’
has been introduced in this release of SCI Store to replace the registry
setting of the same name which has been removed. The new System Setting will
have exactly the same functionality as the ‘CloseLogin’ registry
setting had. It will have a default value of ‘False’ – which
will provide the equivalent behaviour as when the registry setting was set to
‘No’.
The available setting values are ‘True’ and
‘False’ – with ‘True’ providing the equivalent behaviour
as when the registry setting was set to ‘Yes’.
A new System Setting called ‘MaintenancePlan’
has been introduced in this release of SCI Store to replace the
‘MaintenancePlanSetting’ registry setting which has been removed.
The new System Setting will have exactly the same functionality as the ‘MaintenancePlanSetting’
registry setting had.
The new setting will have a default value of ‘False’ –
which will disable maintenance plan functionality. The Auto merge functionality
was previously dependent upon the MaintenancePlanSetting’ registry
setting being enabled - this means that sites which use the ‘Auto merge’
module must create an instance of the new ‘MaintenancePlan’ system
setting and set it to a value of ‘True’.
A new System Setting called ‘ServiceTimerInterval’
has been introduced in this release of SCI Store to replace the
‘ServiceTimerInterval’ registry setting which has been removed. The
new System Setting will have exactly the same functionality as the
‘ServiceTimerInterval’ registry setting had. This new setting will
be defined in seconds – as opposed to the milliseconds definition of the
redundant registry setting.
The new setting will have a default value of 10 seconds – the
equivalent of the redundant registry setting default which was 10000
milliseconds. If any sites had the registry setting set to a value other than
10000, they will be required to create the new System Setting following an
upgrade to this build and set the value appropriately.
The setting can be configured between a range of 10 and 100 seconds.
A new System Setting called ‘WebServiceTokenTimeout’
has been introduced in this release of SCI Store to replace the registry
setting of the same name which has been removed. The new System Setting will
have exactly the same functionality as the ‘WebServiceTokenTimeout’
registry setting had. It will have a default value of 10 minutes – which
will provide the equivalent behaviour as the previous default setting of the
registry setting.
The available setting values are ‘True’ and
‘False’ – with ‘True’ providing the equivalent behaviour
as when the registry setting was set to ‘Yes’. If any sites had the
registry setting set to a value other than 10, they will be required to create
the new System Setting following an upgrade to this build and set the value
appropriately.
The setting can be configured between a range of 5 and 30 minutes.
A new
System Setting called ‘NSDeleteEventDays’
has been introduced in support of the Notification Services enhancements that
have been incorporated into this release. It is anticipated that patient
events will be generated in high numbers - these events should be deleted after
a user-specified amount of time to ensure the database table does not get too
large. This new system setting allows the System Administrator to define the
number of days after which processed events will be automatically deleted.
The
default value for this new System Setting is 60 days. The setting can be
configured between a range of 1 and 365 days.
Registry Settings
The ‘CloseLogin’ registry setting has been removed in this release
of SCI Store. It has been replaced by the new ‘CloseLogin’ System setting as described above.
The ‘MaintenancePlanSetting’ registry setting has been removed in
this release of SCI Store. It has been replaced by the new ‘MaintenancePlan’ System setting
as described above.
The ‘ServiceTimerInterval’ registry setting has been removed in
this release of SCI Store. It has been replaced by the new ‘ServiceTimerInterval’ System
setting as described above.
The ‘WebServiceTokenTimeout’ registry setting has been removed in
this release of SCI Store. It has been replaced by the new ‘WebServiceTokenTimeout’ System
setting as described above.
The 'Apex_Override_Discipline' registry setting has been removed in
this release of SCI Store. This setting has been removed as it is no longer
required by user sites.
A new registry setting called ‘NotificationProcessingMode’ has been created in support of
the enhanced Notification Services functionality that has been incorporated
into this build of SCI Store. The new implementation of Patient Notifications
uses the Store Windows Service to create and process notifications.
This new registry setting can be checked by the windows service.
This setting will determine whether to run all services or only the store
notification services. This will allow an instance of the Store Windows
Service to be installed on another box for the purpose of solely running the
notification services.
The values permissible values are as specified below: -
0 = Run Notifications within the normal service modes (This will be the
default installation value)
1 = Run only notification services
2 = Do not run any notification services
The registry setting will over-ride anything
set in the ‘WindowsServiceMode’ system setting.
Mandatory Fields Registry Settings
Following discussions with user sites, the mandatory field registry
settings have been reviewed – those which are no longer required by user
sites have now been removed from the SCI Store application. As a result only 4
fields on the ‘Find Patient’ search screen can have their behaviour
altered by the remaining registry settings. All registry settings relating to
the ‘Find Result’ search screen have been removed. The details of
the remaining registry settings relating to the ‘Find Patient’
search screen are as follows: -
|
Field Name /
Registry Setting Name |
Available Default
Value |
Available Mandatory
Setting |
Available Comparator
Settings |
|
Identifier |
N/A |
Yes / No |
equals,
begins, contains, index (equals), index (begins) |
|
Forenames |
N/A |
Yes / No |
equals,
begins, contains |
|
Surname |
N/A |
Yes / No |
equals,
begins, contains, soundex |
|
Have
Results |
Yes / No |
N/A |
N/A |
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 2000 Notification Services component has been removed from the application
as it is no longer required.
·
The
SQL 2005 patient notifications functionality has been removed from the SQL 2005
Notifications component. Enhanced patient notifications functionality has now
been incorporated into the core Store functionality.
·
Result
notifications will still be handled by the SQL 2005 Notification Services
component.
·
The
new Web Service version 7.1 has replaced the separate ‘Add’ and ‘Amend’
patient and result Web Services
with more generic ‘AddSubscription’ and ‘AmendSubscription’
services – which can be used for both patient and result subscriptions. Additionally,
the ‘GetMySubscriptions’ service has been replaced with a new ‘FindSubscriptions’
service.
·
The
Windows Service has been extended to process Patient Notifications.
·
The
new ‘NotificationProcessingMode’ Registry setting has been added. This
new registry setting can be checked by the windows service. This setting
will determine whether to run all services or only the store notification
services. This will allow an instance of the Store Windows Service to be
installed on another server for the purpose of solely running the notification
services.
·
Functionality
has also been added to delete Treatment Log notification events.
·
The
Patient Notification type has been extended to include the following additional
fields: -
·
CHI
·
Record
Type
·
Record
Key
·
Transaction
Type (match action)
·
Patient
Process Events (xml snippet of demographic changes)
HL7 Query Service: -
A change request was recently submitted and
approved to enable SCI Store to supply 3rd party systems with patient
demographics data via an HL7 Query request and response mechanism. The implementation
of this functionality is summarised below: -
The SCI Store HL7
Query Service was created to enable this feature. This new socket interface, runs
as a Windows Service that “Listens” on an agreed IP Address and
Port Number for incoming patient request messages from 3rd party systems. The various settings for the service
is configured via an XML configuration file “SCIStore.HL7Query.exe.config”
– which is located in the default installation path folder, normally “C:\Program
Files\SCI\SCIStore\SCIStore.HL7Query\”. On receipt of a request the
Service translates the request into a SCI Store ‘FindPatient’ Web
Service request and in turn sends this request to the SCI Store Web Service
defined in the service configuration. If a patient is found, the Service will
then perform a ‘GetPatient’ Web Service request using the returned
patient identifier. The response from this will then be translated into an HL7
Query response message and passed back to the client using the socket created
in the initial HL7 request.
Full documentation for this new functionality can be obtained from the
SCI Store Support Team.
Tracker 444 –
Find Result Screen - Requestor Location Search Enhancement - In previous releases of SCI Store,
when selecting a ‘Requestor Location’ from the ‘Find
Result’ search screen, all locations in the database were available from
the search popup. This meant that it was possible to select a location which
did not actually have any results associated with it – which would
subsequently result in no records being returned by a search.
This functionality has been enhanced in this release of store - the
'Requestor Location' search on the 'Find Result' search screen will now
only display the organisation values that are associated with results held in
the database, and not all organisations held in t14_Organisation table. This
will be achieved by only returning organisations which exist in the
'RequestingOrg' field of the t14_TestReport' table (i.e. only organisations
which have been defined as Requesting Locations against test results held in
Store.
As a result of this change, it will not be possible to select an item
from the 'Requestor Location' search on the 'Find Result' search screen
which is not associated with at least 1 result.
Tracker 7461 - V6.0 XML: Treatment
Log : Add the Capability to Search on Remote Stores for Treatment Log Records – The Version 6.0 Search Provider
functionality has been extended in this release of SCI Store to allow users to
search for and view Treatment Log records. This facility has not been
implemented against the Version 2.3 and 4.1 Search Providers will only be
available between SCI Stores at this version or above (7.0.1103). To facilitate
this, the following screens have been enhanced: -
Find Treatment Log Search Screen – Users who have been granted
permissions to access a Version 6.0 Search Provider – and provided that
the ‘ShowRemoteDataSources’ System Setting is enabled – will
be able to select a remote data source to search against from the list of
‘Available Data Sources’ which will be available at the bottom of
the ‘Find Treatment Log’ search screen. This will function in a
similar manner to the remote store search functionality which exists on the
‘Find Patient’ Search screen. When searching against remote Stores
on this screen, the ‘Treatment Log ID’ comparator will be disabled
and set to a value of ‘equals’. A ‘begins’ search against
Treatment Log Identifiers is not permitted when searching against remote
Stores.
Patient Details Screen – When remote patients are
accessed and the ‘Patient Details’ screen loaded (i.e. following
selecting a patient from a remote search on the ‘Find Patient’
search screen), if the version 6.0 Search Provider is used an additional
‘Treatment Log’ tab will be displayed. This tab will display and
function as per the ‘Treatment Log’ tab when viewing a
‘Local’ patient. When viewing the ‘Patient Details’
screen for remote patients returned for the Version 2.3 and 4.1 Search
providers, no ‘Treatment Log’ tab will be displayed.
Remote Data Source Configuration
Screen –
When selecting the ‘Test Configuration’ button on this screen for a
Store Version 6.0 provider, the capabilities message has been revised to advise
the user that ‘Treatment Log’ functionality is now available for
this version of the Search Provider.
Tracker 7667 – Revision of
Ordering of User Notes for Results – In previous versions of
Store, when adding \ viewing results notes on the ‘'Add/View Notes' page,
the display order of the notes was oldest first. In response to user
feedback indicating that this can be confusing, we have revised the display
ordering on this page to be ordered by newest first most recent first. This
will function in a similar manner to that of the
Tracker 7827 - Manual Document
Upload Interface - Requires Enhancement To Allow UCPN Details to be Added To
Metadata
– The manual document upload screens have been updated to allow users to
associate a UCPN with the document being uploaded. A new ‘UCPN’
field has been added to the screen to facilitate this. The new field is
optional, but validation has been applied when the field is populated to ensure
that the UCPN format is subjected to the same formatting rules enforced in the
XML schemas which support UCPN’s in other SCI Store interfaces.
Tracker 8653 - Treatment Log
Search: Remove The Ability To
Navigate To The Patient Details Page From The Treatment Log Search Results – In previous
versions of SCI Store, the ‘Find Treatment Log’ search results
allowed the user to navigate directly to the ‘Patient Details’ page
by clicking on the ‘Name’ column in the search results grid. This functionality
has been removed and clicking on any part of a search result row will only
navigate to the ‘Treatment Log Details’ page. This makes the behaviour
on this page consistent with the behaviour on the ‘Find Results’
page search results grid.
Tracker 8655 - Module Permissions:
Add New Module Permission for Ad Hoc Cumulative Reporting Screen Access – In the previous
version of SCI Store (7.0.1102) a new ‘Ad Hoc Cumulative Report’
screen was added. User permissions to access this new screen were combined with
the existing ‘Cumulative Report’ module permission. Thus if a user
was granted the ‘Cumulative Report’ module permission, they were
permitted to access both the existing ‘Cumulative Reporting’ screen
and the new ‘Ad Hoc Cumulative reporting’ screen.
In
response to user requests, this has been revised for this release of SCI Store
and a new ‘Ad Hoc Cumulative Report’ module permission has been
added to the ‘Results’ category of the ‘Edit Module
Permission’ screen to allow access to the two Cumulative Reporting
screens to be granted independently.
By
default, the new module permission will only be granted to the System
Administrator. Thus, following the upgrade process, users who require access to
the ‘Ad Hoc Cumulative reporting’ screen will require to be granted
the new module permission by the System Administrator.
Tracker 8660 - User
Notes: User Notes Are Being
Displayed Under The Reports Comments Section Of The Result Details Page – In testing it was noticed
that User Notes added to test results via the SCI Store front end were being
incorrectly displayed in the ‘Report Comments’ section on the
‘Result Details’ page. This has been revised in this release of SCI
Store. User notes will now only be viewable via the ‘Add / View notes
functionality.
Tracker 8695 – Remove
Navigation Control from User Notes Page and Revise Printer Friendly View – The
‘Add/View Notes’ page has been revised as follows: -
·
The navigation control on the toolbar has been removed.
·
The ‘Printer Friendly’ view and output has been revised. The
Input text box and the associated 'Add' button will no longer be displayed.
Only the actual details of the existing 'User Notes' will be present.
Web Service Changes: -
A new version (7.1) of the SCI Store Web Services has been implemented
in this release of SCI Store. The new version has been created to support the
Notification Service enhancements incorporated in to this release. The full
details of the changes are documented in the StoreWS 7.1 Developer handbook.
Resolved Issues: -
Tracker 7938 -
Document Organisation Text Being Truncated on Front End Displays – It was noticed during
testing that the 'Document Organisation' text when displayed on the 'Document
Information' and 'Documents Uploaded Details' pages is being truncated when the
text length exceeds 60 characters in length. Investigations revealed that the
‘DocumentOrganisationName’ fields in the document tables of the SCI
Store database were incorrectly defined as having a length of 60 characters.
This issue has been resolved in this release of SCI Store – the field
size has been increased to 70 characters. This matches the maximum length of
organisation names allowed in the ‘t14_Organisation’ lookup table,
which is populated with organisation details from the Reference Data upload
files.
Tracker 8518 - Search
Provider View of Merged ID's Incorrect if Merged Patients Have Duplicate
Identifiers – The
following issue was identified during testing when viewing patient identifiers
of merged patient via a Search Provider: - “If merged patients share any
duplicate ID's across their individual patient records prior to the merge, the
duplicate identifiers are displayed multiple times when viewed via a remote
search provider through the SCI Store front end user interface. However when
viewed via the 'local' store, the duplicate id's are displayed
distinctly”.
This issue has been resolved in this release of SCI Store. The shared
identifiers are now displayed without duplication on both the ‘local’
and ‘search provider’ views.
Tracker 8522 - Store
to Store issue when result exists without ReportType (Discipline) – The following issue was
recently reported by NHS Grampian: -
After Grampian setup Store to Store to access Lothian, the following
error was returned while viewing a patient:"Unexpected error encountered
Conversion from type 'DBNull' to type 'String' is not valid"
Analysis revealed that this issue was caused by patient results files
being loaded at the remote site which did not contain ‘Discipline’
values. When being retrieved remotely via the search provider, the lack of a
discipline in 1 or more of the patient test result set was causing the patient
load to fail. Code changes have been made to prevent this scenario from
occurring in future. Where a ‘Discipline’ is not present in an
incoming result file, a default value of ‘ResultOther’ will be
stored as the discipline.
Tracker 8589 - XML60
ADT Parsing Error When C/D Used In Matching Rules – NHS Greater Glasgow & Clyde raised
an issue regarding the fact that Version 6.0 XML ADT files were failing to
parse when the parsing interface was configured to carry out a CHI Web Service
lookup. This issue has now been investigated and resolved.
Tracker 8608 -
Abnormal Flag Showing Incorrectly Against XML Version 2.1 Results – It was discovered that some sites
are submitting numeric test results to SCI Store in XML Version 2.1 format
which have no reference range – an example of the tags being incorporated
into the results is shown below: -
<gen:ReferenceLimit>
<gen:ReferenceLimitNumeric>
<gen:RangeHighValue />
<gen:RangeLowValue />
</gen:ReferenceLimitNumeric>
The Store Implementation team discovered a defect where test results
which were being submitted in this format were incorrectly being flagged as
‘abnormal’ on the SCI Store front end user displays. This issue has
been resolved in this release of SCI Store.
Tracker 8579 -
"Conversion From Type 'DBNull' to Type 'String' is Not Valid"
Exception Within New Ad Hoc Cumulative Reporting Screen – It was reported by NHS
Lothian that there was an issue with the Ad Hoc Cumulative Reporting screen
when attempting to view test results which contain NULL values in the numeric
result fields. An unhandled exception was being generated. This issue has been
resolved in this release of SCI Store.
Tracker 8603 - Partial
Structured Previous Name fails on WS 6.0 GetPatient Response – The following issue with
the Version 6.0 ‘GetPatient’ response message was reported by NHS
Grampian: -
Patients within NHS Grampian have some previous names with a Structured
Name that only contains a family name value. This causes a SOAP exception via
WS 6.0 ‘GetPatient’ response when attempting to retrieve their
details.
This issue has been resolved in this release of SCI Store.
Tracker 8667 –
Performance Issues at Lothian - Missing Indexes – In response to recent performance
issues encountered at NHS Lothian when logging into Store, some additional
indexes have been added to the Store database to resolve the issues.
Tracker 8669 -
Performance Issues at Grampian - Missing Indexes - In response to recent performance issues
encountered at NHS Grampian when logging into Store, some additional indexes
have been added to the Store database to resolve the issues.
Tracker 8684 - Outstanding Notifications Audit Report Sorting and Display Issues
– A number of issues with the Notifications Audit Report screen were
recently raised by NHS Greater Glasgow & Clyde. As a result, the following
changes have now been made to the user interface behaviour of this screen. The
details of the changes are listed below: -
·
Outstanding
and Consumed messages are now displayed in descending order of 'Date Created'\ ‘Date
Consumed’ - i.e. most recent at top of list
·
A
‘Clear’ button has now been implemented to allow search results and
criteria to be cleared.
·
Standard
paging has been implemented - 20 items per page.
·
Standard
‘Records per page’ and ‘View All’ has been implemented.
Tracker 8690 - Exceptions Management Parsed Files Report Error Handling Incorrect
- An issue was reported by NHS Greater Glasgow & Clyde which highlighted an
instance of incorrect error handling when running the Parsed Files Exceptions
mgmt report. The issue was discovered when running a search using a selection
from the 'Service Name' drop down only – which was resulting in a timeout
occurring and no search results being returned. An appropriate error message was
not being returned to the user to indicate the source of the problem.
The issue has now been resolved and if a timeout should occur in future,
an appropriate error message will be fed back to the user to indicate the source
of the problem. In addition, in an attempt to prevent users from using too wide
a range of search criteria on this page in future – and thus minimising
the risk of search timeouts occurring the search criteria validation has been
amended. A warning dialog – which can be overridden by the user –
will be displayed when the ‘Search’ button is invoked if the
following two search rules are not adhered to: -
·
The
'wide ranging search criteria' popup dialog will be displayed if more than a 30
day date range is specified in the 'Transaction Date From' and 'Transaction
Date To' fields on any specified
search.
·
The
'wide ranging search criteria' popup dialog will be displayed if any date range is specified in the
'Transaction Date From' and 'Transaction Date To' and NO other search criteria is specified on any search.
In order to maintain consistency across the exceptions
management screens, the rules defined above have been implemented on the
following additional screens: -
§
Exceptions Management > Uploaded Files
§
Exceptions Management > Documents Uploaded
§
Exceptions Management > ACSC Registrations
When any of the 4 exceptions management pages
described above are loaded, by default the ‘Date From’ field will
default to a value of 30 days prior to the current date and time. The
‘Date To’ field will be blank and the search will be assumed to
incorporate the time period between the default ‘Date From’ value
and the ‘current date and time’.
Tracker 8695 - CHI Save
to Store Could Display An Incorrect Error Message - An issue was reported by NHS Greater Glasgow
& Clyde which highlighted an instance of incorrect error handling which
could occur when a match rule is applied to the CHI lookup service that could
generate a match exception when a CHI save to store is action performed. In
this circumstance the normal 'Success' message was being incorrectly fed back
to the user despite the fact that the CHI patient details were correctly
not being saved to Store. This issue has been resolved in this release of SCI
Store. The correct error message of "Error saving patient from CHI
database" is now being fed back to the user if this scenario occurs.
Tracker 8718 - CHI
Registration Service Processes 1 Registration Rather Than Batch Size - An issue was reported by NHS Greater
Glasgow & Clyde where it was found that the CHI Registration Service was
ignoring the configured batch size and processing the waiting registrations
from the ACSC Registration queue one at a time each time the Store Service was
run. This issue has been resolved in this release of SCI Store. The configured
batch size will be used for this interface each time the Store Service
component is run.
Tracker 8737 - User
Maintenance Screen - 'Save' Icon Incorrectly Displayed – The following
issue with user maintenance security permissions was recently reported by NHS
Grampian: -
“When a User account has only been given the 'User
Configuration' and 'Change Password' module permissions from the 'Security'
group (to allow password administration), the 'Delete' icon is incorrectly
displayed and the 'Save' icon is incorrectly displayed when an attempt is made
to delete a User account that has already been used. The User can then modify
and save the account.”
This issue has been resolved in this release of SCI Store.
Tracker 8760 -
'ServiceProcessMode' System Setting - Multi Threading - With The Doc to DB In
Separate Thread, The Maintenance Process Is Omitted Completely – An issue was recently
raised by NHS Lothian regarding the use of the ‘ServiceProcessMode’
System Setting and running scheduled auto merge tasks. When scheduling an auto
merge task on Lothian, the task never actually ran. Investigation revealed that
this was due to the fact that they had configured the ‘ServiceProcessMode’
system setting to a value of ‘Tasks will run in separate thread based on
task type (Separate thread for fileuploadparser and doctodb)’. A defect
in the code was preventing the scheduled task from being run in this mode.
This issue has now been resolved and scheduled auto merge tasks can now
be run for all four configurations of the ServiceProcessMode System Setting: -
o
All
tasks in one thread (including planned maintenance)
o
All
service tasks in one thread, planned maintenance and Treatment Log
Notifications in separate threads
o
Tasks
will run in separate thread based on task type (Parser type included fileupload
and doctodb)
o
Tasks
will run in separate thread based on task type (Separate thread for
fileuploadparser and doctodb)
Tracker 8766 - Flagging Document as 'Actioned'
Returns Foreign Key Constraint Error – The following issue was reported by
NHS Greater Glasgow & Clyde:-
When a document upload failed due to the error ‘'Could not find
document' being encountered because the document associated with the upload
metadata was not available, attempts to set the exception management status to
‘Actioned’ via the document exception management screens were
returning an unhandled ‘foreign key constraint error.
This issue has been resolved in this release of SCI Store.
Tracker 8799 - Related to work item
8799 - Performance Issue with the User Maintenance Screen – An issue was reported by
NHS Greater Glasgow & Clyde where timeouts were occurring when trying to
access the User Maintenance screen. Searching for the user was OK but clicking
the Row to access the details was timing out resulting in an error screen being
displayed. This issue has now been resolved in this release of SCI Store.
Tracker 8821 - Advice
Request and Advice Response Gateway Message Types Missing From SCI Store
Recipient Web Service Project – An issue was recently reported by NHS Greater Glasgow &
Clyde that when testing Gateway Version 1.0 Advice Request and Version 1.0
Advice Response message types, that they were not being processed into Store.
On further investigation, it was noticed that these messages were not supported
by RWS.
The Recipient Web Services component has been extended in this release
of SCI Store to enable it to process both of these Gateway message types.
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.