Query check ACP Status Collection

From CCMDB Wiki
Revision as of 22:24, 5 March 2025 by Ttenbergen (talk | contribs) (Created page with "{{Data Integrity Check | DIC_summary = every LAU Collection Project must have an entry, and the date must make sense | DIC_related_concepts = Admit date and time; Dispo_DtTm; | DIC_firmness = hard check | DIC_timing = complete | DIC_app = CCMDB.accdb | DIC_coding = query ''check_ACP_Status_Collection_for_LAU'' | DIC_status = | DIC_implementation_date = 2025-03 }} This check is or a temporary entry collected for the LAU Collection Project. Check: * there is...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search
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
  • Cargo


  • SMW


  • Categories:  
  • form:

This check is or a temporary entry collected for the LAU Collection Project.

Check:

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.

  • SMW


  • Cargo


  • Categories

Log

  • 2025-03-05 - cross check defined

Related Articles

Related articles: