Page History
...
A common problem while integrating data sets from heterogenes heterogeneous sources in a Data Warehouse is to provide a mapping of data not only on a syntactical level, but also on a semantical level. In i2b2, every instance of an observation_fact has an association to an instance of a concept in concept_dimension. i2b2 concepts are rather straightforward. From a terminologcal terminological perspective, they mainly consist of an identifier and a label. Furthermore, concepts are arranged hierarchically by a broader/narrower relation. In particular, there is no attribute defining the meaning of a concept. So, if there exists a concept gender in a clinical trial and a second concept gender in a registry, there is no way of recognizing whether they are equivalent. In fact, from i2b2's perspective, they are as much different as any other concept is.
Medical terminologies as human-curated ontologies play an important part in providing a common understanding but in reality, most data elements imported from sources like the clinical data management system, epidemiological registries, survey tools from longitudinal cohorts or the local EHR won't have an explicit annotation refencing referencing terminologies.
A Metadata Repository (MDR) is a central registry of such data elements. Various MDRs exist, most popular the NCI caDSR, but also Australia's METeOR.
...
Name | Description |
|---|---|
MDR Start Designation | This is the ID of the label that designates the root container you want to import, e.g. a clinical trial specification. |
MDR Base URL | The host the MDR is running on. |
MDR Instance | In case multiple instance of the MDR are running on the host in different contexts, the right one is specified here. |
Outlook
It is planned for the near future, when research grant resources bubble up, to implement a more convenient way of browsing through the MDR by providing access similar to Datasource Servers.
