HL7 FHIR website screenshot

HL7 FHIR

HL7 FHIR (Fast Healthcare Interoperability Resources) is the standard API specification for healthcare data exchange, published by Health Level Seven International (HL7). FHIR REST APIs provide access to patient, clinical, financial, and administrative healthcare data in JSON, XML, and RDF formats with a CC0 open license.

HL7 FHIR publishes 6 APIs on the APIs.io network, including Bundle API, Condition API, Encounter API, and 3 more. Tagged areas include Clinical, FHIR, Healthcare, HL7, and Interoperability.

The HL7 FHIR catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

HL7 FHIR’s developer surface includes authentication, developer portal, documentation, changelog, getting-started guide, and 11 more developer resources.

42.1/100 developing ▬ flat Agent 25/100 agent aware Full breakdown ↓
scored 2026-09-08 · rubric v0.20.0
AccessFreemiumSelf serve
1 APIs
ClinicalFHIRHealthcareHL7Interoperability

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Regulatory Posture applies to this provider. Its tags matched the Health regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.
The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/hl7-fhir: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

APIs 8

Individual APIs this provider publishes, each with its own machine-readable definition.

HL7 FHIR R5 Healthcare API

HL7 FHIR R5 (Release 5) is the current published FHIR standard for healthcare data exchange. FHIR R5 REST APIs provide access to patient demographics, observations, conditions, ...

SMART on FHIR Authentication

SMART on FHIR (v2.2.0) defines OAuth 2.0-based authorization patterns for client applications to authorize, authenticate, and integrate with FHIR-based data systems. It enables ...

HL7 FHIR Bundle API

Batch and transaction operations

HL7 FHIR Condition API

Clinical conditions, diagnoses, and problems

HL7 FHIR Encounter API

Patient visits and encounters

HL7 FHIR MedicationRequest API

Medication prescriptions and orders

HL7 FHIR Observation API

Clinical measurements, lab results, vital signs

HL7 FHIR Patient API

Patient demographic and identity resources

Scroll for all 8

Open Collections 8

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

API Collection

OPEN COLLECTION

Scroll for all 8

Pricing Plans 1

Published pricing tiers and plan structures.

Rate Limits 1

Documented rate limits and quota policies.

Hl7 Fhir Rate Limits

5 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Hl7 Fhir Context

13 classes · 21 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

HL7 FHIR API Rules

6 rules · 4 warnings 2 info

SPECTRAL

JSON Schema 1

Standalone JSON Schema definitions for this provider's data models.

HL7 FHIR R4 Patient

23 properties

JSON SCHEMA

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Hl7 Fhir Authentication

oauth2 · 1 scheme

SECURITY

Hl7 Fhir Domain Security

TLSv1.3 · DMARC

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Hl7 Fhir Scopes

7 scopes · authorizationCode

7 scopes

SCOPES

Agentic Access 1

Recommended x-agentic-access execution contracts for AI agents.

Hl7 Fhir Agentic Access

11 operations · 3 acting

11 operations · 3 acting

AGENTIC

Resources

Get Started 2

Portal, sign-up, and the first successful call

Documentation 4

Reference material describing how the API behaves

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Design & Contract 1

Pagination, idempotency, versioning, errors, and events

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 4

Authentication, authorization, and security posture

Operate 1

Status, limits, changes, and where to get help

Company 1

The organization behind the API

Other 1

Properties that don't map to a standard resource type

Source (apis.yml)

apis.yml Raw ↑
aid: hl7-fhir
name: HL7 FHIR
description: HL7 FHIR (Fast Healthcare Interoperability Resources) is the standard API specification for healthcare data exchange,
  published by Health Level Seven International (HL7). FHIR REST APIs provide access to patient, clinical, financial, and
  administrative healthcare data in JSON, XML, and RDF formats with a CC0 open license.
url: https://raw.githubusercontent.com/api-evangelist/hl7-fhir/refs/heads/main/apis.yml
type: Index
deliveryModel:
  model: unknown
  open_source: false
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - openapi
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Freemium · Self-serve signup
  confidence: medium
  try_now_blocked_by: example-domain
  source:
  - plans
  - authentication
  - security
  generated: '2026-08-26'
  method: derived
tags:
- Clinical
- FHIR
- Healthcare
- HL7
- Interoperability
created: '2025'
modified: '2026-05-19'
specificationVersion: '0.23'
apis:
- aid: hl7-fhir:hl7-fhir-r5-api
  name: HL7 FHIR R5 Healthcare API
  description: HL7 FHIR R5 (Release 5) is the current published FHIR standard for healthcare data exchange. FHIR R5 REST APIs
    provide access to patient demographics, observations, conditions, medications, encounters, and care plans in both JSON
    and XML formats across EHR systems, published March 2023.
  humanURL: https://www.hl7.org/fhir/
  baseURL: https://fhir-server.example.com/fhir/R5
  tags:
  - Clinical
  - FHIR
  - Healthcare
  - HL7
  - Interoperability
  - JSON
  - XML
  properties:
  - type: Documentation
    url: https://www.hl7.org/fhir/
  - type: Reference
    url: https://www.hl7.org/fhir/http.html
  - type: Authentication
    url: https://www.hl7.org/fhir/security.html
  - type: ChangeLog
    url: https://www.hl7.org/fhir/history.html
- aid: hl7-fhir:hl7-smart-on-fhir-api
  name: SMART on FHIR Authentication
  description: SMART on FHIR (v2.2.0) defines OAuth 2.0-based authorization patterns for client applications to authorize,
    authenticate, and integrate with FHIR-based data systems. It enables EHR launch, standalone launch, and backend service
    authorization workflows.
  humanURL: http://hl7.org/fhir/smart-app-launch/ImplementationGuide/hl7.fhir.uv.smart-app-launch
  baseURL: https://fhir-server.example.com/fhir
  tags:
  - Authentication
  - FHIR
  - Healthcare
  - SMART
  tags_raw:
  - Authentication
  - FHIR
  - Healthcare
  - OAuth2
  - SMART
  properties:
  - type: Documentation
    url: http://hl7.org/fhir/smart-app-launch/ImplementationGuide/hl7.fhir.uv.smart-app-launch
  - type: Authentication
    url: http://hl7.org/fhir/smart-app-launch/ImplementationGuide/hl7.fhir.uv.smart-app-launch
- aid: hl7-fhir:hl7-fhir-bundle-api
  name: HL7 FHIR Bundle API
  description: Batch and transaction operations
  humanURL: https://www.hl7.org/fhir/
  baseURL: https://fhir-server.example.com/fhir/R5
  tags:
  - Bundle
  properties:
  - type: OpenAPI
    url: openapi/hl7-fhir-bundle-api-openapi.yml
  - type: Documentation
    url: https://www.hl7.org/fhir/R4/
  - type: Reference
    url: https://www.hl7.org/fhir/R4/http.html
  - type: ChangeLog
    url: http://hl7.org/fhir/R4/history.html
- aid: hl7-fhir:hl7-fhir-condition-api
  name: HL7 FHIR Condition API
  description: Clinical conditions, diagnoses, and problems
  humanURL: https://www.hl7.org/fhir/
  baseURL: https://fhir-server.example.com/fhir/R5
  tags:
  - Condition
  properties:
  - type: OpenAPI
    url: openapi/hl7-fhir-condition-api-openapi.yml
  - type: Documentation
    url: https://www.hl7.org/fhir/R4/
  - type: Reference
    url: https://www.hl7.org/fhir/R4/http.html
  - type: ChangeLog
    url: http://hl7.org/fhir/R4/history.html
- aid: hl7-fhir:hl7-fhir-encounter-api
  name: HL7 FHIR Encounter API
  description: Patient visits and encounters
  humanURL: https://www.hl7.org/fhir/
  baseURL: https://fhir-server.example.com/fhir/R5
  tags:
  - Encounter
  properties:
  - type: OpenAPI
    url: openapi/hl7-fhir-encounter-api-openapi.yml
  - type: Documentation
    url: https://www.hl7.org/fhir/R4/
  - type: Reference
    url: https://www.hl7.org/fhir/R4/http.html
  - type: ChangeLog
    url: http://hl7.org/fhir/R4/history.html
- aid: hl7-fhir:hl7-fhir-medicationrequest-api
  name: HL7 FHIR MedicationRequest API
  description: Medication prescriptions and orders
  humanURL: https://www.hl7.org/fhir/
  baseURL: https://fhir-server.example.com/fhir/R5
  tags:
  - MedicationRequest
  properties:
  - type: OpenAPI
    url: openapi/hl7-fhir-medicationrequest-api-openapi.yml
  - type: Documentation
    url: https://www.hl7.org/fhir/R4/
  - type: Reference
    url: https://www.hl7.org/fhir/R4/http.html
  - type: ChangeLog
    url: http://hl7.org/fhir/R4/history.html
- aid: hl7-fhir:hl7-fhir-observation-api
  name: HL7 FHIR Observation API
  description: Clinical measurements, lab results, vital signs
  humanURL: https://www.hl7.org/fhir/
  baseURL: https://fhir-server.example.com/fhir/R5
  tags:
  - Observation
  properties:
  - type: OpenAPI
    url: openapi/hl7-fhir-observation-api-openapi.yml
  - type: Documentation
    url: https://www.hl7.org/fhir/R4/
  - type: Reference
    url: https://www.hl7.org/fhir/R4/http.html
  - type: ChangeLog
    url: http://hl7.org/fhir/R4/history.html
- aid: hl7-fhir:hl7-fhir-patient-api
  name: HL7 FHIR Patient API
  description: Patient demographic and identity resources
  humanURL: https://www.hl7.org/fhir/
  baseURL: https://fhir-server.example.com/fhir/R5
  tags:
  - Patient
  properties:
  - type: OpenAPI
    url: openapi/hl7-fhir-patient-api-openapi.yml
  - type: Documentation
    url: https://www.hl7.org/fhir/R4/
  - type: Reference
    url: https://www.hl7.org/fhir/R4/http.html
  - type: ChangeLog
    url: http://hl7.org/fhir/R4/history.html
common:
- type: CapabilityMap
  url: capabilities/hl7-fhir-capability-edges.yml
  name: HL7 FHIR Business Capability Map
- type: AgenticAccess
  url: agentic-access/hl7-fhir-agentic-access.yml
- type: DomainSecurity
  url: security/hl7-fhir-domain-security.yml
- type: Authentication
  url: authentication/hl7-fhir-authentication.yml
- type: OAuthScopes
  url: scopes/hl7-fhir-scopes.yml
- type: Portal
  url: https://www.hl7.org/fhir/
- type: Documentation
  url: https://www.hl7.org/fhir/
- type: Reference
  url: https://www.hl7.org/fhir/http.html
- type: Authentication
  url: https://www.hl7.org/fhir/security.html
- type: ChangeLog
  url: https://www.hl7.org/fhir/history.html
- type: GettingStarted
  url: https://www.hl7.org/fhir/downloads.html
- type: Website
  url: https://www.hl7.org/
- type: GitHubOrganization
  url: https://github.com/HL7
- type: OpenAPI
  url: openapi/_original/hl7-fhir-r4-openapi.yml
- type: JSONSchema
  url: json-schema/hl7-fhir-patient-schema.json
- type: JSONLDContext
  url: json-ld/hl7-fhir-context.jsonld
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider 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 providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • 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 provider
curl "https://apis.io/api/v1/providers/hl7-fhir"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/hl7-fhir/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/hl7-fhir/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

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.

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