Moves for Medicine: Difference between revisions
Jump to navigation
Jump to search
TOstryzniuk (talk | contribs) |
TOstryzniuk (talk | contribs) |
||
| Line 12: | Line 12: | ||
*The current “MOVE” data is now much more informative because it not only includes the location that a patient has moved to, but also the date and time therefore we can assess total LOS in ER or in an off-service ward bed. | *The current “MOVE” data is now much more informative because it not only includes the location that a patient has moved to, but also the date and time therefore we can assess total LOS in ER or in an off-service ward bed. | ||
*With the addition of MOVE data,the tagging of “overflows” in variable slots 3 & 5 at the VIC is now redundant (Nov 1.07 stopped). | *With the addition of MOVE data, the tagging of “overflows” in variable slots 3 & 5 at the VIC is now redundant (Nov 1.07 stopped). | ||
Revision as of 17:38, 2008 August 13
Moves for Medicine
- Primary Purpose of MOVE 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.
- Secondary Purpose of MOVE data:
To assess how much time an in-service medicine patient spends on off service wards while still under a medicine service physician's care. (we will assess this in one year and see if there is any useful information there).
- On September 1, 2007, we started capturing medicine ward patient movements (MOVES) in the tmp file on the PDA. This information is sent to an ACCESS database (TMPV2) on the Regional Server.
- The current “MOVE” data is now much more informative because it not only includes the location that a patient has moved to, but also the date and time therefore we can assess total LOS in ER or in an off-service ward bed.
- With the addition of MOVE data, the tagging of “overflows” in variable slots 3 & 5 at the VIC is now redundant (Nov 1.07 stopped).
- need to add more informationTOstryzniuk 17:52, 12 August 2008 (CDT)