What Integrations Does Technically
Why This Matters
Watching a data change made in the PMS appear in Weave 15 minutes later (or immediately when triggered manually) makes the synchronization pipeline tangible. This lesson gives you the visceral understanding of what SyncApp does.
What You'll Learn
- How SyncApp syncs data on a ~15-minute interval by default
- A live demo of changing a patient's phone number and birth date in InfiniteVT (PMS) and watching it update in Weave
- How to manually trigger a sync using the VAM portal (Sync Patient + Send Diffs)
- Why data changes in the PMS are NOT immediately reflected in Weave
- The concept of SyncApp as a periodic background service
Watch Video
Open in Google Drive
💡 Open in Drive for AI-powered transcript search and summaries
Lesson Summary
A live demo using the InfiniteVT PMS demonstrates the 15-minute sync cycle. A patient's phone number and birth date are changed in the PMS, but Weave still shows the old values — until a manual sync is triggered via the VAM developer portal (using Sync Patient + Send Diffs). After the manual trigger, the updated values appear immediately in Weave. Under normal operation, this would happen automatically every ~15 minutes, with the exact interval varying by PMS.
Key Concepts
SyncApp
15-Minute Sync Cycle
Manual Sync Trigger
VAM Portal
Sync Patient
Send Diffs
InfiniteVT PMS
Data Lag
Key Takeaways
01Data in Weave is always slightly behind the PMS — the delay is typically ~15 minutes under normal operation
02VAM's 'Sync Patient' + 'Send Diffs' lets developers manually trigger a sync for a specific entity
03Changes in the PMS require a full sync cycle before appearing in Weave — this is by design, not a bug
04The 15-minute interval is a default that can vary by PMS — some sync more frequently, some less
05For debugging data discrepancies, always check when the last sync ran before assuming a bug