Setting up a new CCMDB Data Integrity Check: Difference between revisions

Line 4:

[[Soft checks]] are checks that flag a possible error but still allow the collector to [[send]].

They were one approach to [[CCMDB.accdb cross checks triggering for correct values]].

They were one approach to [[:Category:CCMDB.accdb cross checks triggering for correct values|CCMDB.accdb cross checks triggering for correct values]].

[[Data Integrity Check wiki infrastructure]] explains how these are documented on the wiki.

[[:Category:Data Integrity Check wiki infrastructure]] explains how these are documented on the wiki.

== Timing / Triggering of checks ==

Some fields are checked whenever they change. That led to [[Duplicate error messages]] for values which are checked in relation to each other (e.g. [[Dispo_DtTm]] can't be before [[Visit Admit DtTm]]). Since it is not clear which value is wrong, an error is displayed multiple times as the cross check iterates through vetting all related fields.

So, we are doing many cross checks based on other triggers. Some are only run on [[RecordStatus]]=Complete.

Others (especially for [[Minimal dataset]], run prior to and as part of [[sending]]; those can be run at any time using the [[Pre-send Checker]] to validate data while the collector still has access to a chart.

[[Function TmpChecker]] checks records entered as part of [[Temporary data collection]] / [[Entity–attribute–value model of the L Tmp V2 table]].

[[Category:Data Integrity Checks]]

@@ Line 4: / Line 4: @@
 [[Soft checks]] are checks that flag a possible error but still allow the collector to [[send]].
-They were one approach to [[CCMDB.accdb cross checks triggering for correct values]].
+They were one approach to [[:Category:CCMDB.accdb cross checks triggering for correct values|CCMDB.accdb cross checks triggering for correct values]].
-[[Data Integrity Check wiki infrastructure]] explains how these are documented on the wiki.
+[[:Category:Data Integrity Check wiki infrastructure]] explains how these are documented on the wiki.
+== Timing / Triggering of checks ==
+Some fields are checked whenever they change. That led to [[Duplicate error messages]] for values which are checked in relation to each other (e.g. [[Dispo_DtTm]] can't be before [[Visit Admit DtTm]]). Since it is not clear which value is wrong, an error is displayed multiple times as the cross check iterates through vetting all related fields.
+So, we are doing many cross checks based on other triggers. Some are only run on [[RecordStatus]]=Complete.
+Others (especially for [[Minimal dataset]], run prior to and as part of [[sending]]; those can be run at any time using the [[Pre-send Checker]] to validate data while the collector still has access to a chart.
+[[Function TmpChecker]] checks records entered as part of [[Temporary data collection]] / [[Entity–attribute–value model of the L Tmp V2 table]].
 [[Category:Data Integrity Checks]]