Hi Rasmus | Lumary Integration: Guardian Signature Mapping
Learn how to set up Guardian/Caregiver Signature Mapping to sync from Hi Rasmus to Lumary
Some funders require a parent or guardian signature on every rendered appointment. If your organization is Lumary-integrated, you can set up Hi Rasmus so a caregiver's signature is collected on the session note and synced over to Lumary automatically into Lumary's Guardian Signature field. This article walks through how to set that mapping up.
💡 Manager-level users will need to complete these steps.
Before You Start
For California customers, Lumary can generate a compiled Parent/Caregiver Verification Form (PVF) report. This report pulls the caregiver's signature directly from the Hi Rasmus session note, so the signature has to be collected and mapped correctly in Hi Rasmus for it to populate.
⚠️ The caregiver signature does not need to be collected before the note sends to Lumary. As long as the field is mapped correctly (Step 4), the signature will sync over even if it's added after the note has already gone to Lumary.
Step 1: Create a Custom Client Information Field
- Navigate to [Settings] >> [Organization] >> [Client Information]
- Select [Add Data Field]
- Choose a section for the field, or leave it as "none"
- Create a label, such as "Caregiver Signature"
- Select the [User] data type
- Click [Save]
- Repeat if you would like to have an alternative caregiver signature field
💡 For more on custom client information fields, click HERE.
Step 2: Decide - Will Caregivers Have Hi Rasmus Accounts?
Before you set anything up, decide whether caregivers will sign as Hi Rasmus users (logging in themselves) or whether staff will collect the signature manually on their own device during or after the session. Each route uses the same custom field and Integrations page mapping, but the steps for collecting the signature itself differ. Pick the route that matches your organization below.
Step 3a: Set Up Caregiver Accounts (if needed)
A user account is only required if you want the caregiver to sign remotely through their own Hi Rasmus login, or if you plan to use caregiver bulk-signing. Bulk-signing can only be done if the parent has their own account
To invite the caregiver as a user, and set up for signing:
- Navigate to [Settings] >> [Organization] >> [Users]
- Click [Invite User]
- Select the [Parent] user role
- Once they have accepted the invite, navigate to [Clients] and select the client
- Click [Edit Client]
- Select the [Client Information] tab
- Find the custom field you created in Step 1
- Select the caregiver's name from the dropdown
- Scroll down and click [Save]
Step 3b: Required Set Up if Caregivers are not Hi Rasmus Users
If caregivers are NOT Hi Rasmus users, the provider can collect the signature in person on their own device.
Users needing to collect signatures this way must have the [Sign any signature request] privilege enabled. This can be found under User Abilities - Sessions.
Step 4: Map the Caregiver Field on the Integrations Page
- Navigate to your organization's [Integrations] page
- Locate the [Guardian Signature Mapping] field, underneath all session mapping
- Select the custom client information field you created in Step 1 in the drop down on [Caregiver Client Datafield]
- If you set up an additional caregiver signature field in Step 1, map that field here as well as the Alternative Caregiver
⚠️ If this field is not mapped, the caregiver's signature will not sync to Lumary, even if it's collected correctly on the session note.
Step 5: Require the Signature on Your Note Template
- Navigate to [Settings] >> [Templates] >> [Notes]
- Click into the note template you want to update
- In the [Signatures] section, select [Require signature from additional people]
- Select the custom client information field you created (for example, "Caregiver")
- Scroll down and click [Save]
Now, when this note template is used in a session, the caregiver's signature will be requested on the note and synced to Lumary once collected
What to Expect
- The signature can be added before or after the note is sent to Lumary. As long as the Integrations page mapping (Step 4) is set up, it will sync correctly either way.
- On the compiled PVF report, the final signature covering all lines of service on the document is generated by Lumary, not Hi Rasmus. This is separate from the individual line-of-service signatures that come from your session notes.
- This PVF requirement is currently confirmed for California. If you're unsure whether it applies to your organization or state, check with your billing/funding contact or reach out to Hi Rasmus support.