User:Ttenbergen/questions for tina

From CCMDB Wiki
Jump to navigation Jump to search

Questions

Toggle columns: ModDate

edit page question ModDate
edit page question ModDate
edit DC Treatment _dev_CFE_Data
  • The field has a length of 50 and should be reduced to 2 now that that's the longest content.
 2022-09-01 10:01:08 PM
edit Change of GRA location names from "our" names to EPR/Cognos names
  • Do we need to change old ITEM values for consistencies? --JMojica 12:11, 2022 March 8 (CST)
    • It might be nice to have, and you would know better how important this is. If we want to do it, we would need to ask Pagasa to run the update queries for each item. The query would be like
    • UPDATE L_TmpV2 SET L_TmpV2.Item = "GH-Emergency"
WHERE (((L_TmpV2.Project)="Boarding Loc") AND ((L_TmpV2.Item)="GRA_ER"));
        • Was updated for all except GRA Boarding... Tina needs to fix wiki page. Ttenbergen 16:11, 2022 March 23 (CDT)
    		 2022-03-23 9:11:36 PM
    edit ER Delay
  • I have re-updated Created_Variables_Common_maker_2021 query, for some reason the change I had made was not reflected in the master version. Ready to test. Ttenbergen 13:25, 2022 June 28 (CDT)
    • emailed Tina some inconsistencies found in ER Delays Aug 15,2022. --JMojica 13:21, 2022 August 29 (CDT)
    		•  2023-02-15 10:39:34 PM
    edit Query NDC Bad Postal Code
  • I think this is the process where you said you are having problems with copy/pasting. Copy pasting isn't even mentioned here, so maybe update the process to show how you actually do this, so that someone like Sheila Rusnak would be able to follow the instructions. Ttenbergen 15:45, 2022 March 17 (CDT)
    • Do you create that query each time? Would we be able to update the NDC query that finds these in the first place to include the info you need? We can discuss at our next meeting. Ttenbergen 16:23, 2022 March 17 (CDT)
      • Taking this off Pagasa's list for now, since if we can get this data from DSS we won't need to do this any more. Ttenbergen 15:36, 2022 March 24 (CDT)
    		•  2022-08-10 9:22:01 PM
    edit Transfer Delay (Critical Care)
  • There were problems with the query I provided to Pagasa, this one doesn't seem to play nice if pasted as SQL. Waiting for reply from Julie on above before providing update since it might change. Ttenbergen 11:04, 2022 September 21 (CDT)
    		•  2023-03-23 6:08:10 PM
    edit Transfer Delay (Medicine)
  • this is now implemented in Created TransferReady query so we should just refer there and explain there.
    		•  2023-03-23 4:45:26 PM
    edit R Filter Field Don't understand where or how Julie wants these moved, I don't thin we have a tmp project for these; we can make one but then I'd need a clear definition of what these are. Emailed Julie Ttenbergen 09:52, 2022 August 4 (CDT)
  • CCN/CC (co managed CCU patients intubated/non ventilated) – 633 records from 1989-2004 at STB/HSC MICU. Based on the D_ID, the physical location-service involves, CCU, MICU,SICU.
    • looks like similar with ICUOtherService with a twist (i.e. with intub/non ventilated procedures). I think better as a separate tmp project.
    • in the booklet it says - This codes applies to coronary care patients who are deemed too sick for the Coronary Care Unit and are managed or co-managed in the Medical ICU because they required either ventilation, inotropes, central lines or IABP.
    • if this is the definition, I wander when filtered from L_LOG, the D_ID label have CCU, SICU in addition to HSC MICU or STB MICU (showed HSC_CCU--*, HSC_MICU--*, HSC_SICU--*,STB_CCU-*, STB_MICU-*, VIC_MICU-*) . Not sure if VIC_MICU is an entry error but this has acquired dx Debridement-cardiovascular entry, maybe correct. Also maybe the physical location does not matter? --JMojica 14:53, 2022 August 29 (CDT)
  • H/B/HB/BH (HSC CCU at H7, B3 or both) – 1100 records from 2003 – 2006 at HSC CCU
    • looks like this is similar with tmp boarding concept except without start dates but only location. I think better to make a separate project than add to current tmp Boarding since these had older data (maybe name the project as HSC CCU Location) --JMojica 14:55, 2022 August 29 (CDT)
    		•  2022-09-01 10:19:07 PM
    edit Non-standard ICD10 Diagnoses Dx grouping
  • With our addition of codes, collectors may use one of our codes rather than the closest standard ICD10 code. In that case, the dx would not show up in the range. How should we address this? The most likely candidates above seem Bronchiolitis obliterans organizing pneumonia (BOOP, cryptogenic organizing pneumonia (COP)) and SARS (severe acute respiratory syndrome)
    • AG REPLY -- for this nonstd BOOP code, there are no existing issues regarding any of the comorbid groups (e.g. Charlson)
      • Allan, could you confirm that that this is what we found when we looked into BOOP.
  • AG REPLY --- so far Tina the only 2 U-codes that would ever be a primary dx are U04 and U14.68 -- which belong respectively to ICD10 chapters J and E. But whenever we add a new U-code we need to remember to decide which chapter (if any) it needs to be included under. Tina to add to template.
    • I can't add this to the template, this is not how templates work, they won't warn me as I start a new dx page. We'd need to remember this some other way. And I just saw other dxs that might fit in here: Diabetes mellitus acute complication: Non-ketotic hyperosmolar state, Asystole, Pulseless Electrical Activity (PEA)
    • Actually, neither BOOP nor SARS would currently be captured by our APACHE Acute Dxs in ICD10 codes filter - they likely should be. So this is still an issue and we would miss them if we did something similar. How do we fix it for the Apache codes and prevent this problem going fwd? Ttenbergen 15:22, 2022 June 30 (CDT)
      • Discussed at JALT, Allan will review. Ttenbergen 10:32, 2022 August 24 (CDT)
        • Allan sent an email 2022-10-02 that provides a new inclusion list for some of these. Nothing for APACHE or Charlson Comos, but additions for APACHE Acute Dxs in ICD10 codes. Tina needs to process the additions into S ICD10 APACHE Dx patterns table. Ttenbergen 16:54, 2022 October 27 (CDT)
        • Additionally, Tina will provide Allan the filter info as it's stored in Access so that future updates aren't confusing. Ttenbergen 17:00, 2022 October 27 (CDT)
        • Additionally we need some way to make sure we consider this when we add dxs. Ttenbergen 17:00, 2022 October 27 (CDT)
  • figured out that the structure of APACHE Acute Dxs in ICD10 codes is way different than I had thought and that my current implementation can't accommodate it, reviewing with Julie. Ttenbergen 23:09, 2022 October 27 (CDT)
    		•  2022-10-28 4:09:28 AM
    edit High-Obs Wards Tina to add. 2022-10-20 9:32:54 PM

    To dos

    wiki page question action
    wiki page question action
    R Filter Field _after
    • removed field from sending
    • removed field from sending
    • removed field from ccmdb_data
    • remove field from CFE data
    • delete wiki page when done
    		 2022-08-09
    Controlling Dx Type for ICD10 codes _after
  • Built query "z_ComoAdmAcqu_Primary_List", exported to excel, sent to Barret; Allan said this is low priority, so putting a review data of 3 months from now
  • added this back to the task list, been almost 6 months
    		•  2022-08-10
    Accept DtTm field _after
  • Field is legacy; once no longer used, remove it from sending and then from ccmdb_data. Query to check:
    • SELECT L_Log.D_ID, L_Log.RecordStatus, L_Log.Accept_DtTm, L_Log.Arrive_DtTm
    FROM L_Log
    WHERE (((L_Log.RecordStatus)="incomplete") AND ((L_Log.Accept_DtTm) Is Not Null) AND ((L_Log.Arrive_DtTm) Is Not Null));
    • 98 left as of 2022-08-04
    		 2022-10-30
    Blood Product Data _after
  • Identified as something we should do to streamline data collection. I have made this page to document progress toward this import.
    • This will not happen until we have a PHIA approved repository. Ttenbergen 11:32, 2022 February 9 (CST)
      • Nothing will come of this until our data is stored elsewhere, so pulling it onto my list so we have some record that this is an outstanding want. Ttenbergen 13:04, 2022 June 22 (CDT)
    		•  2022-06-22
    Direct Data Access for RIS/PACS _after
  • Identified as something we should do; the notes below are quite old but might still be a starting point.
    • This will not happen until we have a PHIA approved repository. Ttenbergen 11:32, 2022 February 9 (CST)
      • Nothing will come of this until our data is stored elsewhere, so pulling it onto my list so we have some record that this is an outstanding want. Ttenbergen 13:04, 2022 June 22 (CDT)
    		•  2022-06-22
    Query check long transfer delay _after
  • This will need to be implemented when the 3SD is available.
    		•  2022-08-04
    Created Variables Common 2021 table _after
  • When this is done, Query check_long_transfer_delay and Created Variables Common table will need to be reviewed.Ttenbergen 13:41, 2022 June 14 (CDT)
    		•  2022-08-04
    Controlling Dx Type for ICD10 codes _after

    Make sure that these examples that were mentioned over time are adressed:

    Arrive DtTm field _after
  • Field is legacy; once no longer used, remove it from sending and then from ccmdb_data. Query to check:
    • SELECT L_Log.D_ID, L_Log.RecordStatus, L_Log.Accept_DtTm, L_Log.Arrive_DtTm
    FROM L_Log
    WHERE (((L_Log.RecordStatus)="incomplete") AND ((L_Log.Accept_DtTm) Is Not Null) AND ((L_Log.Arrive_DtTm) Is Not Null));
    • 98 left as of 2022-08-04
    		 2022-10-30
    R Filter Field _CFE_Data_reconsolidate
  • move into ICD10 and tmp - emailed Pagasa Ttenbergen 09:53, 2022 August 4 (CDT)
    • emailed again because the first email didn't explain that the relevant info is under "expand" Ttenbergen 11:42, 2022 August 23 (CDT)
      • Pagasa emailed "done" Aug 23 Ttenbergen 17:19, 2022 September 1 (CDT)
  • figure out last two sets of values - emailed Julie Ttenbergen 09:53, 2022 August 4 (CDT)
    • emailed again because the first email didn't explain that the relevant info is under "expand" Ttenbergen 11:42, 2022 August 23 (CDT)
  • and eliminate this field
    		•  2022-08-25
    Hospitalization ID _CFE_Data_reconsolidate
  • once we have some ClientVisitGUID field data to test we can delete this field, table and page.
    		•  2022-09-25
    Query check ICD10 CLI vs CCI CentralLine _dev_CCMDB * needs to be added to CCMDB
    Cross Check Engine _dev_CCMDB
    • implement better cross-check triggering
    		 2022-04-27
    Problems related to event timing of data consistency checks _dev_ccmdb
  • Listed as ready to fix so needs to be on list. See also Cross Check Engine
    		•  2022-04-13
    ClientGUID field _dev_ccmdb
  • review linking and related processes to see what could change to make best use of this
  • remove the L_Person table - we don't use it and this further means we don't need/use it. as confirmed with Julie here.
    		•  2022-09-25
    Query check CCI CXR vs LOS _dev_CCMDB
  • Not currently implemented; starting point for the query exists but doesn't yet include Julie's values. Also, isn't being called from anywhere.
    		•  2022-04-21
    Query check CCI TISS time means must be two _dev_CCMDB
  • summarized discussion, waiting for confirmation from Julie
    		•
    Processing errors in patient data _dev_CFE 
    Automate the populating of notes so button just does it.
    • raise an input box for a summary, if gets content put data and content into Notes, else put nothing.
    Centralized data front end.accdb Change Request _dev_CFE
  • CCI and ICD10 make button for Pagasa
    		•
    Centralized data front end.accdb Change Request _dev_CFE
  • Linked pairs, better storage
    		•
    CFE Inline Integrity Checks _dev_CFE
  • ready to implement inline cross check for CFE edits. Ttenbergen 10:03, 2022 September 6 (CDT)
    		•  2022-09-06
    Query Mgmt Collector Admission Count _Dev_CFE mgmt queries
  • This table can be removed, but query Mgmt_Collector_Admission_Count needs to be cleaned up as well. No longer relevant after PatientFollow Project.
    		•
    S dispo Collector Location table _Dev_CFE mgmt queries
  • This table can be removed, but query Mgmt_Collector_Admission_Count needs to be cleaned up as well. No longer relevant after PatientFollow Project.
    		•
    Location metadata storage _locationData
  • _Dev_CFE linking of s_LocationData table
  • _Dev_CCMDB - process to import data from wiki (similar to Converting ICD10 between wiki and ccmdb.accdb)
  • set up wiki template for locations
  • consider data import for locations so no manual pre-populating of pages
  • S_level_of_care needs to be integrated with whatever metadata we set up
  • discussed at Task whether we should wait for Shared Health info, will make our own; Shared Health's data is no better than ours, so won't do that.
  • STB-L2HA is another page we will need to include when we deal with this.
    		•  2022-02-09
    Collection location documentation _locationData
  • How should we now keep track of the ward/unit info on the wiki? More questions on page.Ttenbergen 16:07, 2021 July 14 (CDT)
    • Perhaps this can also be included in the Location metadata storage you will set up showing the start and end dates and the bed size. --JMojica 14:32, 2022 February 7 (CST)
      • Agreed! This is also why I think where possible we should shift the s_dispo contents to the same name so the Location metadata storage can supply both. I want to discuss how to best encode this with you, hopefully tomorrow at out wiki meeting. Ttenbergen 15:14, 2022 February 8 (CST)
        • I need the s_dispo because I am using the other columns as various categories of the detailed numeric locations name and I do not want to drop it for now. I have yet to see the Location metadata storage you are talking about to decide.
          • Sorry didn't say that clearly. Don't mean to eliminate s_dispo table at this time, just want to make sure we use same location name as in Boarding Loc where applicable, so we can store the metadata all in one table. Ttenbergen 13:36, 2022 February 9 (CST)
            • Decided at Task today that this likely needs to be done on wiki with dates. Taking off Julie's list until I figure out details Ttenbergen 16:01, 2022 June 22 (CDT)
    		•
    Location metadata storage _locationData
  • Discussed at JALT; we need to store this on a per page on wiki level, with multiple start and end dates being possible. Tina needs to create the structure for this and pre-populate. Probably discuss with Julie at the planning stage. Ttenbergen 12:04, 2022 June 22 (CDT)
    • It needs to be possible to access this as data. Ttenbergen 09:58, 2022 June 28 (CDT)
    		•  2022-06-22
    Query maintenance s tmp deletables _regular * this should be done regularly, maybe every 6 months 2023-02-10
    S dispo table _wiki housekeeping
    • break this out because it needs to apply to locations in general, wiki side, s_dispo, boarding loc etc.
    		 2022-02-10
    S ICD10 Chapter block pattern table _wiki housekeeping
  • Just storing this here for now, it should really be integrated into the SMW like the Charlson and Apache ones. Generated by query CCMDB.accdb.s_ICD10_Chapter_block_pattern_wikimaker.
    		•
    Iatrogenic, infection, central venous catheter-related bloodstream infection (CVC-BSI, CLI) _wiki housekeeping
  • we have a page about attribution somewhere, make sure that this is consistent.
    		•  2022-08-04
    EPR Admit DtTm field _wiki_housekeeping
  • confirmed this is really unused
  • removed field from sending
  • removed field from ccmdb_data
  • confirmed field is not in CFE data
  • delete wiki page when done
    		•  2022-08-09
    Pharm Flow Complete _wiki_housekeeping
  • confirmed this is really unused
  • removed field from sending
  • removed field from ccmdb_data
  • removed field from CFE data
  • delete wiki page when done
    		•  2022-08-09
    Room nr _wiki_housekeeping
  • removed field from sending
  • removed field from ccmdb_data
  • removed field from CFE data
  • delete wiki page when done
    		•  2022-08-09
    FinalCheck field _wiki_housekeeping
  • removed field from sending
  • removed field from ccmdb_data
  • removed field from CFE data
  • delete wiki page when done
    		•  2022-08-09
    ApLab Complete _wiki_housekeeping
  • removed field from sending
  • removed field from ccmdb_data
  • removed field from CFE data
  • delete wiki page when done
    		•  2022-08-09
    Collection location documentation _wiki_housekeeping
  • How should we now keep track of the ward info on the wiki? Do we actually need to? Or is it sufficient to tell the number of beds at e.g. Grace Medicine? what links to site/locations page is likely an indicator of the audience for this info, but Julie may well link from reports as well. Depending how we want to use this going forward, a static page might be an option, but then we can no longer link to individual locations. If we keep separate locations, we need to make sure we keep them updated.
  • I have put this on Julie's question list as well, and emailed Julie and Lisa about it. Ttenbergen 16:07, 2021 July 14 (CDT)
    		•  2021-09-01
    LOS _wiki_housekeeping
  • need to integrate this better and clean things out; also should make sure that queries that deal with LOS use Function LOS()
    		•  2022-03-01
    Query check CCI TISS time means must be two
  • Can you confirm that what I described above is what you have in mind? Ttenbergen 16:27, 2022 December 1 (CST)
    • Correct. sorry for the delayed response. --JMojica 15:28, 2022 December 14 (CST)
      • Julie replied, back in Tina's court Ttenbergen 15:42, 2022 December 14 (CST)
    		•
    ClientGUID field
  • Chastity confirmed there is a merge process for J Does who get identified. Confirming how this works, emailed Chastity 2022-06-16.
  • Asked Chastity if 3 month updates will be possible.
    		•  2022-06-30
    High-Obs Wards
  • Discussed with Julie 15:49, 2022 October 19 (CDT): so much easier to do this with a simple explicit match than to do it through data that we will do it htis way. I will need to link the pages somehow to tag that they are HOBS at some point, and we can have our actual match statements in here.
    		•  2022-10-19
    Transfer Delay (Critical Care)
  • Discussed with Julie that we will actually update these in the data rather than do these updates at reporting time. The query below should do it. Pagasa, could you apply it when you get a chance and update here when done? Thanks! Ttenbergen 09:46, 2022 June 29 (CDT)
    • when I started to make the query to update this I came across TRs that were not on the same date as the dispo_dttm. I can understand why we would change times if the TR is on the Dispo Dt, but it doesn't seem to make sense to change them if they are earlier. So, I just want to make sure that you really would have reported e.g. the following with a changed time.
    • D_ID Transfer_Ready_DtTm Dispo_DtTm HrsMins new_tr_dttm
    GRA_N3-3089 2007-07-31 2007-08-23 15:30:00 00:00:00 2007-07-31 10:00:00
    • I only make a substitution if same date with Dispo date. Added that part now. however when I have looked at my current code, I no longer have this substitution. Is it because you have combined the dttm together when we moved to access from Ed's and thus the time became 00:00. how did you handle it when transitioning to ACCESS, those without time - did you make the transfer ready dttm blanks or made time to 00:00 ? --JMojica 11:37, 2022 September 21 (CDT)
          • This is one field in Access now, so leaving them blank isn't an option. So you treated blank and midnight differently? Would anyone reasonably become transfer ready at midnight? No rounds happening then. I guess it's possible. So, really you haven't done this for some time, possibly since we moved form Ed's version? I am also prepared to take this whole thing out of the documentation and not do it at all... Ttenbergen 16:20, 2022 September 22 (CDT)
            • I agree, let us drop this whole thing out about transfer time missing and do not do any substitution at all when time is missing. --JMojica 11:08, 2022 October 12 (CDT)
              • Will you stop doing them in SAS as well, then? Otherwise we are back to inconsistent definitions. Ttenbergen 11:55, 2022 October 12 (CDT) ****** OK. --JMojica 08:53, 2022 October 19 (CDT)
            • I removed the sub article ... with missing time. --JMojica 16:13, 2023 January 17 (CST)
    Query NDC Bad Postal Code
  • emailed Chastity to see if we could get Postal Code data from them rather than maintaining our own.
    • Never got a response. Emailed Chastity again. Ttenbergen 14:41, 2022 June 30 (CDT)
    		•  2022-07-15
    APACHE Scoring table
  • Generally, if a pH value is present, other ABG values will be present as well. However, what if only a pH value is present? Should it's score be summed into the physiological score or not? The original paper appears to not be clear on this. We only have 2 records in our DB that have pH without other ABG values, and for one the pH score is 0, so Julie and Tina didn't notice this difference until now. Interpretations are:
    • reasoning to include in sum, Julie's interpretation: "under DEVELOPMENT OF APACHE “ …and serum pH was retained in preference to bicarbonate”"
    • reasoning to exclude it, Tina's interpretation: Paper said “Serum HCO2 … [Not preferred, use if no ABGs]”. So, any ABGs missing, I use SerCO2 instead.
  • We flipped a coin; we will go Julie's way :-) Ttenbergen 10:57, 2023 January 11 (CST)
  • Tina emailed Julie to confirm if she does a score-all, or ((score SerCO2) or (FIO2, PO2, CO2))+pH Ttenbergen 14:08, 2023 January 11 (CST)
    		•
    APACHE Acute Diagnoses
  • I will need to re-think how these are documented on the wiki as well, as the current schema was based on individual dxs meeting criteria and this is quite different. Ttenbergen 10:39, 2022 November 15 (CST)
    		•
    Template:Location dropdown cleanup
  • Since no one person knows when an s_dispo item is no longer used on any laptop. Made CFE query z_s_dispo_inactivatable to check. Should check that query occasionally to review if other things can be cleaned up.
    		•  2022-03-05
    "cannot open any more tables" in Access
  • Wasn't able to find what code tops out the tables, need to review further.
  • When fixed, update PL 2Phin Fake or Blank and Generating PseudoPHINs to take out instructions about this bug
    		•  2022-12-07
    Eliminating distinction between different ward types CTU vs NTU - we decided at task that we wanted to eliminate the distinction. A lot of things are part of their network of information, so we will need to work out the details above before we can move ahead.
  • I believe it was only related to Transfer Ready DtTm field between CTU and NTU not eliminate the concept. Medicine program would have to weigh in. Trish Ostryzniuk 16:11, 2018 July 30 (CDT)
    • I seem to remember the reason to stop doing this also involved that we have more and more locations that don't fall into a clean place. For now we pretend we can give medicine this data, but is it true and meaningful? Ttenbergen 15:51, 2018 July 31 (CDT)
      • Allan will contact the medicine stakeholders about eliminating this distinction. Will email Mary-Ann Lynch, VanAmeyde, Griffin. Ttenbergen 12:18, 2019 January 24 (CST)
        • pinged again for Allan to Follow-up. Ttenbergen 13:44, 2019 February 25 (CST)
  • AG REPLY: DONE. NOBODY is using or seeking this info. So let's stop collecting it.
    		•
    APACHE Acute Diagnoses just Tina's working notes:

    Scenarios:

    • one of a * of ICD10s
    • one of a * of ICD10s AND one of a * of ICD10s
    • one of a * of ICD10s AND an ICD10 with a word in it
    • one of a * of ICD10s AND one of a * of CCIs
    • one of a * of CCIs
    • two or more of a * of ICD10s

    AND any admit procedure is EITHER: (a) of the form 1.AA.xx, 1.AB.xx, 1.AC.xx, 1.AE.xx, 1.AD.xx, 1.AG.xx, 1.AJ.xx, 1.AK.xx, 1.AN.xx, 1.AP.xx

    where “xx” = any of 13, 51, 52, 53, 56, 57, 59, 72, 76, 80, 87, 89, 90, 91

    or (b) 2.AA.71.yy, 2.AB.71.yy, 2.AC.71.yy, 2.AE.71.yy, 2.AD.71.yy, 2.AG.71.yy, 2.AJ.71.yy, 2.AK.71.yy, 2.AN.71.yy, 2.AP.71.yy

    where “yy” = any of 70.^, 71.^
    • one of a * of ICD10s AND (one of * of CCI1 and a * of CCI2)
      • might be able to do a pattern recognition on that? Or a regular expression?
    STB-L2HA locationData
  • make sure this will be integrated
    		•  2022-06-28
    S LocationData table locationData
  • No longer applicable, we discussed today that we will need multiple start and end dates and that it maybe should be stored on wiki.

    • ---

    • _dev_CCMDB - the process to import from wiki should run a consistency check on the start and end dates to ensure there is no overlap of same attribute
    • _dev_CFE - include this in the import of s_ tables at startup; there was a second s_ table to pull into CFE, emailed Julie for which one
    		 2022-02-10
    ECIP wiki housekeeping
  • Cleanup after 2020-10 EMIP changes: needs to be cleaned out / integrated with EMIP and possibly Using Cognos2 to keep track of patients. Emailed Steph to see if she can help me with this. Ttenbergen 09:48, 2021 July 15 (CDT)
    		•  2021-08-10
    Adding a CCI or ICD10 entry in CFE wiki housekeeping
  • this may have been automated; if so it's out of date. either way, it should be linked in better.
    		•  2022-06-16
    Change of remaining location names from "our" names to EPR/Cognos names wiki housekeeping

    Need to clean this up

    • * What happens to the ICU Previous Location, Pre-admit Inpatient Institution, Dispo or even Service Location - should they be changed too by the new COGNOS ICU locations? Example current STB_ACCU is SBGH-CCUO in COGNOS, STB_CICU is SBGH_ICCS, STB_MICU is SBGH_ICMS. Should the old labels remain? We need to think hard for its implications to queries of linking and/or matching tables before implementing any change. --JMojica 16:33, 2022 February 2 (CST)
      • It would be nice to have this consistent, and yet you are correct that this would tie into a lot of things. I think the benefits of making it consistent win out, though especially when it comes to also thinking about this in terms of that metadata we discussed the other day. Even if we keep the (possibly identical) data in both s_tmp and s_dispo for now, we would then be able to use that metadata table for both. This would require thinking through the details. Julie, I think it only involves you and me, so maybe we should discuss at our wiki meetings? Ttenbergen 13:44, 2022 February 8 (CST)
        • Julie and Tina discussed:
    • We use the 4 fields Previous Location, Pre-admit Inpatient Institution, Dispo and Service/Location also to map patient flow between laptops, and we very much don't use Cognos values for this (e.g. HSC_Med). We need to retain this ability to use the entries for linking but would also make them the same as Cognos where possible. So we need to keep our "own" values for this for locations where we collect.
    • We decided to use manually split CC entries e.g. HSC_MICU vs HSC_SICU since Julie reports in those increments, ie it is hard to pull apart a stay in two ICU types if it is collected as one record. We don't want to lose that.
    • We would still like to change these own values to the "modern" values where we use legacy terms, eg. STB ICMS vs STB MICU. As long as we make a clean transition between old and new, or change all old, that should not be a problem, but we need to account for it.
    • We could use the Cognos values for all places where we don't collect, e.g. if a pt comes from Ward HSC_A1 and Cognos lists that as HSC-GA1, we could just enter that. However, for locations we don't collect we currently aggregate this to HSC_ward. Do we want the extra detail? It would be easier to enter but might be harder to interpret and possibly even harder to work with for collectors.
    • If we want to keep our proprietary value for locations where we collect, and keep aggregate ones for locations where we don't collect, I am not sure which locations that then leaves where we would use the Cognos values?
        • Julie, do you agree to that summary? If so, there may be nothing to discuss with Lisa, since we will need to leave this as is. If I am missing something pls update and then pass on to Lisa for her take. Ttenbergen 16:56, 2022 March 23 (CDT)
          • agree. pass to lisa. --JMojica 15:27, 2022 June 8 (CDT)
    • I think this is no longer an issue, unless we are looking to change how we collect this, which I am not in favor of Lisa Kaita 12:23, 2022 August 24 (CDT)
    		 2022-08-24
    Template:ICD10 Guideline Signs Symptoms Test Results not needed when cause known wiki housekeeping
  • Apply template to symptoms, physical exam findings, and radiologic findings, but NOT to laboratory findings.
    • I don't know which those would be. If we go through with this definition we should just stick them into a :Category:Lab Result or similar. Category:Testing also contains non-lab findings. Where would this leave things like Fecal occult blood test, positive? The "What links here" link on the left would show all that currently links to this page.
    • R71-R89 inclusive
    		•  2022-02-09
    User:Ttenbergen/Relationship Diagram wiki housekeeping
  • Considering Extension Mermaid and Extension FlexDiagram. Both have bugs in how they implement the ER Diagram for now. Need to review.
    • Scheduled Tasks wiki housekeeping
  • Do we still schedule Backup Checker?
    • No, I remembered it was run through my desk top computer, not now anymore. PTorres 14:08, 2022 March 17 (CDT)
      • no longer doing either of these as scheduled tasks, Tina needs to clean up the documentation. PTorres 15:05, 2022 March 17 (CDT)
    		•  2022-03-17
    Change of remaining location names from "our" names to EPR/Cognos names wiki housekeeping

    need to make sure it is documented somewhere that Julie will group the old and new versions of htese via the Centre column in s_dispo table... where would I document that? Ttenbergen 16:56, 2022 March 23 (CDT)

    • Tina, in the s_dispo, I also use the column ward to group the different labels referring to the same ward/unit and column centre for the order sequence of these ward/unit in the report. --JMojica 15:23, 2022 March 25 (CDT)
    		 2022-08-24
    Template:Drugs included wiki housekeeping
  • need to confirm these are applied to all relevant articles
    		•  2021-11-25
    Drug-induced immunosuppression wiki_housekeeping
  • Emailed queries to Pagasa to translate all instances of this code to Past history of immunosuppressive drugs or corticosteroids. When done I will need to clean up the wiki for this. Ttenbergen 11:41, 2022 July 6 (CDT)
    		•  2022-07-13
    EPR Analytics z
  • decide if it is time to ask the powers-that-be about this again
    		•  2022-01-01
    Questioning data back to collectors z
  • Possible future scenario: The data processor puts the concern into the Notes field and sets the RecordStatus field to "questioned". Next time the collector sends, the record is returned to the laptop by a series of queries. The collector updates the record, sets it to "complete" and sends it in with the next round of sends, at which time it will be processed like any other record.

    • This process is more automated and would need to be validated before we could implement. It would be the least work for all involved, though, I think.

    We keep discussing this, talked about it again today. Ttenbergen 17:44, 2016 December 1 (CST)
    Retrieved from "https://ccmdb.kuality.ca/index.php?title=User:Ttenbergen/questions_for_tina&oldid=157070"