Mapping ADC database tables to Vocabulary Entities
Not all Vocabulary entities must be mapped to corresponding database tables - only those entities whose attribute values need to interact with the external database should be mapped.
In this example, database metadata containing a table named Patient was imported. Because the table’s name spelling matches the name of the entity Patient, the Table Name field was mapped automatically, and displayed in light gray, as shown:
Figure 365. Smart match mapping of Vocabulary Entity
If the automatic mapping feature fails to detect a match for any reason (different spellings, for example), then you must make the mapping manually. In the Table Name field, use the drop-down list to select the appropriate database table to map. The selection is displayed in black, as shown:
Figure 366. Manual Mapping of Valid Vocabulary Entity
If you choose to type in the name of a table and that table is not in the database's metadata, the property value displays in orange, as shown:
Figure 367. Manual Mapping of Invalid Vocabulary Entity
