ON THIS PAGE

DID THIS PAGE HELP YOU?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Epic on FHIR

Epic on FHIR is an electronic health record platform. You can use Epic on FHIR as a data source when landing or replicating data.

For more information about connecting to SaaS applications, see Connecting to SaaS applications.
For more information about Lite connectors, see Classifications for SaaS application connectors.
Depending on your use case, you might need to install Data Movement gateway to move data from SaaS applications. For more information, see When is Data Movement gateway required?.

Landing tasks:

Replication tasks:

Landing data in a data lake tasks:

To access your Epic on FHIR data, you need to authenticate the connection with your account credentials.

Make sure that the account you use has read access to the tables you want to fetch.

Create, activate, licence, and request an app as described here: App Creation & Request Process Overview.

Make sure that https://connector.qlik.com/auth/oauth/v3.htm is set up to be a valid redirect_uri.
Set up a Client Secret as described here: Provisioning Client Secrets.

Click Authenticate when you have filled in the required connection settings.

You may be asked to log in to the source application.

A window is displayed with an authentication code.
Copy the code to the clipboard and return to the connection dialog.
Paste the code in Complete authentication with the code provided by the source and click Verify.

Tip noteYou may need to scroll down to see this field.

When status is Verified,the authentication is verified.
Provide a name for the connection in Connection name.
Select Open connection metadata to define metadata for the connection when it has been created.

Connection settings
Setting	Description
Data gateway	Select a Data Movement gateway if required by your use case. Information note This field is not available with the Qlik Talend Cloud Starter subscription, as it does not support Data Movement gateway. If you have another subscription tier and do not want to use Data Movement gateway, select None. For information on the benefits of Data Movement gateway and use cases that require it, see Qlik Data Gateway - Data Movement.
Client Id	Client ID for Epic on FHIR OAuth authentication.
Client Secret	Client secret for Epic on FHIR OAuth authentication.
Auth Base URI	Auth Base URI. Example: If the Authorize URL is https://fhir.epic.com/interconnect-fhir-oauth/oauth2/authorize, the Auth Base URI would be https://fhir.epic.com/interconnect-fhir-oauth. For more information, see Standalone Launch.
Auth Audience	'aud' (audience) parameter as described in Standalone Launch.
FHIR DSTU2 endpoint	Your FHIR DSTU2 endpoint as listed in the section 'FHIR DSTU2 Endpoints' in open.epic Endpoints.
FHIR R4 Endpoint	Your FHIR R4 endpoint as listed in the section 'FHIR R4 Endpoints' open.epic Endpoints.
FHIR STU3 Endpoint	FHIR STU3 endpoint similar to the DSTU2 and R4 endpoints.
Patient List Identifier	Patient list identifier to be used, as described under 'identifier (String)' in List.Search (Patient List) (STU3) Example: systemlist\|6442

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!