Query check ApARF CRF: Difference between revisions
Jump to navigation
Jump to search
(→ICD10) |
Ttenbergen (talk | contribs) mNo edit summary |
||
Line 5: | Line 5: | ||
|DIC_coding=query ''Check_ApARF_CRF '' | |DIC_coding=query ''Check_ApARF_CRF '' | ||
|DIC_implementation_date=date change was rolled out / first applied | |DIC_implementation_date=date change was rolled out / first applied | ||
|DIC_status= | |DIC_status=ready to implement | ||
|DIC_app=CCMDB.mdb | |DIC_app=CCMDB.mdb | ||
}} | }} |
Revision as of 23:29, 2018 November 20
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: | ready to implement |
Implementation Date: | date change was rolled out / first applied |
Backlogged: | true |
ICD10
- 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.
- So we will use the rule that no single database record can include both Chronic kidney disease (end-stage kidney disease, ESRD), Stage 5 and an ARF/AKI code unless a kidney transplant occurred and the ARF/AKI is for the 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
- updated as of CCMDB.mdb Change Log 2011#ver 2011-12-09 Ttenbergen 13:27, 11 December 2011 (CST)
- implemented CCMDB.mdb Change Log 2009#v1.90. Ttenbergen 15:50, 29 September 2009 (CDT)