Link suspect not same visitAdmitDtTm query

Data Integrity Checks
Summary:	Checks for records that are likely part of the same admission but have different Visit Admit DtTm field.
Related:	Visit Admit DtTm field, Dispo, Service/Location, Previous Location, Pre-admit Inpatient Institution
Firmness:	soft check
Timing:	always
App:	Centralized data front end.accdb
Coding:	Link_suspect_not_same_visitAdmitDtTm query
Uses L Problem table:	no
Status:	implemented
Implementation Date:	not entered
Backlogged:	No

• Cargo

• SMW

• Categories:  

• form:

What does this actually check?

As of 2022-02-16 the query looks for records that:

• have different Visit Admit DtTm
• the both Visit Admit DtTms are less than 2 years ago (to reduce query size)
• the earlier is not Dispo to "Home" or "AMA (left against medical advice)"
• both profiles are at the same site
• have a difference of less than 1 day between the dispo at the first location and the Arrive at the second.
• have a difference of less than 7 days between the dispo at the first location and the Arrive at the second and

(

• (first dispo and second Service/Location match OR
• first Service/Location and second Pre-admit Inpatient Institution match OR
• first Service/Location and second Previous Location match OR
• first dispo and second Pre-admit Inpatient Institution or Previous Location

)

Log

• 2022-05-04 - had false positives, updated to also check that the earlier and later record are at the same site
• 2022-04-05 - something went wrong with this query, and likely got corrupted and re-saving it fixed it
• 2022-03-09 - tweaked query to only consider 4th option if at same site.
• 2022-02-16 - updated query to use new Created AdmitDtTm query instead of Accept or Arrive dttm; also pulled some filters into intermediate query to filter earlier to make more efficient Ttenbergen 15:37, 2022 February 16 (CST)