Query check CCI ICD10 Dialysis no Dx

From CCMDB Wiki
Revision as of 13:08, 2012 November 5 by Ttenbergen (talk | contribs) (Created page with "=== Q2.3(new) - CRF/ARF vs TISS 53, 54 and 55 === ''Note: must be tested after sending since TISS not available before.'' Any patient with '''all''' of the following is an err...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Q2.3(new) - CRF/ARF vs TISS 53, 54 and 55

Note: must be tested after sending since TISS not available before. Any patient with all of the following is an error:

Q2.3 Discussion

  • if community Hosp and admit or complication is ARF and patient discharged to teaching (HSC or STB), and TISS 53-55 not marked, this is okay, because community sent to teaching for dialysis. (Trish)
    • If LOS>3days this would be problematic to the patient, would it not. If the time restriction still stands, then the LOS check above already takes care of this. Are you sure you want patients with 351 who are not dialyzed for more than 3 days not to be flagged? Ttenbergen 14:14, 29 October 2008 (CDT)
    • YES I am sure, otherwise we audit every single dialysis patient (like we are doing right now) to find out that most CRF pts don't have dialysis done daily anyways. So 3 days or less without is fine. (Trish)
      • The above definition already excludes the patients with a LOS < 3. What I am wondering about is CRFs in community who are discharged to teaching after more than 3 days. Those should not be OK, right? Ttenbergen 14:20, 30 October 2008 (CDT)
    • If you are able to add this as a double check to CCMDB where the collector must verify TASK dialysis YES or NO if 351 before they send that would help. Currently cleaner mdb is generating too many checks only to find out that TASK item was indeed not missed for these patients.
      • If we come up with a consistent no-exception rule I can add it, otherwise it just becomes another "gopher" that will be ignored. If it is a check, it would have to be a show-stopper that they have to correct before being allowed to send. Ttenbergen 14:20, 30 October 2008 (CDT)

Q2.3 Programming Status - waiting for clarification

TRISH HERE: I think the query looks fine.TOstryzniuk 17:57, 29 October 2008 (CDT) TINA HERE: There seem to be discussion items left, aren't there? Ttenbergen 14:22, 30 October 2008 (CDT)

  • Consider outcome of ARF vs ARI discussion in Q2.2 for this query as well.