|
|
| Line 1: |
Line 1: |
| ''see the [[:Category: Development Documentation | Development Documentation Category]] for other development logs'' | | ''see the [[:Category: Development Documentation | Development Documentation Category]] for other development logs'' |
| | |
| | == Requests == |
| | ==== after fixing the CCI page names on wiki, '''add wiki link for CCI codes in CCMDB.accdb''' ==== |
|
| |
|
| == Bug Fixes == | | === screen refresh reductions === |
| * see [[Out of Memory Error]]
| | As part of troubleshooting Con's blinky screen Brendan suggested the following: |
| * see also [[:Category:Bugs]]
| |
|
| |
|
| * ApPts in BP and ABG chooser update for whole column rather than just edited line (or so, something is wrong)
| | There’s code you can put in, I forget what the commands actually are, but it turns off the screen refresh during functions so the user doesn’t see what’s happening. You’d turn the refresh off before the function starts, they’ll see a static screen until you tell it to turn the refresh on, where the screen will then load just one time and all of the new info, all the rows, any formatting, or populating, etc.. is done. Instead of refreshing 10 or 20 times, once for each row. |
| * make priority check in drugs so it only checks when complete-checking, not upon every entry.
| |
| | |
| * long-stay error pushes off screen other errors, needs to happen later [[User:Ttenbergen|Ttenbergen]] 09:41, 31 May 2011 (CDT)
| |
| * XBR/BRR check doesn't yellow the field [[User:Ttenbergen|Ttenbergen]] 09:41, 31 May 2011 (CDT)
| |
| | |
| * some Apache errors still remain yellow from one patient to the next [[User:Ttenbergen|Ttenbergen]] 16:15, 2 June 2011 (CDT)
| |
| * "WBC decimal points error" - I wrote this in a meeting with Julie and Trish but can't remember what it is about; can anyone fill in? {{discussion}} [[User:Ttenbergen|Ttenbergen]] 10:49, 3 June 2011 (CDT)
| |
| | |
| * set an actual set of BPs as midpoint for meanBP, rather than the decimal-pointed meanBP. [[User:Ttenbergen|Ttenbergen]] 10:49, 3 June 2011 (CDT)
| |
| | |
| == Additions required ==
| |
|
| |
|
| | == integrity checks checklist == |
| | {{#ask: [[DICStatus::ready to implement]][[DICApp::CCMDB.accdb]] OR [[DICStatus::needs review]][[DICApp::CCMDB.accdb]] |
| | |?DICStatus = Status |
| | |limit=20 |
| | |format=broadtable |
| | |class=sortable wikitable smwtable |
| | |default=No cross checks ready to implement |
| | }} |
|
| |
|
| | == Bug Fixes == |
| | ''see [[:Category:Bugs]] and especially [[:Category:Bugs needing input]] for bugs with their own article'' |
| | {{#ask: [[Category:Bugs]] [[Category:Bugs needing input]] |
| | |?DICStatus = Status |
| | |?Modification date |
| | |sort=Modification date |
| | |order=ascending |
| | |limit=20 |
| | |format=broadtable |
| | |link=all |
| | |class=sortable wikitable smwtable |
| | }} |
|
| |
|
| ==Changes Under Discussion == | | == Next Round of Data Changes == |
| These requested changes can not be processed until the questions about them have been answered. Wherever possible the discussion should conclude in the home article of the topic. If a topic has no home article, it can be listed here.
| | Flag this in the relevant pages as follows so it lists properly in [[To do list]]. See there for actual changes requested. |
|
| |
|
| === Integrity rule for [[ER Wait]] dates in TMP file=== | | { {Todo |
| will need to bring in details from our email exchanges. [[User:Ttenbergen|Ttenbergen]] 17:56, 2 June 2011 (CDT)
| | | who = Tina |
| | | todo_added = 2021-07-21 |
| | | todo_action = |
| | | question = Dev_CCMDB_Data / Dev_CCMDB depending on if CCMDB needs update first. |
| | <provide details of change> |
| | }} |
|
| |
|
| === QA_Infection === | | == Bugs that need input == |
| * see [[QA_Infection#Data Integrity Rules Under Discussion ]]
| | In order to troubleshoot bugs in the program we need to know how they happen. Any further feedback on these bugs might be the piece of the puzzle that allows me to fix the bug. If you find a new bug, you please document it. |
| | {{#ask: [[Category:Bugs needing input]] |
| | |?Modification date |
| | |default=No corresponding old article found |
| | |format=broadtable |
| | |limit=100 |
| | |link=all |
| | |headers=show}} |
|
| |
|
| ===ARF=== | | === renal task checks === |
| *Could the ARF field be changed to a "yes"/"no" or "meets"/"does not meet" the criteria, rather than the current 'check' box which is checked only if the pt meets the criteria for ARF? The current way of collecting this info can not differentiate between my having forgotten to address the issue vs the patient not having ARF. [[User:Mlaporte|Mlaporte]] 21:24, 4 March 2011 (CST) | | * [[Check Renal Tasks]] |
| | There are some possible changes identified that either need to be flagged as needing to be done, or where there is still a discussion going on. |
| | Also related to this: |
| | * confirm "if LOS <3 days and 350 in admit or acq or if 351 in com orbit, then a dialysis TASK item is ok not to be marked." |
| | ** right now this could go through |
| | ** this and related checks are all stuck in [[Check Renal Tasks]] questions |
| | ** this also shows up in [[Change_Priorities#Need_and_NDC:_for_ARF.2C_CRF_.26_Task_dialysis]] |
| | === Pharmacy reference === |
| | * '''reference sheet''' - some suggested we add a reference sheet. I could make a button on that screen to bring up a reference sheet. Problem is that would be at least the ''third'' copy of this information, leading to problems maintaining consistency. I would be willing to do it if we change the table with the info on the wiki to a plain-text formatted table that I can directly copy-and-paste into Access, e.g. something like |
| | --------------------- |
| | | test | second test| |
| | --------------------- |
| | | blah | blah blah | |
| | --------------------- |
|
| |
|
| === Full Apache Score ===
| | * If someone could set up the table on the wiki I will make a form with the content in the app. Any volunteers? I could add this to the next version easily. Ttenbergen 16:41, 2013 April 24 (EDT) |
| Add full apache score to the Viewer form
| | ** No news in about a month. If anyone is interested in making that list, let me know and I'll put it into the CCMDB.accdb. |
| * That one would need thorough testing to make sure I got the score right, e.g. enter 10 patients and check if their apache scores in ccmdb are what you would have calculated. Any volunteers for the testing? If it won't be validated I'd rather not add this to confuse anyone. [[User:Ttenbergen|Ttenbergen]] 11:05, 9 June 2010 (CDT)
| | *** No one ever volunteered to provide the sheet, so taking out the question. If someone is willing to work on this, please add a discussion back in. Ttenbergen 19:39, 2019 November 13 (CST) |
| ** Marie Laporte offered to help with this. I will let her know once I have implemented this. [[User:Ttenbergen|Ttenbergen]] 16:01, 2 July 2010 (CDT) | |
| {{discussion}}
| |
| * What would this "full apache score" be used for? Much of the diagnostic scoring seems to be documented only in the form of a [http://ltc.umanitoba.ca/ccmdb/images/a/ab/ApacheII_MacroDX_code_map.pdf macro] which will be a mess to decipher and implement in Access. What is the benefit? [[User:Ttenbergen|Ttenbergen]] 10:48, 29 October 2010 (CDT) | |
| * if this is implemented, Marie Laporte offered to help test this (2010-06-21) [[User:Ttenbergen|Ttenbergen]] 10:43, 27 January 2011 (CST)
| |
|
| |
|
| === Help to manage Serial numbers=== | | === apache check no longer yellowing fields === |
| If I understand right data collectors currently collect one or more locations from one or more pools of serial number pools.
| | apache check is no longer yellowing fields[[User:Ttenbergen|Ttenbergen]] 10:09, 10 January 2012 (CST) |
| Details of the serial number system are located in [[Serial number]]. This has been flagged as one reason why people find paper printouts of the most recent patients sent useful.
| | *yes, it is no longer yellowing the field, just the error box below. Can't find trace of the code, and not sure when it was changed. Ponder whether to re-instate, error checking is still being called and still prevents sending... [[User:Ttenbergen|Ttenbergen]] 17:13, 2012 January 31 (CST) |
| | **Do we want to re-implement this? Would take a few days of coding I think, so I haven't done it. Ttenbergen 16:58, 2012 October 1 (CDT) |
| | ***not sure what you mean no longer yellowing fields. Do you mean where there is an error (limit) or missing data that is not yellowing? --[[User:TOstryzniuk|Trish Ostryzniuk]] 19:13, 2013 January 28 (EST) |
| | **** been a while, I'll review and let you know what this is about. Ttenbergen 13:55, 2013 January 29 (EST) |
|
| |
|
| Serial numbers have to be unique for a collection location, so if a ward like HSC_H4H is collected on by multiple collectors then a serial number must never be re-used. One way this is achieved is to assign blocks of numbers for each 100 possible serial numbers to a given collector.
| | == Previous requests that were not made (with reasons) == |
| | === DOB format === |
| | * "when you create a new profile and have to fill in the DOB it is backwards to what is written in the chart, so when we go to enter the DOB we have to stop and think about it to enter it in our computer. It is written in all chart as day/month/year, we use to be able to enter it that way and it would automatically fall into place" - Pat 09:29, 2013 December 19 (CST) |
| | ** there was discussion about doing this and we decided not to to keep dates consistent throughout the program. |
|
| |
|
| A study number must be entered before any other data since access uses it to set the relationships for the data. To accomplish that, function new_pat_id() opens a window requesting the serial number pops up when "add new patient" is clicked on the patient list.
| | === prevent setting recordstatus from sent to complete === |
| | *Prevent RecordStatus of Sent files being changed from Sent to Incomplete if data altered after file sent in[[User:Mlaporte|Mlaporte]] 15:18, 2013 December 16 (CST) |
| | ** actually, need to be able to do that to re-send when needed. |
|
| |
|
| Added question to [[Serial_number#Special-Use_Serial_Numbers]] to find out if any serial numbers need to be "reserved".
| | === sending only lab/pharm sums to centralized_data.mdb === |
| | All the info that is actually needed in centralized is the sum of labs and pharmacy. Was hoping to send only that, but it would complicate synching with collector laptops while adding little value, so not doing that for now. |
| | We could re-visit this if it is a problem, or if those files get unwieldy large. Also, could run a "summarizer" across those files for complete records only. |
| | Will leave alone unless main office really wants this done... Ttenbergen 12:35, 2013 November 11 (CST) |
|
| |
|
| ====Possible Solution====
| |
| The program would provide a default serial number. For locations with only one serial pool, this would be a one-step, transparent process. Collectors with more than one serial number pools would get a dropdown list of possible pools; upon choosing one the program would default to serial (most recent+1). Collectors using only blocks of serial numbers would have to keep track if they are "leaving" their block (e.g. if you are using only 20-39 and the program defaults to 1140, you would have to realize that and change it to 1220).
| |
|
| |
| To accomplish this, the _info table would store
| |
| * variable: serial_pools, value: comma-separated list of wards
| |
| * for each ward, a variable "Serial_pool" & <ward> (e.g. Serial_pool_HSC_H4H) with the most recent value used, updated automatically by the serial wizard
| |
|
| |
| {{discussion}}
| |
| * Any thoughts about this? Do you think it would/wouldn't work or be helpful? Especially, do you think collectors would consistently "catch" the ends of blocks?
| |
| **This may not work as planned as there are times when the data collector assigns a number to a patient file in her log book but is unable to use it immediately and must use numbers out of order (even though the numbers are assigned in the right order).--[[User:CMarks|CMarks]] 08:39, 30 November 2010 (CST)
| |
|
| |
| === Facilitating diagnosis entries ===
| |
| As discussed at the [[Minutes_Team_Meeting_December_1%2C_2010#Restructuring_DX_codes_in_Access |Meeting]] Laura Kolesar is reviewing the names of the diagnoses we use to make it more likely that you get the right one when you start typing. Laura, any progress on this? [[User:Ttenbergen|Ttenbergen]] 19:24, 30 December 2010 (CST)
| |
| **I have put the respiratory system changes on the regional server site for Tina and Trish to review before I proceed with similiar changes to the other systems. When you get a chance, take a look and see what you think. --[[User:LKolesar|LKolesar]] 14:08, 21 January 2011 (CST)
| |
| {{discussion}}
| |
|
| |
| === Extra "pathogens" ===
| |
| As part of an effort to reduce relying on paper notes during collection, Marie brought up the possibility to put ''"waiting for tests"'' and ''"review"'' as options into the pathogen dropdown and to conditional-format the field in orange if they are chosen. Of course, choosing them would also disable checking DX complete.
| |
|
| |
| Some of you are entering [[Unknown Pathogen]], and then re-check all patients with unknown pathogens before sending.
| |
|
| |
| {{Discussion}}
| |
| * Actually, I don't understand how this is better than just leaving the entry as "No Value" until you know what you will put there. This way you would get an error if you tried to set the dx to complete. Can someone explain to me how a different dropdown would improve upon this? I don't see how you use this in the field, so I might be missing something. [[User:Ttenbergen|Ttenbergen]] 19:43, 30 December 2010 (CST)
| |
|
| |
| Also, some of you were addressing here how long they wait for a pathogen which is not immediately available; that is discussed in the article [[Pathogens]]. Here i am wondering if additional options would make collection easier.
| |
|
| |
| === change Final_checks to dropdown to allow for more options once we start to be able to send back data ===
| |
| * add s_FinalChecks, fix all spots that use FinalCheck (or make a function to check it)
| |
|
| |
| == Bugs that need replicating ==
| |
| In order to troubleshoot bugs in the program we need to know how they happen. There are a number of articles about known bugs we are trying to fix in the [[:category:bugs | bugs category]]. Any further feedback on these bugs might be the piece of the puzzle that allows me to fix the bug.
| |
|
| |
| == Previous requests that were not addressed (with reasons) ==
| |
| === Default location field to main collection location === | | === Default location field to main collection location === |
| There have been requests to default the location field to the main (or only) collection location. | | There have been requests to default the location field to the main (or only) collection location. |
| Line 89: |
Line 99: |
| * "There are a number of site collecting on 2 or more units using the same laptop. We get ward location entry error when there is a default location set." ... "--[[User:TOstryzniuk|TOstryzniuk]] 12:25, 20 October 2010 (CDT)" | | * "There are a number of site collecting on 2 or more units using the same laptop. We get ward location entry error when there is a default location set." ... "--[[User:TOstryzniuk|TOstryzniuk]] 12:25, 20 October 2010 (CDT)" |
| PS: If I enable defaulting for anywhere then I would not be able to disable defaulting for other locations, so it was decided not to have defaulting. [[User:Ttenbergen|Ttenbergen]] 12:44, 12 January 2011 (CST) | | PS: If I enable defaulting for anywhere then I would not be able to disable defaulting for other locations, so it was decided not to have defaulting. [[User:Ttenbergen|Ttenbergen]] 12:44, 12 January 2011 (CST) |
| | I have, though, reduced the location list to only those wards at a given laptop's site. [[User:Ttenbergen|Ttenbergen]] 18:09, 14 July 2011 (CDT) |
|
| |
|
| === Cancel for Settings === | | === Cancel for Settings === |
| Line 94: |
Line 105: |
|
| |
|
| No can do. There are is a sb-form in settings form that would not be cancelled, so having a cancel would be misleading. | | No can do. There are is a sb-form in settings form that would not be cancelled, so having a cancel would be misleading. |
|
| |
| === Off-line copy of wiki for laptop ===
| |
| We found a way to do this, but it would add overhead work to the collectors' job and it would deter from using the wiki as a tool owned and updated by all, so Trish and Tina decided not to pursue this further. [[User:Ttenbergen|Ttenbergen]] 15:01, 16 April 2010 (CDT)
| |
|
| |
| * look into possibility of automatically downloading WIKI guide to laptop each day that it is synch'd. (portable version of guideline)'''--[[User:TOstryzniuk|TOstryzniuk]] 20:11, 4 April 2009 (CDT)
| |
|
| |
| *As moved from Diagnosis Coding:
| |
| ::A suggestion has been put forth to Tina is to find a away to allow a downloaded copy of the WIKI guide on laptops, the collection tool we are moving to soon. I think this would be an excellent solution if she can do this. Collectors would then be able to search for info no matter where they are in the collection field and each time they synch there laptop, they would get updated WIKI items. That is the plan............but waiting to here from IT support.
| |
| ::It is challenge right now in that the guideline information is not easily and quickly accessible while you are doing your work in the unit or in medical records. Most collectors must run back to their office or find a free computer to log in and look up guide info.
| |
| ::Keep in mind, guide information changes regularily, so what you print out one day is outdated the next for a number of articles. [[User:TOstryzniuk|TOstryzniuk]] 11:25, 29 April 2009 (CDT)
| |
| *April 2010 - Trish and Tina reviewed the apparent option to have a COPY of wiki on laptop. Problem if implemented:
| |
| # if collectors will not have the most update the copy on laptop because changes and updates are happening daily on the MAIN copy here, and thus changes to instruction will get missed.
| |
| #2. Don't want multiple copies of instruction and information on multiple laptops that are not up to date.
| |
| #Collector questions and contribution to the Wiki cannot be added to copy of Wiki on laptop. Questions and contribution must be made centrally not locally so that information is in ONE PLACE and the same for everyone.--[[User:TOstryzniuk|TOstryzniuk]] 19:11, 20 April 2010 (CDT)
| |
|
| |
|
| === APACHE lab value limit change request === | | === APACHE lab value limit change request === |
| Line 113: |
Line 110: |
| ** Decided to leave limits be and have collectors enter limit values and email Pagasa with real values when extreme values are encountered. Contacted Pagasa to let us know if such emails become too frequent. [[User:Ttenbergen|Ttenbergen]] 08:53, 12 July 2010 (CDT) | | ** Decided to leave limits be and have collectors enter limit values and email Pagasa with real values when extreme values are encountered. Contacted Pagasa to let us know if such emails become too frequent. [[User:Ttenbergen|Ttenbergen]] 08:53, 12 July 2010 (CDT) |
|
| |
|
| [[Category: IT Instructions]]
| |
| [[Category: Questions IT]]
| |
| [[Category: Questions]]
| |
| [[Category: Development Documentation]] | | [[Category: Development Documentation]] |
| [[Category: Change Logs CCMDB]] | | [[Category: CCMDB.accdb]] |