# Sending e-Discharge summary via MESH API or MESH Client

**URL:** <https://openhealthhub.org/t/sending-e-discharge-summary-via-mesh-api-or-mesh-client/1775>\
**Category:** open forum\
**Created:** [22 September 2018 21:08 UTC](https://openhealthhub.org/t/sending-e-discharge-summary-via-mesh-api-or-mesh-client/1775 "2018-09-22T21:08:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tharma](https://openhealthhub.org/user_avatar/openhealthhub.org/tharma/32/683_2.png) [@Tharma](https://openhealthhub.org/u/Tharma)\
**Post date:** [22 September 2018 21:08 UTC](https://openhealthhub.org/t/sending-e-discharge-summary-via-mesh-api-or-mesh-client/1775/1 "2018-09-22T21:08:36Z")

</div>

Hi,

What are the differences in these two approaches, does that mean the supplier EPR system would have the option to code against the MESH API ? are these MESH APIs available in all languages ?

with MESH Client, does the EPR sends the documents using REST to the locally installed MESH Clients ?

thank you in advance

---

<div class="post-metadata">

**Author:** ![adamlees](https://openhealthhub.org/letter_avatar_proxy/v4/letter/a/e95f7d/32.png) [@adamlees](https://openhealthhub.org/u/adamlees)\
**Post date:** [24 September 2018 09:43 UTC](https://openhealthhub.org/t/sending-e-discharge-summary-via-mesh-api-or-mesh-client/1775/2 "2018-09-24T09:43:14Z")

</div>

The MESH API is an alternative mechanism to the MESH java client. You would typically use one or the other to access the MESH service, though I guess there’s nothing stopping you using a combination of both mechanisms.

So your EPR can either access the older file folder based mechanism or use the REST API.

If by “are these MESH APIs available in all languages?” you mean programming languages then yes. It is a REST API so any language which has support for https can use it.

API documentation here [https://meshapi.docs.apiary.io/#](https://meshapi.docs.apiary.io/#)