Data Mapping
Data Mapping
Module 2 contains two tools to help you understand data mapping and to develop a map. We
recommend you use these tools together and follow the step-by-step process.
1. Read through 2.1: Guide to Data Mapping to understand the purpose and benefit of
data mapping and the steps necessary for developing a data map.
2. Work with your system vendor to use 2.2: Data Map Template to develop a map of your
system.
3. Use this map as you train staff for data entry, integrate other systems, or prepare for
reporting.
The same data in most modern systems and databases are Table 1 Table 2
stored in multiple tables or collections of data values held
together in the system. This is called a relational database
because there are fields of the shared/related data in
multiple tables. Names or identification (ID) numbers are
examples of shared/related data.
tribaleval.org
MODULE 2 DATA SYSTEM IMPROVEMENT TOOLKIT
appears in both and establishes a relationship between the two different table names.
There are several methods for mapping databases; two methods are most commonly used to map
data manually. One method is graphical mapping – which involves drawing connections between
the tables (as seen below). This method is easy to follow and allows users to quickly see how fields
may be shared across multiple tables. However, graphic mapping can become difficult to follow
when dealing with very large tables.
Another method is the use of codes. Codes can be manually applied to fields common across
multiple tables. An advantage of using codes is they can later be combined with automation files
called transforms. The transforms allow much of the data mapping process to be done automatically.
tribaleval.org 2
MODULE 2 DATA SYSTEM IMPROVEMENT TOOLKIT
In this example, you can see multiple fields with codes to show the matching fields in other tables.
Colors have been applied to see matches easier.
Contacts Forms
tribaleval.org 3
MODULE 2 DATA SYSTEM IMPROVEMENT TOOLKIT
Step-by-Step Process
Step 1. From your vendor, request a system diagram which includes every table in the
system. If this does not exist, request a comprehensive list of every table in the system.
Step 3. Identify fields where the same information is requested by using different field
name(s).
Step 4. Create a code and highlight color for each field asking for the same information
across multiple tables. You may need to ask your system vendor or run test data (enter
information for a fictional family) to determine if fields contain the same information.
Step 5. Develop a single document (such as 2.2 Data Map Template) that contains all
tables and highlighted field names.
Step 6. Determine which table contains the data entered by staff. In other words, which are
the manually entered data and which are the data being automatically completed by the
system relationships.
Step 7. Draw arrows between these highlighted fields so all are connected. The data entry
point identified in Step 6 is the point where the connected fields begin.
tribaleval.org 4