Requested CCMDB changes for the next version

see the Development Documentation Category for other development logs


Bug Fix Requests

Improvement Requests

  • add full apache score
  • put PaO2/AaDO2 score onto main apache form
  • add a search button to the patient list
  • check if I can reduce the # of times an error is displayed in Labs
  • ABG information in the standard order: Ph, then PCO2, then pO2


Counting Date Tracker

As per email from Marie Laporte: "Thought I would email some thoughts re: moving away from paper collection. Each time I have to type in "last counted EKg @ 0000 hrs on date" and have to do the same for pharm, CXR and labs and date reviewed; I think... it would be very convenient and user friendly to have this available from a drop down list/or permanent field adjacent to our notes field. If it was set up like DOB or admit date/time fields we could easily enter date and time of the last counted item-and everyone would have the same format. Example:

  • LAST COUNTED LABS: DATE TIME
  • LAST COUNTED EKG: DATE TIME
  • LAST COUNTED CXR: DATE TIME
  • LAST COUNTED PHARM DATE TIME
  • CHART REVIEWED: DATE TIME
    • I sent an email to Trish to clarify something. Pending response I might implement this. Ttenbergen 15:10, 21 May 2010 (CDT)

non-vital left-overs from 1.9933 testing

  • CCMDB Error list now hidden behind maximised window, duh!

Final Check into drop-down

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. Ttenbergen 13:25, 8 December 2009 (CST)

  • change can not be made via ccmdb.mdb since table structure for linked tables (as used by laptops) can not be manipulated externally.
    • option: Have ccmdb.mdb automatically generate a new .mdb based on the changes, and then change linking to that new .mdb
  • 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")

sL_AaDO2 value delete

Values in helper table sL_AaDO2 are not being deleted at this point when "their" patient is deleted. This is no big deal since the table gets overwritten every time there is a new version is rolled out. Should still get cleaned up, though, but I have to figure out a trick. Ttenbergen 12:25, 17 May 2010 (CDT)

better way to say PO2 apache score type

state "using PO2" better on the AaDO2 apache score display

Bugs that need replicating

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.

WBC = 0 does not uncheck apache box

As per email from Pagasa, and confirmed by Tina, 28 jan 2010 Ttenbergen 14:32, 28 January 2010 (CST)

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. Ttenbergen 12:58, 29 January 2010 (CST)

How to demonstrate this bug

Template:Discussion

Infection without pathogen subcode was sent to csv

Oaks - Patient coded for Cystitis Bladder Infection but no sub code? Admit date Jan 25/10-Jan. 30/10. Pagasa Torres.

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

Template:Discussion


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.


batch file checks

  • make sure the "News and backup" batch file complains noisily if it does not have a server connection. 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? Ttenbergen Template: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.

Template:Discussion

  • Would anyone else find this useful? Should it be included in the Master DB? 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.

Template:Discussion

  • Any thoughts? Ttenbergen 17:34, 9 February 2010 (CST)


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. 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)--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. 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:
  1. 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. 2. Don't want multiple copies of instruction and information on multiple laptops that are not up to date.
  3. 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.--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...Ttenbergen 16:05, 3 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

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.