...
Introduction
This API will submit a new bundle transaction to the CIE Hub. The path will be at the root of API since it can contain multiple different FHIR objects to add, update, or delete.
Authorization
The authorization will contain an API key and also will use an OAuth2 access token. An API key will be provided to each client that intends to consume this API. A development key and also a separate production key will be provided. If this key is not included then an authorization error will be returned.
The process for getting an OAuth2 token can be found here Authorization
| Info |
|---|
Scope Needed For This API CIE SEMI Hub - cie-semi.hub/fhir
|
Rest URL
The following are the URLs for this API. Please note that base url for the region you are looking for can be found here Community Information Exchange Hub Region URL
Environment | URL |
|---|---|
Development | |
UAT | |
Production |
Headers
The following will be headers that will need to be supplied
Header | Description |
|---|---|
x-api-key | This will be a key that will provided by a community information exchange administrator. |
ContentType | application/json |
Authorization | This will be the access token that was retrieved using your client id and secret |
Request
Note that the person ID passed as a parameter in the URL as documented in the REST URL section.
Data Element | Description | Required | ||
|---|---|---|---|---|
Body | ||||
| Procedure Object. The FHIR documentation can be found here https://www.hl7.org/fhir/bundle.html CIE Hub specifics can be found here FHIR Bundle |
| ||
Response
The following will be the response values from the calling of the API. Please note that all responses will also include a instance value which will uniquely identify the specific request that was made. This ensures uniqueness even if the patient was referred to the CIE multiple times.
HTTP Status Code | Description |
|---|---|
201 | Successful Implementation of a transaction bundle.
|
403 | Request is unauthorized and will not be processed. This will happen if the authorization header does not contain a valid client id and secret.
|
400 | Request is malformed and will not be processed.
|
Example CURL for this API Call
The following is an example CURL for calling this api. Also note that there are sample Referral Id’s that are in the CIE Hub development environment that can be used for testing purposes
| Code Block |
|---|
curl -v
--request POST 'https://fhir.{baseCIEURL}.org/'
--header 'x-api-key: aGZoczo4****2ZDk='
--header 'Content-Type: application/json'
--header 'Authorization: bearer etty****iquerui'
--data @BUNDLE_FILE.json \
|