Symptom
You'll notice that:
First-time client admits import correctly to KIPU charts
Readmitted clients' VOBs and PAAs fail to import to their existing KIPU charts
Staff must manually upload documents as a workaround
Cause
The integration's webhook configuration has become unstable, particularly the Secret Key and Header settings that authenticate the connection between Dazos and KIPU. This affects how documents are routed for existing patient records.
Solution
Follow these steps to resolve the webhook configuration issue:
Step 1: Request Super Admin Access
Contact your KIPU system administrator
Request Super Admin access for [email protected]
This access allows Dazos support to review folder structures and webhook settings directly
Step 2: Update Webhook Configuration
Note: This step requires Dazos support assistance
Dazos support will access the webhooks in your KIPU instance
Update the Header and the Value in the Webhook settings
Test the connection stability
Step 3: Verify Document Routing
Test both VOBs and PAAs with recent patient records
Confirm documents are routing to the correct KIPU folders
Verify folder mapping matches exact folder names in KIPU (e.g., "Pre-Admission / Assignment of Schedule (HP)")
Step 4: Test with Readmits
Process a test readmission
Verify that both VOB and PAA documents import correctly
Check that documents appear in the patient's existing KIPU chart
Expected Result
After completing these steps:
Both first-time admits and readmits will import correctly
VOBs and PAAs will automatically route to the proper KIPU folders
Manual document uploading workarounds will no longer be necessary
When to Contact Support
Contact Dazos support if:
You don't have access to grant Super Admin permissions
The issue persists after webhook reconfiguration
You need assistance identifying the correct folder names in KIPU
Integration issues affect other document types or workflows
Related Resources
KIPU Integration Setup Guide
Document Folder Mapping Configuration
Webhook Troubleshooting Documentation