Link suspect not same visitAdmitDtTm query: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 3: Line 3:
|DIC_related_concepts=Visit Admit DtTm field; Dispo; Service/Location; Previous Location; Pre-admit Inpatient Institution
|DIC_related_concepts=Visit Admit DtTm field; Dispo; Service/Location; Previous Location; Pre-admit Inpatient Institution
|DIC_firmness=soft check
|DIC_firmness=soft check
|DIC_coding=query ''Link_suspect_not_same_visitAdmitDtTm''
|DIC_coding=''Link_suspect_not_same_visitAdmitDtTm'' query
|DIC_status=implemented
|DIC_status=implemented
|DIC_LProblem=No
|DIC_LProblem=No

Revision as of 16:15, 2022 February 16

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: true
  • Cargo


  • SMW


  • Categories:  
  • form:

What does this actually check?

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

Log

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)

Related articles

Related articles: