Template:ICD10 Guideline AwaitingTransfer: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older editNewer edit →
m →‎Possible reasons for delay that we can actually code: hopefully if someone can think of others they will still put them in here
mNo edit summary
Line 34: Line 34:
* [[Medical Assistance In Dying]]
* [[Medical Assistance In Dying]]


=== {{CCMDB Data Integrity Checks|ready to implement}} - If this code is present, [[Transfer Ready DtTm]] must be filled in and vice versa===
=== Cross-checks===
* Any patient who has this code has to have a [[Transfer Ready DtTm]].  
{{Data Integrity Check
* Any patient with a with [[Transfer Ready DtTm]] and [[Dispo DtTm]] on different days has to have one of the "awaiting" codes
| DIC_summary = Any patient who has this code has to have a [[Transfer Ready DtTm]].  
| DIC_related_concepts = [[Transfer Ready DtTm]]
| DIC_firmness = hard check
| DIC_app = CCMDB.mdb
| DIC_coding = TBA
| DIC_status = ready to implement
| DIC_implementation_date = TBA
}}


==={{CCMDB Data Integrity Checks|ready to implement}} - If this code is primary dx transfer data must equal arrive date ===
{{Data Integrity Check
| DIC_summary = Any patient with a with [[Transfer Ready DtTm]] and [[Dispo DtTm]] on different days has to have one of the "awaiting" codes
| DIC_related_concepts = [[Transfer Ready DtTm]],[[Dispo DtTm]]
| DIC_firmness = hard check
| DIC_app = CCMDB.mdb
| DIC_coding = TBA
| DIC_status = ready to implement
| DIC_implementation_date = TBA
}}
 
{{Data Integrity Check
| DIC_summary = If this code is [[Primary Admit Diagnosis]]/[[Dx Primary]] then [[Transfer Ready DtTm]] must equal [[Arrive DtTm]]
| DIC_related_concepts = [[Arrive DtTm]], [[Transfer Ready DtTm]], [[Primary Admit Diagnosis]]/[[Dx Primary]]
| DIC_firmness = hard check
| DIC_app = CCMDB.mdb
| DIC_coding = TBA
| DIC_status = ready to implement
| DIC_implementation_date = TBA
}}
 
{{Discuss | who=Tina | question = "Panelling_admit_transfer_same" looks like an existing function, will need to review this when implementing }}
* Panelling_admit_transfer_same(Pat_ID): a record is an error if both
* Panelling_admit_transfer_same(Pat_ID): a record is an error if both
** [[Primary Admit Diagnosis]] = any awaiting code
** [[Primary Admit Diagnosis]] = any awaiting code
** ([[Transfer Ready DtTm]]) <> ([[Arrive DtTm]])
** ([[Transfer Ready DtTm]]) <> ([[Arrive DtTm]])

Revision as of 13:39, 2018 September 6

This template contains details common to all pages in Category:Awaiting/delayed transfer.

To use: 

{{ICD10 AwaitingTransfer}}


awaiting ambiguous locations

See Care levels in the community.

Definition of when a delay has occurred

For the purpose of these diagnosis codes we define a Transfer Delay as having occurred if the Dispo DtTm is not on the same day as the Transfer Ready date and time. For example, if patient was transfer ready on Tuesday, but left on Wednesday or thereafter, use one of the codes in Category:Awaiting/delayed transfer.

Old rules and ICD10

Template:ICD10

Template:DiscussAllan

Template:Discussion

  • Do those cross checks seem reasonable with these new codes?

Possible reasons for delay that we can actually code

Cross-checks

Data Integrity Checks
Summary: Any patient who has this code has to have a Transfer Ready DtTm.
Related: [[Transfer Ready DtTm]]
Firmness: hard check
Timing: always
App: CCMDB.mdb
Coding: TBA
Uses L Problem table: not relevant for this app
Status: ready to implement
Implementation Date: TBA
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.
  • Categories:  
  • form:


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
Related: [[Transfer Ready DtTm,Dispo DtTm]]
Firmness: hard check
Timing: always
App: CCMDB.mdb
Coding: TBA
Uses L Problem table: not relevant for this app
Status: ready to implement
Implementation Date: TBA
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 "Transfer Ready DtTm]],[[Dispo DtTm" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  • Categories:  
  • form:


Data Integrity Checks
Summary: If this code is Primary Admit Diagnosis/Dx Primary then Transfer Ready DtTm must equal Arrive DtTm
Related: [[Arrive DtTm, Transfer Ready DtTm, Primary Admit Diagnosis/Dx Primary]]
Firmness: hard check
Timing: always
App: CCMDB.mdb
Coding: TBA
Uses L Problem table: not relevant for this app
Status: ready to implement
Implementation Date: TBA
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 "Arrive DtTm]], Transfer Ready DtTm, Primary Admit Diagnosis/[[Dx Primary" contains invalid characters or is incomplete and therefore can cause unexpected results during a query or annotation process.
  • Categories:  
  • form:

"Panelling_admit_transfer_same" looks like an existing function, will need to review this when implementing

  • SMW


  • Cargo


  • Categories
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Template:ICD10_Guideline_AwaitingTransfer&oldid=119183"