I have a question about LocalId in the control (.ctl) in the MESH specification … what this element signifies… is this one need to be associated with the processing node or per ODS (or even per mailbox) ??
Do you have a link to an example file?
HI, here is the example page Message Exchange for Social Care and Health: client user guide - NHS Digital. In fact, I found out the answer when looking the example you have asked… it seems this field is up to the implementer what they choose to link with. The
<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.
We populate the locaID with the transaction reference number recorded in our logging system. I see you are talking about CTL files so assume you are using the MESH client. You may want to match up a CTL file with a an audit trail on a transaction in case of any errors to enable you to trace the source of the error or similar - use the locaID to do that
Hope that helps?
Thanks for the information @Pedros . Actually we implement MESH API… so this should be under Mex-LocalId,
Yep. We use the API too, so use Mex-LocalID for your transaction number or similar in the API message header