If you don’t already have an App created with Fullscript, sign in to the Fullscript API Dashboard and click Create Application (or continue to sign up if you’re brand new to us!). For initial development, target one of our sandbox servers (either US or Canadian).
You’ll need an application name (currently used for your information only), and a redirect uri where we will send users once they have authorized your app’s request to access their Fullscript data.
Both the application name and redirect uri can be edited later, so there’s no need to agonize over those decisions now.
The Fullscript.js integration process needs the following OAuth scopes:
Clinic:readClinic:writePatients:writePatients:treatment_plan_historyConfigure your app to use these via the Fullscript API Dashboard's OAuth scopes settings for your App. Don’t forget to save your changes.
Create one or more test practitioners by clicking the Create Test Account button on the right side of your App’s page in the Fullscript API Dashboard. For now, choose Skip when asked to upload certifications for your new test users. Stop when you get to the authorization screen for your new user. It requires you to have your redirect endpoint available. We’ll get to that in a few more steps.
When you create test practitioners as described above, they are automatically approved and there’s no need to upload fake certifications for your test users.
You’ll also need at least one test patient for your integration. Use the Patient Sign Up link from your practitioner’s welcome email, or log in to the Fullscript App as the practitioner, then select Patients > New Patient.
Here are the practitioner login links for the Fullscript sandbox Apps: