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

Oracle Health Data Intelligence Populations API

The Populations API from Oracle Health Data Intelligence — population-scoped read access to a patient's aggregated allergy record within the longitudinal patient record. Two operations, listAllergies and getAllergy, both cursor-paginated and both returning protected health information. Authenticated with a system-account bearer token or two-legged OAuth 1.0a.

Oracle Health Data Intelligence Populations API is one of 2 APIs that Oracle Health Data Intelligence publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Populations, Allergy, and Health Records. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

Requests are made against a single base URL, https://cernerdemo.api.us-1.healtheintent.com/allergy/v1.

2 operations 2 paths 4 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://cernerdemo.api.us-1.healtheintent.com/allergy/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Oracle Health Data Intelligence Populations API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Bearer token supplied via the Authorization header.

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.

Populations 2
GET
/populations/{populationId}/patients/{patientId}/allergies
Retrieve a list of allergies for a patient
listAllergies 5 params → 200400401403404
GET
/populations/{populationId}/patients/{patientId}/allergies/{allergyId}
Retrieve a single allergy
getAllergy 3 params → 200400401403404

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Allergy (15 properties), CodeableConcept (4 properties), Allergies (3 properties), Error (2 properties). Each schema is shown below with its type and property counts.

Allergy
object
15 properties 1 required
CodeableConcept
object
4 properties
Error
object
2 properties
Allergies
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

oracle-health-data-intelligence-populations-api-openapi.yml Raw ↑

Other APIs Oracle Health Data Intelligence publishes across the network.

Oracle Health Data Intelligence
Where this information came from

This is an independent, third-party profile of Oracle Health Data Intelligence Populations 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.