Overview
This guide explains what to do when insurance field data is not pushing from Dazos CRM to your KIPU EMR. This issue is commonly caused by insurance fields being hidden in the CRM interface layout, which prevents the data from being included in the KIPU sync payload.
Symptom
When pushing a patient record to KIPU EMR, insurance information does not appear in the KIPU patient chart. The integration may otherwise appear to be working correctly — demographics or other fields may transfer successfully — but insurance data is consistently missing.
Cause
Fields that are hidden from the CRM interface layout are excluded from the data payload sent to KIPU. Even if the insurance data exists in the system, hidden fields will not be included in the sync and will not map over to the EMR.
This is not a connection or webhook issue — the integration itself can be functioning correctly while hidden fields are silently blocked from transferring.
Solution
Navigate to your CRM layout settings for the relevant module (e.g., Intake Opportunities or the Insurance section).
Review the layout to identify any insurance-related fields that are currently set to hidden.
Make the insurance fields visible in the interface layout.
Save the layout changes.
Re-push the patient record to KIPU EMR and verify that the insurance data now transfers correctly.
⚠️ Important: Any field hidden from the CRM interface layout will be excluded from the KIPU data payload — regardless of whether data exists for that field. Fields must be visible in the layout to sync.
Verification / Expected Result
After making the insurance fields visible and re-pushing the record, the insurance data should appear correctly in the KIPU patient chart. Check the KIPU Incoming queue or the patient's chart to confirm the insurance details have mapped over.
✅ Success indicator: Insurance information (such as payer name, policy details, or related fields) is visible within the patient record in KIPU after the push.
Escalation
Contact Dazos Support if:
Insurance fields are visible in the layout but data is still not syncing to KIPU.
You are unsure which fields in your layout correspond to the insurance data being blocked.
You need assistance reviewing your KIPU webhook logs to identify specific payload errors.
💡 Tip: When contacting support, provide the name of the patient record used for testing and a screenshot of your current CRM layout showing the insurance fields.