HDIM + Oracle Health (Cerner)

HDIM connects to Oracle Health through the Cerner Millennium FHIR Server. Data flows through the HDIM microservice pipeline for quality measure evaluation, with CDS Hooks enabling real-time care gap alerts back into Millennium workflows.

┌──────────────────────────────────────────────────────────────────┐
│                   Oracle Health (Cerner Millennium)              │
│  ┌────────────────┐  ┌──────────────────┐  ┌─────────────────┐  │
│  │ Millennium EHR │  │ Cerner FHIR      │  │ CDS Hooks       │  │
│  │ (Clinical      │→ │ Server (R4)      │  │ Service         │  │
│  │  Workflows)    │  │ /r4 endpoint     │  │ (Hook triggers) │  │
│  └────────────────┘  └────────┬─────────┘  └────────▲────────┘  │
│                               │ FHIR R4 REST API     │ CDS Cards │
└───────────────────────────────┼──────────────────────┼───────────┘
                                │                      │
                                ▼                      │
┌────────────────────────────────────────────────────────────────────┐
│                            HDIM Platform                           │
│                                                                    │
│  ┌──────────┐   ┌──────────────┐   ┌──────────┐   ┌────────────┐  │
│  │ FHIR     │ → │ Patient      │ → │ CQL      │ → │ Care Gap   │  │
│  │ Service  │   │ Service      │   │ Engine   │   │ Service    │  │
│  │ (8085)   │   │ (8084)       │   │ (8081)   │   │ (8086)     │  │
│  └──────────┘   └──────────────┘   └──────────┘   └─────┬──────┘  │
│       ▲                                                  │         │
│       │                  ┌──────────────────┐            ▼         │
│       └──────────────────│ Quality Measure  │← Quality Reports &  │
│                          │ Service (8087)   │  CDS Hook Payloads  │
│                          └──────────────────┘                      │
└────────────────────────────────────────────────────────────────────┘

Follow these six steps to connect HDIM with your Oracle Health Millennium deployment.

1. 1
   Register in Cerner Code Console — Create a developer account at code.cerner.com and register a new application. Submit for SMART on FHIR authorization and request the required FHIR resource scopes (patient/Patient.read, patient/Observation.read, patient/Condition.read, and others matching your HEDIS measures). For production use, complete the Cerner App Submission process to enable access to live patient data.
2. 2
   Configure OAuth2 client credentials — Obtain your client_id and client_secret from the Cerner Code Console. HDIM uses the SMART on FHIR Backend Services authorization flow (RFC 7523 JWT bearer token) for system-level access. Set CERNER_CLIENT_ID and CERNER_CLIENT_SECRET in your HDIM environment configuration. The token endpoint is https://authorization.cerner.com/tenants/{tenant-id}/protocols/oauth2/profiles/smart-v1/token.
3. 3
   Set up Millennium FHIR R4 endpoint — Configure FHIR_SERVER_URL to point to your organization's Millennium FHIR R4 endpoint in the format https://fhir-ehr.cerner.com/r4/{tenant-id}. For on-premises Millennium deployments, the endpoint follows the pattern https://{millennium-host}/fhir/r4. Verify connectivity using the FHIR capability statement: GET {FHIR_SERVER_URL}/metadata.
4. 4
   Configure Bulk FHIR export — Enable Bulk FHIR export for population-level quality measurement. Set FHIR_BULK_EXPORT_ENABLED=true and configure the polling interval. Bulk export allows HDIM to evaluate HEDIS measures across your entire patient panel without individual FHIR queries.
5. 5
   Deploy HDIM on your infrastructure — Deploy HDIM on your RHEL servers or cloud VPC using Docker Compose or Kubernetes. Set spring.profiles.active=production and FHIR_SERVICE_URL to your Millennium FHIR R4 endpoint. HDIM connects over your private network — PHI never leaves your infrastructure.
6. 6
   Verify integration — Run the built-in verification suite to confirm end-to-end connectivity. Check FHIR connectivity via the health endpoint, verify OAuth2 token acquisition, confirm FHIR resource retrieval (Patient, Encounter, Condition, Observation), and validate CQL measure evaluation and care gap detection against your Millennium data.

HDIM deploys on your infrastructure and connects to your Millennium FHIR endpoint directly. Configure these Spring Boot properties for each deployment.

# Configuration reference — actual property names may vary by release

# Active profile
spring.profiles.active=production

# Cerner Millennium FHIR R4 endpoint (on your network)
# Cloud-hosted Millennium:
FHIR_SERVICE_URL=https://fhir-ehr.cerner.com/r4/<your-millennium-tenant-id>
# On-premises Millennium:
# FHIR_SERVICE_URL=https://<millennium-host>/fhir/r4

# OAuth2 SMART on FHIR (Backend Services)
FHIR_AUTH_TYPE=oauth2
FHIR_CLIENT_ID=<your-cerner-code-client-id>
FHIR_CLIENT_SECRET=<your-cerner-code-client-secret>
FHIR_TOKEN_URL=https://authorization.cerner.com/tenants/<your-tenant-id>/protocols/oauth2/profiles/smart-v1/token

# Bulk FHIR Export for population-level evaluation
FHIR_BULK_EXPORT_ENABLED=true
FHIR_BULK_EXPORT_POLL_INTERVAL=30

# Connection tuning (adjust for your Millennium capacity)
FHIR_CONNECTION_POOL_SIZE=20
KAFKA_PARTITIONS=12
PATIENT_BATCH_SIZE=1000

HDIM supports multiple data exchange protocols with Oracle Health Millennium.