Salesforce
Overview
The Zus Salesforce integration consists of two main components:
Back-end data connection: Allows Zus to call the Salesforce REST API to fetch patient demographics from the Account endpoint and patient outreach calls via the query endpoint.
Embedded ZAP UI: Enables viewing the ZAP directly within a Salesforce patient record page.
Data Flows
Single Patient Backfill
The backfill endpoint accepts a Salesforce Account ID and loads patient demographics into a FHIR Patient resource in Zus, along with patient outreach calls as FHIR Encounter resources. This process is automatically triggered when the embedded ZAP is launched within Salesforce.
Patients are marked as active (enabling data sharing through Zus' Common Patient Record) based on custom logic configured per customer.
Poller
Zus polls the Salesforce query API every 15 minutes for outreach call tasks that were modified in the last 15 minutes. This ensures lower latency in retrieving outreach data. These rely on custom logic configured per customer.
Zus polls the Salesforce query API every 15 minutes for person accounts modified in the last 15 minutes.
Authentication and Authorization
When the embedded ZAP launches in Salesforce, the app authenticates with Salesforce and receives an access token. This token is verified against the Salesforce API and exchanged for a Zus access token. If the user doesn't exist in Zus, they're created with a Care Team User role.
Updated 2 days ago