Medplum

Medplum is an Apache 2.0 open-source, FHIR-native developer platform for shipping clinical software. It bundles a FHIR R4 datastore, REST and GraphQL APIs, a TypeScript SDK, React component library, OAuth 2.0 / SMART on FHIR authentication, declarative Access Policies, Subscriptions, and TypeScript-based serverless Bots — sold as a hosted service at api.medplum.com and as a self-hostable monorepo on GitHub. Medplum is HIPAA, SOC 2 Type II, and ONC-certified.

Medplum publishes 4 API contracts indexed on the APIs.io network, including Fhir API, and 3 more. Tagged areas include Healthcare, FHIR, Open Source, Developer Platform, and HIPAA.

The Medplum catalog on APIs.io includes 1 event-driven AsyncAPI specification, 1 JSON-LD context, and 2 Spectral governance rulesets.

Medplum’s developer surface includes authentication, documentation, getting-started guide, API reference, CLI, developer console, pricing, and 66 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

77.4/100 exemplar ▬ flat Agent 56/100 agent ready Front door AI 3/6 light Heartbeat 100/100 alive open core · Apache-2.0 Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemiumSelf serve⚡ Free to try

1 published contract 1 MCP Servers 3 Agent Skills 9 Features 7 Use Cases

Healthcare FHIR Open Source Developer Platform HIPAA SMART on FHIR Clinical Interoperability

What this lets a business do 1

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Health Information Management

BC-2900

Fhir

POST /fhir/R4 GET /fhir/R4/{resourceType} POST /fhir/R4/{resourceType}

What people ask Medplum 1

The questions people put to an LLM, and the jobs they hand an agent, that Medplum's APIs answer — each one linked to the operation that does it. Generated by API Evangelist

Medplum Fhir API Search FHIR resources of a given type “How do I list all the Patient resources stored in my Medplum project?” Create a new FHIR resource “How do I add a brand-new Patient record to the FHIR server?” Fetch one FHIR resource by its id “How do I fetch a single Patient by its FHIR id?” Replace an existing FHIR resource “How do I overwrite an existing FHIR resource with a complete new copy?”

Kin Score

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

Composite quality — 77.4/100 · exemplar

Contract Quality 12.0 / 16

Developer Ergonomics 9.7 / 13

Access Clarity 11.3 / 13

Operational Transparency 6.2 / 8

Contract Governance 2.8 / 8

Discoverability 4.3 / 7

Regulatory Posture 8.7 / 15

Open Source Surface 6.0 / 10

Create-or-Update Ergonomics 1.1 / 10

Agent readiness — 56/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 10 / 10

Documented Reversibility 0 / 6

MCP Server 12 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 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 6 / 6

Protected Resource Metadata 5 / 5

Registration Without a Human 6 / 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.

Open Source Surface applies to this provider. This product is open source and we read its repository directly, so Open Source Surface carries 10 points of the composite. It is scored from what the repository actually publishes — a security policy, a contribution guide, a release history, a code of conduct — read live from the provider rather than inferred from our own catalog pointers. This facet adds; nothing was taken away to make room for it. An open-source project is not excused from the commercial facets, because exemption would strip it of the points it does earn. If we have the wrong repository, or this product is not open source, say so on your provider repo and we will drop the facet rather than have you publish against 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 65 points between them, because both conditional facets apply and carry 35 points together. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 65% 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/medplum/"><img src="https://apis.io/badge/medplum/card.svg" alt="Medplum 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):

A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too
Agentic Commerce Well-Known Document +5 pts — a parsing /.well-known/ucp.json or acp.json declaring a version and at least one service, OR (0.27) a live x402 payment challenge from _data/x402-adoption.json — `self` when its endpoints are on the provider's own domain, `platform` when they are on a vendor's
Dry-Run / Simulate Mode +4 pts — OpenAPI: destructive operations expose a dry_run / simulate / preview / validate_only parameter
Well-Known Catalog +4 pts — common[].type includes WellKnown, APICatalog, or api-catalog
Consent & Bot Identity +3 pts — common[].type includes AIPREF, ContentSignal, WebBotAuth, or HTTPMessageSignatures

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

Contract Governance scores 35.6 — up to +7.7 composite points
Contract Quality scores 74.1 — up to +6.5 composite points
Developer Ergonomics scores 74.4 — up to +5.1 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/medplum/apis.yml: open an issue on github.com/api-evangelist/medplum 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 →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Healthcare (FHIR)	core	24.1	1	1
Medical Technology (certified health IT, FDA-authorized AI devices)	core	24.1	1	1
FHIR Implementation Guides (HL7 FHIR package and IG publishers)	core	24.1	1	1
OpenSSF Best Practices Badge Holders	core	24.1	1	1

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 8

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

SMART on FHIR

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

Model Context Protocol (MCP)

measured — observed by APIs.io (documented)

OAuth 2.0 Protected Resource Metadata

measured — observed by APIs.io (verified)

Dynamic Client Registration

measured — observed by APIs.io (published)

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

OpenID Connect

measured — observed by APIs.io (declared)

APIs 4

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

Medplum GraphQL API

FHIR-aware GraphQL endpoint at https://api.medplum.com/fhir/R4/$graphql. Supports typed nested queries, reverse-reference traversal (_reference), FHIRPath-style array filtering,...

Medplum Bots

Bots are TypeScript serverless functions (AWS Lambda-style) executed in response to FHIR Subscriptions, HTTP triggers, or scheduled cron. Bots are the backbone of Medplum integr...

Medplum Subscriptions

FHIR Subscription resources that match a search criteria and dispatch real-time notifications via REST hooks (webhooks) or Websockets when matching resources are created or upda...

Medplum Fhir API

Medplum's FHIR R4 REST API, as described by its own OpenAPI (https://api.medplum.com/openapi.json): batch/transaction, search, create (incl. conditional create via If-None-Exist...

Postman Collections 1

Ready-to-run Postman collections for exercising this provider's APIs.

Medplum - OpenAPI 3.0

POSTMAN

Open Collections 1

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

Medplum - OpenAPI 3.0 Fhir API

OPEN COLLECTION

Arazzo Workflows 11

Multi-step API workflows described with the Arazzo specification.

Medplum Amend Resource With History

Read a resource, update it, then inspect its version history and prior version.

ARAZZO

Medplum Clinical Data Query

Locate a patient by name, read the Patient resource, then pull that patient's Observations.

ARAZZO

Medplum Create Diagnostic Report

Create an Observation result, then assemble a DiagnosticReport that references it.

ARAZZO

Medplum Deploy Bot

Create a Bot resource, then create a Subscription that invokes the Bot on resource changes.

ARAZZO

Medplum FHIR Resource CRUD

Create a FHIR R4 resource, read it back by id, update it, then search the resource type for it.

ARAZZO

Medplum Finalize Observation

Find a preliminary Observation, patch its status to final, and read it back to confirm.

ARAZZO

Medplum Find And Delete Resource

Search a resource type, and if a match is found read it for audit then delete it.

ARAZZO

Medplum Register Patient With Observation

Create a Patient, then record a vital-sign Observation that references that patient.

ARAZZO

Medplum FHIR Resource Versioning

Create a FHIR resource, update it to mint a new version, read its history, then read a specific version.

ARAZZO

Medplum Schedule Encounter

Create a Practitioner, create an Encounter linking the patient and practitioner, then read it back.

ARAZZO

Medplum Upsert Patient

Update a Patient matched by identifier, or create it, in one FHIR conditional update.

ARAZZO

Scroll for all 11

MCP Servers 1

Model Context Protocol servers that expose these APIs to AI agents.

Medplum MCP Server

Official hosted Medplum MCP server. Exposes the Medplum FHIR API to AI clients through a single general-purpose FHIR request tool plus two client-compatibility shims, authentica...

MCP SERVER

Agent Skills 3

Packaged agent skills for driving this provider's APIs from an AI assistant.

medplum-amend-resource-with-history

AGENT SKILL

medplum-register-patient-with-observation

AGENT SKILL

medplum-upsert-patient

AGENT SKILL

GraphQL 1

GraphQL schemas published by this provider.

Medplum GraphQL API

FHIR-aware GraphQL endpoint at https://api.medplum.com/fhir/R4/$graphql. Supports typed nested queries, reverse-reference traversal (_reference), FHIRPath-style array filtering,...

GRAPHQL

Medplum API pricing

Prices published by Medplum, read 2026-10-28 from www.medplum.com/pricing.

Plan	Price
Free	$0/month Includes: For prototyping and learning. Medplum-hosted, 1 custom domain, 3 access policies (testing only), Dis
Production	Starts at $2,000/month Includes: Medplum-hosted, 5 custom domains, 2,000 concurrent WebSocket connections, 10 access policies, includ
Premium	Starts at $6,000/month Includes: Medplum-hosted, 10 custom domains, 5,000 concurrent WebSocket connections, 20 access policies, large
Enterprise	Contact Us Includes: Hosted or self-hosted, per-agreement SLA and support channels

Plan details, limits and sources →

Rate limits

Login Endpoints: 5 requests per minute
Auth and OAuth2 Endpoints: 160 requests per minute
Default Request Rate — Free: 6000 requests per minute

Compiled by API Evangelist, not yet checked against Medplum's documentation. All 4 limits →

Billed by: subscription · FinOps profile →

Pricing Plans 2

Published pricing tiers and plan structures.

Medplum Plans Pricing

4 plans

PLANS

Medplum Price Estimates

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Medplum Rate Limits

4 limits

RATE LIMITS

Service Levels 1

Uptime the provider promises or reports, as SLA4OAI. Read from its own pages; APIs.io runs no monitors.

Medplum

SLA

FinOps 1

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

Medplum Finops

FINOPS

Features 9

Notable capabilities this provider offers.

FHIR-Native Datastore

PostgreSQL-backed datastore that natively models FHIR R4 resources, including search, history, and versioning.

REST + GraphQL APIs

Dual API surface — FHIR REST and FHIR-aware GraphQL — sharing the same authorization, schema, and access policies.

Bots (Serverless TypeScript Functions)

AWS Lambda-style TypeScript functions executed by Subscriptions, HTTP, or cron triggers; the integration backbone of Medplum.

Subscriptions (Webhooks + Websockets)

FHIR Subscription resources dispatch real-time notifications when matching resources change.

Access Policies

Declarative resource- and field-level authorization rules attached to ProjectMembership.

SMART on FHIR + OAuth 2.0

Standards-based authentication and authorization, supporting SMART App Launch 2.0.0 and Bulk Data 2.0.0.

TypeScript SDK and React Components

@medplum/core, @medplum/react, and @medplum/react-hooks provide typed client and reusable UI primitives.

On-Premise Agent

Bridges local clinical systems (HL7v2, DICOM, MLLP) to Medplum cloud.

AWS CDK Deployment

First-class CDK constructs for self-hosting Medplum on AWS.

Scroll for all 9

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Medplum Webhooks

ASYNCAPI

Semantic Vocabularies 1

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

Medplum Context

18 classes · 2 properties

JSON-LD

Spectral Rules 2

Spectral governance rulesets for linting and validating these APIs.

Medplum — jsonschema rules

5 rules · 3 warnings 2 info

SPECTRAL

Medplum API Rules

5 rules · 4 warnings 1 info

SPECTRAL

OpenAPI Overlays 2

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Medplum Fhir Api Overlay

5 actions · documentation · medplum-fhir-api-openapi.yml

DERIVED

Medplum Fhir Api Phrasing Overlay

9 actions · phrasing · medplum-fhir-api-openapi.yml

GENERATED

JSON Schema 9

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

Bot

28 properties

JSON SCHEMA

Condition

34 properties

JSON SCHEMA

Encounter

32 properties

JSON SCHEMA

MedicationRequest

43 properties

JSON SCHEMA

Observation

46 properties

JSON SCHEMA

Organization

19 properties

JSON SCHEMA

Patient

27 properties

JSON SCHEMA

Practitioner

19 properties

JSON SCHEMA

Subscription

16 properties

JSON SCHEMA

Scroll for all 9

JSON Structure 1

JSON Structure definitions describing this provider's data shapes.

Medplum Patient Structure

8 properties

JSON STRUCTURE

Examples 5

Example request and response payloads for these APIs.

Medplum Bot Hl7 To Fhir Example

6 fields

EXAMPLE

Medplum Graphql Patient Query Example

4 fields

EXAMPLE

Medplum Observation Bloodpressure Example

7 fields

EXAMPLE

Medplum Patient Create Example

7 fields

EXAMPLE

Medplum Subscription Webhook Example

6 fields

EXAMPLE

Security Posture 4

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

Medplum Authentication

http/openIdConnect/oauth2 (SMART App Launch 2.0.0, not declared in OpenAPI securitySchemes) · 4 schemes

SECURITY

Medplum Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Medplum Vulnerability Disclosure

no policy recorded

SECURITY

Medplum Trust Center

SOC 2, HIPAA, GDPR, CSA STAR

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Medplum Scopes

12 scopes · authorizationCode/clientCredentials

12 scopes

SCOPES

Agentic Access 1

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

Medplum Agentic Access

8 operations · 4 acting

AGENTIC

Use Cases 7

What developers build with this provider.

Custom EHR Development

Build custom electronic health records on top of FHIR-native storage and React UI components.

Patient Engagement Portals

Ship patient-facing portals using SMART on FHIR auth and the Medplum React component library.

AI Scribe and Clinical Documentation

Capture clinical notes, run them through LLM pipelines via Bots, and persist structured FHIR resources.

HL7v2 to FHIR Integration

Receive legacy HL7v2 ADT, ORU, and SIU messages via the on-premise Agent and convert them to FHIR with Bots.

Population Health and Analytics

Use Bulk Data 2.0 exports and GraphQL aggregations for cohort and population-level analysis.

Care Management Workflows

Model longitudinal care plans, tasks, and questionnaires with FHIR-native resources.

Revenue Cycle Automation

Automate claim, coverage, and explanation-of-benefit workflows with Bots and Subscriptions.

Scroll for all 7

Integrations 8

Pre-built integrations with other platforms and tools.

AWS

First-class deployment on AWS via CDK, with Bots running on Lambda and storage on RDS PostgreSQL.

HL7v2

Bidirectional HL7v2 messaging via the Medplum on-premise Agent.

FHIRcast

Real-time clinical-context synchronization protocol support.

Stripe

Billing and payment integration examples for revenue cycle.

Twilio

SMS, voice, and messaging integration patterns via Bots.

DocuSeal / DocuSign

Patient consent and document-signing integration examples.

SendGrid / Mailgun

Transactional email integration patterns via Bots.

AWS HealthLake

Cross-platform FHIR data exchange examples.

Scroll for all 8

Solutions 6

Packaged solutions this provider offers.

Custom EHR

Build production EHR systems on top of Medplum.

Patient Portal

Reference patient-facing portal application.

Provider Portal

Reference provider-facing clinical application.

AI-Powered Clinical Scribe

Solution pattern for LLM-driven clinical documentation pipelines.

Population Health Platform

Solution pattern for cohort identification and outcome tracking.

Revenue Cycle Management

Solution pattern for automating claims, coverage, and billing workflows.

Resources

Get Started 2

Portal, sign-up, and the first successful call

GettingStarted

GettingStarted

Console

Console

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 5

MCP servers, agent skills, and machine-readable catalogs

MCPServer

AgenticAccess

WellKnown

LLMsTxt

AgentSkill

Design & Contract 22

Pagination, idempotency, versioning, errors, and events

Spectral

Spectral

Arazzo

Arazzo

Arazzo

Arazzo

Arazzo

Arazzo

Arazzo

Arazzo

SpectralRules

Vocabulary

JSONLD

Conformance

ErrorCatalog

Lifecycle

Conventions

Idempotency

Components

DataModel

Webhooks

Scroll for all 22

Build 11

SDKs, sample code, and the tooling you integrate with

IntegrationEdges

PostmanWorkspace

SDKs

SDKs

SDKs

CLI

GitHubOrganization

GitHubRepository

Packages

ToolCrosswalk

CLI

Scroll for all 11

Access & Security 8

Authentication, authorization, and security posture

SecurityPolicy

SecurityPolicy

TrustCenter

TrustCenter

VulnerabilityDisclosure

VulnerabilityDisclosure

DomainSecurity

Authentication

Authentication

Compliance

OAuthScopes

Scroll for all 8

Operate 9

Status, limits, changes, and where to get help

IssueTracker

Releases

Support

Discord

RateLimits

StatusPage

Deprecation

ChangeLog

Roadmap

Scroll for all 9

Commercial 6

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

License

Plans

FinOps

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 7

Properties that don't map to a standard resource type

Hosts

Vendors

CapabilityMap

APICatalog

CapabilityStatement

CapabilityStatement

SMARTConfiguration

SMARTConfiguration

Overlay

Overlay

Scroll for all 7

Source (apis.yml)

aid: medplum
name: Medplum
description: Medplum is an Apache 2.0 open-source, FHIR-native developer platform for shipping clinical software. It bundles
  a FHIR R4 datastore, REST and GraphQL APIs, a TypeScript SDK, React component library, OAuth 2.0 / SMART on FHIR authentication,
  declarative Access Policies, Subscriptions, and TypeScript-based serverless Bots — sold as a hosted service at api.medplum.com
  and as a self-hostable monorepo on GitHub. Medplum is HIPAA, SOC 2 Type II, and ONC-certified.
type: Index
deliveryModel:
  model: open-core
  license: Apache-2.0
  license_evidence:
    repo: medplum/medplum
    spdx: Apache-2.0
    url: https://github.com/medplum/medplum/blob/main/LICENSE.txt
    stars: 2703
  open_source: true
  commercial: true
  callable_host: true
  label: Open core · an OSS project plus a commercial hosted product
  confidence: medium
  source:
  - openapi
  - pricing
  - repository-license
  generated: '2026-09-25'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: false
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  - scopes
  - security
  generated: '2026-11-06'
  method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/medplum.png
x-docs-platform: docusaurus
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-10-04
tags:
- Healthcare
- FHIR
- Open Source
- Developer Platform
- HIPAA
- SMART on FHIR
- Clinical
- Interoperability
tags_raw:
- Healthcare
- FHIR
- Open Source
- Developer Platform
- HIPAA
- SMART on FHIR
- Clinical
- Interoperability
- Open-Source
url: https://raw.githubusercontent.com/api-evangelist/medplum/refs/heads/main/apis.yml
created: '2026-05-25'
modified: '2026-10-11'
specificationVersion: '0.23'
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
common:
- type: IntegrationEdges
  url: integrations/medplum-integration-edges.yml
- type: Spectral
  url: rules/medplum-rules.yml
- type: Spectral
  url: rules/medplum-jsonschema-spectral-rules.yml
- type: Hosts
  url: hosts/medplum-hosts.yml
- type: Vendors
  url: vendors/medplum-vendors.yml
- type: CapabilityMap
  url: capabilities/medplum-capability-edges.yml
  name: Medplum Business Capability Map
- type: IssueTracker
  url: https://github.com/medplum/medplum/issues
- type: Releases
  url: https://github.com/medplum/medplum/releases
- type: SecurityPolicy
  url: https://github.com/medplum/medplum/blob/main/SECURITY.md
- type: MCPServer
  url: mcp/medplum-mcp.yml
- type: AgenticAccess
  url: agentic-access/medplum-agentic-access.yml
- type: TrustCenter
  url: security/medplum-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/medplum-vulnerability-disclosure.yml
- type: DomainSecurity
  url: security/medplum-domain-security.yml
- type: Authentication
  url: authentication/medplum-authentication.yml
- type: PostmanWorkspace
  url: https://www.postman.com/kinlaneapi/medplum/overview
- type: Arazzo
  url: arazzo/medplum-amend-resource-with-history-workflow.yml
  name: Medplum Amend Resource With History
- type: Arazzo
  url: arazzo/medplum-create-diagnostic-report-workflow.yml
  name: Medplum Create Diagnostic Report
- type: Arazzo
  url: arazzo/medplum-deploy-and-run-bot-workflow.yml
  name: Medplum Deploy Bot
- type: Arazzo
  url: arazzo/medplum-finalize-observation-workflow.yml
  name: Medplum Finalize Observation
- type: Arazzo
  url: arazzo/medplum-find-and-delete-resource-workflow.yml
  name: Medplum Find And Delete Resource
- type: Arazzo
  url: arazzo/medplum-register-patient-with-observation-workflow.yml
  name: Medplum Register Patient With Observation
- type: Arazzo
  url: arazzo/medplum-schedule-encounter-workflow.yml
  name: Medplum Schedule Encounter
- type: Arazzo
  url: arazzo/medplum-upsert-patient-workflow.yml
  name: Medplum Upsert Patient
- type: Website
  url: https://www.medplum.com
- type: Documentation
  url: https://www.medplum.com/docs
- type: GettingStarted
  url: https://www.medplum.com/docs/tutorials
- type: APIReference
  url: https://www.medplum.com/docs/api
- type: Authentication
  url: https://www.medplum.com/docs/auth
- type: SDKs
  url: https://www.medplum.com/docs/sdk/core
- type: SDKs
  url: https://www.npmjs.com/package/@medplum/core
- type: SDKs
  url: https://www.npmjs.com/package/@medplum/react
- type: CLI
  url: https://www.medplum.com/docs/cli
- type: Console
  url: https://app.medplum.com
- type: Pricing
  url: https://www.medplum.com/pricing
- type: TermsOfService
  url: https://www.medplum.com/terms
- type: PrivacyPolicy
  url: https://www.medplum.com/privacy
- type: Blog
  url: https://www.medplum.com/blog
- type: GitHubOrganization
  url: https://github.com/medplum
- type: GitHubRepository
  url: https://github.com/medplum/medplum
- type: Support
  url: mailto:support@medplum.com
- type: Discord
  url: https://discord.gg/medplum
- type: License
  url: https://www.apache.org/licenses/LICENSE-2.0
- type: SpectralRules
  url: rules/medplum-rules.yml
- type: Vocabulary
  url: vocabulary/medplum-vocabulary.yml
- type: JSONLD
  url: json-ld/medplum-context.jsonld
- type: Plans
  url: plans/medplum-plans-pricing.yml
- type: RateLimits
  url: rate-limits/medplum-rate-limits.yml
- type: FinOps
  url: finops/medplum-finops.yml
- type: Packages
  url: packages/medplum-packages.yml
- type: WellKnown
  url: well-known/medplum-well-known.yml
- type: ToolCrosswalk
  url: mcp/medplum-tool-crosswalk.yml
- type: LLMsTxt
  url: llms/medplum-llms.txt
- type: APICatalog
  url: well-known/medplum-api-catalog.json
- type: CapabilityStatement
  url: fhir/medplum-fhir-r4-capabilitystatement.json
- type: SMARTConfiguration
  url: fhir/medplum-smart-configuration.json
- type: Overlay
  url: overlays/medplum-fhir-api-overlay.yaml
- type: Conformance
  url: conformance/medplum-conformance.yml
- type: Compliance
  url: https://www.medplum.com/docs/compliance
- type: ErrorCatalog
  url: errors/medplum-problem-types.yml
- type: Lifecycle
  url: lifecycle/medplum-lifecycle.yml
- type: StatusPage
  url: https://status.medplum.com
- type: Deprecation
  url: https://www.medplum.com/docs/compliance/alpha-beta
- type: OAuthScopes
  url: scopes/medplum-scopes.yml
- type: Conventions
  url: conventions/medplum-conventions.yml
- type: Idempotency
  url: conventions/medplum-conventions.yml
- type: ChangeLog
  url: changelog/medplum-changelog.yml
- type: CLI
  url: cli/medplum-cli.yml
- type: Components
  url: components/medplum-components.yml
- type: DataModel
  url: data-model/medplum-data-model.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Webhooks
  url: asyncapi/medplum-webhooks.yml
- type: Roadmap
  url: https://github.com/orgs/medplum/projects/1
- type: Features
  data:
  - name: FHIR-Native Datastore
    description: PostgreSQL-backed datastore that natively models FHIR R4 resources, including search, history, and versioning.
  - name: REST + GraphQL APIs
    description: Dual API surface — FHIR REST and FHIR-aware GraphQL — sharing the same authorization, schema, and access
      policies.
  - name: Bots (Serverless TypeScript Functions)
    description: AWS Lambda-style TypeScript functions executed by Subscriptions, HTTP, or cron triggers; the integration
      backbone of Medplum.
  - name: Subscriptions (Webhooks + Websockets)
    description: FHIR Subscription resources dispatch real-time notifications when matching resources change.
  - name: Access Policies
    description: Declarative resource- and field-level authorization rules attached to ProjectMembership.
  - name: SMART on FHIR + OAuth 2.0
    description: Standards-based authentication and authorization, supporting SMART App Launch 2.0.0 and Bulk Data 2.0.0.
  - name: TypeScript SDK and React Components
    description: '@medplum/core, @medplum/react, and @medplum/react-hooks provide typed client and reusable UI primitives.'
  - name: On-Premise Agent
    description: Bridges local clinical systems (HL7v2, DICOM, MLLP) to Medplum cloud.
  - name: AWS CDK Deployment
    description: First-class CDK constructs for self-hosting Medplum on AWS.
- type: UseCases
  data:
  - name: Custom EHR Development
    description: Build custom electronic health records on top of FHIR-native storage and React UI components.
  - name: Patient Engagement Portals
    description: Ship patient-facing portals using SMART on FHIR auth and the Medplum React component library.
  - name: AI Scribe and Clinical Documentation
    description: Capture clinical notes, run them through LLM pipelines via Bots, and persist structured FHIR resources.
  - name: HL7v2 to FHIR Integration
    description: Receive legacy HL7v2 ADT, ORU, and SIU messages via the on-premise Agent and convert them to FHIR with Bots.
  - name: Population Health and Analytics
    description: Use Bulk Data 2.0 exports and GraphQL aggregations for cohort and population-level analysis.
  - name: Care Management Workflows
    description: Model longitudinal care plans, tasks, and questionnaires with FHIR-native resources.
  - name: Revenue Cycle Automation
    description: Automate claim, coverage, and explanation-of-benefit workflows with Bots and Subscriptions.
- type: Integrations
  data:
  - name: AWS
    description: First-class deployment on AWS via CDK, with Bots running on Lambda and storage on RDS PostgreSQL.
  - name: HL7v2
    description: Bidirectional HL7v2 messaging via the Medplum on-premise Agent.
  - name: FHIRcast
    description: Real-time clinical-context synchronization protocol support.
  - name: Stripe
    description: Billing and payment integration examples for revenue cycle.
  - name: Twilio
    description: SMS, voice, and messaging integration patterns via Bots.
  - name: DocuSeal / DocuSign
    description: Patient consent and document-signing integration examples.
  - name: SendGrid / Mailgun
    description: Transactional email integration patterns via Bots.
  - name: AWS HealthLake
    description: Cross-platform FHIR data exchange examples.
- type: Solutions
  data:
  - name: Custom EHR
    description: Build production EHR systems on top of Medplum.
  - name: Patient Portal
    description: Reference patient-facing portal application.
  - name: Provider Portal
    description: Reference provider-facing clinical application.
  - name: AI-Powered Clinical Scribe
    description: Solution pattern for LLM-driven clinical documentation pipelines.
  - name: Population Health Platform
    description: Solution pattern for cohort identification and outcome tracking.
  - name: Revenue Cycle Management
    description: Solution pattern for automating claims, coverage, and billing workflows.
- type: ArazzoWorkflows
  workflows:
  - url: arazzo/medplum-amend-resource-with-history-workflow.yml
    name: Medplum Amend Resource With History
    summary: Read a resource, update it, then inspect its version history and prior version.
  - url: arazzo/medplum-clinical-data-query-workflow.yml
    name: Medplum Clinical Data Query
    summary: Locate a patient by name, read the Patient resource, then pull that patient's Observations.
  - url: arazzo/medplum-create-diagnostic-report-workflow.yml
    name: Medplum Create Diagnostic Report
    summary: Create an Observation result, then assemble a DiagnosticReport that references it.
  - url: arazzo/medplum-deploy-and-run-bot-workflow.yml
    name: Medplum Deploy Bot
    summary: Create a Bot resource, then create a Subscription that invokes the Bot on resource changes.
  - url: arazzo/medplum-fhir-resource-crud-workflow.yml
    name: Medplum FHIR Resource CRUD
    summary: Create a FHIR R4 resource, read it back by id, update it, then search the resource type for it.
  - url: arazzo/medplum-finalize-observation-workflow.yml
    name: Medplum Finalize Observation
    summary: Find a preliminary Observation, patch its status to final, and read it back to confirm.
  - url: arazzo/medplum-find-and-delete-resource-workflow.yml
    name: Medplum Find And Delete Resource
    summary: Search a resource type, and if a match is found read it for audit then delete it.
  - url: arazzo/medplum-register-patient-with-observation-workflow.yml
    name: Medplum Register Patient With Observation
    summary: Create a Patient, then record a vital-sign Observation that references that patient.
  - url: arazzo/medplum-resource-versioning-workflow.yml
    name: Medplum FHIR Resource Versioning
    summary: Create a FHIR resource, update it to mint a new version, read its history, then read a specific version.
  - url: arazzo/medplum-schedule-encounter-workflow.yml
    name: Medplum Schedule Encounter
    summary: Create a Practitioner, create an Encounter linking the patient and practitioner, then read it back.
  - url: arazzo/medplum-upsert-patient-workflow.yml
    name: Medplum Upsert Patient
    summary: Search for a Patient by identifier and update it if found, otherwise create it.
apis:
- aid: medplum:medplum-graphql-api
  name: Medplum GraphQL API
  description: FHIR-aware GraphQL endpoint at https://api.medplum.com/fhir/R4/$graphql. Supports typed nested queries, reverse-reference
    traversal (_reference), FHIRPath-style array filtering, and access-policy enforcement at the field level.
  humanURL: https://www.medplum.com/docs/graphql
  baseURL: https://api.medplum.com/fhir/R4/$graphql
  tags:
  - GraphQL
  - FHIR
  - Healthcare
  properties:
  - type: Documentation
    url: https://www.medplum.com/docs/graphql
  - type: Examples
    url: examples/medplum-graphql-patient-query-example.json
  - url: graphql/medplum-graphql.md
    type: GraphQL
- aid: medplum:medplum-bots
  name: Medplum Bots
  description: Bots are TypeScript serverless functions (AWS Lambda-style) executed in response to FHIR Subscriptions, HTTP
    triggers, or scheduled cron. Bots are the backbone of Medplum integrations — HL7v2 to FHIR conversion, document generation,
    webhook fan-out, and questionnaire-driven workflow automation.
  humanURL: https://www.medplum.com/docs/bots
  tags:
  - Bots
  - Automation
  - Serverless
  - Integration
  properties:
  - type: Documentation
    url: https://www.medplum.com/docs/bots
  - type: JSONSchema
    url: json-schema/medplum-bot-schema.json
  - type: Examples
    url: examples/medplum-bot-hl7-to-fhir-example.json
- aid: medplum:medplum-subscriptions
  name: Medplum Subscriptions
  description: FHIR Subscription resources that match a search criteria and dispatch real-time notifications via REST hooks
    (webhooks) or Websockets when matching resources are created or updated. Subscriptions are the primary trigger for Bots
    and external system integrations.
  humanURL: https://www.medplum.com/docs/subscriptions
  tags:
  - Subscription
  - Webhook
  - FHIR
  - Event
  tags_raw:
  - Subscriptions
  - Webhooks
  - FHIR
  - Events
  properties:
  - type: Documentation
    url: https://www.medplum.com/docs/subscriptions
  - type: Examples
    url: examples/medplum-subscription-webhook-example.json
- aid: medplum:medplum-fhir-api
  name: Medplum Fhir API
  description: 'Medplum''s FHIR R4 REST API, as described by its own OpenAPI (https://api.medplum.com/openapi.json): batch/transaction,
    search, create (incl. conditional create via If-None-Exist), conditional update (upsert), $validate, read, update, patch,
    delete and history; OAuth2 / OpenID Connect, bearer and basic security schemes.'
  humanURL: https://www.medplum.com/docs/api
  baseURL: https://api.medplum.com/fhir/R4
  tags:
  - FHIR
  tags_raw:
  - Fhir
  properties:
  - type: OpenAPI
    url: openapi/medplum-fhir-api-openapi.yml
  - type: CapabilityStatement
    url: fhir/medplum-fhir-r4-capabilitystatement.json
  - type: SMARTConfiguration
    url: fhir/medplum-smart-configuration.json
  - type: Documentation
    url: https://www.medplum.com/docs/api
  - type: APIReference
    url: https://www.medplum.com/docs/api
  - type: Authentication
    url: https://www.medplum.com/docs/auth
  - type: RateLimits
    url: https://www.medplum.com/docs/rate-limits
  - type: MCPServer
    url: mcp/medplum-mcp.yml
  - type: ToolCrosswalk
    url: mcp/medplum-tool-crosswalk.yml
  - type: Documentation
    url: https://www.medplum.com/docs/ai/mcp
  - type: JSONSchema
    url: json-schema/medplum-patient-schema.json
  - type: JSONSchema
    url: json-schema/medplum-observation-schema.json
  - type: JSONSchema
    url: json-schema/medplum-encounter-schema.json
  - type: JSONSchema
    url: json-schema/medplum-practitioner-schema.json
  - type: JSONSchema
    url: json-schema/medplum-organization-schema.json
  - type: JSONSchema
    url: json-schema/medplum-condition-schema.json
  - type: JSONSchema
    url: json-schema/medplum-medicationrequest-schema.json
  - type: JSONSchema
    url: json-schema/medplum-subscription-schema.json
  - type: JSONStructure
    url: json-structure/medplum-patient-structure.json
  - type: Examples
    url: examples/medplum-patient-create-example.json
  - type: Examples
    url: examples/medplum-observation-bloodpressure-example.json
  - type: Examples
    url: examples/medplum-subscription-webhook-example.json
x-enrichment:
  date: 2026-10-12
  status: enriched
  artifacts_added: 3
  pass: local-v5

Medplum API — frequently asked questions

Does Medplum have an API?

Yes. APIs.io lists 4 APIs from Medplum, including Medplum GraphQL API, Medplum Bots and Medplum Subscriptions, and 1 more.

Is there an OpenAPI specification for the Medplum API?

Yes. APIs.io indexes 1 OpenAPI specification for Medplum, each linked for download from this page.

How do I authenticate with the Medplum API?

Medplum documents its authentication (http/openIdConnect/oauth2 (SMART App Launch 2.0.0, not declared in OpenAPI securitySchemes) · 4 schemes). The details are profiled on APIs.io as Medplum Authentication.

How much does the Medplum API cost?

Medplum publishes its prices; its Free plan is $0/month as of 2026-10-28. APIs.io lists 4 pricing plans for Medplum, with each plan's price, limits and inclusions under Pricing on this page.

Does Medplum have an MCP server?

Yes. APIs.io lists 1 MCP server for Medplum: Official hosted Medplum MCP server. Exposes the Medplum FHIR API to AI clients through a single general-purpose FHIR request tool plus two client-compatibility shims, authenticated with OAuth 2.0 agai

Is the Medplum API ready for AI agents?

Medplum has a Kin Score of 77.4 out of 100 (exemplar) and an Agent Readiness score of 55.8 (agent-ready), 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/medplum"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/medplum/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.