Function Dispo Chronological(): Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) |
||
| Line 23: | Line 23: | ||
** First, Trish, do you think I am right about that? | ** First, Trish, do you think I am right about that? | ||
** Second, if so, do we need to adjust this? How does this work with Julie’s reports now, and how would it work if changed. | ** Second, if so, do we need to adjust this? How does this work with Julie’s reports now, and how would it work if changed. | ||
*** '''Yes, Tr DtTm can be between accept and arrive.''' | *** '''Discussed at Task 2019-01-24: As I left we said: Yes, Tr DtTm can be between accept and arrive. Need to update both the cross check and the rules. Will need to review minutes to see what came of it.''' | ||
}} | }} | ||
Revision as of 12:58, 24 January 2019
| 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: | needs review |
| 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 vs (accept vs arrive)
|
|
Transfer time rule
|
|
Will want to reconcile Transfer time rule |