Changes between Version 6 and Version 7 of LEGACY - ProcessingPidSet


Ignore:
Timestamp:
12/30/11 17:37:01 (12 years ago)
Author:
jeff.lusted
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • LEGACY - ProcessingPidSet

    v6 v7  
    33=== Cardinality, with some examples. ===
    44
     5==== __Example One__ ====
    56First of all, this is wrong. Every pid must have a patient_id.
    67{{{
    … …  
    1112}}}
    1213
    13 
     14==== __Example Two__ ====
    1415This is acceptable:
    1516{{{
    … …  
    2021}}}
    2122
    22 
     23==== __Example Three__ ====
    2324The following example is also acceptable, but implies we know the participant is either:
    2425 * already within the CRC (and that we know the internal identifier = 2) or:
    2526 * this is a new participant and we are ourselves assigning a new i2b2 internal identifier (= 2) for them.
    26 Both situations are ones we can avoid by adopting the approach of the example above, and omitting the HIVE as a source.
     27Both situations are ones we can avoid by adopting the approach of Example Two above, and omitting the HIVE as a source.
    2728{{{
    2829<pid>
    … …  
    3334}}}
    3435
     36==== __Comment__ ====
     37As far as I can tell, a row in the temporary table covers a patient_id / patient_map_id combination. So:
     38 * Example Two would give rise to one row.
     39 * Example Three would give rise to two rows.
     40
    3541=== First Stage: Eliminate Duplicates. ===
     42Any "duplicates" are eliminated from the temporary table.
     43A duplicate is one where another row matches on:
     44 1. patient_id
     45 1. patient_id source
     46 1. patient_map_id
     47 1. patient_map_id source
    3648
    3749=== Second Stage: Process HIVE as a Source. ===