|
|
| 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'' |
| ==September 7, 2011== | | |
| *Please remove [[QASeptic]] from the TMP project drop down list. [http://ccmdb.kuality.ca/index.php/QASeptic#End_Date Stop date] was July 1.11 --[[User:TOstryzniuk|TOstryzniuk]] 18:19, 7 September 2011 (CDT)
| | == Requests == |
| *please also remove [[EarlyID]] from the TMP project dropdown list. thank you.--[[User:TOstryzniuk|TOstryzniuk]] 18:27, 7 September 2011 (CDT)
| | ==== after fixing the CCI page names on wiki, '''add wiki link for CCI codes in CCMDB.accdb''' ==== |
| I have not touched the master ccmdb version because I am not sure Tina has a copy she is working on that is not in master program on Regional Server.
| |
|
| |
|
| == 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]]
| |
| * data .mdbs are not compact/fixing, change so they do that on close [[User:Ttenbergen|Ttenbergen]] 14:12, 6 September 2011 (CDT)
| |
|
| |
|
| == Collection tool improvement requests ==
| | 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. |
| * add the */+/- buttons to the date in tmp form as well (good suggestion Debbie)
| |
| * waiting for feedback on Laura's Dx list changes before doing this: change spelling of dx 19914 to "Interleukin", mirror on the wiki [[User:Ttenbergen|Ttenbergen]] 13:29, 15 July 2011 (CDT)
| |
| * [[Check_ORDx#Discussion]] [[User:Ttenbergen|Ttenbergen]] 17:11, 26 July 2011 (CDT)
| |
| * confirm [[Field_Ranges_and_Decimal_Settings#Rare Min and Rare Max]] ended up implemented, I think we reverted that. If reverted, revisit this. [[User:Ttenbergen|Ttenbergen]] 17:36, 26 July 2011 (CDT)
| |
| * was the implementation of MaxDoses (see [[Pharmacy Collection Other Sites]] finished? [[User:Ttenbergen|Ttenbergen]] 17:41, 26 July 2011 (CDT)
| |
| * implement [[ER_Wait#Integrity_Check]] [[User:Ttenbergen|Ttenbergen]] 12:51, 27 July 2011 (CDT)
| |
| * fix/improve/document duplicate error msgs [[User:Ttenbergen|Ttenbergen]] 17:28, 28 July 2011 (CDT)
| |
| * add data output for [[RIS/PACS#Direct_access_to_data]] [[User:Ttenbergen|Ttenbergen]] 11:36, 4 August 2011 (CDT)
| |
| * make sure count for rows being deleted is visible (then change [[Sending Patients]]) [[User:Ttenbergen|Ttenbergen]] 08:52, 29 August 2011 (CDT)
| |
|
| |
|
| === Next Round of Data Changes === | | == integrity checks checklist == |
| ==== ARF ====
| | {{#ask: [[DICStatus::ready to implement]][[DICApp::CCMDB.accdb]] OR [[DICStatus::needs review]][[DICApp::CCMDB.accdb]] |
| *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)
| | |?DICStatus = Status |
| ** Yes, I could do that. I will need to update the data structure to do it, though, so it will need to be when I next update that file. [[User:Ttenbergen|Ttenbergen]] 17:58, 14 July 2011 (CDT)
| | |limit=20 |
| | |format=broadtable |
| | |class=sortable wikitable smwtable |
| | |default=No cross checks ready to implement |
| | }} |
|
| |
|
| == Bugs that need replicating == | | == Bug Fixes == |
| 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.
| | ''see [[:Category:Bugs]] and especially [[:Category:Bugs needing input]] for bugs with their own article'' |
| | | {{#ask: [[Category:Bugs]] [[Category:Bugs needing input]] |
| ===Apache Errors remaining yellow from one patient to the next ===
| | |?DICStatus = Status |
| I left myself the following note: "some Apache errors still remain yellow from one patient to the next [[User:Ttenbergen|Ttenbergen]] 16:15, 2 June 2011 (CDT)". I can't even imagine now how that would be, since you would have to close one patient to open another. Does anyone else know what this was all about? [[User:Ttenbergen|Ttenbergen]] 17:56, 14 July 2011 (CDT)
| | |?Modification date |
| | | |sort=Modification date |
| ===Access allows an Admit date in the future===
| | |order=ascending |
| {{discussion}}
| | |limit=20 |
| *We are still finding patient with admit dates in the future. For example Concordia recently sent a file with admit date of July 2011. This date is beyond current date. We thought this error was already address and entry level.--[[User:TOstryzniuk|TOstryzniuk]] 12:32, 9 June 2011 (CDT)
| | |format=broadtable |
| ** I have tried to reg-complete check data for a patient with a future discharge date and it will not let me. So, I can't duplicate this. Can anyone else show me how one might make this happen? Trish, is this a one-of, or have there been others? [[User:Ttenbergen|Ttenbergen]] 17:45, 14 July 2011 (CDT)
| | |link=all |
| | | |class=sortable wikitable smwtable |
| === WBC decimal points error ===
| | }} |
| * "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)
| |
| | |
| === ABG and BP Chooser Apache Points ===
| |
| {{discussion}}
| |
| * "ApPts in BP and ABG chooser update for whole column rather than just edited line (or so, something is wrong)" I can't make this error happen. Can someone tell me what this is about? If no one has added a comment by 2011-Aug-15 this section can be deleted. [[User:Ttenbergen|Ttenbergen]] 12:48, 14 July 2011 (CDT)
| |
| | |
| === Duplicate Priority error in Dxs when there is no duplicate Dx ===
| |
| I saw on Joyce's PC an error for a duplicate diagnosis priority when there was not one. I can't duplicate the error. Is anyone else getting an error about duplicate priorities when there are none? If so, can you tell me under what conditions the error happens? [[User:Ttenbergen|Ttenbergen]] 16:58, 1 September 2011 (CDT)
| |
| | |
| === Post-Op Dx Error ===
| |
| Likely this applies only to SICUs, or possibly community ICUs. Joyce gets an error that a diagnosis for a patient who is from the OR is not a post-op diagnosis when it should be, and is on the CheckORDSX list. I can't duplicate that error. Is anyone else getting this error? [[User:Ttenbergen|Ttenbergen]] 17:01, 1 September 2011 (CDT)
| |
| ** Yes I get this error sometimes and I just continue on and it goes away. Lois
| |
| ***Yes, I have had this error as well. Sometimes it is because the priority number has not been entered yet and it will automatically give the error until you have the different diagnosis all in correct priority order. However this message can persist for awhile but will eventually disappear and I really don't find it continues after going out of the pt profile and coming back in later. --[[User:LKolesar|LKolesar]] 07:19, 6 September 2011 (CDT)
| |
| ***Yes, I get this error on surgical admissions. It seems to me that the error occurs when trying to enter an admit diagnosis such as, the reason for the surgery or problems during the OR. These "non post-op" entries are automatically assigned a priority of "0" which then ranks them higher than the surgical procedure with priority "1" already assigned. I enter the priority before entering a non post-op diagnosis as an admit diagnosis to avoid getting the error message.[[User:Mlaporte|Mlaporte]] 15:59, 6 September 2011 (CDT)
| |
| | |
| == No-Lab error when first entering a new patient ==
| |
| When a new patient is first entered on a CC laptop sometimes there is an error that you have to have at least one line in labs to enter a patient. I can't duplicate this. Can anyone tell me the circumstances under which this will happen? [[User:Ttenbergen|Ttenbergen]] 17:09, 1 September 2011 (CDT)
| |
| *I sometimes get the same error when I am leaving the file through the window.Lois
| |
| | |
| ==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.
| |
| | |
| === automate prioritization of acquireds/complications ===
| |
| [[Acquired Diagnosis / Complication#Automating Priorization]]
| |
| | |
| === Integrity rule for [[ER Wait]] dates in TMP file===
| |
| will need to bring in details from our email exchanges. [[User:Ttenbergen|Ttenbergen]] 17:56, 2 June 2011 (CDT)
| |
| | |
| === QA_Infection ===
| |
| * see [[QA_Infection#Data Integrity Rules Under Discussion ]]
| |
| | |
| === Full Apache Score ===
| |
| Add full apache score to the Viewer form
| |
| * 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)
| |
| ** 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===
| |
| If I understand right data collectors currently collect one or more locations from one or more pools of serial number pools.
| |
| 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.
| |
| | |
| 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. This is currently achieved by assigning blocks of numbers for each 100 possible serial numbers to a given collector (again, see [[Serial number]] for details]]).
| |
|
| |
|
| A serial 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.
| | == 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. |
|
| |
|
| Added question to [[Serial_number#Special-Use_Serial_Numbers]] to find out if any serial numbers need to be "reserved".
| | { {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> |
| | }} |
|
| |
|
| ==== Possible Solution 1 ==== | | == Bugs that need input == |
| 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).
| | 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}} |
|
| |
|
| To accomplish this, the _info table would store
| | === renal task checks === |
| * variable: serial_pools, value: comma-separated list of wards | | * [[Check Renal Tasks]] |
| * 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 | | 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 | |
| | --------------------- |
|
| |
|
| {{discussion}}
| | * 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) |
| * 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? | | ** 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. |
| **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) | | *** 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) |
|
| |
|
| ==== Possible Solution 2 ==== | | === apache check no longer yellowing fields === |
| If we are not able to provide the next number on the list, we could at least suggest it, and then do error checking on what is chosen.
| | apache check is no longer yellowing fields[[User:Ttenbergen|Ttenbergen]] 10:09, 10 January 2012 (CST) |
| Scenario: When the "Add Patient" button is clicked on the Patient List, the msg box could default to (highest serial currently on the laptop)+1. If a different number is desired, the collector could change it. This would be followed by the existing checks for a blank ID and for an existing ID. The program would then check if the ID was '''smaller''' than the largest ID already present (since some collectors use multiple indices, this error would be ignorable). The program could also check if the new Patient ID is more than “X” greater than the previous max(Pat_ID) (what would be a reasonable "X"?) (again, this error would be ignorable).
| | *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) |
| {{discussion}}
| | **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) |
| * Do you think this would be helpful? Can you see problems with this? [[User:Ttenbergen|Ttenbergen]] 14:14, 15 July 2011 (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) |
|
| |
|
| === Facilitating diagnosis entries === | | == Previous requests that were not made (with reasons) == |
| {{discussion}}
| | === DOB format === |
| * 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) | | * "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) |
| ** 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)
| | ** there was discussion about doing this and we decided not to to keep dates consistent throughout the program. |
| *** can't find the file, could you tell me the file name and location on the regional server? [[User:Ttenbergen|Ttenbergen]] 18:03, 14 July 2011 (CDT) | |
| **** As per Laura file is on [[Regional Server]]\maintenance\s_alldiagnosis.mdb [[User:Ttenbergen|Ttenbergen]] 12:20, 15 July 2011 (CDT)
| |
|
| |
|
| === Extra "pathogens" === | | === prevent setting recordstatus from sent to complete === |
| 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.
| | *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. |
|
| |
|
| Some of you are entering [[Unknown Pathogen]], and then re-check all patients with unknown pathogens before sending.
| | === 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) |
|
| |
|
| {{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)
| |
|
| |
| == 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 137: |
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 ===
| |
| see [[Wiki onto laptops]]
| |
|
| |
|
| === APACHE lab value limit change request === | | === APACHE lab value limit change request === |
| Line 145: |
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]] |