Unify and manage your data

Crosswalk Patterns

You can define Crosswalk patterns for structuring data from source systems.

Data from Source systems can be structured in a number of ways. As an example, the address data for an HCP (Individual) could be provided as follows:

  • 1:1 Flat file with each row containing the HCP details as well as the address. If multiple HCPs worked at the same address, the address data would be repeated for each HCP.

  • 1:M relational data with two tables, one for the HCP and one for ADDRESS. If multiple HCPs worked at the same address, there would be one entry in the ADDRESS table, and the Foreign Key in the HCP table would reference the Primary Key of the relevant address in ADDRESS.

  • M:M relational data with three tables, one for the HCP, one for the ADDRESS and an intersection table for the HCP_ADDRESS containing the PKs of both the HCP and ADDRESS tables. This approach is used when an HCP can be associated with multiple addresses. If multiple HCPs worked at the same address, there would be one entry in the ADDRESS table, one entry in the HCP table and the HCP_ADDRESS table would contain one record with the FKs from both the other tables for each HCP.