I’m working on adding MESH functionality into our systems and am struggling to understand some of how MESH works.
As part of the send message endpoint you specify content type. Initially I was setting that to application/pdf, however the message was always received as application/octet-stream. I then spoke to NHS digital who said that all messages are sent in that manner, and that any header containing the content-type is ignored.
So my question: How does MESH know what document I’m sending? .pdf .doc or even just .txt
At the moment I’m sending the content as the base64_encoded string of the PDF, but have no idea how it is being received at the client end as I don’t yet have access to a mailbox with a GUI!
MESH is a transport like TCP/IP and JMS. It doesn’t really have message layer where you specify message metadata like this.
From what I understand the workflowId is associated with messaging layer. For example some workflowId’s will specify the payload is always HL7v2 ORU_R01 messages, others such as those for Transfer of Care will state the payload is a HL7 FHIR Message with FHIR Document.
So MESH doesn’t understand the payload (or need to), it knows who the message is going to, where it is from and the workflowId. The receiving system needs to know how to handle the payload according to the workflowId.
Graham, as Kev, says MESH is just the transport. Our experience is that the different consuming systems have different encoding approaches - it’s trial and error to get it right. We have an RESTFUL API that we’ve put in front of MESH that allows PDF documents to be delivered into GP Systems for NHS Contracted services. At the moment this uses the Kettering approach to actually define the message to deliver. Happy to see if we can help commercially if that would benefit you organisation. We have a simple JSON API with a connection and per message cost. Paul. ptargett@riviam.com
All our messages will be PDFs being delivered to GP practices. Most of our clients use Docman/EMIS or SystmOne. Do these systems have integration with MESH?
Originally I was thinking the practice would receive our PDF into their MESH inbox (like email) and then manually file. I’ve already developed our backend to send and receive messages with the MESH API - it seems I just need to get the encoding right.
From what you say about workflows, might it be possible to get NHS Digital to create a new workflow ID for our documentation?