L TmpV2 table: Difference between revisions
Ttenbergen (talk | contribs) mNo edit summary |
TOstryzniuk (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
The '''L_TmpV2''' table contains data on the PDA and in the [[CCMDB.mdb]] that is either intermittent or just not currently accomodated in the rest of the database. When the data collector sends, the data gets dumped to [[Regional Server]]\Output\TmpV2_1.mdb | The '''L_TmpV2''' table contains data on the PDA and in the [[CCMDB.mdb]] that is either intermittent or just not currently accomodated in the rest of the database. When the data collector sends, the data gets dumped to [[Regional Server]]\Output\[[TmpV2_1.mdb]] | ||
The table has fields to accomodate dates, integers, reals/floating point variables, text or booleans. It can accomodate one of each of these per line, such that if two variables of the same data type are needed, two lines need to be entered. The table was set up this way to accomodate any possible combination of data, but this flexibility comes at the expense of some inefficiencies in data-entry. | The table has fields to accomodate dates, integers, reals/floating point variables, text or booleans. It can accomodate one of each of these per line, such that if two variables of the same data type are needed, two lines need to be entered. The table was set up this way to accomodate any possible combination of data, but this flexibility comes at the expense of some inefficiencies in data-entry. | ||
Revision as of 16:37, 5 January 2009
The L_TmpV2 table contains data on the PDA and in the CCMDB.mdb that is either intermittent or just not currently accomodated in the rest of the database. When the data collector sends, the data gets dumped to Regional Server\Output\TmpV2_1.mdb
The table has fields to accomodate dates, integers, reals/floating point variables, text or booleans. It can accomodate one of each of these per line, such that if two variables of the same data type are needed, two lines need to be entered. The table was set up this way to accomodate any possible combination of data, but this flexibility comes at the expense of some inefficiencies in data-entry.
For details about the dropdown options for various projects, and their actual project identifier, see the corresponding project's article. For a list of these projects, see Category:L_TmpV2 Data.
Data Structure
| Field Name | Data Type | Usage |
| Serial | Number | unique identifier of patient |
| Site | dropdown-limited text | Hospital where the patient was admitted |
| Location | dropdown-limited text | Ward the patient was admitted to |
| collected | Date/Time | date the variable was collected |
| Project | dropdown-limited text | |
| Item | Text | Project-Item identifier |
| DtTm_var | Date/Time | date/time variable collected, if needed |
| int_var | number | integer variable, if collected |
| float_var | number | float/real variable, if collected |
| bool_var | Yes/No | boolean variable, if collected |
| comment_var | Text | comment variable, if collected |
| Instruction | dropdown-limited text | Instruction as given in the dropdown S_Tmp |
| data_sent | Date/Time | Date/Time the patient was sent |