skip to main content
Corticon Server: Data Integration Guide : Getting Started with Multiple Database Connectivity : Import multiple Datasource metadata into a Vocabulary : A closer look at MDB metadata

Try Corticon Now
A closer look at MDB metadata
When the two Datasources defined in the Vocabulary text bring in their metadata, the Treatment Entity is shown to have bindings to both Datasources through the Attribute medicalCode.
Figure 333. Multiple Datasources bound to the Treatment Entity
The linkage enables each execution to take the medicalCode value in the request to access the corresponding treatmentCode and the data in its row in the other Datasource.
Figure 334. Multiple Datasources bound to the medicalCode Attribute
You can consolidate the data from tables and columns residing in different schemas into one intelligent vocabulary entity that can apply rules across the consolidated data. The rules modeler does not need to be concerned about how the data is sourced -- rules can be written to one, simplified semantical representation of the underlying database model.
The description value is in grey indicating that SmartMatch found an unambiguous match of precisely the same name in the CMSDetails Datasource.
Figure 335. Lookup of description value from the related Datasource
When tests are run, both Datasources are connected to seamlessly provide the output of their combined data.
Figure 336. Ruletest that gets output from multiple Datasources