Renal Coding Considerations (old): Difference between revisions
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
These checks are currently done partly by Pagasa ([[! | 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]]. | ||
== Data Integrity Rules that can be checked before sending== | == Data Integrity Rules that can be checked before sending== | ||
| Line 9: | Line 9: | ||
* [[Acute Tubular Necrosis | ATN]] (352-00) | * [[Acute Tubular Necrosis | ATN]] (352-00) | ||
* [[ARF (Diagnosis)]] (350 **) | * [[ARF (Diagnosis)]] (350 **) | ||
==== Implementation ==== | |||
Implementing ARF vs CRF as per [[Check Renal IncomaptibleDxs]]. The rule seems to be less consistent with ARI and ATN, we might include those at a later time. [[User:Ttenbergen|Ttenbergen]] 16:40, 29 September 2009 (CDT) | |||
=== Diagnoses, Comos vs. Tasks, locations === | === Diagnoses, Comos vs. Tasks, locations === | ||
| Line 25: | Line 28: | ||
=== Apache vs. CRF comorbid === | === Apache vs. CRF comorbid === | ||
* | * see [[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 Rules that can not be checked before sending== | |||
== Data Integrity Rules that can '''not''' be checked before sending== | |||
===ARF and ICU TISS === | ===ARF and ICU TISS === | ||
| Line 41: | Line 45: | ||
== Related Articles == | == Related Articles == | ||
see [[:Category:Renal Problem]] for other renal problems | see [[:Category:Renal Problem]] for other renal problems | ||
Revision as of 16:40, 2009 September 29
These checks are currently done partly by Pagasa ([[1]]) and are about to be implemented in CCMDB.mdb.
Data Integrity Rules that can be checked before sending
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
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 **)
Implementation
Implementing ARF vs CRF as per Check Renal IncomaptibleDxs. The rule seems to be less consistent with ARI and ATN, we might include those at a later time. Ttenbergen 16:40, 29 September 2009 (CDT)
Diagnoses, Comos vs. Tasks, locations
- Dialysis task is required if all of the following are true:
- one of the following is present:
- LOS >= 3
- Renal Transplant (80504 or 80505) is not present
- Dialysis Task must never be marked for
- GRA N3/N5/W3
- VIC N5/S3/S4/S5
Discussion
Trish mentions something in !_Automated_Data_Integrity_Checks#Q9.5_-_Dialysis_Tasks re patients admitted to above exception wards and then sent to tertiary center for dialysis. Apparently these should be coded. If that's true, we can not check for the exceptions. Please clarify, and also update Dialysis Tasks. Ttenbergen 16:42, 3 September 2009 (CDT)
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)
Data Integrity Rules that can not be checked before sending
ARF and ICU TISS
- 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