Skip to main content

Message Exchange for Social Care and Health: client installation guidance

The Message Exchange for Social Care and Health (MESH) client installation guidance explains the installation and configuration of the default MESH client on Windows. We recommend systems suppliers or IT administrators handle the set-up of MESH for each organisation.

This guidance explains the installation and configuration of the default MESH client on Windows. There is an additional MESH client advanced and other settings page which offers further information on specific settings and technical requirements, including the installation process for LINUX, that may be applicable for some, but not all, installations. There are links throughout this guidance indicating where these additional options may be applicable for you.

For user guidance on how you use MESH client once installed, including how to send and receive messages, please refer to our MESH client user guide.

MESH is a centralised service managed by NHS Digital. It supports clinical and business processes requiring the secure transfer of data between NHS and affiliated organisations.

MESH consists of a:

  1. MESH client - usually integrated into supplier provided applications installed at end-sites (individual organisations).
  2. Central MESH server - located within the Spine Core Messaging Service.

MESH client allows secure transfer of data via an encrypted link between the end-site application (your organisation) and the central MESH server. The central MESH server stores data sent to it until the intended recipient site connects to the service and, with its MESH client, collects the data addressed to it over an encrypted link.

Installation pre-requisites

Please ensure you have met all the following requirements before beginning the MESH client installation.

Necessary firewall configurations in place for HSCN connection

To access MESH through the Health and Social Care Network (HSCN)/N3 connection, you will need to ensure that you have this connection, and that your local firewall configurations allow access where necessary to connect to appropriate Uniform Resource Locators (URLs)/Internet Protocol (IP) addresses.

The minimum requirement to access the MESH service to send and receive data is:

Domain name server Port Protocol External IPs Target application
mesh-sync.national.ncrs.nhs.uk TCP/443 HTTP over TLS

155.231.48.156
155.231.48.220

URL used by the MESH client to send and receive messages

To test your current access to these, we recommend you work in conjunction with your local technical lead to complete the following steps.

If using Windows, open a command prompt (Start, search “cmd”, open Command Prompt) and enter the following commands:

telnet mesh-sync.national.ncrs.nhs.uk 443

telnet 155.231.48.156 443

telnet 155.231.48.220 443

If using Linux, open a terminal and enter the following commands:

telnet mesh-sync.national.ncrs.nhs.uk 443

telnet 155.231.48.156 443

telnet 155.231.48.220 443

If you have the required access, you'll get a blank screen. If you have anything other than a blank screen, you'll need to get the IP addresses added to the local firewall.

Necessary firewall configurations in place for internet connection

To access MESH via the Internet, you will need to ensure that you have this connection, and that your local firewall configurations allow access to all IP addresses for port 443. 

The minimum requirement to access the MESH service to send and receive data is:

Domain name server Port Protocol Target application
mesh-sync.spineservices.nhs.uk TCP/443 HTTP over TLS URL used by the MESH client to send and receive messages

 To test your current access to these, we recommend you work in conjunction with your local technical lead to complete the following steps.

If using Windows, open a command prompt (Start, search “cmd”, open Command Prompt) and enter the following commands:

telnet mesh-sync.spineservices.nhs.uk 443

If using Linux, open a terminal and enter the following commands:

telnet mesh-sync.spineservices.nhs.uk 443

Create a mailbox

All new MESH client installations require a mailbox to be requested and created. If you already have an existing MESH mailbox, you can use this for the installation of MESH client.

Please complete a MESH mailbox request form if you require a mailbox.

Once the registration is complete and approved the technical contact at the responsible organisation, as described on the request form, will be provided with the mailbox and authentication key (mailbox password) details to support the local installation. Confirmation of the mailbox details excluding the authentication key will also be provided to the requestor.

Obtain correct certificate for access to Spine

Important information

Before requesting the certificate, please ensure your mailbox has been created. You will need to send the mailbox details via a new service request to have a certificate created before you can begin the MESH Client installation. 

To improve security levels to meet the current Spine Core security requirements, all MESH client installations will require a specific local certificate.

Please refer to our MESH certificate guide for more information about which certificate you will need, and how to request one.

The minimum software environment of Java Runtime Environment 8x

The MESH client is written in Java and requires a Java Virtual Machine (JVM) 8 or later to be installed on the server running the client. This is a common pre-requisite for a number of applications, and it's likely you'll already have a JVM running on your server.

We recommend the latest version of the JVM is installed (currently version 8.x) and it can be downloaded from the Java Download web page.

Computer systems which access NHS Digital services must meet certain technical standards. The Warrented Environment Specification (WES) defines the client environments that we support.

Find out more about WES.

Microsoft client
Operating System/Java Version Non-Java Java 61 Java 72 Java 83
Windows 2000 (SP3/SP4) Not supported MESH Client 6.x supported Not supported Not supported
Windows Vista (SP1,SP2) – x86/x64 Not supported MESH Client 6.x MESH Client 6.x MESH Client 6.x
Windows 7 (SP1) – x86/x64 Not supported MESH Client 6.x MESH Client 6.x MESH Client 6.x
Windows 8.x – x86/x64 Not supported MESH Client 6.x MESH Client 6.x MESH Client 6.x
Windows 10 – x86/x64 Not supported Not supported MESH Client 6.x MESH Client 6.x
Microsoft Server
Operating System/Java Version Non-Java Java 6.1 Java 7.2 Java 8.3
Windows Server 2003 SP1/SP2 Not supported MESH Client 6.x supported Not supported Not supported
Windows Server 2008 (SP1, SP2) –x64 Not supported MESH Client 6.x MESH Client 6.x MESH Client 6.x
Windows 2012 – x64 Not supported MESH Client 6.x MESH Client 6.x MESH Client 6.x
UNIX
Operating System/Java Version Non-Java Java 61 Java 72 Java 83
Sco Unix MESH Perl Client Not supported Not supported Not supported
HP-UX 11i v1 (11.11) - HP PA-RISC4  MESH Perl Client MESH Client 6.x Not supported Not supported
HP-UX 11i v2 (11.23) - HP PA-RISC4  MESH Perl Client MESH Client 6.x Not supported Not supported
HP-UX 11i v3 (11.31) - HP PA-RISC4  MESH Perl Client MESH Client 6.x Not supported Not supported
HP-UX 11i v2 (11.23) - HP Itanium4 MESH Perl Client MESH Client 6.x MESH Client 6.x Not supported
HP-UX 11i v3 (11.31) - HP Itanium4 MESH Perl Client MESH Client 6.x MESH Client 6.x MESH Client 6.x
Linux MESH Perl Client MESH Client 6.x MESH Client 6.x MESH Client 6.x
IBM AIX 5.35 MESH Perl Client MESH Client 6.x Not supported Not supported
Minimum memory requirements

We recommend that the host system has a minimum memory of 1GB random access memory (RAM) to run the client, in addition to the operating system requirements.

We recommend that sites have a minimum of 100MB of RAM for each mailbox the MESH client is supporting. If your MESH client will be supporting several mailboxes, you'll need to ensure your server has enough memory to accommodate potential simultaneous upload or downloads in a multi-mailbox operation.

Sufficient disk space for the client and the log files

The MESH client is contained in a Java Archive .jar file and requires approximately 10MB of disk space. 

The system requirements of the MESH client are governed by the size of the files being transferred rather than the requirements of the application. 

For servers running an operating system that does not support a JVM of 1.7 or later, or have limited memory, NHS Digital has developed a script-based client that is started using a schedule task or a UNIX cron job to send and receive messages. Please contact us at ssd.nationalservicedesk@nhs.net for more information.

We recommend you allocate additional space on the server/PC hard drive for archive reports and sent/received folders.

Security

Since the service provides access to patient identifiable data, we recommend that the software is installed on a server or in a secure shared environment. We do not recommend users install the MESH client on individual computers or local drives.

Install MESH client on Windows

The following sections describe the steps for installing the MESH client on a Windows server.

It's assumed that the user performing the installation has logged onto the server with administration rights and has checked that their systems meet the pre-requisites outlined above.

Step 2

Open this pack and click “Extract to” before choosing the location you wish to extract these files to.

The installation .jar file is named: “mesh-6.2.0_20180601”. To ensure this file will open and run, right click on the file, click “Properties” and check that:

  • the type of file = executable .JAR file
  • it opens with Java ™

Step 3

Open the .jar file by either double clicking on the icon in your folders, or right-click on the .jar file and click “Open With”, then select the appropriate Java Runtime. 

Alternatively, the .jar file can be opened by opening the Command Prompt (search via your Start button for “cmd”, open the Command Prompt). Rewrite the drive location manually if necessary to where the .jar file is saved.  After the file location in the Command Prompt copy in:

java –jar MESH-<version number>-installer-signed.jar

Write in the version number of the MESH client you are installing (found on the name of the .jar file itself) where the bold text is above. It should look something similar to:

java –jar MESH-6.2.0_20180601-installer-signed.jar

Press “Enter” on your keyboard, and the installer should open on your screen.

Step 4

You'll now be presented with a screen stating: “Welcome to the installation of the NHS Digital MESH Client 6. 2. 0_20180601!”. Click “Next”.

Step 5

This screen will prompt you to select the installation path. You'll have a suggested path already in the box; this can be changed using the “Browse” button if you wish to select a new installation path. Once you are happy with your installation pathway, click “Next”.

Selecting “Quit” will stop the installation process.

If the target directory exists, you'll be warned that the installer may overwrite files in this directory. Confirm as required, then click “Next”.

If the target directory does not exist, you'll be warned that the installer will create it. Confirm as required, then click “Next”.

Step 6

A default folder location for the install will be displayed. If you do not wish to install the client into this folder location, you have the option to change the location via the “Browse” button.

Once you're satisfied that the appropriate folder location is specified, click “Next”.

Step 7

You'll now be prompted to provide details of your MESH mailbox and the mailbox type. You'll have received this information when you completed the mailbox request form as part of your pre-requisite checks.

Type your mailbox name into the box indicating “Mailbox ID”. Ensure that the mailbox type is set to the default of “MESH” before clicking “Next”.

Step 8

If you wish for your MESH client to automatically update when newer versions are available, click “Yes” on this screen. This means the MESH client will check automatically that the newest version is running and, if a newer version is available, download the new version and install it for you. This will cause MESH client to stop running and may involve a manual restart. The update of client will mean you need to restart locally on your systems; however, communications will be provided before the release of any new version, so users have prior warning and have the option to review their configuration. We recommend that this setting is enabled.

If you wish to manage the update process manually, or wish to use MESH as a service, please select “No”.

Click “Next” to continue.

Step 9

The installer will now summarise the installation tasks it will perform on the “Summary Configuration Data” page.

If you're happy with your installation, click “Next”.

Step 10

The installer will now install the required packages.

Once the installation is complete, the screen will show:

  • Pack installation programme: Finished
  • Overall installation progress: 5/5

Click “Next”

Step 11

The installer will now show “Perform External Processes” in the top right corner of the screen, with “Processing” in the top centre. This is a summary of its actions. 

Click “Next”.

Step 12

This screen has an option for you to “Generate an automatic installation script”, which will allow any similar changes to be undertaken for additional installs. If you do not wish to utilise this option to generate an installation script (if you do not wish to make similar future installs of MESH), click “Done” to complete the installation and move on to Step 13 in this guide.

If you wish to use this option, then select the button provided.

An xml file will be generated similar to the code below:

COPY
<?xml version-"1.0"-encoding="UTF-8"-standalone="no"?>

<AutomatedInstallation-langpack="eng">

<com.izforge.izpack.panels.hello.HelloPanel-id="HelloPanel_0"/>

<com.izforge.izpack.panels.target.TargetPanel-id="TargetPanel_1">

<installpath>C:\MESH-APP-HOME</installpath>

</com.izforge.izpack.panels.target.TargetPanel>

<com.izforge.izpack.panels.userinput.UserInputPanel-id="Config.DTSClient">

<entry key="data.path" value="false"/>

</com.izforge.izpack.panels.userinput.UserInoutPanel>

<com.izforge.izpack.panels.userinput.UserInputPanel-id="Config.DataLocation">

<entry-key="data.path"-value="C:MESH-DATA-HOME"/>

</com.izforge.izpack.panels.userinput.UserInputPanel>

<com.izforge.izpack.userinput.UserInputPanel-id="Config.AllowAutoUpdates">

<entry-key="autoupdate.allow"-value="Y"/>

</com.izforge.izpack.panels.userinput.UserInputPanel>

</com.izforge.izpack.panels.userinput.UserInputPanel-id="SummaryPanel_6"/>

</com.izforge.izpack.panels.userinput.UserInputPanel-id="InstallPanel_7"/>

</com.izforge.izpack.panels.userinput.UserInputPanel-id="ProcessPanel_8"/>

</com.izforge.izpack.panels.userinput.UserInputPanel-id="FinishPanel_9"/>

</AutomatedInstallation>

HTML

You'll be prompted to save the file for later use. Please select where you wish to store the file and click “Save”. There is also an option to cancel if you no longer want to save the file.

Step 13

The installation of the MESH client is now complete. A few further configuration steps must be undertaken before the MESH client is available for use.

The MESH client will have been installed in your chosen folder. Find this folder (if you did not adjust the install destination previously, it will be in “MESH-APP-HOME”). You should have a series of folders, including “log”, “proxy” and “KEYSTORE”. The following configuration steps require access to the files beneath these folders on the list.

Open the meshclient.cfg file in a text editor (such as Notepad or Wordpad). There are three lines to edit in this document. Please edit the bold sections, shown below:

<KeyStorePassword>InsertYourKeyStorePasswordHere</KeyStorePassword>

<ClientIdentity>InsertYourMailboxIDHere</ClientIdentity>

<ClientAuthentication>InsertYourMailboxPasswordHere (it will currently say “ClntAuth1”)</ClientAuthentication>

Your mailbox ID and client authentication will have been confirmed when you applied for your mailbox during the pre-requisite checks. ”Client Authentication” is also known as your mailbox password. You will have made your Keystore password when applying for your endpoint certificate during pre-requisite checks.

The Keystore path refers to the location of your MESH Keystore file (C:\MESH-APP-HOME\KEYSTORE\MESH.keystore for example). You will have made your Keystore password when applying for your endpoint certificate during pre-requisite checks.

If using the MESH client on a non-Windows based server, the above process can be used and the MESH.keystore copied to the server and configured in the same way. 

If you'll be accessing the MESH client via the Internet, rather than using the default N3/HSCN network, the following parameters will need to be changed in the mesh.cfg file:

<PrimaryURL> - this needs to be set to: https://mesh-sync.spineservices.nhs.uk
<Keystore> - will need to be set to the name of your KeyStore

For API installation only, the configuration of your certificate will vary depending upon your current systems.

Further configuration changes are available from the default settings, if you wish. Our Advanced and other settings page details many changes that can be implemented, including:

meshclient.cfg file: the maximum and minimum number of messages that can be sent per poll.

Proxy: setting up your MESH client if you sit behind or use a proxy server.

log4j.xml file: how detailed the logging levels of your MESH client will be. This refers to a log that MESH client produces of all actions, such as start-up, sending data, receiving data, and any message errors. The logs are helpful to refer to if your files fail to send correctly.

Step 14

Once all the configuration changes have been saved the client can be started by double clicking the runMeshClient.bat. If the client is running you will see the log file generated in the folder defined in the meshclient.cfg file. The default folder location for the log file is \MESH-APP-HOME\log for a new MESH installation.

Below are sections outlining the running of MESH client as a service (running the software automatically in the background) and how to configure your files. These are optional.

If you do not want to run the MESH client as a service, and would rather manually run the MESH client when logging on: To start MESH client, select the .bat file stated above to begin the client after logging on to your computer each time, which will open up a blank command window. To stop the MESH client, simply close the blank command window.

Run the MESH client as a service (ensure MESH client is installed first)

This section describes the installation of a utility to run the MESH client as a Windows service. This is an optional part of the installation process - it will enable MESH client to automatically run when restarting your server and run in the background without the need for you to keep opening and closing the client manually for it to run. Without installing MESH client as a service, you'll need to ensure you always leave the blank command box open if you wish to run the software, and manually start MESH client after restarting the server.

The utility is a reconfigured version of the Apache Procrun utility. The installation of the MESH client Windows service should be completed after the MESH client has been installed and tested.

One limitation of running the MESH client as a service is that it prevents the MESH client auto-update from refreshing the MESH client if a new version is available. Therefore, we recommend that this feature is disabled.

To disable the MESH auto-upgrade, edit the meshclient.cfg and disable this feature. It's turned off by having ‘N’ in the AutoUpgrade setting:

<AutoUpgrade>N</AutoUpgrade>

The MESH client will continue to check if a new version of the MESH client is available and will log when a new client is available but not attempt to automatically install it.

Step 1

Right-click on meshclient_windows_service.zip and choose to “Extract All”. Click “Browse” to select the installation path of the MESH client and the files will be installed into that location.

Step 2

Before installing, check that the meshclient_service_install.bat and meshclient_service_uninstall.bat files reflect the version of Java that the client is running on.

Right-click on meshclient_service_install.bat and click “Edit”. If you are using a 32 bit version of Java, change to @set ARCH=x86. If it is 64 bit, leave as default. Then File, Save and Exit.

Repeat for the meshclient_service_uninstall.bat file.

Prior to the actual install, stop the MESH client (for example, by sending a “1” to the mexclient.sig signal file) as the service cannot be started if it is already running.

Step 3

Double-click on mesh_service_install.bat to commence the service installation. Depending on security settings, you may be prompted with "are you sure?" type questions. Select the appropriate response if you wish to install. After the "Press Any Key to continue..." the service is installed (but not started).

Step 4

Press the Windows key on your keyboard, go to “Run” and open services.msc. Highlight the MESH client Service and click Start. For convenience, a SysTray icon is provided to the bottom right of your screen. To install it, double-click mesh_service_systray.bat.

Step 5

Once installed, you can Right-click on the SysTray to start/stop the service or double-click to access further settings.

Step 6

You may wish to change the current configuration. To do this, right-click on the SysTray icon and click “Configure”.

The “General” tab allows the start-up settings to be changed.

The “Log on” tab allows the log on user to be changed for this service.

The “Logging” tab allows the logging level and log file location to be changed. The default location will be the MESH log directory and to log at “info” level. The Apache wrapper creates its own log file as well as adding entries into the MESH mesh.log log file.

The “Java” tab specifies the Java Virtual Machine to use and defines the Java classpath, which is the location of the Java command to be run as a service with the Java options to be used.

The “Startup” and “Shutdown” tabs specify the Java class to be run when the service is started or stopped. The settings on this tab should not need to be changed.

Install a new version of MESH client over an existing installation (updating an older version)

New versions of the MESH client will be released periodically as the service matures and new functionality is introduced in support of requirements for extended use of the service. NHS Digital will support the current and one previous version of the client.

If you have disabled the automatic update option on your configuration of MESH client, you can update the version of MESH client that you are using by following the steps for either of the options below:

Install as if a fresh install

Undertake a completely fresh install as if no previous installation exists. The existing client and/or the associated service, if used, must be stopped. Install the new client as detailed above.

Once the installation process is complete the configuration and keystore can be copied from the original installation and any additional configuration changes to take advantage of any new functionality can be made. It's not necessary to apply for a new digital certificate. The configuration for the client is contained in the meshclient.cfg file within the \MESH-APP-HOME folder. The keystore is stored in \MESH-APP-HOME\Keystore. 

Once the configuration file and keystore have been copied to the new installation the client and/or service should be restarted. The old client files should be removed or archived once the new client deployment has been assured and is fully operational.

Install over existing installation

  1. Download the installation pack from the website and unzip the contents. The latest version of MESH client can be found in the installation pack. 
  2. Logon to the machine where the client installation resides.
  3. Stop the MESH client and/or service.  
  4. Go to the \MESH-APP-HOME\ folder and rename the meshclient.jar meshclient.old.
  5. Copy the new MESH client file from the installation pack to \MESH-APP-HOME\.
  6. Rename the copied file meshclient.jar.
  7. Restart the MESH client and/or service.
  8. Review the log file to see that the new client is running as expected.

If changes are required to be made to the client configuration they can be made at this time. The client and or the service will need to be stopped. The attributes held in the \MESH-APP-HOME\meshclient.cfg file may be changed, and then the service restarted.

MESH client file configuration

Now you have installed the MESH client, this section will cover the interface of the mailbox(es), and how these can be updated and configured to your needs.

The MESH client will transfer data to and from the host application via a simple file based interface. The MESH client will use the following default 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.

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. 

Send and receive data

Where data is to be transferred (such as sending or receiving data) the file interface will contain two files;

Data file – <message_id>.dat

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 20GB. 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.

Control file - <message_id>.ctl

The control file will contain the information required to identify, transmit and audit the data file. The control file content may change, depending upon the transaction, however it must always be formatted as the following:

<DTSControl>
<Version>1.0</Version>
<AddressType>DTS</AddressType>
<MessageType>Data</MessageType>            
<WorkflowId>WorkflowID</WorkflowId>
<To_DTS>Recipient mailbox</To_DTS>
<From_DTS>Your mailbox</From_DTS> 
<Subject>XXXSubjectHeaderXXX</Subject>
 <LocalId>EXAMPLEXXXX-03102019-0001</LocalId> 
<Compress>Y</Compress>
<AllowChunking>Y</AllowChunking>
<Encrypted>N</Encrypted>
</DTSControl>

In bold are the commonly altered aspects of the control file. A full breakdown of the control file data structure is:

 

Data item Values / size Mandatory/ Optional/ Conditional Description
Version 1.0 M Version of control file
AddressType

SMTP
DTS
ALL 

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.

MessageType

Data

Report
M

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.

Conditional – must be supplied if AddressType = SMTP or ALL

From_DTS MESH mailbox 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 mailbox 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 email

Mandatory elements must be supplied.
Optional elements may be ignored or specified with no data.

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. 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.

Where only status information is to be transferred, such as delivery status information or error indication, the transaction will be a single control file. 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.

Use multiple mailboxes for one MESH client installation

You can use multiple mailboxes with one installation of the MESH client software. We recommend using a different mailbox for each type of service you will be using it for. For example, you may have one mailbox to send National Data Opt Out data, and another mailbox to send admissions, discharges and withdrawals data.

If you wish to use the MESH client with multiple mailboxes, you'll need to first request a new mailbox using our mailbox request form before completing the following steps to configure your MESH client to support multiple mailboxes.

If you decide to use a new mailbox with an existing client, you need to edit the MESH configuration file, meshclient.cfg, which will be in the directory and folder where the MESH client has been installed.

Add a new client section by including the following code in the configuration file:

<Client>
<ClientIdentity>mailbox ID</ClientIdentity>
<ClientAuthentication>authentication key</ClientAuthentication>
<MailboxType>MESH</MailboxType>
<InterfaceRoot>C:\MESH-DATA-HOME\Mailbox2</InterfaceRoot>
<CollectReport>Y</CollectReport>
<TransferReport>Y</TransferReport>
<PollReport>N</PollReport>
<SaveSent>Y</SaveSent>
</Client>

HTML

Enter the mailbox name and authentication key you were sent when your MESH mailbox was set up. The authentication key is also known as the mailbox password. Make sure the location in the InterfaceRoot field matches the directory location where the new MESH Mailbox is to be accessed, and ensure a corresponding folder and subfolders are created in the directory location. 

If Client has been installed as a service please stop and restart the service to ensure that changes are picked up.

See an example of a multi-mailbox configuration file.

Contact NHS Digital

If you have further questions related to MESH please contact the National Service Desk.

Last edited: 26 March 2021 4:44 pm