Oracle Health (Cerner) MCP Server & Agent Skill

What is the Oracle Health (Cerner) API, and what can an agent read from it?

FHIR R4 (4.0.1) REST APIs over about 35 resource types, including Patient, Encounter, Observation, MedicationRequest, DocumentReference, Appointment, Coverage and ChargeItem, with read, search and selected create, update and patch.

• API: FHIR R4 APIs for Oracle Health Millennium Platform (FHIR R4)
• Access: Issued by your administrator
• Base URL: https://fhir-ehr-code.cerner.com/r4/{tenant-id} (secure) and https://fhir-open.cerner.com/r4/{tenant-id} (open, no auth), as shown in the R4 overview
• Authentication: SMART EHR launch (OAuth 2.0 authorization code); SMART standalone launch (OAuth 2.0 authorization code); SMART Backend Services (client credentials)

Developers register applications in Oracle Health's code Console. A System or Confidential app receives a system account (client ID and secret) managed in Cerner Central System Account Management.

System accounts authenticate with Basic client_id:secret or a signed JWT (RS384 or ES384, JWKS registered in Cerner Central). Scopes use SMART v1 or v2 syntax, e.g. system/Patient.read. Wildcard scopes are not supported.

What can an agent read from Oracle Health (Cerner)?

• Patients — Patient read and search on the R4 endpoint.
• Encounters — Encounter read and search.
• Results and vitals — Observation and DiagnosticReport read and search.
• Medications — MedicationRequest, MedicationAdministration and MedicationDispense read and search.
• Documents — DocumentReference and Binary read.
• Schedule — Appointment and Slot read and search.

What can an agent write to Oracle Health (Cerner)?

• Appointments — Appointment create and patch (book or change a visit). Confirm with the user first.
• Clinical documents — DocumentReference create and update files a document into the chart. Confirm with the user first.
• Observations — Observation create and update.
• Problems and allergies — Condition and AllergyIntolerance create and update.
• Charges — ChargeItem create posts a charge for billing. Confirm with the user first.

Limits: Results page through Bundle links (self, next, previous); follow the given URLs and do not build your own. De-duplicate by resource ID across pages. Access tokens last 570 seconds by default.

Records are HIPAA protected health information (PHI). Scopes must be requested one by one; system accounts read data without a user present, so limit them to what the task needs.

How do I connect Oracle Health (Cerner) to an AI agent over MCP?

As of October 2026 we found no MCP server published by Oracle Health itself.

The practical path is to host a small MCP server that wraps the FHIR R4 APIs for Oracle Health Millennium Platform, or to give the agent the calls directly with the SKILL.md below.

On ibl.ai an MCP connection is three records, and a working integration always needs all three:

1. Register the server — POST …/mcp-servers/ with its URL, a transport (sse, websocket or streamable_http) and an auth_type of none, token or oauth2.
2. Create a connection that holds the credential, scoped to the whole organization (platform), to a single agent, or to each user (user).
3. Enable it on the agent — mcp-tool in tool_slugs and the server id in mcp_servers. Both lists are replaced, not merged, so read the settings first.

Oracle Health (Cerner) supports per-user OAuth, so the server can use auth_type=oauth2 with auth_scope=user: each person connects their own Oracle Health (Cerner) account in the chat the first time the agent needs it.

The field reference is in MCP server connections, and the /iblai-api-agent-mcp skill runs all three steps from a coding agent.

What does the Oracle Health (Cerner) agent skill do?

The Oracle Health (Cerner) skill is one SKILL.md file named iblai-connect-oracle-health-cerner. It gives an agent the auth conventions, what to read, which writes need a person's confirmation, the ibl.ai MCP wiring, example prompts and guardrails.

Download the Oracle Health (Cerner) SKILL.md

Save it as .claude/skills/iblai-connect-oracle-health-cerner/SKILL.md, or in your agent's skills folder. The ibl.ai platform skills it calls come from one install:

This connector skill is a starting point maintained on ibl.ai, not part of the iblai/vibe repository.

It was checked against Oracle Health's documentation on October 20, 2026. Test it against your own Oracle Health (Cerner) setup before you rely on it.

What can I ask an Oracle Health (Cerner) agent to do?

• “Find today's inpatient encounters for patient 12724066 and list active conditions.”
• “Show the most recent vital signs recorded for this patient.”
• “List open appointment slots in cardiology next week.”
• “Summarize the discharge documents filed for this encounter.”

How do I run an Oracle Health (Cerner) agent on ibl.ai?

Agentic OS is where the agent runs on ibl.ai: it holds the Oracle Health (Cerner) MCP connection, the model the agent uses, its instructions and its conversation history.

On ibl.ai you own all the code and the data, run it model-agnostic across any LLM, and pay with no per-seat pricing — so you can deploy anywhere, from your own cloud to a fully air-gapped network.

• AI agents for Healthcare — what ibl.ai deploys in this sector

Which ibl.ai agents work with Oracle Health (Cerner) data?

• Clinical Support — Healthcare
• Care Coordination — Healthcare
• Documentation — Healthcare

Which ibl.ai platform skills does an Oracle Health (Cerner) agent use?

• /iblai-api-agent-mcp — MCP connectors for ibl.ai agents, end to end
• /iblai-vibe-agent-mcp — Add the agent MCP tab (Model Context Protocol connector management with featured connectors, custom connectors, OAuth,…
• /iblai-api-agent-tool — Enable or disable an ibl.ai agent's tools via the platform API

What else should I know before connecting Oracle Health (Cerner) to an AI agent?

Which other data sources can an AI agent connect to alongside Oracle Health (Cerner)?

Which other Healthcare systems have a connector?

• athenahealth — Cloud EHR and practice management
• Availity — Payer-provider health information network
• Epic — Electronic health record (EHR)
• HL7 FHIR — Healthcare data exchange standard
• MEDITECH Expanse — Electronic health record (EHR)
• Veradigm — Electronic health record (EHR)

Every connector, grouped by sector, is on the connectors hub.