Category:Task Elements: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
Line 1: Line 1:
We are collecting tasks as indicators of quality care, nursing work load and for other future uses. When you collect tasks, think of them as '''not''' only an indicator of nursing workload. Please follow the guidelines given in the individual article for each task, and these guidelines will be taken into account for any analysis of task data.  
We are collecting tasks as indicators of quality care, nursing work load and for other future uses. When you collect tasks, think of them as '''not''' only an indicator of nursing workload. Please follow the guidelines given in the individual article for each task, and these guidelines will be taken into account for any analysis of task data.  


Tasks are collected in [[L_Dxs]] because at the time we started collecting this we were limited in where/how we could store data. Accordingly, the task options are stored in [[S AllDiagnoses]].
To facilitate task collection CCMDB.mdb automatically adds a task entry "fill" for each of the tasks for every new patient. The corresponding dx codes sort before the allowed tasks, so clicking on any one of them will bring up the allowed tasks as next options. Using a "fill" task instead of defaulting to "none" will prevent anyone from just forgetting to set this while still facilitating easier entry of tasks.
 
To facilitate task collection in starting in [[CCMDB.mdb_Change_Log_2010#ver_1.9951 | CCMDB.mdb ver 1.9951]] sometime after 2010-Oct-29 we will start to automatically add a task entry "fill" for each of the tasks. The corresponding dx codes are ((task - none) - 1) which means the "fill" tasks sort before the allowed tasks, so clicking on any one of them will bring up the allowed tasks as next options. Using a "fill" task instead of defaulting to "none" will prevent anyone from just forgetting to set this while still facilitating easier entry of tasks.


==Start Date==
==Start Date==
*Start Date: '''December 15, 2006'''; Medicine Program only (in Task.mdb collection started on Dec 19.2006)
*Start Date: '''December 15, 2006'''; Medicine Program only (in Task.mdb collection started on Dec 19.2006)
A comment regarding improving the input for the tasks once the laptop arrives has been added to [[Requested CCMDB changes for the next version#Improve Data Entry for Tasks]]


== Why not default to "none" ==  
== Why not default to "none" ==  
Line 15: Line 11:
==Legacy==
==Legacy==
When the [[:Category:MOST |MOST]] Score was implemented for the Medicine Program, the collection of [[iTISS]] data was stopped. A need was identified to continue to collect some information on nursing workload therefore the medicine program adopted a list of [[:Category: Task Elements | Task Elements]] they wanted to track.
When the [[:Category:MOST |MOST]] Score was implemented for the Medicine Program, the collection of [[iTISS]] data was stopped. A need was identified to continue to collect some information on nursing workload therefore the medicine program adopted a list of [[:Category: Task Elements | Task Elements]] they wanted to track.
 
Tasks are collected in [[L_Dxs]] because at the time we started collecting this we were limited in where/how we could store data. Accordingly, the task options are stored in [[S AllDiagnoses]].




[[Category: Medicine Elements]]
[[Category: Medicine Elements]]
[[Category: Data Integrity Rules ]]
[[Category: Data Use]]
[[Category: Data Use]]

Revision as of 13:36, 2011 May 4

We are collecting tasks as indicators of quality care, nursing work load and for other future uses. When you collect tasks, think of them as not only an indicator of nursing workload. Please follow the guidelines given in the individual article for each task, and these guidelines will be taken into account for any analysis of task data.

To facilitate task collection CCMDB.mdb automatically adds a task entry "fill" for each of the tasks for every new patient. The corresponding dx codes sort before the allowed tasks, so clicking on any one of them will bring up the allowed tasks as next options. Using a "fill" task instead of defaulting to "none" will prevent anyone from just forgetting to set this while still facilitating easier entry of tasks.

Start Date

  • Start Date: December 15, 2006; Medicine Program only (in Task.mdb collection started on Dec 19.2006)

Why not default to "none"

We thought about defaulting these to "none" but decided not to do this because some of them are rare and the risk of missing those if they are always defaulted would be to great. Ttenbergen 10:26, 3 November 2010 (CDT)

Legacy

When the MOST Score was implemented for the Medicine Program, the collection of iTISS data was stopped. A need was identified to continue to collect some information on nursing workload therefore the medicine program adopted a list of Task Elements they wanted to track. Tasks are collected in L_Dxs because at the time we started collecting this we were limited in where/how we could store data. Accordingly, the task options are stored in S AllDiagnoses.

Subcategories

This category has only the following subcategory.

T