Requested CCMDB changes for the next version: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older edit
TOstryzniuk (talk | contribs)
CCMDB_legit, approved, Bureaucrats, Administrators
27,522 edits
m Text replacement - "[[Category: " to "[[Category:"
 
Line 1: Line 1:
== Requested CCMDB '''changes''' for the ''next version'' ==
''see the [[:Category: Development Documentation | Development Documentation Category]] for other development logs''
*also see [[CCMDB.mdb Change Log 2009]] for changes that have been rolled out to sites.
== Requests ==
==== after fixing the CCI page names on wiki, '''add wiki link for CCI codes in CCMDB.accdb''' ====


=== screen refresh reductions ===
As part of troubleshooting Con's blinky screen Brendan suggested the following:


*''this information was transferred here from ccmdb change log for 2008.''[[User:TOstryzniuk|TOstryzniuk]] 15:06, 29 December 2008 (CST)
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.


== 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 check]]s ready to implement
}}


** ''' There are changes in the master version that were not part of the version current changes are based off. These changes need to be added to the change version before sending it life!'''
== 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
}}


== 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.


===March 2.09-NO LABS and NO Pharmacy===
{ {Todo
*'''CHANGE Suggestion''': next ACCESS version there should be 2 separate check boxes for NO lab and NO Pharm [[User:TOstryzniuk|TOstryzniuk]] 13:29, 2 March 2009 (CST)
| who = Tina
**'''March 30, 2009'''-Hi Trish, We had the same issue with comorbids, and what we did was add a comorbid entry that says “no comorbids”. We then made Access deal with stripping that out. I think this would be better than adding a checkbox. If you add this to the requested changes” I’ll put it in. Tina
| todo_added = 2021-07-21
***sounds good. Go for it.--[[User:TOstryzniuk|TOstryzniuk]] 17:55, 30 March 2009 (CDT)
| todo_action =  
| question = Dev_CCMDB_Data / Dev_CCMDB depending on if CCMDB needs update first.
<provide details of change>
}}


****'''PROBLEM''': there are a few patients who do not have any labs & pharmacy data from the items we are tracking.  ACCESS will not allow a collector to SEND if there is no data in '''BOTH''' LAB and PHARM. One site's workaround is to put EKG into lab field for the sole purpose of getting past this ACCESS restriction. This is not an acceptable workaround.--[[User:TOstryzniuk|TOstryzniuk]] 13:29, 2 March 2009 (CST)
== 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}}


=== Checks and Updates ===
=== renal task checks ===
(currently all done, ready for roll-out)?
* [[Check Renal Tasks]]
*What does this mean does this refer to item above? [[User:TOstryzniuk|TOstryzniuk]] 13:29, 2 March 2009 (CST)
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  |
---------------------


===[[BRR]], [[XBR]] & T6===
* 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)
*If [[Cardiac/Respiratory Arrest | Cardiac Arrest Witnessed 100-2]] in ADMIT or COMPLICATION DX slot then the following '''must''' also be marked:  
** 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.
*For CCMDB.mdb:
*** 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)
**[[ICU_Var 2 | ICU Var 2]] – “[[BRR]]” or “[[XBR]]”


*For Data Cleaner:
=== apache check no longer yellowing fields ===
**[[ICU_Var 2 | ICU Var 2]] – “[[BRR]]” or “[[XBR]]”
apache check is no longer yellowing fields[[User:Ttenbergen|Ttenbergen]] 10:09, 10 January 2012 (CST)
::'''AND'''
*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)
**TISS item [[TISS Neurological | T6-hypothermia/hyperthermia blanket]]
**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)
:I put this back in here, not sure where it went.--[[User:TOstryzniuk|TOstryzniuk]] 15:02, 3 April 2009 (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)


{{Discussion}}
== Previous requests that were not made (with reasons) ==
=== 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.


*what happened to the BRR XBR check that was in this article?  I put it into BRR article under data integrity rule.[[User:TOstryzniuk|TOstryzniuk]] 15:31, 23 March 2009 (CDT)
=== 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.


=== Updates required for Laptops ===
=== sending only lab/pharm sums to centralized_data.mdb ===
* automate the backup to the [[Regional Server]]
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.
* automate a backup to the SD card
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.  
* automate checking for new front-end on every log in to the network
Will leave alone unless main office really wants this done... Ttenbergen 12:35, 2013 November 11 (CST)
* Must be able to enter new files into[[CCMDB.mdb | Access]]
* look into possibility of automatically downloading WIKI guide to laptop each day that it is synch'd. (portable version of guideline)--[[User:TOstryzniuk|TOstryzniuk]] 20:11, 4 April 2009 (CDT)


=== QA Functionality ===
=== Default location field to main collection location ===
There have been requests to default the location field to the main (or only) collection location.
I could set this up, but defaulting these would increase the chances of the data just being left in there if a patient is an exception.
Upon consultation with Trish it was decided not to risk an increase in errors to make this more convenient.
* "There are a number of site collecting on 2 or more units using the same laptop.  We get ward location entry error when there is a default location set."  ... "--[[User:TOstryzniuk|TOstryzniuk]] 12:25, 20 October 2010 (CDT)"
PS: If I enable defaulting for anywhere then I would not be able to disable defaulting for other locations, so it was decided not to have defaulting. [[User:Ttenbergen|Ttenbergen]] 12:44, 12 January 2011 (CST)
I have, though, reduced the location list to only those wards at a given laptop's site. [[User:Ttenbergen|Ttenbergen]] 18:09, 14 July 2011 (CDT)


==== Facilitate exchange of patient discharge times ====
=== Cancel for Settings ===
DCs have to know the discharge times for patients arriving at their wards from another collected ward. We should automate that rather than have them exchange manually. Might be an extension of the status file for Julie...[[User:Ttenbergen|Ttenbergen]] 16:05, 3 February 2009 (CST)
change the settings form to have a save and a cancel button...
* moved a note into [[Admit, Transfer and Discharge date and time]], as this is unrelated to updates to the program. [[User:Ttenbergen|Ttenbergen]] 09:27, 11 February 2009 (CST)


==== Logging errors in the CCMDB.mdb ====
No can do. There are is a sb-form in settings form that would not be cancelled, so having a cancel would be misleading.  
Add a table to the CCMDB that records every time an error is generated with the following details:
* Date/time of error
* patient ID (Hosp Loc Serial)
* Field Identifier
* error descriptor (text)
* erroneous value
Make that table sync to a central repository on send.


===Defer or in Discussion===
=== APACHE lab value limit change request ===
====ARF & CRF & ARI Integrity Check====
*Apache upper limit for creatinine is 2968, which is based on the highest APACHE that was ever in database.  STB has one pt with a creat of 3000 and has requested to change upper limit. Laura K. --[[User:TOstryzniuk|TOstryzniuk]] 12:12, 6 July 2010 (CDT)
*if [[CRF - Chronic Renal Failure|CRF (351)]] in comorbid then [[ARF]] (Diagnosis (350) or [[ARI]] (364) cannot be in admit or complication. (see [[CRF vs ARF, ARI, Renal Transplant]])
** 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)


{{Discussion}}
[[Category:Development Documentation]]
 
[[Category:CCMDB.accdb]]
=====Discussion=====
* The 364 is new since the discussion about the cleaner. What is it about? [[User:Ttenbergen|Ttenbergen]] 15:55, 5 November 2008 (CST)
**Yes, since I have been further reviewing patient profiles in more detail from the problems that SAS has generated, I see renal insufficiency (364)being coded in admit or complication DX slots for patients who have a comorbid condition of chronic renal failure (351).
*The article [[CRF vs ARF, ARI, Renal Transplant]] also mentions something about transplant. Is that still accurate? [[User:Ttenbergen|Ttenbergen]] 14:12, 18 February 2009 (CST)
 
 
==== Ensure that date/time formats are explicit ====
Make sure that Access explicitly looks for the format set out in [[Date and Time Format]], rather than using the PC format.
{{Discussion}}
=====Discussion=====
*Right now [[CCMDB.mdb]] uses dd-mmm-yyyy, e.g. 12 Jan 2009. This is less ambiguous than the standard set out on the wiki. I think it's the better option since it eliminates the chance for transposition errors. I think we should use this format for collection. This does not affect how it is sent to Ed, or how it is stored in Ed's program. If Trish is OK with this, this section should be removed from the change log and [[Date and Time Format]] should be updated accordingly. [[User:Ttenbergen|Ttenbergen]] 12:58, 12 February 2009 (CST)
 
====take out Autopsy YES OR NO====
*ACCESS program is affected because of the way S or E is tied to autopsy on PDA.
*PDA Reader or master database utility programs are not affected if this field is left BLANK.
[[User:TOstryzniuk|TOstryzniuk]] 16:29, 12 December 2008 (CST)
*'''Approved, leave blank'''.[[User:TOstryzniuk|TOstryzniuk]] 05:24, 19 January 2009 (CST)
{{Discussion}}
=====Discussion=====
Julie and Dr. Garland are currently working on moving the whole survive/expire issue into a "Dispo" field. I suggest we wait until they are done rather than implementing this twice. The advantage is that their change will use a data approach (discharge-to has a table) whereas editing the survive/expire options would be a manual change on HanDBase (notoriously unreliable). [[User:Ttenbergen|Ttenbergen]] 13:56, 10 February 2009 (CST)
 
====APACHE II Screen====
*get rid of fields that are not long being collected on the APACHE II screen (SAPS II items).
*total Bilirubin, CPAP, urine CC;s, Urea,SAP_Systolic,
*also - eliminate APACHE II Active TX field.
{{Discussion}}
===== Discussion =====
* Is this for the CCMDB or for HanDBase? Bad idea to mess with HanDBase as it reverts and causes errors for unknown reasons. Since we are moving away from HanDBase, we should leave this alone and let it resolve itself. If it is about an issue in the CCMDB.mdb, please explain further. [[User:Ttenbergen|Ttenbergen]] 13:56, 10 February 2009 (CST)
**CCMDB.mdb only since we are stuck with Handibase and it's problems until everyone is on laptops.[[User:TOstryzniuk|TOstryzniuk]] 13:28, 9 March 2009 (CDT)
***Tina, you do what you need to do to transition from HanDBase to just CCMDB. I know the story about HanDBase.  If you can hide or get rid of these fields from CCMDB then do it. Having fields that are no longer collected creates confusion, especially for new hires.  If this answers your question, then can you remove this discussion. Thanks.--[[User:TOstryzniuk|TOstryzniuk]] 21:03, 4 April 2009 (CDT)
 
====[[Registry Patient Type]] - eliminate this field====
*The Access program is affected because it requires this field to be filled in before sending is allowed.
*PDA Reader or master database utility programs are not affected if this field is left BLANK
*needs to be approved by Critical Care before implementation of change.
[[User:TOstryzniuk|TOstryzniuk]] 16:29, 12 December 2008 (CST)
*'''approved''', leave blank. [[User:TOstryzniuk|TOstryzniuk]] 05:27, 19 January 2009 (CST)
{{Discussion}}
=====Discussion=====
This can be removed in Access and in the output, but I would suggest leaving it alone on the PDA for now due to HanDBase. Access would no longer check for it. If that is OK, this can be moved to "Checks and Updates".[[User:Ttenbergen|Ttenbergen]] 14:00, 10 February 2009 (CST)
 
====APACHE II ACTIVE TX-eliminate this====
*ACCESS program is affected because it makes this a required field (though my understanding is that many data collectors have set default for boxed to be checked).
*PDA Reader or master database utility programs are not affected if this field is left BLANK
*needs to be approved by Critical Care before implementation of this change
[[User:TOstryzniuk|TOstryzniuk]] 16:29, 12 December 2008 (CST)
*Approved, leave blank.  [[User:TOstryzniuk|TOstryzniuk]] 05:25, 19 January 2009 (CST)
{{Discussion}}
=====Discussion=====
* are you saying that ccmdb.mdb will not allow sending a pt with unchecked active tx? [[User:Ttenbergen|Ttenbergen]] 14:25, 11 February 2009 (CST)
**YES.[[User:TOstryzniuk|TOstryzniuk]] 13:35, 9 March 2009 (CDT)
 
====s_Fi02 table in Handibase====
*The S_FI02  (note: with a zero rather than a capital o) is a relic we have been unable to get rid of due to technical problems. It is the mis-spelled table name for S_FIO2 (i.e. capital o). Nothing can be done about it until the PDAs are all gone, so this should be taken out of the change log. (see [[S FI02]] for details; remove the link from there if this is taken out of here.)
[[User:Ttenbergen|Ttenbergen]] 13:30, 10 February 2009 (CST)
 
 
==== Ensure discharge time = 0:00 can't get through ====
to implement check mentioned in [[Admit, Transfer and Discharge date and time]] but not currently working
{{Discussion}}
=====Discussion=====
* Check appears to be working for Admit and Discharge. Can't run check for Transfer time because transfer time is not mandatory. If there is a bug in this, please describe. [[User:Ttenbergen|Ttenbergen]] 12:47, 18 February 2009 (CST)
 
 
 
[[Category: IT Instructions]]
[[Category: Questions IT]]
[[Category: Questions]]

Latest revision as of 11:00, 30 July 2025

see the 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

screen refresh reductions

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.

integrity checks checklist

 Status
Function long LOS()needs review
Query Check_VADT_too_close_to_first_boarding_locneeds review
Query Check_from_ED_and_prev_location_same_siteready to implement
Query check CCI each count vs LOSneeds review
Query check long transfer delayneeds review
Query check_tmp_AHCneeds review
Query check_tmp_Overstay2needs review
Query s_tmp_MRneeds review

Bug Fixes

see Category:Bugs and especially Category:Bugs needing input for bugs with their own article

 StatusModification date"Modification date" is a predefined property that corresponds to the date of the last modification of a subject and is provided by Semantic MediaWiki.
Bug needing input7 November 2012 22:35:09
Combiner tab re-sorts after entering5 October 2022 17:07:01
CCI Picklist tab is slow25 January 2023 16:56:36
Repeat clicks being needed when entering CCI PX Type12 March 2024 15:51:37
Error: There isn't enough free memory to update the display. Close unneeded programs and try again.12 March 2024 16:13:18
Error "Unrecognized database format" when sending9 June 2025 16:17:34
Typing in the dx tab no longer expands to the full dx in Windows 117 August 2025 16:46:36
Error "Invalid SQL statment..." when sending7 November 2025 15:17:49
Error "The database cannot be opened because ..."27 November 2025 04:11:02

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

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.

 Modification date"Modification date" is a predefined property that corresponds to the date of the last modification of a subject and is provided by Semantic MediaWiki.
Bug needing input7 November 2012 22:35:09
CCI Picklist tab is slow25 January 2023 16:56:36
Combiner tab re-sorts after entering5 October 2022 17:07:01
Error "Invalid SQL statment..." when sending7 November 2025 15:17:49
Error "The database cannot be opened because ..."27 November 2025 04:11:02
Error "Unrecognized database format" when sending9 June 2025 16:17:34
Error: There isn't enough free memory to update the display. Close unneeded programs and try again.12 March 2024 16:13:18
Repeat clicks being needed when entering CCI PX Type12 March 2024 15:51:37
Typing in the dx tab no longer expands to the full dx in Windows 117 August 2025 16:46:36

renal task checks

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:

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  |
---------------------
  • 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 is no longer yellowing fieldsTtenbergen 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... Ttenbergen 17:13, 2012 January 31 (CST)
    • 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? --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)

Previous requests that were not made (with reasons)

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.

prevent setting recordstatus from sent to complete

  • Prevent RecordStatus of Sent files being changed from Sent to Incomplete if data altered after file sent inMlaporte 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)

Default location field to main collection location

There have been requests to default the location field to the main (or only) collection location. I could set this up, but defaulting these would increase the chances of the data just being left in there if a patient is an exception. Upon consultation with Trish it was decided not to risk an increase in errors to make this more convenient.

  • "There are a number of site collecting on 2 or more units using the same laptop. We get ward location entry error when there is a default location set." ... "--TOstryzniuk 12:25, 20 October 2010 (CDT)"

PS: If I enable defaulting for anywhere then I would not be able to disable defaulting for other locations, so it was decided not to have defaulting. Ttenbergen 12:44, 12 January 2011 (CST) I have, though, reduced the location list to only those wards at a given laptop's site. Ttenbergen 18:09, 14 July 2011 (CDT)

Cancel for Settings

change the settings form to have a save and a cancel button...

No can do. There are is a sb-form in settings form that would not be cancelled, so having a cancel would be misleading.

APACHE lab value limit change request

  • Apache upper limit for creatinine is 2968, which is based on the highest APACHE that was ever in database. STB has one pt with a creat of 3000 and has requested to change upper limit. Laura K. --TOstryzniuk 12:12, 6 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. Ttenbergen 08:53, 12 July 2010 (CDT)
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Requested_CCMDB_changes_for_the_next_version&oldid=166754"