Cerner FHIR Adapter
Overview
The Cerner FHIR adapter is designed to provide a template for getting started with Cerner FHIR integrations. It leverages the CERNERFHIR Library to authenticate with the Cerner FHIR Server via OAuth2.0 (JWT) and perform various interactions against the Cerner FHIR Server including read and search.
This component can be customized and adapted according to your workflow needs.
Requirements
-
The Base-URL of FHIR Server.
- Oracle has provided a secure-sandbox for testing.
-
The Client ID of your registered Cerner/Oracle Health application.
-
Your private key that is used to sign JWT assertions for authentication.
- Its associated public key must be published in the JSON Web Key Set (JWKS) so Cerner can verify the signature.
-
The Key ID (kid) of the public key mentioned above.
-
List of authorization scopes you want your token to have.
Running the Component
STEP 1: Import the Cerner FHIR Adapter component
Using +COMPONENT, import the Cerner FHIR Adapter component.
STEP 2: Set up the component configurations
Bolded fields are required, otherwise default values defined in config.json are used:
Field | Description | Default Value |
|---|---|---|
Base URL | The base Cerner FHIR endpoint for your tenant. This must match the tenant used when issuing OAuth tokens and should not include resource paths like '/Patient' | |
Client ID | The OAuth client identifier assigned to your Cerner application. This value is used as the client_id and as the iss and sub claims when authenticating with a JWT. | |
Private Key | The PEM-encoded private key used to sign the OAuth client_assertion JWT. The corresponding public key must be registered in Cerner via your JWKS. | |
Key ID | The kid (Key ID) identifying which public key in your JWKS Cerner should use to verify the JWT signature. This value must exactly match a kid published in your JWKS. | |
Scopes | The SMART on FHIR OAuth scopes requested when obtaining an access token. Scopes must be provisioned and enabled for your application and tenant by Cerner. |
|
STEP 3: Start the component and view the default example's result in the component card (if using the Oracle Sandbox)
Keep in-mind that the default code inside the adapter is designed to work with the sample data inside the Oracle-provided secure sandbox.