Use the Oracle Health (Cerner) FHIR R4 API to query US Core-compliant resources with Cerner-specific search parameter requirements and handle Cerner's pagination and authentication patterns
Register an application in the Cerner Code Developer Experience portal and configure the SMART on FHIR scopes required for the target resources, noting that Cerner requires explicit per-resource scope approval during app registration
Authenticate using SMART standalone or EHR launch flow against the Cerner SMART authorization server, using the Cerner-provided FHIR base URL for the target tenant or the open sandbox endpoint for development
Query resources using Cerner-documented required search parameters — Cerner enforces specific combinations of search parameters and returns 400 errors for unsupported parameter combinations, unlike permissive servers that ignore unknown parameters
Handle Cerner's pagination by following the Bundle.link[rel=next] URL, noting that Cerner encodes pagination tokens in the next URL rather than using offset or page parameters
Interpret Cerner-specific response extensions and resource constraints: some fields present in the US Core profile may be absent or modeled differently in Cerner, requiring mapping logic that differs from Epic integrations
Known gotchas
Cerner's FHIR API enforces required search parameter combinations that differ from the base FHIR specification and US Core; a search that works on a reference FHIR server may return 400 on Cerner if mandatory parameters are missing
Cerner uses separate FHIR base URLs per tenant; there is no single multi-tenant endpoint, and production tenant URLs must be obtained through the Cerner App Market process rather than self-configuration
Cerner open sandbox data is reset periodically and does not reflect real patient data patterns; integration testing against a real Cerner tenant in a staging environment is essential before production deployment
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