Link_suspect_visitAdmitDtTm_mult_to-from-home 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
Firmness:	hard check
Timing:	always
App:	Centralized data front end.accdb
Coding:	Link_suspect_visitAdmitDtTm_mult_to-from-home query
Uses L Problem table:	yes
Status:	ready to implement
Implementation Date:	not entered
Backlogged:	No

• Cargo

• SMW

• Categories:  

• form:

implement this with L_Problems tie in? tell Pagasa it exists

• SMW

• Cargo

• Categories

What does this actually check?

The query looks for records that:

• have one Visit Admit DtTm
  • less than 2 years ago if full query is too slow
• more than 1 dispo entry that is Discharged to community
• more than 1 Previous Location entry that is Discharged to community

Log

• 2025-03-11 requirement for this query was discussed during JALT Meeting - Rolling Agenda and Minutes 2025#JALT 2025-03-11 to address counterpart to Visit Admit DtTm differences within same admission i.e. same Visit Admit DtTm for different admissions