A suggested file name format, as used above, is: “Organisation_Date_Time”. This ensures there are no duplicates on MESH.
You can use any text editor, including Notepad or Wordpad, to create or edit the .dat and .ctl files.
Create the .dat (data) file
MESH can send all types of data.
Rename the data you wish to send as a .dat file. This can be done in two ways: adding on the “.dat” extension after the original file type or removing the original file type extension and replacing with “.dat”.
For example, you may have a xxxx.csv file that you wish to send. You can either add the file type to the end (rename the file xxxx.csv.dat) or change the file type (rename the file xxxx.dat). With the former option, your recipient will need to remove the “.dat” from the file name to view, and with the latter, the recipient will need to know what programme to open the data file with, as there is no indication from the file name what type of data is contained. Choose the option most suitable for you and your recipient.
Create the .ctl file (also known as the control file)
This is the companion to the .dat file and contains all message meta-data in an XML file.
The structure of the file must match the format of the example below. The text highlighted in bold should be replaced with your own organisation’s details. Without these changes, your file will not successfully be delivered and processed.
<WorkflowID> section should be the name of the correct workflow ID described in the email received when your mailbox was first created.
<ToDTS> section should be the name of your recipient’s mailbox. If you do not know what this is already, it's usually easiest to ask your recipient directly for their MESH mailbox name. Otherwise, please refer to the MESH endpoint lookup service page for further guidance on finding a mailbox name.
<FromDTS> section should be the name of your mailbox ID, included on the email received when your mailbox was first created.
<Subject> section is optional and acts like an email subject header, so you may use this as an opportunity to explain to the recipient what the message is about, name a specific member of staff for the recipient mailbox’s information, or what the message contains. You may leave blank if you wish.
<LocalId> section is an optional field. You can specify any reference or information which is useful to you, such as which clinician sent the file. You may leave blank if you wish.
<Compress> section is to indicate that the data file can be compressed by the MESH client. Put “Y” if you wish for this, and a “N” if you do not want it compressed.
Send both the .dat and .ctl files as a message
Once you’ve created the .dat and .ctl files, place these in the “out” folder in your mailbox. If you're moving the files individually into this folder, please ensure you put the .dat file in first.
The timing of the message being sent will depend upon how the MESH client is configured to connect to the mailbox – this is referred to as “polling”. This is automatically set up to be every 30 minutes, however your MESH client installer may have altered the configuration of your MESH client for specific needs. When your mailbox has polled, your messages will then automatically be moved to your “sent” folder and get sent through to the “in” folder of your recipient’s mailbox.
The .ctl file will be altered when moved from your “out” folder to your “sent” folder. The new structure of the .ctl file will be:
<IsCompressed >Y</IsCompressed >
<Event>Transfer to DTS Server</Event>
To check that your message has been sent correctly, the
<Status> field of the returned .ctl file should read “Success”.
It's up to your organisation to manage the “sent” folder and archive/delete files as necessary.