Data Integrity Check under review: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) mNo edit summary |
Ttenbergen (talk | contribs) mNo edit summary |
||
| Line 1: | Line 1: | ||
== Cross checks that need review == | == Cross checks that need review == | ||
Current number of Data Integrity Checks: {{#ask: [[DICStatus::needs review]] |format=count }} | Current number of Data Integrity Checks: {{#ask: [[DICStatus::needs review]] |format=count }} | ||
{{# | |||
{{#cargo_query: | |||
tables=DataIntegrityChecks,Discussions,_pageData | |||
|join on=DataIntegrityChecks._pageName=_pageData._pageName,DataIntegrityChecks._pageName=Discussions._pageName | |||
|fields= | |||
CONCAT("\[\{\{fullurl:",DataIntegrityChecks._pageName, "{{!}}action=edit\}\} edit]")=edit, | |||
DataIntegrityChecks._pageName=page, App, Status, Timing, Firmness, Summary, question, who | |||
|where=DataIntegrityChecks.Status = "needs review" | |||
}} | |order by=question | ||
|limit=100 | |||
|offset=some number | |||
|default=Nothing found | |||
|format=dynamic table | |||
|rows per page=1000 | |||
}} | |||
[[Category:Data Integrity Checks | *]] | [[Category:Data Integrity Checks | *]] | ||
Revision as of 12:46, 15 September 2021
Cross checks that need review
Current number of Data Integrity Checks: 8
| edit | page | App | Status | Timing | Firmness | Summary | question | who | ||
|---|---|---|---|---|---|---|---|---|---|---|
| edit | page | App | Status | Timing | Firmness | Summary | question | who | ||
| edit | Function long LOS() | CCMDB.accdb | needs review | complete | soft check | LOS/Length of Stay should not be unlikely long based on historical LOS for a given ward (Service/Location field). | ||||
| edit | Query check CCI each count vs LOS | CCMDB.accdb | needs review | complete | soft check | Confirm that a Category:Labs Imaging count is not unreasonably high | ||||
| edit | Query check long transfer delay | CCMDB.accdb | needs review | always | soft check | Is the Transfer Delay (Critical Care) or Transfer Delay (Medicine) unreasonably long? | ||||
| edit | Query Import request matcher | DSM Labs Consistency check.accdb | needs review | always | not entered | Records in for which we have patients in L_Log but no lab records from DSM | ||||
| edit | Query s tmp MR | CCMDB.accdb | needs review | complete | hard check | Checks for Project MR | ||||
| edit | Query check tmp AHC | CCMDB.accdb | needs review | complete | hard check | For patients with Previous Location ER at same site there should be a Boarding Loc ER. |
| Lisa | ||
| edit | Query check tmp AHC | CCMDB.accdb | needs review | complete | hard check | For patients with Previous Location ER at same site there should be a Boarding Loc ER. |
| Lisa | ||
| edit | Query Check VADT too close to first boarding loc | CCMDB.accdb | needs review | always | soft check | no idea hope JM or LK remember |
| Lisa | ||
| edit | Query check tmp Overstay2 | CCMDB.accdb | needs review | complete | hard check | Not yet filled in | others? | Julie | ||
| edit | Query Check VADT too close to first boarding loc | CCMDB.accdb | needs review | always | soft check | no idea hope JM or LK remember | We discussed this in our after-Task meeting 2023-07-23 and I just stumbled across it. I do not remember what this was about, nor what a reasonable delay would be. Could one of you fill in the details for the query if we still want it? No hurry. In fact I'd prefer if you not hurried ;-). Ttenbergen 21:38, 13 August 2025 (CDT)
| Julie |