Known data errors: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) No edit summary |
||
| Line 23: | Line 23: | ||
|link=all | |link=all | ||
|class=sortable wikitable smwtable | |class=sortable wikitable smwtable | ||
}} | |||
Cargo | |||
{{#cargo_query: | |||
tables=DataIntegrityChecks,Discussions,_pageData | |||
|join on=DataIntegrityChecks._pageName=_pageData._pageName,DataIntegrityChecks._pageName=Discussions._pageName | |||
|fields= | |||
DataIntegrityChecks._pageName=page, Status, Timing, Summary, Status | |||
|where=App="Centralized data front end.accdb " and (Status<>"retired" and Status<>"declined") and (L_Problem=true or L_Problem is null) | |||
|order by=question | |||
|limit=20 | |||
|more results text=Link to table of cross-checks that use L_Problem table to exclude false-positives | |||
|default=Nothing found | |||
|format=dynamic table | |||
|rows per page=20 | |||
}} | }} | ||
Revision as of 22:31, 22 July 2025
Some records have known errors or data that triggers false positives in consistency checks. L Problem is a record of these so they can be excluded from queries. The table would usually be populated by the data collector during vetting.
Instructions for adding a record
If a false positive or known uncorrected error is found:
- open table L Problem from Centralized data front end.accdb
- make a new line
- D_ID field: the D_ID of the record
- Query field: the name of the query that detected this record and from which it should be masked
- Notes field: explanations, eg why the error was not corrected or why it is a false positive
Instructions for using the table in queries
For every query, filter the L Problem table to only records related to that query and only list if null.
List of queries that use L_Problem table (SMW)
(Based on Property:DICLProblem, Property:DICStatus as set in Template:Data Integrity Check.)
| Status | problem | |
|---|---|---|
| Query NDC dx implying death across encounters | implemented | true |
| Link_suspect_visitAdmitDtTm_mult_to-from-home query | ready to implement | true |
| Link suspect mismatch pre inpt ours incomplete query | implemented | true |
| Link suspect mismatch pre inpt should be ours incomplete query | implemented | true |
| Query cardiac arrest throughout admission | ready to implement | true |
| Link suspect negative transit time query | implemented | true |
| Link suspect dead then alive query | implemented | true |
Cargo
| page | Status | Timing | Summary |
|---|---|---|---|
| page | Status | Timing | Summary |
| Query NDC dx implying death across encounters | implemented | always | Category:Diagnosis implying death across encounters |
| Link suspect dead then alive query | implemented | always | Used in Correcting suspect links to find records where an earlier record with that PHIN was listed as dispo field deceased, but a later entry then shows up. |
| Link suspect negative transit time query | implemented | always | Used in Correcting suspect links to find records where an earlier record for a patient with that PHIN has a Dispo DtTm that is later than the next record's Admit DtTm. |
| Link suspect mismatch pre inpt ours incomplete query | implemented | always | Checks for patients where Pre-admit Inpatient Institution is one of ours but we don't have a corresponding record. |
| Link suspect mismatch pre inpt should be ours incomplete query | implemented | always | What is description |
| Query cardiac arrest throughout admission | ready to implement | complete | Any patient who is admitted to ICU from Med or another ICU with a #Cardiac Arrest dx should have one in their immediately preceeding Med or ICU record also. |
| Link suspect visitAdmitDtTm mult to-from-home query | ready to implement | always | Checks for records that are likely part of the same admission but have different Visit Admit DtTm field. |
Other known errors
We store information about some other known errors in the L_Problem table:
Related articles
| Related articles: |