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
mNo edit summary
 
(509 intermediate revisions by 12 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''
''see [[TISS28.mdb Change Log]] for TISS28 Access Program changes
==Priority Bug Fix==
none currently Ttenbergen 19:45, 2013 October 17 (CDT)
==New change request==
   
   
====waiting for final review on Nov 7.13====
== Requests ==
# add new New TMP [[TmpV2]] project to ccmdb.  See [[Comfort Care]].[[User:TOstryzniuk|Trish Ostryzniuk]] 12:20, 2013 November 8 (CST)
==== after fixing the CCI page names on wiki, '''add wiki link for CCI codes in CCMDB.accdb''' ====
# change S_AllDiagnosis wording from 90400-Palliative Care to 90400-[[Palliative Service]].[[User:TOstryzniuk|Trish Ostryzniuk]] 12:20, 2013 November 8 (CST)


===Sept/Oct 2013===
=== screen refresh reductions ===
*[[Centralized_data.mdb]] - Fix SendDtTm.  Patient that are entered onto laptop AND completed BETWEEN sending dates each week, are missing SendDtTm stamp.  Details as per email sent today. [[User:TOstryzniuk|Trish Ostryzniuk]] 17:51, 2013 October 21 (CDT)
As part of troubleshooting Con's blinky screen Brendan suggested the following:  
** Could you please '''Use 24 clock  for TIME for the SendDtTm stamp, same format and other times'''.[[User:TOstryzniuk|Trish Ostryzniuk]] 11:36, 2013 October 28 (CDT).[[User:TOstryzniuk|Trish Ostryzniuk]] 18:00, 2013 November 6 (CST) 
* Make available to main office: the database that includes all patient identifiers, that are stripped out of centralized so Main office can starting practicing with how we will be able to work with it on go forward basis.  Thank you.[[User:TOstryzniuk|Trish Ostryzniuk]] 17:50, 2013 October 18 (CDT)
* add sending collector name to centralized. Ttenbergen 15:31, 2013 October 17 (CDT)
* change "send date" in centralized to be populated by "most recent update date" Ttenbergen 15:31, 2013 October 17 (CDT)
* [[Centralized_data.mdb_Change_Log#time_sent_and_time_completed]]
* generate request to notify Pagasa if location changed after first send (generates duplicate entries) Ttenbergen 16:23, 2013 September 11 (CDT)
* update send code for Labs and Pharmacy to only send summary record to centralized, not individual lines. Ttenbergen 17:37, 2013 September 12 (CDT)


=== checks for minimal data admit/discharge ===
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.
* [[Admit,_Transfer_and_Discharge_date_and_time#Early_date_consistency_checks]]


=== Mandating colours ===
== integrity checks checklist ==
{{discussion}}
{{#ask: [[DICStatus::ready to implement]][[DICApp::CCMDB.accdb]] OR [[DICStatus::needs review]][[DICApp::CCMDB.accdb]]
Several versions ago there was a discussion re. mandating Overstay colours. At the time Trish asked me not to make this mandatory, and I cautioned that this will lead to unreliable data. The question was not resolved. Trish, Julie, are you both OK with non-mandated Overstay colours? Ttenbergen 12:25, 2013 August 29 (CDT)
  |?DICStatus = Status
*I never said that. What is this about?  There was an email sent to you about making color visible and also about collector having to press confirm to record which color final that was posted.[[User:TOstryzniuk|Trish Ostryzniuk]] 17:11, 2013 September 19 (CDT)
  |limit=20
** I had suggested making it mandatory for _every_ patient to have a colour before _any_ patient could be sent. At the time I understood that you were worried that this might keep collectors from sending, that there might be some legit reason they would have demographics for a patient but not yet an overstay colour. If this is no longer a concern I can implement this check. Ttenbergen 20:03, 2013 October 17 (CDT)
  |format=broadtable
***I see workarounds if color is mandatory for every single patient on laptop before sending. There are number of scenarios where staff cannot ideally complete all required data to generate a color before a send date each weel such as; vacation relief available or not, sick relief, short week due to stat days. Minimal data set will be collected even more on paper and not entered into laptop before a send date. The data would be entered just after a send date so that sending is not impeded. A color will be generated even if not final, just so sending is not blocked. This makes it unreliable also. [[User:TOstryzniuk|Trish Ostryzniuk]] 17:50, 2013 October 18 (CDT)
  |class=sortable wikitable smwtable
* do additional error checking on the overstay questions to make sure one of each is present, or corresponding "missing"s. Ttenbergen 17:04, 2013 March 14 (EDT)
|default=No cross checks ready to implement
}}


== Bug Fixes ==
== Bug Fixes ==
''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]]
|?DICStatus = Status
|?Modification date
|sort=Modification date
|order=ascending
|limit=20
|format=broadtable
|link=all
|class=sortable wikitable smwtable
}}


== Next Round of Data Changes ==
== Next Round of Data Changes ==
None currently Ttenbergen 15:03, 2013 March 11 (EDT)
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 ==
''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]]
|?Modification date
|default=No corresponding old article found
|format=broadtable
|limit=100
|link=all
|headers=show}}


===Chinese in TMPV2 ===
=== renal task checks ===
[[Chinese characters being sent to TmpV2]] moved here because likely fixed, and if not, need more info. Ttenbergen 10:44, 2013 July 29 (CDT)
* [[Check Renal Tasks]]
 
=== Overstay update for palliative patients ===
If I understood correctly at the data collector meeting we are going to make the following changes:
* add a subcode to diagnosis [[Palliative Care#survival not expected]] to indicate survival is not expected.
** '''can't proceed with this until the questions at the link above are addressed {{discussion}}
***will take this to task group meeting.[[User:TOstryzniuk|Trish Ostryzniuk]] 17:17, 2013 July 3 (CDT)
**** as per minutes from meeting: ''"TO raised the question of how to define and code “palliative care” in the Medicine Database.  While Dr. Roberts desires this as an exclusion in the ward Overstay project, it is not entirely clear what information he is seeking, as the term can indicate a number of different concepts.  Towards figuring out how to get that information, AG will send and email to Dr. Roberts to inquire."'' Ttenbergen 10:53, 2013 July 15 (CDT)
 
==Changes Under Discussion ==
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.  
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:
See [[:Category:Potential Change]] as well, this are only changes without a home article.
* 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 ===
=== 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  
* '''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  
Line 64: 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 76: Line 79:
**** been a while, I'll review and let you know what this is about. Ttenbergen 13:55, 2013 January 29 (EST)
**** been a while, I'll review and let you know what this is about. Ttenbergen 13:55, 2013 January 29 (EST)


=== Pharmacy Tally ===
== Previous requests that were not made (with reasons) ==
*Would it be possible to have a line showing the cumulative totals of treatment days for the Pharm drugs collected in this field? (as in Labs)10:04, 2012 December 21 (EST)
=== DOB format ===
** How would this help with collection? I am asking to find out if there might be more to it. For example, are you trying to compare the summary to something else, maybe that can be built in as well. I just need to understand how you would use this. Ttenbergen 10:14, 2012 December 21 (EST)
* "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)
*** moved this request here. If there are no further comments on it within 2 weeks then this section can please be delete by whoever stumbles on it next. Ttenbergen 16:28, 2013 March 11 (EDT)
** 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 in[[User:Mlaporte|Mlaporte]] 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)


== 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 94: 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 102: 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"