1. Introduction
This feature expands the Kipu EMR multi-form (evaluation form) integration so that an evaluation form field can pull data from more than just the PreAssessment module.
Previously, when you mapped a Kipu evaluation form, you could only choose fields from the PreAssessment (PAA) module, plus a fixed set of Intake Opportunity and Account fields. With this update, you can map an evaluation item to a reference block from any of the intake's parent modules, giving you the flexibility to organize clinical information across several modules and still push everything into a single Kipu evaluation form.
What's new at a glance:
Map from more modules: The mapping picker now lists reference blocks grouped by the module they belong to (PreAssessments, Intake Opportunities, Accounts, and Treatment Episodes when enabled).
Custom blocks supported: Reference blocks you have added to those modules — including custom blocks built with the module generator—are now selectable for evaluation mapping.
Same-named blocks kept separate: Two blocks that share the same name on different modules (for example, an “Allergies” block on Accounts and another on PreAssessments) now appear as separate, correctly labeled options.
Safer re-mapping: When you re-point an evaluation item to a different block, only that previous block's field selections are cleared—your other field mappings stay intact.
2. Before You Begin
Make sure the following are in place before configuring evaluation form mappings:
You are signed in as a CRM administrator with access to the EMR settings area.
The Kipu EMR integration is set up and the connection is established for your account.
The reference blocks and fields you want to push already exist on the relevant module (PreAssessments, Intake Opportunities, Accounts, or Treatment Episodes).
If you want to map from Treatment Episodes, that module must be enabled for your account.
If it is not enabled, Treatment Episode blocks simply will not appear, and nothing else is affected.
3. Key Concepts
A few terms used throughout this guide:
Intake chain: The chain of records that make up a single intake: the PreAssessment, the Intake Opportunity it belongs to, and the patient's Accounts record. The evaluation form can now pull values from any of these.
Reference block: A grouped section of fields on a module (for example an “Allergies” or “Medications” block). This is the source the evaluation form reads from.
Evaluation form: The Kipu form that your CRM data is pushed into when you create the patient in Kipu.
Latest record: If a module has more than one matching record (for example several Treatment Episodes), the form uses the most recent record.
4. Open the Kipu Evaluation Form Mapping Screen
Go to the CRM Settings area and open the EMR Integration / Kipu settings.
Confirm the Kipu connection status shows as connected.
Open the Kipu Fields Mapping screen, then switch to the evaluation form mapping section.
Select the evaluation form you want to configure.
The list of its evaluation items appears, each of which can be mapped to CRM data.
5. Map an Evaluation Item to a Reference Block
Follow these steps for each evaluation item you want to populate from CRM data:
Locate the evaluation item you want to map.
Open the object / source-block selector for that item.
In the picker, choose the reference block to read from.
Blocks are grouped under their parent module (PreAssessments, Intake Opportunities, Accounts, and Treatment Episodes when enabled).
Pick the block from the correct module.
Map each Kipu evaluation field to the matching CRM field from the block you selected.
Save the mapping.
Your selection, including which module the block belongs to, is stored, so it loads back correctly the next time you open the screen.
💡 Tip: If you see the same block name listed under two different modules (for example “Allergies” under Accounts and under PreAssessments), make sure you pick the one under the module that actually holds the data you want to push.
6. Change (Re-point) an Item to a Different Block
You can change which block an evaluation item reads from at any time:
Open the same evaluation item and choose a different reference block in the picker.
Save.
Only the field selections that belonged to the previous block are cleared.
Any other field mappings on that item, such as regular Account or Intake Opportunity fields, are preserved, so you do not have to re-create them.
7. Send the Evaluation Form to Kipu
Once your mappings are saved, push the data from a patient's records into Kipu:
Open the Pre Assessment record you want to push.
Open the three-dot (more actions) menu and choose the option to Send to Kipu as Evaluation Form.
The system reads the mapped reference blocks from each parent record in the Pre Assessment chain and sends their values into the Kipu evaluation form.
Where a module has more than one matching record (for example multiple Treatment Episodes), the most recent record is used.
💡 Tip: Only mapped fields that contain a value are sent. Empty fields are skipped automatically, so blank values do not overwrite anything in Kipu.
8. Verify the Pushed Data
Open the evaluation form in Kipu and confirm the values from your mapped blocks appear in the correct fields.
Spot-check a few mapped fields against the source block to confirm the values match.
9. Working with Treatment Episodes (When Enabled)
If your account uses the Treatment Episodes module, its reference blocks and fields also appear in the evaluation picker and can be mapped like any other module.
When the patient has several Treatment Episodes, the most recent one is used for the push.
If the module is not enabled for your account, Treatment Episode options simply do not appear, and the rest of the mapping and push work exactly as described above.
10. Good to Know
Existing setups keep working: Evaluation forms you previously set up using only PreAssessment fields continue to work exactly as before; no re-configuration is required.
Field Mapping tab unaffected: The standard EMR Field Mapping tab is separate from evaluation form mapping and is not changed by this feature.
Resilient push: If a particular block has no usable link to the intake record, it is safely skipped during the push so the rest of the form still sends successfully.