Setting up a new tmp project: Difference between revisions

Line 15:

* document these, and specific collection instructions, on the wiki page for the project

** ask for input and feedback from collectors on this early and throughout the project to make sure you get the data you want

* consider if the [[#project will only run at some sites or for one program]]

== Set-up ==

* add records to the [[s_tmp table]] as per [[#Project Design]]; these can be added early and s_tmp.active=false until the day of go-live

Line 28:

== Additional info and options ==

If an entry will need to be added programmatically from VBA eg based on other data and a collector input, use [[Function GenerUpdate_tmp_entry]]. For an example of this, consider [[Overstay2 Overview]].

=== project will only run at some sites or for one program ===

* To make the project only show up for some sites, enter an (almost) identical line for each site and enter the hospital in [[s_tmp]].site

* If the project should only be collected for one [[program]], enter that program into [[s_tmp]].program; since we only collect two [[program]]s additional lines should not be required.

=== [[Data Integrity Checks]] ===

* If there is data that would benefit from [[Data Integrity Checks]], consider [[Setting up a new CCMDB Data Integrity Check]]

** generically, if the combination of Project/Item has no corresponding Study/Value entry in [[s_tmp table]] then [[query s_tmp_project_item_consistent]] will flag the query during [[Pre-send Checker]]

** ~~To make them only show up for one [[Program]]~~, ~~eg a CC project, add that program's key to the program column~~

** To make the project only show up for some sites, enter an (almost) identical line for each site and enter the hospital in the ''hosp'' column

** if the combination ~~doesn't exist~~ in [[s_tmp table]] then [[query s_tmp_project_item_consistent]] will flag the query during [[Pre-send Checker]]

=== [[Automatic Generation of TMP entries]] ===

@@ Line 15: / Line 15: @@
 * document these, and specific collection instructions, on the wiki page for the project
 ** ask for input and feedback from collectors on this early and throughout the project to make sure you get the data you want
+* consider if the [[#project will only run at some sites or for one program]]
 == Set-up ==
 * add records to the [[s_tmp table]] as per [[#Project Design]]; these can be added early and s_tmp.active=false until the day of go-live
@@ Line 28: / Line 28: @@
 == Additional info and options ==
 If an entry will need to be added programmatically from VBA eg based on other data and a collector input, use [[Function GenerUpdate_tmp_entry]]. For an example of this, consider [[Overstay2 Overview]].
+=== project will only run at some sites or for one program ===
+* To make the project only show up for some sites, enter an (almost) identical line for each site and enter the hospital in [[s_tmp]].site
+* If the project should only be collected for one [[program]], enter that program into [[s_tmp]].program; since we only collect two [[program]]s additional lines should not be required.
 === [[Data Integrity Checks]] ===
 * If there is data that would benefit from [[Data Integrity Checks]], consider [[Setting up a new CCMDB Data Integrity Check]]
+** generically, if the combination of Project/Item has no corresponding Study/Value entry in [[s_tmp table]] then [[query s_tmp_project_item_consistent]] will flag the query during [[Pre-send Checker]]
-** To make them only show up for one [[Program]], eg a CC project, add that program's key to the program column
-** To make the project only show up for some sites, enter an (almost) identical line for each site and enter the hospital in the ''hosp'' column
-** if the combination doesn't exist in [[s_tmp table]] then [[query s_tmp_project_item_consistent]] will flag the query during [[Pre-send Checker]]
 === [[Automatic Generation of TMP entries]] ===