Moves for Medicine: Difference between revisions
Jump to navigation
Jump to search
TOstryzniuk (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) |
||
| Line 4: | Line 4: | ||
==Collection Guideline== | ==Collection Guideline== | ||
Use '''Moves''' project entries. | |||
For each patient move, enter the <? to, from?> ward as the '''item''', and the date? time? at which <what> actually happened. | |||
== Legacy Data== | == Legacy Data== | ||
Revision as of 17:47, 2009 September 16
We collect "Moves" data to assess
- the time delay from when a patient is first accepted to Medicine Service in ER (emergency room) to when the patient actually arrives in a medicine ward bed
- how much time an in-service medicine patient spends on off service wards while still under a medicine service physician's care.
Collection Guideline
Use Moves project entries.
For each patient move, enter the <? to, from?> ward as the item, and the date? time? at which <what> actually happened.
Legacy Data
- Collection was started September 1, 2007
- Collection of Moves data made tagging of “overflows” in variable slots 3 & 5 at the VIC redundant (Nov 1.07 stopped).
- we will review this within one year
- attempted to bring this up at steering comittee meetings for review and analysis without success so farTtenbergen 18:26, 16 September 2009 (CDT)
- will review with the CTU transition team (Tina emailed Sept 16 09)Ttenbergen 18:26, 16 September 2009 (CDT)
Data Structure
We capture medicine ward patient movements (moves) in L_TmpV2. The data is sent to and stored in TmpV2_1.mdb.