Symptom/Error
When pushing patient records from Dazos to KIPU EMR, patients are being assigned to the wrong location or campus. For example, patients intended for the Palm City location are instead appearing under a campus file or a different treatment program in KIPU.
This typically occurs during urgent transfers when staff need patients to appear in the correct KIPU location immediately.
Cause
This issue is caused by a mapping discrepancy in the KIPU integration settings. The system uses location mapping to determine which KIPU location/program the patient should be sent to during the transfer process.
When the mapping is incorrect or incomplete, KIPU defaults patient records to a fallback location rather than the intended treatment program.
Solution
Follow these steps to identify and correct the location mapping issue:
Review the treatment program/location mapping
Navigate to the KIPU integration settings in your Dazos CRMVerify the correct location mapping
Confirm that the Dazos treatment program is properly mapped to the correct KIPU locationUpdate the mapping configuration
Correct any mapping discrepancies found between the Dazos treatment program and the intended KIPU destinationTest the patient transfer
Re-attempt pushing a patient record to KIPU to confirm the correct location is now being applied
Expected Result: The patient record should now appear in the correct KIPU location/treatment program instead of defaulting to the wrong campus or location.
⚠️ Note: The mapping correction takes effect immediately for new transfers. Previously transferred patients will need to be manually moved within KIPU if they were sent to the wrong location.
Escalation
Contact Dazos support if:
You cannot locate the KIPU integration settings or location mapping options
The mapping appears correct but patients are still being sent to the wrong location
You need assistance identifying which treatment programs should map to which KIPU locations
The issue persists after updating the mapping configuration



