Requested CCMDB changes for the next version

see the Development Documentation Category for other development logs

Bug Fixes

• fix the error checking for overstay project to not allow any missing tmp entries (possibly more)

• see Out of Memory Error
• see also Category:Bugs

• able to uncheck checkboxes without finalcheck unchecking. Need to determine if this could lead to bad data going through. Ttenbergen 14:45, 2012 May 22 (CDT)

• as per Lois, and confirmed by other collectors at the team meeting: "Every once in a while when I open my files the ADL’s appear on my registry page for CICU. I go in and out and they disappear."; have asked if anyone can provide specific steps that can make this happen. Ttenbergen 18:42, 2012 June 7 (CDT)

• please fix spelling error for code #86800 in both the other medical, and charlson comorbid sections of code book, and access. It should be spelled Churg-Strauss Syndrome, not Ghurg-Strauss Syndrome. DPageNewton 15:49, 2012 October 1 (CDT)

Collection tool improvement requests

• repeat of review and act on Feedback Request - Patient List -- Ttenbergen 13:20, 2012 September 20 (CDT)
  • confirm that the new screen fits laptops Ttenbergen 16:43, 2012 September 25 (CDT)

Drugs Collected

see Pharmacy_collection#Pharmacy_Format_on_CCMDB.mdb

automatic generation of tmp entries

see Automatic Generation of TMP entries

Organ Donor Check

• Organ_Donor#Data_Integrity_Rules

duplicate error messages

fix/improve/document duplicate error msgs Ttenbergen 17:28, 28 July 2011 (CDT)

These are based on the events used to trigger error messages. I think I have eliminated most of them - collectors, please log here any that I may have missed. Template:Discussion

apache check no longer yellowing fields

• apache check is no longer yellowing fieldsTtenbergen 10:09, 10 January 2012 (CST)
  • 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... Ttenbergen 17:13, 2012 January 31 (CST)

Template:Potential Change 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)

Next Round of Data Changes

• make sure that the updater works if there is no network connection on first opening Access. likely will require the copying of the new data file to happen in the news.batch instead, so would need to update that. Ttenbergen 15:11, 2012 July 4 (CDT)

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 bugs category. Any further feedback on these bugs might be the piece of the puzzle that allows me to fix the bug.

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? Ttenbergen 16:58, 1 September 2011 (CDT)

L_Pharm_Flowsheet_sum

Occasionally a data collector has sent data with more than one line of pharmacy for a patient. Still looking into what causes this. Ttenbergen 15:07, 2012 June 18 (CDT)

• have monitored this since the spring and it has not recurred. If it recurs please let me know. Will consider it a dead issue otherwise. Ttenbergen 09:56, 2012 September 13 (CDT)

Changes Under Discussion

see Category:Potential Change as well, this are only changes without a home article.

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.

Anything under here is a Potential Change. Template:Potential Change To get anything done, if applicable flag it in the home article rather than here.

automate prioritization of acquireds/complications

Acquired Diagnosis / Complication#Automating Priorization

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.

Added question to Serial_number#Special-Use_Serial_Numbers to find out if any serial numbers need to be "reserved".

Possible Solution 1

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

• 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).--CMarks 08:39, 30 November 2010 (CST)

Possible Solution 2

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. 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). Template:Discussion

• Do you think this would be helpful? Can you see problems with this? Ttenbergen 14:14, 15 July 2011 (CDT)
  • Hi Collectors - is this still something that would be helpful or not? Please advise, if not we will take it off change request list. Thanks kindly.Trish Ostryzniuk 14:52, 2012 April 3 (CDT)

Facilitating diagnosis entries

• As discussed at the 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? 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. --LKolesar 14:08, 21 January 2011 (CST)
    • can't find the file, could you tell me the file name and location on the regional server? Ttenbergen 18:03, 14 July 2011 (CDT)
      • As per Laura file is on Regional Server\maintenance\s_alldiagnosis.mdb Ttenbergen 12:20, 15 July 2011 (CDT)

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

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." ... "--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. Ttenbergen 12:44, 12 January 2011 (CST) I have, though, reduced the location list to only those wards at a given laptop's site. Ttenbergen 18:09, 14 July 2011 (CDT)

Cancel for Settings

change the settings form to have a save and a cancel button...

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 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. --TOstryzniuk 12:12, 6 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. Ttenbergen 08:53, 12 July 2010 (CDT)