1. Overview
This feature lets your facility pull each patient's dietary information from Kipu directly into the CRM, so your team can view it on the Opportunity without logging into Kipu. A patient may have more than one diet entry (for example "Vegan" or "No nuts, no shellfish"), so the information is shown as a list - one row per diet.
The information is read from Kipu only. It is never sent back to Kipu. You turn the feature on with a single setting, and the CRM automatically builds the "Special Diets" section on the Opportunity and keeps it updated on each sync.
Tip: This feature is pull-only. Diet information flows from Kipu into the CRM - changes made in the CRM are not pushed back to Kipu.
2. Before You Begin
• You must be signed in as an administrator.
• Your instance must be connected to Kipu as the EMR.
• Opportunities must already be linked to their Kipu patients/episodes.
3. Enabling Special Diets Pull
Step-by-step
1. Go to Settings, then Integrations, then Kipu.
2. Find the "Enable Special Diets Pull" toggle.It is located in the EMR Setting page for KIPU. 3. Switch the toggle ON and confirm the prompt.
4. Wait for the success message.
Once enabled, the CRM automatically creates a new "Special Diets" section on the Opportunity, along with two fields - Diet and Food Restrictions - and their default mapping to Kipu.
Tip: This setup runs only the first time. Turning the toggle off and on again will not create duplicate sections or fields.
4. Viewing Special Diets on an Opportunity
5. Open any Opportunity record.
6. Scroll to the new "Special Diets" section below the existing detail blocks.
7. Each diet the patient has in Kipu appears as its own row, showing the Diet name and any Food Restrictions. The section refreshes automatically on each Kipu sync (hourly by default). If a patient's diet changes in Kipu, the CRM updates on the next sync.
5. Customizing the Field Mapping (Optional)
By default, Kipu's diet and food-restriction values map to the Diet and Food Restrictions fields. You can change this if needed.
8. Open EMR Mapping for your Kipu account.
9. Select the "Special Diets" tab.
10. You will see two pre-filled default mappings: Diet and Food Restrictions.
11. Click Edit on a row, choose a different CRM Field from the dropdown, and save.
12. On the next sync, the Kipu value is written into the field you selected.
Note – This Mapping is flexible. The “Special Diets” can be mapped to any Sub-Module-reference type block of either of the modules – Accounts, Intake Opportunities or Pre- Assessments. Upon clicking on Change Target Block button, user can select their desired Sub-Module-reference block and map the fields to that table.
6. Disabling Special Diets Pull
13. Go to Settings, then Integrations, then Kipu.
14. Switch the "Enable Special Diets Pull" toggle OFF.
Disabling is safe and non-destructive. Syncing stops, but the Special Diets section and any diet information already pulled remain in place. Turning the toggle back ON resumes syncing.
Note: Diets that are removed in Kipu are kept in the CRM as historical snapshots - they are not deleted automatically.
7. Things to Keep in Mind
• Special Diets data is read from Kipu only and is never sent back.
• A patient can have several diets - each is shown as a separate row.
• Re-syncing the same data updates existing rows rather than duplicating them.
• The feature is per-facility and behaves the same on InsightsTx and AllevaCRM.
• The toggle appears only when your EMR is Kipu.