Temple Health · OpenAPI Overlay 1.0.0

API Evangelist enhancements for Temple Health FHIR R4 Allergy Intolerance Encounter API

4 actions 4 updates update extends openapi/temple-health-encounter-api-openapi.yml

Derived by API Evangelist Built from the contracts Temple Health publishes. Temple Health did not publish this file.

View Overlay File View on GitHub Overlay Specification

What the actions change

x-apievangelist-providerx-apievangelist-enrichedx-fhir-versionx-us-core-versionx-epic-releasex-capability-statementx-smart-configurationx-regulatory-basis

Targets 4

$.info

$.servers[0]

$.paths['/Encounter'].get

OpenAPI Overlay

overlay: 1.0.0
info:
  title: API Evangelist enhancements for Temple Health FHIR R4 Allergy Intolerance Encounter API
  version: 1.0.0
extends: openapi/temple-health-encounter-api-openapi.yml
x-generated: '2026-08-15'
x-method: generated
x-source: Live probes of https://epicaccess.templehealth.org/FhirProxyPrd/api/FHIR/R4 on 2026-08-15 plus
  the derived artifacts in this repository. The original OpenAPI is never mutated.
actions:
- target: $.info
  description: Record API Evangelist provenance and the live conformance facts observed on 2026-08-15.
  update:
    x-apievangelist-provider: temple-health
    x-apievangelist-enriched: '2026-08-15'
    x-fhir-version: 4.0.1
    x-us-core-version: 6.1.0
    x-epic-release: February 2026 (releaseDate 2026-07-10, observed 2026-08-15)
    x-capability-statement: https://epicaccess.templehealth.org/FhirProxyPrd/api/FHIR/R4/metadata
    x-smart-configuration: https://epicaccess.templehealth.org/FhirProxyPrd/api/FHIR/R4/.well-known/smart-configuration
    x-regulatory-basis: CMS-9115-F Interoperability and Patient Access; 21st Century Cures Act ONC Final
      Rule
- target: $.servers[0]
  description: Annotate the production server with observed runtime behaviour.
  update:
    x-observed:
      probed: '2026-08-15'
      tls: TLSv1.2
      hsts: max-age=31536000; includeSubDomains
      cors: 'Access-Control-Allow-Origin: * with Allow-Credentials: true'
      cache_control: no-cache,no-store
      unauthenticated_response: '401 with bare "WWW-Authenticate: Bearer" and an empty JSON body (no OperationOutcome)'
      rate_limit_headers: none observed
- target: $
  description: Record that responses carry protected health information.
  update:
    x-data-classification: PHI
    x-agent-handling: Stay inside the SMART patient context granted by the token. Never accept a model-supplied
      patient identifier. Do not log or transcribe response bodies.
- target: $.paths['/Encounter'].get
  description: Cross-link searchEncounter to the derived artifacts in this repository.
  update:
    x-apievangelist-artifacts:
      conventions: conventions/temple-health-conventions.yml
      errors: errors/temple-health-problem-types.yml
      authentication: authentication/temple-health-authentication.yml
      scopes: scopes/temple-health-scopes.yml
      data_model: data-model/temple-health-data-model.yml
    x-idempotency: not supported — server declares conditionalCreate:false and conditionalUpdate:false
      on all 59 resource types

Work with this as data

Every overlay here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for openapi overlays

4 MCP tools reach this

find_overlaysBrowse and filter every overlay in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This overlay

curl "https://apis.io/api/v1/overlays/temple-health-encounter-api-overlay"

All openapi overlays

curl "https://apis.io/api/v1/overlays?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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