Version 6 (modified by 13 years ago) ( diff ) | ,
---|
Processing the Patient Identifer Set during a Load.
Cardinality, with some examples.
First of all, this is wrong. Every pid must have a patient_id.
<pid> <patient_map_id source="BRICCS">BPt00000040</patient_map_id> <patient_map_id source="UHLT">Snnnnnnn</patient_map_id> </pid>
This is acceptable:
<pid> <patient_id source="BRICCS">BPt00000040</patient_id> <patient_map_id source="UHLT">Snnnnnnn</patient_map_id> </pid>
The following example is also acceptable, but implies we know the participant is either:
- already within the CRC (and that we know the internal identifier = 2) or:
- this is a new participant and we are ourselves assigning a new i2b2 internal identifier (= 2) for them.
Both situations are ones we can avoid by adopting the approach of the example above, and omitting the HIVE as a source.
<pid> <patient_id source="HIVE">2</patient_id> <patient_map_id source="BRICCS">BPt00000040</patient_map_id> <patient_map_id source="UHLT">Snnnnnnn</patient_map_id> </pid>
First Stage: Eliminate Duplicates.
Second Stage: Process HIVE as a Source.
Third Stage: Not using HIVE as a Source.
Note:
See TracWiki
for help on using the wiki.