HAPI FHIR

HAPI FHIR provides an open-source implementation of the HL7 FHIR (Fast Healthcare Interoperability Resources) standard for Java. It enables developers to quickly build and deploy FHIR‑based clinical data repositories, offering RESTful APIs, a powerful server framework, and extensive tooling for validation, searching, and transaction processing. The project powers numerous health‑IT solutions and is maintained by the community and Smile CDR, delivering a robust, scalable platform for interoperable healthcare data exchange.

HAPI FHIR is listed with 2 APIs on the APIs.io network: Fhir API and Patient API. Tagged areas include Healthcare, Interoperability, Open Source, Java, and FHIR.

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

HAPI FHIR’s developer surface includes CLI, changelog, API reference, getting-started guide, documentation, engineering blog, support, and 11 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

22.0/100 emerging ▬ flat Agent 15/100 agent aware Heartbeat 50/100 alive Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

2 APIs

Healthcare Interoperability Open Source Java FHIR

Kin Score

Kin Score How this is scored →
scored 2026-11-06 · rubric v0.27.0

Composite quality — 22.0/100 · emerging

Contract Quality 3.6 / 19

Developer Ergonomics 4.8 / 15

Access Clarity 0.0 / 15

Operational Transparency 2.1 / 10

Contract Governance 2.0 / 9

Discoverability 5.0 / 8

Regulatory Posture 1.3 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 15/100 · agent aware

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 10

Idempotency 0 / 9

Stable Error Semantics 0 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 0 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

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/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/hapi-fhir/"><img src="https://apis.io/badge/hapi-fhir/card.svg" alt="HAPI FHIR on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Machine-Readable Auth +10 pts — a served openid-configuration/oauth-authorization-server carrying `issuer` (served), else the securitySchemes class in the provider OpenAPIs — bound (mutualTLS, DPoP, Signature) > negotiable (oauth2 authorizationCode/clientCredentials, openIdConnect) > bearer (http bearer, apiKey)
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
Stable Error Semantics +8 pts — OpenAPI $refs a shared error schema across 4xx/5xx responses (verified), else common[].type includes ErrorCatalog / ErrorCodes / DeclineCodes
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0

12 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Contract Quality scores 19.4 — up to +20.2 composite points
Access Clarity scores 0.0 — up to +20.0 composite points
Developer Ergonomics scores 32.1 — up to +13.6 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

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 the provider profile at artifacts.apis.io/hapi-fhir/apis.yml: open an issue on github.com/api-evangelist/hapi-fhir to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Standards implemented 2

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

HL7 FHIR

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

measured — observed by APIs.io (published)

APIs 2

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

HAPI FHIR Fhir API

The Fhir API from HAPI FHIR — 1 operation(s) for fhir.

HAPI FHIR Patient API

The Patient API from HAPI FHIR — 2 operation(s) for patient.

Semantic Vocabularies 1

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

Hapi Fhir Context

3 classes · 3 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

HAPI FHIR API Rules

7 rules · 5 errors 1 warnings 1 info

SPECTRAL

JSON Schema 3

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

PostPatientRequest

1 properties

JSON SCHEMA

PostPatientResponse

1 properties

JSON SCHEMA

PutPatientPatientidRequest

1 properties

JSON SCHEMA

Security Posture 1

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

Hapi Fhir Domain Security

TLSv1.2 · HSTS

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

Documentation 2

Reference material describing how the API behaves

APIReference

APIReference

Documentation

Documentation

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Spectral

JSONLD

Vocabulary

DataModel

Conformance

Build 4

SDKs, sample code, and the tooling you integrate with

CLI

SDKs

Packages

GitHub

Access & Security 1

Authentication, authorization, and security posture

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

ChangeLog

ChangeLog

Support

Support

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

Hosts

Hosts

Source (apis.yml)

aid: hapi-fhir
name: HAPI FHIR
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  probe_state: unreadable
  source:
  - security
  generated: '2026-11-06'
  method: derived
image: https://hapifhir.io/hapi-fhir/images/logos/raccoon-forwards.png
description: HAPI FHIR provides an open-source implementation of the HL7 FHIR (Fast Healthcare Interoperability Resources)
  standard for Java. It enables developers to quickly build and deploy FHIR‑based clinical data repositories, offering RESTful
  APIs, a powerful server framework, and extensive tooling for validation, searching, and transaction processing. The project
  powers numerous health‑IT solutions and is maintained by the community and Smile CDR, delivering a robust, scalable platform
  for interoperable healthcare data exchange.
url: https://raw.githubusercontent.com/api-evangelist/hapi-fhir/refs/heads/main/apis.yml
x-type: company
x-source: harvest:tag-qc
x-tier: profiled
x-tier-reason: enrichment pass 2026-10-14 (modular-v1; was harvest)
specificationVersion: '0.20'
created: '2026-10-13'
modified: '2026-10-13'
x-coverage:
  state: unreadable
  reason: no-machine-readable-spec
  detail: The provider's documentation site lists API reference but no OpenAPI or other machine‑readable contract was found.
  evidence:
  - url: https://api.hapifhir.io/openapi.json
    status: timeout
  checked: '2026-10-14'
tags:
- Healthcare
- Interoperability
- Open Source
- Java
- FHIR
tags_raw:
- Healthcare
- Interoperability
- OpenSource
- Java
- FHIR
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Spectral
  url: rules/hapi-fhir-rules.yml
- type: JSONLD
  url: json-ld/hapi-fhir-context.jsonld
- type: Vocabulary
  url: vocabulary/hapi-fhir-vocabulary.yml
- type: DataModel
  url: data-model/hapi-fhir-data-model.yml
- type: CLI
  url: cli/hapi-fhir-cli.yml
- type: ChangeLog
  url: changelog/hapi-fhir-changelog.yml
- type: Conformance
  url: conformance/hapi-fhir-conformance.yml
- type: Hosts
  url: hosts/hapi-fhir-hosts.yml
- type: SDKs
  url: packages/hapi-fhir-packages.yml
- type: Packages
  url: packages/hapi-fhir-packages.yml
- type: APIReference
  url: https://hapifhir.io/hapi-fhir/apidocs/hapi-fhir-base/
- type: GettingStarted
  url: https://hapifhir.io/hapi-fhir/docs/getting_started/introduction.html
- type: DomainSecurity
  url: security/hapi-fhir-domain-security.yml
- type: Website
  url: https://hapifhir.io
- type: Documentation
  url: https://hapifhir.io/hapi-fhir/
- type: Blog
  url: https://hapifhir.io/hapi-fhir/blog/
- type: Support
  url: https://smilecdr.com/
- type: GitHub
  url: https://github.com/jamesagnew/hapi-fhir
apis:
- aid: hapi-fhir:hapi-fhir-fhir-api
  name: HAPI FHIR Fhir API
  description: The Fhir API from HAPI FHIR — 1 operation(s) for fhir.
  humanURL: https://hapifhir.io/hapi-fhir/docs/server_plain/rest_operations.html
  baseURL: http://your-server-base
  tags:
  - FHIR
  tags_raw:
  - Fhir
  properties:
  - type: OpenAPI
    url: openapi/hapi-fhir-fhir-api-openapi.yml
  - type: JSONSchema
    url: json-schema/hapi-fhir-post-patient-response-schema.json
  - type: JSONSchema
    url: json-schema/hapi-fhir-post-patient-request-schema.json
  - type: JSONSchema
    url: json-schema/hapi-fhir-put-patient-patientid-request-schema.json
- aid: hapi-fhir:hapi-fhir-patient-api
  name: HAPI FHIR Patient API
  description: The Patient API from HAPI FHIR — 2 operation(s) for patient.
  humanURL: https://hapifhir.io/hapi-fhir/docs/server_plain/rest_operations.html
  baseURL: http://your-server-base
  tags:
  - Patients
  tags_raw:
  - Patient
  properties:
  - type: OpenAPI
    url: openapi/hapi-fhir-patient-api-openapi.yml
  - type: JSONSchema
    url: json-schema/hapi-fhir-post-patient-response-schema.json
  - type: JSONSchema
    url: json-schema/hapi-fhir-post-patient-request-schema.json
  - type: JSONSchema
    url: json-schema/hapi-fhir-put-patient-patientid-request-schema.json
x-enrichment:
  date: '2026-10-14'
  status: enriched
  artifacts_added: 17
  pass: modular-v1
  engine: identity=local,contract=local,surfaces=local,docs=local,regulatory=local

HAPI FHIR — frequently asked questions

Does HAPI FHIR have an API?

Yes. APIs.io lists 2 APIs from HAPI FHIR, including HAPI FHIR Fhir API and HAPI FHIR Patient API.

Is there an OpenAPI specification for the HAPI FHIR?

Yes. APIs.io indexes 2 OpenAPI specifications for HAPI FHIR, each linked for download from this page.

Is the HAPI FHIR ready for AI agents?

HAPI FHIR has a Kin Score of 22.0 out of 100 (emerging) and an Agent Readiness score of 14.8 (agent-aware), scored by API Evangelist on 2026-11-06.

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/hapi-fhir"

All providers

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

Every operation they expose

curl "https://apis.io/api/v1/providers/hapi-fhir/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/hapi-fhir/evidence"

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.