Query check long transfer delay

Data Integrity Checks
Summary:	Is the Transfer Delay (Critical Care) or Transfer Delay (Medicine) unreasonably long?
Related:	Transfer Delay (Critical Care), Transfer Delay (Medicine), Transfer Ready DtTm tmp entry, Dispo DtTm field
Firmness:	soft check
Timing:	always
App:	CCMDB.accdb
Coding:	Query check long transfer delay
Uses L Problem table:	not relevant for this app
Status:	needs review
Implementation Date:	not entered
Backlogged:	No

• Cargo

• SMW

• Categories:  

• form:

This is a check to ensure that patients with a long Transfer Delay (Critical Care) or Transfer Delay (Medicine) are not errors.

Any patient with a transfer delay longer than the following limits will launch an error when the dispo tab checkbox is checked. Data collectors need to confirm if not an error and write in the notes box that the transfer ready date_time is correct. The Statistician will look at the notes when doing report about avoidable days.

1. ICU (MICU, SICU, CICU, CCU, ACCU) - 7 days
2. IICU - 14 days
3. HOBS Wards - ?? days
4. Regular Wards - ?? days

If we actually want a cross check like this it needs to be based not on NTU/CTU. We could either base it on specific units or on Level of care hierarchy, ie. add another column to s_level_of_care table. Would that work for you? Ttenbergen 23:08, 2020 October 15 (CDT) must be changed to high obs and regular wards. --JMojica 09:41, 2022 June 7 (CDT)

• SMW

• Cargo

• Categories

At the meeting about cross checks (a long time ago) it was decided to change the cut-off to SD*3; if we want to proceed with this check, I will need values for that. Ttenbergen 23:08, 2020 October 15 (CDT) the MED above has to changed. I will do a calculation of recent data based on the new process using Mean+3SD. --JMojica 15:16, 2022 February 16 (CST) I am waiting for your Created Variables Common 2021 table to be done and from that table, the calculation of mean +3 SD will be derived. --JMojica 09:41, 2022 June 7 (CDT)

• SMW

• Cargo

• Categories

Use of the Notes field to escape errors

Requiring notes to have content is really a very soft error check... do we need to consider something better? maybe just a pop-up message to confirm if correct is enough? I will assume the date time entry has been confirmed to be correct. --JMojica 15:16, 2022 February 16 (CST) That would be an even softer error check, so might as well keep the notes field one and avoid ask-backs. Ttenbergen 08:24, 2022 June 9 (CDT)

• SMW

• Cargo

• Categories

• There was a suggestion to omit the error if the notes box has a comment. That makes me think: we use this method for other checks, but I don't actually know how powerful it is, since most collectors use notes for all sorts of things, and some will leave the content when they are ready to send. If we are serious about this we might want to require them to put an entry into the tmp field instead. Is it worth adding one more entry to that? Guess it depends partly on how common the scenario is. Thoughts? Ttenbergen 16:44, 2018 June 7 (CDT)

After implementation

Update the cross check info in Transfer Delay, Transfer Ready DtTm field and Dispo DtTm field from "needs discussion".