Accept DtTm field: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
m (Accept dtTm Field - working on it)
mNo edit summary
 
(140 intermediate revisions by 16 users not shown)
Line 1: Line 1:
  ''This field is currently being implemented, please check the instructions and put a discussion for anything that isn't clear. ''
{{Todo
 
| who = Tina
 
| todo_added = 2022-06-30
The [[Accept DtTm field]] contains the date and time when the attending physician accepts a patient. If there is a change in service then it is the date and time of the change from the [[Previous Service field|Previous '''Service''' field]] to the current [[Service/Location field]].
| todo_action = 2023-05-04
 
  | question =  _ccmdb_dev
 
* Field is legacy; once no longer used, remove it from sending and then from ccmdb_data. Query to check:
::SELECT L_Log.D_ID, L_Log.RecordStatus, L_Log.Accept_DtTm, L_Log.Arrive_DtTm
::FROM L_Log
::WHERE (((L_Log.RecordStatus)="incomplete") AND ((L_Log.Accept_DtTm) Is Not Null) AND ((L_Log.Arrive_DtTm) Is Not Null));
* 98 left as of 2022-08-04
* None left as of 2023-05-04, field can be removed...  
** remove from sending
** remove from CCMDB_data
}}


{{Data element
|field_name=Accept DtTm
|CCMDB_label=Accept DtTm
|in_table=L_Log table
|data_type=date
|program_collecting=Med and CC
|created_raw=Raw
|data_element_start_date=2016-07-01
|data_element_end_date=2022-04-22
|data_element_sort_index=43
|element_description=First [[Service tmp entry]] DtTm for pts who came from the '''ER department''' only
}}
== Collection Instruction ==
== Collection Instruction ==
For all patients, if there is a record of the date/time that the service physician accepted the patient, enter this as the Accept DtTm. Collect this wherever available, but it is especially important for patients coming from ER.  
For each patient, enter First [[Service tmp entry]] DtTm for pts who came from the same hospital's the '''ER department''' only (i.e. who had an initial [[Boarding Loc]] of ER). Follow the instructions at [[Service tmp entry]].
If the patient is accepted and arrives at the same time, or if there is no clear record of the accept date/time, enter the [[Arrive_DtTm field]] and then click the "set accept_DtTm to Arrive_DtTm" button to copy the DtTm across.  


If the [[Accept DtTm field|Accept DtTm]] > [[Arrive DtTm field|Arrive DtTm]], make accept = arrive.  
This means the {{PAGENAME}} should be equal to the first [[Service tmp entry]] DtTm if it is entered at all.


== Planned elimination of this field ==
see [[Change to replace Accept DtTm with first Service tmp entry, and Arrive DtTm with first Boarding Loc]]


===Possible documentation locations===
== Data Use ==
* admission/separation registers
[[Patient flow]]
* Physician Order sheet when being transferred ie: "May transfer to D5/ non-teaching" or in Progress note section MD may write transfer plan pending bed.--[[User:Llemoine|Llemoine]] 15:11, 2016 May 9 (CDT)
* medicine program: to monitor delays to move patient from ER to Med ward bed
* For all the patients  from ER and for PARR patients, the orders are a good source of data for this.  For the other previous locations (wards and other hospital icu’s and wards) this is not a consistently accurate source. (Laura via email)
* as of July 2016 onward - ICU same purpose
Accept DtTm is used as part of the formula to calculate delay in the transfer of patient from ER bed to Med ward or ICU bed - see [[ER Delay]]. This measures the amount of time for the patient already accepted in Medicine or Critical Care service but still using the ER bed and resources.


== Questions ==
{{Data Integrity Check List}}
=== ward to ward ===
* When a pt moves from ward to ward do you want us enter the date & time the transfer order is written in the "Accept DtTM"  or the time the pt actually arrived to the unit and comes under the care of the new unit?  In ER, once an order is written for a pt to transfer to a ward the accepting service will care for the pt. in ER. Ward to ward transfers are different. When a pt transfers from ward to ward sometimes the service or physician will continue the care for the pt. on the new unit & sometimes they do not.
** {{discussion}} Julie, Tina and Trish are still discussing this. Ttenbergen 16:52, 2016 May 16 (CDT)
** A good example is a patient that is located in ICMS at STB who has been accepted by CCU attending during their stay in the ICU.  When they get transferred to CCU, the CCU data collector would be tempted to put the accept time documented in the transfer orders, however the same service was covering the pt during their stay in the ICU so this is a problem.  I did discuss this with Julie and she said that we already track these types of patients in the tmp by putting the CCU service entry so it would only be confusing and skew the purpose of the accept dttm to document the accept time in CCU as per the orders.  She suggested just putting the same time as the arrive dttm to CCU in this example.  --[[User:LKolesar|LKolesar]] 12:47, 2016 May 19 (CDT)


=== delay between acceptance and arrival ===
== Legacy ==
* I don't think this is feasible. A patient can be accepted (ie - order written to transfer to D5) but cannot go until an actual bed is available which may take a number of days. In the meantime the original ward that the patient is on, is still collecting data.--[[User:CMarks|CMarks]] 07:53, 2016 May 10 (CDT)
{{Collapsable
** so which service and physician is responsible for that patient in the meantime? Ttenbergen 10:22, 2016 June 23 (CDT)
| always=Click to see legacy info
| full=
* related info: [[Change to start collection at accept rather than arrive time]]
* 2017_January:  also enter lines in TMP for all [[AcceptDateSource]]s.


** {{discussion}} Julie, Tina and Trish are still discussing this. Ttenbergen 16:52, 2016 May 16 (CDT)
* The source for gathering the accept date/time may vary from site to site see [[#Possible documentation locations]]


== Data Use ==
*This field is part of the [[2016 Time and Place changes]].
Many things, need to pull them together Ttenbergen 12:59, 2016 March 21 (CDT)
**For '''medicine''' this concept is ''related'' to [[admit date and time]] (when pt is from ER). It does not simply replace the field, so this value still needs to be entered for patients not from ER. Resp. field L_Log.R_AdmDate and L_Log.R_AdmTime
 
**For '''critical care''' this concept is related to [[Service Sending to ICU]]. (There is no comparable field in ICU for this in the old system).
== {{CCMDB Data Integrity Checks}} ==
}}
* Function ''[[Dispo Chronological]]''
 
== Legacy ==
This field is part of the [[2016 Time and Place changes]].


For '''medicine''' this concept is ''related'' to [[admit date and time]] (when pt is from ER). It does not simply replace the field, so this value still needs to be entered for patients not from ER.
== Related articles ==
{{Related Articles}}


For '''critical care''' this concept is related to [[Service Sending to ICU]]. (There is no comparable field in ICU for this in the old system).


[[Category: 2016 Time and Place changes]]
[[Category:2016 Time and Place changes]]
[[Category: Admit/Discharge]]
[[Category:Admit/Discharge]]
[[Category:Data Collection Guide]]

Latest revision as of 17:16, 2023 May 4

_ccmdb_dev

  • Field is legacy; once no longer used, remove it from sending and then from ccmdb_data. Query to check:
SELECT L_Log.D_ID, L_Log.RecordStatus, L_Log.Accept_DtTm, L_Log.Arrive_DtTm
FROM L_Log
WHERE (((L_Log.RecordStatus)="incomplete") AND ((L_Log.Accept_DtTm) Is Not Null) AND ((L_Log.Arrive_DtTm) Is Not Null));
  • 98 left as of 2022-08-04
  • None left as of 2023-05-04, field can be removed...
    • remove from sending
    • remove from CCMDB_data
  • added: 2022-06-30
  • action: 2023-05-04
  • Cargo


  • Categories


 
 
 
 

Legacy Content

This page contains Legacy Content.
  • Explanation: This is a legacy data field, its DataElementEndDate is in the past.
  • Successor: No successor was entered

Click Expand to show legacy content.

Data Element (edit)
Field Name: Accept DtTm
CCMDB Label: Accept DtTm
CCMDB tab: not stated
Table: L_Log table
Data type: date
Length: not stated
Program: Med and CC
Created/Raw: Raw
Start Date: 2016-07-01
End Date: 2022-04-22
Sort Index: 43

First Service tmp entry DtTm for pts who came from the ER department only

  • SMW

Legacy implementation right in the table

  • Cargo


  • Categories
  • Forms


Collection Instruction

For each patient, enter First Service tmp entry DtTm for pts who came from the same hospital's the ER department only (i.e. who had an initial Boarding Loc of ER). Follow the instructions at Service tmp entry.

This means the Accept DtTm field should be equal to the first Service tmp entry DtTm if it is entered at all.

Planned elimination of this field

see Change to replace Accept DtTm with first Service tmp entry, and Arrive DtTm with first Boarding Loc

Data Use

Patient flow

  • medicine program: to monitor delays to move patient from ER to Med ward bed
  • as of July 2016 onward - ICU same purpose

Accept DtTm is used as part of the formula to calculate delay in the transfer of patient from ER bed to Med ward or ICU bed - see ER Delay. This measures the amount of time for the patient already accepted in Medicine or Critical Care service but still using the ER bed and resources.

Data Integrity Checks (automatic list)

none found

Legacy

Click to see legacy info   
  • This field is part of the 2016 Time and Place changes.
    • For medicine this concept is related to admit date and time (when pt is from ER). It does not simply replace the field, so this value still needs to be entered for patients not from ER. Resp. field L_Log.R_AdmDate and L_Log.R_AdmTime
    • For critical care this concept is related to Service Sending to ICU. (There is no comparable field in ICU for this in the old system).

Related articles

Related articles:
Retrieved from "https://ccmdb.kuality.ca/index.php?title=Accept_DtTm_field&oldid=159262"