Overview
Before the Sunwave integration with Dazos CRM can be configured and activated, a specific set of information and access credentials must be requested from the customer's Sunwave account. This article walks you through every item you need to collect and why each one matters.
This setup is required for every new Sunwave integration. Without these items, the integration cannot be properly configured and data will not sync correctly between Sunwave and Dazos CRM.
Step 1 — Request Full Admin Access to Sunwave
To configure the integration, Dazos needs a dedicated integration account inside Sunwave with full platform access. Request the following from the customer's Sunwave administrator or their Sunwave account representative:
Location Alias — The unique identifier for the customer's facility or location inside Sunwave. This is used to scope all API calls to the correct account.
Email Address with Integration Access — Use integrations@dazos.com as the email address that should be granted access. Ask the customer's Sunwave admin to invite this email with full admin-level permissions.
Client ID — A unique Client ID is required for each account/location. Request one Client ID per facility the customer operates in Sunwave.
Secret Key — The Secret Key paired with the Client ID. This is used to authenticate all API requests from Dazos to Sunwave. Store this securely — never share it publicly.
⚠️ Important: The Client ID and Secret Key are unique per account. If the customer has multiple facilities, you will need a separate Client ID and Secret Key for each one.
Step 2 — Confirm Document Storage Location
Dazos can push documents (such as VOB results) into Sunwave on behalf of the customer. Before enabling this, confirm:
Which folder inside Sunwave documents should be stored in (e.g., a specific patient documents tab or upload folder configured in the customer's Sunwave instance).
Note: Sunwave must also enable the "Dazos Uploads" tab on their end before document pushing will work. Remind the customer to request this from their Sunwave support rep.
Step 3 — Collect Discharge Types
Sunwave uses specific Discharge Type values to categorize how a patient left treatment. You need the full list of Discharge Types configured in the customer's Sunwave instance so they can be mapped to the corresponding values in Dazos CRM.
Ask the customer or Sunwave support to provide the full list of all active Discharge Types.
These are configured in Dazos under: Settings → CRM Settings → Integrations → EMR Settings → Sunwave → EMR Mapping Entities
Step 4 — Collect Admitted Status Values
Sunwave tracks patient admission statuses (e.g., Admitted, Discharged, Waitlist, No Show). You need the full list of Admitted Status values used in the customer's Sunwave instance to create the correct field mapping in Dazos.
Request all active Admitted Status options from the customer or Sunwave support.
Each status must be mapped in Dazos so that status changes in Sunwave sync correctly to Dazos CRM opportunity stages.
Step 5 — Collect Insurance List with Legacy IDs
This is one of the most critical steps. Sunwave identifies insurance payers using internal Legacy IDs. These IDs must be added to each insurance record inside Sunwave before the integration can correctly sync