Practice Fusion

Practice Fusion is effectively read-only for third-party integrators. There is no write API for clinical data, no scheduling API, no webhooks, and the developer onboarding path is unclear.

High complexityNo self-serveFHIR R4 (read-only)PDS (C-CDA)

FHIR Version

R4 (4.0.1)

Rate Limit

Not published — PDS API enforces HTTP 429

Sandbox

None documented

ONC Certified

Yes

Capability Matrix

Capability	Read	Write
Patients	No self-serve developer portal. Access requires direct engagement.
Appointments
Encounters	No self-serve developer portal. Access requires direct engagement.
Clinical Notes	No self-serve developer portal. Access requires direct engagement.
Document Upload
Lab Results	No self-serve developer portal. Access requires direct engagement.
Medications	No self-serve developer portal. Access requires direct engagement.
Allergies	No self-serve developer portal. Access requires direct engagement.
Conditions	No self-serve developer portal. Access requires direct engagement.
Immunizations	No self-serve developer portal. Access requires direct engagement.
Vitals	No self-serve developer portal. Access requires direct engagement.

Billing / Claims
Coverage / Insurance
Referrals
Bulk Data Export	No self-serve developer portal. Access requires direct engagement.	—
Events / Webhooks		—

DocumentedNot documentedSelf-serveGatedPartner only

Integration considerations

No write API for any clinical data — read-only system for third-party integrators
No scheduling or appointment API exists
No webhooks or event-driven integration capability
PDS API portal exists (pfpds.practicefusion.com) but requires registration. No public sandbox available.
FHIR base URLs are published in ServiceBaseURLs.json, linked from the vendor's FHIR Get Started page (practicefusion.com/fhir/get-started/).
Practice Fusion has multiple API surfaces (FHIR R4 and a separate PDS API). This Explorer page documents the FHIR R4 API.