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

Orion Health Encounter API

Operations on Encounter resources

Orion Health Encounter API is one of 33 APIs that Orion Health publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

This API exposes 3 JSON Schema definitions.

Tagged areas include Encounter. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a JSON-LD context, an AsyncAPI specification, a getting-started guide, and 3 JSON Schemas.

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

Requests are made against 2 base URLs: https://api.orionhealth.com/fhir, https://sandbox.orionhealth.com/fhir.

2 operations 2 paths 8 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.orionhealth.com/fhir
Authentication
OAuth 2.0, HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 2

Orion Health Encounter API declares 2 security schemes for authenticating requests. It supports OAuth 2.0 (oauth2) using the authorizationCode flow, exposing 9 scopes. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • oauth2 — OAuth 2.0 authorization using SMART on FHIR

Paths & Operations 2

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

Encounter 2

Operations on Encounter resources

GET
/Encounter
Orion Health Search for encounters
searchEncounters 8 params → 200400401
GET
/Encounter/{id}
Orion Health Read an encounter by ID
getEncounter 2 params → 200401404

Schemas 8

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

CodeableConcept
object
2 properties
Reference
object
2 properties
Period
object
2 properties
Encounter
object
9 properties
Bundle
object
5 properties
Coding
object
3 properties
Resource
object
3 properties
OperationOutcome
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

orion-health-encounter-api-openapi.yml Raw ↑

Other APIs Orion Health publishes across the network.

Orion Health
Orion Health Alerts API
Orion Health AllergyIntolerance API
Orion Health Analytics API
Orion Health Audit API
Orion Health Care Programs API
Orion Health CarePlan API
Orion Health Cohorts API
Orion Health Communication Points API
Orion Health Condition API
Orion Health Configuration API
Orion Health Consent API
Where this information came from

This is an independent, third-party profile of Orion 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.