Query check CCI Date: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Created page with "{{Data Integrity Check | DIC_summary = Px Date must be sensible when compared to Arrive_DtTm and Dispo_DtTm | DIC_related_concepts = Px Date, Arrive_DtTm,..."
 
mNo edit summary
Line 5: Line 5:
| DIC_app = CCMDB.mdb
| DIC_app = CCMDB.mdb
| DIC_coding =   
| DIC_coding =   
| DIC_status = needs review, ready to implement, implemented, not feasible
| DIC_status = needs review
| DIC_implementation_date =  
| DIC_implementation_date =  
}}
}}
'''If this check changes, consider whether [[Dx Chronological]] should be changed the same way.'''
* If exists, [[Dx_Date]] must be between [[Accept_DtTm]] {{discussion}} or is it [[Arrive_DtTm]]? and [[Dispo_DtTm]]
* mandatory for procedures with [[Px Type]] '''acquired'''
* not allowed for procedures with [[Px Type]] '''admit'''.




[[Px Type#CCMDB Data Integrity Checks]]
Same as for [[Dx Date]]


[[Category: CCI]]
[[Category: CCI]]

Revision as of 12:52, 23 August 2018

Data Integrity Checks
Summary: Px Date must be sensible when compared to Arrive_DtTm and Dispo_DtTm
Related: [[Px Date, Arrive_DtTm, Dispo_DtTm]]
Firmness: hard check
Timing: always
App: CCMDB.mdb
Coding:
Uses L Problem table: not relevant for this app
Status: needs review
Implementation Date:
Backlogged: true
  • Cargo


  • SMW
"CCMDB.mdb" is not in the list (SAP, not entered, Centralized data front end.accdb, DSM Labs Consistency check.accdb, CCMDB.accdb, TISS28.accdb) of allowed values for the "DICApp" property. Property "DICRelatedConcepts" (as page type) with input value "Px Date]], Arrive_DtTm, [[Dispo_DtTm" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  • Categories:  
  • form:

If this check changes, consider whether Dx Chronological should be changed the same way.


  • mandatory for procedures with Px Type acquired
  • not allowed for procedures with Px Type admit.