# MESH Client and FHIR

**URL:** https://openhealthhub.org/t/mesh-client-and-fhir/2435
**Category:** FHIR
**Created:** [21 May 2021 07:44 UTC](https://openhealthhub.org/t/mesh-client-and-fhir/2435 "2021-05-21T07:44:03Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Chris.Rouse](https://openhealthhub.org/user_avatar/openhealthhub.org/chris.rouse/32/832_2.png) [@Chris.Rouse](https://openhealthhub.org/u/Chris.Rouse)
#### Post date: [21 May 2021 07:44 UTC](https://openhealthhub.org/t/mesh-client-and-fhir/2435/1 "2021-05-21T07:44:03Z")

</div>

I am new to the MESH\ITK3 standards so I’m wondering if I can seek some advice.

Our outpatient letters come to us from the 3rd part system as a PDF. We need to send this to our GP practices using the MESH client. Using FHIR I think we can achieve this using the workflow TOC\_FHIR\_OP\_ATTEN.

What options are available to send a PDF?

As a side note, I think Kettering XML may be out of the question as the TOC\_OP\_ATT\_DMS workflow is used on another mailbox that is already being used by another system.

---

<div class="post-metadata">

### Author: ![mayfield.g.kev](https://openhealthhub.org/user_avatar/openhealthhub.org/mayfield.g.kev/32/648_2.png) [@mayfield.g.kev](https://openhealthhub.org/u/mayfield.g.kev)
#### Post date: [21 May 2021 08:06 UTC](https://openhealthhub.org/t/mesh-client-and-fhir/2435/2 "2021-05-21T08:06:38Z")

</div>

I believe that workflow id refers to this specification [Transfer of Care - FHIR API - NHS Digital](https://digital.nhs.uk/services/interoperability-toolkit/developer-resources/transfer-of-care-specification-versions)  
and **Outpatient Clinic Letter**.

This is a FHIR Document which means a HTML document plus structured clinical content.

I don’t know what the workflow id for kettering is I’d expect TOC still means transfer of care.

If you have a PDF document, the only option I believe is Kettering over MESH.

---

<div class="post-metadata">

### Author: ![Chris.Rouse](https://openhealthhub.org/user_avatar/openhealthhub.org/chris.rouse/32/832_2.png) [@Chris.Rouse](https://openhealthhub.org/u/Chris.Rouse)
#### Post date: [21 May 2021 08:15 UTC](https://openhealthhub.org/t/mesh-client-and-fhir/2435/3 "2021-05-21T08:15:06Z")

</div>

Thank you. I think that has just confirmed my that at thought might be the case.

---

<div class="post-metadata">

### Author: ![chris.cooper](https://openhealthhub.org/letter_avatar_proxy/v4/letter/c/b9bd4f/32.png) [@chris.cooper](https://openhealthhub.org/u/chris.cooper)
#### Post date: [21 June 2024 13:02 UTC](https://openhealthhub.org/t/mesh-client-and-fhir/2435/4 "2024-06-21T13:02:03Z")

</div>

Hi @mayfield.g.kev

I’m currently developing a MESH API interface to send PDF reports, but I can’t seem to get the MESH API to send the PDFS.

What I have tried, which have failed.

1. Simple PDF converting to Base 64 and sent in body with content-type of application/pdf
2. Kettering. I’ve taken a example from number of different source online (plus a vision document) and sent the Kettering XML in the body with a content-type of “application/octet-stream”

Di you get your service to send a PDF and if so how? If you could help or point me to some useful resource, that would be great.

Thanks
