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

From CCMDB Wiki
Jump to navigation Jump to search
(Created page with "__NOTOC__ == List of items to bring to task meeting == Add to this by adding the following '''to the article where the problem is documented''': <pre>{{DiscussTask | explanation}}</pre> {{#cargo_query: tables=Discussions, _pageData |join on=Discussions._pageName=_pageData._pageName |fields=Discussions._pageName=wiki page, question, _modificationDate=Last modified |where=_pageData._pageName<>"MediaWiki:Common.js" and who="Task" |limit=1000 |rows per page=200 |default=...")
 
Line 24: Line 24:
'''Copied here as starting point for 2023, please edit/overwrite'''
'''Copied here as starting point for 2023, please edit/overwrite'''


*Present: ___
*Present: Allan, Gail, Julie, Michelle, Mindy, Stephanie, Tina, Val, Pagasa, Mailah
*Minutes prepared by: AG
*Minutes prepared by: AG
*Action items in BOLD
*Action items in BOLD
Line 30: Line 30:
1. [[Transition to Database Server#Shared Health]] - '''Nothing new''' about either of the possible alternative options for hosting the database.
1. [[Transition to Database Server#Shared Health]] - '''Nothing new''' about either of the possible alternative options for hosting the database.


2. Two related issues: (a)  [[APACHE Comorbidities in ICD10 codes]] - Moving to automated identification of the five APACHE II comorbid conditions, and (b) [[Non-standard ICD10 Diagnoses]] - Adding non-standard ICD10 Diagnoses to APACHE II codings for chronic conditions or admit diagnoses.
2. [[Controlling Dx Type for ICD10 codes]] - Regarding the task to improve data collector diagnosis assignment into the 3 "bins" of admission diagnosis, acquired diagnosis and comorbid diagnosis.
*Allan has done both of these tasks, and what remains to be done is: (a) Tina to reformat them for integration into our existing data infrastructure (ACCESS and SAS) (Tina has done), (b) send the reformatted version to Allan so he can ensure completeness (Tina has done), and finally (c) Tina/Julie to incorporate them into workflow and backdate them to 1/1/2019.  
*'''Lisa indicated that for a first pass on this, she will distribute all the codes among all the collectors'''.
*'''Allan and Tina to meet about this later today'''.


3. [[Location metadata storage]] - Regarding creating new table containing information (metadata) about individual medicine wards (including High Obs). Tina reports '''no new progress'''.
3. New item: Clarification of [[Pulmonary emphysema or bullous disease without COPD]]. Allan modified this Wiki entry to make it clearer.


4. [[Validating new types of DSM results]] - Update on lab issues -- '''Allan and Tina have a followup meeting planned with Dr. Sokoro and Alun Carter'''.
4. New item:  Regarding Sudden [[cardiac death (and died)]]
*After discussion we recognized that we have no need to specifically code patients' cause of death.  We know it occurred by virtue of the [[Dispo field]].  Thus we '''agreed to remove this item from the list of ICD-10 codes, and to have Julie go into all records where it has been recorded and remove it'''.  Allan modified the Wiki page also.


5. [[Controlling Dx Type for ICD10 codes]] - Regarding the task (led by Barret) to improve data collector diagnosis assignment into the 3 "bins" of admission diagnosis, acquired diagnosis and comorbid diagnosis. 
5. New question:  It was noticed that an error occurs if a diagnosis of Influenza is recorded (which is an implied bug) and one attempts to combine it with a Nosocomial problem code.  '''Tina will fix this.'''
*Lisa believes there is capacity to have one of the experienced collectors to work with Barret on this task.  '''Lisa, Barret and Julie to meet about this soon'''.


6. New item: for [[Pre acute living situation field]], how to code group homes. After discussion, we recognized that group homes, "Supportive Housing" and assisted living exist on a continuum of care levels in the community.  Furthermore, no user has ever asked for this information. Thus, we agreed to combine them altogether.  To this end '''Tina will create a new value for this field (to be called something like “Community Facility with support”, and distinguish it from PCHs'''.
6. Followup item from long ago: Seeking to get ABGs at Grace Hospital to be included in the Lab Info System (LIS).
 
*The last time we tried for this, in 2015, the resp therapy group at Grace was not interested in being required to manually logging this information into LIS, as IS done at HSC and St. B.
7.  New question:  now to code transfusion-associated fluid overload. Answer is combine one of the Congestive Heart Failure codes with [[Iatrogenic problem NOS, related to a surgery or procedure, NOS]], and of course to code the transfusion as a procedure.
*We think they may be more open to it now -- so '''Allan will ask Heather Smith to raise it with them.'''
*'''If they indeed now are willing, then Allan will talk to Dr. Soroko about getting it implemented'''.


8. '''Next Task meeting January 11, 2023 at 11 am'''
8. '''Next Task meeting January 11, 2023 at 11 am'''


== 2022... ==
== 2022... ==

Revision as of 20:29, 2023 January 11

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}}

Toggle columns: Last modified

wiki page question Last modified
wiki page question Last modified
Gangrene, NOS can we use this code for necrosis or necrotic wounds? Lisa Kaita 11:57, 2024 April 17 (CDT) 2024-04-17 5:03:39 PM
Query s tmp Boarding Loc ER delay reasonable There are many false positives due to ICU delays shorter than 30 mins. Do we want to change anything about that threshold? Discussed with Julie and Lisa today but can't remember the outcome. Ttenbergen 10:58, 2024 April 24 (CDT)
  • No we are fine with the thresholds, collectors are not happy about how many times the soft check prompts them, at least 3 when checking off the box, and then a couple more when we complete the file, you were going to think about this more Lisa Kaita 15:59, 2024 April 24 (CDT)
2024-04-24 8:59:31 PM
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) 2019-03-09 9:24:42 PM
Sepsis (SIRS due to infection, without acute organ failure) When the progression is very fast eg. admitted at 0100 with severe sepsis, lactate 1.7, then at 0220 lactate is now 2.7 do we use the admit severe sepsis and code the septic shock as acquired? Lisa Kaita 12:17, 2024 April 17 (CDT) 2019-03-09 9:24:42 PM
Severe sepsis 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) 2019-10-31 3:04:29 PM
Severe sepsis 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) 2022-02-17 10:56:05 PM
Severe sepsis When the progression is very fast eg. admitted at 0100 with severe sepsis, lactate 1.7, then at 0220 lactate is now 2.7 do we use the admit severe sepsis and code the septic shock as acquired? Lisa Kaita 12:17, 2024 April 17 (CDT) 2019-10-31 3:04:29 PM
Severe sepsis When the progression is very fast eg. admitted at 0100 with severe sepsis, lactate 1.7, then at 0220 lactate is now 2.7 do we use the admit severe sepsis and code the septic shock as acquired? Lisa Kaita 12:17, 2024 April 17 (CDT) 2022-02-17 10:56:05 PM
Shock, septic 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) 2019-01-10 7:32:04 PM
Shock, septic When the progression is very fast eg. admitted at 0100 with severe sepsis, lactate 1.7, then at 0220 lactate is now 2.7 do we use the admit severe sepsis and code the septic shock as acquired? Lisa Kaita 12:17, 2024 April 17 (CDT) 2019-01-10 7:32:04 PM
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)
  • 2024-04-08 4:27:53 PM
    Stroke, NOS we 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) 2024-04-17 5:01:53 PM
    Template:ICD10 Guideline Sepsis 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) 2024-04-17 5:17:33 PM
    Template:ICD10 Guideline Sepsis When the progression is very fast eg. admitted at 0100 with severe sepsis, lactate 1.7, then at 0220 lactate is now 2.7 do we use the admit severe sepsis and code the septic shock as acquired? Lisa Kaita 12:17, 2024 April 17 (CDT) 2024-04-17 5:17:33 PM

    Also see Task Team Meeting - Rolling Agenda and Minutes 2022

    _

    _

    ICU Database Task Group Meeting – Jan 11, 2023

    Copied here as starting point for 2023, please edit/overwrite

    • Present: Allan, Gail, Julie, Michelle, Mindy, Stephanie, Tina, Val, Pagasa, Mailah
    • Minutes prepared by: AG
    • Action items in BOLD

    1. Transition to Database Server#Shared Health - Nothing new about either of the possible alternative options for hosting the database.

    2. Controlling Dx Type for ICD10 codes - Regarding the task to improve data collector diagnosis assignment into the 3 "bins" of admission diagnosis, acquired diagnosis and comorbid diagnosis.

    • Lisa indicated that for a first pass on this, she will distribute all the codes among all the collectors.

    3. New item: Clarification of Pulmonary emphysema or bullous disease without COPD. Allan modified this Wiki entry to make it clearer.

    4. New item: Regarding Sudden cardiac death (and died)

    • After discussion we recognized that we have no need to specifically code patients' cause of death. We know it occurred by virtue of the Dispo field. Thus we agreed to remove this item from the list of ICD-10 codes, and to have Julie go into all records where it has been recorded and remove it. Allan modified the Wiki page also.

    5. New question: It was noticed that an error occurs if a diagnosis of Influenza is recorded (which is an implied bug) and one attempts to combine it with a Nosocomial problem code. Tina will fix this.

    6. Followup item from long ago: Seeking to get ABGs at Grace Hospital to be included in the Lab Info System (LIS).

    • The last time we tried for this, in 2015, the resp therapy group at Grace was not interested in being required to manually logging this information into LIS, as IS done at HSC and St. B.
    • We think they may be more open to it now -- so Allan will ask Heather Smith to raise it with them.
    • If they indeed now are willing, then Allan will talk to Dr. Soroko about getting it implemented.

    8. Next Task meeting January 11, 2023 at 11 am

    2022...

    Also see Task Team Meeting - Rolling Agenda and Minutes 2022