Query check ACP Status Collection for LAU: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) No edit summary |
Ttenbergen (talk | contribs) No edit summary |
||
| Line 27: | Line 27: | ||
{{Related Articles}} | {{Related Articles}} | ||
[[Category: LAU Collection Project]] | [[Category: LAU Collection Project]] | ||
[[Category: ACP]] | [[Category: ACP]] | ||
Revision as of 23:39, 5 March 2025
| Data Integrity Checks | |
| Summary: | every LAU Collection Project must have an entry, and the date must make sense |
| Related: | Admit date and time, Dispo_DtTm |
| Firmness: | hard check |
| Timing: | complete |
| App: | CCMDB.accdb |
| Coding: | query check_ACP_Status_Collection_for_LAU |
| Uses L Problem table: | not relevant for this app |
| Status: | |
| Implementation Date: | 2025-03 |
| Backlogged: | true |
This check is or a temporary entry collected for the LAU Collection Project.
Check:
- there is at least one entry for every LAU Collection Project record
- "item" is not "not entered"
- (L_TmpV2 table date_var + time_var) must be before Dispo DtTm field
- (L TmpV2 table date_var + time_var) must be after Admit date and time
|
Is that last one reasonable? I guess it depends on how we want to collect a status that was set before admission to this unit. See question in ACP_Status_Collection_for_LAU#Data_Entry_Instructions. |
Log
- 2025-03-05 - cross check defined
Related Articles
| Related articles: |