Check function previous NE Location: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) m →Log |
||
| Line 12: | Line 12: | ||
. | . | ||
== 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]] | ||
* 2019-01-07 - updated so they will work with the workload sharing locations | * 2019-01-07 - updated so they will work with the workload sharing locations | ||
Latest revision as of 14:47, 25 August 2021
| Data Integrity Checks | |
| Summary: | Previous Location field can't be same as Service/Location field |
| Related: | Service/Location field, Previous Location field |
| Firmness: | hard check |
| Timing: | complete |
| App: | CCMDB.accdb |
| Coding: | function previous_NE_Location() |
| 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: |