Academy / Week 2 / SyncApp Architecture — High Level / High Level Overview — SyncApp Architecture & Write-backs

High Level Overview — SyncApp Architecture & Write-backs

Lesson 7.1 ⏱ ~8 min Week 2

💡 Why This Matters

Understanding the full bidirectional flow — data in from PMS and data written back to PMS — sets the context for all the more detailed architecture lessons that follow. This overview shows you the big picture before diving into individual components.

🎯 What You'll Learn

  • The two main SyncApp types: on-prem (pulls from local DB) and cloud (pulls via REST API)
  • How Data Service acts as the central repository consumed by all Weave UI clients
  • What 'write-back' (rightback) means: writing Weave UI changes back to the PMS
  • Specific write-back features: patient updates (demographics), payments, appointment scheduling, forms
  • How forms write-back works end-to-end: patient submits digital form → Weave → PMS (demo with Dentrix)

▶ Watch Video

Open in Google Drive 💡 Open in Drive for AI-powered transcript search and summaries

📋 Lesson Summary

SyncApp has two deployment modes: on-prem (runs on client machine, pulls from local DB) and cloud (runs as a pod, pulls via REST API). Both feed data into Data Service, which powers the Weave UI for mobile and desktop users. Write-backs (also called 'rightbacks') are the reverse flow — changes made in the Weave UI that must be written back into the PMS. Write-back use cases include patient demographic updates, payment recording, appointment scheduling/cancellation, and digital forms. A live Dentrix demo shows a new patient created via form submission appearing in both Weave and the PMS database.

🏷 Key Concepts

On-Prem SyncAppCloud SyncAppData Service RepositoryWrite-back (Rightback)Patient Write-backPayment Write-backSchedule Write-backForms Write-backBidirectional Data Flow

⭐ Key Takeaways

01SyncApp is bidirectional: pulling data in AND writing changes out to the PMS
02Data Service is the central store — all Weave UI data comes from here, not directly from PMS
03Write-backs are triggered by user actions in the Weave UI (e.g., editing a patient's phone number)
04Forms write-back is the most complex: it creates/updates both Weave records AND PMS database entries
05On-prem write-backs write directly to the SQL database; cloud write-backs use the PMS's POST APIs
← Back to Module High Level Architecture Overview — ICPA,… →