A Visit Validation Exception can occur when a visit is not verified electronically by a carer checking in via the Carer Companion App. This can happen for a number of reasons, such as:
The carer was unable to use the app
The carer wasn’t able to gain entry
The visit was away from the service user’s home
The carer forgot to check in/out
Whenever a Visit Validation Exception occurs, you can record it when manually completing the visit via the Management Portal. This is important for a number of reasons:
It helps to track the number of visits that are not being verified.
It helps to ensure that all visits are being recorded accurately. This is important for billing and compliance purposes.
It helps to protect the carer and the client. If a visit is not verified, it is possible that the carer did not actually visit the client. This could have implications for the carer's employment and the client's care plan.
Recording a visit validation exception
Exceptions can only be recorded when manually completing a visit via the Management Portal.
To record a Visit Validation Exception, follow the following article: Incomplete bookings
For each arrival/departure, you have the option of selecting the Reason for the manual completion from the dropdown.
Once an exception has been recorded, it will be available via the Visit Reports.
Managing the list of exceptions
To manage the list of Visit Validation Exceptions, open Bookings from the main navigation, then Visit Exceptions.
You can:
Edit the existing exceptions
Add your own exceptions
Remove any that you don’t want/need
Archive any that you don’t need, but have already been used
Usage with CM2000 integration
When manually completing a visit, it's important to select the correct Visit Validation Exception in order for it to be sent to CM2000. This exception code can be mapped directly to a CM2000 "Exception Code," but local authorities may provide different values. To ensure accuracy, modify the list of Visit Validation Exceptions accordingly.