The converters provided with the application can be extended to allow conversion
of custom database columns to person/prospect person dynamic evidence. Interfaces are available
for each evidence type and can be found in the package curam.pdc.impl,
these are listed below. Custom implementations can be written that make use of these
interfaces, depending on the evidence type.
Converter Extension (Populator) Interfaces
- PDCAddressEvidencePopulator
- PDCAlternateIDEvidencePopulator
- PDCAlternateNameEvidencePopulator
- PDCBankAccountEvidencePopulator
- PDCBirthAndDeathEvidencePopulator
- PDCContactPreferencesEvidencePopulator
- PDCEmailAddressEvidencePopulator
- PDCGenderEvidencePopulator
- PDCPhoneNumberEvidencePopulator
- PDCRelationshipsEvidencePopulator
The majority of the interfaces have one method populate.
It accepts varying parameters depending on the evidence types.
PDCBirthAndDeathEvidencePopulator and PDCGenderEvidencePopulator,
interfaces have two methods, populatePerson and populateProspectPerson.
populatePerson accepts four parameters:
- concernRoleKey - unique identifier for the concern role that this evidence is relating to
- caseIDKey - the unique identifier of the Participant Data Case
- personDtls - the struct containing the extended person details from the legacy table
- dynamicEvidenceDataDetails - the dynamic evidence details
populateProspectPerson also accepts four parameters:
- concernRoleKey - unique identifier for the concern role that this evidence is relating to
- caseIDKey - the unique identifier of the Participant Data Case
- prospectPersonDtls - the struct containing the extended prospect person details from the legacy table
- dynamicEvidenceDataDetails - the dynamic evidence details