Terms of Service Application access patient selection – g(7)
Elixir APIs enable healthcare organizations to seamlessly connect with their FHIR API’s and All Data Request, ensuring compliance with the Cures Act requirements and beyond.
POSTToken generation{EHR Instance}/ services/ oauth2/ token
Parameters
grant_type: client_credentialsclient_id: Enter the client Idclient_secret: enter the client secret key
Response
{
"access_token": "String",
"signature": "String",
"instance_url": "https://{salesforce_Instance}",
"id": "String",
"token_type": "String",
"issued_at": "String"
}Use the access_token generated for the successive HTTP requests
Application Access Patient Selection: FHIR APIs
GETFetch Patient Info{EHR Instance}/ services/ apexrest/ fhir/ Patient/ {Id}
Parameters
accountId= {}
Response
{
"resourceType": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}GETFetch Encounter Info{EHR Instance}/ services/ apexrest/ fhir/ Encounter/ {Id}
Parameters
visitId={}
Response
{
"resourceType": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}GETFetch Practitioner Info{EHR Instance}/ services/ apexrest/ fhir/ Practitioner/ {Id}
Parameters
visitId={}
Response
{
"resourceType": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}GETFetch Appointment Info{EHR Instance}/ services/ apexrest/ fhir/ Appointment/ {Id}
Parameters
visitId={}
Response
{
"resourceType": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}GETFetch Allergy Info{EHR Instance}/ services/ apexrest/ fhir/ Allergy/ {Id}
Parameters
allergyId={}
Response
{
"resourceType": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}GETFetch Diagnosis Info{EHR Instance}/ services/ apexrest/ fhir/ Diagnosis/ {Id}
Parameters
diagnosisId={}
Response
{
"resourceType": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}GETFetch Condition Info{EHR Instance}/ services/ apexrest/ fhir/ Condition/ {Id}
Parameters
problemId={}
Response
{
"resourceType": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}GETFetch Coverage Info{EHR Instance}/ services/ apexrest/ fhir/ Claim/ {Id}
Parameters
insuranceId={}
Response
{
"resourceType": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}GETFetch Organization Info{EHR Instance}/ services/ apexrest/ fhir/ Organization/ {Id}
Parameters
organizationId={}
Response
{
"resourceType": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}GETFetch Procedure Info{EHR Instance}/ services/ apexrest/ fhir/ Procedure/ {Id}
Parameters
procedureId={}
Response
{
"resourceType": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}GETFetch DiagnosticReport Info{EHR Instance}/ services/ apexrest/ fhir/ DiagnosticReport/ {Id}
Parameters
laborderId={}
Response
{
"resourceType": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}GETFetch Medication Info{EHR Instance}/ services/ apexrest/ fhir/ Medication/ {Id}
Parameters
medicationId={}
Response
{
"resourceType": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}GETFetch Location Info{EHR Instance}/ services/ apexrest/ fhir/ Location/ {Id}
Parameters
locationId={}
Response
{
"resourceType": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}GETFetch CareTeam Info{EHR Instance}/ services/ apexrest/ fhir/ CareTeam/ {Id}
Parameters
careteamId={}
Response
{
"resourceType": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}All Data Request: CCDA
Overview: The C-CDA API returns a Continuity of Care Document (CCD) formatted in accordance with the C-CDA API version 2.1 specification.
GETFetch Patient Info{EHR Instance}/ services/ apexrest/ ccda
Body
{
"CDAType": "Consolidated CDA",
"strAccountId": "String"
}Terms and Conditions
By accessing the Elixir API, users agree to the following terms
- Data must be accessed responsibly and comply with all HIPAA regulations.
- Access is restricted to authorized users and permitted applications.
- The API is subject to maintenance; downtime may occur during scheduled updates.
Error Handling and Conditions
Error - Request with a invalid query parameter
Response message
{
"resourceType": "OperationOutcome",
"issue": [
{
"code": "invalid",
"details": { "text": "Not found" },
"severity": "error"
}
]
}Error - Absent or invalid auth token
Response message
{
"resourceType": "OperationOutcome",
"issue": [
{
"code": "invalid",
"details": { "text": "Not found" },
"severity": "error"
}
]
}Error - Request from the client not have permissions to make
Response message
{
"resourceType": "OperationOutcome",
"issue": [
{
"code": "invalid",
"details": { "text": "Not found" },
"severity": "error"
}
]
}Error Handling and Exceptions
Error responses follow HTTP status codes. Common errors include:
- 404 Not Found: Resource with specified Id does not exist.
- 401 Unauthorized: Invalid API key or credentials.
- 500 Internal Server Error: General error on the server; try again later.
Each error returns a JSON object with an errorCode and message field for troubleshooting.
Software Requirements
To interact with the API, the following configurations are required
- HTTP Client Library: For sending RESTful requests.
- OAuth 2.0 or API Key authentication setup for access.
- JSON Parsing Library: For handling responses in JSON format.
Get Started
Talk to an Elixir Integration Advisor
Tell us what you're integrating and which systems are involved. An integration advisor will follow up within one business day.
- A specialist follows up within one business day
- A no-obligation conversation about your specific goals
- Answers from someone who actually works in this space
- Your information stays confidential