ALERT Scale timing of assessment: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Ppiche (talk | contribs)
mNo edit summary
Line 10: Line 10:
* Why would this be an exceptional instruction for STB? What is different about the situation there that would lead to different instructions?  
* Why would this be an exceptional instruction for STB? What is different about the situation there that would lead to different instructions?  
  [[User:Ttenbergen|Ttenbergen]] 11:12, 2021 April 1 (CDT)
  [[User:Ttenbergen|Ttenbergen]] 11:12, 2021 April 1 (CDT)
 
**This has always been collected at STB this way. (Pam)
*This has always been collected at STB this way.
*** That doesn't mean it should stay that way since we used to collect ''all'' of this only upon arrival. So let's discuss at Task what this should be. The difference is probably really minor, but if we have exceptions it should be clear why. [[User:Ttenbergen|Ttenbergen]] 13:57, 2021 April 1 (CDT)
}}
}}


Line 17: Line 17:
* Direct transfers that bypass the ER take the value on arrival to your unit.
* Direct transfers that bypass the ER take the value on arrival to your unit.


== vs [[Selection and timing of APACHE components]] ==
{{Timing for ALERT vs APACHE}}
{{TT|
* Should we merge this with [[Selection and timing of APACHE components]]? Med doesn't collect all of these, but those that are collected should probably be collected following the same instructions... This especially should be reviewed since we no longer make a distinction between EMIPs and inpts for most other instructions. Should this instruction instead simply be:
** "Use the most recent value before service acceptance. If no value is available before service acceptance, use the first value available after service acceptance."
* if we reject this change, we should at least state once and for all that they are similar but different, and why. [[User:Ttenbergen|Ttenbergen]] 14:29, 2020 December 23 (CST)
** No, we can not merge these two because the definitions are still different. See further comments on counterpart page and integrate before deleting question. [[User:Ttenbergen|Ttenbergen]] 13:34, 2021 February 22 (CST)
}}


== Related articles ==  
== Related articles ==  

Revision as of 12:57, 2021 April 1

This article explains which time/entry of vital signs to use for the ALERT Scale.

Collection Instructions

  • When a patient is admitted from the emergency department, use the values that are closest but prior to the time medicine service accepts the patient to their service (ie Accept DtTm).
  • When patients move between wards or from an icu to a ward use the values that are closest but prior to discharge/transfer from the sending service.
  • For STB Medicine: Patients transferred from ICU to ward use the values on arrival to medicine unit.
  • Why would this be an exceptional instruction for STB? What is different about the situation there that would lead to different instructions?
Ttenbergen 11:12, 2021 April 1 (CDT)
    • This has always been collected at STB this way. (Pam)
      • That doesn't mean it should stay that way since we used to collect all of this only upon arrival. So let's discuss at Task what this should be. The difference is probably really minor, but if we have exceptions it should be clear why. Ttenbergen 13:57, 2021 April 1 (CDT)
  • SMW


  • Cargo


  • Categories
  • For direct transfers to Medicine via the ER use the first value taken and recorded on the triage record.
  • Direct transfers that bypass the ER take the value on arrival to your unit.

Timing of ALERT vs APACHE

Selection and timing of APACHE components and ALERT Scale timing of assessment use similar but different criteria. They can't be unified because one uses values based on being closest to acceptance, and the other based on being worst.

Related articles

Related articles: