Requested CCMDB changes for the next version: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
 
(795 intermediate revisions by 13 users not shown)
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 ===
* fix the error checking for overstay project to not allow any missing tmp entries (possibly more)
As part of troubleshooting Con's blinky screen Brendan suggested the following:


* see [[Out of Memory Error]]
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.
* see also [[:Category:Bugs]]


* with reg already checked, was able to change discharge date to a future date and it didn't uncheck initially; it did catch on trying to final-check, so this is a low-grade bug, just should be fixed eventually Ttenbergen 20:37, 2012 November 1 (EDT)
== 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
}}


* able to uncheck checkboxes without finalcheck unchecking. Need to determine if this could lead to bad data going through. [[User:Ttenbergen|Ttenbergen]] 14:45, 2012 May 22 (CDT)
== Bug Fixes ==
 
''see [[:Category:Bugs]] and especially [[:Category:Bugs needing input]] for bugs with their own article''
* if an error handler turns the dx tab yellow this is not automatically reset when a new patient is opened. Ttenbergen 13:15, 2012 October 31 (EDT)
{{#ask: [[Category:Bugs]] [[Category:Bugs needing input]]
 
|?DICStatus = Status
* [[ADL - now you see them now you don't]]
|?Modification date
 
|sort=Modification date
* [[DX Delete Bug]]
|order=ascending
 
|limit=20
* [[Pharmacy LOS Bug]]
|format=broadtable
 
|link=all
== New projects ==
|class=sortable wikitable smwtable
 
}}
== Collection tool improvement requests ==


== Next Round of Data Changes ==
== 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. [[User:Ttenbergen|Ttenbergen]] 15:11, 2012 July 4 (CDT)
Flag this in the relevant pages as follows so it lists properly in [[To do list]]. See there for actual changes requested.


== Bugs that need replicating ==
{ {Todo
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.
| 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>
}}


=== Duplicate Priority error in Dxs when there is no duplicate Dx ===
== Bugs that need input ==
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)
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}}


===L_Pharm_Flowsheet_sum===
=== renal task checks ===
Occasionally a data collector has sent data with more than one line of pharmacy for a patient. Still looking into what causes this. [[User:Ttenbergen|Ttenbergen]] 15:07, 2012 June 18 (CDT)
* [[Check Renal Tasks]]
* 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. [[User:Ttenbergen|Ttenbergen]] 09:56, 2012 September 13 (CDT)
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  |
---------------------


==Changes Under 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)
'' see [[:Category:Potential Change]] as well, this are only changes without a home article.
** 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)
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 [[:Category:Potential Change|Potential Change]]. {{Potential Change}} To get anything done, if applicable flag it in the home article rather than here. '''
 
 
=== label for filter field ===
* change label for '''[[Filter_Field#Should_the_label_change.3F | Filter Field]]''' to "LTV"? (see question/discussion at that article) Ttenbergen 16:51, 2012 October 15 (CDT)
 
=== 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 [[User:Ttenbergen|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'''. {{Discussion}}


=== apache check no longer yellowing fields ===
=== apache check no longer yellowing fields ===
* apache check is no longer yellowing fields[[User:Ttenbergen|Ttenbergen]] 10:09, 10 January 2012 (CST)
apache check is no longer yellowing fields[[User:Ttenbergen|Ttenbergen]] 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... [[User:Ttenbergen|Ttenbergen]] 17:13, 2012 January 31 (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... [[User:Ttenbergen|Ttenbergen]] 17:13, 2012 January 31 (CST)
{{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)
**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)


=== automate prioritization of acquireds/complications ===
== Previous requests that were not made (with reasons) ==
[[Acquired Diagnosis / Complication#Automating Priorization]]
=== 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.


=== Facilitated Management of Serial numbers ===
=== prevent setting recordstatus from sent to complete ===
see [[Facilitated Management of Serial numbers]]
*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.


=== Facilitating diagnosis entries ===
=== sending only lab/pharm sums to centralized_data.mdb ===
{{discussion}}
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.  
* 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)
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.  
** 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)
Will leave alone unless main office really wants this done... Ttenbergen 12:35, 2013 November 11 (CST)
*** 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)
***** Is this still something we are interested in or should we abandon it and wait for ICD10? Another options is to pick the 10-or-so diagnoses that are hardest to find due to a bad name and rename only those. I'd need input from collectors. Ttenbergen 17:40, 2012 October 1 (CDT)


== 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 90: 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 98: 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: Development Documentation]]
[[Category: Development Documentation]]
[[Category: Change Logs CCMDB]]
[[Category: CCMDB.accdb]]

Latest revision as of 10:00, 2023 April 27

see the 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.

integrity checks checklist

 Status
Function long LOS()needs review
Query check CCI each count vs LOSneeds review
Query check long transfer delayneeds review

Bug Fixes

see Category:Bugs and especially Category:Bugs needing input for bugs with their own article

 StatusModification date"Modification date" is a predefined property that corresponds to the date of the last modification of a subject and is provided by Semantic MediaWiki.
Bug needing input7 November 2012 22:35:09
Combiner tab re-sorts after entering5 October 2022 17:07:01
CCI Picklist tab is slow25 January 2023 16:56:36
Repeat clicks being needed when entering CCI PX Type12 March 2024 15:51:37
Error "Invalid SQL statment..." when sending12 March 2024 16:10:23
Error: There isn't enough free memory to update the display. Close unneeded programs and try again.12 March 2024 16:13:18

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.

 Modification date"Modification date" is a predefined property that corresponds to the date of the last modification of a subject and is provided by Semantic MediaWiki.
Bug needing input7 November 2012 22:35:09
CCI Picklist tab is slow25 January 2023 16:56:36
Combiner tab re-sorts after entering5 October 2022 17:07:01
Error "Invalid SQL statment..." when sending12 March 2024 16:10:23
Error: There isn't enough free memory to update the display. Close unneeded programs and try again.12 March 2024 16:13:18
Repeat clicks being needed when entering CCI PX Type12 March 2024 15:51:37

renal task checks

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:

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  |
---------------------
  • 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)

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)
    • 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? --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)

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.

prevent setting recordstatus from sent to complete

  • Prevent RecordStatus of Sent files being changed from Sent to Incomplete if data altered after file sent inMlaporte 15:18, 2013 December 16 (CST)
    • actually, need to be able to do that to re-send when needed.

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)

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.

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)