Link suspect mismatch to ours incomplete query: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary Tag: Reverted |
||
| Line 9: | Line 9: | ||
}} | }} | ||
Follow steps in [[Processing errors in patient data]] to fix errors found. | Follow steps in [[Processing errors in patient data]] to fix errors found. | ||
{{Discuss | who = Pagasa | question = * There is a query Link suspect mismatch to ours incomplete2 (with a 2 at the end) in [[CFE]]. What is the story, and which one do you actually use? }} | |||
== Related articles == | == Related articles == | ||
Revision as of 18:36, 31 October 2018
| Data Integrity Checks | |
| Summary: | Used in Correcting suspect links to find records where an earlier record with that PHIN has a dispo entry corresponding to one of our sites as per the s_dispo table.real_collection, but a later corresponding entry doesn't exist for that location. |
| Related: | PHIN field, Dispo field |
| Firmness: | hard check |
| Timing: | always |
| App: | Centralized data front end.accdb |
| Coding: | query Link suspect mismatch to ours incomplete |
| Uses L Problem table: | Yes |
| Status: | implemented |
| Implementation Date: | not entered |
| Backlogged: | true |
Follow steps in Processing errors in patient data to fix errors found.
|
|
Related articles
| Related articles: |