Check function location NE dispo: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) m →Log |
Ttenbergen (talk | contribs) mNo edit summary |
||
Line 10: | Line 10: | ||
|DIC_backlogged=No | |DIC_backlogged=No | ||
}} | }} | ||
== Log == | == Log == | ||
* 2021-08-25 - changed to hard check again since change in [[Processes around changing a PatientFollow assignment]] means this can no longer be correct | * 2021-08-25 - changed to hard check again since change in [[Processes around changing a PatientFollow assignment]] means this can no longer be correct | ||
* 2020-12-23 - changed to soft check since this can now be correct in the context of [[Processes around changing a PatientFollow assignment]] | * 2020-12-23 - changed to soft check since this can now be correct in the context of [[Processes around changing a PatientFollow assignment]] |
Latest revision as of 14:53, 2022 June 22
Data Integrity Checks | |
Summary: | Service/Location field can't be same as Dispo field |
Related: | Service/Location field, Dispo field |
Firmness: | hard check |
Timing: | complete |
App: | CCMDB.accdb |
Coding: | location_NE_dispo() which calls query Check_Location_NE_Dispo |
Uses L Problem table: | not relevant for this app |
Status: | implemented |
Implementation Date: | 2016-12-31 |
Backlogged: | No |
Log
- 2021-08-25 - changed to hard check again since change in Processes around changing a PatientFollow assignment means this can no longer be correct
- 2020-12-23 - changed to soft check since this can now be correct in the context of Processes around changing a PatientFollow assignment
- 2019-01-07 - updated so they will work with the workload sharing locations
Related articles
Related articles: |