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) No edit summary |
||
| Line 14: | Line 14: | ||
{{DT | | {{DT | | ||
* implement this | * implement this | ||
* with L_Problems tie in | * with L_Problems tie in | ||
* tell Pagasa it exists}} | * tell Pagasa it exists}} | ||
Revision as of 13:46, 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: |