Prerequisites
Before you begin, make sure you have:
An active Dazos CRM instance with the Leads module in use
A KIPU EMR integration that is configured and active
An existing SSN field already present on the Accounts module
Access to submit a Dazos Support ticket
Overview
By default, the SSN (Social Security Number) field in Dazos CRM lives on the Account record and is used when pushing patient data to KIPU. If your team collects information at the Lead stage — for example, during an initial admissions inquiry — you may want to capture SSN on the Lead form so it carries through automatically when the Lead is converted to an Account, and then pushes to KIPU as expected.
This end-to-end flow requires a backend configuration that maps the SSN field from the Leads module to the existing SSN field on Accounts. Do not create a new, duplicate SSN field — this can cause data conflicts and will not connect to the existing KIPU field mapping. Instead, contact Dazos Support to have the correct mapping configured.
Steps
Do not create a new SSN field. If you add a separate SSN field to the Leads module on your own, it will not automatically map to the existing Account SSN field, and it will not push to KIPU. Using a duplicate field can result in two SSN fields on your records, which causes confusion and data integrity issues.
Contact Dazos Support and request that the existing SSN field be configured to work end-to-end from Leads → Accounts → KIPU. Describe that you want to:
Capture SSN at the Lead stage
Have that value auto-map to the Account's existing SSN field on lead conversion
Have the SSN push to KIPU as it normally would from the Account
Support will configure the backend mapping. The Dazos Support team will set up the Lead Conversion Data Mapping so that the SSN field on Leads maps directly to the existing SSN field on Accounts — using the existing field, not a new one.
Test with a sample Lead. Once Support confirms the configuration is complete, submit a test Lead with an SSN value entered. Convert the Lead to an Account and verify the SSN appears on the Account record. Then push the Account to KIPU and confirm the SSN is present on the patient's facesheet in KIPU.
Result
After the mapping is configured by Support, SSN entered on a Lead will automatically carry over to the Account when the Lead is converted, and will push to the KIPU facesheet as part of the standard patient push — all using the existing SSN field with no duplicate fields created.
⚠️ Important: This configuration must be set up by Dazos Support on the backend. Attempting to resolve this by creating a new SSN field in the Leads module will not achieve the desired result and may complicate your data.
💡 Tip: Always test the full flow — Lead submission → Lead conversion → Account → KIPU push — with a sample record before using it with live patient data.