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 |
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.
- ICU (MICU, SICU, CICU, CCU, ACCU) - 7 days
- IICU - 14 days
- HOBS Wards - ?? days
- Regular Wards - ?? days
|
|
Use of the Notes field to escape errors
- 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.
|
_after
|
|
After implementation
Update the cross check info in Transfer Delay, Transfer Ready DtTm field and Dispo DtTm field from "needs discussion".