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 publishes 4 APIs on the APIs.io network. Tagged areas include Company, Healthcare, Electronic Health Records, EHR, and FHIR.

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 📡 Source on GitHub
59.0/100 strong ▲ 12.4 Agent 43/100 agent ready Full breakdown ↓
scored 2026-08-17 · rubric v0.11.0
AccessSelf serve
4 APIs 1 MCP Servers
CompanyHealthcareElectronic Health RecordsEHRFHIRInteroperabilityMedicalHealth ITSMART on FHIRClinical Data

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 59.0/100 · strong
Contract Quality 8.5 / 21
Developer Ergonomics 10.4 / 17
Commercial Clarity 15.7 / 17
Operational Transparency 5.2 / 11
Governance 1.3 / 10
Discoverability 6.9 / 9
Regulatory Posture 11.1 / 15
Agent readiness — 43/100 · agent ready
Machine-Readable Contract 18 / 18
Agentic Access Contract 0 / 10
MCP Server 12 / 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
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.
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/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. This rating is computed from github.com/api-evangelist/practice-fusion: open an issue to ask a question, or submit a pull request to add artifacts. Want it done for you? Prioritized profiling — $2,500 →

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.

MCP Servers 1

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

practice-fusion-mcp.yml

MCP SERVER

Pricing Plans 1

Published pricing tiers and plan structures.

Practice Fusion Plans Pricing

8 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Practice Fusion Rate Limits

0 limits

RATE LIMITS

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
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
 MCPServer
MCPServer
 LLMsTxt
LLMsTxt
 AgentSkill
AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conformance
Conformance
 ErrorCatalog
ErrorCatalog
 Lifecycle
Lifecycle
 Conventions
Conventions
 Idempotency
Idempotency
 DataModel
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
DomainSecurity
 Authentication
Authentication
 OAuthScopes
OAuthScopes
 Compliance
Compliance
 TrustCenter
TrustCenter
 VulnerabilityDisclosure
VulnerabilityDisclosure
 Security
Security

Scroll for all 7

Operate 5

Status, limits, changes, and where to get help

Support
Support
 StatusPage
StatusPage
 RateLimits
RateLimits
 ChangeLog
ChangeLog
 Support
Support

Commercial 5

Pricing, plans, and the legal terms of use

Pricing
Pricing
 TermsOfService
TermsOfService
 PrivacyPolicy
PrivacyPolicy
 Plans
Plans
 TermsOfService
TermsOfService

Company 2

The organization behind the API

Website
Website
 Blog
Blog

Source (apis.yml)

apis.yml Raw ↑ 
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
accessModel:
  pricing: unknown
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  label: Self-serve signup
  confidence: medium
  source:
  - authentication
  generated: '2026-07-22'
  method: derived
image: https://www.practicefusion.com/assets/img/practice-fusion-logo.png
specificationVersion: '0.20'
created: '2026-07-17'
modified: '2026-08-14'
tags:
- 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: MCPServer
  url: mcp/practice-fusion-mcp.yml
- 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