Question 1 of 3
What is ICPA and what problem does it solve?
AA caching layer that stores PMS data locally to reduce API calls
BA proxy that monitors and throttles API calls to PMS partners to comply with rate limits and contracts
CAn authentication service that validates PMS credentials before SyncApp starts
DA dashboard tool for visualizing sync status across all offices
Question 2 of 3
In the V3 write-back architecture, how do product teams (e.g., scheduling team) trigger a write-back?
AThey call the SyncApp directly via a WebSocket connection
BThey import the 'Integrations Platform' library which calls the SyncApp Manager directly
CThey send a message to NSQ which the SyncApp Writebacks service consumes
DThey make a REST call to the SyncApp API which routes to the correct SyncApp
Question 3 of 3
What is the upsert mechanism in SyncApp API, and why is it used instead of separate create/update calls?
AUpsert encrypts data before sending — it's a security measure
BUpsert checks if data exists; if yes it updates, if no it inserts — simplifying the caller's logic
CUpsert batches multiple records into a single API call for efficiency
DUpsert is only used for patient data; appointments use standard create/update