Automatic Generation of TMP entries: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
[[CCMDB.mdb]] will automatically enter Tmp lines if the entry in s_tmp | |||
* applies to this site | |||
* applies to this program | |||
* active = true | |||
* auto_add_at_patient_creation = true | |||
Further, the program can programmatically enter values for s_tmp entries. If we want to restrict ability to edit those, '''auto_cant_add_manually''' and/or '''auto_cant_edit''' can be set. | |||
''' | == [[S_Tmp]] table usage == | ||
* '''auto_add_at_patient_creation''' - if true then the line is auto-added at patient creation time if applicable for a location '''(not yet implemented)''' | |||
* '''auto_cant_add_manually''' - entry can't be ''added'' manually, ie. will show up in dropdowns | |||
* '''auto_cant_edit''' - entry will not be visible in tmp tab to be ''edited'' manually | |||
Legacy only below here | |||
== Legacy == | |||
Before [[CCMDB.mdb_Change_Log_2012#ver_2012-11-16]], whenever we ran a project using TMP tab entries, data collectors had to generate one or more lines before they could actually enter data, resulting in extra steps. | |||
Shortly after starting [[Postal code collection]] we decided to have CCMDB.mdb automatically generate an entry since, although it is in tmp, it is a permanent item. | |||
== [[CCMDB.mdb_Change_Log_2012#ver_2012-11-16]]== | == [[CCMDB.mdb_Change_Log_2012#ver_2012-11-16]]== | ||
| Line 17: | Line 29: | ||
Added relevant columns to [[S Tmp]] because they were needed for another change implemented in | Added relevant columns to [[S Tmp]] because they were needed for another change implemented in | ||
[[Category: TmpV2]] | [[Category: TmpV2]] | ||
Revision as of 17:33, 16 November 2012
CCMDB.mdb will automatically enter Tmp lines if the entry in s_tmp
- applies to this site
- applies to this program
- active = true
- auto_add_at_patient_creation = true
Further, the program can programmatically enter values for s_tmp entries. If we want to restrict ability to edit those, auto_cant_add_manually and/or auto_cant_edit can be set.
S_Tmp table usage
- auto_add_at_patient_creation - if true then the line is auto-added at patient creation time if applicable for a location (not yet implemented)
- auto_cant_add_manually - entry can't be added manually, ie. will show up in dropdowns
- auto_cant_edit - entry will not be visible in tmp tab to be edited manually
Legacy only below here
Legacy
Before CCMDB.mdb_Change_Log_2012#ver_2012-11-16, whenever we ran a project using TMP tab entries, data collectors had to generate one or more lines before they could actually enter data, resulting in extra steps.
Shortly after starting Postal code collection we decided to have CCMDB.mdb automatically generate an entry since, although it is in tmp, it is a permanent item.
CCMDB.mdb_Change_Log_2012#ver_2012-11-16
- added/changed entries in s_tmp to autogenerate lines
- for postal code, just checked "auto_add_at_patient_creation"
- for Overstay had to create generic lines collectors can change to acceptable lines
- created sub add_automatic_tmp_entries and append query s_tmp__auto_record_adder to add lines
- added function call to cb_addPt_Click(), removed old code that generated Postal Codes since this will take care of it
- updated query check_overstay_not_entered to ensure that auto entries for overstay won't slip through as completed
CCMDB.mdb_Change_Log_2012#ver_2012-10-19
Added relevant columns to S Tmp because they were needed for another change implemented in