HealthSparq FHIR API
App Developer Introduction to HealthSparq FHIR API
CHRISTUS Health Plan has contracted with HealthSparq to manage and support FHIR Provider Directory API. In order for your application (APP) to use the FHIR Provider Directory API, please read the following instructions.
API Documentation: OpenAPI Definition
Accessing the FHIR Provider Directory API
No authentication is required because this is a public token. This is a deviation from the JOT methodology because we don’t use a client and secret; it's simply passing a public token request. This gets passed as a "Subject-Token" in the header of your request and not as a "Bearer_Token".
Public Token URL
https://christushealthplan.healthsparq.com/api/healthsparq-public-login-service/v1/token
Base FHIR Provider Directory URL
https://christushealthplan.healthsparq.com/api/provider-fhir-service
Insured code: CHRISTUS_I
Brand code: CHRISTUS
Using a Public Token to Authenticate
The Provider Directory API hosted by HealthSparq is protected by public authentication tokens. Any party that needs to query the API must first retrieve a token from HealthSparq’s public login service.
curl --location --request POST 'https://christushealthplan.healthsparq.com/api/healthsparq-public-login-service/v1/token' \
--header 'Content-Type: application/json' \
--data-raw '{
"city":"",
"state":"",
"postalCode":"",
"country":"", "insurerCode":"CHRISTUS_I", "brandCode":"CHRISTUS", "alphaPrefix":"", "bcbsaProductId":"", "productCode":""
}'
The subject-token generated is to then be passed in the header of subsequent calls to the FHIR Provider Directory API itself. Each public token expires after 15 minutes. Third party developers are expected to request new public tokens if needed after that period of time, which is a common public API practice.
Token Call Required Header:
--header 'Content-Type: application/json' \
FHIR Provider Call Required Headers:
--header 'Accept: application/json' \ --header 'Content-Type: application/json' \ --header 'Subject-Token: