Overview
This article explains how the Admit Alert to KIPU workflow sends patient data to KIPU EMR and how facility routing is handled. You do not need to create a separate workflow for each facility — the global KIPU integration mapping handles facility routing automatically in the background.
Before You Begin
Your KIPU EMR integration must already be configured in Dazos. See How to Integrate Dazos CRM with KIPU EMR for setup instructions.
You need admin access to CRM Settings and Workflows.
Confirm that your global EMR integration mapping is set up correctly (Treatment Programs, LOC, and other field mappings).
How Facility Routing Works
When the Admit Alert workflow triggers, Dazos uses the global KIPU integration mapping to determine which facility a patient record should be routed to. This happens automatically based on how your Treatment Programs and LOC fields are mapped in your EMR settings — no additional conditions or per-facility workflows are required.
⚠️ Important: Do not create separate workflows per facility or add multiple facility conditions to a single workflow. One workflow with a single condition (Send Admit Alert = Yes) is all that is needed.
Workflow Configuration
Your Admit Alert to KIPU workflow should be configured as follows:
Navigate to Settings > CRM Settings > Workflows.
Open or create the workflow named Admit Alert to KIPU.
Set the Recurrence to Every time conditions are met. This means the workflow will trigger and attempt to push data to KIPU every time the record is saved.
Set a single condition: Send Admit Alert = Yes.
Ensure the workflow is set to Active and save.
💡 Tip: Because the workflow triggers on every save, make sure all required fields are populated before saving the record to avoid a failed push to KIPU.
Required Fields Before Saving
Because the workflow triggers every time the record is saved, KIPU will reject the data payload if any of the following required fields are missing at the time of save. Ensure all of the fields below are populated before saving:
Demographics
Name
Treatment Program
Admission Date
Admitting to LOC
Date of Birth (DOB)
⚠️ Warning: If any of these fields are missing when the record is saved, KIPU may reject the push. Always complete these fields before saving to ensure a clean sync.
Verification / Expected Result
When the workflow runs successfully:
The patient record is pushed to KIPU EMR automatically upon save.
KIPU routes the record to the correct facility based on the global integration mapping.
No manual facility selection or additional workflow conditions are needed.
✅ Success Indicator: The patient data appears in the correct facility within your KIPU EMR instance after the record is saved in Dazos.
Troubleshooting / Common Errors
KIPU rejects the data or the patient does not appear in KIPU:
Verify that all required fields (Demographics, Name, Treatment Program, Admission Date, Admitting to LOC, DOB) are filled in before saving.
Confirm the workflow condition is set to Send Admit Alert = Yes and the workflow status is Active.
Check that your global EMR integration mapping is configured correctly in Settings > CRM Settings > Integration > EMR Settings.
Patient routes to the wrong facility:
Review your Treatment Program and LOC mapping in the KIPU EMR settings. Facility routing is driven by these mappings, not by workflow conditions.
Contact Dazos Support if the mapping appears correct but routing is still incorrect.