CCMDB Wiki

Requested CCMDB changes for the next version: Difference between revisions

← Older edit
mNo edit summary
mNo edit summary
 
(169 intermediate revisions by 7 users not shown)
Line 2: Line 2:
   
   
== Requests ==
== Requests ==
===New change request===
==== after fixing the CCI page names on wiki, '''add wiki link for CCI codes in CCMDB.accdb''' ====
* remove labs [http://ccmdb.kuality.ca/index.php?title=Lab_Collection_Process&curid=424&diff=57292&oldid=57270]
** hid fields 10:40, 2017 October 10 (CDT), will delete and update wiki after a month if no problem.


=== ACCU borrow project ===
=== screen refresh reductions ===
* [[ACCU_borrow#stay_less_than_2_hours]]
As part of troubleshooting Con's blinky screen Brendan suggested the following:


=== integrity checks checklist ===
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.
{{#ask: [[Category:CCMDB Data Integrity Checks]] [[Has IntegrityCheckStatus::ready to implement]]
 
  |?Has IntegrityCheckStatus = Status
== 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
}}
 
== 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
  |?Modification date
  |sort=Modification date
  |sort=Modification date
  |order=ascending
  |order=ascending
  |limit=3
  |limit=20
  |format=broadtable
  |format=broadtable
  |link=all
  |link=all
  |class=sortable wikitable smwtable
  |class=sortable wikitable smwtable
}}
}}


=== remove OR requirement ===
== Next Round of Data Changes ==
{{Discussion}}
Flag this in the relevant pages as follows so it lists properly in [[To do list]]. See there for actual changes requested.  
*Tina, Laura reported at last task meeting that this was resolved.  I don't see it in [[CCMDB.mdb Change Log 2017]]. Please remove if you don't need to document in change log.
 
*waiting for confirmation from Trish
 
* Allow cardiology previous service for STB ACCU previous location. (still will not allow)--[[User:LKolesar|LKolesar]] 10:46, 2017 October 3 (CDT)
 
See and fix articles when done
* [[Admit Diagnosis]]
* [[Check ORDx]]
* [[Valvuloplasty]]
* [[S alldiagnoses OR]]


=== TR DtTm error wording ===
{ {Todo
* Fix wording of error pop up in "transfer ready dt/tm" which says "transfer date and time less than admit date and time". In our new structure the word "admit" refers to the visit admit. Instead you need to use the word "Arrive dttm"  --[[User:LKolesar|LKolesar]] 07:37, 2017 October 5 (CDT)
  | who = Tina
** I can't find an error with that exact wording. The closest thing I can find is
| todo_added = 2021-07-21
<pre>If <...> Form_View.Arrive_DtTm > Form_View.Transfer_Ready_DtTm Then error = "Arrive_DtTm can't be greater than Transfer_Ready_DtTm. "</pre>
| todo_action =
::which is already referring to arrive. Could you please send me a screen shot of this? Ttenbergen 10:17, 2017 October 10 (CDT)
  | question = Dev_CCMDB_Data / Dev_CCMDB depending on if CCMDB needs update first.  
 
<provide details of change>
=== dispo tab popups ===
}}
* Review all pop ups in the dispo tab to ensure that they are compatible with the new wording in this structure.--[[User:LKolesar|LKolesar]] 07:40, 2017 October 5 (CDT)
* {{discussion}} pop-ups? Do you mean error messages? As far as I know all are changed, but if you find any that are wrong pls let me know and I will fix. Ttenbergen 10:35, 2017 October 10 (CDT)
 
==2016_June==
*from team meeting a while ago:
* provide a listing of highest serial for each unit to help with next serial
** keep deleted for 4 weeks so highest serial will not be wrong a short-stay patient leaves before the next higher number is assigned.
* Add a unit sorter secondary by pat-id
 
== Bug Fixes ==
''see [[:Category:Bugs]] and especially [[:Category:Bugs needing input]] for bugs with their own article''
 
== Next Round of Data Changes ==


== Bugs that need input ==
== Bugs that need input ==
''See '''[[:Category:Bugs needing input]]'''. 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 [[:Category:Bugs needing input]]. 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.
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]]
=== Error when deleting many Pts and then opening next Pt ===
|?Modification date
* weird errors when deleting a pile of PTs and then opening the next Pt
|default=No corresponding old article found
** could not replicate... no idea what this is about. Does anyone get these and could provide more info?
|format=broadtable
* "can't assign" error when opening patient in list
|limit=100
Como_checker crashes on opening patient in patient list; line starting with Q_str = Left goes bad if ???, but only some of the time. Wasn't able to replicate. This might be related to an error reported before that happens when many patients are deleted. Need more info...
|link=all
 
|headers=show}}
==Changes Under Discussion ==
See [[:Category:Potential Change]] as well, this are only changes without a home article.
 
=== separating the date/time in new fields ===
{{discussion}}
#the date utilizing the star and then the + or – ; then tab into the time where it can be typed in easily. Unfortunately, the dispo tab data format does not at this time allow the ease of entry that the registry has.  Are you planning to make the change to this format once we have gone through the trial period?    Just wondering because currently it is not as easy to enter the dates and times as the current registry format is.  Data collectors have been asking about this.  Laura -June 15.16
#*will require further discussion with Trish. -- Ttenbergen 16:53, 2016 June 16 (CDT) still Ttenbergen 19:38, 2016 June 27 (CDT)


=== renal task checks ===
=== renal task checks ===
Line 88: Line 67:
  | blah | blah blah  |
  | blah | blah blah  |
  ---------------------
  ---------------------
* If someone could set up the table on the wiki I will make a form with the content in the app. {{discussion}} 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.mdb.
* 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 no longer yellowing fields ===
{{Potential Change}}
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)
Line 126: 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 135: Line 111:


[[Category: Development Documentation]]
[[Category: Development Documentation]]
[[Category: CCMDB.mdb]]
[[Category: CCMDB.accdb]]
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Requested_CCMDB_changes_for_the_next_version"