Feature Requests

BCBSMI now requires behavior technicians to sign parent training and supervision notes when they participate in these direct services. To comply, a streamlined approval workflow in HiRasmus is essential. I am requesting the following workflow structures: APPROVAL WORKFLOW FOR 97153 SESSION NOTES: A. Technician completes and signs note B. Note enters "pending approval (clinical)" C. BCBA reviews note and either: Rejects note into "revision request (clinical)" → workflow starts over (step A) Signs note → workflow moves to step D D. Note enters "pending approval (billing)" E. Billing reviews note and either: Rejects note into "revision request (billing)" → workflow starts over (step A) Signs note → integrated appt is completed → claim enters billing bucket APPROVAL WORKFLOW FOR 97155 & 97156 SESSION NOTES: A. BCBA completes and signs note B. Note enters "pending approval (general)" C. Technician signs note D. Note enters "pending approval (billing)" E. Billing reviews note and either: Rejects note into "revision request (billing)" → workflow starts over (step A) Signs note → integrated appt is completed → claim enters billing bucket

I would like to be able to have the option to select what type of phase comes next to have the option to return to baseline. Right now the only option is one baseline phase and the rest are acquisition phases.

It would be beneficial to be able to set mastery workflow across a certain number of trials instead of just limiting to sessions

We require additional phases prior to mastery. Can you please add a generalization and maintenance phases PRIOR to mastery on the workflow as an option in the same way there is an acquisition phase

have ability to add in multiple mastery criteria such as 80/3 / 90/2 into one workflow.

Requesting the ability for users to control how a parent target status updates based on the status of its sub-targets. Suggested Logic: If all sub-targets are Closed, the parent target should automatically move to Closed. If at least one sub-target is in Maintenance, the parent target should remain in Mastered/Maintenance (rather than automatically moving to Closed).

When I have a total task analysis set up to master at 80% independence all together, I have to keep moving mastered steps back into aquistiion because the total task isn't meeting the mastery criteria. If we could have the whole set of targets master together instead of separately based on criteria.

We write a lot of mastery criteria as an average % correct across X sessions, and would like a mastery criteria that evaluates average % correct/

"I noticed that Hi rasmus will consider mastery across sessions rather than days and it will master out programs even when it is not consecutive. Is there a workaround so that it doesn't automatically master it out, I would prefer it to master out if mastery criteria is met consecutively in 3 days." Gwen provided a temporary solution via tickets and user requested she make a feature request here :)