Query check ICD10 needs awaiting if TR Dt and Dispo Dt on diff days: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
mNo edit summary
Line 9: Line 9:
| DIC_implementation_date = 2018-11-24
| DIC_implementation_date = 2018-11-24
}}
}}
{{DT | 2018-11-27 - suspended this check because it has false positives; we also consider ACP-C as transfer ready. Need to figure out if we can check this at all.}}
== Awaiting code but no date diff ==
We already check for this as part of [[Query check_ICD10_awaiting_has_Transfer_Ready_DtTm]].


== Date diff but no awaiting code ==
== Date diff but no awaiting code ==
Line 27: Line 22:
* If a patient is ready for transfer/discharge, but has an unexpected complication, we still keep the original transfer ready date, even though their discharge is put on hold.  
* If a patient is ready for transfer/discharge, but has an unexpected complication, we still keep the original transfer ready date, even though their discharge is put on hold.  
** as per [[Template:ICD10 Guideline AwaitingTransfer]] we will keep them
** as per [[Template:ICD10 Guideline AwaitingTransfer]] we will keep them
== Awaiting code but no date diff ==
We already check for this as part of [[Query check_ICD10_awaiting_has_Transfer_Ready_DtTm]].


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

Revision as of 13:40, 2019 January 22

Data Integrity Checks
Summary: Any patient with a with Transfer Ready DtTm and Dispo DtTm on different days has to have one of the "awaiting" codes and vice versa.
Related: Transfer Ready DtTm, Dispo DtTm, [[Awaiting/delayed transfer to long-term care/PCH inside or outside of Winnipeg]], [[Change from Awaiting/delayed dx codes to Transfer Ready DtTm]], [[Check if awaiting code is primary dx then Transfer Ready DtTm must be equal to Arrive DtTm]], [[Template:ICD10 Guideline AwaitingTransfer]], [[Query check ICD10 needs awaiting if TR Dt and Dispo Dt on diff days]], [[Task Team Meeting - Rolling Agenda and Minutes 2021]]
Firmness: hard check
Timing: complete
App: CCMDB.mdb
Coding: query check_ICD10_needs_awaiting_if_TR_Dt_and_Dispo_Dt_on_diff_days'
Uses L Problem table: not relevant for this app
Status: needs review
Implementation Date: 2018-11-24
Backlogged: true
  • Cargo


  • SMW
"CCMDB.mdb" is not in the list (CCMDB.accdb, Centralized data front end.accdb, TISS28.accdb, SAP, DSM Labs Consistency check.accdb, not entered) of allowed values for the "DICApp" property. Property "DICRelatedConcepts" (as page type) with input value "Awaiting/delayed transfer to long-term care/PCH inside or outside of Winnipeg" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process., Property "DICRelatedConcepts" (as page type) with input value "Change from Awaiting/delayed dx codes to Transfer Ready DtTm" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process., Property "DICRelatedConcepts" (as page type) with input value "Check if awaiting code is primary dx then Transfer Ready DtTm must be equal to Arrive DtTm" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process., Property "DICRelatedConcepts" (as page type) with input value "Template:ICD10 Guideline AwaitingTransfer" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process., Property "DICRelatedConcepts" (as page type) with input value "Query check ICD10 needs awaiting if TR Dt and Dispo Dt on diff days" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process., Property "DICRelatedConcepts" (as page type) with input value "Task Team Meeting - Rolling Agenda and Minutes 2021" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  • Categories: 
  • form:

Date diff but no awaiting code

There are transfer ready reasons that would not result in an awaiting code. These resulted in false positives. If we want to check for date diff but no awaiting code we will need to enumerate these reasons, and all need to be present in data. I will put aside this half of the query until we address that. Details in wiki page. 
  • SMW


  • Cargo


  • Categories

Additional dx codes that might act as "transfer ready" signal? Or do they?

  • Palliative care
  • Respite care
  • ACP-C, but we don't code taht as a dx for now, do we?
  • we don't have a code for "awaiting transfer within same hospital" from ICU
  • deemed medically stable on same date as transfer to a subacute ward at same facility-entered delay for awaiting transfer to another facility, but sent to another ward at same facility, now getting error message
  • At HSC, when a patient moves to RR6 they are considered transfer ready. This would include patients that are on long term antibiotic therapy that aren't candidates for the CIVP program. There isn't really a code to explain that...
  • If a patient is ready for transfer/discharge, but has an unexpected complication, we still keep the original transfer ready date, even though their discharge is put on hold.

Awaiting code but no date diff

We already check for this as part of Query check_ICD10_awaiting_has_Transfer_Ready_DtTm.

Related articles

Related articles: