Check function previous NE Location: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
No edit summary
mNo edit summary
Line 2: Line 2:
|DIC_summary=[[Previous Location field]] can't be same as [[Service/Location field]]
|DIC_summary=[[Previous Location field]] can't be same as [[Service/Location field]]
|DIC_related_concepts=Service/Location field; Previous Location field
|DIC_related_concepts=Service/Location field; Previous Location field
|DIC_firmness=soft check
|DIC_firmness=hard check
|DIC_timing=complete
|DIC_timing=complete
|DIC_coding=function previous_NE_Location()
|DIC_coding=function previous_NE_Location()
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.
* 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


== Related articles ==  
== Related articles ==  

Revision as of 14:44, 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
  • Cargo


  • SMW


  • Categories:  
  • form:

.

Log

Related articles

Related articles: