Feature Requests

I feel it would be helpful to either have ability to remove or "hide" outlier data (eg. low trial counts, errored data dates) so that graphs reflect more accurately in reporting. For example, i've had some sessions where a program is set at 5 trials but there was only 1-2 opportunities which depicts highly variable on the graph compared to days in which the trial count was met.

Would love for new targets to show up in a different color/be highlighted as a prompt for techs to see/use.

A session note log that pulls the narrative sections into a single view rather than needing to pull up multiple notes.

A quick reference table that labels the last 5 to 10 sessions and the lessons that have been practiced (via checkmark)

Once a report has been published all the information is saved and can no longer be changed unless reverted to a draft. Ex: Currently data continues to update, new programs continue to be added to the report, and any information updated in the client profile will also change (ie assessment date, address, etc.) Would like to see this information be saved and unchangeable once a report has been published.

WE ALL WANT IT :)

Ability to manually enter data for targets that have were added after a session created

Currently, if I want anecdotal data such as a list of new sounds a client is emitting, I need to hope that the RBT lists the sounds in program notes and then review the history session note by session note to manually generate a list. Please instead add anecdotal data as a data type option that clearly requires the RBT to type into a text field to take data and that provides the BCBAs with a quick/easy way to review the anecdotal data such as in the "all trials" view. Thank you.

for a certain amount of time (for example, 5 days or so pass and the program has not been ran) if a program has not been ran, it would be ideal to prompt staff that it needs to be ran (or notify the BCBA through a notification), it is hard to see previous data from sessions or from the day!

During program creation, it would be nice to set limitations around what the system will default to presenting a BT. For example never presenting more than two of the highest level in a row. Currently we've tested it where occasionally we will get four CFCRs or highest level in a row which doesn't feel random. I don't want to rely on a BT to hit the view history and make sure that their ratio of trial difficulty is correct.