Skip to main content

How to Add a Second KIPU Instance to Your Existing Dazos (CRM)

If your organization needs to connect an additional KIPU EMR instance to your existing Dazos CRM

This guide explains the process, what information you'll need to provide, the expected timeline, and whether your current configuration can be mirrored to the new instance.

⚠️ Note: Adding a second KIPU instance involves an additional cost. For pricing details, please contact your Dazos account or sales representative.

Before You Begin

  • An addendum to your existing Dazos agreement must be signed before the integration process can start.

  • Have the following KIPU credentials ready for the new instance: API credentials, account name, and account number.

  • If you have questions about pricing, reach out to your Dazos account or sales team before proceeding.

Steps

  1. Sign the Addendum
    Contact your Dazos representative to receive the addendum for adding a new KIPU instance. The integration process cannot begin until this document is signed.

  2. Provide Your KIPU Credentials
    Once the addendum is confirmed, submit the following information for the new KIPU instance to the Dazos Support team:

    • KIPU API credentials

    • KIPU account name

    • KIPU account number

  3. Dazos Support Completes the Integration
    The Dazos Support team will handle the backend setup for the new KIPU instance. This process typically takes 5 business days from the time all required information is received.

Configuration Mirroring

If you would like the new KIPU instance to be configured the same way as your existing one — for example, matching discharge type mappings and other settings — this is feasible. Let the Dazos Support team know at the time of your request that you would like the configuration mirrored, and they will set it up accordingly.

💡 Tip: Mirroring your existing configuration can save setup time and keep your workflows consistent across both KIPU instances.

Verification / Expected Result

Once the integration is complete, the new KIPU instance will be connected to your Dazos CRM and syncing data. If configuration mirroring was requested, settings such as discharge type mappings should reflect your existing setup.

Troubleshooting / Common Errors

  • Integration not started after addendum: Confirm the addendum has been fully signed and that you have submitted all required KIPU credentials (API credentials, account name, account number) to the Dazos Support team.

  • Version mismatch between KIPU instances: Both KIPU instances must be on the same version (e.g., both on V4) for the integration to work correctly. If one instance is on V3 and the other on V4, contact KIPU support to upgrade before proceeding. See the related article below for details.

  • Questions about pricing: Dazos Support cannot provide pricing information. Please direct all cost-related questions to your Dazos account or sales representative.

Related Resources

  • KIPU Multi-Instance Integration: All Instances Must Be on the Same KIPU Version (CRM)

  • How to Set Up Additional Treatment Facilities and Connect KIPU EMR + Dazos IQ (CRM)

  • How to Transfer KIPU Integration Keys Between Dazos Instances (CRM)

  • Understanding Discharge Type Mapping from Kipu EMR to Dazos (CRM)

Did this answer your question?