DOV — Data Owner Verification & Multi-Office PMS
Why This Matters
DOV is a non-obvious but critical concept for multi-office PMS scenarios. Large PMS vendors often give Weave a single API token that can access data for dozens of offices. Without DOV, a new SyncApp could inadvertently access another office's patient data. Understanding DOV protects both data integrity and legal compliance.
What You'll Learn
- Why DOV exists: large PMS vendors give Weave access to multi-office databases, requiring verification of which offices we're authorized to sync
- The scenario: Weave has 70+ PMS partnerships, and enterprise PMS vendors provide single-token access to multiple offices
- How DOV works: when connecting a new SyncApp, the system verifies the office is in the authorized list before syncing
- What 'multi-office PMS' means and how it relates to the SourceTenantId concept from Week 1
- The services involved in the DOV verification flow
Watch Video
Lesson Summary
When Weave partners with large enterprise PMS vendors, those vendors often provide access tokens that cover multiple dental/medical offices in their database. Without Data Owner Verification (DOV), Weave could sync data for offices that didn't sign up for Weave — a compliance and privacy violation. DOV is the process that checks, when a new SyncApp is created, whether the office being onboarded is in the authorized list from the PMS vendor. This connects directly to the multi-source location architecture covered in Week 1 Module 3.