CCMDB Wiki

Requested CCMDB changes for the next version: Difference between revisions

← Older edit
mNo edit summary
 
(798 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]]


* 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)
== 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
}}


* 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)
== 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
}}


* [[ADL - now you see them now you don't]]
== 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.


* [[DX Delete Bug]]
{ {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>
}}


* [[Pharmacy LOS Bug]]
== 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}}


== New projects ==
=== 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  |
---------------------


== Collection tool 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.
=== label for filter field ===
*** 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)
* 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)


== Next Round of Data Changes ==
== Previous requests that were not made (with reasons) ==
* 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)
=== 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.


== Bugs that need replicating ==
=== prevent setting recordstatus from sent to complete ===
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.
*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.  


=== Duplicate Priority error in Dxs when there is no duplicate Dx ===
=== sending only lab/pharm sums to centralized_data.mdb ===
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)
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)


===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. [[User:Ttenbergen|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. [[User:Ttenbergen|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 [[:Category:Potential Change|Potential Change]]. {{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]]
=== Facilitated Management of Serial numbers ===
see [[Facilitated Management of Serial numbers]]
=== Facilitating diagnosis entries ===
{{discussion}}
* 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)
** 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)
*** 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 87: 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 95: 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]]
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Requested_CCMDB_changes_for_the_next_version"