User:Ttenbergen/questions for tina

Questions

Toggle columns: ModDate

edit	page	question	ModDate
edit	page	question	ModDate
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	Project Overstay2	{{{1}}}	2025-01-24 10:57:19 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).	2023-07-05 5:36:20 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)	2023-05-04 5:03:24 PM
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
edit	Project Overstay2	OutsideWPG - I have used Previous Location because Leigh Anne specified the patient came from a facility outside of Winnipeg. MB - I would think Leigh Anne had used the Province because the data set has no Postal Code yet I just checked the query check_from_out_of_town I used to derive this and it only considered Pre-admit Inpatient Institution having geog like "out-of*"! Ttenbergen 16:57, 24 January 2025 (CST) Will ask Dr. Roberts what this was all about to better understand what to use now. Specifically, if we use previous location, would we only care about hospitals, or also e.g. nursing stations, PCH, hospice, "unknown/other" loc_types. Ttenbergen 16:51, 24 January 2025 (CST)	2025-01-24 10:57:19 PM
edit	Pre-admit Inpatient Institution field	Hey T/Julie, I recently admitted a pt from day sx and did as the wiki instructions on Previous Location and put HSC_ward, which according to the article is not an inpt location, so put NA for pre admit pt institution, however I got an error saying previous loc and pre-admit must be the same if coming from an inpt location. Should we change the instruction and use HSC ambulatory care instead of HSC ward?, or do we need to rethink this? Lisa Kaita 13:04, 2024 October 16 (CDT) Yes I agree, Ambulatory care seems to be the closest scenario for day-surgery locations. --JMojica 13:38, 2024 October 16 (CDT)	2024-10-16 7:25:09 PM
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	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	2023-07-13
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
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
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
R Filter Field	_CFE_Data_reconsolidate make sure the remaining data transitions are complete: Project Legacy Co-managed Project Legacy HSC CCU Loc and eliminate this field	2023-07-13
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
Cross Check Engine	_dev_CCMDB implement better cross-check triggering	2022-04-27
S Priorities table	_dev_CCMDB Is this even still used or can it be removed?	2023-05-17
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
Centralized data.mdb Requested Changes	_dev_centralized_data dxs rank remove empty L_Aux table	2023-05-09
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
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.
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.
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
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
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
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.
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 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) the MED above has to changed. I will do a calculation of recent data based on the new process using Mean+3SD. --JMojica 15:16, 2022 February 16 (CST) I am waiting for your Created Variables CC 2021 table and Created TransferReady query to be done and from that table, the calculation of mean +3 SD will be derived. --JMojica 09:41, 2022 June 7 (CDT) Created Variables CC 2021 table is now done. Ttenbergen 14:34, 2022 June 30 (CDT) new queries are live now so this could proceed. Ttenbergen 16:46, 2023 April 19 (CDT) new queries are live but need to be validated before we do this. Ttenbergen 16:08, 2023 May 3 (CDT)
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
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)
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)
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)
Transfusion of plasma products	review instructions once FFP is expected to be depleted, Sept 2023	2023-09-30
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) In the meantime I am changing the LOC for this location to 50 in s_level_of_care table since I think that table is only used by the queries that derive Transfer Delay. Ttenbergen 13:45, 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)
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
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
"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.
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)
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
Query NDC Bad Postal Code	PWC 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
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.
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)