CRRT

From CCMDB Wiki
Jump to: navigation, search
Projects
Active?: active
Program: CC
Requestor:
  • Critical Care Program: Jodi Walker Tweed, Ryan Holland
  • Renal Program: Dr. Joe Bueti, Dr Herman Lam


see also other pages in Category:CRRT

The CRRT project tracks wikipedia-Hemofiltration Continuous Renal Replacement Therapy CRRT use and reasons. For now the data is collected at HSC MICU and HSC SICU.

Data Collection Instructions

for which patients to code

HSC Critical Care patients only who get CRRT therapy, defined as those who have an CRRT (TISS Item).

how to code in CCMDB TMP

Nephrology will complete a the non-permanent health record form Renal Diagnostic Codes Checklist. This form is attached to the HSC_ICU_CRRT Consult form and will stay on the patient chart. The Nephrology attending must enter the reason(s) for CRRT in the form (i.e. primary reason will be assigned by number 1 and the secondary reason(s) if available will be assigned by number 2). Collectors simply transcribe this; no interpretation or correction against chart are required.

Enter

  • Project: CRRT
  • Item / Column N: enter the field marked in the form
    • there could be more than than one reason for CRRT, if so, enter additional rows
      • enter the number 1 or 2 as applicable.
        • if there is only one reason, enter 1.
        • if there is more than one reason, enter 1 for the primary reason and 2 for the rest of the reason(s)
        • if there is more than one reason and the Nephrology attending did not indicate the ranking, enter 2 in all reasons.
    • if entry is 'Form Missing' or 'Form not done'

options for entries

  • AKI pre-renal
  • AKI shock sepsis
  • AKI shock no sepsis
  • AKI hepatorenal
  • AKI cardiorenal
  • AKI contrast
  • AKI drug
  • AKI endogenous
  • AKI exogenous
  • AKI postop
  • AKI thrombotic
  • AKI glomerulonephritis
  • AKI interstitial nephritis
  • AKI urinary obstruction
  • ESRD continuous CRRT
  • ESRD intermittent HD
  • Overdose
  • Fluid reduction
  • Form not done (call Ryan 7-3699)
  • Form missing (call Ryan 7-3699)

follow-up when the data is not on the chart

If you enter 'Form Missing' or 'Form not done' CCMDB.mdb will remind you to email

  • email Ryan Holland, Dr. Herman Lam and Dr. Joe Bueti.
  • Include:
    • Subject: CRRT Info missing
    • minimal patient identifier
    • whether sticker is missing or only not filled out

follow-up

If the patient is still in your laptop and if you are still working on the chart and then you find a filled-up HSC_ICU_CRRT Consult form in it, change the entry with the reason for CRRT. Otherwise, you are not expected to run after the chart or wait for Ryan or the nephrologist until the form is filled up. If the profile is already complete but still the form is missing or not filled up, then submit the profile with 'Form Missing' or 'Form not done'.

Adding STB

  • If possible, for STB, it would be optimal if the sheet that the renal attending could be put on the electronic chart. It could pop up when the orders are written for CRRT or the doctors could put it into their electronic progress notes. We may find that compliance using a paper sheet may not be good here. --LKolesar 10:48, 2016 February 9 (CST)
    • The CRRT project is piloted at HSC for now. There is no discussion yet if to be done at STB. JMojica 14:34, 2016 September 16 (CDT)

Start and Stop Dates

  • Start Date from CCMDB TMP: Monday Sept 19, 2016
    • CRRT usage from TISS only: January 1, 2016
    • Adding the rank of AKI diagnosis start date: May 24, 2017.
  • Evaluation Date: Jan 12.2017
  • End date: none

Form revision start date

CCDMB Data Integrity Checks (needs review)

None yet

CFE checks

  • query NDC_zCRRT_tmp_no_TISS: lists patients who have tmp entry but no TISS
  • query NDC_zCRRT_TISS_no_tmp: lists patients who have TISS entry and admission after <when?> but no tmp entry.

Data Use

  • To identify the reason(s) why CRRT therapy was requested by the attending nephrologist for quality improvement and resource utilization in the Renal Program.
  • To track the CRRT usage for workload and resource utilization in the Critical Care Program.

Background

The patients on CRRT therapy during the stay in ICU are being tracked by a CRN in Critical Care Program since ?? (date to be asked). The CRN collects the patient names, the hospital number, the renal diagnosis for reason for CRRT, the initiation and duration of therapy in paper form. The Renal Program states that they need the demographics of patients who were on CRRT as well as the reasons why CRRT were requested by Neprologists for quality improvement, resource utilization and billing purposes. Critical Care Program shares these information to the Renal Program by faxing the hand written data sheets to them on a monthly basis.

In Jan 2013, the Critical Care Program implemented the usage of the new TISS28 form which include various nursing activities, interventions and procedures including CRRT. The bed side nurse records on the TISS form these activities if present on a daily basis for each patient during the whole duration of stay at ICU. The data collectors of the Critical Care Database quality check the entries of the TISS forms for completion and consistencies. Since the same information is being collected by the CRN and bed side nurses, a comparative analysis between the two process of data collections and an additional real time audit by an independent auditor were done. TISS CRRT had 96% matched with the real time CRRT while 85% matched with the CRN CRRT.

The Critical Care and Renal Programs made a decision last Feb 2, 2016 to consider the TISS28 as the source of CRRT data starting Jan 2016.

However TISS28 does not contain the diagnostic reasons for CRRT therapy so a request to collect this information separately by the data collectors of the Critical Care Database was made. The Renal Program had identified the possible reasons for CRRT therapy and proposed to list them in a form for the attending Nephrologist to mark. The form has been developed and in Sept 2016 has been placed together with the Nephrologist's consult for the attending Nephrologist to fill up. A meeting has been held Sept 15, 2016 with the Critical Care Manager and Statistician to begin the collection of the CRRT diagnostic reasons in the next three months Oct to Dec 2016 and the group have agreed to have the results presented on Jan 12, 2017.

Additional data

There was not space in the tmp dropdown for the full length reason as on the form, so we use a shortened version in s tmp table. To translate the shortened version to the full version, e.g. for reporting, use table s_tmp_CRRT.

Location of CRRT Related Info

x: CCMDB_Special_Projects_CRRT_Ryan&Bueti

SAS Program

  • CRRT Days from TISS28 - The SAS program is in X:\Julie\CC Projects\CRRT_Ryan&Bueti\ICU_CRRT_byMonth.sas. The program generates the list of patient names, PHIN, Chart#, Date of Birth, First day on CRRT, year, month and calendar days on CRRT and total CRRT days.
  • Reasons for CRRT starting Oct 2016 - are added to the SAS program above and frequencies of the reasons are presented in the report.

ICD10

We decided that we will need to keep coding this in tmp even when we move to ICD10 because:

  • some reasons would require more than one code
  • some reasons don't have a specific ICD10 code and would not be captured

equivalent ICD10 dxs

As emailed by Allan Garland 2017-11-18: He is comfortable with these:

There are concerns about these:

From email:

The ones in BLACK (ie the first set) I'm comfortable with.  But note that 2 of them require 2 codes combined.
The ones in RED (ie the second set) don't have specific ICD10 codes.  I don't even know what they mean by AKI endogenous and exogenous.  And AKI thrombotic is nonspecific in that it could be EITHER of the 2 ICD10 codes I listed there.  

Note that I only here tried to find ICD10 codes for the causes. The coders would still need to code the acute kidney failure, if present. (i.e. Kidney, acute renal failure NOS, Kidney, renal failure/insufficiency/uremia, unspecified as acute or chronic or Kidney transplant, failure or rejection or unspecified complication)

Because I wasn't able to map EVERY one of their entities, we probably need to talk more about how to move forward on this item.