Query check ApARF CRF

Revision as of 14:07, 29 October 2018 by Agarland (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 (end-stage kidney disease, ESRD), Stage 5
Firmness: hard check
Timing: always
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

  • ARF (APACHE)
  • If a person has pre-existing Chronic kidney disease (end-stage kidney disease, ESRD), Stage 5 then they cannot subsequently have any of the various Acute Renal Failure/AKI diagnoses UNLESS they got a renal transplant in between --- so the ESRD is before the TP and the AKI is in the new/transplanted kidney.
  • Thus, even though it is possible for an AKI to become fixed/permanent and become any level (1-5) of CRF -- this usually takes time (weeks to months) and for simplicity in coding, except for the case above where a renal TP occurred, the rule is that no single record should have both Chronic kidney disease (end-stage kidney disease, ESRD), Stage 5 and an ARF/AKI code.
    • This really is only an issue for patients with very long hospital stays, and we've decided we can live with this small, uncommon inconsistency.

See also

Log

Related Articles

Related articles: