Renal Coding Considerations (old): Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m (Text replacement - "Renal Coding Considerations for ICD10" to "ICD10 Guideline for Renal Coding")
 
(47 intermediate revisions by 4 users not shown)
Line 1: Line 1:
These checks are currently done partly by Pagasa ([[http://ltc.umanitoba.ca/wikis/ccmdb/index.php/!_Automated_Data_Integrity_Checks#CRF_vs_ARF]]) and are about to be implemented in [[CCMDB.mdb]].
{{LegacyContent
|explanation=These are so different in ICD10 that we made a new page: [[ICD10 Guideline for Renal Coding]]
|successor=[[ICD10 Guideline for Renal Coding]]
|content=


== Data Integrity Rules that can be checked before sending==
See also [[ICD10 Guideline for Renal Coding]]
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.


=== Competing Diagnoses ===
There are a few restrictions about which renal diagnoses can be coded together. These checks are currently done partly by Pagasa and have been partly implemented in [[CCMDB.accdb]].
If comorbid [[CRF - Chronic Renal Failure|CRF]] (351-00) exists then the following must '''not''' appear in Admit/Acquired codes
* [[ARI]]  (364-00)
* [[Acute Tubular Necrosis | ATN]]  (352-00)
* [[ARF (Diagnosis)]] (350 **)


==== Implementation ====
== CRF in pt with transplant failure ==
Implementing ARF vs CRF as per [[Check Renal IncompatableDxs]].  
Just a comment about '''[[CRF - Chronic Renal Failure]]''': when pt has [[Renal Transplant Problems]] and/or [[Renal Transplant|Renal Transplant - Removal of Transplant-Organ]] and requires dialysis, they can have acquired diagnoses of '''[[ARF (Diagnosis)]]''', '''[[Acute Tubular Necrosis (ATN)]]''' and/or [[ARI]], which is related to their new donor kidney.


===== Discussion =====
== [[:Category:Renal insufficiency (old)]] ==
{{discussion}}
*'''Comorbid'''
The check does not include [[ATN]] yet since the guideline for that diagnosis doesn't instruct not to code with [[CRF]], and the concept ATN does not seem to preclude CRF. Could someone explain why ATN can not coincide with CRF? [[User:Ttenbergen|Ttenbergen]] 11:08, 30 September 2009 (CDT)
**[[Renal insufficiency-mild (creatinine 160-240 mmol)]]
**[[Renal Insufficiency-moderate (Cr greater than 240)]]
*'''Admit or complication'''
**[[ARI]] there is a different range - creatinine rise of >250 mmol OR a rise of >100 mmol from baseline over 24 hrs. 
*'''No dialysis''' or
*'''N history of CRF'''
**if patient required acute dialysis, it is not due to renal insufficiency - please see [[ARF]]
**This is in the code book but not on the Wiki. (code books OLD so folks should not use).
 
== 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.accdb]], more are to follow.
 
=== CCMDB Data Integrity Checks: Competing Diagnoses ===
see [[query Check Renal IncompatibleDxs]]


=== Diagnoses, Comos vs. Tasks, locations ===
=== Diagnoses, Comos vs. Tasks, locations ===
* see [[Check_Renal_Tasks]]
* see [[Check_Renal_Tasks]]
==== Discussion ====
{{discussion}}
* see [[Check_Renal_Tasks#Discussion]]


=== Apache vs. CRF comorbid ===
=== Apache vs. CRF comorbid ===
* see [[Check ApARF CRF]].  
* see [[Query check ApARF CRF]].  


=== Apache vs. ARF Dx ===
=== Apache vs. ARF Dx ===
cross-checks impossible due to different definitions, see [[ARF (Diagnosis)]] and [[ARF (APACHE)]]
cross-checks impossible due to different definitions, see [[ARF (Diagnosis)]] and [[ARF (APACHE)]]


== Data Integrity Checks that can '''not''' be checked before sending==
* ''Query check_CCI_TISS_Dxs_vs_Dialysis''


== Data Integrity Rules that can '''not''' be checked before sending==
== Related articles ==
 
see [[:Category:Renal Problem (old)]] for other renal problems
===ARF and ICU TISS ===
{{Related Articles}}
* TISS 53 to 55: Don't forget to cross check the TISS form with the diagnosis and visa versa.
 
===ARF & TISS integrity checks===
* have TISS 53, 54, 55 but no Renal failure DX (350, 351, 352, 355, 356, 398, 450-499, 327, 357)
* from community hosp to teaching hosp with DX of 350 AND no dialysis on TISS at community hosp AND DX of 350 AND TISS 53, 54 or 55 marked at teaching hospital, then the DX of ARF for community hospital is correct.
 
== Related Articles ==
see [[:Category:Renal Problem]] for other renal problems
 
 


[[Category: Renal Problem]]
[[Category:Renal Problem (old)]]
[[Category: Questions]]
}}
[[Category: Data Integrity Rules]]
[[Category: Questions Diagnosis]]
[[Category: Questions Integrity Rules]]

Latest revision as of 16:31, 2021 December 30

Legacy Content

This page contains Legacy Content.

Click Expand to show legacy content.

See also ICD10 Guideline for Renal Coding

There are a few restrictions about which renal diagnoses can be coded together. These checks are currently done partly by Pagasa and have been partly implemented in CCMDB.accdb.

CRF in pt with transplant failure

Just a comment about CRF - Chronic Renal Failure: when pt has Renal Transplant Problems and/or Renal Transplant - Removal of Transplant-Organ and requires dialysis, they can have acquired diagnoses of ARF (Diagnosis), Acute Tubular Necrosis (ATN) and/or ARI, which is related to their new donor kidney.

Category:Renal insufficiency (old)

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.accdb, more are to follow.

CCMDB Data Integrity Checks: Competing Diagnoses

see query Check Renal IncompatibleDxs

Diagnoses, Comos vs. Tasks, locations

Apache vs. CRF comorbid

Apache vs. ARF Dx

cross-checks impossible due to different definitions, see ARF (Diagnosis) and ARF (APACHE)

Data Integrity Checks that can not be checked before sending

  • Query check_CCI_TISS_Dxs_vs_Dialysis

Related articles

see Category:Renal Problem (old) for other renal problems

Related articles: