Mapping Non-Identical SSN Evidence to Identification Evidence

By configuring the non-identical evidence attribute mapping between these two dynamic evidence types, the evidence broker will share the attributes that match as if it were identical evidence. While the evidence are deemed non identical because they are different types, the attributes mapped between each type allow for any sharing to be treated in the same way as identical evidence. The following steps illustrate how this configuration would be applied in this scenario:

1. Fred completes an online application for benefits and enters the required information along with the following SSN identification details:

   SSN Identification Reference: 123-45-6789

   Type: SSN

   Comments: A brief note.

   Fred did not record any details for SSN Status, No SSN Reason, No SSN Other Details.

2. Fred submits the application to the agency where it is determined,using the search and match process, that he is not registered on the system.
3. Fred is registered as a person. The registration process inserts name, date of birth, and gender which is the mandatory registration information required. The system creates the person evidence records – name, birth and death and gender.
4. An application case for benefits is then created for Fred and all of the evidence that he supplied on his online application is added to the application case. Note an application case is created automatically when the application is submitted, all the evidence captured on his application is mapped to the new application case, using the Cúram Data Mapping Engine.
5. Paul, the intake worker, reviews the application case evidence and authorizes the application case. When the application is authorized, this triggers the evidence broker to share the application evidence based on its configurations.
6. Once the application is authorized, an integrated case is automatically created for Fred and adds the program for which Fred has been approved.
7. The evidence broker shares the evidence from the application case to the integrated case. The SSN details evidence on the application case maps directly to the SSN details evidence on the integrated case.
8. The evidence broker then shares Fred's application evidence to his person tab. The SSN details from the application case are non-identical and must be mapped to the identification evidence stored in the person tab. The system maps the evidence as follows:

   Table 2. Mapping of Evidence when Shared from Application to Person tab

   SSN Details Evidence	Identification Evidence
   SSN Identification Reference	Identification Reference
   Type	Type
   Comments	Comments

9. Later the same day, Fred provides details of his passport that was required to verify his date of birth on the integrated case. The receptionist Jan also decides to capture this information in Fred's identification evidence. She therefore performs a person search and finds Fred's person record. She opens the person record and then proceeds to creating new identification evidence. Jan selects the type is Passport and the Identification reference is PO111111.
10. Jan saves the identification record. The evidence broker is triggered and the identification evidence is shared to the integrated case.
11. Caseworker for the integrated case, Sam, notices there is new incoming evidence received. He views the incoming evidence and notices that a passport/ID has been captured for Fred. Sam decides to reject this evidence because he does not require it for the case. Note that if Sam had accepted the evidence, a new SSN identification evidence record would be displayed as in edit. However, upon activating that evidence, the system may have invoked a validation to say that the type must only be SSN (if no validation on type then this would have been applied to the case).