MESH client File Interface Specification

Transcription

1 Document filename: MESH Client File Interface Specification Directorate / Programme Operations and Project Assurance Services Spine Services/ MESH Document Reference <insert> Project Manager Andrew Meyer Status Issued Owner Ash Raines Version 1.2 Author Paddy Yung Stuart Baskerville Version issue date 08/08/2017 MESH client File Interface Specification

2 Document Management Revision History Version Date Summary of Changes /05/2016 Initial version /05/2016 Updated following review /05/2016 Issued Reviewers This document must be reviewed by the following people: Reviewer name Title / Responsibility Date Version Simon Richards DTS Service Owner Marta Raper Kathryn Common Spine2 Project Manager Senior Communications Officer Approved by This document must be approved by the following people: Name Signature Title Date Version Ash Raines Glossary of Terms Term / Abbreviation API DNS DR DSN DTS EPR HSCIC MESH MOLES MTA MTSID NDR RA What it stands for Application Programming Interface Domain Name Service Delivery Report Delivery Service Notification Data Transfer Service End Point Registration Health and Social Care Information Centre Messaging Exchange for Social Care and Heath MESH Online Enquiry Service Message Transfer Agent Message Transfer Service Identity Non Delivery report Registration Authority Page 2 of 23

3 SMTP Simple Message Transfer Protocol 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 23

4 Contents 1 Introduction Purpose of Document Background 5 2 Background MESH Client Overview MESH Client File Interface Directory/File Structure Multi Mailbox Considerations File Interface 7 3 Data Transfer OUT Transactions 12 4 MESH Control File Examples Sent Control File Received Control File 18 5 MESH Status Values 19 6 XML Schema for Control file 21 7 Contact HSCIC 23 Page 4 of 23

5 1 Introduction 1.1 Purpose of Document The purpose of this document it to detail the Messaging Exchange for Social Care and Health (MESH) interface specification to enable users of DTS and MESH to send and receive messages using MESH. The intended audience for this document is MESH users who need to understand how messages are sent/received by MESH. 1.2 Background The BT contract for provision of the DTS expires on 30 June The Health and Social Care Information Centre (HSCIC) has developed a replacement for DTS which will be an inhouse managed service. This transition enabled HSCIC to introduce a number of service improvements and deliver cost savings. In January 2016 we transitioned the DTS Central Service from BT to the HSCIC MESH Service. This means that the service is now operated and managed by the HSCIC. The transition will also enable the new service to adapt to emerging user requirements in a more flexible and efficient manner. Page 5 of 23

6 2 Background 2.1 MESH Client Overview MESH is a secure service developed for application to application messaging, which carries data flows on a platform which supports NHS compliance with e-gif. The MESH client will run as a separate application on the server platform supporting the host application. It will perform the following functions; Send application data to the central MESH server for delivery to the specified recipient. Receive application data from the central MESH server for delivery to the local application. Provide delivery and error status indications to the local host application. The MESH client will interface to the host application via the file interface defined in this document. 2.2 MESH Client File Interface The MESH client will transfer data to and from the host application via a simple file based interface. The following sections define the file-based interface; Directory/File structure Control Information Status Information 2.3 Directory/File Structure The MESH client will use the following file system directory/folder structure to transfer data to and from the host application; <MESH-DATA-HOME> \FAILED \IN \OUT \SENT \TEMP \TEMP\RCV The <MESH-DATA-HOME> is the path to the MESH client interface top level directory/folder. The MESH client root path will be specified as a configuration item in the MESH client parameter file (meshclient.cfg). The MESH client will read this file when it starts up to configure site/implementation specific parameters. Page 6 of 23

7 The FAILED directory will be used by the MESH client to hold malformed or syntactically incorrect control files along with their respective data files. The IN directory will be used by the MESH client to deposit data and status information to be received by the host application. The OUT directory will be used by the HOST application to copy data to be sent by the MESH client. The SENT directory will be used by the MESH client to copy sent data for use by the host application. The TEMP directory will be used by the MESH client for any intermediate files during its processing of outgoing data transfers. The TEMP/RCV directory will be used by the MESH client for any intermediate files during its processing of incoming data transfers. 2.4 Multi Mailbox Considerations If the MESH client is to be used for multiple mailboxes then the structure defined in section2.3, Directory/File Structure is required for each mailbox. Each mailbox requires a unique file interface structure. When using the MESH client in multi mailbox mode the following additional file structures need to be set up; Log path a directory where the MESH client can put its log files Work path a directory where the MESH client can perform generic file activities. Signal path a directory where the MESH client will look for its signal file. Proxy path an optional directory where the MESH client will look for the proxy.ini proxy configuration file. 2.5 File Interface Data Transfer File Handling Where data is to be transferred, e.g. sending or receiving data, the file interface will contain two files; Data file <message_id>.dat Control file - <message_id>.ctl Where only status information is to be transferred e.g. delivery status information or error indication the transaction will be a single control file. Please note that this will only be sent from the MESH client to the host application. Report file - <mailbox_id>_report_type<message_id>.ctl with report type being a C, P or a T to signify Collect, Poll or Transfer respectively. Page 7 of 23

8 The data file will contain the data (payload) to be transferred. This may be in any form and will be treated by the MESH client and Server as an arbitrary data file. The maximum size the file can be is 50MB. The only operation that the MESH client may perform on the data file is to compress it if the option within the associated control file is selected. The control file will contain the information required to identify, transmit and audit the data File. The report file will contain information to identify the transaction being reported on and the status report information. The message id will uniquely identify the data transfer files Data Transfer File Handling The MESH client will run independently from the System Supplier application in the processing of the data files. There is a potential for the MESH client or Supplier application to access the data transfer files before they are completed. The following functionality has been included to mitigate this risk; 1. The data and control files should be created in a temporary directory area and then moved to the destination directory. 2. The data file should be placed in the destination directory before the control file. 3. The receiving application should look for the control file before starting to handle the data transfer Control File The control file will be in the format as defined in the Page 8 of 23

9 MESH Control File Example. The control file and report file will be the same format but will contain different information depending on the transaction. The control and report file data structure is defined in the following table. Mandatory elements must be supplied Optional elements may be ignored or specified with no data. DATA ITEM VALUES/ SIZE MANDATORY/ OPTIONAL/ CONDITIONAL DESCRIPTION Version 1.0 M Version of control file AddressType MessageType SMTP DTS ALL Data Report M M Identifies the type of address. SMTP - SMTP address DTS DTS name addressing ALL Used by MESH Server when sending to MESH client. All address fields will be completed. Identifies the type of transfer Data will have a data file and a control file. Report will have a control file. WorkflowId 32 characters M Identifier for the workflow that the data transfer is part of. This may be used for reporting and to define processing at the MESH Server. For example Pathology MEDRPT v1.003 messages should have a WorkflowId of PATH_MEDRPT_V3. (WorkflowId s should be populated in message transfers in upper case only) From_ESMTP SMTP address C Identifies the originator of the data transfer. SMTP address of the originator. Conditional must be supplied if AddressType = SMTP or ALL To_ESMTP SMTP address C Identifies the recipient of the data transfer. SMTP address of the recipient. From_DTS To_DTS MESH mailbox Name MESH mailbox Name C C Conditional must be supplied if AddressType = SMTP or ALL Identifies the originator of the data transfer. MESH mailbox Name of the originator. Conditional must be supplied if AddressType = DTS or ALL Identifies the recipient of the data transfer. MESH mailbox Name of the recipient. Conditional must be supplied if AddressType = DTS or ALL Subject SMTP Subject O Subject of the data transfer as for SMTP Page 9 of 23

10 subject. LocalId 255 characters O Local identifier of the data transfer. This is specific to the host application sending via the MESH client. This will allow for correlation with DTSId. DTSId 100 characters O Each data transfer will be associated with a DTSId (also known as a message id) as it passes through the MESH Server. This will allow for correlation with LocalId and PartnerId. PartnerId 255 characters O CCN005 - Now obsolete. If a local identifier was included in the original message this is now presented to the receiving Client in the LocalId field. Compress Y N O Flag to indicate that the data file can be compressed by the MESH client. Default = Y Encrypted Y N O Flag to indicate that the data file has been encrypted by the host application. Default = N ProcessId 32 characters O For future use. Identifier to specify the type of processing that might be required before forwarding to the recipient. DataChecksum O Field to be used for a checksum for the data file. IsCompressed Y O Field to indicate that the data file is compressed. N AllowChunking Y N O Flag to support the transfer of files in excess of 100Mb (compressed). If set to Y the client will support the transfer of files up to a maximum of 20Gb. Failure to set this flag when attempting to transfer files with a size in excess of 100Mb will result in a failed transfer. To support the transfer, the client will process large files in 20Mb chunks. StatusRecord O Status information on the status of the data transfer. This will contain the following information; Date Time Event Status success or error Status code Description File Interface Maintenance There is a requirement for the files in the file interface directories to be managed. A brief description regarding the management of data through the folders is shown below. 1. IN The MESH client will copy received data transfer files and report files to the IN directory. Page 10 of 23

11 It is the responsibility of the host application to manage the IN directory. i.e. to use, delete or archive the data files. 2. OUT MESH client will move data transfer files from the OUT directory once it has successfully transferred it to the MESH Server. If configured to do so the MESH client will copy sent data transfer files to the SENT directory. 3. SENT - It is the responsibility of the host application to manage the SENT directory. i.e. to use, delete or archive the data files. 4. TEMP The TEMP directory is private to the MESH client, the MESH client will manage the contents of the directory 5. FAILED The MESH client will move malformed messages into the FAILED directory so that they may be examined. It is recommended that this directory is checked periodically for messages that could not be sent to the MESH server. 6. TEMP/RCV The TEMP/RCV directory is private to the MESH client, the MESH client will manage the contents of the directory Page 11 of 23

12 3 Data Transfer The Control File will contain different information depending on the circumstances. The following sections describe the different contents for the following 1. Out transaction The host application sends data via the MESH client 2. In data transactions The host application receives data via the MESH client 3. In status transaction The MESH client reporting on status / events. 3.1 OUT Transactions OUT transactions are those sent from the host application via the MESH client to the MESH server. The requirement of the control file is to identify the recipient of the data and to identify the transfer for audit purposes. The following table shows the data items for this Transaction. DATA ITEM VALUES/ SIZE MANDATORY/ OPTIONAL DESCRIPTION Version 1.0 M Version of control file AddressType SMTP M Type of address. DTS ALL MessageType Data M Identifies the type of transfer, the OUT transaction will have a data file and a control file. WorkflowId 32 characters M Mandatory flag indicating the workflow, e.g. Pathology MEDRPT v1.003 messages should have a WorkflowId of PATH_MEDRPT_V3. (WorkflowId s should be populated in message transfers in upper case only). From_ESMTP SMTP address C Identifies the originator of the data transfer. SMTP address of the originator. Conditional must be supplied if AddressType = SMTP or ALL To_ESMTP SMTP address C Identifies the recipient of the data transfer. SMTP address of the recipient. Conditional must be supplied if AddressType = SMTP or ALL From_DTS MESH Name C Identifies the originator of the data transfer. MESH mailbox Name of the originator. Conditional must be supplied if Address Type = DTS or ALL To_DTS DTS Name C Identifies the recipient of the Data Transfer. MESH mailbox name of the recipient. Page 12 of 23

13 Conditional must be supplied if AddressType = DTS or ALL Subject SMTP Subject O Subject of the data transfer as for SMTP subject. LocalId 255 characters O Local identifier of the data transfer. This is specific to the host application sending via the MESH client. DTSId O Not applicable in the OUT transaction. Compress Encrypted Y N Y N O O Optional flag to indicate that the data file can be compressed. Default = Y Optional flag to indicate that the data file is encrypted. Default = N ProcessId 32 characters O Optional flag indicating processing to be performed at the MESH Server. For future use. AllowChunking Y N O Optional flag indicating processing to be adopted for large files i.e. above 100Mb (compressed) DataChecksum O Not applicable in the OUT transaction. IsCompressed O Not applicable in the OUT transaction. StatusRecord O Not applicable in the OUT transaction IN Data Transactions In data transactions are those from the MESH Server via the MESH client to the host application. The requirements for the control file are to identify the recipient of the data and to identify the transfer for audit purposes. The following table shows the data items for this transaction. DATA ITEM VALUES/ SIZE MANDATORY/ OPTIONAL DESCRIPTION Version 1.0 M Version of control file AddressType SMTP DTS ALL M Type of address. MessageType Data M Identifies the type of transfer, the IN Data Transaction will have a data file and a control file. WorkflowId 32 characters M Mandatory flag indicating the workflow, e.g. Pathology MEDRPT v1.003 messages should have a WorkflowId of PATH_MEDRPT_V3. (WorkflowId s should be populated in message transfers in upper case only). Page 13 of 23

14 From_ESMTP SMTP address C Identifies the originator of the data transfer. SMTP address of the originator. Conditional must be supplied if AddressType = SMTP or ALL To_ESMTP SMTP address C Identifies the recipient of the data transfer. SMTP address of the recipient. Conditional must be supplied if AddressType = SMTP or ALL From_DTS DTS Name C Identifies the originator of the data transfer. MESH mailbox Name of the originator. Conditional must be supplied if AddressType = DTS or ALL To_DTS MESH Name C Identifies the recipient of the data transfer. MESH mailbox name of the recipient. Conditional must be supplied if AddressType = DTS or ALL Subject SMTP Subject O Subject of the data transfer as for SMTP subject. LocalId O Any local identifier applied to the data transfer by the sending application. This is specific to the host application sending the data. DTSId 100 characters O MESH identifier for the data transfer. This can be used to identify the transfer for tracking purposes. Compress O Not applicable in the IN data transaction. Encrypted O Not applicable in the IN data transaction. ProcessId O Not applicable in the IN data transaction. AllowChunking O Not applicable in the IN data transaction. DataChecksum O Not applicable in the IN data transaction. IsCompressed O Not applicable in the IN data transaction. StatusRecord O Status information on the status of the Data Transfer. Date Time Event - Delivery Status Success Page 14 of 23

15 3.1.2 IN Status Transactions Status transactions will be sent from the MESH client to the host application. The requirements for the control file are to identify the data transfer involved and the status. Status transactions will be sent to the host application from the MESH client in the following circumstances. Configuration of the MESH client to report on the event will be configurable via the MESH client configuration file. 1. Collect error: The MESH client has detected an error with the OUT transaction files. 2. Collect Report : Optional Status report indicating that the MESH client has taken responsibility for the data transfer files in the OUT transaction. 3. Delay Report : Optional - MESH client has failed to transfer to MESH Server but will retry. 4. Transfer fail: MESH client has failed to transfer to MESH Server and has aborted the transfer 5. Transfer Report: Optional MESH client has successfully transferred to the MESH Server 6. Server fail: MESH Server failed to transmit the data. 7. Poll fail: Optional MESH client has attempted to poll the MESH Server but has failed. 8. Poll Report: Optional - MESH client has polled the MESH Server successfully. 9. Non-delivery: Negative Delivery Service Notification (DSN) received from the SMTP service. 10. Server authentication error: MESH Server authentication failed. 11. Client authentication error: MESH client authentication failed. The status transactions will specify the same data transfer information as the original data transfer control file (where possible). This will allow the host application to identify which data transfer the status report is about. All status information regarding success or failure will be specified in the tracking records data elements in the report file. The following table shows the data items for this transaction. Page 15 of 23

16 DATA ITEM VALUES/ SIZE MANDATORY/ OPTIONAL DESCRIPTION Version 1.0 M Version of control file AddressType SMTP DTS ALL M Type of address. MessageType Report M Identifies the type of transfer file, either Data or Report WorkflowId 32 characters M From the original OUT transaction control file if specified. This will not be specified for the poll fail and poll report status reports. From_ESMTP SMTP address C SMTP address of the originator. From the original OUT transaction control file if specified. This will not be specified for the poll fail and poll report status reports To_ESMTP SMTP address C SMTP address of the recipient. From the original OUT transaction control file if specified. This will not be specified for the poll fail and poll report status reports From_DTS MESH Name C MESH mailbox name of the originator. From the original OUT transaction control file if specified. This will not be specified for the poll fail and poll report status reports To_DTS MESH Name C MESH mailbox name of the recipient. From the original OUT transaction control file if specified. This will not be specified for the poll fail and poll report status reports Subject SMTP Subject O Subject of the data transfer as for SMTP subject. From the original OUT transaction control file, if specified. This will not be specified for the poll fail and poll report status reports LocalId 255 characters O From the original OUT transaction control file. This will not be specified for the poll fail and poll report status reports DTSId 100 characters O MESH message identifier for the data transfer. This will only be specified if the status report comes from the MESH Server. Compress O Not applicable in the IN Status Transaction. Encrypted O Not applicable in the IN status transaction. ProcessId O Not applicable in the IN status transaction. AllowChunking O Not applicable in the IN status transaction. DataChecksum O Not applicable in the IN status transaction. Page 16 of 23

17 IsCompressed O Not applicable in the IN status transaction. StatusRecord O Status information on the status of the data transfer. See MESH Status Values for the list of events, codes and descriptions. Date Time Event Status Status code Description Page 17 of 23

18 4 MESH Control File Examples 4.1 Sent Control File <DTSControl> <Version>1.0</Version> <AddressType>DTS</AddressType> <MessageType>Data</MessageType> <From_DTS>testdts1</From_DTS> <To_DTS>testdts2</To_DTS> <Subject>EDI Data</Subject> <LocalId>Testbox01</LocalId> <DTSId>DTS </DTSId> <PartnerId></PartnerId> <Compress>Y</Compress> <Encrypted>N</Encrypted> <WorkflowId>PATH_MEDRPT_V3</WorkflowId> <ProcessId></ProcessId> <DataChecksum></DataChecksum> <IsCompressed>Y</IsCompressed> <AllowChunking>Y</AllowChunking> </DTSControl> 4.2 Received Control File <DTSControl> <Version>1.0</Version> <AddressType>DTS</AddressType> <MessageType>Data</MessageType> <From_DTS>testdts1</From_DTS> <To_DTS>testdts2</To_DTS> <Subject>EDI Data</Subject> <LocalId>Testbox01</LocalId> <DTSId>DTS </DTSId> <PartnerId></PartnerId> <Compress>Y</Compress> <Encrypted>N</Encrypted> <WorkflowId>PATH_MEDRPT_V3</WorkflowId> <ProcessId></ProcessId> <DataChecksum></DataChecksum> <IsCompressed >Y</IsCompressed > <StatusRecord> <DateTime> </DateTime> <Event>Transfer to DTS Server</Event> <Status>Success</Status> <StatusCode>0</StatusCode> <Description></Description> </StatusRecord> </DTSControl> Page 18 of 23

19 5 MESH Status Values The following Status events have been identified; Collect error: The MESH client has detected an error with the OUT transaction files. Collect Report: Optional Status report indicating that the MESH client has taken responsibility for the data transfer files in the OUT transaction. DelayReport: Optional - MESH client has failed to transfer to MESH Server but will retry. Transfer Fail: MESH client has failed to transfer to MESH Server and has aborted the transfer TransferReport: Optional MESH client has successfully transferred to the MESH Server Server fail: MESH Server failed to transmit the data. Poll fail: Optional MESH client has attempted to poll the MESH Server but has failed. PollReport: Optional - MESH client has polled the MESH Server successfully. Non Delivery: Negative delivery service notification received from the SMTP service. Server authentication error: MESH Server authentication failed. Client authentication error: MESH client authentication failed. Although not an exhaustive list, the table below summarises the possible causes. Further information to help diagnose errors can be obtained from the ssl.log and MESHclient.log files. Status Type Event Status Status Code Description Collect Report COLLECT SUCCESS 00 Data collect success confirmation. Collect Error COLLECT ERROR 01 Control file is missing or inaccessible. Collect Error COLLECT ERROR 02 Data file is missing or inaccessible. Server Authentication TRANSFER ERROR 03 Server authentication failure caused by an invalid certificate, unreachable certificate path or problem Page 19 of 23

20 Error loading the certificate itself. Transfer Report TRANSFER SUCCESS 00 Data transfer success confirmation. Client Authentication Error TRANSFER ERROR 04 Client authentication failure caused by invalid MESH username or authentication string. Delay Report TRANSFER SUCCESS 05 A Delay Report has been produced indicating that the Client has failed to transfer the data file to the MESH Server. The Client will retry again. Transfer Fail TRANSFER ERROR 06 Transfer failure. There has been a problem transferring the data file to the MESH Server. The maximum retry attempts have been reached. Server Fail SEND ERROR 07 Invalid From address in the control file. Server Fail SEND ERROR 08 Invalid To address in the control file. Server Fail SEND ERROR 09 Invalid Version of the control file. Server Fail SEND ERROR 10 Invalid Address Type in the control file. Server Fail SEND ERROR 11 Invalid Message Type for the transfer. Server Fail SEND ERROR 12 Unregistered To address. Non Delivery SEND ERROR 13 SMTP delivery failure. Non Delivery SEND ERROR 14 MESH delivery failure. Poll Report RECEIVE SUCCESS 00 Poll Report Success confirmation. Poll Fail RECEIVE ERROR 15 Receive poll error. Check the MESH client log file for information that may help to identify the cause. Server Authentication Error Client Authentication Error RECEIVE ERROR 16 Server authentication failure due to invalid server certificate. RECEIVE ERROR 17 Client authentication failure caused by invalid MESH username or authentication string. Page 20 of 23

21 6 XML Schema for Control file The following XML Schema for the Control file has been validated against XML Schema version 1.1 (also known as XSD 1.2 this version does not include file chunking). <?xml version="1.0"?> <xs:schema xmlns:xs=" <xs:element name="dtscontrol"> <xs:complextype> <xs:sequence> <xs:element name="version" type="xs:string" fixed="1.0"/> <xs:element name="addresstype" type="addresstype" /> <xs:element name="messagetype" type="messagetype" /> <xs:element name="workflowid"> <xs:simpletype> <xs:restriction base="xs:string"> <xs:maxlength value="32"/> </xs:restriction> </xs:simpletype> </xs:element> <xs:element name="from_esmtp" type="xs:string" minoccurs="0" nillable="true"/> <xs:element name="to_esmtp" type="xs:string" minoccurs="0" nillable="true"/> <xs:element name="from_dts" type="xs:string" minoccurs="0" nillable="true"/> <xs:element name="to_dts" type="xs:string" minoccurs="0" nillable="true"/> <xs:element name="subject" type="xs:string" minoccurs="0" /> <xs:element name="localid" minoccurs="0"> <xs:simpletype> <xs:restriction base="xs:string"> <xs:maxlength value="255"/> </xs:restriction> </xs:simpletype> </xs:element> <xs:element name="dtsid" minoccurs="0"> <xs:simpletype> <xs:restriction base="xs:string"> <xs:maxlength value="100"/> </xs:restriction> </xs:simpletype> </xs:element> <xs:element name="partnerid" minoccurs="0"> <xs:simpletype> <xs:restriction base="xs:string"> <xs:maxlength value="255"/> </xs:restriction> </xs:simpletype> </xs:element> <xs:element name="compress" type="xs:string" minoccurs="0" default="y" /> <xs:element name="encrypted" type="xs:string" minoccurs="0" default="n"/> <xs:element name="processid" minoccurs="0"> <xs:simpletype> <xs:restriction base="xs:string"> <xs:maxlength value="32"/> </xs:restriction> Page 21 of 23

22 </xs:simpletype> </xs:element> <xs:element name="datachecksum" type="xs:string" minoccurs="0" /> <xs:element name="iscompressed" type="xs:string" minoccurs="0" /> <xs:element name="statusrecord" minoccurs="0" maxoccurs="unbounded"> <xs:complextype> <xs:sequence> <xs:element name="datetime" type="xs:string" minoccurs="0" /> <xs:element name="event" type="xs:string" minoccurs="0" /> <xs:element name="status" type="xs:string" minoccurs="0" /> <xs:element name="statuscode" type="xs:string" minoccurs="0" /> <xs:element name="description" type="xs:string" minoccurs="0" /> </xs:sequence> </xs:complextype> </xs:element> </xs:sequence> <xs:assert test="if (AddressType eq 'SMTP') then count(from_esmtp) = 1 else if (AddressType eq 'ALL') then count(from_esmtp) = 1 else true()"/> <xs:assert test="if (AddressType eq 'SMTP') then count(to_esmtp) = 1 else if (AddressType eq 'ALL') then count(to_esmtp) = 1 else true()"/> <xs:assert test="if (AddressType eq 'DTS') then count(from_dts) = 1 else if (AddressType eq 'ALL') then count(from_dts) = 1 else true()"/> <xs:assert test="if (AddressType eq 'DTS') then count(to_dts) = 1 else if (AddressType eq 'ALL') then count(to_dts) = 1 else true()"/> </xs:complextype> </xs:element> <xs:simpletype name="addresstype"> <xs:restriction base="xs:string"> <xs:enumeration value="smtp"/> <xs:enumeration value="dts"/> <xs:enumeration value="all"/> </xs:restriction> </xs:simpletype> <xs:simpletype name="messagetype"> <xs:restriction base="xs:string"> <xs:enumeration value="data"/> <xs:enumeration value="report"/> </xs:restriction> </xs:simpletype> </xs:schema> Page 22 of 23

23 7 Contact NHS Digital For further information and a set of FAQs, a dedicated MESH page has been created on the NHS Digital website at If users have specific question related to MESH please contact the National Service Desk. Page 23 of 23