When This Matters
This information is critical when:
Configuring PAA-to-KIPU field mapping for the first time
Troubleshooting why certain PAA fields don't appear in KIPU
Planning PAA form design for KIPU integration
Deciding whether to create a new PAA from scratch in KIPU
PAA Field Types That Cannot Be Mapped
Conditional Questions
Fields with follow-up questions based on answers cannot be mapped individually:
Children (conditional question with multiple follow-ups)
Overdose history
Seizure history
Pregnancy status
TBI (Traumatic Brain Injury)
Surgeries and pain level
Dental and communicable disease
Physical limitations
Psychiatric conditions (delusions/hallucinations, psychiatric hold)
Medications
Self-harm history
Eating disorders and trauma
Legal issues and violence history
Employment status
Living skills (meal planning, budgeting, shopping)
Special Field Types
Leave Tx — field type does not exist in Dazos
AMA — field type does not exist in Dazos
Allergies — special system field that requires manual handling
Relationship Status — contains a picklist that lives inside KIPU and cannot be mapped
Data Type Limitations
String fields — certain string fields like "Longest Sobriety" cannot map properly due to data type incompatibility
⚠️ Important: These limitations are imposed by the KIPU API, not the Dazos integration. The integration team works within KIPU's available endpoints.
How Unmapped Data Still Reaches KIPU
Fields that cannot be mapped directly are not lost. When a patient is pushed to KIPU, the entire PAA is sent as a PDF attachment. All unmapped field data remains visible in KIPU within this PDF document. Staff can reference the PAA PDF to manually enter critical information into KIPU fields as needed.
Recommended Solution
For facilities with extensive conditional questions or special field requirements, the best approach is often to create a new PAA from scratch directly in KIPU. This ensures:
Questions are designed to work within KIPU's field structure
Maximum field-to-field mapping compatibility
Reduced reliance on manual data entry
Better workflow efficiency for staff
Tips & Notes
💡 Planning Tip: Review your current PAA structure against this list before configuring KIPU integration to identify which fields will require alternative workflows.
✅ Best Practice: Consider your facility's workflow needs when deciding between modifying existing PAAs versus creating new ones directly in KIPU.