Link suspect visitAdmitDtTm mult to-from-home query: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) No edit summary |
Ttenbergen (talk | contribs) m Text replacement - "|DIC_LProblem=yes" to "|DIC_LProblem=Yes" |
||
| Line 5: | Line 5: | ||
|DIC_coding=''Link_suspect_visitAdmitDtTm_mult_to-from-home'' query | |DIC_coding=''Link_suspect_visitAdmitDtTm_mult_to-from-home'' query | ||
|DIC_status=ready to implement | |DIC_status=ready to implement | ||
|DIC_LProblem= | |DIC_LProblem=Yes | ||
|DIC_app=Centralized data front end.accdb | |DIC_app=Centralized data front end.accdb | ||
|DIC_backlogged=No | |DIC_backlogged=No | ||
Latest revision as of 22:15, 22 July 2025
| 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 |
|
|
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
Related articles
| Related articles: |