CCMDB Wiki

User:Ttenbergen/questions for tina

< User:Ttenbergen

__NOCACHE__

Questions

edit page question ModDate
edit page question ModDate
edit Overstay2 Screening Reports
  • According to the draft SOPs we are to provide communication of the results as below. Andrea Thiessen explained that they would want something like a list split by colour. Then people would start manually populating other documents with this. I should follow up to determine the details and possibly set up a better way.
  • 2025-07-03 TT emailed to Katherine Graham and Kathy Kwiatkowski how they will use it (include Andrea Thiessen)
 2025-09-06 12:28:06 PM
edit Overstay2 Screening Reports
  • The DPST SOP (live temp limited access, also see uploaded copy, might be outdated) says that we will provide a report or patient colours. The details need to still be worked out.
      • I need to work with Andrea and Katherine Graham on overall reporting, so please don't do a separate approach on this. Separate emails are awkward for them, I asked to do it like that for now because it's low effort on collector part and you said you are already overwhelmed by all the changes. Ttenbergen 12:12, 3 July 2025 (CDT)
  • If this remains in email form there may end up being a mailing list for this.

    • Once the final reports are figured out collectors may or may not be involved in providing these. Ttenbergen 00:11, 2 July 2025 (CDT)

      • As of July25,2025 collectors were advised they can stop sending the automatically generated emails to Andrea, so we have, TT removed this function Sept 5, 2025 Lisa Kaita 07:28, 6 September 2025 (CDT)
    		 2025-09-06 12:28:06 PM
    edit Re-analysis and generation of Overstay2 model still needs to be set up by Tina... 2025-08-12 8:43:59 PM
    edit Postal Code field do we have a page for that to also include instructions about province etc. like we have for homeless... 2025-08-11 2:48:50 PM
    edit Postal Code field
  • this is related to Minimal Data Set and when it's used... do we document this as a concept?
    		•  2025-08-11 2:48:50 PM
    edit Chronic Health Facility
  • This issue raised a problem with medicine data recently, and we will review again if this needs to be coded more granular after all,
  • dicussed at JALT June 25, 2025 while Bojan would like this it is not possible to keep track of unit changes and not always easy to tell which unit they arrive from so leave a Riverview and Deer Lodge (DLC), with the exception of the PCH units in each facility.Lisa Kaita 14:52, 25 June 2025 (CDT)
    		•  2025-08-06 5:02:14 AM
    edit Chronic Health Facility We have discussed lately that we might want to become more nuanced about some chronic care locations (Deer Lodge (DLC) and Riverview). I have removed the details from the above linked fields and consolidated here. Once this page is cleaned up this discussion entry can be removed.
  • Discussed at
    		• 2025-08-06 5:02:14 AM
    edit Chronic Health Facility
  • review, that might need to be consolidated with this page as well.
    		•  2025-08-06 5:02:14 AM
    edit Chronic Health Facility
  • These should be made consistent with [[Template:PCH Riverview Deer Lodge (DLC)]] and should probably use that template to enforce consistent use. Ttenbergen 14:23, 2024 October 16 (CDT)
    • and I have lost track of the details Ttenbergen 10:45, 2024 November 1 (CDT)
      • There might be an easy way out of this question. We now only have one awaiting code; if waiting for any of them qualifies for this code then we may not need to know about the level of care. But then again, some of those sites also have acute/LAU type settings so we may need to figure this out after all...Ttenbergen 20:27, 2024 December 11 (CST)
  • that template does not exist or I can't find it Lisa Kaita 14:56, 25 June 2025 (CDT)
    		•  2025-08-06 5:02:14 AM
    edit Chronic Health Facility
  • Discussed this at JALT Meeting - Rolling Agenda and Minutes 2025#JALT 2025-03-11 but I don't remember if we came to an answer or next step. Just found a note to add that we will also need to decide if any of these are in-patient locations. This would make them collectable as Pre-admit Inpatient Institution, and is relevant as per Pre-admit Inpatient Institution field#Data Use / Purpose.
  • are you referring to PCH's because they are not inpt locations or are you referring to chronic health facilities? Lisa Kaita 14:52, 25 June 2025 (CDT)
    		•  2025-08-06 5:02:14 AM
    edit Data definition for factor candidates for the Overstay2 project Integrate these better
  • re pre admit for outside Winnipeg facility discussion, change from getting from Previous Location only to getting it from both Previous Location and Pre-admit Inpatient Institution; this was missed before because we based the initial fields on the last overstay project, and back then these two fields were still combined
  • re-institute amputation; before we were only looking at the CCI code, but we should consider Past history, loss of limb(s) as well
    		•  2025-07-31 2:29:57 PM
    edit Query check ACP Status Collection
  • add "date of first should be before last"
    		•  2025-07-30 4:55:28 PM
    edit Geri Rehab this is one of the things we needed to discuss further, currently we capture RR5 as HSC_ward, but it is a combination of spinal cord rehab, NMSK rehab, amputation rehab, Riverview has stroke rehab, Deer Lodge (DLC) has Geri rehab, If we are capturing these rehab wards for CGH, SOGH and VGH should we not be capturing this for all dispo locations that are rehab? Lisa Kaita 13:11, 8 April 2025 (CDT) 2025-07-30 4:33:58 PM
    edit DSM Lab Extract
  • A possibility to change the current Chart entry to be the same with SH format (see #DSM Inclusion Criteria/ Process for reason why in details).
    		•  2025-07-30 4:32:23 PM
    edit Selkirk Mental Health Centre
  • I am unclear with these instructions, if indirect code as applicable? if we are using chronic care facility, like we do for Riverview and Deer Lodge (DLC), we have Riverview as an option for if they arrive as a direct or indirect, but now Deer Lodge (DLC) and Selkirk mental health are not an option, shouldn't we be treating these all the same? There is a question on the Chronic Health Facility Lisa Kaita 17:50, 16 June 2025 (CDT)
    		• 2025-07-23 7:13:07 PM
    edit Link suspect visitAdmitDtTm mult to-from-home query
  • implement this
  • with L_Problems tie in
  • tell Pagasa it exists
    		•  2025-07-23 4:15:01 AM
    edit Community Nursing Home Location Helper flagging this because it's a close sibling to the idea of getting a listing of shelter PCs to cross check (or facilitate entering maybe? homeless status in Pre acute living situation field. See Community and Long Term Care Master List. 2025-07-18 10:35:02 PM
    edit Unique CFE module fill in 2025-06-30 4:57:40 PM
    edit Query s tmp check combined Boarding Loc and TransferReadyDtTm
  • This doesn't catch duplicate Transfer Ready DtTm tmp entry for Boarding Loc on incompletes. That is probably fine since we don't use the incompletes, but it could be added the next time the check is worked on anyway.
    		•  2025-06-27 2:08:32 PM
    edit Awaiting/delayed transfer to long-term care/PCH inside or outside of Winnipeg
  • I just saw this line, its probably been there for a while, but just thinking that in our definition of community living with support, in Pre acute living situation, we include assisted living, supportive housing, AIA, lennox bell, and 1010 Sinclair, we currently do not use this code for these dispo locations, should we include them or we should rethink this Lisa Kaita 21:24, 10 June 2025 (CDT)
    • I actually just don't understand what this means... is the full statement "This includes those living in a community facility with support and being panelled for PCH" or what? In any case, yes, judging by how often this comes up in a search, we should likely make a page for community facility with support and store the details there to be back-linkable if we mess with the concept anywhere. Possibly that should be a template:community facility with support instead or in addition, depending on the details we need. But have a look at the search link above and let's make sure we pick the right solution that can tie in to everywhere the concept is used. Ttenbergen 00:42, 11 June 2025 (CDT)
    		•  2025-06-11 5:43:19 AM
    edit LAU Public Trustee I also used this field for FORM 21 but documented it in the Q column, should we take this out? I think there were a handful of these Lisa Kaita 07:27, 11 April 2025 (CDT) 2025-05-03 5:39:57 AM
    edit High-Obs Wards Tina to add. 2025-03-20 5:17:20 PM
    edit Overstay2 data processing and reporting in CFE
  • add functions/subs when I finalize this
    		•  2025-02-23 10:13:18 PM
    edit PowerBI Data Model for CCMDB ER Delay and Overstay
  • Need to make sure I do things this way and include this in the right pages, possibly Change from Service Location to Service, Boarding Loc and Transfer Ready DtTm tmp entry but a lot of other pages touch on this, so maybe it needs to be a template? It may not be consistent everywhere:

    • Note from email from Julie 2024-20-24:

    I do not use any cut-off e.g. 2020-10-15 because the tmp has been populated by boarding data since July 2018 for ICU and Sept 2019 for Med. The cut-off Oct 2020 Patient Follow only applies for tmp Service but not for tmp Boarding loc. By the way. the patient follow started early at Grace Oct 1, 2020 (they piloted it), while HSC and STB started Oct15, 2020. Similar with EMIPs, I have two sources of ER-delay namely 1. from Accept and Arrive 2. from Tmp : first boarding dttm and second boarding dttm. If both have values, I use the one from the tmp source.    		 2024-12-12 12:11:55 AM
    edit Created TransferReady query Still need to import this into master CFE, the version I have right now is messed up. Here it is: 2024-11-22 6:08:24 AM
    edit Query check has transfer ready date or checkbox
    • This check doesn't seem to catch when a time is entered without a date. It would be good to update that. Don't have time right now, so leaving a note. Email exchange 2024-11-14. Ttenbergen 12:12, 2024 November 15 (CST)
    		 2024-11-15 6:12:47 PM

    To dos

    edit wiki page question action ModDate DESC
    edit wiki page question action ModDate DESC
    edit EPR Analytics z
    • decide if it is time to ask the powers-that-be about this again
    		 2022-01-01 2022-02-18 4:19:30 AM
    edit 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)
    		•  2022-08-10 7:29:46 PM
    edit 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 2022-08-10 7:29:46 PM
    edit Query maintenance s tmp deletables _regular * this should be done regularly, maybe every 6 months 2023-02-10 2022-08-10 7:41:02 PM
    edit 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?
    		 2022-11-15 4:39:51 PM
    edit 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)
    		•  2022-11-15 4:39:51 PM
    edit 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 2022-11-29 7:30:20 PM
    edit "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 2022-12-07 6:15:25 PM
    edit Re-importing CCI and IDC10 categories from wiki to CCMDB.accdb The query to re-populate this one is now incomplete; don't delete it, just review the output of the re-generating query against this one until fixed; deleting and re-importing breaks TISS and other entry functionatlity. 2023-05-02 9:05:58 PM
    edit HSC-GA7S
  • I came across this issue because Julie's data and mine had different Transfer Delay when this location was involved. This seems to mean that Julie's doesn't use the table to designate level of care. That could become a source of inconsistency. Should we do this the same way? What is the obstacle? Ttenbergen 13:45, 2022 October 13 (CDT)
    • I do not use the s_level_of_care table for the reason that the same location can be assigned with more than one level of care either CC or HOBS or regular. I simplify the process in my program. For Critical Care, since each record is based by unit, if the patient stays in more than one boarding loc i.e. ER/PACU/Home unit/offservice unit, I consider them under the same level of care. Ex an IICU pt staying at SICU/GGA7/GA7S have same level of care, an ICMS patient staying at L2ME(IMCU)/L2HA(Recovery)/home unit/offunit(ACCU/ICCS) are under same level of care. For Medicine, in my program, for each record and boarding locations, I just need to distinguish the HOBS locations (e.g. HSC-GH7S,HSC_HOBS,HSC_H4H,HSC_B2 (only from dt 4/7/2020 to 8/7/2020) and STB_IMCU) and others not specified as HOBS are treated as regular wards (no need to spell out the individual names and no worry if new location comes up which are not yet added in the s_level_of_care table). --JMojica 16:33, 2022 October 14 (CDT)
    		•  2023-05-03 9:01:42 PM
    edit HSC-GA7S
  • Is this a unit we currently collect on? What is it now? Ttenbergen 13:45, 2022 October 13 (CDT)
    • It is currently empty, I think it is used as contingency beds Lisa Kaita 12:19, 2022 October 20 (CDT)
      • Yes, it seems to be a wildcard place. So we need to document on this page when we find out a change in function, since it affects how we categorize admissions. EG at some point this was an ICU, at another a Med ward (possibly high obs). Ttenbergen 17:31, 2022 November 3 (CDT)
    		•  2023-05-03 9:01:42 PM
    edit HSC-GA7S
  • This same location has different levels of care over time. Currently the s_level_of_care table can only accommodate one, ie changes over time can't be included in it. My first thought was to include start and end times for this, but what if patients from both programs were boarding on a given unit at the same time? Can that happen? The very concept that these are boarding locations kind of means crazy things could go on. How do we best accommodate this? Would we always know as a physical location (especially a boarding one) changes LOC? Ttenbergen 13:53, 2022 October 13 (CDT)
    • discussed 10:59, 2023 April 19 (CDT), we need to be able to assign different values over time. Ttenbergen 10:59, 2023 April 19 (CDT)
    		 2023-05-03 9:01:42 PM
    edit 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
    • None left as of 2023-05-04, field can be removed...
      • remove from sending
      • remove from CCMDB_data
    		 2023-05-04 2023-05-04 10:18:08 PM
    edit Transfusion of plasma products
  • review instructions once FFP is expected to be depleted, Sept 2023
    		•  2023-09-30 2023-05-17 6:56:02 PM
    edit 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.
    		•  2023-05-17 9:25:08 PM
    edit Query check tmp 2 BL TR S same tm do we have a query where two consecutive date_times have the same boarding loc? When checking ER_delay, found 2 cases with 2 ER entries which when re-checked was typo error on the second location. --JMojica 13:44, 2024 October 24 (CDT) 2024-10-24 6:44:46 PM
    edit Accept DtTm field _ccmdb_dev
  • Field is legacy; once no longer used, remove it from sending and then from ccmdb_data.
    • remove from sending
    • remove from CCMDB_data
    		•  2023-05-04 2024-11-17 12:36:05 AM
    edit Template:Location dropdown cleanup _regular
  • 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 2025-03-06 5:12:06 PM
    edit 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 2025-03-20 5:17:20 PM
    edit STB-L2HA locationData
  • make sure this will be integrated
    		•  2022-06-28 2025-03-20 5:25:55 PM
    edit Palliative patient
  • add this properly to the relevant report/indicator templates.
    		•  2025-06-11 2025-06-11 10:34:51 PM
    edit 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 2025-06-20 7:25:36 PM
    edit Cross Check Engine _dev_CCMDB
  • implement better cross-check triggering
    		•  2022-04-27 2025-06-20 7:27:08 PM
    edit 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.
    		•  2025-06-20 7:27:10 PM
    edit Charlson Comorbidity Index
  • I need to confirm this is not in any of our VBA code or queries
  • I implemented it in CCMDB (not CFE for some reason) "L_ICD10_Charlson_Agepts" query.
    		•  2025-06-19 2025-06-30 6:12:25 AM
    edit Query cardiac arrest throughout admission
  • Lisa flagged that, if we do this for Cardiac Arrest, we should really do it for other dxs as well. And if we did that, it could result in a lot of work since it would need to be mediated by Pagasa for now. So we decided to see where the SF implementation goes and review the definition of this check once we have a centralized tool where the data collector would not need to mediate this. Ttenbergen 15:43, 2023 July 13 (CDT)
    • Now that SF is on hold, leave this as a to do?Lisa Kaita 14:42, 2024 October 2 (CDT)
      • I am OK with turning this into a to-do if SF is on hold for the forseeable future. Ttenbergen 12:46, 2024 October 3 (CDT)
    		•  2024-10-02 2025-07-23 4:15:04 AM
    edit 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 2025-07-23 7:52:09 PM
    edit 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 2025-07-23 7:52:49 PM
    edit 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 2025-07-23 7:52:49 PM
    edit 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
    		•  2023-07-13 2025-07-23 9:38:28 PM
    edit R Filter Field _CFE_Data_reconsolidate
  • make sure the remaining data transitions are complete:
  • and eliminate this field
    		•  2023-07-13 2025-07-23 9:38:28 PM
    edit 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 2025-07-30 4:29:40 PM
    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.
    		•  2023-05-04 2025-07-30 4:32:02 PM
    edit Centralized data.accdb Requested Changes _dev_centralized_data
  • dxs rank
  • remove empty L_Aux table
    		•  2023-05-09 2025-07-30 4:32:26 PM
    edit Centralized data front end.accdb Change Request _dev_CFE
  • Linked pairs, better storage
    		•  2025-07-30 4:32:55 PM
    edit Centralized data front end.accdb Change Request _dev_CFE
  • CCI and ICD10 make button for Pagasa
    		•  2025-07-30 4:32:55 PM
    edit 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 2025-07-30 4:34:20 PM
    edit 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 2025-07-30 4:34:20 PM
    edit 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 2025-07-30 4:35:00 PM
    edit 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)    		 2025-07-30 4:55:38 PM
    edit Query check long transfer delay
    • At the meeting about cross checks (a long time ago) it was decided to change the cut-off to SD*3; if we want to proceed with this check, I will need values for that. Ttenbergen 23:08, 2020 October 15 (CDT)
    		2025-07-30 4:55:46 PM
    edit Query check long transfer delay _after
  • This will need to be implemented when the 3SD is available.
    		•  2022-08-04 2025-07-30 4:55:46 PM
    edit 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.
    		 2025-07-30 4:56:52 PM
    edit 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 2025-07-30 5:01:23 PM
    edit S Priorities table _dev_CCMDB
  • Is this even still used or can it be removed?
    		•  2023-05-17 2025-07-30 5:05:16 PM
    edit S AllDiagnoses table
  • This table could be moved to CFE with S Pathogens table since it is no longer used in CCMDB.accdb.
    		•  2023-05-17 2025-07-30 5:11:35 PM
    edit 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.
    		•  2025-07-30 5:12:27 PM
    edit S Pathogens table
  • This table could be moved to CFE with S AllDiagnoses table since it is no longer used in CCMDB.accdb.
    		•  2023-05-17 2025-07-30 5:12:46 PM
    edit Category:Data Semantics
  • There are some pages with the word "change" in the title that address major changes in data encoding; those should be added to this category.
    		•  2025-08-14 2025-08-14 10:42:45 PM
    edit 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 2025-09-26 10:39:05 PM
    edit 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 2025-09-27 2:12:27 AM
    edit Query Mgmt Collector Admission Count _Dev_CFE mgmt queries
  • This query can be removed, no longer relevant after PatientFollow Project.
    		•  2025-09-29 6:48:07 AM
    Retrieved from "https://ccmdb.kuality.ca/index.php?title=User:Ttenbergen/questions_for_tina&oldid=167441"