# Business ACKs for MESH messages

**URL:** <https://developer.community.nhs.uk/t/business-acks-for-mesh-messages/8547>\
**Category:** Message Exchange for Social Care and Health (MESH)\
**Tags:** mesh-api, mesh\
**Created:** [3 November 2025 12:19 UTC](https://developer.community.nhs.uk/t/business-acks-for-mesh-messages/8547 "2025-11-03T12:19:47Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Faraz\_Malik](https://avatars.discourse-cdn.com/v4/letter/f/f14d63/32.png) [@Faraz\_Malik](https://developer.community.nhs.uk/u/Faraz_Malik)\
**Post date:** [3 November 2025 12:19 UTC](https://developer.community.nhs.uk/t/business-acks-for-mesh-messages/8547/1 "2025-11-03T12:19:47Z")

</div>

Hello,

Just wanted to ask for some clarification about the business acknowledgment workflow. Currently we’ve set up copies from a GP practice for the following workflow IDs:

- `DISCH_KET`
- `OOH_ADASTRA`
- `OOH_MESSAGE`
- `DIGMED_FLU_VAC`
- `TOC_FHIR_EC_DISCH`

Of these, the following workflow IDs require business ACKs to be sent back:

- `DIGMED_FLU_VAC_ACK`
- `TOC_FHIR_EC_DISCH_ACK`

We need to be prepared to complete these business ACKs, once we redirect messages from the practice’s mailbox to ours.

The approach we’re taking is to send an ACK with the original message ID in the `mex-localid` header. Is this approach valid? Or does it vary between workflow IDs?

Thanks in advance,

Faraz

---

<div class="post-metadata">

**Author:** ![paddy.yung](https://avatars.discourse-cdn.com/v4/letter/p/e79b87/32.png) [@paddy.yung](https://developer.community.nhs.uk/u/paddy.yung)\
**Post date:** [4 November 2025 09:15 UTC](https://developer.community.nhs.uk/t/business-acks-for-mesh-messages/8547/2 "2025-11-04T09:15:52Z")

</div>

Hi Faraz,

Unfortunately, the main issue affecting developers and suppliers like yourself needing help and guidance is that a lot of the workflows that you want to use are deprecated…

[https://digital.nhs.uk/developer/api-catalogue/transfer-of-care-pre-fhir](https://digital.nhs.uk/developer/api-catalogue/transfer-of-care-pre-fhir)

[https://digital.nhs.uk/developer/api-catalogue/out-of-hours](https://digital.nhs.uk/developer/api-catalogue/out-of-hours)

[https://digital.nhs.uk/developer/api-catalogue/digital-medicine-fhir](https://digital.nhs.uk/developer/api-catalogue/digital-medicine-fhir)

…while others (like the Transfer Of Care FHIR ones) did have an onboarding team which has since been disbanded, but you may be able to get information and message specifications from the pages under [https://digital.nhs.uk/services/transfer-of-care-initiative](https://digital.nhs.uk/services/transfer-of-care-initiative)

As the structure of the deprecated workflows may be non-standard, for details of a specific integration, you may need to reach out to the supplier of the application you want to integrate with:  
Advanced  
EMIS Web  
Medicus Health  
TPP SystmOne

We encourage contributions on this forum from developers who may be able to assist, but a wider search on internet has shown related discussions (albeit a few years old) on community forums such as e.g. [Kettering XML and SystmOne - open forum - openhealthhub.org](https://openhealthhub.org/t/kettering-xml-and-systmone/2468)