Transfer Ready DtTm tmp entry

Projects
Active?:	active
Program:	CC and Med
Requestor:	internal
Collection start:	2020-10-15
Collection end:

This isn't so much a project as a change to Transfer Ready DtTm collection to allow us to collect more than one Transfer Ready DtTm per patient-program-stay. See Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry for why we needed to change to this.

Transition to new way of entering this

Transfer Ready DtTms before 2020-10-15 should be entered using the old field, any Transfer Ready DtTms starting 2020-10-15 midnight should be entered into the new tmp entry.

For the date cutoff are we referring to admission date, transfer ready date, or discharge date? Surbanski 10:22, 2020 October 16 (CDT) The Transfer Ready DtTm

• SMW

• Cargo

• Categories

Data Collection Instructions

• Use tmp fields:
  • Project: Transfer Ready DtTm
  • Item: Transfer Ready DtTm
  • Transfer Ready Date: Date as defined in Transfer Ready DtTm, under column E.
  • Transfer Ready Time: Time as defined in Transfer Ready DtTm, under column M.
  • checkbox: to be checked only if a transfer ready date never became available
  • comment (under 'q'): only if TR date not available (ie if checkbox checked), enter either "not ready" or "not available" into the comment field.

A first entry is added automatically to each new patient entered on the laptop.

If a transfer date never becomes available, check the checkbox to say so. This is so we can be sure the entry wasn't just forgotten. Don't check this until the patients moves to a unit with a different level of care (either stays in your collection or not) and you are sure a date never became available.

The first time the patient becomes transfer ready, enter the date and time into this pre-entered record. Don't check the checkbox in this case, since the patient is transfer ready.

If, after this initial entry, the patient moves to a physical location (ie new entry in Boarding Loc that has a different level in the Level of care hierarchy, then:

• leave the original line as is
• enter a new line, either without a date (for now), or if a new transfer ready date from the new level of care is known by the time you enter this, enter the new date and time

Then either check the box on the new line when you finally complete the patient, or lather rinse repeat.

So do we need a transfer ready time for every physical move - for example, ER to D4, D4 to H4? Or only when a patient moves to a lower level of care. So when ER --> D4, no transfer ready time, but D4 --> WRS3, we would have a transfer ready time. no new entry for same level of care, but entry for higher or lower level of care. Why higher as well? Because once a patient actually moves to a higher level of care, the original determination that they were transfer ready almost certainly is no longer valid. The only exception might be the original ER entry - that is a high level of care location, but would we expect someone to become transfer ready there and then still move to the ward? Probably not. I'd say no entry for that part, but should see what Julie has to say. Ttenbergen 15:16, 2020 October 16 (CDT)

• SMW

• Cargo

• Categories

Moving this into a different topic because it's about how to interpret these, not how to enter them This is my dilemma with our definition, it is the intent which I cannot qualify thru the data. if I see an entry in transfer ready date but the physical transfer location is the same or higher level of care, I have to consider that transfer ready date to be valid. I rely that the entry is correct. I rather have the definition to be consistent with the level of care (except for Deaths) so I can quality check the transfer date entry and remove the intent as part of the definition. The goal is to measure bed wastage and when the patient moves to the same or higher level of care, that is not bed wastage to me. --JMojica 10:18, 2020 October 16 (CDT) 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. The only way this makes sense is if it is done by intent. Ttenbergen 15:16, 2020 October 16 (CDT)

• SMW

• Cargo

• Categories

Data Integrity Checks (automatic list)

	App	Status
Query check ICD10 needs awaiting if TR Dt and Dispo Dt on diff days	CCMDB.accdb	declined
Query check TISS each day	CCMDB.accdb	declined
Query check ICD10 awaiting has Transfer Ready DtTm	CCMDB.accdb	implemented
Query check transfer DtTm during admission	CCMDB.accdb	implemented
Query check has transfer ready date or checkbox	CCMDB.accdb	implemented
Query s tmp check combined Boarding Loc and TransferReadyDtTm	CCMDB.accdb	implemented
Query s tmp check Boarding Loc and TransferReadyDtTm pairs	CCMDB.accdb	implemented
Query check Transfer DtTm after paired BL and before later BL	CCMDB.accdb	implemented
Query Check BL TR combiner null	CCMDB.accdb	implemented
Query check tmp 2 BL TR S same tm	CCMDB.accdb	implemented
Query check long transfer delay	CCMDB.accdb	needs review
Function Validate Transfer Ready DtTm	CCMDB.accdb	retired
Function Transfer Ready DtTm vs status	CCMDB.accdb	retired
Query check transfer ready tmp for each Boarding Loc	CCMDB.accdb	retired
Query check tmp Transfer Ready not before Boarding Loc	CCMDB.accdb	retired
Query s tmp check combined BL and TRDtTm nonsequential	CCMDB.accdb	retired

Data Use

Critical care and Medicine programs want to know this to better understand patient flow and bed utilization.

SAS Program

Background

Related articles