Data Transfer Service transition The DTS transition explained presented by Simon Richards and Stuart Baskerville

What is DTS? DTS is a secure application-to-application messaging service In operation for ten years under the BT Spine contract Data Transfer Service

Who uses DTS? The main users of DTS are general practices and pathology departments Other users include: HSCIC Exeter systems National screening services National HSCIC services e.g. CQRS and GPES 111 services Ministry of Defence sites Transfer of Care (discharges) GPs and pathology departments account for 60 per cent of all DTS traffic Most service users have their DTS arrangements managed by their system supplier, a small minority don’t, and we are engaging directly with these organisations and providing support

Key facts about DTS 12 million messages exchanged every month 7500 active accounts Current BT contract for DTS ends on 30 June 2016 Usage stats increasing every month

DTS replacement - MESH Messaging Exchange for Social Care and Health HSCIC managed service Functional replacement of DTS Use of robust, secure and modern Spine infrastructure HSCIC managed service – bringing greater flexibility and we will adapt and improve the service based on emerging user requirements. Includes extending the service to different setting such as social care. Exposing the MESH client-server interface so that a MESH client is not required. Like for like replacement – initially but will develop and improve incrementally Spine – stable platform, gain economies of scale/cost savings, 24/7 365 support

The engagement story so far… Discussions with system suppliers, including key GP, pathology and other DTS users Direct communications and support being provided to service users who manage their own DTS arrangements Most services who use DTS have their arrangements managed via their system supplier. We have identified and are talking to around 100 users who do not have this in place, this includes the very small handful of GPs not on the GPSoC suppliers

Managing the transition Test phase for system suppliers started in November 2015. Original plan was for parallel running of DTS and MESH services till the end of the BT Contract 30 June 2016 Gradual six month transition window Once the test phase is complete, services can gradually transition from December 2015 to the end of June 2016 Testing will

New Transition Approach DTS Adapter developed to remove the need for a parallel running phase for DTS and MESH Switch over at of the central services at the end of January 2016 DTS Client will then be able to connect to the HSCIC MESH Central Server Continue to plan for transition to MESH client from DTS Client by 30 June 2016 MESH client available via HSCIC website MESH client rollout from February Once the test phase is complete, services can gradually transition from December 2015 to the end of June 2016 Testing will

DTS and MESH N3 MESH Server DTS Server Trust MESH Client GP DTS Client MESH will re-use the DTS mailbox settings so DTS addressing will work. Authentication is the same Requires a Java Virtual Machine to be installed. Supported on OSs that have a JVM of 1.5 or more. Linux now supported. Wizard-based installation that prompts user for the DTS installation location to re-use the folders. Manual deployment will be possible also. MESH client launched from the command line in the same way as the DTS client and can therefore be run as a service under windows. MESH Client GP DTS Client TLS TLS DTS Client MESH Client DTS Adapter

Introducing the MESH client Utilises DTS principles and processes Java based client (JVM 1.7) Supported on Windows (XP, Vista, Windows 7, Windows 8, Server 2003 and Server 2008), Linux, Solaris, AIX, HP-UX Wizard-based installation Command-line support Run as a service MESH will re-use the DTS mailbox settings so DTS addressing will work. Authentication is the same Requires a Java Virtual Machine to be installed. Supported on OSs that have a JVM of 1.5 or more. Linux now supported. Wizard-based installation that prompts user for the DTS installation location to re-use the folders. Manual deployment will be possible also. MESH client launched from the command line in the same way as the DTS client and can therefore be run as a service under windows.

RATS now MOLES MESH OnLine Enquiry Service Functional replacement for RATS Smartcards will be required to access the new service User/organisation administration Message tracking – DTS and MESH API Usernames and Passwords will be transferred to MOLES as will the organisational information. Current RATS functionality will be transferred to MOLES and will allow user/mailbox administration and message tracking. Message tracking API will also be supported for querying message statuses.

MESH Server API New feature with MESH HTTP based API Enables suppliers to integrate directly with MESH Replaces MESH/DTS client Available to test Specification available Exposing the API used by the MESH client to send/receive Enables Systems to talk directly to MESH without the need for a client

Next Steps…Testing Environment Available for Testing Testing of: MESH client DTS client with the adapter MOLES Message Tracking API MESH Server API Further details at http://systems.hscic.gov.uk/ddc/DTS/test-client Issues raised via the SA Service Desk – sa.servicedesk@hscic.gov.uk Testing is key: MESH client testing – ensuring the client systems work the same way as DTS DTS client – ensure the DTS Adapter works in the same way as DTS Moles – Familiarise yourself with the new interface Message Tracking API – integration with existing systems MESH Server API – suppliers wanting to test the new API to send/receive messages without the need for the client

Summary Function replacement no redevelopment required Message tracking in MOLES (smartcard required) Testing available now mesh@hscic.gov.uk http://systems.hscic.gov.uk/spine/DTS Usernames and Passwords will be transferred to MOLES as will the organisational information. Current RATS functionality will be transferred to MOLES and will allow user/mailbox administration and message tracking. Message tracking API will also be supported for querying message statuses.