Provision Flow — Validate Credentials
Why This Matters
Credential validation is the first thing that runs in every provision call. Understanding how each PMS validates its credentials (typically a test API call) helps you implement validation correctly for new integrations.
What You'll Learn
- How the provisioner interface requires a Provision method that implements the ordered steps
- Step 1: Authorize and validate PMS credentials by making a lightweight test API call
- How DentalEMR validates: calls a 'get practices' API with the submitted office practice ID
- Integration partner codes and how they're assigned (auto-increment per PMS)
- The metadata structure: field name, display name, value type, step description, integration type (cloud/on-prem/unknown)
- What the subsequent steps are: create SyncApp credentials, set DentalEMR settings, create cloud SyncApp
Watch Video
Open in Google Drive
💡 Open in Drive for AI-powered transcript search and summaries
Lesson Summary
The first step in every provision flow is credential validation. For DentalEMR, this means calling the 'get practices' API with the submitted office practice ID. If the API returns a response, the credentials are valid. This pattern (make a lightweight API call to verify credentials) is the standard approach for all cloud PMS integrations. After validation passes, the flow proceeds to create SyncApp credentials (data source), add PMS-specific settings, and spin up the SyncApp process.
Key Concepts
Credential Validation StepTest API Call PatternDentalEMR Practice IDProvisioner StepsIntegration Partner CodeCloud vs On-Prem TypeMetadata Field Structure
Key Takeaways
01Always validate credentials first — never proceed to create a data source with unvalidated credentials
02The validation pattern is consistent: make a lightweight, read-only API call with the submitted credentials
03Choose a 'get' API for validation — avoid APIs that create or modify data as part of the credential check
04Each provisioner step should be atomic — if validation fails, nothing else runs
05Document your validation API choice in the provisioner's Steps method for future reference