Edit Data Integrity Check: Query send check centralized is owner

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 ''send_check_centralized_is_owner''
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:

Error: At least one of the patients you are sending already exists in the Centralized_data as a complete patient. You most likely have a record with a wrong location or Patient ID. Or, you might be re-sending a patient you previously sent as complete. Click OK to see a list. This query will usually trigger if * an earlier combination of [[Pat_ID]] and [[Service/Location]] is accidentally re-used on a collector laptop (e.g. should enter HSC_A1-1000 but entered HSC_A1-100) * something went wrong during a previous send and records were not set to "sent" or "completed" properly * a "sent" record was set back to "complete" or "incomplete" on a collector laptop before sending ** this can happen if a cross-check (possibly a recently changed one) triggers on a sent record that is re-opened; in that case, delete the sent record that is causing the error Correct by addressing the issue. == Implementation == Component ''query L_Log_ownerCheck_maker'' makes temporary ''table L_Log_ownerCheck'' which is then compared with local [[L Log table]]. == Log == *2020-04-26 - changed component ''query L_Log_ownerCheck_maker'' to only look at [[D_ID]]s that start with this laptop's [[Laptop identifier]] *2019-10-27 - changed to not include recordstatus "deleted" *2019-03-13 - tweaked query to only use relevant fields of O_L_Log, since it turns out that Access has a maximum record set size of 1GB; hopefully this will fix [[System resource exceeded]] *2019-03 Around this time the STB_MedB laptop had >200 records on it and was getting [[System resource exceeded]] errors. The errors were happening when this query was run. == Related articles == {{Related Articles}} [[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