Data Preparation
| ATTENTION: This page has been migrated to the Tazama GitHub repository and is now located at: https://github.com/frmscoe/docs/blob/main/Product/transaction-monitoring-service-api.md This page will no longer be maintained in Confluence. |
|---|
Data Preparation (DP)
In the data preparation phase, we address some of the challenges and risks in the various data sources received.
We start by resolving the transaction participants into unique entities - Entity resolution is a complex subject, so we have provided dedicated section on what we mean by Entity Resolution.
Having identified a unique individual we then start the process of pseudonymisation and removing personal identifying information. This allows us to continue processing but have reduced the risk of exposing personally identifiable information (PII). This approach has the added benefit of reducing PII that could affect the decisions of an investigator in the Case Management System. We have provided further information on the considerations for Pseudonymisation to assist
Given not all key information is held within an ISO20022 message, there is the option to further enrich data at this stage.
The message history is saved to persistent storage and the various transaction network graphs (that are used by some rule processors) are updated before the transaction is sent on to the Channel Router and Setup processor for processing.