Information gathered in the life event script is stored in the data store schema defined for the life event. In order to pass this information into the Cúram system it must be mapped to dynamic evidence entities. Dynamic Evidence entities must be firstly defined in the Rules and Evidence section of the administration application. Once defined, these entities must be specified as Social Record Evidence Types in the Universal Access section of the administration application. An indicator is also provided which will allow an administrator to dictate if a particular evidence type will be visible to a citizen in the portal(My Information in the citizen account) or not. Once the social record evidence entities are defined, the Data Mapping Editor( accessible from the Mappings tab on the life event) can be used to map the data from the data store to the appropriate evidence entities.
When a life event is submitted from the portal the information gathered is mapped (using the mappings defined above) to evidence entities associated with a new case type called a social record case. The Evidence Broker can then be used to pass the information from this case to the appropriate ongoing client cases.
For more information on Dynamic Evidence see the Cúram Dynamic Evidence Configuration Guide. For more information on data mapping see the Cúram Data Mapping Editor Guide. For more information on the brokering of evidence see the Cúram Evidence Broker Guide.