ACCU borrow: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
 
(27 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Project
{{Project
| Project = ACCU borrow
|ProjectActive=legacy
| ProjectActive = active
|ProjectProgram=CC
| ProjectProgram = CC
|ProjectRequestor=unknown
| ProjectRequestor = unknown
|ProjectCollectionStartDate=2016-07-07
}}  
|ProjectCollectionStopDate=2018-07-19
|Project=ACCU borrow
}}


ACCU Borrow is used to track duration that a [[STB ACCU]] patient spends in a [[STB CICU]], or [[STB MICU]] bed. This is a special case of [[Bed borrow]].
{{LegacyContent
|explanation= rolled up in successor
|successor=[[Boarding Loc]]
|content=


== Data Collection Instructions ==
Deleted old instructions so they don't pollute linking and searches. See history if needed. This is now collected as part of [[Project Borrow arrive]].  
For any STB_ACCU patient who occupies an STB MICU or CICU bed while under Acute Care Cardiology Service (ACCU) at any time, enter all moves between borrowed beds.
}}
*Discussed this process with Julie first week of August, 2016.  Just to clarify:  When an A_CCU patient is in MICU or CICU from the start, the date and time in the borrow tmp field will be the same as the admit date and time to that unit.  If the patient is later discharged to the ward, no other action is needed because it will be understood that the pt remained in the borrowed location the entire time.  If, however, the pt is transferred to the A_CCU location, then, another entry must be made in the borrow tmp section to indicate the date and time for this move.  For example,  the first entry will have A_CCU borrow then "MICU" with the date and time.  The second entry for A_CCU borrow will be A_CCU and then the date and time when moved there.  A patient could also start out in A_CCU and then move to MICU or CICU so then the entries would be made to reflect these moves. --[[User:LKolesar|LKolesar]] 11:47, 2016 August 11 (CDT)
 
*Use tmp fields:
** Project: '''ACCU borrow'''
** Item: '''CICU''' or '''MICU''' or '''ACCU'''
** start_dt: '''date on unit'''
** start_tm: '''time on unit'''
 
*Dispo Tab
**[[Service/Location field]] enter: STB_ACCU
***See: [[STB Cardiac Care patients]]
 
If physician service changes from ACCU to [[STB MICU]] or [[STB CICU]] while still in MICU or CICU, '''create a new profile'''.
 
== Different Scenario of ACCU Borrow ==
* The whole stay has been borrowed bed in '''MICU''' or '''CICU'''.
* Only partial stay has been borrowed bed in '''MICU''' or '''CICU'''.
** Usually the order of stay is '''MICU''' or '''CICU''' first and then move to '''ACCU'''.
** Rare case that '''ACCU''' is first and then borrowing bed in  '''MICU''' or '''CICU''' at the end of stay.
** Rare case that '''ACCU''' is first and then borrowing bed in  '''MICU''' or '''CICU''' And then back to  '''ACCU'''.
** Rare case that ACCU borrowed beds are in both '''MICU''' and '''CICU''' in consecutive orders.
 
== Start/End Dates ==
*Start: July 7, 2016
*End: there is no planned end date
 
== Data Use ==
 
=={{CCMDB Data Integrity Checks|needs review}}==
SEE: [[Requested CCMDB changes for the next version]].
 
{{Discussion}}
needs review from ''Tina'' and ''Julie''.
* query ''s_tmp_CCU_Service_shouldntve'' - no pt not STB_MICU can have any
** this query should be replaced by this:
*** Single record D_ID should have Item equal to 'MICU' or 'CICU' and should not have an item='ACCU'
*** if an item is 'ACCU', there should be another entry of same D_ID having an item of either 'MICU' or 'CICU')
**** I need to understand more about this before I can implement... Ttenbergen 21:57, 2017 July 29 (CDT)
***** The case for partial stay in ACCU and partial stay in 'MICU' or 'CICU' should have another paired item in addition to 'ACCU'. --[[User:JMojica|JMojica]] 15:21, 2017 November 10 (CST)
{{discussion}}
* query ''s_tmp_CCU_Service_twins'' - can't have two entries that are the same (ie same service and time)
**Need to change the query name. [[User:JMojica|JMojica]] 12:14, 2017 March 16 (CDT)
*** why is that? Ttenbergen 21:57, 2017 July 29 (CDT)
*** this is just a query for duplicate entries. if too complicated, I can delete the duplicate in SAS --[[User:JMojica|JMojica]] 15:21, 2017 November 10 (CST)
{{discussion}}
* added code to check that same service in consecutive sequence is not allowed
** This is OK. [[User:JMojica|JMojica]] 12:14, 2017 March 16 (CDT)
*** "next record" comparisons are not supported natively by Access. Is this check vital? It's possible but would be somewhat messy to implement. Ttenbergen 21:57, 2017 July 29 (CDT)
*** we can exclude this if messy. --[[User:JMojica|JMojica]] 15:21, 2017 November 10 (CST)
{{discussion}}
* add a query that the date_var and time_var should not be outside the Accept DtTm/Arrived DtTm and Dispo DtTm.--[[User:JMojica|JMojica]] 15:21, 2017 November 10 (CST)
 
== SAS Program ==
* To be filled up by Julie
 
 
 
 
 
[[Category:St Boniface Hospital Office (Critical Care)]]
[[Category:Site Specific Collection Guide]]
[[Category:L TmpV2 Data]]
[[Category:L TmpV2 Data]]
[[Category:All Projects ICU only]]
[[Category:Legacy Overflow]]
[[Category:Overflow]]

Latest revision as of 13:44, 2020 July 24

Projects
Active?: legacy
Program: CC
Requestor: unknown
Collection start: 2016-07-07
Collection end: 2018-07-19

Legacy Content

This page contains Legacy Content.

Click Expand to show legacy content.

Deleted old instructions so they don't pollute linking and searches. See history if needed. This is now collected as part of Project Borrow arrive.