L Problem table: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) Created page with "'''L_Problem''' in Centralized_data.mdb contains known errors or false-positives. It is used for recording this information, and for excluding records from check queries...." |
Ttenbergen (talk | contribs) m Text replacement - "[[Category: " to "[[Category:" |
||
| (26 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:L_Problem table}}The [[L_Problem table]] in [[Centralized_data.accdb]] contains [[known data errors]] to exclude them from several [[CFE Data Integrity Checks]]. This could be needed because we deliberately decided they were not worth fixing, or because a [[cross check]] delivers a false positive in some circumstances. | |||
It is manually populated by the [[data processor]] as she encounters the errors or false positives, for example as part of [[vetting]]. | It is manually populated by the [[data processor]] as she encounters the errors or false positives, for example as part of [[vetting]]. | ||
L_Problem contains the fields | L_Problem contains the fields | ||
{| | {| class="wikitable sortable" | ||
|- | |- | ||
| | !| field | ||
!| type | |||
!| description | |||
|- | |- | ||
|Notes || further explanations, eg why the error was not corrected or why it is a false positive | |D_ID || long || unique record ID | ||
} | |- | ||
|Query || text || One of the following: | |||
* query from which to exclude this false positive | |||
* [[Known data errors#Other known errors]] documentation | |||
|- | |||
|Notes || text || further explanations, eg why the error was not corrected or why it is a false positive | |||
|} | |||
=== List of cross-checks that use L_Problems === | |||
{{#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 | |||
}} | |||
== Related Articles == | |||
{{Related Articles}} | |||
[[Category: Data structure]] | [[Category:Data structure]] | ||
[[Category: Data Processing]] | [[Category:Data Processing]] | ||
[[Category:Data Processing]] | |||
[[Category:Centralized data front end.accdb]] | |||
[[Category:Centralized_data.accdb]] | |||
Latest revision as of 11:34, 30 July 2025
The L_Problem table in Centralized_data.accdb contains known data errors to exclude them from several CFE Data Integrity Checks. This could be needed because we deliberately decided they were not worth fixing, or because a cross check delivers a false positive in some circumstances.
It is manually populated by the data processor as she encounters the errors or false positives, for example as part of vetting.
L_Problem contains the fields
| field | type | description |
|---|---|---|
| D_ID | long | unique record ID |
| Query | text | One of the following:
|
| Notes | text | further explanations, eg why the error was not corrected or why it is a false positive |
List of cross-checks that use L_Problems
| 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. |