How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Oracle Health (Cerner)

Cerner (Oracle Health) Encounter API

Patient encounter records.

Documentation Provider Profile APIs.io OpenAPI GitHub

Cerner (Oracle Health) Encounter API is one of 54 APIs that Oracle Health (Cerner) publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Encounter. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 4 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 5 base URLs: https://fhir-ehr.cerner.com/r4, https://fhir-open.cerner.com/r4, https://fhir-ehr-code.cerner.com/r4/{tenant}, https://fhir-myrecord.cerner.com/r4/{tenant}, https://fhir-open.cerner.com/r4/{tenant}.

4 operations 2 paths 5 schemas 2 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://fhir-ehr.cerner.com/r4/{tenant}
Authentication
OAuth 2.0, OAuth 2.0
Contact
Oracle Health Developer Program
Resource Areas
1

Authentication & Security 2

Cerner (Oracle Health) Encounter API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode and clientCredentials flows, exposing 4 scopes. It supports OAuth 2.0 (smartOnFhir) using the authorizationCode and clientCredentials flows, exposing 303 scopes.

  • oauth2 — SMART on FHIR OAuth 2.0 with patient, user, and system scopes.
  • smartOnFhir — SMART on FHIR OAuth 2.0. Endpoints are tenant-scoped and are discovered per tenant from /.well-known/smart-configuration. Client authentication methods adverti…

Paths & Operations 4

Across 2 paths, the API surfaces 4 operations — 2 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Encounter 4

Patient encounter records.

GET
/Encounter
Search or Read Encounter
searchEncounter 1 param → 200401
POST
/Encounter
Create Encounter
createEncounter body → 201400401403404406422500
GET
/Encounter/{id}
Read Encounter
readEncounter 1 param → 200400401403404406422500
PATCH
/Encounter/{id}
Patch Encounter
patchEncounter 2 params body → 200409400401403404406422

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Bundle (5 properties), FHIRBundle (4 properties), Resource (3 properties), OperationOutcome (2 properties). Each schema is shown below with its type and property counts.

FHIRBundle
object
A FHIR R4 Bundle resource wrapping a collection of resources.
4 properties
FHIRResource
object
A generic FHIR R4 resource.
2 properties
Bundle
object
A FHIR R4 Bundle. Search results are returned as type: searchset; paging is carried on link[relation=next].
5 properties 2 required
OperationOutcome
object
FHIR R4 OperationOutcome — the error envelope for every non-2xx response.
2 properties 2 required
Resource
object
A FHIR R4 resource. The wire format is application/fhir+json; element-level schemas are defined by HL7 FHIR R4 (4.0.1), not by this document.
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cerner-encounter-api-openapi.yml Raw ↑

Other APIs Oracle Health (Cerner) publishes across the network.

Oracle Health Millennium FHIR DSTU2 API
AE Profile APIs.io
Oracle Health Code Console (Developer Portal)
AE Profile APIs.io
Cerner CareAware Integration APIs
AE Profile APIs.io
Oracle Health SMART on FHIR App Launch
AE Profile APIs.io
Cerner (Oracle Health) Capability API
AE Profile APIs.io
Cerner (Oracle Health) Condition API
AE Profile APIs.io
Cerner (Oracle Health) Definitions API
AE Profile APIs.io
Cerner (Oracle Health) Generic API
AE Profile APIs.io
Cerner (Oracle Health) Patient API
AE Profile APIs.io
Cerner (Oracle Health) Procedure API
AE Profile APIs.io
Oracle Health (Cerner) Account API
AE Profile APIs.io
Oracle Health (Cerner) Allergy Intolerance API
AE Profile APIs.io
#Encounter
← Back to C APIs
API Details
ID
cerner:cerner-encounter-api
Base URL
https://fhir-ehr.cerner.com/r4/{tenant}
Docs
https://docs.oracle.com/en/industries/health/millennium-platform-apis/mfrap/r4_overview.html
Provider
Oracle Health (Cerner)
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=cerner-encounter-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/cerner-encounter-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Cerner (Oracle Health) Encounter API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.