The purpose of these Release Notes is to highlight the changes to SCI Gateway that occur in version PDF Free Download

Scottish Care Information SCI Gateway Version 15.0 Release Notes The purpose of these Release Notes is to highlight the changes to SCI Gateway that occur in version 15.0. The major changes are listed on pages III to VII What s New in SCI Gateway version 15.0. Further details are provided on subsequent pages where appropriate. NATIONAL INFORMATION SYSTEMS GROUP

What s new in SCI Gateway version 15.0 for End Users 1 Local News When users log in to SCI Gateway the home page will now have two main sections: SCI News and Local News. Users will see local news items that are relevant to them based on their location. See page 1-2 2 Urgent Suspected Cancer priority SCI Gateway R15.0 now allows for Cancer tracking within the Worklist. See page 1-3 Advice Referral Priority 3 A new referral priority of Advice has been added to the existing priorities, e.g. Urgent - Suspected Cancer, Urgent, Soon, Routine. See page 1-6 Batch Save to Docman 4 Practice users can select a number of received messages and file them all in Docman in a single action. This includes egpfr Requests from the Department for Work and Pensions. See page 1-9 Crown Copyright 2012 III

5 Hide Consultant Drop-down list The consultant drop-down list can be optionally hidden from the New Referral window at the health board s discretion. See page 1-12 6 egpfr Changes Additional saving options are now available for egpfr Requests. Changes have been made to the way payment options are displayed in the egpfr Requests and Responses. See page 1-13 7 GP Data Validation Changes have been made to the way patient data is validated when it is retrieved from GP IT systems. If there is incorrect or missing data a message will be displayed explaining the errors. Users will be able to manually add/amend the data. See page 1-16 8 Ethnicity Categories The Ethnic Origin field in SCI Gateway messages has been increased to hold a maximum length of 70 characters. See page 1-17 Crown Copyright 2012 IV

What s new in SCI Gateway version 15.0 for System Administrators 1 Change Home HCE When a user of SCI Gateway moves from one work location to another Administrators can now move the user from the HCE that they were in to another HCE instead of having to create a new log in for them. See page 2-2 2 Local News Administrators can now create Local News items on the Home Page. End users of will only see the Local News items that are relevant to them based on their Home HCE. See page 2-7 3 Advice Referral Priority There is a new Priority of Advice for Referrals. To use this Referral Priority Administrators will need to amend their referral protocols to include Advice in the Priority drop-down list. See page 2-14 4 Stop Attachments After Message Submitted A new Extra is available which when applied to an HCE prevents attachments being made to messages that have already been sent. See page 2-15 Crown Copyright 2012 V

5 Batch Save to Docman A new Extra is available which when applied to an HCE allows practice users to select a number of received messages and file them all in Docman in a single action. See page 2-18 6 Improved Search Options for Protocol and Stylesheet Maintenance The Protocol and Stylesheet pages have had search options and page numbers added to make it easier to manage Protocols and Stylesheets in SCI Gateway. The HCE Groups pages have also had similar enhancements to improve their functionality. See page 2-21 7 Hide Consultant Dropdown list The consultant drop-down list can be optionally hidden from the New Referral window at the Health Board s discretion. See page 2-27 8 Ethnicity Categories The Ethnic Origin field in SCI Gateway messages has been increased to hold a maximum length of 70 characters. See page 2-29 Crown Copyright 2012 VI

9 Queue Items Visibility The message queuing system in SCI Gateway R15.0 has changed from a single queue for all Health Boards to a queue per Health Board. See page 2-30 10 Recipient Web Service Enhancements A new recipient web service interface has been created so that a third party system can choose to implement to receive messages and notifications from SCI Gateway. See page 2-37 11 Referring to New Branches Where there are new branches in the NHS Directory that do not have an associated Specialty, additional XML will be required in their protocols for those HCEs in order for end users to be able to send messages. See page 2-39 Crown Copyright 2012 VII

Local News When users log in to SCI Gateway the Home Page will now have two main sections: SCI News and Local News. Users will only see the Local News items that are relevant to them based on their Home HCE and for the duration that the health board administrators have determined that the Local News should be displayed. SCI News: configured by NISG at National level Local News: configured by the Health Board Crown Copyright 2012 1-2

Urgent Suspected Cancer Priority SCI Gateway R15.0 now allows for Cancer tracking within the Worklist. It is important for users to be able to differentiate between referral messages which have been classified as Urgent and those which have been classified as Urgent - Suspected Cancer. Urgent Suspected Cancer icon Crown Copyright 2012 1-3

The default setting for new messages is ordered by priority. Therefore when a recipient opens their New Referral Worklist it will be displayed with the Urgent-Suspected Cancer referrals at the top of the Worklist, if they have received any, followed by Urgent: Hospital Receive tab opened for New Referrals with Urgent - Suspected Cancer referrals at the top of the Worklist When users view the All Referrals menu the default setting is in date/time order: All Referrals Worklist Referrals shown in date/time order not in priority order Crown Copyright 2012 1-4

To re-order the Worklist by priority click on the Filter icon: Click here to order by priority Click on Order by Priority menu option to re-order the Worklist. Worklist re-ordered and Urgent Suspected Cancer priority at the top of the list Users can filter on this new priority within the Worklist using the list under the Filter by priority option. Click here to filter the list by Urgent- Suspected Cancer When you filter by priority only referrals from your chosen filter will be displayed for example Urgent Suspected Cancer. Crown Copyright 2012 1-5

Advice Referral Priority A new referral priority of Advice has been added to the existing priorities, e.g. Urgent - Suspected Cancer, Urgent, Soon, Routine. Advice in the Priority drop-down list Referrals that have been given the Advice priority will be differentiated by the icon. Advice priority icon If users of SCI Gateway request advice on how to take a patient s treatment forward and they require a reply from a Consultant/Clinician they must use the Advice Request/Response message types already available in SCI Gateway. The Advice Referral Priority is simply a new priority that is available in referral message types. Only Referral protocols that use the 2.8 schema will have the Advice priority listed in the priority drop-down. If you do not have this option consult your local System Administrator. Crown Copyright 2012 1-6

When the Order by priority menu option is selected on the Worklist, any messages with Advice priority will be sorted last. Order by Priority menu option Advice priority listed after Routine All Advice priority referrals are listed last after choosing Order by Priority When Advice is selected from the Filter by priority option, as shown above only referrals with the priority of Advice will be displayed on the Worklist as pictured below: Only Advice priority referrals are shown Crown Copyright 2012 1-7

Users at the receiving end of SCI Gateway will see the Advice referrals at the bottom of the new referrals Worklist: Hospital Receive tab opened for new referrals with Advice referrals showing at the bottom of the Worklist When the user opens the All Referrals Worklist referrals will be displayed in date/time order: All referrals Worklist Referrals shown in date/time order not in priority order Crown Copyright 2012 1-8

Batch Save to Docman This new functionality allows practice users to select a number of received messages and file them all into the Batch Manager of Docman in a single action. This includes egpfr Requests from the Department for Work and Pensions. If a practice uses Docman there will be a Save to Docman button displayed on the Receive Worklist only. The user can select the messages to be saved to Docman by either clicking the tick box for each individual messages or clicking the tick box in the Worklist heading to select all messages. 1. Select either one or a combination of messages by ticking the select box(es) Click on the Save to Docman button 2. A message will be displayed listing the message types and the name of the associated patient: Click on Ok to continue Crown Copyright 2012 1-9

3 Pictured below is the Worklist displayed after clicking on OK on the message window as described on the previous page: The Filed and Viewed icons are shown for the messages that have been saved to Docman All selected messages will be saved in the same way to Docman as saving individually i.e messages statuses updated and the filed and viewed flags set. If the Save To Docman button is clicked for messages that already have the filed flag set then a message similar to the one below will be displayed: Crown Copyright 2012 1-10

If a user does not have permission to print a message but does have permission to save the message to Docman a tool tip will be displayed. As all locations do not use Docman these Tooltips will only mention Docman permissions if the HCE has the Docman Extra assigned to one or more message types, regardless of the message type being viewed on the Worklist. Pictured below is an example of a screen with the Tooltip displayed showing the user does not have permission to print egpfr Requests. This logged on user does not have permission to print egpfr Requests but can save messages to Docman Pictured below is an example of a screen with the Tooltip displayed showing the user does not have permission to print or save an egpfr Requests. This logged on user does not have permission to print egpfr Requests or save messages to Docman Crown Copyright 2012 1-11

Hide Consultant Drop-down list In order to meet the requirements RTT targets hospital and health board preference is for GPs to refer to a specialty rather than a named consultant. SCI Gateway R15.0 allows the consultant drop-down list to be hidden from the new referral window at the health board s discretion. SCI Gateway R14 view (Current) This HCE is set up to allow the consultant drop-down list as an option SCI Gateway R15 view This HCE is set up to hide the consultant drop-down list from the options Crown Copyright 2012 1-12

egpfr Changes Received egpfr Requests An egpfr Request can be saved to the Batch Manager in Docman using current functionality, provided the relevant Extra (File messages in Docman) for the egpfr Request message type is configured for the GP practice by the Health Board Administrator. Submitted egpfr Responses SCI Gateway R15.0 will automatically save submitted egpfr Response messages to the batch manager of Docman if patient details are missing such as the CHI number, surname, forename and date of birth. If a submitted message (potentially with attachments) is automatically saved to the batch manager in Docman due to patient details not being available, a message will be displayed giving the details of missing/incorrect data: If an attachment is sent after the message has been submitted, and the message has been saved to the batch manager in Docman, a warning message will be displayed: This is an example of a warning message displayed when a follow up attachment is sent after the original message could not be saved to the patient s record in Docman due to missing patient information. Crown Copyright 2012 1-13

Bank details There have been changes made to protect your personal/practice bank details when you add or amend your bank details in the course of completing an egpfr Response. Click on the Payment Details tab on your egpfr Response: Click here to add bank details Select Yes and add details here if required Add new or amended bank details here In the egpfr Response protocol you can see bank details entered however, they will not be displayed in the letter format. When the egpfr Response is previewed or sent and a copy saved to Docman the bank details will be hidden by an * (asterisk) character as shown on the next page. Crown Copyright 2012 1-14

When you view the egpfr Response message that has been saved to Docman or if the patient leaves the practice and their Docman record is sent on to their new GP your practice bank details will remain private. The bank details will be displayed as in the window pictured below: DWP will be able to view the bank details in the egpfr Response using their own IT system which handles the information in a different way. Line spacing in the text of an egpfr Response In previous versions of SCI Gateway if you added a line space to your text in the egpfr Response protocol using the Return/Enter key on your keyboard, when the letter was displayed, the line spacing had been removed. This has now been fixed and line spacing will transfer to the final letter as displayed in the picture below: Crown Copyright 2012 1-15

GP Data Validation When creating messages in SCI Gateway using pre-population from third party systems, for example GP IT systems EMIS and INPS, patient data goes through a validation process to ensure that the data meets the necessary Standards. Previously if any data was missing or not valid, the retrieval of the information would fail and the user would not be able to proceed with sending a message. Changes have been made so that users will be able to receive error messages explaining the error(s) in the patient data thereby allowing them to take action to resolve the issue and continue with sending the message. In the New Referral window after selecting your referral destination options click on Create, your third party system will attempt to retrieve patient information. Pictured below is an example of an error message displayed when the retrieval failed because the patient s post code is incorrect: Click here to save the error message Click here to return to protocol no information will be pre-populated Click here to continue - patient demographics and medical data will be pre-populated excluding the error item Validation message displayed with details of errors No Pre-population - if you select his option you will be returned to the protocol and none of the patient s demographics or medical information will be populated. You have the option to manually enter the information or return to the third party system and amend the patient s details there. Pre-population - if you select this option you will be returned to the protocol and all of the patient s demographics and medical information will be pre-populated except for the information that was indicated as missing/incorrect in the validation message. Crown Copyright 2012 1-16

Change Home HCE Health Board Administrators can now change a user s Home HCE to another HCE. This enables Administrators to easily move a user from one HCE to another if they change their work location. Navigate to the required user who will be changing their Home HCE. Alternatively use the Search for User option to locate your required user. 1. Click here to use the search for user option User M_Baird1 is a member of the Alva Medical Practice Click on Maintain to change the user s Home HCE 2. The User Maintenance page now has a new section above the Admin Capabilities section that will display the user s Home HCE with a Change Home HCE button which gives you the option to move the users HCE. Home HCE displayed here Change Home HCE button Click on Change Home HCE to reveal the HCE directory screen as seen on the next page Crown Copyright 2012 2-2

3. The Health Care Entity window pictured below is displayed after clicking on Change Home HCE as described on the previous page: The user s Home HCE (Alva Medical Practice) is ticked 4. When you select the required new HCE the old HCE will automatically be deselected. Click in the box required to select the new HCE (in this case Balfron HC). Click on Select Crown Copyright 2012 2-3

5. Once you have clicked on Select as described on the previous page you are returned to the Modify User screen and the Home HCE that you have selected will be displayed. The Home HCE has now changed Any Roles, Sending Groups and Receiving Groups that the user was a member of will remain the same. You must remember to change them to what is appropriate for their new HCE and Role. See the following page. Home HCE is set to Balfron Health Centre Roles, Receiving and Sending Groups are still the same as they were originally for the Alva Medical Practice Crown Copyright 2012 2-4

6. Amend the user s Location, Role and Sending and Receiving Groups as required: Note the new positioning the Save, Reset and Delete buttons in the Modify User screen. Note the new positioning of Receiving and Sending Groups in the Modify User screen. The Roles section now has the same Remove /Restore function as the group sections Change any demographic details accordingly Change the Roles, Receiving Groups and Sending Groups accordingly. 7. After clicking on Save to save all of your changes the following message will be displayed: User modified successfully Crown Copyright 2012 2-5

When you navigate to the user s original home HCE their username is no longer displayed in the list of users. Alva Medical Practice List of users (no M_Baird) When you navigate to the user s new home HCE their user name is displayed in the list of users. Balfron Health Centre List of users including M_Baird The user will not be able to view messages at their original Home HCE. Crown Copyright 2012 2-6

Local News Administrators of SCI Gateway now have the ability to create Local News items on the Home Page of each user when they login. This means that users of the system will only see the local news items that are relevant to them based on their Home HCE. Adding the Local News capability to an administrator 1. In order to create Local News Items on SCI Gateway Home page an Administrator needs to be allocated the necessary Admin capability. Navigate to the user required: 2. Click on Save to save changes User Administrator who is to be given the Local News capability - click on Maintain Select the Local News capability and click on Add Crown Copyright 2012 2-7

3. After clicking on Save as described on the previous page the following message will be displayed: User modified successfully Note:- the Local News capability has now been added to the user The user will now be able to add local news items to HCEs and their descendants that come under their area of control. In the first instance if you require Local News capability allocated to an administrator user in your health board contact NISG Product Support. If an administrator in your health board already has the capability they will be able to allocate it to other administrators. Crown Copyright 2012 2-8

Adding Local News to an HCE and its descendants 1. Navigate to the Local News area by selecting Admin News Local News screen by following the steps below: Access the Local News area via Admin News Local News 2. When you select Local News the following screen is displayed: Start and End dates for news item to be visible to users Click here for HCEs that the news is to be applied to News heading and News text boxes Existing news items that can be updated or deleted Save and Reset buttons Click here to add a new local news item Note:-By default News Headings will be displayed in bold on the SCI Gateway Home Page and News text will be displayed as normal unless there is formatting added through the HTML. Crown Copyright 2012 2-9

3. Start and End dates need to be added to determine the period of time that you want to display the local news item. Local News items will be displayed to users within these dates When a user logs in, the Local News items to be displayed will be determined by the Start and End dates. Only the items that have a start date less than or equal to the current date and an end date greater than the current date will be displayed in the relevant section. 4. The Local News item now needs to be applied to the appropriate HCE(s). Choose which HCE (and its descendants) the Local News will apply to by clicking on the HCEs button Click on Select once the HCE(s) have been chosen Crown Copyright 2012 2-10

5. The detail of the relevant news item can now be added: To add a hyperlink to a web page click here and type or paste from the copied URL Click in each section to add a news heading and news text Click on Save 6. The new local news item will be displayed at the bottom of the screen. Any existing news items will be listed at the bottom of the screen and the most recent news item will go to the top of the list Message saying that the news item has been created successfully The News Text can be formatted with the basic HTML tags, however other HTML tags as well as Style, Class and Attributes are not allowed. See next page for HTML tags If there are a large number of news items there will be a single scrollbar available to aid viewing the news items. As part of the SCI Gateway upgrade, the End Date of all SCI News items that do not have an End Date will be set to their Creation Date plus 90 days. Crown Copyright 2012 2-11

Local News HTML Tags <big> <big> Editing a News Item You can change the dates, the heading, the text, hyperlinks and the HCEs that can view a news item as required: Click on Update to select the news item you want to edit The details for the news item are displayed and can be edited as required Click on Save once all adjustments are made Crown Copyright 2012 2-12

After clicking on Save as shown on the previous page a message will be displayed confirming the news item has been modified successfully as displayed below: Deleting a News Item If you no longer want to display a news item on Local news it can be deleted: Click on Delete for the appropriate news item A message will be displayed asking you to confirm that you would like to delete the news item Click on OK to delete After clicking on OK a message will be displayed confirming you have deleted the news item as pictured below: As part of the SCI Gateway overnight maintenance process, all SCI News and Local News items with an End Date older than 30 days from the date of maintenance will be deleted. Crown Copyright 2012 2-13

Advice Referral Priority In order to use the new Advice referral priority Health board administrators will be required to amend their referral protocols to include the priority in the drop-down list. Advice priority referrals also require a new Schema (2.8) and on upgrade to SCI Gateway version15.0 this Schema will be set as the default. Health board administrators need to ensure that all recipient systems are able to handle any new Schemas prior to implementing them. In order to ensure that the current Schema version continues to be used until recipient systems have been upgraded and tested, administrators with the Extras capability can add the, Default new message schema version, Extra to ensure that the current version continues to be used. This Extra should be added prior to the R15.0 upgrade if you want to maintain your existing Schema. At upgrade to R15.0 the default new message Schema version is set to 2.8 by NHS Scotland for referral messages Click on Add Extra to change your default Schema version Fill in all the relevant details: 1. Extra type 2. Info Text - Schema version No 3. Message Type Then click on Save The default new message Schema is now set to 2.7 and can be updated to 2.8 when all recipient systems are ready to accept referrals using the 2.8 Schema. If you do not have this Extra set and have not upgraded your recipient third party systems they will not be able to receive messages. Crown Copyright 2012 2-14

Stop Attachments after Message Submitted An Extra has been added to SCI Gateway R15.0 which allows health board administrators to prevent attachments being made to messages that have already been sent. If a user attaches a file to a message after it has been sent, it is not clear to the recipient that a new attachment has been made. If users wants to send an attachment to a message that has already been sent they should use the Supplementary Message type. Adding the Extra 1. Navigate to the Extras section for the required HCE: Find the HCE that the setting has to be applied to. In this case General Medicine in Falkirk Community Hospital 2. Info text field now a drop-down list Click on Add Extra 1. Choose Receive Attachments as the Extra type 2. Choose With message as the Info Text 3. Choose a specific Message Type or choose All for all message types New Description field which is read-only and describes Extra Type Click on Save to complete If With message is selected, attachments cannot be sent after the message has been submitted. If With and after message is selected, attachments can be sent with the original message or attached at a later date/time. If Never is selected the attachments cannot be sent with the message at any time. Crown Copyright 2012 2-15

The Extra is set after clicking on Save as described on the previous page and is displayed on the list of Extras as pictured below: Receive Attachments now added as an Extra With Message set as Info Text If With message, is selected as the info text for the recipient HCE and a user from a practice attempts to attach a file to a message that has already been submitted the menu option for Attachments, will not be displayed. Menu option does not display Attachments for submitted messages due to the above Extra being set Crown Copyright 2012 2-16

If a user at a GP practice clicks on the paperclip icon of a message that has already been submitted and is being sent to a location with the Receive attachments, Extra set to With message, they will not have the ability to attach further documents as pictured below: This submitted message has an attachment that was attached prior to being submitted (Test Word Doc). Due to the Receive Attachments Extra for CrossHouse Hospital A&E being set to With messages the Attach Files or Attach Docman buttons are not available If a location s Receive Messages, Extra is set to With and after message, users will be able to send attachments when the message is submitted and also at a later date. A sending user would be able to add an attachment from the Worklist in the options menu and from clicking on the paperclip. The Message Attachments screen as pictured below would be displayed: Attach options are available Crown Copyright 2012 2-17

Batch Save to Docman Health board administrators can now allow practice users to select a number of received messages and file them all into the batch manager of Docman in a single action. This includes egpfr Requests from the Department for Work and Pensions. The Save To Docman button is available on the received message Worklist (inbox) only. It is displayed (regardless of the message type being viewed in the Worklist) only if both of the following criteria are matched: The HCE has the File messages in Docman, Extra assigned for the Receive tab of the Worklist for one or more message types. The logged on user is a member of a role that has the File in Docman permission assigned for one or more message types. Adding the File Messages in Docman Extra 1. Navigate to the relevant HCE in the NHS Directory: Find the relevant HCE in the NHS Directory 2. Click on Add Extra 1. Choose File Messages in Docman as the Extra Type 2. Choose Yes for the Info Text 3. Choose the Message Type New Description field which is read-only and describes the Extra Type Click on Save to complete Crown Copyright 2012 2-18

The Extra is displayed in the list after clicking Save as described on the previous page: File Messages in Docman is now added as an Extra Worklist Toolips and Warning Messages If a user does not have permission to print a message but does have permission to save the message to Docman a Tooltip will be displayed. As all locations do not use Docman these Tooltips will only mention Docman permissions if the HCE has the Docman Extra assigned to one or more message types, regardless of the message type being viewed on the Worklist. Pictured below is an example of a Worklist where the user has the permission to print but not save: This logged on user does not have permission to print egpfr Requests but can save messages to Docman Crown Copyright 2012 2-19

Pictured below is an example of a Worklist where the user does not have permission to print or save: This logged on user does not have permission to print egpfr Requests or save messages to Docman Pictured below is an example of a warning message where a user attempts an action for which they do not have permission. In the example the user does not have permission to print. The message box informs them that they have tried to execute an operation on a message without having the required permission, and they should deselect messages before continuing. Crown Copyright 2012 2-20

Improved Search Options for Protocol and Stylesheet Maintenance The protocol and stylesheet pages have been amended to make it easier to manage the number of protocols and stylesheets viewed in SCI Gateway. Some further improvements to the HCE Groups pages have also been made. Protocols Screen Pictured below is the Protocol screen displayed after clicking on Admin Protocol from the main menu: New Protocol button Reset button that resets all controls back to their default settings Screen is now named Protocols rather than Protocol List Versions Status column previously named Active 1. Message type drop down 2. Version status drop down (can search for Active versions, All inactive versions or All) 3. Part Name or Description free text field Protocol Names are now hyperlinked. Click on the name to open up the Protocol Versions screen Items displayed and page links Click on the Search button after choosing above filters Items per page Crown Copyright 2012 2-21

Opening up an existing protocol To open up an existing protocol the user can use the filters to find the message and then click on its hyperlinked name to open the Protocol Versions screen: 1. Use the filters to search for the protocol and display it in the list below 2. Click on the hyperlinked name to open the Protocol Versions screen Click on the version you want to view/update by clicking on Update If you choose to delete a version you can click on the Delete link Crown Copyright 2012 2-22

3. Click here to manage protocol versions If the user is creating a new protocol, the Protocol Version button will not be visible until the protocol is successfully saved. When the Protocol Version button is clicked, the user will be navigated to the Protocol Versions page of the protocol just edited. The page number should be the same as when the user last viewed the page, or page 1 when a new protocol has been created. Stylesheets New Stylesheet button Search for GUID functions as before Versions Status column previously Active Stylesheet Name is now hyperlinked. Click on the name to open up the Stylesheet Versions screen Reset button that resets all controls back to their default settings Click on the Search button after choosing above filters 1. Message type drop down 2. Version status drop down (can search for Active versions, All inactive versions or All) 3. Part Name or Description free text field Crown Copyright 2012 2-23

Opening up an existing stylesheet To open up an existing stylesheet the user can use the filters to find the stylesheet and then click on its hyperlinked name to open the Stylesheet Versions screen: 1. Use the filters to search for the stylesheet and display it in the list below Click on the hyperlinked name to open the Stylesheet Versions screen 2. Click on the version you want to view/update by clicking on Update If you choose to delete a version you can click on the Delete link Crown Copyright 2012 2-24

3. Click here to view Stylesheet Versions information If the user is creating a new Stylesheet, the Stylesheet Versions button will not be visible until the stylesheet is successfully saved. Clicking on the Stylesheet Versions button, will open the Stylesheet Versions page of the protocol just edited. The page number should be the same as the when the user last viewed the page, or page 1 when a new stylesheet has been created. Crown Copyright 2012 2-25

HCE Groups The HCE Groups pages have been amended to make it easier to find specific groups in SCI Gateway. Previously users would have to scroll through pages at the bottom of the HCE Groups screen to find a particular group. A new search field Name Contains has been added. Insert all or part of the HCE Group name required the in Name Contains field Click on Search All HCEs containing the search criteria will be displayed in a list Crown Copyright 2012 2-26

Hide Consultant drop-down list In order to meet the requirements of RTT targets some hospital and Health Boards preference is for GPs to refer to a specialty rather than a named consultant. SCI Gateway R15.0 allows the consultant drop-down list to be hidden from the new referral window at the health board s discretion. This allows flexibility, for example, the consultant drop-down list can be switched off at one hospital and on at another, or off at a hospital but on for one of its specialties. Adding the Stop further destination selection, Extra Health board administrators can add the, Stop further destination selection, Extra to allow any type of HCE to be hidden for example hospital and specialties not just Consultant/HCPs. 1. Navigate to the relevant HCE in the NHS Directory: Find the relevant HCE Click on Add Extra 1. Choose Stop further destination selection as the Extra Type 2. Choose Yes for the Info Text 3. Choose the Message Type or All Description field is Read Only Click here to save the new Extra New Extra has now been added to the HCE Crown Copyright 2012 2-27

Sending the message Pictured below is the New Referral window which is displayed when a user at a GP Practice is making a new referral to Stirling Community Hospital\General Medicine following the, Stop further destination selection, Extra being added as described on the previous page: 1. No consultant drop-down list option 2. When another HCE is chosen as the destination the consultant drop-down is available: Consultant drop-down available for other HCEs that do not have the Stop further destination Extra Crown Copyright 2012 2-28

Ethnicity Categories The Ethnic Origin field in SCI Gateway messages has been increased to hold a maximum of 70 characters. The names of the Ethnic categories have been amended and expanded to match those in the 2011 Census. The Scottish National General Schema and the Third Party Interface Schema have been changed to allow an increased maximum of 70 characters for the EthnicOrigin element. A note has been added to both Schemas, in a documentation element, listing the ethnic categories used in the Scottish census 2011, with ISD codes. The new General Schema has been implemented in new Referral, Discharge and Clinic Letter Schema versions. Crown Copyright 2012 2-29

Queue Items Visibility The message queuing system in SCI Gateway R15.0 has changed from a single queue for all health boards to a queue per health board. In addition each URL will have a priority assigned to it of Low, Normal or High. The priority will be relative to the other URLs for the health board but will not affect different boards. Administrators will now be able to restart URLs that have been marked as Dead, without being able to add, edit or delete a URL. This new functionality provides greater protection for boards from the effects of issues occurring with health board s URLs. Users will still be able to resubmit dead messages but the Dead Messages user capability is being replaced by the Destination Queues user capability. All users who currently have Dead Messages capability will be granted Destination Queue, capability, therefore no maintenance of assigned user capabilities is required. Destination Queues user capability If a user already has the Dead Messages admin capability it will be renamed Destination Queues after the R15.0 upgrade. R14.0 R15.0 Dead Messages capability Destination Queues capability Crown Copyright 2012 2-30

Destination Queues Pictured below is the Destination Queues screen displayed after clicking on the Destination Queues menu option as shown on the previous page: Priority column Status of URL No. of Queued messages URLs assigned to Health Board No. of Dead messages Total no of Queued and Dead messages Priority Column Users can set the priority of each URL to Low, Normal or High by using the options in the priority column. The default will be set to Normal. Click on the drop-down list to set the priority of each URL Status Column If a URLs status is Alive users have the ability to pause it by clicking on the Pause hyperlink in the status column. If a URLs status is Dead, users have the ability to restart it by clicking on the Restart hyperlink in the status column. Crown Copyright 2012 2-31

Queued/Dead/Total Columns A count of the number of queued messages for each URL is displayed under the Queued column. Likewise a count of the number of dead messages is displayed under the Dead column. A total of queued and dead messages for each URL are displayed in the Total column. Users can click on the number to view details of the messages: Click on the number to view details of the messages In the following example the number 3 in the Dead message column has been clicked on to open up the Destination Queue Items screen: Destination Queue Items screen Click on Destination Queues to go back to the previous screen Click on the Status Filter drop-down to change the messages that you are viewing e.g. change from Dead to Queued or All Number of failed attempts Place a tick in the boxes to select the messages or choose to view All, All Dead or All Queued messages from the selection drop-down list above then choose an action Reason for Dead Message Crown Copyright 2012 2-32

The user is able to select one queued or dead item and view its audit history by clicking on the icon in the 2 nd column. The audit history is ordered on descending event date & time. Click on the message icon required to view audit history of the message Audit history displayed here See page 2-34 for more information on icons. Crown Copyright 2012 2-33

New Icons in Destination Queues SCI Gateway R15.0 has been enhanced to facilitate sending notifications to other systems when a message is cancelled, deleted, redirected or a cancel is reversed. There are new received notifications from other systems to set and clear message flags, delete, cancel and redirect a message. See Recipient Web Service Enhancements on page 2-37 for more information. The typical message icons for example the referral icon are used in the 2 nd column of the Destination Queue Items screen along with other relevant symbols to show the type and status of each message. A Tooltip is displayed explaining what each symbol represents by hovering your mouse over it. The table pictured below shows the icons that may be viewed in the Destinations Queues screen: Icon Delete Discharge Description Cancel Reverse (Discharge) Cancel Discharge Delete Clinic Letter Cancel Reverse (Clinic Letter) Cancel Clinic Letter Delete Advice Request Cancel Reverse (Advice Request) Cancel (Advice Request) Message, including message sent with attachments Attachment subsequently uploaded to an existing message Redirect (notification to original provider) Message redirect, including message redirect with attachments (notification to new provider) Crown Copyright 2012 2-34

Destination URLs The Column headers in the Destination URLs screen have changed: R14 R15 In R14 this column is named Original. In R15 it is named Synchronous In R14 this column is named Restart. In R15 it is named Status and the URL can be Paused, Resumed or Restarted from here Click here to delete a URL When a URL is deleted in the Destination URLs function, all Queued and Dead items will be removed from the queue and all HCE links to the URL will be deleted. Crown Copyright 2012 2-35

Edit URL Details screen In keeping with the changes of the Destination URLs screen the Edit URL screen has changed the name of two radio buttons to co-ordinate with the changes on the column headers as shown in the picture below: These radio buttons were previously named Original and Asynch respectively This control contains the entries (in order) Low, Normal, High. This control contains the entries (in order) Alive, Paused, Dead. Crown Copyright 2012 2-36

Recipient Web Service Enhancements Recipient Web Service v3.0 is a new recipient web service interface which has been created so that third party systems have the option to receive messages and notifications from SCI Gateway. The third party systems will be able to call in order to send messages to SCI Gateway and update the status of messages etc. Specifically the new interface version will be able to: Send messages onto other systems including the HTML and the XML. This will reduce the management overhead of distributing stylesheets to ricipient systems and ensure that there are no differences in the rendered letter. Send messages onto other systems within a wrapper that includes the message ID. This will avoid the possibility of the message XML and message ID being separated and thereby being unable to tell which SCI Gateway message the XML represents. Send notifications onto other systems when a message is cancelled, deleted, redirected or a cancel is reversed. This will keep all systems synchronised. Receive notifications from other systems to set and clear message flags, delete, cancel and redirect a message. This will keep all systems synchronised. A new In bound web service and a new Outbound web service have been created and changes have been made to the Cancel, Delete and Redirect functionality within SCI Gateway. Changes have also been made to the queue processing for Asynchronous Messages and a new version of the Developer Kit has been created. Destination URLs Destination URLs will need to be updated to enable Recipient Web Services v3.0 functionality. To setup the new web service click on New URL Crown Copyright 2012 2-37

Pictured below is the New URL screen which is displayed after clicking on New URL as described on the previous page. This option enables administrators to configure the new recipient web service interface. Add a name and the URL of the recipient web service Choose the sending method (Asynchronous if copies of messages have to be sent to a third party system). Choose Recipient Web Service v3.0 from the Interface drop-down Tick the appropriate capabilities and add the relevant HCEs Set Status of URL to Alive, Paused or Dead. Set Priority to Low, Medium or High Click here to save the new URL Destination Queues If messages are sent asynchronously to a Recipient Web Service v3.0 interface the messages will queue and will be viewable by users with the Destination Queue Items capability. See Queue Items Visibility for more information. For more information on how to implement Recipient Web Service v3.0 see the new version of the Developer Kit or contact NISG Support. Crown Copyright 2012 2-38

Referring to New Branches The referral Schema mandates that each referral must have a referred to Specialty and a referred to Hospital (or location). SCI Gateway pre-populates these details from the referral destinations selections made in the New Referral window. However, if the referral is to a new branch and the branch does not contain a Specialty HCE or a Hospital/Location HCE then these details cannot be pre-populated and in R14.0 the only solution is to have the referring end user key in the details manually. In R15.0 it is now possible to have the Hospital and Specialty specified within the protocol. If they are not present within the new branch then the protocol will enter the detail without the end user requiring to enter them manually. The mechanism to specify them within the protocol is to define the relevant questions as drop down questions, i.e. type=select, with a single option that will automatically be selected. The questions can either be visible or hidden from the end user as required. There are four questions that can be specified this way which are: hospital_id, hospital_name, specialtyref & specialty, where specialtyref specifies the specialty code as defined in the ISD reference file and specialty is the name of the specialty. An example of the relevant protocol questions is given below. <question text="hospital Name" type="select" id="hospital_name" mandatory="true"> <option text="community Nursing, Alva Health Centre" value="community Nursing, Alva Health Centre" isdefault="true"/> </question> <question text="hospital ID" type="select" id="hospital_id" mandatory="true"> <option text="v201b" value="v201b" isdefault="true"/> </question> <question text="specialty" type="select" id="specialty" mandatory="true"> <option text="community nursing (district nursing)" value="community nursing (district nursing)" isdefault="true"/> </question> <question text="specialty Code" type="select" id="specialtyref" mandatory="true"> <option text="t5" value="t5" isdefault="true"/> </question> The questions may be hidden by specifying the hidden= true attribute on the question, or by utilising the <freetext> element and HTML/CSS to hide the container of the question. Multiple options may be specified and the user able to choose, however this is not recommended as the questions are not linked and so it would be possible to specify the wrong code for the specialty selected or the wrong id for the hospital/location selected. Crown Copyright 2012 2-39