When evidence is captured for a case, the Cúram Verification engine is called in order to determine if any of the evidence data requires verification. If a piece of data requires verification, the Cúram Verification engine checks to see whether or not verifications are required for the case type where the evidence has been captured. In the case of shared evidence captured for an integrated case, the Cúram Verification engine determines if either the integrated case or its product deliveries (if any exist) require that the evidence be verified. All non-closed product deliveries are considered. If the evidence has any verification requirements, a list of these requirements is returned to the caseworker via an informational message.
When participant evidence is captured, it can be verified in isolation of any case usage of the evidence. Participant evidence is automatically activated when captured and therefore any mandatory verification defined about the participant evidence will exist against this active evidence. The caseworker will see these verifications listed in Verifications listed at both the Person and Case level. Note that participant level verifications do not impact the case level processing. Even if there are outstanding mandatory participant verifications present, the Verification Engine will allow the cases for that participant to be activated and will not impact the eligibility and entitlement processing. Where verification of participant data (e.g. verification of a person's date of birth or SSN) must impact the case level processing, the recommended approach is to associate that evidence with the case and set up case level verifications.