Renal Coding Considerations (old)
There are a few restrictions about which renal diagnoses can be coded together. These checks are currently done partly by Pagasa (!_Automated_Data_Integrity_Checks#CRF_vs_ARF) and have been partly implemented in CCMDB.mdb.
CRF vs transplant
Wonder if this should really go here, but needed it out of "!automated checks" `Just a comment about CRF 351, When pt receiving a Renal Transplant 361,who then has complications and requires dialysis, they can have 350, 352 and 364, which is related to their new donor kidney.--FLindell 08:36, 25 November 2008 (CST)
Template:Data Integrity Checks
These rules are currently checked at the main office and result in calls for clarification from Pagasa if broken. Some of them have been added to CCMDB.mdb, more are to follow.
Template:CCMDB Data Integrity Checks: Competing Diagnoses
see Check Renal IncompatibleDxs
- If no Renal Transplant (80504 or 80505) in either Dxs or Comos then
- If comorbid CRF (351-00) exists then the following must not appear in Admit/Acquired codes
- ARI (364-00)
- ATN (352-00)
- ARF (Diagnosis) (350 **)
- If comorbid CRF (351-00) exists then the following must not appear in Admit/Acquired codes
Diagnoses, Comos vs. Tasks, locations
Apache vs. CRF comorbid
- see Check ApARF CRF.
Apache vs. ARF Dx
cross-checks impossible due to different definitions, see ARF (Diagnosis) and ARF (APACHE)
Template:Data Integrity Checks that can not be checked before sending
Related Articles
see Category:Renal Problem for other renal problems