Task Team Meeting - Rolling Agenda and Minutes 2022: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Line 24: Line 24:
2.  Update on what Shared Health is planning with regards to the databases.  Allan reported that as requested, he provided Perry with a document (from Tina) a technical description of what is needed.  '''Awaiting more information from Perry'''.
2.  Update on what Shared Health is planning with regards to the databases.  Allan reported that as requested, he provided Perry with a document (from Tina) a technical description of what is needed.  '''Awaiting more information from Perry'''.


3.  Update on plan (4/15/2021 Task meeting) to implement automatic coding of APACHE comorbidities
3.  Update on plan (4/15/2021 Task meeting) to implement automatic coding of APACHE comorbidities'''Allan is working on refining the ICD10 codes'''.
*'''Allan is working on refining the ICD10 codes'''.


4.  Update on the decision from 11/30/2021 meeting to revert to the old system, of starting a new record (with new APACHE score and new admit diagnoses) with service changes.  This has been done, with relevant changes to the Wiki and “unwinding” of the 10 records that contain such MICU to SICU or SICU to MICU transfers into separate records.
4.  Update on the decision from 11/30/2021 meeting to revert to the old system, of starting a new record (with new APACHE score and new admit diagnoses) with service changes.  This has been done, with relevant changes to the Wiki and “unwinding” of the 10 records that contain such MICU to SICU or SICU to MICU transfers into separate records.
Line 46: Line 45:
10.  There is confusion about TISS elements #19 and #20.  '''Allan will track back in the Minutes to clarify what we want (7/8/21 and 9/1/21 minutes)'''.  '''Julie will figure out the correct # of TISS points for these'''.
10.  There is confusion about TISS elements #19 and #20.  '''Allan will track back in the Minutes to clarify what we want (7/8/21 and 9/1/21 minutes)'''.  '''Julie will figure out the correct # of TISS points for these'''.


11.  Tina identified that there are approximately 200 database questions that have been assigned for assessment but not addressed.  Lisa will go over this list and categorize them into 3 groups:  Need to be addressed; Can be deleted from further consideration; Unclear.  '''We’ll discuss this further next meeting'''.
11.  Tina identified that there are approximately 200 database questions that have been assigned for assessment but not addressed.  '''Lisa will go over this list and categorize them into 3 groups''':  Need to be addressed; Can be deleted from further consideration; Unclear.  '''We’ll discuss this further next meeting'''.


12.  '''Next meeting February 3, 2022 at 11 am'''.
12.  '''Next meeting February 3, 2022 at 11 am'''.

Revision as of 14:28, 2022 January 6

List of items to bring to task meeting

Add to this by adding the following to the article where the problem is documented:

{{DiscussTask | explanation}}
 QuestionModification date"Modification date" is a predefined property that corresponds to the date of the last modification of a subject and is provided by Semantic MediaWiki.
Cardiac arrestCould we please have some clarification around using this code and when to check as primary?
    • example 1 patient arrests in ER, goes to OR and is admitted to ICU from the OR. Diagnosis, cardiac arrest (6-10 min downtime) abdominal compartment syndrome/obstruction/perforation/, acute liver failure from shock liver, shock, NOS
  • when to carry it forward as an admit for subsequent profiles in the same episode of care?
    • example 2 April 6, PEA arrest secondary to anaphylactic shock, April 19 melena, scope suspicious for ischemic gut, goes to the OR April 20 confirms gangrenous bowel/perforation, abscesses, to SICU post op (clinically in SS but doesn't have lactate high enough for our criteria) do we still include the cardiac arrest code? (In MICU no anoxic brain injury, A & O) Lisa Kaita 11:54, 2024 May 2 (CDT)
2 May 2024 16:54:06
Gangrene, NOScan we use this code for necrosis or necrotic wounds? Lisa Kaita 11:57, 2024 April 17 (CDT)
  • discussed at April 24 TASK Allan will give this thought and address it at next TASK Lisa Kaita 20:01, 2024 April 24 (CDT)
  • 2 May 2024 16:03:55
    ICD10 Guideline SepsisHow hard of a rule is lactate >2? If they meet the criteria for septic shock with the exception of a high enough lactate, can we code septic shock Lisa Kaita 12:17, 2024 April 17 (CDT)
  • discussed at TASK April 24, Dr Ziegler is researching various definitions of septic shock and will speak to this at next TASK Lisa Kaita 19:57, 2024 April 24 (CDT)
  • 25 April 2024 00:57:46
    Kidney, acute renal failure, postproceduralcould we please have some guidelines around when to use this code? how long after the procedure can we use this code? Lisa Kaita 11:37, 2024 May 2 (CDT)2 May 2024 16:37:08
    STB ICUs VAP Rate, CLIBSI Rate Summary
  • IIRC we collected CAM positive (TISS Item) specifically for this, right? If so, can we stop collecting it? And can we make sure a stoppage like this in the future results in reviewing what we collect? Ttenbergen 10:02, 2024 March 20 (CDT)
    • Delirium rate per 1000 days per unit is being reported in the OIT Reports. ---JMojica 11:49, 2024 March 20 (CDT)
      • As in Delirium days is reported in Critical Care Program Quality Indicator Report? But that doesn't mention anything about per-1000-days. Ttenbergen 17:00, 2024 March 20 (CDT)
      • The rate is mentioned in the succeeding definition with the delirium days as numerator. Your proposal here is to stop collecting TISS item CAM positive which I disagree because that TISS item is being used and reported as rate in OIT Report. Besides, the reason why it was dropped in in the STB VAPCLI report is because the requestor has changed. Brett Hiebert who used to request this was involved in the VAP group and another Delirium group so he asked to have both as one request. Brett had left and the VAP group filled up a new request to continue the VAP data and not on the delirium data. --JMojica 13:58, 2024 March 25 (CDT)
  • 8 April 2024 16:27:53
    Sepsis (SIRS due to infection, without acute organ failure)How hard of a rule is lactate >2? If they meet the criteria for septic shock with the exception of a high enough lactate, can we code septic shock Lisa Kaita 12:17, 2024 April 17 (CDT)
    • discussed at TASK April 24, Dr Ziegler is researching various definitions of septic shock and will speak to this at next TASK Lisa Kaita 19:57, 2024 April 24 (CDT)
    9 March 2019 21:24:42
    Severe sepsisHow hard of a rule is lactate >2? If they meet the criteria for septic shock with the exception of a high enough lactate, can we code septic shock Lisa Kaita 12:17, 2024 April 17 (CDT)
  • discussed at TASK April 24, Dr Ziegler is researching various definitions of septic shock and will speak to this at next TASK Lisa Kaita 19:57, 2024 April 24 (CDT)
  • 31 October 2019 15:04:29
    Shock, septicHow hard of a rule is lactate >2? If they meet the criteria for septic shock with the exception of a high enough lactate, can we code septic shock Lisa Kaita 12:17, 2024 April 17 (CDT)
  • discussed at TASK April 24, Dr Ziegler is researching various definitions of septic shock and will speak to this at next TASK Lisa Kaita 19:57, 2024 April 24 (CDT)
  • 10 January 2019 19:32:04
    Stroke, NOSwe need clarification on when to use this code, eg. if there is a history where it says a history of stroke, or if on CT they comment remote lacunar infarcts? Lisa Kaita 12:01, 2024 April 17 (CDT)17 April 2024 17:01:53

    Also see Task Team Meeting - Rolling Agenda and Minutes 2020

    _

    _

    ICU Database Task Group Meeting – January 6, 2022

    • Present: Allan, Julie, Sherry, Lisa, Stephanie, Tina, Val, Pam, Mailah, Mindy
    • Minutes prepared by: AG
    • Action items in BOLD

    1. Update on new lab listings, which appear to duplicate prior listings. Allan has begun working on this. Nothing new to report.

    2. Update on what Shared Health is planning with regards to the databases. Allan reported that as requested, he provided Perry with a document (from Tina) a technical description of what is needed. Awaiting more information from Perry.

    3. Update on plan (4/15/2021 Task meeting) to implement automatic coding of APACHE comorbidities. Allan is working on refining the ICD10 codes.

    4. Update on the decision from 11/30/2021 meeting to revert to the old system, of starting a new record (with new APACHE score and new admit diagnoses) with service changes. This has been done, with relevant changes to the Wiki and “unwinding” of the 10 records that contain such MICU to SICU or SICU to MICU transfers into separate records.

    5. Allan reported that he is working on drafting a Data Sharing Agreement that all users of line-level (i.e. individual record) data will need to complete to obtain such data. Work is ongoing on this. Also, a decision will need to be made about whether we need a similar agreement for users of cumulative/aggregate data.

    6. Discussion about the Minimal Dataset and reporting. We agreed:

    • We will retain the 11 elements of the “true” minimal dataset, all of which come from Cognos.
    • Going forwards, all reporting by Julie will consist of details only from completed records, along with information about what % and # of records for the time interval are incomplete as of the time of the reporting.
    • Lisa will let all collectors know of this change
    • Tina will change the Wiki regarding it
    • Allan will let Bojan know -- done.

    7. There is a new ICD10 code U07.5 Past history of Covid-19 infection which is meant to be used just like the other “Past history of…” codes. Lisa to let all collectors know about it.

    8. After discussion we agreed that there is no further need for the Wiki page HSC Boarding Locations. Tina will delete it.

    9. The question was raised about definition of “emergency surgery”. After discussion we agreed to maintain it as is, i.e. admitted from Operating Room or Recovery AND surgery was classified as E1. Tina will ensure that this is consistent in the Wiki.

    10. There is confusion about TISS elements #19 and #20. Allan will track back in the Minutes to clarify what we want (7/8/21 and 9/1/21 minutes). Julie will figure out the correct # of TISS points for these.

    11. Tina identified that there are approximately 200 database questions that have been assigned for assessment but not addressed. Lisa will go over this list and categorize them into 3 groups: Need to be addressed; Can be deleted from further consideration; Unclear. We’ll discuss this further next meeting.

    12. Next meeting February 3, 2022 at 11 am.

    2021...

    Also see Task Team Meeting - Rolling Agenda and Minutes 2021