Configuring Evidence Types - The Dynamic Evidence Editor

Basic information about each evidence type is defined during administration. This information includes the name of the evidence type, its logical name, and the name of the related group of security identifiers that are generated in respect of the evidence type. Administrators can subsequently group these generated security identifiers any way they want. However if they wish to grant a user read, create, and maintain rights for an evidence type, the administrator can add the group name defined to the user's role. For information on assigning security identifiers to users, see the Cúram System Configuration Guide.

An effective from date is also specified which allows flexibility for the evidence type to change over time. For example, an agency may configure an evidence type to reflect legislation that says that says the agency must capture a participant's dental records but from the 1st of January the agency needs to capture a participant's medical records. From the 1st of January the medical record evidence type automatically supersedes the dental record evidence type. The system automatically stores a version history of the evidence type records that are effective over time and displays the correct evidence pages related to the evidence type to the case worker at runtime.

Once basic information is defined about the evidence type, a new version of the evidence type is created by default. Administrators can then modify its metadata using the Dynamic Evidence Editor. This effectively designs all of the evidence pages that relate to the evidence type. In general, the editor is used to:

• define all of the attributes that will appear on the evidence pages.
• define all of the evidence pages that relate to the evidence type.
• set up validations on each evidence type, e.g., if a case worker enters hair colour, he must also enter eye colour, or identify duplicate date ranges.
• set up parent/child evidence relationships. For example, Alien Sponsor evidence is child of Alien evidence.
• design how the evidence page will look in the user interface. For example, an administrator can drag fields on to an application page cluster, show one panel on a particular evidence page but not another.

For detailed information on configuring dynamic evidence using the Dynamic Evidence Editor, see the Cúram Dynamic Evidence Configuration Guide.