Skip to main content

Product FAQ: KIPU Integration (Internal Reference) (CRM)

This FAQ provides internal guidance for team members handling KiPu EMR integrations with Dazos CRM.

Updated over 3 months ago

Intro / Context

This FAQ provides internal guidance for team members handling KiPu EMR integrations with Dazos CRM. It covers common setup questions, troubleshooting scenarios, and escalation procedures.


Q: I’m getting an error that the key doesn’t work or credentials are invalid. What should I do?

A:

  • Wait 48 hours and test the connection again — in some cases, credential propagation can take time.

  • If the issue persists after 48 hours, reach out to the KiPu point of contact (POC) at [email protected].

  • If you don’t receive a response within 24 hours, escalate internally by contacting Nelson to review next steps.


Q: The test patient’s chart doesn’t appear in Dazos CRM after integration. What should I do?

A:
Send an email to [email protected] requesting assistance. Include:

  • Patient’s full name

  • The payload received in the CRM

  • Date and time when the patient was pushed to the EMR


Q: How can a client automatically create outbound referrals in Dazos from KiPu?

A:
Instruct the client to use the Discharge/Transition To field in KiPu EMR.

  • This field automatically triggers an outbound referral creation in Dazos CRM when populated.


Q: What does a red blinking dot on a patient in the EMR census mean?

A:
A red blinking dot indicates that no MR (Medical Record) number has been created yet for that patient on the census.


Q: How do treatment programs populate in KiPu?

A:

  • Always click the Test Connection button in the integration setup.

  • This auto-populates treatment programs from KiPu into Dazos.

  • Do not manually add or create new entities for treatment programs.


Q: How do I handle integrations for CMD clients using KiPu?

A:
If the client is CMD-based, do not contact the CMD team directly.
Instead, email [email protected] and request assistance for the integration.


Pro Tips / Extra Help

  • Always document each step in the ticket for visibility.

  • If the integration fails multiple times, review credentials and mappings before escalating.

  • Escalate only after confirming all prerequisites (key, connection test, and program mapping) are complete.


Related Resources

Did this answer your question?