This Web site supports the HL7® FHIR® standard with SMART® authorization
Running HIEBus 29.14.0.23531
HIEBus™ WebClient
http://fhir.careevolution.com/Master.Adapter1.WebClient/api/fhir
DSTU2 – documented here, try it here.
HIEBus™ WebClient
http://fhir.careevolution.com/Master.Adapter1.WebClient/api/fhir-cedars
R4 – documented here, try it here.
HIEBus™ WebClient
http://fhir.careevolution.com/Master.Adapter1.WebClient/api/fhir-providers
R4 (provider index) – documented here, try it here.
HIEBus™ WebClient
http://fhir.careevolution.com/Master.Adapter1.WebClient/api/fhir-r4
R4 – documented here, try it here.
HIEBus™ WebClient
http://fhir.careevolution.com/Master.Adapter1.WebClient/api/fhir-stu3
STU3 – documented here, try it here.
All end points require authentication, so first login - either registering yourself or using a Google account:
Once logged in you have access to all data through all FHIR end points ('provider' access).
You can play with the FHIR end points using the built-in test page (see links at the top of this page for each end point):
or get a bearer token here and use it in PostMan, curl or other similar tools (or in your own code).
Register your SMART apps here.The OAuth 2.0 authorization and token URLs can be obtained from the FHIR end points as per the SMART-on-FHIR specifications.
The are same pre-defined patient accounts - ie users linked to a specific patient and that can access only its data (and the data of dependants in some cases). See here.
All end points support the bulk data access protocol
Backend services authentication is supported as well.
For testing there is a pre-registered client ID and certificate; see here for all the details.
More documentation and tutorials can be found here
Release notes for all FHIR API changes can be found here.