User guide for CRM administrators • Netsmart (myAvatar) integration
This guide explains how to let a myAvatar form pull information from additional modules in the CRM — not just the Pre-Assessment. You can now include fields from the modules that are attached to an Intake Opportunity or an Account, including custom modules your team has built with the module generator.
You do not need any technical knowledge to use this. Everything is done from the CRM Settings screen — no coding, no files.
What this feature does
When the CRM sends a form to myAvatar, it fills the form using values from CRM records. Previously it could only use fields kept on the Pre-Assessment. With this update you can choose extra modules as "sources," and then map their fields onto the myAvatar form the same way you map Pre-Assessment fields today.
Typical uses: sending a Verification of Benefits (VOB) detail, a Transaction amount, or any information stored in a custom module that hangs off the Intake Opportunity or the Account.
Who can use it
• CRM administrators who manage the Netsmart (myAvatar) integration settings. • The Netsmart (myAvatar) integration must already be connected for the account you are configuring.
The two kinds of modules
On the settings screen you will see a list called Form Mapping Module Sources. It has two kinds of entries:
1. Core modules (always available)
These are always usable and cannot be removed. They appear with an "Always available" tag and a small lock icon:
• Pre Assessment
• Intake Opportunities
• Accounts (the client/patient record)
• Referral Sources
2. Custom modules (you add these)
These are additional modules — including ones your team created with the module generator — that are attached to an Intake Opportunity or an Account. You add the ones you want, and you can remove them later. Only modules that are genuinely attached to those records are offered, so everyday system areas (such as Calendar, Tickets, Comments, Projects, Survey, and Call Logs) are intentionally not listed.
Where to find the settings
1. Open Settings (the gear icon) and go to Integrations → EMR Settings.
2. Choose the Netsmart myAvatar tab near the top.
3. Under Select Account, pick the account you want to configure.
4. Turn on Send PAA Through Form? (the toggle switch). This reveals the myAvatar credentials and, just below them, the Form Mapping Module Sources section.
If you do not see the "Form Mapping Module Sources" section, make sure the "Send PAA Through Form?" toggle is switched ON. The section is part of that area and stays hidden while the toggle is off.
Adding a custom module
5. In the Form Mapping Module Sources section, find the Custom Module dropdown. 6. Open it and pick the module you want. Each option shows which record it is attached to in brackets — for example, "VOB (→ Intake Opportunities)" or "Transactions (→ Accounts)". 7. Click + Add. The module appears as a new row in the list above, showing the module name and its parent.
8. Repeat for any other modules you want to include.
9. Click Save. You will see a confirmation message.
Adding a module here only makes its fields available for mapping. It does not send anything on its own — you still choose exactly which fields go onto the form in the next step.
Removing a custom module
10. In the list, find the custom module row you want to remove.
11. Click the trash icon in the Action column. (Core modules have a lock icon instead and cannot be removed.)
12. Click Save to confirm.
Mapping the fields onto a form
Once a module is added as a source, its fields become available on the field-mapping screen. 13. From the Netsmart myAvatar settings, click Netsmart field mapping.
14. Choose the Form Field Mapping tab, then Map the Fields.
15. Add or edit a field row. For CRM Field, open the dropdown — the fields are now grouped by module (for example, an "Intake Opportunities" group, an "Accounts" group, and a group for each custom module you added, such as "VOB"). Pick the field you need.
16. Save the mapping.
You can use a custom module's fields in either of two ways, depending on how the form is set up: • Regular Block — the field sends a single value. Choose the field from its module group in the CRM Field list.
• Sub Module Reference — the module is sent as a block of information. Choose the module (for example, "VOB (Intake Opportunities)") as the Object, then map its fields.
What gets sent to myAvatar
When a form is pushed to myAvatar, each custom module you added contributes its most recent record. For example, if an Intake Opportunity has several VOB records, the form uses the latest one.
Only the most recent record from each added module is sent. If you need historical or multiple records included, let the product team know — that is outside the current behavior.
Good to know
• Existing myAvatar setups are unaffected. If you do not add any custom modules,
forms behave exactly as before.
• If a module you previously added is later changed so it is no longer attached to its parent record, it is shown as "(unresolved)" in the list and is simply skipped when sending — it will not cause errors. • The core modules cannot be removed, so the fields you rely on today remain available. • Module names shown here follow your CRM's own labels (for example, the client module appears as "Accounts").
Quick reference
Goal | Where | Action |
See the settings | Settings → EMR Settings → Netsmart myAvatar | Turn on "Send PAA Through Form?" |
Add a module | Form Mapping Module Sources | Pick under "Custom Module" → + Add → Save |
Remove a module | Form Mapping Module Sources | Click the trash icon → Save |
Map its fields | Netsmart field mapping → Form Field Mapping → Map the Fields | Pick the field from its module group; Save |
For questions or to request behavior changes, contact your Dazos administrator or the product team.