Query check long transfer delay

From CCMDB Wiki
Revision as of 12:14, 2018 September 25 by Ttenbergen (talk | contribs) (Text replacement - "DIC_timing = complete always" to "DIC_timing =")
Jump to navigation Jump to search
Data Integrity Checks
Summary: Is the Transfer Delay unreasonably long?
Related: [[Transfer Delay, Transfer Ready DtTm, Dispo DtTm field]]
Firmness: soft check
Timing:
App: CCMDB.mdb
Coding: Query check long transfer delay
Uses L Problem table: not relevant for this app
Status: needs review
Implementation Date:
Backlogged: true
  • Cargo


  • SMW
"CCMDB.mdb" is not in the list (CCMDB.accdb, Centralized data front end.accdb, TISS28.accdb, SAP, DSM Labs Consistency check.accdb, not entered) of allowed values for the "DICApp" property. Property "DICRelatedConcepts" (as page type) with input value "Transfer Delay]], Transfer Ready DtTm, [[Dispo DtTm field" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  • Categories:  
  • form:

This is a check to ensure that patients with a long Transfer Delay 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. CTU Med Wards - 21 days
  4. NTU Med Wards - 42 days
  • 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?
  • 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".

Related Articles

Related articles: