Allow users to record "yes" ROI when client has a "no" recorded by another agency
We have had a recurring situation where the following takes place:
1. Client has a “no” ROI recorded by Agency A with no end date (but has an unlocked profile)
2. Client begins working with staff at Agency B and gives consent/signs ROI
3. Staff at Agency B try to record this “yes” ROI but cannot; it throws an error for the ROI start date because there is no end date for the previous “no” ROI.
Staff at Agency B cannot edit and add an end date to the “no” ROI because it was recorded by Agency A.
Currently when this happens, staff must notify me and then I go in and add an end date for the “no” ROI, let them know, and then they can record the new “yes” ROI. This is quite inconvenient and can prevent electronic signatures from being recorded when staff are physically with a client.
We think a "yes" ROI should override a "no" regardless of what agency uploaded it. Ideally, the system would allow Agency B staff to upload the ROI in this situation, and add an end date automatically for the previous "no" ROI that reflects the start date of the new "yes" ROI.
Connor Foley
shared this idea
Thank you for your feedback. We are currently reviewing this request.
-
Tucker Morgan commented
It would also be nice if when one agency put "yes" to an ROI that didn't include documentation (like only verbal consent from a call center or SO project) another agency could enter an overlapping ROI that has attached documentation (uploaded signed copy or e-signed when the client is sheltered or housed).