The first step is to work out the Evidence requirements for a project. Describing this exercise is beyond the scope of this document, but it will be based upon program requirements, administrative and legislative policy, and other business needs. Once the evidence requirements have been identified, these must be mapped onto Cúram-shipped Dynamic Evidence Types.
In some cases, this will result in a requirement to create completely new, project-specific Dynamic Evidence Types to implement the data requirements of their programs. In other cases, customers will want to change or augment Cúram-supplied Dynamic Evidence Types.
In either case, Dynamic Evidence Type specifications must be defined using the Dynamic Evidence Administration pages and the Dynamic Evidence Editor; See Dynamic Evidence Types and Dynamic Evidence Type Versions for more details.