We have detected that you are using Internet Explorer to visit this website. Internet Explorer is now being phased out by Microsoft. As a result, NHS Digital no longer supports any version of Internet Explorer for our web-based products, as it involves considerable extra effort and expense, which cannot be justified from public funds. Some features on this site will not work. You should use a modern browser such as Edge, Chrome, Firefox, or Safari. If you have difficulty installing or accessing a different browser, contact your IT support team.
Why use MESH
There are several reasons why your organisation may choose to use MESH. It:
- allows you to transfer large data files securely from one organisation to another
- allows large files (up to 20GB) to be sent, which cannot be sent over NHSmail (up to 35MB)
- has a user friendly interface, available through MESH UI
- allows some configuration to suit business needs when using MESH client/API
Organisations should have separate mailboxes for each use case to maintain the security of the data being sent and received.
MESH connects to the Spine infrastructure via the N3/HSCN network. If you cannot register for an N3/HSCN connection (local authorities for example) there is an option to connect via the public internet.
MESH can send files of any type, for many different purposes. Some examples of what MESH may be used for include:
- A pathology lab using MESH to communicate test results to GP practices.
- A hospital sending and receiving notifications to adult social services to identify patients who may need adult social care when they leave hospital, in line with the Care Act 2014.
In most cases, the systems suppliers or IT administrators will handle the set-up of MESH for each organisation. If you are a user of MESH and have technical questions, we recommend you get in touch with your organisation’s IT contact first.
Types of MESH available
We currently have three types of MESH to suit a variety of organisational needs and requirements.
- MESH Client - ideal for organisations sending or receiving large files (up to 20GB), such as GP sites, Trusts, private NHS providers).
- MESH User Interface (UI) - ideal for organisations sending or receiving small files (under 100MB over N3/HSCN and under 50MB over Internet Gateway).
- MESH Application Programming Interface (API) - MESH API is a restful API ideal for organisations who have the technical skills to integrate MESH into their systems.
Visit our Compare MESH services page for a more detailed summary of each method.
Users can apply for an account to track and trace messages sent using MESH by using the MESH Online Enquiry Service (MOLES), a message tracking service hosted on Spine which is accessed through via a user interface (UI). Also note that message tracking is available as part of the restful API.
Test your implementation - test client and message tracking API
Please contact the National Service Desk at email@example.com or call on 0300 30 35 035 for any technical or service issues and general enquiries including requests to be added to the distribution list for regular updates to service suppliers and users.
For testing related enquiries about MESH please contact Solutions Assurance at firstname.lastname@example.org.
Track messages sent using MESH through the Messaging Online Enquiry Service. Smartcard authentication required.
For new MESH account requests, support or technical queries raise a call to the National Service Desk (log-in and HSCN access required)
View our selection of MESH and MOLES technical documentation. These guides will help you install and use your MESH client, manage your advanced settings and identify recipient mailboxes using the endpoint lookup service.
We currently have three types of MESH to suit a variety of organisational needs and requirements. Here is a summary of the three types, with links to installation and user guides.
Track and trace messages sent using Messaging Exchange for Social Care and Health (MESH)
NHS organisations, IT specialists, adult social care teams and individuals can use this form to request a MESH mailbox. This new single form can be used to access the MESH user interface (UI) and MESH client/API.