Skip to main content

KIPU Integration Failures Caused by Multiple CRM Locations Using the Same EMR API Key (CRM)

Overview This guide explains why Intake Opportunities may fail to auto-link to KIPU patient charts and why admission statuses may stop updating — and how to resolve it when the cause is multiple CRM locations sharing one KIPU EMR API key.

Problem

Intake Opportunities are not automatically linking to KIPU patient charts, and opportunity statuses are not updating to Admitted as expected. This typically affects multiple records at the same time and may occur alongside missing or mismatched discharge type values in the CRM.

Possible Causes

  • Multiple CRM locations sharing the same KIPU EMR API key. When more than one CRM location or account is configured using the same EMR API key, synchronization conflicts occur that prevent intake opportunities from auto-linking and admission statuses from updating correctly.

  • New discharge types added in KIPU that are not reflected in the CRM. When discharge types are added or updated in the EMR, they must also be manually added and mapped in the CRM. If the CRM does not have a matching value, the integration cannot match records correctly, leading to sync failures.

Solution

  1. Identify how many CRM locations are configured with the same KIPU API key. Review your EMR integration settings to confirm whether multiple CRM locations or accounts are sharing a single EMR API key. Only one CRM location should be configured per KIPU EMR API key.
    ​

  2. Determine the correct primary CRM location. Work with your team to confirm which CRM location should serve as the single, authoritative configuration for that KIPU API key.
    ​

  3. Contact Dazos Support to perform the re-integration. Because this change affects active integrations and all associated mappings, it is recommended to have Dazos Support perform the reconfiguration. Coordinate a time when no users are actively working in either the CRM or the EMR to minimize disruption.
    ​

  4. Remap all associated configurations to the single correct CRM location. Once the duplicate configurations are removed, all of the following must be remapped to the single, correct CRM location:

    • Treatment Programs

    • Admitted Statuses

    • Discharge Types

    • Levels of Care (LOC)

    • Any other related integration mappings
      ​

  5. Add any missing discharge types to the CRM. Review the discharge types currently configured in KIPU and compare them against what is mapped in the CRM. Any discharge types that exist in the EMR but are missing from the CRM must be manually added and mapped. Confirm the corresponding Discharge Status and Admission Status values so they align correctly.
    ​

  6. Test the integration after changes are complete. After reconfiguration, verify that new intake opportunities pushed from KIPU are automatically linking in the CRM and that admission status updates are synchronizing as expected.

Still Need Help?

If intake opportunities are still not auto-linking or updating to Admitted after following these steps, contact Dazos Support with the following information:

  • Your CRM instance name (the URL you sign in to)

  • The names of the CRM locations that were configured with the same API key

  • Links to specific Opportunity records that are not linking correctly

  • A list of any discharge types in KIPU that may be missing from the CRM

⚠️ Important: Never configure more than one CRM location with the same KIPU EMR API key. Doing so will cause synchronization conflicts that prevent intake opportunities from linking and admission statuses from updating. Whenever new discharge types are added in KIPU, they must also be added and mapped in the CRM immediately to prevent future sync failures.
​
​

Related Resources

Related Articles
Did this answer your question?