Function Dispo Chronological(): Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 26: | Line 26: | ||
[[Category:2016 Time and Place changes]] | [[Category:2016 Time and Place changes]] | ||
[[Category: | [[Category:Registry checks]] | ||
Revision as of 11:38, 26 October 2018
| Data Integrity Checks | |
| Summary: | Checks that the registry times are in a sensible chronological order. |
| Related: | [[Arrive DtTm, Accept DtTm, Transfer Ready DtTm, Dispo DtTm ]] |
| Firmness: | hard check |
| Timing: | always |
| App: | CCMDB.mdb |
| Coding: | Function Dispo Chronological() |
| Uses L Problem table: | not relevant for this app |
| Status: | implemented |
| Implementation Date: | 2016-05-25 |
| Backlogged: | true |
The check will generate an error if:
- Arrive DtTm has to be before or equal to Accept DtTm
- Arrive DtTm has to be before or equal Transfer Ready DtTm
- Arrive DtTm has to be before Dispo DtTm
- Transfer Ready DtTm has to be before Dispo DtTm
- Dispo DtTm has to be before Now() / today
No checks on Visit Admit DtTm field since taken direct from EPR, so it is what it is.
Transfer time rule
Template:Discussion Will want to reconcile Transfer time rule