Difference between revisions of "OpenEMR 7.0.0 API"
From OpenEMR Project Wiki
|
Tag: Redirect target changed |
| (24 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| = Overview =
| | #REDIRECT [[OpenEMR_7.0.2_API]] |
| :OpenEMR API documentation for both FHIR API and Standard API.
| |
| <br>
| |
| | |
| = FHIR API =
| |
| :*[https://github.com/openemr/openemr/blob/master/FHIR_README.md FHIR API Documentation for 7.0.0]
| |
| :*[https://github.com/openemr/openemr/blob/master/FHIR_README.md#fhir-api-documentation Click Here] for instructions on using Swagger, which is included in OpenEMR, to see full documentation of endpoints and testing support.
| |
| :*Online links to Swagger based documentation can be found at [[Development_Demo|7.0.0 Demo]].
| |
| :*Videos that overview OpenEMR's FHIR API:
| |
| ::*[https://youtu.be/LQHNRBgg6Q8 OpenEMR FHIR Lecture Series: Lecture 1 - Overview and Use of FHIR in OpenEMR]
| |
| ::*[https://youtu.be/2qr0IV9Kulg OpenEMR FHIR Lecture Series: Lecture 2 - FHIR Bulk Data in OpenEMR]
| |
| <br>
| |
| | |
| = Standard API =
| |
| :*[https://github.com/openemr/openemr/blob/master/API_README.md Standard API Documentation for 7.0.0]
| |
| :*[https://github.com/openemr/openemr/blob/master/API_README.md#standard-api-documentation Click Here] for instructions on using Swagger, which is included in OpenEMR, to see full documentation of endpoints and testing support.
| |
| :*Online links to Swagger based documentation can be found at [[Development_Demo|7.0.0 Demo]].
| |
| <br>
| |
| | |
| = Native Applications =
| |
| :*Native applications wishing to use the OpenEMR FHIR API with refresh tokens MUST be capable of storing the refresh token in a secure manner similar to the requirements of storing a secret for confidential apps. Native applications must register their application as a confidential app and request the offline_scope in their initial API request in order to receive a refresh token. Refresh tokens are valid for 3 months before they must be renewed. Native applications can only communicate with OpenEMR over a TLS secured channel in order to ensure the safe transmission of the refresh token. Native applications must use the Authorization Code grant flow in order to receive a refresh token. It is recommended that native applications follow best practices for native client applications as outlined in RFC 8252 OAuth 2.0 for Native Apps.
| |
| | |
| = Terms of use =
| |
| :*This section is required for ONC 2015 certification. OpenEMR and the API is open source and licensed under the [https://www.gnu.org/licenses/gpl-3.0.en.html GNU General Public License 3].
| |
| <br>
| |
Latest revision as of 07:43, 16 November 2023
