Query check transfer ready tmp for each Boarding Loc: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
(Pam was right, the instructions had been clarified after discussion with Julie and Allan, and the query had not been updated yet.)
mNo edit summary
Line 6: Line 6:
| DIC_app = CCMDB.accdb
| DIC_app = CCMDB.accdb
| DIC_coding = query ''check_transfer_ready_tmp_for_each_Boarding_Loc''
| DIC_coding = query ''check_transfer_ready_tmp_for_each_Boarding_Loc''
| DIC_status = implemented
| DIC_status = needs review
| DIC_implementation_date = 2021-02-04
| DIC_implementation_date = 2021-02-04
}}
}}


The count of [[Boarding Loc]] should be the same as the count of [[Transfer Ready DtTm tmp entry]].
The count of [[Boarding Loc]] should be the same as the count of [[Transfer Ready DtTm tmp entry]]. This means there could be several undated transfer ready entries with check boxes/comments but no dates/times.


A direct one-on-one match is not possible since there is nothing to identify the undated entries to a specific [[Boarding Loc]], so an identical count will be used as an approximation.  
A direct one-on-one match is not possible since there is nothing to identify the undated entries to a specific [[Boarding Loc]], so an identical count will be used as an approximation.  


{{Discuss|  
{{TT | Once [[query check_transfer_ready_tmp_one_per_Boarding_Loc]] is implemented, this one can go away since it checks a subset of that. }}
* Does the above statement mean that for patients with several moves between medicine units (including ER) there could be several undated transfer ready entries with check boxes/comments but no dates/times? This seems prone to inadvertent entry errors? Could this be clarified? Thank you (Pam)
** Yes, that's what it means. It's not ideal and we are discussing alternatives, but for now that's it. [[User:Ttenbergen|Ttenbergen]] 15:23, 2021 February 9 (CST)}}


== Log ==
== Log ==

Revision as of 10:50, 2021 March 31

Data Integrity Checks
Summary: There should be a Transfer Ready DtTm tmp entry for each Boarding Loc entry of a profile
Related: Transfer Ready DtTm tmp entry, Boarding Loc
Firmness: hard
Timing: complete
App: CCMDB.accdb
Coding: query check_transfer_ready_tmp_for_each_Boarding_Loc
Uses L Problem table: not relevant for this app
Status: needs review
Implementation Date: 2021-02-04
Backlogged: true
  • Cargo


  • SMW


  • Categories: 
  • form:

The count of Boarding Loc should be the same as the count of Transfer Ready DtTm tmp entry. This means there could be several undated transfer ready entries with check boxes/comments but no dates/times.

A direct one-on-one match is not possible since there is nothing to identify the undated entries to a specific Boarding Loc, so an identical count will be used as an approximation.


Once query check_transfer_ready_tmp_one_per_Boarding_Loc is implemented, this one can go away since it checks a subset of that.

  • added: no added date
  • action: no action date
  • Cargo


  • Categories

Log

Related articles

Related articles: