Please refer to Integration to MESH for an introduction to the use of MESH for GP Connect Messaging use cases.
MESH message routing
|GPCM-SD-056||all messages sent through this use case MUST use MESH automated message routing in order to ensure that the message is routed correctly to the registered practice of the patient|
Please refer to Message routing to registered practice for details of how to use this facility.
Workflow groups and Workflow ID
|GPCM-SD-057||Each instance of a Send Federated Consultation Report message MUST include the following MESH Workflow ID in the MESH message metadata:
|GPCM-SD-058||each instance of an acknowledgement message generated as a result of receipt of a Send Federated Consultation Report message MUST include the following Workflow ID in the MESH message metadata:
MESH client configuration
When using the MESH client to send a message to the MESH server, the
.CTL file will contain the following metadata about the message:
.CTL file is given below for a Federated Consultation Report message regarding a consultation which took place for a fictional patient: Mr Richard Smith, NHS Number 1234567890, Date of birth 9th January 1955.
<DTSControl> <Version>1.0</Version> <AddressType>DTS</AddressType> <MessageType>Data</MessageType> <From_DTS>GP0001</From_DTS> <To_DTS>GPPROVIDER_1234567890_09011955_Smith</To_DTS> <Subject>Federated GP consultation summary for patient Mr Richard Smith , NHS Number 1234567890, with details of encounter which at practice GP0001</Subject> <LocalId></LocalId> <DTSId></DTSId> <PartnerId></PartnerId> <Compress>Y</Compress> <Encrypted>N</Encrypted> <WorkflowId>GPFED_CONSULT_REPORT</WorkflowId> <ProcessId></ProcessId> <DataChecksum></DataChecksum> <IsCompressed>Y</IsCompressed> </DTSControl>
MESH API configuration