Query check transfer ready tmp for each Boarding Loc: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
 
(15 intermediate revisions by 4 users not shown)
Line 6: Line 6:
| DIC_app = CCMDB.accdb
| DIC_app = CCMDB.accdb
| DIC_coding = query ''check_transfer_ready_tmp_for_each_Boarding_Loc''
| DIC_coding = query ''check_transfer_ready_tmp_for_each_Boarding_Loc''
| DIC_status = needs review
| DIC_status = retired
| DIC_implementation_date =  
| DIC_implementation_date = 2021-02-04
}}
}}


The count of non-ER [[Boarding Loc]] should be the same as the count of [[Transfer Ready DtTm tmp entry]].
Replaced by more comprehensive check [[query s_tmp_check_combined_Boarding_Loc_and_TransferReadyDtTm ]]  
 
== nr of entries ==
{{Discuss |
* 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? [[User:Ttenbergen|Ttenbergen]] 18:58, 2021 January 28 (CST)
** 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.
}}
 
== ER entries ==
{{Discuss |
* 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. (Pam)
** 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. [[User:Ttenbergen|Ttenbergen]] 10:55, 2021 February 1 (CST)
}}


== Log ==
== Log ==
* 2021-03-31 - retired, replaced by [[query s_tmp_check_combined_Boarding_Loc_and_TransferReadyDtTm ]]
* 2021-02-04 - implemented after clarification of [[Transfer Ready DtTm tmp entry]]
* 2021-01-28 - defined  
* 2021-01-28 - defined  


Latest revision as of 11:13, 2021 March 31

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: retired
Implementation Date: 2021-02-04
Backlogged: true
  • Cargo


  • SMW


  • Categories: 
  • form:

Replaced by more comprehensive check query s_tmp_check_combined_Boarding_Loc_and_TransferReadyDtTm

Log

Related articles

Related articles:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Query_check_transfer_ready_tmp_for_each_Boarding_Loc&oldid=149673"