L TmpV2 table: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
 
(26 intermediate revisions by 2 users not shown)
Line 1: Line 1:
Nov 1.13 - Hi everyone: RE: TMP
{{DISPLAYTITLE:L_TmpV2 table}}L_TmpV2 table in [[CCMDB.accdb]] and [[Centralized_data.mdb]] contains data that is either intermittent or just not currently accommodated in the rest of the database. All data that is stored in this table can be found at [[Projects]].
*Please do not enter date and times for studies into TMP until you have confirmed a DX of VAP or CLI exists.  Please don't use this as a note section as a reminder to yourself. Use your note section.  Few problem using TMP for own reminders: when you send files in each week, incomplete files also get sent into the a centralized database. Things like VAP, CLI dates get sent in for all complete and incomplete files each week you send. Obviously once complete and final sent, this information is not longer sent each week.  Problem is this:  Julie mines the database daily. She provides QA data monthly using this information. If she finds a date for CLI or VAP here, she reports it because it is entered there.  What happens later is that when she is crosschecking for final reports and she is finding that for a patient there is no DX for VAP or CLI but in TMP there is a date.  Opposite also happens.  When we follow up with collector, Pagasa is told, just delete the TMP date even though collector cannot remember if they forgot to code the DX or forgot to delete the date in TMP for the VAP or CLI. Thanks for your help with this.   
**FYI: Each week when you send data, any INCOMPLETE files are also sent to TMPV2 database.  So if you put in a TMP CLI or VAP as only reminder to self then when Julie is asked for reports on CLI or VAP, she picks this up for her report from the TMPV2 database. This affect the data in that it reduces the number days between CLI dates.  We have no way of knowing that this only a reminder for you not a confirmed CLI or VAP.  [[User:TOstryzniuk|Trish Ostryzniuk]] 15:33, 2013 November 1 (CDT )


=== Entity–attribute–value model ===
See [[Entity–attribute–value model of the L Tmp V2 table]]


L_TmpV2 table (also know as '''Tmp file''')in the [[CCMDB.mdb]] contains data 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]] (some data is sent every time, some only when the patient is sent, see [[S Tmp Complete_send]] for more.)
=== Linking ===
This table is linked to [[L_Log table]] by [[D_ID]]. See [[CCMDB Data Structure]] for more info.


Usually the data in L_TmpV2 will be data generated by [[:Category:Special Short Term Projects | Special Short Term Projects]] but some other permanently collected data such as [[ER Wait]] & [[Postal code collection]] is stored here as well.
===Data Structure===
 
To see the most up-to-date data structure of this table, see most up-to-date [[CCMDB data.mdb]] in [[Regional Server]]\data\Master. The fields are used differently depending on project, see [[Projects]] for a list and the individual project pages for field usage.
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 any projects that have been stored in L_TmpV2, see  [[:Category:L TmpV2 Data | Category:L TmpV2 Data]].
 
==Data Structure==
To see the most up-to-date data structure of this table, see most up-to-date ccmdb_data.mdb in [[Regional Server]]\data\Master [[CCMDB.mdb]].
 
{| class="wikitable" border=1 <hiddentext> set to 0 for no borders</hiddentext>
|- style="font-size:11pt"  valign="bottom"
| width="89" height="16" | Field Name
| width="74" | Data Type
| width="230" | Usage
 
|- style="font-size:11pt"  valign="bottom"
| height="16" | Serial
| Number
| unique identifier of patient
 
|- style="font-size:11pt"  valign="bottom"
| height="16" | Site
| dropdown-limited text
| Hospital where the patient was admitted
 
|- style="font-size:11pt"  valign="bottom"
| height="16" | Location
| dropdown-limited text
| Ward the patient was admitted to
 
|- style="font-size:11pt"  valign="bottom"
| height="16" | collected
| Date/Time
| date the variable was collected
 
|- style="font-size:11pt"  valign="bottom"
| height="16" | Project
| dropdown-limited text
| &nbsp;
 
|- style="font-size:11pt"  valign="bottom"
| height="16" | Item
| Text
| Project-Item identifier
 
|- style="font-size:11pt"  valign="bottom"
| height="16" | DtTm_var
| Date/Time
| date/time variable collected, if needed
 
|- style="font-size:11pt"  valign="bottom"
| height="16" | int_var
| number
| integer variable, if collected
 
|- style="font-size:11pt"  valign="bottom"
| height="16" | float_var
| number
| float/real variable, if collected
 
|- style="font-size:11pt"  valign="bottom"
| height="16" | bool_var
| Yes/No
| boolean variable, if collected
 
|- style="font-size:11pt"  valign="bottom"
| height="16" | comment_var
| Text
| comment variable, if collected
 
|- style="font-size:11pt"  valign="bottom"
| height="16" | Instruction
| dropdown-limited text
| Instruction as given in the dropdown [[S_Tmp]]
 
|- style="font-size:11pt"  valign="bottom"
| height="16" | data_sent
| Date/Time
| Date/Time the patient was sent


{| class="wikitable sortable"
|-
! Field Name !! position !! type !! description
|-
| Tmp_ID ||1 || AutoNumber (Long integer)|| unique identifier of tmp entry
|-
| Pat_ID/[[D_ID]] ||2 || ||
|-
| Project ||3 || text () || Ward the patient was admitted to
|-
| Item ||4 || text () || date the variable was collected
|-
| obsdate ||5 || Date/Time || automatically entered date of collection
|-
| obstime ||6 || Date/Time || automatically entered time of collection
|-
| date_var ||7 || Date/Time || date, if collected
|-
| time_var ||8 || Date/Time || time, if collected
|-
| int_var ||9 || number (long integer) || integer variable, if collected
|-
| float_var ||9 || number (double) || float/real variable, if collected
|-
| bool_var ||10 || Yes/No || boolean variable, if collected
|-
| comment_var ||11 || Text || comment variable, if collected
|}
|}


== Related articles ==
{{Related Articles}}


 
<noinclude>
[[Category: Data structure]]
[[Category:Project | *]]
[[Category: L_TmpV2 Data]]
[[Category:Data structure]]
[[Category: TmpV2]]
[[Category:L_TmpV2 Data | *]]
[[Category: All Projects]]
[[Category:TmpV2 | *]]
[[Category:L TmpV2 table | *]]
[[Category:L Table]]
</noinclude>

Latest revision as of 12:48, 2023 June 27

L_TmpV2 table in CCMDB.accdb and Centralized_data.mdb contains data that is either intermittent or just not currently accommodated in the rest of the database. All data that is stored in this table can be found at Projects.

Entity–attribute–value model

See Entity–attribute–value model of the L Tmp V2 table

Linking

This table is linked to L_Log table by D_ID. See CCMDB Data Structure for more info.

Data Structure

To see the most up-to-date data structure of this table, see most up-to-date CCMDB data.mdb in Regional Server\data\Master. The fields are used differently depending on project, see Projects for a list and the individual project pages for field usage.

Field Name position type description
Tmp_ID 1 AutoNumber (Long integer) unique identifier of tmp entry
Pat_ID/D_ID 2
Project 3 text () Ward the patient was admitted to
Item 4 text () date the variable was collected
obsdate 5 Date/Time automatically entered date of collection
obstime 6 Date/Time automatically entered time of collection
date_var 7 Date/Time date, if collected
time_var 8 Date/Time time, if collected
int_var 9 number (long integer) integer variable, if collected
float_var 9 number (double) float/real variable, if collected
bool_var 10 Yes/No boolean variable, if collected
comment_var 11 Text comment variable, if collected

Related articles

Related articles: