Description
This page allows you to view verification requirement usage details. A verification requirement usage record is the use of a verification requirement by a case type. A verification requirement can be used by different types of case. For example, a participant's income amount is captured at the integrated case level. If there is a verification requirement to verify the income amount, this requirement can be used by multiple cases within the integrated case.
Page Preview
Page Flow Diagram
Click the diagram to manipulate and zoom. Traverse the diagram using Click-and-Drag motions. Fullscreen
Fields
LabelTypeDescriptionMandatory
NameVERIFICATION_REQUIREMENT_NAMEVerification requirement name e.g., verification requirement 1.No
LevelVERIFICATION_LEVELThe level of verification that must be achieved in order to consider the data verifiedNo
From DateCURAM_DATEThe start of the period during which the verification requirement appliesNo
To DateCURAM_DATEThe end of the period during which the verification requirement appliesNo
Minimum ItemsVERIFICATION_REQUIREMENT_MINIMUM_ITEMSThe minimum number of items that must be provided before the data can be considered verified. The application will not allow the verification to be accepted unless at least the number of items specified within the administration of the verification requirement has been added to the verificationNo
Reverification ModeREVERIFICATION_MODEThis field indicates how much, if any, of the verification information that was recorded for an Active evidence record that is copied forward to the In Edit record. The verification engine supports three modes of reverification; Reverify Always, Reverify If Changed, and Never ReverifyNo
Supplied By ClientCURAM_INDICATORThis field indicates if it is the responsibility of the primary client as opposed to the third party to supply the verification items. This is useful during communications between the organization and the client to ensure that a client is not asked to supply a verification item that should be sourced elsewhereNo
MandatoryCURAM_INDICATORA verification requirement may be defined as mandatory or optional. A mandatory verification means that the evidence associated with the verification cannot be activated until the rules defined for the verification have been satisfied. Therefore, if an In Edit evidence record has a data item that has a mandatory verification requirement, the evidence record cannot be activated until the verification rules have been satisfied and the data can be considered verified.No
Verification Conditions
LabelTypeDescriptionMandatory
Rule ClassCREOLE_RULE_CLASS_DESCRIPTIONNo
Display UIMDISPLAY_UIM_NAMENo
Display Rule ClassDISPLAY_RULESET_WITH_RULECLASS_NAMENo
Verification Due Details
LabelTypeDescriptionMandatory
Due DaysNUMBER_OF_DAYSThe number of days after the event specified in the Date From field below by which date the verification must be achieved.No
Warning DaysNUMBER_OF_DAYSThe number of days after the event specified in the Due Date From field by which date a warning is raised, indicating that there is an outstanding requirement to verify this piece of data.No
Due Date FromVERIFICATION_DUE_DATE_FROMThe event that will trigger the calculation of the Due Days value above, e.g., Insert EvidenceNo
Modify Due DateCURAM_INDICATORThis field indicates whether or not a case worker can modify the due date for this verification.No
Due Date EventVERIFICATION_REQUIREMENT_DUE_DATE_EVENT_TYPEThis field indicates the event which will trigger the calculation of the Due Days value above, e.g. Insert Evidence.No
Event Details
LabelTypeDescriptionMandatory
Add EventVERIFICATION_REQUIREMENT_ADDED_EVENT_TYPEThe type of workflow event that is generated when a verification to meet this requirement is createdNo
Update EventVERIFICATION_REQUIREMENT_UPDATE_EVENT_TYPEThe type of workflow event that is generated when the verification is updated by the addition of removal of a verification item.No
Value Changed EventVERIFICATION_REQUIREMENT_VALUE_VERIFIED_CHANGED_EVENT_TYPEThe type of workflow event that is generated when the value of the evidence to be verified has changed.No
Description
LabelTypeDescriptionMandatory
DescriptionCOMMENTSNo
Links and Actions
None
Messages
When page is loaded
MessageMessage CatalogConfigurableConfigurable Validation Reference ID
'To be' rule sets contain validation errors - cannot continue with rule set migrationLinkNo
(error accessing field - '%1s')LinkNo
%1s: %2s %3s (%4n %5n) %6sLinkNo
- %1s = %2sLinkNo
Ancestor attribute availability not found for current attribute availability '%1s'.LinkNo
Ancestor attribute availability not found for to-be attribute availability '%1s'.LinkNo
Ancestor rule class not found for current rule class '%1s'.LinkNo
Ancestor rule class not found for to-be rule class '%1s'.LinkNo
An Exception occurred as the timeout has been reached and the transaction has been rolled back.LinkNo
Arguments for invocation %1n:LinkNo
A row identifier cannot be null.LinkNo
Batch result codes were:LinkNo
Current rule set details not found for rule set '%1s'.LinkNo
Current rule set not found for rule set name '%1s'.LinkNo
Details structs were:LinkNo
Error during batch database operation - check log for details.LinkNo
Error processing invocation %1n of %2n - batch result code %3n:LinkNo
Error re-validating derivation for '%1s'.LinkNo
existing entry found for %1s (%2s).LinkNo
MESSAGE CATALOG ENTRY REQUIRED: %1sLinkNo
New rule class not found for moved attribute '%1s' (moving to '%2s').LinkNo
New rule set not found for moved class '%1s' (moving to '%2s').LinkNo
No attribute availability storage row found for attribute availability ID %1s.LinkNo
No database access is allowed at this point.LinkNo
No rule attribute storage row found for rule attribute ID %1s.LinkNo
No rule class storage row found for rule class '%1s'.LinkNo
No rule class storage row found for rule class '%1s' and rule set ID %2s.LinkNo
No rule set storage row found for rule set name '%1s'.LinkNo
Number of results from batch database operation (%1n) does not equal number of invocations of batch operation (%2n).LinkNo
Post migration rule sets contain validation errors - cannot continue with rule set migrationLinkNo
Resource '%1s' not found on classpathLinkNo
Result %1n = %2nLinkNo
Rule attribute not found for current rule available attribute '%1s'.LinkNo
Rule attribute not found for to-be rule available attribute '%1s'.LinkNo
Rule class migration pair not found for '%1s'.LinkNo
Rule set migration pair not found for '%1s'.LinkNo
Rule set not found for to-be rule set '%1s'.LinkNo
The Key Server cache and the Key Server database values are out of sync and therefore this record cannot be inserted. LinkNo
The login ID %1s does not map to a user name.LinkNo
There is more than one rule set with name '%1s'.LinkNo
This attribute value has been removed.LinkNo
To-add rule set not found for rule set name '%1s'.LinkNo
To-be rule set not found for rule set name '%1s'.LinkNo
To-remove rule set not found for rule set name '%1s'.LinkNo
When page is submitted
None
Related Entities
Technical Information
Page IDVerificationAdmin_viewVerificationRequirementFromList
LocationC:\Users\david\dev\src\esystems-inc\Curam_V8_IS\webclient\components\Verification\Verification Admin\Verification Requirement\VerificationAdmin_viewVerificationRequirementFromList.uim
Page Load InterfaceVerificationAdministration.getVerificationRequirementDetails
Page Submit Interface
Linked From PagesRequirements (VerificationAdmin_listVerificationRequirements)