Changes between Version 5 and Version 6 of Onyx to PDO

Timestamp:

01/10/12 21:47:10 (12 years ago)

Author:

jeff.lusted

Comment:

--

Onyx to PDO

@@ -17 +17 @@
 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 '''__code lookup__''' is a lookup table. Basically 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.
+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.
 
+The '''__provider dimension__''' holds details of physicians or providers at an institution. Every observation relates (or should relate) to a provider; ie: the observation has been made by a provider. Currently no attempt is made to populate the provider dimension: it is empty.
+
+The '''__patient mapping__''' maps external identifiers (eg: s-number or bpt-number) to an internal i2b2 patient identifier. The favoured way of populating this is via the web service that invokes the CRC loader facility. The alternative is to use a manually supplied number. Either way, the contents of this is relatively uncontroversial.
+
+