Check function location NE dispo: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 2: | Line 2: | ||
|DIC_summary=[[Service/Location field]] can't be same as [[Dispo field]] | |DIC_summary=[[Service/Location field]] can't be same as [[Dispo field]] | ||
|DIC_related_concepts=Service/Location field; Dispo field | |DIC_related_concepts=Service/Location field; Dispo field | ||
|DIC_firmness= | |DIC_firmness=hard check | ||
|DIC_timing=complete | |DIC_timing=complete | ||
|DIC_coding=location_NE_dispo() | |DIC_coding=location_NE_dispo() | ||
| Line 10: | Line 10: | ||
|DIC_backlogged=No | |DIC_backlogged=No | ||
}} | }} | ||
. | |||
== Log == | == Log == | ||
2020-12-23 | * 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}} | |||
[[Category:Registry checks]] | [[Category:Registry checks]] | ||
Revision as of 15:51, 2021 August 25
| 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() |
| 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: |