Changes between Version 13 and Version 14 of LEGACY - i2b2 - The algorithms applied to importing a PDO

Timestamp:

12/29/11 14:25:37 (13 years ago)

Author:

jeff.lusted

Comment:

--

LEGACY - i2b2 - The algorithms applied to importing a PDO

@@ -66 +66 @@
 Detailed processing will be reviewed later. For the moment, there are two observations I think need to be made:
 
- * 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/or 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 (multiple processes doing the same thing at the same time). However, although we know what a participant is, we are still somewhat in the dark concerning events: what is an event in terms of a source system?
+ * 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. I've made one pass at code reading this, and feel reasonably confident. 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/or 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 (multiple processes doing the same thing at the same time). However, although we know what a participant is, we are still somewhat in the dark concerning events: what is an event in terms of a source system?
 
  * All seven sets or some subset of the seven can be supplied. Even if all seven were supplied, the loader message itself (the web service message that triggers the load process) contains control data which can specify which sets of those present should be processed. The processing will always be done in the above order, even if it has gaps, but see the next section for dependencies.