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

Cerner (Oracle Health) Procedure API

Patient procedures.

Cerner (Oracle Health) Procedure 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 Procedure. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 3 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-code.cerner.com/r4/{tenant}, https://fhir-myrecord.cerner.com/r4/{tenant}, https://fhir-open.cerner.com/r4/{tenant}, https://fhir-ehr.cerner.com/r4, https://fhir-open.cerner.com/r4.

3 operations 2 paths 5 schemas 2 GET1 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
Resource Areas
1

Authentication & Security 2

Cerner (Oracle Health) Procedure API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (smartOnFhir) using the authorizationCode and clientCredentials flows, exposing 303 scopes. It supports OAuth 2.0 (oauth2) using the authorizationCode and clientCredentials flows, exposing 4 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…
  • oauth2 — SMART on FHIR OAuth 2.0 with patient, user, and system scopes.

Paths & Operations 3

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

Procedure 3

FHIR R4 Procedure resource as implemented by Oracle Health Millennium Platform.

GET
/Procedure
Search Procedure
searchProcedure 5 params → 200400401403404406422500
POST
/Procedure
Create Procedure
createProcedure body → 201400401403404406422500
GET
/Procedure/{id}
Read Procedure
readProcedure 1 param → 200400401403404406422500

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), FHIRResource (2 properties). Each schema is shown below with its type and property counts.

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
FHIRBundle
object
A FHIR R4 Bundle resource wrapping a collection of resources.
4 properties
FHIRResource
object
A generic FHIR R4 resource.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cerner-procedure-api-openapi.yml Raw ↑

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

Oracle Health Millennium FHIR DSTU2 API
Oracle Health Code Console (Developer Portal)
Cerner CareAware Integration APIs
Oracle Health SMART on FHIR App Launch
Cerner (Oracle Health) Capability API
Cerner (Oracle Health) Condition API
Cerner (Oracle Health) Definitions API
Cerner (Oracle Health) Encounter API
Cerner (Oracle Health) Generic API
Cerner (Oracle Health) Patient API
Oracle Health (Cerner) Account API
Oracle Health (Cerner) Allergy Intolerance API
Where this information came from

This is an independent, third-party profile of Cerner (Oracle Health) Procedure 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.