Changes between Version 9 and Version 10 of LEGACY - i2b2 - The algorithms applied to importing a PDO
- Timestamp:
- 12/29/11 10:35:22 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
LEGACY - i2b2 - The algorithms applied to importing a PDO
v9 v10 52 52 </pdo:patient_data> 53 53 }}} 54 55 === Order of Processing === 56 The loader processes the PDO in the order displayed in the above XML skeleton; ie: 57 58 1. pid_set 59 1. eid_set 60 1. patient_set 61 1. event_set 62 1. concept_set 63 1. observer_set 64 1. observation_set 65 66 There are two observations I think need to be made about this: 67 68 * I believe that processing the pid_set and eid_set first in the work flow allows the loader to be in control in assigning i2b2 internal identifiers to patients and to events. That is: there is no need for i2b2 internal id's to somehow be manufactured and placed in the PDO '''''beforehand'''''. The source and source identifiers (eg: BRICCS participant id and s-number) can be used as patient identifiers and the loader will take care of assigning internal ids and mapping them to the external source ids. This is a big gain: the process is transactional, it is database independent and there are no problems with concurrency.