Practice Fusion

Practice Fusion is a cloud-based electronic health record (EHR) platform for independent ambulatory medical practices, serving roughly 6.4% of U.S. ambulatory practices with more than 43 million clinical records and around 5 million patient visits per month. Its developer surface centers on an ONC Certified Health IT FHIR R4 (Patient Data Sharing / PDS) API implementing US Core 6.1.0, SMART App Launch 2.0.0, and Bulk Data Access 1.0.1 over SMART-on-FHIR OAuth2, alongside proprietary bi-directional Labs and Imaging APIs and a partner marketplace of 600+ integrated companies.

Practice Fusion is listed with 4 APIs on the APIs.io network. Tagged areas include Company, Healthcare, Electronic Health Records, FHIR, and Interoperability.

Practice Fusion’s developer surface includes authentication, documentation, API reference, getting-started guide, support, signup flow, engineering blog, and 32 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

56.9/100 strong ▬ flat Agent 38/100 agent ready Front door AI 1/6 silent Heartbeat 0/100 dormant saas Full breakdown ↓
scored 2026-11-06 · rubric v0.27.0 · Show this score on your site →

AccessFreemiumSelf serveFree trial⚡ Free to try

4 APIs 4 Agent Skills

Company Healthcare Electronic Health Records FHIR Interoperability Medical Health IT SMART on FHIR Clinical Data

Kin Score

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

Composite quality — 56.9/100 · strong

Contract Quality 6.9 / 21

Developer Ergonomics 9.6 / 17

Access Clarity 14.1 / 17

Operational Transparency 4.9 / 11

Contract Governance 1.9 / 10

Discoverability 6.7 / 9

Regulatory Posture 6.9 / 15

Agent readiness — 38/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 9 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 0 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 0 / 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 0 / 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.

Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% 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/practice-fusion/"><img src="https://apis.io/badge/practice-fusion/card.svg" alt="Practice Fusion 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
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link
Typed Event Surface +6 pts — AsyncAPI document, OR webhooks/callbacks objects in the as-published OpenAPI, OR common[].type includes Webhooks
Documented Reversibility +6 pts — a reversal operation in the contract, graded up when a window is documented too

5 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 32.3 — up to +16.9 composite points
Contract Governance scores 18.2 — up to +9.8 composite points
Developer Ergonomics scores 56.5 — up to +8.7 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/practice-fusion/apis.yml: open an issue on github.com/api-evangelist/practice-fusion 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
Medical Technology (certified health IT, FDA-authorized AI devices)	regulated	62.0	-	-
E-Prescribing (pharmacy, e-prescribing, medication data)	regulated	62.0	-	-
Certified Health IT (health IT accreditation and certification registers)	regulated	62.0	-	-
FHIR Implementation Guides (HL7 FHIR package and IG publishers)	regulated	62.0	-	-

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 3

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

Dynamic Client Registration

measured — observed by APIs.io (published)

APIs 4

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

Practice Fusion FHIR API (Patient Data Sharing)

ONC Certified FHIR R4 (v4.0.1) API implementing US Core 6.1.0, SMART App Launch 2.0.0, and Bulk Data Access 1.0.1. Provides read and search access across 47 FHIR resource types ...

Practice Fusion Patient Fusion PHR API

Patient-facing personal health record API documented in the PDS API Developer Guide. Serves a patient their own clinical documents and record data from the Practice Fusion EHR, ...

Practice Fusion Labs API

Proprietary bi-directional laboratory integration API connecting practices with 300+ independent, hospital, and health-system labs including Labcorp, Quest Diagnostics, RadNet, ...

Practice Fusion Imaging API

Proprietary bi-directional imaging integration API for order receipt and study transmission across imaging providers, supporting 100,000+ medical professionals.

Agent Skills 4

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

Run a Practice Fusion FHIR Bulk Data group export

AGENT SKILL

Retrieve clinical documents and provenance from Practice Fusion

AGENT SKILL

Connect to a Practice Fusion FHIR endpoint with SMART on FHIR

AGENT SKILL

Assemble a patient chart summary from Practice Fusion

AGENT SKILL

Practice Fusion API pricing

Prices published by Practice Fusion, read 2026-10-28 from www.practicefusion.com/pricing/.

Plan	Price
Practice Fusion EHR	199/month per provider Includes: 3 signing staff licenses & unlimited non-signing staff licenses; required annual commitment
Free trial	complimentary 2-week trial Includes: No commitment, no risk

Plan details, limits and sources →

Billed by: provider · FinOps profile →

Pricing Plans 1

Published pricing tiers and plan structures.

Practice Fusion Plans Pricing

2 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Practice Fusion Rate Limits

0 limits

RATE LIMITS

FinOps 1

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

Practice Fusion Finops

FINOPS

Security Posture 4

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

Practice Fusion Authentication

oauth2/openIdConnect/mutualTLS · 3 schemes

SECURITY

Practice Fusion Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Practice Fusion Vulnerability Disclosure

Hackerone · security.txt · contact published

SECURITY

Practice Fusion Trust Center

SOC 2 Type 2, EHNAC accreditation, EPCS certification, ISO 9001:2015, ONC Certification Rule (Certified Health IT), HIPAA

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Practice Fusion Scopes

OAuth 2.0 · no documented scopes

0 scopes

SCOPES

Resources

Get Started 5

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Login

DeveloperPortal

DeveloperPortal

Documentation 3

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Documentation

Documentation

Agent Surfaces 4

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

Idempotency

DataModel

Build 2

SDKs, sample code, and the tooling you integrate with

Packages

Packages

GitHubOrganization

GitHubOrganization

Access & Security 7

Authentication, authorization, and security posture

DomainSecurity

Authentication

OAuthScopes

Compliance

TrustCenter

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

Scroll for all 7

Operate 5

Status, limits, changes, and where to get help

Support

StatusPage

RateLimits

ChangeLog

Support

Commercial 5

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

Plans

TermsOfService

Company 2

The organization behind the API

Website

Website

Blog

Blog

Source (apis.yml)

aid: practice-fusion
name: Practice Fusion
description: Practice Fusion is a cloud-based electronic health record (EHR) platform for independent ambulatory medical practices,
  serving roughly 6.4% of U.S. ambulatory practices with more than 43 million clinical records and around 5 million patient
  visits per month. Its developer surface centers on an ONC Certified Health IT FHIR R4 (Patient Data Sharing / PDS) API implementing
  US Core 6.1.0, SMART App Launch 2.0.0, and Bulk Data Access 1.0.1 over SMART-on-FHIR OAuth2, alongside proprietary bi-directional
  Labs and Imaging APIs and a partner marketplace of 600+ integrated companies.
url: https://raw.githubusercontent.com/api-evangelist/practice-fusion/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- battery-ventures
x-tier: stub
x-tier-reason: portfolio-lead
x-enrichment:
  date: '2026-08-14'
  status: enriched
  artifacts_added: 13
  pass: local-v1
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: false
  label: Hosted service · you call their endpoint
  confidence: medium
  source:
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: freemium
  onboarding: self-serve
  trial: true
  try_now: true
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Freemium (free trial) · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  - scopes
  - rate-limits
  - security
  generated: '2026-11-06'
  method: derived
image: https://www.practicefusion.com/assets/img/practice-fusion-logo.png
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-08-14'
tags:
- Company
- Healthcare
- Electronic Health Records
- FHIR
- Interoperability
- Medical
- Health IT
- SMART on FHIR
- Clinical Data
tags_raw:
- Company
- Healthcare
- Electronic Health Records
- EHR
- FHIR
- Interoperability
- Medical
- Health IT
- SMART on FHIR
- Clinical Data
apis:
- name: Practice Fusion FHIR API (Patient Data Sharing)
  description: ONC Certified FHIR R4 (v4.0.1) API implementing US Core 6.1.0, SMART App Launch 2.0.0, and Bulk Data Access
    1.0.1. Provides read and search access across 47 FHIR resource types (Patient, Observation, Condition, Encounter, MedicationRequest,
    DiagnosticReport, DocumentReference, and more) via SMART-on-FHIR OAuth2 (authorization code, client credentials, refresh
    token). Provider/System access and Patient (FMH) access endpoints are provisioned per practice organization.
  humanURL: https://www.practicefusion.com/fhir/
  baseURL: https://api.practicefusion.com/fhir/r4/v1/
  properties:
  - type: Documentation
    url: https://www.practicefusion.com/fhir/api-specifications/
  - type: APIReference
    url: https://www.practicefusion.com/fhir/api-specifications/
  - type: GettingStarted
    url: https://www.practicefusion.com/fhir/get-started/
  - type: Authentication
    url: authentication/practice-fusion-authentication.yml
  - type: OAuthScopes
    url: scopes/practice-fusion-scopes.yml
  - type: WellKnown
    url: well-known/practice-fusion-well-known.yml
  - type: SmartConfiguration
    url: well-known/practice-fusion-smart-configuration.json
  - type: CapabilityStatement
    url: conformance/practice-fusion-capability-statement.json
  - type: AgentSkill
    url: skills/_index.yml
  - type: RateLimits
    url: rate-limits/practice-fusion-rate-limits.yml
  - type: ErrorCatalog
    url: errors/practice-fusion-problem-types.yml
  - type: DataModel
    url: data-model/practice-fusion-data-model.yml
- name: Practice Fusion Patient Fusion PHR API
  description: 'Patient-facing personal health record API documented in the PDS API Developer Guide. Serves a patient their
    own clinical documents and record data from the Practice Fusion EHR, authorized with OAuth 2.0 plus OpenID Connect through
    the Patient Fusion identity provider at auth.patientfusion.com, which publishes a full OIDC/RFC 8414 discovery document
    anonymously. Distinct from the FHIR PDS API: it uses a proprietary JSON surface with its own status-code table (including
    300 Multiple Choices for an ambiguous patient match) rather than FHIR OperationOutcome.'
  humanURL: https://www.practicefusion.com/pds-api/developer-guide/
  baseURL: https://api2.practicefusion.com/phr/patient/v1
  properties:
  - type: Documentation
    url: https://www.practicefusion.com/pds-api/developer-guide/
  - type: Authentication
    url: authentication/practice-fusion-authentication.yml
  - type: OpenIDConnect
    url: https://auth.patientfusion.com/.well-known/openid-configuration
  - type: WellKnown
    url: well-known/practice-fusion-well-known.yml
  - type: RateLimits
    url: rate-limits/practice-fusion-rate-limits.yml
  - type: ErrorCatalog
    url: errors/practice-fusion-problem-types.yml
- name: Practice Fusion Labs API
  description: Proprietary bi-directional laboratory integration API connecting practices with 300+ independent, hospital,
    and health-system labs including Labcorp, Quest Diagnostics, RadNet, SimonMed, and Rayus for lab order transmission and
    results delivery.
  humanURL: https://www.practicefusion.com/practice-fusion-apis/
  baseURL: https://www.practicefusion.com/labs-documentation/
  properties:
  - type: Documentation
    url: https://www.practicefusion.com/labs-documentation/
  - type: APIReference
    url: https://www.practicefusion.com/assets/pdfs/HL7-Ordering-API-Developer-Guide-v1.5.pdf
  - type: Specification
    url: https://www.practicefusion.com/assets/pdfs/HL7-Order-Specification-v1.5.pdf
  - type: Documentation
    url: https://www.practicefusion.com/assets/pdfs/HL7-2.5.1-Lab-Results-API-Developer-Guide.pdf
  - type: Documentation
    url: https://www.practicefusion.com/assets/pdfs/HL7-2.3-Lab-Results-API-Developer-Guide.pdf
  - type: GettingStarted
    url: https://www.practicefusion.com/assets/pdfs/Practice-Fusion-API-Client-Installation-and-Usage-Guide-for-Windows.pdf
- name: Practice Fusion Imaging API
  description: Proprietary bi-directional imaging integration API for order receipt and study transmission across imaging
    providers, supporting 100,000+ medical professionals.
  humanURL: https://www.practicefusion.com/practice-fusion-apis/
  baseURL: https://www.practicefusion.com/imaging-documentation/
  properties:
  - type: Documentation
    url: https://www.practicefusion.com/imaging-documentation/
  - type: APIReference
    url: https://www.practicefusion.com/assets/pdfs/HL7-Ordering-API-Developer-Guide.pdf
  - type: Documentation
    url: https://www.practicefusion.com/assets/pdfs/HL7-Radiology-Results-API-Developer-Guide-2.5.1.pdf
  - type: GettingStarted
    url: https://www.practicefusion.com/assets/pdfs/Practice-Fusion-API-Client-Installation-and-Usage-Guide-for-Windows.pdf
common:
- type: DomainSecurity
  url: security/practice-fusion-domain-security.yml
- type: Authentication
  url: authentication/practice-fusion-authentication.yml
- type: OAuthScopes
  url: scopes/practice-fusion-scopes.yml
- type: WellKnown
  url: well-known/practice-fusion-well-known.yml
- type: Conformance
  url: conformance/practice-fusion-conformance.yml
- type: Compliance
  url: https://www.practicefusion.com/onc-certified-ehr/
- type: ErrorCatalog
  url: errors/practice-fusion-problem-types.yml
- type: Lifecycle
  url: lifecycle/practice-fusion-lifecycle.yml
- type: Conventions
  url: conventions/practice-fusion-conventions.yml
- type: Idempotency
  url: conventions/practice-fusion-conventions.yml
- type: DataModel
  url: data-model/practice-fusion-data-model.yml
- type: X-MCPServerCandidate
  url: mcp/practice-fusion-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: LLMsTxt
  url: llms/practice-fusion-llms.txt
- type: Website
  url: https://www.practicefusion.com/
- type: DeveloperPortal
  url: https://www.practicefusion.com/fhir/
- type: Documentation
  url: https://www.practicefusion.com/fhir/api-specifications/
- type: APIReference
  url: https://www.practicefusion.com/fhir/api-specifications/
- type: GettingStarted
  url: https://www.practicefusion.com/fhir/get-started/
- type: Support
  url: https://partnersupport.practicefusion.com/s/
- type: SignUp
  url: https://pfpds.practicefusion.com/s/Registration
- type: Blog
  url: https://www.practicefusion.com/blog/
- type: Pricing
  url: https://www.practicefusion.com/pricing/
- type: StatusPage
  url: https://status.practicefusion.com/
- type: TermsOfService
  url: https://www.practicefusion.com/pages/terms-of-use.html
- type: PrivacyPolicy
  url: https://www.practicefusion.com/pages/privacy-policy.html
- type: Packages
  url: packages/practice-fusion-packages.yml
- type: Plans
  url: plans/practice-fusion-plans-pricing.yml
- type: RateLimits
  url: rate-limits/practice-fusion-rate-limits.yml
- type: ChangeLog
  url: changelog/practice-fusion-changelog.yml
- type: AgentSkill
  url: skills/_index.yml
- type: TrustCenter
  url: security/practice-fusion-trust-center.yml
- type: VulnerabilityDisclosure
  url: security/practice-fusion-vulnerability-disclosure.yml
- type: Security
  url: https://veradigm.com/legal/security-program/
- type: GitHubOrganization
  url: https://github.com/practicefusion
- type: Login
  url: https://static.practicefusion.com/apps/ehr/
- type: DeveloperPortal
  url: https://www.practicefusion.com/developer-center/
- type: Documentation
  url: https://www.practicefusion.com/pds-api/developer-guide/
- type: TermsOfService
  url: https://www.practicefusion.com/pds-api/termsofservice/
- type: Support
  url: https://help.practicefusion.com/s/article/using-fhir-in-practice-fusion
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io

Practice Fusion API — frequently asked questions

Does Practice Fusion have an API?

Yes. APIs.io lists 4 APIs from Practice Fusion, including Practice Fusion FHIR API (Patient Data Sharing), Practice Fusion Patient Fusion PHR API and Practice Fusion Labs API, and 1 more.

How do I authenticate with the Practice Fusion API?

Practice Fusion documents its authentication (oauth2/openIdConnect/mutualTLS · 3 schemes). The details are profiled on APIs.io as Practice Fusion Authentication.

How much does the Practice Fusion API cost?

Practice Fusion publishes its prices; its Practice Fusion EHR plan is 199/month per provider as of 2026-10-28. APIs.io lists 2 pricing plans for Practice Fusion, with each plan's price, limits and inclusions under Pricing on this page.

Is the Practice Fusion API ready for AI agents?

Practice Fusion has a Kin Score of 56.9 out of 100 (strong) and an Agent Readiness score of 37.6 (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/practice-fusion"

All providers

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

Every operation they expose

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

How their score was established

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