CCMDB Wiki

Requested CCMDB changes for the next version: Difference between revisions

← Older edit
m replacing , with ; for multiple listings of old articles; wasn't working because some article names contain commas (and/or general clean-up)
m Text replacement - "[[Category: " to "[[Category:"
 
(87 intermediate revisions by 2 users not shown)
Line 2: Line 2:
   
   
== Requests ==
== Requests ==
=== IICU consult ===
==== after fixing the CCI page names on wiki, '''add wiki link for CCI codes in CCMDB.accdb''' ====
{{Discuss | who = all | question =  - this needs to be added as we are to start this week. thanks[[User:TOstryzniuk|Trish Ostryzniuk]] 11:59, 2018 November 13 (CST)
*[[IICU consult]] - needs this added to TMP so we can start project on Nov 12.18[[User:TOstryzniuk|Trish Ostryzniuk]] 14:37, 2018 November 5 (CST)
=== Comorbids in another tab? ===
Team meeting staff raised concerned about too many rows to scroll down through when comorbid are together with Admits and acquired.
*Not sorting properly and adds to difficulties with longs lists. 
*One suggestion to put in separate tab? Tina to investigate further with staff and perhaps see if there are any options. 
=== better color differentiation between Admit, Acquired and comorbid rows ICD10 CCI ===
currently color is so pale and barely visible. Staff comments at team meeting Sept 20 
===ICD10/CCI priority number column move ===
*staff requested ICD10/CCI DX priority number column to be moved closer left instead of being on the far right of row.  Staff can advise where exactly that column would best be.[[User:TOstryzniuk|Trish Ostryzniuk]] 19:59, 2018 September 21 (CDT)
=== return dispo screen tab order ===


=== screen refresh reductions ===
=== screen refresh reductions ===
As part of troubleshooting Con's blinky screen Brendan suggested the following:  
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.


=== ICD10 list ===
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.
*work-around, for now: I printed a copy of the ICD10 Codes (only the categories ie. A00-B99 Certain infectious and parasite diseases to U00-U99 Codes for special purposes) so when I am uncertain I quickly glance at my list then scroll to the appropriate category number  rather than scroll through the list trying to eyeball the diagnosis.
** Category sorting for ICD10 will come once dx reconciling is done. (not yet done: {{#ask: [[Category:ICD10 Diagnosis]]
[[Has ICD10TransitionStatus::freshly automatically generated article]]
|format=count
}}, need review: {{#ask:
[[Category:ICD10 Diagnosis]]
[[Has ICD10TransitionStatus::needs review]]
|format=count
}})


===CCI list===
== integrity checks checklist ==
{{Discuss | who = all | question = 
{{#ask: [[DICStatus::ready to implement]][[DICApp::CCMDB.accdb]] OR [[DICStatus::needs review]][[DICApp::CCMDB.accdb]]
* '''we will add a way to filter for organ systems'''
  |?DICStatus = Status
** waiting for CCI Items on wiki to be categorized, then will use that to categorize them on CCMDB.mdb.
  |limit=20
* we can add a way to filter for diagnostic/therapeutic/imaging/obstetric/misc if that is still relevant after organ system filter is implemented
* '''add a way to type and have CCMDB.mdb find any entry with those words in it (rather than at beginning of line)
** this is now implemented for the component list, just press the "?" button. Let me know if this helps. Ttenbergen 14:06, 2018 September 25 (CDT)
* no procedure performed should be at the top of CCI picklist rather than at the bottom (originally this included "no procedure entered", but that should never be entered at all and really should just not be on the list. It's only purpose is as placeholder before a value is entered. If there is no procedure entered, the line should not be there. )
 
*Couple of suggestions - sorting the current pick list alphabetically and having a broad search function (where you could type in any part of a word) would help to reduce scrolling in CCI's. --[[User:Jvelasco|Jvelasco]] 11:39, 2018 May 14 (CDT)
** Picklist was changed to alpha sorting. Hesitant to change component list to that - it's now broadly from-head-to-toe; if you don't know the words that were used sorting them alphabetically would be harder than this.
 
===New change request===
* [[CXR count cross check]]
 
=== integrity checks checklist ===
{{#ask: [[Category:CCMDB Data Integrity Checks]] [[Has IntegrityCheckStatus::ready to implement]]
  |?Has IntegrityCheckStatus = Status
|?Modification date
|sort=Modification date
|order=ascending
  |limit=3
  |format=broadtable
  |format=broadtable
|link=all
  |class=sortable wikitable smwtable
  |class=sortable wikitable smwtable
|default=No [[cross check]]s ready to implement
}}
}}


Line 60: Line 21:
''see [[:Category:Bugs]] and especially [[:Category:Bugs needing input]] for bugs with their own article''
''see [[:Category:Bugs]] and especially [[:Category:Bugs needing input]] for bugs with their own article''
{{#ask: [[Category:Bugs]] [[Category:Bugs needing input]]
{{#ask: [[Category:Bugs]] [[Category:Bugs needing input]]
  |?Has IntegrityCheckStatus = Status
  |?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
Line 71: Line 32:


== Next Round of Data Changes ==
== 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 ==
== Bugs that need input ==
Line 81: Line 51:
|link=all
|link=all
|headers=show}}
|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 105: 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 143: 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 151: 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: 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"