Query check LAU collection readmission data: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) No edit summary |
Ttenbergen (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
{{Data Integrity Check | {{Data Integrity Check | ||
| DIC_summary = dates must make sense | | DIC_summary = dates must make sense | ||
| DIC_related_concepts = Admit date and time; Dispo_DtTm; | | DIC_related_concepts = Admit date and time; Dispo_DtTm; LAU collection readmission data | ||
| DIC_firmness = hard check | | DIC_firmness = hard check | ||
| DIC_timing = complete | | DIC_timing = complete | ||
Revision as of 22:43, 5 March 2025
| Data Integrity Checks | |
| Summary: | dates must make sense |
| Related: | Admit date and time, Dispo_DtTm, LAU collection readmission data |
| Firmness: | hard check |
| Timing: | complete |
| App: | CCMDB.accdb |
| Coding: | query LAU_collection_readmission_data |
| 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:
- for item = "has previous", (L_TmpV2 table date_var + time_var) must be before the Admit date and time
- for item = "has later", (L_TmpV2 table date_var + time_var) must be after Dispo DtTm field
- don't need to limit this to only LAU collection records since no other records should have this; if a record has the entry it should meet these conditions.
Log
- 2025-03-05 - cross check defined
Related Articles
| Related articles: |