Creating a Cloud SyncApp from the Weave Portal
Why This Matters
Understanding the customer-facing flow for connecting a PMS to Weave helps you empathize with the customer experience and understand how the SyncApp gets provisioned from the Weave side. This flow ends with you overriding data verification as a developer.
What You'll Learn
- The customer-facing path: Settings → Data Sync → Add Integration → Select PMS → Enter credentials
- What the Office ID (GEO ID) is for InfiniteVT and where customers get it
- What happens in WAM immediately after a customer submits their sync request
- Why data needs to be 'verified' after a SyncApp is created (and how devs can manually override this)
- How to confirm the SyncApp is running and data is flowing by checking patient counts in WAM
Watch Video
Lesson Summary
From the Weave portal, an office goes to Settings → Data Sync → Add Integration, selects their PMS (InfiniteVT), and enters their Office ID (GEO ID). After submitting, WAM shows a new data source with a generated SourceId and begins syncing data. However, the data isn't immediately visible in the Weave portal because it's pending verification. Developers can manually override this in WAM ('Manually Override') to immediately verify the data. Once verified, patients appear in the Weave UI. This entire flow represents one SyncApp being spun up for one office.