Edit Data Integrity Check: Service tmp post-send consistency checks

Are you logged on?

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in the group: CCMDB_legit.

Summary (what is the check, one-liner):
links to related pages:
Firmness (is this a warning only (soft check) or will it stop sending (hard check) - applicable only in CCMDB.accdb app):	None/unknown hard check soft check
Timing (does this query run for all records or only complete ones):	None/unknown complete always
Name of the function or query this is implemented as:
Implementation date:
Implementation Status:
L_Problem (are false positive special cases addressed in table L_Problems - applicable only in CFE):	None/unknown Yes No
App:
Backlogged (is this query cleaned up to date or backlogged? Applicable only in CFE):

Free text:

== [[Medicine records]] == For [[Medicine records]], ... {{DJ | * As discussed at [[JALT Meeting - Rolling Agenda and Minutes 2025#JALT 2025-11-27]]: Do we need any post-send, cross-record checks relating to [[Service tmp entry]]? [[User:Ttenbergen|Ttenbergen]] 16:44, 27 November 2025 (CST) }} == [[Critical Care records]] == For [[Critical Care records]], we do not use the [[Service tmp entry]], so no post-sending checks will be performed. == Log == * 2025-11-27 - created page partly to document the decision at [[JALT Meeting - Rolling Agenda and Minutes 2025#JALT 2025-11-27]] to not do post send cross checks for [[Critical Care records]] == Related articles == {{Related Articles}} [[Category:Tmp check]]

Explain your edit, if you think it needs explanation (e.g. "as discussed with ...", or "content moved to ...", or "duplicate content, see ..."):

This is a minor edit

Watch this page

Cancel