Innowell API Introduction
The Innowell platform uses a REST interface based on the FHIR R4 standard. The interface allows you, with the help of you systems integration team, to connect your PMS or EMR to the Innowell platform.
Getting started
Here you will find simple examples of how to get started using the Innowell FHIR integration.
You don't need to know FHIR, but it will help. You will need familiarity with calling APIs using REST.
The Innowell FHIR interface does not implement the entire FHIR specification. It only contains resources relevant to the Innowell platform.
What you'll need
The following will be required before you can start using the FHIR integration:
- Integration endpoint URL (supplied by Innowell)
- API Key for a Sandbox environment (supplied by Innowell)
- EMR ID for your EMR/PMS system (supplied by Innowell)
- Tenant ID(s) for each Innowell tenant you own (supplied by Innowell)
- A tool such as curl or postman to test and debug
- Your own way to connect to the API using an integration platform (e.g. MusleSoft, Azure Logic Apps, Boomi, Zapier) or framework in the language of your choice (e.g. NodeJs, .NET, Ruby, Java)
We will use curl to provide examples of how to access the API.
Sandbox testing
A Sandbox provides an isolated environment, enabling you to safely test the implementation of your integration with minimal risk to your data.
You should NEVER put real data into a Sandbox. Only use test data and never real patient information.
The FHIR interface supports the following actions:
- create patient, update patient, get patient
- create practitioner, update practitioner, get practitioner
- create careteam, update careteam, get careteam
- get observation
Download complete integration documentation (PDF)
Ready for production
Once your integration is tested and working, contact Innowell API Support to discuss moving to production.
You will need a production integration URL, API Key and Tenant ID(s) which will be different from your Sandbox ones.
Something missing?
If something is missing in the documentation or if you found some part confusing, please us suggestions by emailing API Support.