Skip to main content

How to Map KIPU Program Field to Multiple CRM Fields for Static and Dynamic Level of Care Tracking (CRM)

This guide shows you how to map the KIPU Program field to multiple CRM fields to track both the initial admission level of care (static) and current treatment level (dynamic) for comprehensive patient tracking and reporting.

Before You Begin

  • Ensure you have administrator access to CRM Settings

  • Confirm your KIPU integration is configured and active

  • Verify both 'Admitting to LOC' and 'Current LOC' fields exist in your CRM

  • Have [email protected] user access to KIPU for testing (if needed)

Steps

1. Navigate to KIPU Integration Settings

Log in to the CRM and navigate to the Dashboard.

Click Settings.

Select CRM Settings.

Click Integrations.

Select EMR Settings.

Click on the KIPU tab.

2. Access KIPU Field Mapping

Click KIPU Field Mapping to view the current mapping configuration.

Locate the Program field mapping section.

3. Configure Static Field Mapping (Admitting to LOC)

Verify that the KIPU Program field is mapped to the Admitting to LOC field.

This field should be configured to capture the initial level of care and remain static after the first data push.

4. Add Dynamic Field Mapping (Current LOC)

In the mapping configuration, add a new mapping for the same KIPU Program field.

Map the KIPU Program field to the Current LOC field.

Configure this mapping to receive real-time updates when the program value changes in KIPU.
Click Save to apply the mapping configuration.

5. Test the Dual Mapping

Create or update a test patient record in KIPU with a Program value.

Verify that both CRM fields populate correctly:

  • Admitting to LOC: Shows initial program assignment

  • Current LOC: Shows current program assignment

Change the Program value in KIPU and confirm that only the Current LOC field updates while Admitting to LOC remains unchanged.

Verification / Expected Result

After successful configuration:

  • The Admitting to LOC field captures and retains the initial level of care from admission

  • The Current LOC field updates in real-time when program changes occur in KIPU

  • Both fields can be used separately for reporting and automated notifications

  • You can track patient progression from admission level to current treatment level

Common Use Cases

  • Reporting: Calculate days spent in each level of care using both static and dynamic data

  • Automated Notifications: Trigger alerts when level of care changes (using Current LOC field)

  • Treatment Progression Analysis: Compare admission level with current level for patient outcomes

  • Compliance Tracking: Maintain records of both original admission criteria and current treatment status

Troubleshooting / Common Errors

Current LOC field not updating:

  • Verify the field mapping is configured correctly for real-time updates

  • Check that webhooks are properly configured between KIPU and Dazos

  • Confirm the integration user has appropriate permissions in KIPU

Admitting to LOC field changing when it should stay static:

  • Review the field mapping configuration to ensure proper static vs. dynamic setup

  • Contact support to verify the mapping logic for the static field

Neither field populating:

  • Confirm the KIPU Program field contains data

  • Verify the integration connection is active

  • Check that the field names match exactly between systems

Related Resources

  • KIPU EMR Integration with Dazos CRM (Bidirectional)

  • Product FAQ: Understanding the "Admitting to LOC" Field When Pushing Records to KIPU

  • EMR Integration Field Mapping Overview

Did this answer your question?