Link suspect mismatch pre inpt should be ours incomplete query: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 1: Line 1:
{{Data Integrity Check
{{Data Integrity Check
|DIC_summary= What is description  
|DIC_summary= What is description  
|DIC_related_concepts=PHIN; Arrive DtTm field; Dispo DtTm field
|DIC_related_concepts=
|DIC_firmness=hard check
|DIC_firmness=hard check
|DIC_coding=''link_suspect_mismatch_pre_inpt_should_be_ours__incomplete'' query
|DIC_coding=''link_suspect_mismatch_pre_inpt_should_be_ours__incomplete'' query
Line 9: Line 9:
|DIC_backlogged=No
|DIC_backlogged=No
}}
}}
{{Todo
 
| who = Tina
| todo_added = 2022-03-24
| todo_action = 2022-03-24
| question = 
* Was added ages ago but not documented; need to document this. 
** This is done in CCMDB by [[Query check prev pre-admit consistent]] - if we have records in this check then something must be done with the CCMDB version! [[User:Ttenbergen|Ttenbergen]] 15:55, 2022 April 5 (CDT)
}}
Generally follow steps in [[Processing errors in patient data]] to fix errors found.
Generally follow steps in [[Processing errors in patient data]] to fix errors found.


Line 26: Line 19:
{{Discuss | who = Pagasa |question =  
{{Discuss | who = Pagasa |question =  
* You say "Sometimes the error continuous admission the second admission was admitted to ER" - that woldn't come up in this query, though, right? What are you actually telling someone who is doing vac relief with this? [[User:Ttenbergen|Ttenbergen]] 14:24, 2022 March 24 (CDT)
* You say "Sometimes the error continuous admission the second admission was admitted to ER" - that woldn't come up in this query, though, right? What are you actually telling someone who is doing vac relief with this? [[User:Ttenbergen|Ttenbergen]] 14:24, 2022 March 24 (CDT)
** After we talked I initially thought that this was essentially CCMDB [[Query check prev pre-admit consistent]]. But it clearly is something different and I still don't understand what it does. We'll need to discuss again. [[User:Ttenbergen|Ttenbergen]] 16:03, 2022 April 5 (CDT)
}}
}}



Revision as of 16:03, 2022 April 5

Data Integrity Checks
Summary: What is description
Related:
Firmness: hard check
Timing: always
App: Centralized data front end.accdb
Coding: link_suspect_mismatch_pre_inpt_should_be_ours__incomplete query
Uses L Problem table: no
Status: implemented
Implementation Date: not entered
Backlogged: No
  • Cargo


  • SMW


  • Categories: 
  • form:

Generally follow steps in Processing errors in patient data to fix errors found.

Specific error fixing info for this query

  • You have to click the hand shake to see the admission the patient
  • Most of the error on this query the discharged date of the first admission is after the second admission, if the case is this scenario, I just change the discharged date without looking the EPR
  • Sometimes this query triggers as a side effect for errors that are actually link_suspect_mismatch_pre_inpt_should_be_ours__incomplete query, ie error continuous admission the second admission was admitted to ER

PTorres 13:59, 2022 March 24 (CDT)

  • You say "Sometimes the error continuous admission the second admission was admitted to ER" - that woldn't come up in this query, though, right? What are you actually telling someone who is doing vac relief with this? Ttenbergen 14:24, 2022 March 24 (CDT)
    • After we talked I initially thought that this was essentially CCMDB Query check prev pre-admit consistent. But it clearly is something different and I still don't understand what it does. We'll need to discuss again. Ttenbergen 16:03, 2022 April 5 (CDT)
  • SMW


  • Cargo


  • Categories

Still shows records after errors are fixed

If after correcting the errors in this query it still shows entries, re-do Populate linking pairs and it will update the linking error.

log

???

Related articles

Related articles: