Function Validate Chart: Difference between revisions

Latest revision as of 16:11, 11 March 2020

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

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

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

@@ Line 8: / Line 8: @@
 | DIC_firmness = hard check
 | DIC_timing =
-| DIC_app = CCMDB.mdb
+| DIC_app = CCMDB.accdb
-| DIC_coding =
+| DIC_coding =  Function ''Validate_Chart''
 | DIC_status = implemented
 | DIC_implementation_date = 2008-01-01
 }}
-Approximate implementation date
-The numerical-check is relevant because chart is relevant because the field is stored as a string. Reason unknown.
+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}}
 [[Category:Registry checks]]