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 Herstellung einer Verbindung zu SaaS-Anwendungen.
For more information about Lite connectors, see Klassifizierungen für SaaS-Anwendungskonnektoren.
Depending on your use case, you might need to install Data Movement Gateway to move data from SaaS applications. For more information, see Wann ist Data Movement Gateway erforderlich?.

Supported update methods

For more information, see Eine Übersicht über Zielaktualisierungsmethoden.

Landing tasks:

Reload and compare

Replication tasks:

Full load

Landing data in a data lake tasks:

Reload

Preparing for authentication

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.

Creating the connection

For more information, see Herstellung einer Verbindung zu SaaS-Anwendungen.

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.

TipphinweisYou 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	Wählen Sie ein Data Movement Gateway aus, wenn dies für Ihren Anwendungsfall erforderlich ist. Informationshinweis Dieses Feld ist für das Qlik Talend Cloud Starter-Abonnement nicht verfügbar, da dieses Abonnement Data Movement Gateway nicht unterstützt. Wenn Sie eine andere Abonnementstufe haben und Data Movement Gateway nicht verwenden möchten, wählen Sie Keine. Weitere Informationen zu den Vorteilen von Data Movement Gateway und den Anwendungsfällen, in denen es erforderlich ist, finden Sie unter 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

Hat diese Seite Ihnen geholfen?

Wenn Sie Probleme mit dieser Seite oder ihren Inhalten feststellen – einen Tippfehler, einen fehlenden Schritt oder einen technischen Fehler –, teilen Sie uns bitte mit, wie wir uns verbessern können!

Geben Sie hier Ihr Feedback ab