![mesh enabler alternative mesh enabler alternative](https://www.redhat.com/sysadmin/sites/default/files/styles/full/public/2020-01/yellow-and-black-detour-signage-1717728.jpg)
Please refer to the applicable messaging use case details page for information on the Workflow ID to be used when generating particular messages. Where the use case requires some form of ITK acknowledgement, an additional Workflow ID will be created to be used for acknowledgement messages generated for the use case. Workflow ID configurationĪll messages which are sent to MESH specify a Workflow ID which identifies the workflow a particular data transfer is part of.Įach GP Connect Messaging use case will be associated with a single Workflow ID which has been created use with messages generated by that use case only. When using this automated means of message routing, the To_DTS field in the MESH message control (.ctl) file must be populated according to the same syntactic conventions described for the MESH API above. The MESH Client is an alternative means which organisations use to send and receive messages from the MESH central server infrastructure. The underscore _ character is used as the delimiter.ĭate of birth is specified in yyyyMMdd format.įor example, when sending a message about a patient Mr Brian Smith, born 14 February 2001, with NHS Number 12345678, the Mex_To field will have the following value: When using the MESH endpoint lookup service, the Mex-To HTTP header is populated according to following syntactic conventions. Please refer to the MESH API specification for details. The MESH API is a simple REST HTTP API which enables message senders to send messages through MESH.
#MESH ENABLER ALTERNATIVE HOW TO#
Refer to details below in the MESH API and MESH client for how to do this. Rather than specifying the destination mailbox ID, the message sender simply specifies the NHS Number, Surname and Date of Birth of the patient in the message header. This simplifies the task of message creation for the sending organisation.
![mesh enabler alternative mesh enabler alternative](https://d2908q01vomqb2.cloudfront.net/fe2ef495a1152561572949784c16bf23abb28057/2020/11/23/AppMesh-Components.png)
MESH takes care of routing the message to the mailbox of the patient’s registered GP practice.
![mesh enabler alternative mesh enabler alternative](https://www.esa.int/var/esa/storage/images/esa_multimedia/images/2020/09/mesh_reflector_for_shaped_radio_beams/22210554-1-eng-GB/Mesh_reflector_for_shaped_radio_beams.jpg)
Where message senders create messages destined for a patient’s registered practice, MESH message automated message routing is encouraged.Īutomated message routing enables a message sender to send a message to the MESH server without specifying a destination MESH mailbox ID. Note: For a more complete introduction to MESH, including details on how to get going if your organisation does not yet have MESH connectivity, see MESH - Message Exchange for Health and Social Care.