Query Check_VADT_too_close_to_first_boarding_loc

Data Integrity Checks
Summary:	no idea hope JM or LK remember
Related:	Visit Admit DtTm field, Boarding Loc
Firmness:	soft check
Timing:	always
App:	CCMDB.accdb
Coding:	Query Check_VADT_too_close_to_first_boarding_loc
Uses L Problem table:	not relevant for this app
Status:	needs review
Implementation Date:	not entered
Backlogged:	No

	We discussed this in our after-Task meeting 2023-07-23 and I just stumbled across it. I do not remember what this was about, nor what a reasonable delay would be. Could one of you fill in the details for the query if we still want it? No hurry. In fact I'd prefer if you not hurried ;-). Ttenbergen 21:38, 13 August 2025 (CDT) this came about when the Pre-admit Inpatient Institution location is own site and previous location is own ER and the VADT is too close to first boarding loc dttm. If I remember correctly you mentioned 6 hours (0.25d) gap as maybe entry error on the preadmit inpt. Is 12 hours (0.50d) reasonable? --JMojica 09:23, 14 August 2025 (CDT) So this is also about Patients who appear to transfer from in-patient situation to Emergency Room, which would be checked by Query Check_from_ED_and_prev_location_same_site. If the patient is from anywhere else there would be no such thing as vadt being too close to first boarding loc, right? So what is this cut-off, then? Is it a hard check?

Log

2025-07-23 Task post meeting - discussed this query, decided that I would write it up at least so we have a clean discussion trail