MESH submission guidance
The Message Exchange for Social Care and Health (MESH) is the main secure large file transfer service used across health and social care organisations and has been chosen by the Cumberlege Programme to enable the submission of Surgical Device and Implant data by Health Care Organisations (HCO) and Independent Health Care Sector Organisations (IHCSO) to NHS Digital.
The Data Liaison team supports the organisations in England as they prepare their data submissions. Establishing MESH for submitting data is included in the preparations.
Types of MESH currently used for the Surgical Devices and Implants Data Collection
MESH client
Is currently the favoured type for Surgical Device and Implant Data submissions, as it allows for submission file size to grow (Up to 20GB). Set up requires application of software on local networks and sending the data is a bit more involved that MESH UI, but quick when you know the steps to follow). Automation of submission is easier through MESH Client.
MESH user interface
Has a quicker set up, lower file size (under 100MB over N3/HSCN and under 50MB over Internet Gateway) and an easier sending process). This option does not lend itself to automation because it involves going to a website and clicking on items.
If you are a health care organisation, there is a good chance you will have already established MESH client as it was required for the National Opt Out programme. If that is the case and they are happy using that client, then all that needs to be done is setting up a Surgical Devices and Implant mailbox, which Data Liaison can help with.
If HCOs and IHCSO’s decided to "start small and then go big", they can start with MESH UI and then change to MESH client.
Detailed breakdown of each MESH option along with set up and user guides are available on the MESH hub.
MESH set up
HCOs and IHCSO’s must first select the type of MESH they would like to use to submit the required data. The Data Liaison Manager then works closely with them to complete this task, using the Client Installation Guides found on the MESH hub.
Added information for data submissions via MESH Client
To help HCOs and IHCSO’s send a Surgical Device and Implant Data submission (also known as a Bulk Upload Submission) via MESH we recommend you work through the following checklist.
- Request a Surgical Devices and Implants Dedicated MESH mailbox for this work. DLT has special permissions to do this for the organisation they are engaged with.
- Check format of data is correct. It MUST be CSV comma (,) delimited with quote character “
- Create .ctl and .dat file. DLT upskill organisations in doing this and for more info on this read on.
- Place the .ctl and.dat files into the mailbox's OUT folder for collection by the MESH Client and confirm if it has been sent correctly. The MESH Client user guide has detailed steps which helps with this.
Checklist item
Request a Surgical Devices and Implants Dedicated MESH mailbox for this work
The regional data liaison manager can request the MESH Mailbox for you from directly from the National Service desk.
You will need to provide organisation name, ODS Code, org code.
Check format of data is correct
Header names: Column C on the Surgical Devices and Implants tab of the Technical Output Specification, called Physical Data Item Name MUST be used to produce the Headers in the file. The file format must be CSV comma (,) delimited with quote character “
Content: Where no value is present in a data item in a record, the entry must contain double quotes ,"",
File format: The submission file should be saved as a CSV comma (,) delimited with quote character “ before changing the file type to .dat. and placing it along with the control file in Messaging Exchange Service for Social Care and Health (MESH) dedicated mailbox
Create .ctl and .dat file
The .ctl file
Details needed
Where the data should be sent to
<WorkflowID> Workflow ID: DPS_DEVICES_IMPLANTS
<ToDTS> Mailbox ID: X26HC046 (noting that is a zero and not a capital O in the mailbox ID)
Where the data should be sent from
<FromDTS> NEW Mailbox ID: Insert Mailbox ID the Data Liaison Manager helps get
Creating the .ctl file
- Copy the script template available in MESH Client user guide and found under sub heading Create the .ctl file (also known as the control file)
- Open MS Notepad and paste the script
- Update script with required details as per MESH Client user guide and found under sub heading Create the .ctl file (also known as the control file)
- Save the file
- Close the file
- Go to the file
- Right click open with notepad
- Select file
- Select save as
- Change save as type to all files
- Add .ctl onto end of file name
- Select save
- Your .ctl file has now been created
The .dat file
Creating your .dat file
Right click open with notepad, select file save as and then add .dat onto the end of the file name.
Naming of the .ctl and .dat file
MESH does not care about content of the .dat file.
The name in front of the .dat in the file name must exactly match exactly what is in front of the .ctl
for example
your-ODS_20220131.csv.ctl
your-ODS_20220131.csv.dat
Place the .ctl and.dat files into the mailbox's OUT folder for collection by the MESH Client and confirm if it has been sent correctly
Follow the advice on how to make the bulk submission found in the “Send both the .dat and .ctl files as a message” section of the MESH client user guide.
To check that the message has been sent correctly, the <Status> field of the returned .ctl file should read success.
It's up to individual health care organisations and Independent health care sector organisations to manage the “sent” folder and archive/delete files as necessary.
If the file submitted cannot be sent, the organisation will receive a .ctl file to the “in” folder. To know why the message did not send correctly, refer to the <Event>, <Status> and <StatusType> fields of the .ctl file received to the “in” folder.
The common types of error received in the “in” folder, and how to resolve them, are listed in the “Error Messages and failure to send” section of the MESH client user guide
Last edited: 1 March 2023 5:28 pm