How the PAA and Kipu Integration Works
When a PAA (Pre-Admission Assessment) form is sent to Kipu, data flows in one direction only, from Dazos to Kipu. The integration is non-bidirectional, which means:
Data flows from Dazos to Kipu when the PAA form is sent.
Updates, notes, or changes made to the PAA in Kipu do not update the corresponding fields in Dazos.
The original PAA data in Dazos stays the same, no matter what is changed in Kipu.
Note: The Dazos and Kipu integration does pull some patient details back from Kipu, such as demographics, admission and discharge information, and insurance. PAA form content is not part of that sync.
Clinician Notes and Required Fields
This matters most in a scenario like this one:
A clinician needs to sign the PAA and add notes.
The clinician is not a user in Dazos.
The notes fields are set as required.
The clinician can complete and sign the PAA in Kipu, but their notes and input will not be loaded back into the PAA in Dazos, because the integration only works in one direction.
Important Considerations
⚠️ Planning note: When designing your PAA workflow with the Kipu integration, keep in mind that any data entered or changed in Kipu stays only in Kipu.
💡 Tip: If you need clinician notes captured in Dazos, set up your workflow so that this information is entered in Dazos before the PAA is sent to Kipu.
Still Need Help?
For additional questions about PAA forms or the Kipu integration, contact Dazos Support.