FHIR Application Provisioning

Note: This page contains links to Cerner Wiki Reference Pages that require a CernerCare account to access. If you do not already have an account, see Create My Cerner Profile for information on how to register.

Overview

This page describes the Oracle Health customer (health system) self-service provisioning and mapping process for FHIR applications in a customer environment.

When a developer creates an application in code Console, they are creating an application against the production cloud environment that is associated with a production-level internal Millennium environment.

Note: This application can connect to a customer’s production environment.

If a customer requires support for implementing an application, they can contact Oracle Health to request a contract for a custom scope. If the developer is part of Oracle PartnerNetwork (OPN) and has obtained expertise for FHIR in the Healthcare Track, they can submit a sales request to Oracle Health.

Self-service provisioning does not apply to CommunityWorks, PowerWorks, or Continuum customers (shared domain customers) unless it fits within the Minimum Viable Strategy (MVS). Have the customer reach out to their Oracle Cerner representative to explore this option.

Each service request (SR) listed below must be a separate SR. Do not combine any SR topics.

You can post development questions to the Oracle Health Developer Forums.

Customers can log SRs for issues to the solution of Cerner Ignite APIs for Millennium. If they are logging an SR for the first time, they can select I can’t find my solution. The available solutions are displayed and the customer can search for Cerner Ignite APIs for Millennium.

Prerequisites

The developer must already have an application created in a production environment through code Console.

RHO Customers

RHO Nonproduction

The following process applies to remote-hosted option (RHO) customers requesting application provisioning in a nonproduction environment:

  1. The customer requests a tenant ID for the domain from Oracle Health Hosting.

  2. The developer provides a nonproduction (sandbox) application ID and client ID to the customer. If the developer does not have a nonproduction application ID and client ID, complete the following steps:

    1. The developer who owns the application ensures that they have a nonproduction CernerCare account. See Create Account to create a CernerCare account.
    2. The developer provides the production client ID, application ID, and application name to the customer, which are found in code Console.
    3. The customer logs an SR to the solution of Cerner Ignite APIs for Millennium to request transferring the application ID and client ID to the sandbox authorization server.

  3. The customer logs an SR to Cerner Ignite APIs for Millennium for provisioning.

    • Ask for the application ID and customer ID to be provisioned against the tenant ID.

  4. The customer logs an SR to Cerner Ignite APIs for Millennium for any codable concepts that the developer might use.

    • Include DataWorks_FHIR_PopHlth in the description and ask for specific codable concepts that need to be mapped. The developer provides this information.

  5. If applicable, the developer provides any external website dependencies to the customer for adding to the trusted sites on Citrix.

    • Customers should work with their Oracle Hosting contacts for this step.

  6. If applicable, the customer completes the SMART application setup. See Configure SMART Applications to Run in PowerChart or FirstNet on Cerner Wiki for more information.

  7. The following root URL is used for the FHIR sandbox environment:

    https://fhir-ehr.sandboxcerner.com/r4/<tenant ID/

RHO Production

The following process applies to RHO customers requesting application provisioning in a production environment:

  1. The customer requests a tenant ID for the domain from Oracle Health Hosting.

  2. The developer provides a production application ID and client ID to the customer.

  3. The customer logs an SR to Cerner Ignite APIs for Millennium for provisioning.

    • Ask for the application ID and client ID to be provisioned against the tenant ID.
    • Request the FHIR URL.
    • If applicable, the customer completes a Process for Executing Client Approval (PECA) form.

  4. If applicable, the developer provides any external website dependencies to the customer for adding to the trusted sites on Citrix.

    • Customers should work with their Oracle Hosting contacts for this step.

  5. If applicable, the customer completes the SMART application setup. See Configure SMART Applications to Run in PowerChart or FirstNet on Cerner Wiki for more information.

  6. The following root URL is used for the FHIR production environment:

    https://fhir-ehr.cerner.com/r4/<tenant ID/

CHO Customers

CHO Nonproduction

The following process applies to customer-hosted option (CHO) customers requesting application provisioning in a nonproduction environment:

  1. The customer finds their tenant ID in Cerner Central. The domain owners have access to the tenant for the domain.

  2. The developer provides a nonproduction (sandbox) application ID and client ID to the customer. If the developer does not have a nonproduction application ID and client ID, complete the following steps:

    1. The developer who owns the application ensures that they have a nonproduction CernerCare account. See Create Account to create a CernerCare account.
    2. The developer provides the production client ID, application ID, and application name to the customer.
    3. The customer logs an SR to the solution of Cerner Ignite APIs for Millennium to request transferring the application ID and client ID to the sandbox authorization server.

  3. The customer logs an SR to Cerner Ignite APIs for Millennium for provisioning.

    • Ask for the application ID and client ID to be provisioned against the tenant ID.

  4. The customer logs an SR to Cerner Ignite APIs for Millennium for any codable concepts that the developer might use.

    • Include DataWorks_FHIR_PopHlth in the description and ask for specific codable concepts that need to be mapped. The developer provides this information.

  5. If applicable, the developer provides any external website dependencies to the customer for adding to the trusted sites on Citrix.

  6. If applicable, the customer completes the SMART application setup. See Configure SMART Applications to Run in PowerChart or FirstNet on Cerner Wiki for more information.

  7. The following root URL is used for the FHIR sandbox environment:

    https://fhir-ehr.sandboxcerner.com/r4/<tenant ID/

CHO Production

The following process applies to customer-hosted option (CHO) customers requesting application provisioning in a production environment:

  1. The customer finds their tenant ID in Cerner Central. The domain owners have access to the tenant for the domain.

  2. The developer provides a production application ID and client ID to the customer.

  3. The customer logs an SR to Cerner Ignite APIs for Millennium for provisioning.

    • Ask for the application ID and client ID to be provisioned against the tenant ID.
    • If applicable, the customer completes a PECA form.

  4. If applicable, the customer completes the SMART application setup. See Configure SMART Applications to Run in PowerChart or FirstNet on Cerner Wiki for more information.

  5. The following root URL is used for the FHIR production environment:

    https://fhir-ehr.cerner.com/r4/<tenant ID>/

Global Customers

Global Nonproduction

The following process applies to global customers requesting application provisioning in a nonproduction environment:

  1. The customer requests a tenant ID for the domain from Oracle Health Hosting.
  2. The developer provides a nonproduction (sandbox) application ID and client ID to the customer. If the developer does not have a nonproduction application ID and client ID for the customer’s cloud region, complete the following steps:
    1. The developer creates a nonproduction or sandbox instance of their application in code Console.
    2. The developer provides the nonproduction client ID, application ID, and application name to the customer, which are found in code Console.
  3. The customer logs an SR to Cerner Ignite APIs for Millennium to request transferring the application ID and client ID to the customer’s cloud region.
  4. The customer logs an SR to Cerner Ignite APIs for Millennium for provisioning.
    • Ask for the application ID and client ID to be provisioned against the tenant ID.
  5. The customer logs an SR to Cerner Ignite APIs for Millennium for any codable concepts that the developer might use.
    • Include DataWorks_FHIR_PopHlthin the description and ask for specific codable concepts that need to be mapped. The developer provides this information.
  6. If applicable, the developer provides any external website dependencies to the customer for adding to the trusted sites on Citrix.
    • Customers should work with their Oracle Hosting contacts for this step.
  7. If applicable, the customer completes the SMART application setup. See Configure SMART Applications to Run in PowerChart or FirstNet on Cerner Wiki for more information.

Global Production

The following process applies to global customers requesting application provisioning in a production environment:

  1. The customer requests a tenant ID for the domain from Oracle Health Hosting.
  2. The developer provides a production application ID and client ID to the customer that is in the customer’s cloud region.
  3. The customer logs an SR to Cerner Ignite APIs for Millennium for provisioning.
    • Ask for the application ID and client ID to be provisioned against the tenant ID.
    • If applicable, the customer completes a PECA form.
  4. If applicable, the developer provides any external website dependencies to the customer for adding to the trusted sites on Citrix.
    • Customers should work with their Oracle Hosting contacts for this step.
  5. If applicable, the customer completes the SMART application setup. See Configure SMART Applications to Run in PowerChart or FirstNet on Cerner Wiki for more information.

Region-Specific Systems

The following regions override the format above with a region-specific system:

Additional Resources

Cerner Wiki

Oracle Health Community

Making Self-Developed SMART Apps Available in Your Domain in the Ignite APIs Community group

Oracle Help Center

Oracle Health Millennium Platform

Oracle.com