# Use FHIR in open EMR V7

**URL:** <https://community.open-emr.org/t/use-fhir-in-open-emr-v7/19117>\
**Category:** OpenEMR Development\
**Tags:** question, feature\
**Created:** [September 9, 2022, 6:17pm UTC](https://community.open-emr.org/t/use-fhir-in-open-emr-v7/19117 "2022-09-09T18:17:59Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![adunsulag](https://community.open-emr.org/user_avatar/community.open-emr.org/adunsulag/32/12606_2.png) [@adunsulag](https://community.open-emr.org/u/adunsulag)\
**Post date:** [October 11, 2022, 11:41am UTC](https://community.open-emr.org/t/use-fhir-in-open-emr-v7/19117/3 "2022-10-11T11:41:08Z")

</div>

Great post Mandrake, only thing I would mention is that applications that are patient facing (meaning it is a patient that is using the app in their browser or mobile device) should use the Authorization Grant flow and not the client credentials grant. If you are needing offline\_access you must request the offline\_access scope in your app registration as well as in your authorization request.

Client Credentials grant is intended to be used for backend server to server communication. While you can register a mobile device or even a browser with a JWKS right now in OpenEMR, at some point we plan to restrict the JWKS registration to the URL option only in order to improve the security and ‘authenticity’ element of the credentials grant. The OpenEMR server will request the JWKS from the backend and so the URL must be publicly accessible on the internet secured via SSL/TLS.

Overall though great explanation and walkthrough @mandrake, thanks for putting this together.

---

_[View the full topic](https://community.open-emr.org/t/use-fhir-in-open-emr-v7/19117)._
