Template:ICD10 Guideline AwaitingTransfer: Difference between revisions
Jump to navigation
Jump to search
Ttenbergen (talk | contribs) |
Ttenbergen (talk | contribs) m →Old rules and ICD10: moved the question to Panelling or Discharge Planning |
||
| Line 16: | Line 16: | ||
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 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]]. | 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]]. | ||
=== Possible reasons for delay that we can actually code === | === Possible reasons for delay that we can actually code === | ||
Revision as of 14:58, 6 September 2018
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.
Possible reasons for delay that we can actually code
- Physical rehabilitation care
- Palliative care
- Respite care
- Homelessness
- Problem related to unspecified psychosocial circumstances
- Medical Assistance In Dying
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 |
| 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 |
| 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 |
|
"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
- Primary Admit Diagnosis = any awaiting code
- (Transfer Ready DtTm) <> (Arrive DtTm)