Query check ApARF CRF

Revision as of 14:18, 26 October 2018 by Ttenbergen (talk | contribs)
Data Integrity Checks
Summary: ARF (APACHE) and CRF - Chronic Renal Failure can not be coded together for the same patient.
Related: [[ARF (APACHE)]], [[Chronic kidney disease (uremia, chronic renal insufficiency) Stage 1]], [[Chronic kidney disease (uremia, chronic renal insufficiency) Stage 2]], [[Chronic kidney disease (uremia, chronic renal insufficiency) Stage 3]], [[Chronic kidney disease (uremia, chronic renal insufficiency) Stage 4]], [[Chronic kidney disease (end-stage kidney disease, ESRD), Stage 5]]
Firmness: hard check (not allowed) or soft check (allowed, but give error; in CFE this means it has to go into the ... table, and cross checks have to consider that table)
Timing:
App: CCMDB.mdb
Coding: query Check_ApARF_CRF
Uses L Problem table: not relevant for this app
Status: needs review
Implementation Date: date change was rolled out / first applied
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. 
  • Categories:  
  • form:

ICD10

Template:ICD10 ARF (APACHE)

and any of

can not be coded together.

Template:Discussion Can any level of above be coded with ARF (APACHE), e.g. a low stage one that suddenly got much worse? Ttenbergen 15:30, 2017 December 28 (CST)

See also

Log

Related Articles

Related articles: