Register at code.cerner.com (now Oracle Health Developer Portal) and create a new application to receive a client_id for the Ignite FHIR sandbox.
Use the Cerner authorization endpoint discovered from the FHIR server's .well-known/smart-configuration for the sandbox environment (e.g., the millennium sandbox base URL).
Follow the standard SMART on FHIR standalone or EHR launch flow using the client_id obtained from the portal; Cerner supports both SMART v1 and v2 flows.
Query the sandbox FHIR R4 base URL with the obtained access token; Cerner's Ignite FHIR R4 endpoint follows standard FHIR R4 conventions with Cerner-specific implementation notes documented in their Millennium FHIR API docs.
Check the Cerner FHIR API documentation for supported resources, search parameters, and any Cerner-specific extensions or identifier systems for the Millennium platform.
Use Cerner's open sandbox patient IDs (documented in their developer portal) for test queries; the open sandbox allows unauthenticated read access to a limited set of synthetic data.
Known gotchas
Cerner/Oracle Health has multiple product lines (Millennium, PowerChart, etc.); ensure you are using the Ignite FHIR API documentation specific to Millennium for R4 support.
Some Cerner FHIR endpoints require a tenant-specific base URL; the generic sandbox URL differs from production URLs which include an organization-specific path segment.
Cerner's open sandbox may lag behind the production API version; test against the authenticated sandbox for full scope of supported operations.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp