FHIR® Developer Sandbox
Overview
The Practice Fusion Developer Sandbox provides a shared testing environment for third-party app developers integrating with Practice Fusion’s FHIR API. Practice Fusion supports two patient portals—Patient Fusion and FollowMyHealth—allowing you to integrate with either or both. Note that separate app registrations are required for each patient portal.
This sandbox provides test patients and service base URLs for testing:
- Patient apps integrating with FollowMyHealth
- Patient apps integrating with Patient Fusion
- System apps integrating with Practice Fusion (bulk data access)
Prerequisites
- App Approval: Your application must be approved and available in the Practice Fusion App Marketplace
- Production Credentials: You must use your production credentials to access the sandbox environment
Patient Apps
Patient apps access individual patient data through OAuth 2.0 authorization code grant type via either Patient Fusion or FollowMyHealth portals.
FollowMyHealth
Test Service Base URL:
https://api.practicefusion.com/fhir/fmh/r4/v1/0f4bdecd-1549-4acf-8255-2012323dc667
Test Service Base URL:
| Username | Password |
|---|---|
| sophia32875 | Bl@zz1n9 |
| jorge67485 | Bl@zz1n9 |
| anita23474 | Bl@zz1n9 |
| markchen345325 | Bl@zz1n9 |
| thom5 | Bl@zz1n9 |
| louinferno | Bl@zz1n9 |
| daisy4364 | Bl@zz1n9 |
| henry2345 | Bl@zz1n9 |
Note: The first six patients contain realistic health data and conditions. The last three patients have data specifically designed to pass all Inferno Single Patient API tests with complete FHIR resource/US Core profile coverage.
Patient Fusion
Test Service Base URL:
https://api.patientfusion.com/fhir/r4/v1/b930bc01-3a8d-4b26-99ba-c1560177876b
Test Patient Credentials:
| Username | Password |
|---|---|
| Eddie501 | Bl@zz1n9 |
| becky09 | Bl@zz1n9 |
| mitchell499 | Bl@zz1n9 |
| amina185 | Bl@zz1n9 |
| vance254 | Bl@zz1n9 |
| martin896 | Bl@zz1n9 |
Note: The first six patients contain realistic health data and conditions. The last patient has data specifically designed to pass all Inferno Single Patient API tests with complete FHIR resource/US Core profile coverage.
System Apps
System apps can access any patient data for a given practice in the Practice Fusion EHR. These apps use the OAuth 2.0 client credentials grant type with a signed JWT that includes a Client ID (no secret is required, though the JWT should be signed with a key whose public portion is published via a JWKS URL that is registered for the app).
To use Practice Fusion’s bulk FHIR export API, an app must be registered as a system app.
Test Service Base URL:
https://api.practicefusion.com/fhir/r4/v1/0f4bdecd-1549-4acf-8255-2012323dc667
Bulk Data Testing Group ID:
6f637d01-06bc-4fde-a45b-ae2ab741b91f
This group references all nine test patients in the FollowMyHealth environment and contains both realistic patient data and Inferno test case-compliant data for comprehensive bulk data export testing.
Limitations
- Provider Apps: Provider applications and EHR app launches are not currently supported in the sandbox
- Periodic Resets: This shared sandbox will be periodically reset to default settings, which may result in changes to test patient logins, group IDs, and other information. Documentation will be updated to reflect any changes.
- Shared Access: Other developers may access the same test data in this shared environment
Best Practices
- Comprehensive Testing: For patient apps, test with both realistic data patients (first six) and Inferno-compliant patients (last three) to ensure complete coverage
- Bulk Data Validation: For system apps, you can use the provided Group ID to validate group based bulk export functionality across different data types
- Authentication Flow: Ensure you’re implementing the correct OAuth 2.0 flow—authorization code for patient apps, client credentials for system apps
- Credential Security: Protect your production credentials even in the sandbox environment
- Documentation Updates: Check this documentation periodically for any changes due to sandbox resets
Additional Resources
For complete API specifications and technical documentation, visit: FHIR API Specifications | Practice Fusion