Query check LAU collection readmission data: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) No edit summary |
Ttenbergen (talk | contribs) |
||
| Line 20: | Line 20: | ||
== Log == | == Log == | ||
* 2025-03-09 - updated check to account for "no readmission" items | |||
* 2025-03-06 - implemented | * 2025-03-06 - implemented | ||
* 2025-03-05 - cross check defined | * 2025-03-05 - cross check defined | ||
Revision as of 11:42, 9 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: | always |
| App: | CCMDB.accdb |
| Coding: | query check_LAU_collection_readmission_data |
| Uses L Problem table: | not relevant for this app |
| Status: | implemented |
| Implementation Date: | implemented |
| Backlogged: | true |
This check is or a temporary entry collected for the LAU Collection Project.
Check:
- (L_TmpV2 table date_var, time_var) must not be null
- 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.
- check these always, if a record was added it should be complete
Log
- 2025-03-09 - updated check to account for "no readmission" items
- 2025-03-06 - implemented
- 2025-03-05 - cross check defined
Related Articles
| Related articles: |