01
BAA before PHI
The public fit check asks for practice-level workflow information, not patient data. A Business Associate Agreement and implementation scope come before production PHI access.
Security & PHI posture
Trust comes from the rollout details—not a badge.
DrSupport supports operational work inside dental practice systems. Before that work touches PHI, we document the workflow, access boundary, responsible people, and BAA path with the practice.
02
Role-scoped credentials
Access is limited to the systems and queues required for the agreed workflow. Practices retain control of account provisioning, permissions, and offboarding.
03
Customer-specific review
Security and compliance depend on the actual people, tools, permissions, and workflow in a rollout. We review those details with each practice instead of relying on a marketing badge.
04
Narrow rollout first
We begin with a defined queue, owner, measurement window, and escalation path. Broader access is considered only after the first workflow is working as intended.
What we do not ask you to assume
Marketing language is not a substitute for vendor review.
- • No PHI through public marketing forms.
- • No certification should be inferred unless a current report is provided.
- • No workflow goes live without practice approval and scoped access.
- • No clinical or billing judgment is delegated beyond the agreed process.
Review the actual implementation before you decide.
Ask for the proposed workflow, access matrix, BAA path, escalation policy, and any current security documentation relevant to your practice.