Query check transfer ready tmp for each Boarding Loc

From CCMDB Wiki
Revision as of 15:46, 2021 February 3 by Ttenbergen (talk | contribs)
Jump to navigation Jump to search
Data Integrity Checks
Summary: There should be a Transfer Ready DtTm tmp entry for each Boarding Loc entry of a profile
Related: Transfer Ready DtTm tmp entry, Boarding Loc
Firmness: hard
Timing: complete
App: CCMDB.accdb
Coding: query check_transfer_ready_tmp_for_each_Boarding_Loc
Uses L Problem table: not relevant for this app
Status: needs review
Implementation Date:
Backlogged: true
  • Cargo


  • SMW


  • Categories: 
  • form:

The count of non-ER Boarding Loc should be the same as the count of Transfer Ready DtTm tmp entry.


if we can't figure out more, at least each profile has to have one Transfer Ready DtTm tmp entry...

  • added: no added date
  • action: no action date
  • Cargo


  • Categories

nr of entries

AJTT

  • I implemented this query and tested it on Steph's data, and none of the profiles have more than one Transfer Ready DtTm tmp entry. From how I read the article, there should be one per Boarding Loc - is that not how collectors are understanding this? Ttenbergen 18:58, 2021 January 28 (CST)
    • was this not addressed/answered in Julie's email of January 29?
    • This was discussed at task and as an example in medicine program the decision made was to consider all medicine collection units as having equal status, so transfers between medicine units are considered lateral moves; so there is usually only one transfer ready date/time entry per profile not per boarding location.
      • I remember the discussion that different med units now being all considered one level of care, but not that we will not re-evaluate for what would previously have been a different service. Pts who stay in hospital a long time may become transfer ready (and then leave that status) repeatedly. Before patient follow we would have reconsidered this status at service (and therefore laptop) change. If we no longer do this, we will artificially inflate the transfer ready delay. For example, before a pt might be ready to go home, be on a ward for 2 weeks in that state, then have a stroke and get moved to a higher ward. Pt is no longer ready to go home for 2 weeks, and eventually becomes transfer ready again. If we don't re-evaluate at that service change the whole time will be listed as transfer ready.
      • The following is copied from the Transfer Ready DtTm tmp entry article:

What if the pt ends up transferred to a higher level of care[edit]

It might seem that a patient who was transfer ready but then moves to a higher level of care should be excluded, since they did not actually get transferred to a lower level of care. However, when the patient was deemed transfer ready, additional time in the ward was "wasted time" - if we could have sent them elsewhere we would have. If the patient later crashes, that doesn't make it not-wasted time - they could have crashed anywhere. So the interpretation that a pt moving to a higher level of care after transfer ready is not wasted time is not right. We discussed this repeatedly at task and steering meetings. The only way this makes sense is if it is done by intent. '

  • SMW


  • Cargo


  • Categories

ER entries

AJTT

  • For medicine patients accepted and cared for in ER (one boarding location) then transferred to a medical unit, there isn't a transfer ready date/time because the patient was not ready for a lower level hierarchy of care but made a lateral move. Same concept applies for medicine unit to medicine unit moves. This is specific to patient moves from ER to medicine units.
    • That is not necessarily true. They might want to send a pt home but can't because pt now needs home care, but once home care is in place they can discharge from ER. Ttenbergen 10:55, 2021 February 1 (CST)
  • SMW


  • Cargo


  • Categories

Log

  • 2021-01-28 - defined

Related articles

Related articles: