Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Need help? Contact us:

...

 

 

The AthenaHealth adapter is designed to provide a template for getting started with Epic FHIR Athenahealth API integrations, including:

  1. Authenticating with the Epic FHIR Athenahealth API Server via OAuth2.0 using the OAUTH Library.

  2. Generating FHIR Resources using the FHIR Library.

  3. Performing various interactions against the Epic FHIR Server including create, read, search, and extended $operations.Demo AthenaOne APIs Integration: saerchPatient and createPatient

  4. Demo FHIR APIs Integration: searchPatientsFhir

This component can be customized and adapted according to your workflow needs.

...

Expand
titleSTEP 3: Configure the ClientId and PrivateKey custom fields and click Edit to open the Translator

Enter the ClientId and PrivateKey certificate path.

Using the information provided, the component will run through the authentication workflow and set the Key and KeyExpiry value of the obtained access token automatically.

How the EPICFHIR Library works:

Expand
titleEPICFHIRclient - sets up the adapter framework

Sets up the EPIC FHIR adapter framework, adding the various method modules to a metatable and storing the configurations added to the custom fields.

Expand
titleEPICFHIRauth - authenticates with the Epic FHIR Server

The EPICFHIRauth function, builds and makes the HTTP POST token request to obtain the access token required for any resource requests against the FHIR Server.

A separate CreateJWT function creates the JSON Header and Payload components of the JWT and calls the OAUTH Library to sign and return the JWT required for the token request.

If the token requests is successful (HTTP 200 response), the token and token expiry returned are set to the Key and KeyExpiry custom fields respectively.

Expand
titleEPICFHIRcustom - makes API requests and returns the response

EPICcustom takes in any API requests and parameters to make the API call and return the response.

  • First the function checks if the token Key exists and performs the OAuth2.0 authentication workflow to obtain the token to be used in subsequent requests.

  • Uses the passed configurations API request parameters - the method (ex. post), API (ex. Patient) and parameters for the call (ex. the patient resource to be created) - to build and carry out the appropriate HTTP request.

  • For resiliency, the Retry Library is used to retry any failed attempts and the response is handled and returned.