Office Data and SyncApp — Multi-Source Architecture
Why This Matters
Real enterprise customers don't have just one database. Understanding how an organization's data can span multiple sources — each with data for multiple locations — is the foundation for understanding why we need three separate identifiers.
What You'll Learn
- How a single organization can have multiple separate data sources (databases)
- How each database can contain patient and appointment data for multiple physical locations
- Why SyncApp needs one instance per data source, not one per location
- How SyncApp tags each synced record with its source location for granular tracking
- Why this architecture is described as 'complicated' — it took the presenter 6+ months to understand
Watch Video
Lesson Summary
Large organizations may have data distributed across multiple databases. Each database may contain records for multiple physical locations. Because SyncApp syncs from a single source, you need one SyncApp per data source — not per location. If an organization has 3 data sources, 3 SyncApps are spun up. When each SyncApp pushes data into Weave, it tags every record with the source location so Weave knows which physical location the data belongs to. This location-tagged data becomes the building block for all UI configuration.