Transfer Ready DtTm tmp entry: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
m →‎data checks: moved the note to the cross check page.
Line 33: Line 33:
Then either check the box on the new line when you finally complete the patient, or lather rinse repeat.
Then either check the box on the new line when you finally complete the patient, or lather rinse repeat.


== data checks ==
{{DT | We will want a replacement for [[function Transfer_Ready_DtTm_vs_status]]. }}
{{Data Integrity Check List}}
{{Data Integrity Check List}}



Revision as of 22:36, 2020 October 15

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 to GRA Med, HSC Med, STB Med Service Location 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.

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: 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.

Data Integrity Checks (automatic list)

 AppStatus
Query check ICD10 needs awaiting if TR Dt and Dispo Dt on diff daysCCMDB.accdbdeclined
Query check TISS each dayCCMDB.accdbdeclined
Query check ICD10 awaiting has Transfer Ready DtTmCCMDB.accdbimplemented
Query check transfer DtTm during admissionCCMDB.accdbimplemented
Query check has transfer ready date or checkboxCCMDB.accdbimplemented
Query s tmp check combined Boarding Loc and TransferReadyDtTmCCMDB.accdbimplemented
Query s tmp check Boarding Loc and TransferReadyDtTm pairsCCMDB.accdbimplemented
Query check Transfer DtTm after paired BL and before later BLCCMDB.accdbimplemented
Query Check BL TR combiner nullCCMDB.accdbimplemented
Query check tmp 2 BL TR S same tmCCMDB.accdbimplemented
Query check long transfer delayCCMDB.accdbneeds review
Function Validate Transfer Ready DtTmCCMDB.accdbretired
Function Transfer Ready DtTm vs statusCCMDB.accdbretired
Query check transfer ready tmp for each Boarding LocCCMDB.accdbretired
Query check tmp Transfer Ready not before Boarding LocCCMDB.accdbretired
Query s tmp check combined BL and TRDtTm nonsequentialCCMDB.accdbretired

Data Use

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

SAS Program

Background

Related articles

Related articles: