# Oracle Health Data Intelligence

> Oracle Health Data Intelligence (formerly Cerner HealtheIntent) is a tenant-scoped population
> health platform. It aggregates data from electronic health records, claims and other sources into
> a longitudinal record per patient, and exposes roughly sixty REST APIs over that record and over
> the intelligence computed from it — registries, risk scores, hierarchical condition categories,
> care plans, cohorts and consumer engagement.

Generated by API Evangelist on 2026-08-27 from Oracle's public developer portal and from the
artifacts in this repository. Oracle does not publish an llms.txt of its own
(https://docs.healtheintent.com/llms.txt returned 403 on 2026-08-27).

## What you need to know before calling anything

- **These APIs return protected health information.** Oracle states that user-level authorization
  and filtering are NOT applied by the platform. It is a business-to-business surface and the
  calling system is responsible for applying authorization controls for its own users. An agent
  placed in front of these APIs inherits that obligation.
- **There is no public signup.** Access requires an Oracle system account requested through the
  Cerner Central portal, plus a per-API authorization grant made by an administrator in the Health
  Data Intelligence Console. There is no free tier, no self-serve key and no anonymous access.
- **Patient IDs are not stable.** Oracle instructs that they must not be stored locally for
  long-term use. Resolve a source system's local patient ID to a platform patient ID at the start
  of each workflow using the Patient API ID lookup.
- **These are deliberately not FHIR APIs.** Oracle publishes a reasoned position on why. If you
  need FHIR, that is the separate Oracle Health Millennium Platform product.

## Base URL

    https://{tenant}.api.{region}.healtheintent.com/{api}/{version}/{resource}

- `tenant` — mnemonic for the customer tenant. `cernerdemo` is Oracle's shared sandbox tenant,
  populated with realistic synthetic data and no PHI.
- `region` — Oracle Cerner Cloud Region: `us-1`, `emea-1`, `emea-2`, `ca-1`, `ap-1`. The region is
  in the hostname, so the base URL determines data residency.
- Version in the path is mandatory.

Legacy (pre-1.0) APIs use a different structure:
`https://{tenant}.{solution}.{region}.healtheintent.com/api/{resource}`

## Authentication

Two methods, both tied to a system account:

1. **Bearer token** (preferred). `Authorization: Bearer <token>`. Tokens do not expire
   automatically and must be rotated manually.
2. **Two-legged OAuth 1.0a**. Consumer key and secret are exchanged for a short-lived
   `oauth_token` (3600s) sent in an OAuth Authorization header.

There is no OAuth 2.0, no OpenID Connect and no scope vocabulary. A live 401 advertises both
schemes: `WWW-Authenticate: Bearer realm=... OAuth realm=...`

- https://docs.healtheintent.com/#authentication
- authentication/oracle-health-data-intelligence-authentication.yml

## Conventions

- **Pagination**: cursor-based. Send `cursor` and `limit` (default 20, max 100). Responses carry
  `items`, `firstLink` and `nextLink` as absolute URLs — follow `nextLink` verbatim.
- **Errors**: `{ "code": <int>, "message": "<string>", "errorDetails": [ { domain, reason, message,
  locationType, location } ] }`. Not RFC 9457 problem+json.
- **Correlation**: every response carries a `cerner-correlation-id` header. Quote it to support.
- **Rate limits**: Oracle throttles and returns 429, but publishes no limit, no window and no
  rate-limit response headers. Use exponential backoff; there is no `Retry-After` to read.
- **Idempotency**: not supported. No idempotency key, no dedupe window.
- **Versioning**: path-based. Within a version, only passive (additive) changes occur; anything
  nonpassive gets a new version.

- conventions/oracle-health-data-intelligence-conventions.yml
- errors/oracle-health-data-intelligence-problem-types.yml
- rate-limits/oracle-health-data-intelligence-rate-limits.yml

## Machine-readable contract

Oracle publishes no OpenAPI, Swagger, GraphQL schema, AsyncAPI, protobuf or WSDL. The developer
portal is a Slate-rendered HTML reference. This repository carries one derived OpenAPI covering the
Allergy API's population-scoped reads:

- openapi/oracle-health-data-intelligence-populations-api-openapi.yml — `listAllergies`,
  `getAllergy`
- overlays/oracle-health-data-intelligence-populations-api-overlay.yaml — corrections and additions
  read from Oracle's own reference
- data-model/oracle-health-data-intelligence-data-model.yml

## Documented API surface

Care planning and coordination: Care Management (legacy), Health Concern, Longitudinal Plan,
Provider v1, Provider v2, Specialty, Readmission Risk (legacy), Transition of Care (legacy),
Risk Assessment.

Consumer engagement: Application Experience, Patient Portal Application, Consumer Notifications,
Consumer Engagement, Consumer Identity Provider, Salesforce Integration.

Content and core: Ontology, Master Person Management, Tenant.

Data ingestion: CareAware Data Ingestion, Classic Data Ingestion, Data Ingestion, Prime Data
Ingestion, Universal Data Ingestion, Data Collector (legacy).

Genomics: Genomics.

Longitudinal record: Consumer, Organization, Personnel, Specialty, Attribution, Chart Search,
Cohort, Allergy, Appointment, Condition, Encounter, HealtheRecord (legacy), Immunization,
Longitudinal Record (Binary, Bulk Extract, Document Reference, Medication Dispense and related),
Medication, Observation, Patient, Procedure, Questionnaire Response, Provider Search.

Analytics and syndication: Analytics Content Management, Analytics Data Warehouse, Business
Intelligence, Data Syndication, Soarian ODS.

Intelligence: Condition Identification, Diagnosis Insights Application, Hierarchical Condition
Category, HealtheInsights Application, HealtheRegistries (legacy), Quality Measure.

Index of all of the above: https://docs.healtheintent.com/

## What is not published

- No SDKs. Oracle states plainly: "Oracle Health Data Intelligence does not have any SDK."
- No CLI.
- No MCP server for this platform.
- No A2A agent card.
- No `/.well-known/` documents on any host.
- No webhooks or event subscriptions. Data Syndication delivers bundles by writing to a
  customer-owned Amazon S3 bucket; Consumer Notifications sends SMS and email to patients.
- No public status page, no public SLA, no public changelog (Release Notes sit behind a Cerner Wiki
  login), and no public pricing — API access is bundled with the platform licence.

## Links

- Developer portal: https://docs.healtheintent.com/
- Allergy API reference: https://docs.healtheintent.com/api/v1/allergy/
- System account request (US): https://cernercentral.com/system-accounts/
- System account request (EU): https://eu.cernercentral.com/system-accounts/
- Ignite APIs community: https://community.oracle.com/oraclehealth/group/1423-ignite-apis-community
- Service records: https://eservice.ucern.com/
- Product page: https://www.oracle.com/health/population-health/
- Oracle cloud compliance: https://www.oracle.com/corporate/cloud-compliance/
- Terms: https://www.oracle.com/legal/terms/
- Privacy: https://www.oracle.com/legal/privacy/