Skip to content
English
  • There are no suggestions because the search field is empty.

Hi Rasmus | Lumary Integration: Signature Mapping

Learn how to set up additional Signature Mapping to sync from Hi Rasmus to Lumary 

Some funders require additional signatures on notes or to include in a signature log.

 If your organization is Lumary-integrated, signature mapping lets you send a signature's URL (the image of the signature) from the Hi Rasmus session note to Lumary, where it can be used in any required signature logs or reports that Lumary generates.

You can map up to three signature fields:

  • Caregiver and Alternative Caregiver, which both sync to Lumary's Guardian Signature field
  • Additional Signature, which syncs to a separate field in Lumary, so a different signature type (for example, a school rep signature) can pull into signature logs on its own

This article walks through how to set that mapping up.

💡 Manager-level users will need to complete these steps.

Before You Start 

Signature mapping is commonly used for:

  • Parent/Caregiver Verification Form (PVF): For California customers, Lumary can generate a compiled PVF report. This report pulls the caregiver's signature directly from the Hi Rasmus session note.
  • School district signature logs (e.g., SSG): Organizations serving clients in some California school districts need a school representative's signature on their signature logs. Use the Additional Signature field for this.

In both cases, the signature has to be collected and mapped correctly in Hi Rasmus for it to populate in Lumary.

⚠️ The session note will not send to Lumary until all required signatures are collected.

If your organization has the setting enabled to send activity times before additional signatures are collected, the activity times will send first, so the appointment can still be completed in Lumary.

The note and its mapped signatures send once the signatures are collected. Talk to your Hi Rasmus representative or reach out to our help desk to enable this setting.

Step 1: Create a Custom Client Information Field 

  1. Navigate to [Settings] >> [Organization] >> [Client Information]
  2. Select [Add Data Field]
  3. Choose a section for the field, or leave it as "none"
  4. Create a label, such as "Caregiver Signature" 
  5. Select the [User] data type
  6. Click [Save]
  7. Repeat for any other signers, such as an alternative caregiver (e.g., "Alternative Caregiver Signature") or an additional signer (e.g., "School Rep Signature")

💡 For more on custom client information fields, click HERE.

Step 2: Decide - Will Signers Have Hi Rasmus Accounts? 

Before you set anything up, decide whether each signer (caregiver, alternative caregiver, or additional signer) will sign as a Hi Rasmus user (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. You can use different routes for different signers.

Step 3a: Set Up Signer Accounts (if needed)

A user account is only required if you want the signer to sign remotely through their own Hi Rasmus login, or if you plan to use bulk-signing. Bulk-signing can only be done if the parent has their own account.

To invite the signer as a user, and set up for signing:

  1. Navigate to [Settings] >> [Organization] >> [Users]
  2. Click [Invite User]
  3. Select the [Parent] user role for caregiver. (Confirm which role to use for additional signers, such as school reps). 
  4. Once they have accepted the invite, navigate to [Clients] and select the client
  5. Click [Edit Client]
  6. Select the [Client Information] tab
  7. Find the custom field you created in Step 1
  8. Select the caregiver's name from the dropdown
  9. Scroll down and click [Save]

Step 3b: Required Set Up if Signers are not Hi Rasmus Users

If signers 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 

  1. Navigate to your organization's [Integrations] page
  2. Locate the [Signature Mapping] field, underneath all session mapping
  3. Select the custom client information field you created in Step 1 in the drop down on [Caregiver Client Datafield]
  4. If you set up an additional caregiver signature field in Step 1, map that field here as well as the [Alternative Caregiver Datafield].
  5. If you created an additional signer field, map it in the [Additional Signature Client Data field].

Hi Rasmus mapping

Where it syncs in Lumary

Caregiver Client Datafield

Guardian Signature

Alternative Caregiver

Guardian Signature (same field as Caregiver)

Additional Signature Client Data field

Additional Signature (separate field) 

⚠️ 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.

Screenshot 2026-11-12 at 9.15.33 AM

Step 5: Require the Signature on Your Note Template 

  1. Navigate to [Settings] >> [Templates] >> [Notes]
  2. Click into the note template you want to update
  3. In the [Signatures] section, select [Require signature from additional people]
  4. Select the custom client information field you created (for example, "Caregiver")
  5. 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 session note send to Lumary only after all required signatures are collected. With the activity times setting enabled, activity times send first so the appointment can be completed in Lumary in the meantime. Contact Hi Rasmus to enable this.
  • 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.