Write clear step by step documentation for your users. Include screenshots.
Email us when you've completed your integration. Include information for us to login to your system and test the integration from our end.
We usually only accept integrations with commercial patient management systems / EHRs that have at least 500 practitioners. We make exceptions for larger practices (50+ practitioners who subscribe to Physitrack) who have in-house patient management systems.
Depending on the commercial relationship between your system and Physitrack, we may ask you to sign an API Usage Agreement before granting you access to our API.
1. Single Sign On (SSO)
This is our most basic type of integration. Robust, easy to implement and very convenient for the practitioner: the practitioner logs in to Physitrack and adds/opens the client with one click. The RESTful integration (3 & 4) builds on the SSO integration.
Authentication is through a shared secret (your system generates a token which is added to the practitioner's account in Physitrack). We also support OAuth, with your system being the OAuth provider.
The practitioner clicks a UI control in your UI (e.g. "Open client in Physitrack").
This then triggers an HTTP POST request from your system to Physitrack with the required data.
Physitrack then returns a 302 to the practitioner's browser, redirecting them to the client.
If you'd like to enrich your system with core Physitrack functionality, such as assigning templates to patients, or if you'd like to automatically get patient adherence data from Physitrack into your system, Physitrack's RESTful API and event model allow for many possibilities.
For authentication, Physitrack uses both the pattern described in option 1 (SSO) where Physitrack stores your system's secret and generates an API token for each practitioner which is stored in your system as a shared secret. More on authentication for our RESTful API.
Events We can register various webhooks for you to listen to events. You can combine this with our RESTful endpoints to add a high degree of synchronicity between Physitrack and your system. Read about our events.
5. Your system loads Physitrack inside an iframe
Our iframe integration lets you load Physitrack's UI into an iframe that sits in your UI, at the same time authenticating the practitioner and adding (or opening) the client. This type of integration is possible if you have a web-based system with ample space in your UI to accommodate an iframe that is at least 990 px wide.
For authentication, Physitrack uses either OAuth or the SSO pattern (see 1. above).
Your system loads Physitrack with a JWT parameter for further authentication.
The client in context is automatically added or opened.
Physitrack can optionally prepare a "dashboard" view that is loaded as the default state in the iframe.
Physitrack® is a registered Trademark of Physitrack Limited. Physitrack is a fitness and wellness tool and does not guarantee outcomes in a rehabilitation process. For more information, contact your healthcare provider. Patent pending.