Oracle Health Multi-Tenant Domains

Overview

Multi-tenant domains in Oracle Health are a collection of several shared environment domains that vary in customer type. Oracle provides API and SMART launch integration to support those customers.

If your application performs API write transactions or is an embedded SMART launch, you must complete Oracle Validated Integration (OVI) through the Oracle PartnerNetwork (OPN) Healthcare track. See the OPN Healthcare track journey for more information on the process.

For the full list of OVI application requirements, see Oracle Validated Integration Expertise Application Requirements for Oracle Health. An Oracle.com account is required to view this page. If you do not already have an account, see the Oracle Partner Hub for information on how to register.

Note: The default browser for SMART launch in a multi-tenant domain is Microsoft Edge.

Supported Customer Domains

The following customer domains are supported:

Ambulatory ASP: Supports physician practices of all sizes across more than 55 specialties. The Ambulatory Application Service Provider (ASP) model provides customers with ongoing solution support, updates, and maintenance.
CommunityWorks: Provides a complete package of integrated solutions for community and critical access organizations across the U.S.
Population Health: Provides big data solutions to assist with managing a population’s health through predictive and trending analysis. This domain provides Oracle Health Care Management, Consumer Well-being, and Identity Provider as a Service (IdPaaS) solutions for customers without an Oracle Health Millennium Platform footprint.
Continuum: Supports long-term care, and behavioral health and rehabilitation venues.

API and SMART Launch Integration

API integration in a multi-tenant domain follows a unique process. Compared to customer- or remote-hosted single-tenant domains, API transaction limitations do not apply to multi-tenant domains; however, multi-tenant domains require a more rigorous validation process. This validation ensures that other customer experiences in the domains are not affected. The API infrastructure is shared at the parent domain level, but each individual customer has their own cloud tenant ID to keep data and transactions separate.

Multi-tenant customers typically do not have access through their own site to the data points that you may need to fully integrate your application. System code values necessary to make transactions may require resources from Oracle, which you can request through OPN to complete the integration.

You can use a minimum viable strategy (MVS) process or OPN for API transaction access and SMART launch integration.

MVS Process

The MVS process may be appropriate for applications that only require the read capability of USCDI FHIR R4 APIs. If you can successfully integrate the application without guidance or support from Oracle, customers or vendors can follow the MVS process to work toward production API access. This process is an alternative to the OPN validation process; however, if integration services are required for delivery, you must follow the OPN process.

The MVS process has the following requirements:

Customers must contact their account executive to start this integration.
Customers must complete an MVS onboarding document.
A successful demonstration must be completed in a nonproduction environment.
A monitoring period is required to review API transactions and ensure that they are appropriate for the use case and traffic volume does not overburden the domain.

Note: If you want to integrate a SMART launch or any APIs that require customer configuration, the MVS process is not an appropriate method.

Title and Copyright Information

Oracle Health Multi-Tenant Domains

G11840-01

July 2024

Primary Author: Oracle Corporation