Business ACKs for MESH messages

Message Exchange for Social Care and Health (MESH)
,
1

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

2

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/out-of-hours

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

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