Content Comparison

...

1. Look up definitions of bins (e.g. logically what do they do, we'll need descriptions too
2. Write up description
3. Write and test query (with :terminology/:version interpolations)

REQUIRED bins

• nci_merge: Merged SCUI current version NCI atoms

  Code Block
  select a.id clusterId, a.id conceptId from concepts a, concepts_atoms b, atoms c where a.terminology = :terminology and a.id = b.concepts_id and b.atoms_id = c.id and c.terminology='NCI' group by a.id having count(distinct c.conceptId)>1

• nci_sub_split: Split SCUI current version NCI (or sub-source) atoms

  Code Block
  TBD: select a.id clusterId, a.id conceptId from concepts a, concepts_atoms b, atoms c where a.terminology = :terminology and a.id = b.concepts_id and b.atoms_id = c.id and c.terminology in (select terminology from root_terminologies where family = 'NCI' and terminology != 'NCI') group by a.id having count(distinct c.conceptId)>1

• sct_sepfnpt: SNOMED concept clusters where the FN and PT terms are separated

• cdsty_coc: Find concepts with Clinical Drug STY and any other STY
   

• multsty:concepts with more than 3 STYs|
   

• styisa:One STY is an ancestor of another in the STY isa hierarchy
   

• sfo_lfo: Short form in one concept, long form in another
   

• deleted_cui: CUIs that are going away - will need bequeathal rel

NON-required bins

• rxnorm_merge
  • Same as nci_merge but with RXNORM
    
    
•  cbo_merge
  • Same as nci_merge but with CBO
• sct_sepfnpt

• rxnorm_split

  Code Block
  see split query above

  
  
  

• nci_pdq_merge
  
  

• nci_sct_merge
  
  

• ambig_no_ncimth_pn
  
  

• ambig_no_mth_pn
  
  

• ambig_no_rel
  
  

• pn_pn_ambig
  
  

• multiple_pn
  
  

• pn_no_ambig
  
  

• ambig_pn
  
  

• pn_orphan
  
  

• cdsty_coc
  
  

• nosty
  
  

• multsty
  
  

• styisa
  
  

• cbo_chem
  
  

• go_chem
  
  

• mdr_chem
  
  

• true_orphan
  
  

• sfo_lfo
  
  

• deleted_cui_split

...