Changes between Version 7 and Version 8 of Onyx to PDO

Timestamp:

01/10/12 22:12:35 (13 years ago)

Author:

jeff.lusted

Comment:

--

Onyx to PDO

@@ -15 +15 @@
  1. Code lookup
 
-The '''__concept dimension__''' can be considered immaterial to importing onyx data into i2b2 on a routine basis. The assumption here is that the concept dimension should be in synch with the ontology cell where the main ontology data is held. Currently, this assumption is safeguarded by previous steps in the process which updates both the ontology cell and the ontology dimension before we import any participant data.
+The '''__concept dimension__''' can be considered immaterial to importing onyx data into i2b2 on a routine basis. The assumption here is that the concept dimension should be in synch with the ontology cell where the main ontology data is held. Currently, this assumption is partly safeguarded by previous steps in the process which update both the ontology cell and the ontology dimension before we import any participant data.
 
 The '''__code lookup__''' is a lookup table. Basically this is a code-to-description mapping (eg, LCBRU : Leicester Cardiovascular Biomedical Research Unit). Currently no attempt is made to populate the lookup table: it is empty. The code lookup table is considered here to be a minor issue.
@@ -28 +28 @@
 
 The '''__visit dimension__'''  holds one row for every visit/encounter/event that a patient is involved in. What is an event with respect to the BRICCS questionnaire? Currently, the process creates just one event for each participant in the questionnaire.
+
+The '''__patient dimension__'''  holds one row for every patient (ie: for every participant interviewed in the questionnaire).
+
+The '''__observation facts__''' holds one row for every fact (deemed sensible to include) that has been gleaned about a participant from the questionnaire.