Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Column 2 represents the concepts in your local i2b2 ontology. Where the concepts are the same in the network and local ontology, then the same values that appear in column 1 should appear in column 2.

Here is a example sql query for creating the 1-to-1 Adaptermappings from the ontology and table access tables:

  select '\\' || ta.c_table_cd || ont.c_fullname as key,
       '\\' || ta.c_table_cd || ont.c_fullname as local_key
  from ONT_TABLE1 ont
  join table_access ta on substr(ont.c_fullname,1,length(ta.c_fullname)) = ta.c_fullname
  where ont.c_visualattributes not in ('FH','FI','LH','LI')
  UNION
  select '\\' || ta.c_table_cd || ont.c_fullname as key,
       '\\' || ta.c_table_cd || ont.c_fullname as local_key
  from ONT_TABLE2 ont
  join table_access ta on substr(ont.c_fullname,1,length(ta.c_fullname)) = ta.c_fullname
  where ont.c_visualattributes not in ('FH','FI','LH','LI')
  UNION
  select '\\' || ta.c_table_cd || ont.c_fullname as key,
       '\\' || ta.c_table_cd || ont.c_fullname as local_key
  from ONT_TABLE3 ont
  join table_access ta on substr(ont.c_fullname,1,length(ta.c_fullname)) = ta.c_fullname
  where ont.c_visualattributes not in ('FH','FI','LH','LI')

NOTE: If your local concepts are the same, but your local TABLE_ACCESS table uses different C_TABLE_CD values, then you will need to edit the prepended C_TABLE_CD values for column 2

...