Function Validate Chart: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m nothing changed, just confirming that the >8 digit check was being run.
 
(3 intermediate revisions by 2 users not shown)
Line 8: Line 8:
| DIC_firmness = hard check
| DIC_firmness = hard check
| DIC_timing =
| DIC_timing =
| DIC_app = CCMDB.mdb
| DIC_app = CCMDB.accdb
| DIC_coding =  Function ''Validate_Chart''
| DIC_coding =  Function ''Validate_Chart''
| DIC_status = implemented
| DIC_status = implemented
Line 17: Line 17:


== Log ==
== Log ==
* 2020-03-11 - confirmed again that a 9-digit chart will throw error; emailed Pagasa
* 2019-09-15 - Confirmed again that this check seems to hold; asked Pagasa to flag if [[PL Chart 9 Digit]] triggers again
* 2019-08-22 - [[PL Chart 9 Digit]] was triggered even though this check exists
* 2008-01-01 - Approximate implementation date
* 2008-01-01 - Approximate implementation date



Latest revision as of 16:11, 2020 March 11

Data Integrity Checks
Summary: validates the Chart number:
  • Chart must be numerical
  • chart must be
  • checks Function PHIN same as Chart
  • no further checks at this time because chart numbers are different at different hospitals
Related: PHIN, Chart number
Firmness: hard check
Timing:
App: CCMDB.accdb
Coding: Function Validate_Chart
Uses L Problem table: not relevant for this app
Status: implemented
Implementation Date: 2008-01-01
Backlogged: true
  • Cargo


  • SMW


  • Categories:  
  • form:

The numerical-check is relevant because the field is stored as a string. Reason unknown.

Log

  • 2020-03-11 - confirmed again that a 9-digit chart will throw error; emailed Pagasa
  • 2019-09-15 - Confirmed again that this check seems to hold; asked Pagasa to flag if PL Chart 9 Digit triggers again
  • 2019-08-22 - PL Chart 9 Digit was triggered even though this check exists
  • 2008-01-01 - Approximate implementation date

Related articles

Related articles: