|
|
| 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''' ==== |
|
| |
|
| | === screen refresh reductions === |
| | As part of troubleshooting Con's blinky screen Brendan suggested the following: |
|
| |
|
| | 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. |
|
| |
|
| == Bug Fix Requests == | | == 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 |
| | }} |
|
| |
|
| | == Next Round of Data Changes == |
| | Flag this in the relevant pages as follows so it lists properly in [[To do list]]. See there for actual changes requested. |
|
| |
|
| | { {Todo |
| | | 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> |
| | }} |
|
| |
|
| | == Bugs that need input == |
| | 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}} |
|
| |
|
| | === renal task checks === |
| | * [[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 | |
| | --------------------- |
|
| |
|
| == Improvement Requests ==
| | * 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) |
| | ** 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. |
| | *** 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) |
|
| |
|
| === Final Check into drop-down === | | === apache check no longer yellowing fields === |
| Make final check into a drop down to comply with requirement for stating the status within the process of data once we store data on U of M. [[User:Ttenbergen|Ttenbergen]] 13:25, 8 December 2009 (CST)
| | apache check is no longer yellowing fields[[User:Ttenbergen|Ttenbergen]] 10:09, 10 January 2012 (CST) |
| * first phase completed, field is being added everywhere as of [[CCMDB.mdb_Change_Log_2010#V1.9933]]. Will change element on form to dropdown when all fields have been changed. | | *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) |
| * still required: change every spot that deals with finalcheck to deal with record_status instead. Easiest might be to make it a function finalcheck = (record_status = "CollectComplete") | | **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) |
|
| |
|
| == Bugs that need replicating == | | == Previous requests that were not made (with reasons) == |
| In order to troubleshoot a bug we need to know a way to "make it happen". This section contains bugs that have been reported but can not be demonstrated on demand.
| | === 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. |
|
| |
|
| === [[WBC]] = 0 does not uncheck apache box === | | === prevent setting recordstatus from sent to complete === |
| As per email from Pagasa, and confirmed by Tina, 28 jan 2010 [[User:Ttenbergen|Ttenbergen]] 14:32, 28 January 2010 (CST)
| | *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. |
|
| |
|
| There may also still be a problem with sending very low numbers. Lois apparently thought she entered and sent WBC with a value of 0.02, which CCMDB.mdb should accept, but may not send properly. [[User:Ttenbergen|Ttenbergen]] 12:58, 29 January 2010 (CST)
| | === sending only lab/pharm sums to centralized_data.mdb === |
| ==== How to demonstrate this bug ====
| | 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. |
| {{discussion}}
| | 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. |
| *Anyone?[[User:Ttenbergen|Ttenbergen]] 12:25, 12 April 2010 (CDT)
| | Will leave alone unless main office really wants this done... Ttenbergen 12:35, 2013 November 11 (CST) |
|
| |
|
| === Infection without pathogen subcode was sent to csv === | | === Default location field to main collection location === |
| Oaks - Patient coded for Cystitis Bladder Infection but no sub code? Admit date Jan 25/10-Jan. 30/10. Pagasa Torres.
| | There have been requests to default the location field to the main (or only) collection location. |
| | I could set this up, but defaulting these would increase the chances of the data just being left in there if a patient is an exception. |
| | Upon consultation with Trish it was decided not to risk an increase in errors to make this more convenient. |
| | * "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) |
| | 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) |
|
| |
|
| Patient coded for Cystitis Bladder Infection but no sub code; Admit date Jan 25/10-Jan. 30/10.
| |
|
| |
| Asked Wendy if there was any extraordinary edits for this pt, and she replied
| |
| "Nope and I too am surprised as it has always been caught if I miss it in the Edit Patients pane??? I just simply forgot as I was awaiting the results...have no idea how it got sent???"
| |
|
| |
| ==== How to demonstrate this bug ====
| |
| {{discussion}}
| |
| *Anyone? [[User:Ttenbergen|Ttenbergen]] 16:59, 9 February 2010 (CST)
| |
|
| |
|
| |
| ==Changes Under Discussion==
| |
| 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.
| |
|
| |
| === Include pH in ABG checker ===
| |
| The pH is to come from the same sample as the other ABGs, so it should be included in the ABG checker.
| |
|
| |
| ==== Overall score, then? ====
| |
| {{discussion}}
| |
| Just to be clear, does this mean the overall ABG that gives the highest score should be chosen, then? Eg if there were a pH of 3 on one, and a sum of Apaches of 2 on another sample, which would be chosen? This may be addressed in the Apache instructions, but I would appreciate a quick answer to make sure we are on the same page. [[User:Ttenbergen|Ttenbergen]] 14:05, 20 April 2010 (CDT)
| |
| * The FiO2, PaO2, PaCo2 & PH should all be from the same arterial blood gas. The most abnormal blood gas is the one associated with the lowest PaO2 '''or''' the highest AaDO2 ratio, which ever one gives the most points for APACHE II.
| |
|
| |
| === batch file checks ===
| |
| * make sure the [["News and backup" batch file]] complains noisily if it does not have a server connection. [[User:Ttenbergen|Ttenbergen]] 09:47, 18 December 2009 (CST)
| |
| ** actually, if it were to complain if there is no network connection, then it will complain every time there is a backup done off the network, which is not the intent. Will have to think of a better error scenario, e.g. if a backup to network has not been done in one week. Might be best to have that error come up to Trish rather than a collector, that way we'd catch two birds with one stone: make sure process works, and make sure process is followed. Suggested course of action: Tina will make batch file for Trish that runs by scheduled task and alerts if there is no data file in a given directory with a time stamp within the last week. Trish would know if there is a good reason and ignore the error accordingly. If there is no reason, Trish would contact the collector to find out if they have backed up to network. If so, Trish or collector would contact Tina for tech support. Plan? [[User:Ttenbergen|Ttenbergen]] {{discussion}}
| |
|
| |
| === Apache Score Helper ===
| |
| Make Apache score "helpers" to do the calculation for [[mean BP]].
| |
|
| |
| {{Discussion}}
| |
| * I made a "helper" to facilitate choosing the [[AaDO2]] for the next version. The calculation for mean BP is rather easier, so I was wondering: ICU collectors, do you think you would actually use this? [[User:Ttenbergen|Ttenbergen]] 14:37, 9 February 2010 (CST)
| |
|
| |
|
| |
| === 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.
| |
|
| |
| {{Discussion}}
| |
| * Would anyone else find this useful? Should it be included in the Master DB? [[User:Ttenbergen|Ttenbergen]] 17:34, 9 February 2010 (CST)
| |
|
| |
|
| |
| === Changes to the ccmdb.mdb to reduce reliance on paper ===
| |
| The "extra pathogens" entry above makes me wonder: are there other features collectors can think of that would suddenly make it more desirable to enter data electronically in the first place rather than on paper? This question really only applies to the access program (e.g. to laptop users) since we are phasing out the PDAs and I am not going to make any modifications to them because they cause cascading problems.
| |
|
| |
| {{discussion}}
| |
| * Any thoughts? [[User:Ttenbergen|Ttenbergen]] 17:34, 9 February 2010 (CST)
| |
|
| |
| ====[[Notes field]]====
| |
| discussion moved to [[Notes field]] [[User:Ttenbergen|Ttenbergen]] 16:19, 16 April 2010 (CDT)
| |
|
| |
| == Wikis onto 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)
| |
|
| |
| == QA Functionality ==
| |
|
| |
| === Facilitate exchange of patient discharge times ===
| |
| DCs have to know the discharge times for patients arriving at their wards from another collected ward. We should automate that rather than have them exchange manually. Might be an extension of the status file for Julie...[[User:Ttenbergen|Ttenbergen]] 16:05, 3 February 2009 (CST)
| |
| * moved a note into [[Admit, Transfer and Discharge date and time]], as this is unrelated to updates to the program. [[User:Ttenbergen|Ttenbergen]] 09:27, 11 February 2009 (CST)
| |
|
| |
| === Logging errors in the CCMDB.mdb ===
| |
| Add a table to the CCMDB that records every time an error is generated with the following details:
| |
| * Date/time of error
| |
| * patient ID (Hosp Loc Serial)
| |
| * Field Identifier
| |
| * error descriptor (text)
| |
| * erroneous value
| |
| Make that table sync to a central repository on send.
| |
|
| |
|
| |
| == After-Laptop changes ==
| |
| === Improve Data Entry for Tasks ===
| |
| make tasks easier to enter, e.g. a checklist
| |
|
| |
|
| |
| == Previous requests that were not addressed (with reasons) ==
| |
| === Cancel for Settings === | | === Cancel for Settings === |
| change the settings form to have a save and a cancel button... | | change the settings form to have a save and a cancel button... |
| Line 120: |
Line 106: |
| 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. |
|
| |
|
| [[Category: IT Instructions]] | | === APACHE lab value limit change request === |
| [[Category: Questions IT]] | | *Apache upper limit for creatinine is 2968, which is based on the highest APACHE that was ever in database. STB has one pt with a creat of 3000 and has requested to change upper limit. Laura K. --[[User:TOstryzniuk|TOstryzniuk]] 12:12, 6 July 2010 (CDT) |
| [[Category: Questions]]
| | ** 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: Development Documentation]] | | [[Category: Development Documentation]] |
| [[Category: Change Logs CCMDB]] | | [[Category: CCMDB.accdb]] |