MESH General Practice Clinical System Changes and Impacts on Addressing

Transcription

1 Document filename: MESH General Practice Guidance Directorate / Programme Operations and Assurance Services Project Spine Services/ MESH Document Reference <insert> Project Manager Andrew Meyer Status Owner Ash Raines Version 1.0 Author Simon Richards Version issue date 14/07/2016 MESH General Practice Clinical System Changes and Impacts on Addressing

2 Document Management Revision History Version Date Summary of Changes /07/2016 Initial version. Reviewers This document must be reviewed by the following people: Reviewer name Title / Responsibility Date Version Stuart Baskerville Spine2 Release Manager Marta Raper Sarga Moore Spine2 Project Manager MESH Service Manager Approved by This document must be approved by the following people: Name Signature Title Date Version Ash Raines Glossary of Terms Term / Abbreviation API DTS EPR HSCIC keystore MESH MOLES What it stands for Application Programming Interface Data Transfer Service End Point Registration Health and Social Care Information Centre Repository for security certificates Messaging Exchange for Social Care and Heath MESH Online Enquiry Service Page 2 of 8

3 RA RATS RBAC Registration Authority Registration and Tracking Service Role-Based Access Control Document Control: The controlled copy of this document is maintained in the HSCIC corporate network. Any copies of this document held outside of that area, in whatever format (e.g. paper, attachment), are considered to have passed out of control and should be checked for currency and validity. Page 3 of 8

4 Contents 1 GP Practice Clinical System Changes and Impacts on MESH Addressing 5 2 Appendix For Pathology/Radiology Messages For Out of Hours Messages 7 Page 4 of 8

5 1 GP Practice Clinical System Changes and Impacts on MESH Addressing When a clinical system change is made in General Practice the planning process should include the potential impacts on messaging flows from the organisations (Trading Partners) with which that practice communicates. Failure to do so could result in messages not being received by the practice and therefore represents a clinical risk. Where a change involves system suppliers other than TPP there is no change to the addressing details that Trading Partners should use for the practice. For example a change to the practice system from a solution provided by In Practice Systems (InPS) to a solution provided by EMIS, or vice versa, requires no change to the MESH mailbox address. The change is therefore transparent to the Trading Partners and they are not required to make any addressing change within their systems. From a MESH perspective the ownership of the MESH Mailbox for the practice is simply transferred to the new supplier. This is actioned by the HSCIC MESH Service Team at the request of the incoming supplier via a support call. Where the change to the GP Practice system does involve a change to/from TPP SystmOne then there is an impact on the MESH addressing. The reason why a change to the addressing details is required is because of the specific configuration of TPP SystmOne and its use of MESH Mailboxes. TPP SystmOne utilises shared mailboxes to support all of its customers. There is not a one-to-one relationship between a GP Practice and the MESH Mailbox that supports messaging for the practice (this model is the one in place for all other suppliers with the exception of TPP). In the TPP model a single MESH Mailbox supports many GP Practices. The appendix provides guidance on which specific MESH Mailbox should be used for which GP Practice. As TPP SystmOne utilises shared MESH Mailboxes then the Trading Partners need to be informed of the change to the MESH Address that should be used for the specific practice. The Trading Partner should also be informed as to when this change becomes effective i.e. the go-live for the new system. Where the change involves the installation of a TPP SystmOne solution then it is very important that the old system is decommissioned. The plan should therefore include a request to the supplier of the old system to at the very least decommission the MESH Client on their solution. If the old solution is not decommissioned then the Trading Partner may continue to send messages to the practice at the old address and there is a significant clinical risk that the practice never actually read these messages. Once the old solution MESH Client is decommissioned then any Trading Partner attempting to send messages to the MESH Mailbox will receive Non-Collected Reports and so will know that there is an issue with the MESH Mailbox which they should investigate. Non-Collected Reports are only generated by the MESH Central Service for messages that have not been collected from MESH within 5 days. Trading Partners may therefore not be aware for this period that the practice has not collected the messages that they have sent. If the HSCIC MESH Team have been informed that the old mailbox should no-longer be used for the GP Practice then they can de-activate the mailbox on the MESH Online Enquiry Service (MOLES) where mailbox registrations are managed. If a Trading Partner attempts to send to a MESH Mailbox that has been de-activated then they will receive an immediate Send Failed error. The management of Trading Partner addressing is equally important where the change Page 5 of 8

6 might be away from a TPP SystmOne solution i.e. TPP to EMIS or In Practice Solution. In these cases it is not possible to decommission the MESH Client or deactivate the MESH Mailbox as it will be shared by other TPP SystmOne Practices. The management of the Trading Partners requires very thorough management as Non-Collected Reports or send Failed errors will not be generated. For further advice/assistance please raise a call with the MESH Team via the National Service Desk (NSD) via the NSD weblog tool or via telephone on Page 6 of 8

7 2 Appendix TPP have been provided with a number of MESH Mailboxes to support the transfer of messages with SystmOne. The distribution of message transfers with SystmOne across a number of MESH Mailboxes will provide benefits to all parties. Collection and transfer times should improve particularly later in the day, which should mean that any acknowledgement messages should be returned to message originators in a more timely manner. It will also be significantly easier to investigate support issues should they arise and there will no longer be a single point of failure. MESH Mailboxes are allocated based on the message type and the first letter of the ODS Code (organisation code) of the GP Practice. 2.1 For Pathology/Radiology Messages For Pathology/Radiology Messages the MESH Mailboxes are allocated as follows; ODS Code starting with MESH Mailbox Address A B C D E F G H J K L M N P W Y ygm27pm ygm27pm1 ygm27pm2 ygm27pm3 ygm27pm4 ygm27pm5 ygm27pm6 ygm27pm7 ygm27pm8 ygm27pm9 ygm27pm10 ygm27pm11 ygm27pm12 ygm27pm13 ygm27pm14 ygm27pm15 For example, if your pathology/radiology lab sends to a GP Practice (SystmOne unit) with an ODS code starting with C then the recipient MESH address should be changed to ygm27pm For Out of Hours Messages For Out of Hours Messages the MESH Mailboxes are allocated as follows ODS Code starting with MESH Mailbox Address A to E F to J ygm27hc5 ygm27hc6 Page 7 of 8

8 K to O P to T U to Z ygm27hc7 ygm27hc8 ygm27hc9 For example, if your OOH Service sends a message to a GP Practice (SystmOne unit) with an ODS code starting with C then the recipient MESH address should be changed to ygm27hc5 as it would fall within the range A through E. Page 8 of 8