CCMDB Wiki

Requested CCMDB changes for the next version: Difference between revisions

← Older edit
TOstryzniuk (talk | contribs)
CCMDB_legit, approved, Bureaucrats, Administrators
27,522 edits
→Requests: for Tina
mNo edit summary
 
(35 intermediate revisions by 2 users not shown)
Line 2: Line 2:
   
   
== Requests ==
== Requests ==
=== L_Log ===
==== after fixing the CCI page names on wiki, '''add wiki link for CCI codes in CCMDB.accdb''' ====
*CON and Oak urgent care in [[L_Log]] for [[Previous Location field]]. 
**Please update and change to CON - UC, OAK - UC (this would then be consistent with what we use for VIC - UC).  Not active yet.[[User:TOstryzniuk|Trish Ostryzniuk]] 16:17, 2019 May 24 (CDT)
 
===s Dispo table change ===
[[Task_Team_Meeting_-_Rolling_Agenda_and_Minutes_2019#ICU_Database_Task_Group_Meeting_.E2.80.93_April_23.2C_2019 | April 23.19-task team meeting with changes to Dispo field]]
*[[Dispo field]]
**DISPO item changes: Death - organ donor & Died – NOT organ donor,  ''''change to the following''':
***Died - to morgue
***Died - to ICU
****(you would use this for any patient who has been coded as braindead in one ICU and a potential organ donor to be transferred to another ICU)
***Died - to OR
****(you would use this for any patient who has been coded as braindead and is an organ donor to be sent to OR)
 
=== CCI stuff ===
 
==== update component 2 on [[L_CCI_Component_subform]] so it only lists what is allowed ====
*This turns out to be tricky...
 
==== after fixing the CCI page names on wiki, '''add wiki link for CCI codes in CCMDB.mdb''' ====


=== screen refresh reductions ===
=== screen refresh reductions ===
Line 29: Line 10:


== integrity checks checklist ==
== integrity checks checklist ==
{{#ask: [[DICStatus::ready to implement]][[DICApp::CCMDB.mdb]] OR [[DICStatus::needs review]][[DICApp::CCMDB.mdb]]
{{#ask: [[DICStatus::ready to implement]][[DICApp::CCMDB.accdb]] OR [[DICStatus::needs review]][[DICApp::CCMDB.accdb]]
  |?DICStatus = Status
  |?DICStatus = Status
  |limit=3
  |limit=20
  |format=broadtable
  |format=broadtable
  |class=sortable wikitable smwtable
  |class=sortable wikitable smwtable
Line 40: 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 51: 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 61: 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 85: 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 123: 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 132: 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"