Template:ICD10 Guideline AwaitingTransfer: Difference between revisions

Line 10:

</noinclude>=== ~~Definition~~ of ~~when~~ a delay ~~has occurred~~ ===

</noinclude>=== Guidelines for the use of "awaiting" codes ===

~~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]].

==== How much of a delay is required before we code "awaiting"? ====

Code awaiting if [[Dispo DtTm]] is '''not on the same calendar day''' as the [[Transfer Ready date and time]].

We realize this is different from [[Transfer Delay]].

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]].

==== status changes and is no longer awaiting ====

If the transfer is cancelled '''do NOT remove the "awaiting" code'''.

==== status changes and is awaiting different destination ====

If during the wait to leave, the location to which the planned transfer changes, then add the additional Awaiting code, thus can have >1 Awaiting code in this situation.

=== awaiting ambiguous locations ===

Line 25:

Line 33:

* [[Medical Assistance In Dying]]

{{DT|

{{DT|have a check that whenever 1st transfer ready is 1 or more calendar days before dispoDtTM, that there should be at least 1 Awaiting code also.}}

*if the transfer ready DtTm is not the same as the Dispo DtTm, should the data collectors ALWAYS include one of these five ''awaiting delay/transfer reasons'' '''and/or''' any of the OTHER reasons listed here: [[#Possible_reasons_for_delay_that_we_can_actually_code]]. Don't think the collectors know this yet....-- Trish & [[User:JMojica|JMojica]] 17:01, 2018 December 24 (CST)

** As discussed w Allan: the pt could deteriorate. then we would keep the tr date but lose the awaiting code.

~~If the awaiting is rescinded, e.g. patient gets sicker and decision to send person elsewhere is stopped, then remove the waiting. Then this cross check doesn't make sense.~~

*AG REPLY --- this can become very complex and so we decided that:

**(a) if 1st transfer ready is 1 or more calendar days before dispoDtTM, then to not only record that transf ready DtTM but also record the appropriate Awaiting ICD10 code;

**(b) IF the transfer is cancelled do NOT remove either the orig transfer ready DtTM or the Awaiting code,

**(c) if during the wait to leave, the location to which the planned transfer changes, then add the additional Awaiting code, thus can have >1 Awaiting code in this situation,

**(d) have a check that whenever 1st transfer ready is 1 or more calendar days before dispoDtTM, that there should be at least 1 Awaiting code also.}}

@@ Line 10: / Line 10: @@
-</noinclude>=== Definition of when a delay has occurred ===
+</noinclude>=== Guidelines for the use of "awaiting" codes ===
-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]].
+==== How much of a delay is required before we code "awaiting"? ====
+Code awaiting if [[Dispo DtTm]] is '''not on the same calendar day''' as the [[Transfer Ready date and time]].
+We realize this is different from [[Transfer Delay]].
 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]].
+==== status changes and is no longer awaiting ====
+If the transfer is cancelled '''do NOT remove the "awaiting" code'''.
+==== status changes and is awaiting different destination ====
+If during the wait to leave, the location to which the planned transfer changes, then add the additional Awaiting code, thus can have >1 Awaiting code in this situation.
 === awaiting ambiguous locations ===
@@ Line 25: / Line 33: @@
 * [[Medical Assistance In Dying]]
-{{DT|
+{{DT|have a check that whenever 1st transfer ready is 1 or more calendar days before dispoDtTM, that there should be at least 1 Awaiting code also.}}
-*if the transfer ready DtTm is not the same as the Dispo DtTm, should the data collectors ALWAYS include one of these five ''awaiting delay/transfer reasons'' '''and/or''' any of the OTHER reasons listed here: [[#Possible_reasons_for_delay_that_we_can_actually_code]].  Don't think the collectors know this yet....-- Trish & [[User:JMojica|JMojica]] 17:01, 2018 December 24 (CST)
-** As discussed w Allan: the pt could deteriorate. then we would keep the tr date but lose the awaiting code.
-If the awaiting is rescinded, e.g. patient gets sicker and decision to send person elsewhere is stopped, then remove the waiting. Then this cross check doesn't make sense.
-*AG REPLY --- this can become very complex and so we decided that:
-**(a) if 1st transfer ready is 1 or more calendar days before dispoDtTM, then to not only record that transf ready DtTM but also record the appropriate Awaiting ICD10 code;
-**(b) IF the transfer is cancelled do NOT remove either the orig transfer ready DtTM or the Awaiting code,
-**(c) if during the wait to leave, the location to which the planned transfer changes, then add the additional Awaiting code, thus can have >1 Awaiting code in this situation,
-**(d) have a check that whenever 1st transfer ready is 1 or more calendar days before dispoDtTM, that there should be at least 1 Awaiting code also.}}