Whenever a check-in (arrival) or check-out (departure) is logged which wasn't recorded electronically using the Carer Companion App, CM2000 expects an Exception Code to be reported.
To ensure the correct Exception Code is reported, see Recording Visit Validation Exceptions.
CareLineLive provides a mapping between our Visit Validation Exceptions, and CM2000's Exception Codes. When manually completing a visit, it's important you select the corresponding Visit Validation Exception to ensure the data is correctly reported to your local authority.
Managing the Exception Codes
Your Local Authority may wish to published their own set of Exception Codes. CareLineLive includes the default exception codes, but also allows you to manage the list to meet the requirements of your authority.
Check with our support team if you're not sure if the list needs to be changed.
To see the list, visit Integrations from the main navigation, then CM2000, then Exception Codes.
❗️ Changes made to the Exception Codes will only apply to new records that are sent to CM2000.
From here you can:
Add any new exception codes that are required
Make changes to existing codes
Delete any that aren't required
Archive any that are no longer needed
Once an exception code has been used, you cannot delete it permanently.
Mapping Exception Codes to Visit Validation Exceptions
Once you've set up the CM2000 Exception Codes, you'll need to map them to CareLineLive Visit Validation Exceptions.
To set up the mapping, follow the steps for Managing Visit Validation Exceptions.
Either edit the corresponding exception, or create a new one. Select the Exception Code from the dropdown to set up the mapping.
When recording a Visit Validation Exception against a manually completed visit, the corresponding Exception Code will be automatically associated with the CM2000 record.
