Edit Data Integrity Check: Query NDC Postal Code over time

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:	query ''NDC_Postal_Code_over_time''
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:

We compare the consistency of [[Postal Code field]] during a continuous hospital admission. Also see [[query NDC_Bad_Postal_Code]]. == CFE Data Integrity Checks Steps == Comparisons are done after [[vetting]] via NDC query ''NDC_Postal_Code_over_time'' in [[CFE]]. *Steps will be: ==Start Date== 2020-01-09 Cleaning to start from the beginning of 2017 == Related articles == {{Related Articles}} [[Query NDC Bad Postal Code]] [[Category:Data Processing]] [[Category:Postal Codes]] [[Category:Registry checks]]

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