Query check CCI Component duplicates: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) m was implemented, just had not changed tag |
||
| Line 6: | Line 6: | ||
|DIC_coding=query ''check_CCI_Component_duplicates'' | |DIC_coding=query ''check_CCI_Component_duplicates'' | ||
|DIC_implementation_date=2018-10-14 | |DIC_implementation_date=2018-10-14 | ||
|DIC_status= | |DIC_status=implemented | ||
|DIC_LProblem=No | |DIC_LProblem=No | ||
|DIC_app=CCMDB.mdb | |DIC_app=CCMDB.mdb | ||
Revision as of 10:03, 24 December 2018
| Data Integrity Checks | |
| Summary: | No duplication of CCI Component Px_Type, Px_Date |
| Related: | CCI Component, Px Type, Dx_Priority, No Dx Entered |
| Firmness: | hard check |
| Timing: | complete |
| App: | CCMDB.mdb |
| Coding: | query check_CCI_Component_duplicates |
| Uses L Problem table: | not relevant for this app |
| Status: | implemented |
| Implementation Date: | 2018-10-14 |
| Backlogged: | true |
- Px Type = Acquired – no same Px_Date and CCI code
- Px Type = Admit – no same CCI code (it should not have a Px_Date at all, dealt with by Query check CCI Date).
We are not currently planning to check for CCI Collection Modes being used correctly but this may change.
Related articles
| Related articles: |