Soft checks: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
Created page with "Some of our cross checks are implemented as "soft checks", where the collector can still send data even if a check is triggered. These are for scenarios where a trigger usually means that something went wrong, but there are scenarios where the entry is actually correct. == When multiple soft checks trigger, only one will be visible == One of the problems with our current implementation is that, if there is more than one triggered soft check, only one will be visible. T..."
 
 
Line 6: Line 6:
== List of soft checks ==
== List of soft checks ==
{{#cargo_query:
{{#cargo_query:
tables=DataIntegrityChecks,Discussions,_pageData
tables=DataIntegrityChecks
|join on=DataIntegrityChecks._pageName=_pageData._pageName,DataIntegrityChecks._pageName=Discussions._pageName
|fields=DataIntegrityChecks._pageName=check, Status, Timing, Summary
|fields=
|where=Firmness="soft check" and Status not in ("declined", "not feasible", "retired")
CONCAT("\[\{\{fullurl:",DataIntegrityChecks._pageName, "{{!}}action=edit\}\} edit]")=edit,
|order by=_pageName
DataIntegrityChecks._pageName=page, Coding, Status, Timing, Firmness, Summary, question, who
|where=Firmness="soft check"
|order by=question
|limit=1000
|limit=1000
|offset=some number
|default=no soft checks found
|default=Nothing found
|format=dynamic table
|format=dynamic table
|rows per page=1000
|rows per page=1000
}}
}}


== Related articles ==  
== Related articles ==  

Latest revision as of 13:46, 2023 May 24

Some of our cross checks are implemented as "soft checks", where the collector can still send data even if a check is triggered. These are for scenarios where a trigger usually means that something went wrong, but there are scenarios where the entry is actually correct.

When multiple soft checks trigger, only one will be visible

One of the problems with our current implementation is that, if there is more than one triggered soft check, only one will be visible. This is because our original implementation relied on the idea that we only need to show one problem at a time, since that problem would have to be fixed, and when it gets fixed any other issue would then show up. Since the problem might never be fixed in the case of soft checks, only the last one checked would be visible.

List of soft checks

check Status Timing Summary
check Status Timing Summary
Function long LOS() needs review complete LOS/Length of Stay should not be unlikely long based on historical LOS for a given ward (Service/Location field).
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 not same visitAdmitDtTm query implemented always Checks for records that are likely part of the same admission but have different Visit Admit DtTm field.
PL Diff Phin SameLN FN DOB implemented always Checks that there are no likely matches of this patient with a different PHIN (ie typos)
PL SamePHIN Site Diff chart implemented always Another record exists for this site with the same PHIN and a different Chart number.
Query check CCI each count vs LOS needs review complete Confirm that a Category:Labs Imaging count is not unreasonably high
Query check CCI TISS discontinuous ETT implemented complete T22 - ETT Present (TISS Item) should start with an T40 - Insertion of ETT (TISS Item) and end with an T28 - Planned extubation (TISS Item) or T29 - Unplanned extubation (TISS Item).
Query check ICD10 ESRD and AKI only if transplant implemented complete A patient who has an ESRD dx and an AKI dx is an error unless they also have a kidney transplant CCI.
Query check ICD10 trach has trach but no TISS implemented always If there is a Tracheostomy, has one (Z93.0) ICD10, there should likely be a T23 - Trach Tube Present (TISS Item)
Query check long transfer delay needs review always Is the Transfer Delay (Critical Care) or Transfer Delay (Medicine) unreasonably long?
Query check pt from ER implemented always part of validating Boarding Loc
Query s tmp Boarding Loc ER delay reasonable implemented complete Flags Boarding Loc entries for ERs where a second Boarding Loc entry exists that is less than 30 min later or more than 67 hours later for CC or more than 144 hrs later for Med

Related articles

Related articles: