Changes between Version 30 and Version 31 of Onyx Export and Purge

Timestamp:

09/28/11 19:19:29 (13 years ago)

Author:

jeff.lusted

Comment:

--

Onyx Export and Purge

@@ -164 +164 @@
 Another awkwardness is that once a participant is exported, it is only possible (as far as I can see) to look at a limited amount of their data via the Onyx web interface. So validating what is at the end of the Onyx-to-i2b2 trail by manual inspection will be difficult.
 
+=== On Filtering using a Date ===
+
+A further experiment revealed that the filter illustrated below worked, selecting participants with a status of completed where the conclusion questionnaire end date was some time in January, and the participant hadn't been exported before. All the valueTables within the export config file had the same filter. It doesn't take much imagination to work out how to add a further condition to test for year.
+
+
+{{{
+    <valueset entityType="Participant" valueTable="Participants">
+      <entities>
+        <excludeAll />
+        <script type="INCLUDE">
+          <javascript><![CDATA[// Include any ValueSet that has 'COMPLETED' as a value for the 'Participant.Interview.Status' variable
+                               // and the conclusion questionnaire timeEnd is in January
+          ($('Participants:Admin.Interview.status').any('COMPLETED')).
+             and($('ConclusionQuestionnaire:QuestionnaireRun.timeEnd').month().trim().any('0'))
+          ]]></javascript>
+        </script>
+        <script type="EXCLUDE">
+          <javascript><![CDATA[$('Participants:Admin.Interview.exportLog.destination').any('BRICCS.Participants')]]></javascript>
+        </script>
+      </entities>
+    </valueset>
+}}}
+