Setting up a new tmp project: Difference between revisions

No edit summary
Line 1: Line 1:
To add a new
The Critical Care and Medicine Database has a flexible method of quickly adding additional values required for temporary [[Projects]]. [[Tmp Project Collection]] explains how or [[data collector]]s collect these.
{{DT|add|}}
 
Here are the pages that document how to run a project:
* if you don't already understand how our project data works, see  [[Entity–attribute–value model of the L Tmp V2 table]] to understand what your options are in our framework
* [[Creating a new project article]] - almost always a good first step, a place to take notes about the details for the project
* Consider if there is data that would benefit from [[Data Integrity Checks]]; if so, they are set up by building a query that will have lines if the test fails and adding that query to [[Function TmpChecker]], which is run as part of [[Pre-send Checker]]
* Add the line(s) for the project to [[s_tmp table]]
** 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]]
 
== "dropdown" functionality ==
 
== [[Automatic Generation of TMP entries]] ==
To make it easier for collectors to know what [[projects]] are currently collected, starting entries for projects that require an entry for ''every'' profile (possibly at a given site/program) are automatically created at profile creation through [[Automatic Generation of TMP entries]].
 
 


[[Category:Tmp Project Infrastructure|*]]
[[Category:Tmp Project Infrastructure|*]]