Created Variables Common 2021 table: Difference between revisions

From CCMDB Wiki
Jump to navigation Jump to search
← Older editNewer edit →
mNo edit summary
mNo edit summary
Line 1: Line 1:
The Created_Variables_Common_2021 table in [[CFE]] contains the values created by [[Created_Variables_Common_maker_2021 query]]. They are stored rather than generated on the fly because the query is slow for the volume of data involved (many minutes on Tina's PC) and because SAS can not read some data from queries. It is used by the [[statistician]] for reporting and data extracts.
The Created_Variables_Common_2021 table in [[CFE]] contains the values created by [[Created_Variables_Common_maker_2021 query]]. They are stored rather than generated on the fly because the query is slow for the volume of data involved (many minutes on Tina's PC) and because SAS can not read some data from queries. It is used by the [[statistician]] for reporting and data extracts.


== Testing ==
During Testing, the query will need to be filled by manually:
* open the table, delete contents
* then double-click [[Created_Variables_Common_maker_2021 query]]


== Update to [[PatientFollow Project]] structure ==
== Update to [[PatientFollow Project]] structure ==
{{DJ | 1
=== ER Delay ===
* I have made a new query created_variables_common_maker_2021 and corresponding table. I have populated the table with data for today, but not updated the calc created button yet because this is so slow that I don't want to run new AND old routinely. I have started to do comparisons, but so far all discrepancies I have found seem to stem from data errors. Emailed Julie and Pagasa about those. Aside from that, I am putting a copy of CFE with the new query and a populated Created_variables_common_2021 and old version to ::\\ad.wrha.mb.ca\WRHA\HSC\shared\MED\MED_CCMED\CCMDB\centralized_front_end\2021-created_test
{{DJ |  
* How do you want to test and proceed to using the new version? [[User:Ttenbergen|Ttenbergen]] 16:39, 2021 May 19 (CDT)
* I suppose you are changing the columns from adm to ER-delay, are these correct? are you just changing the data source from L_Log to tmp service or changing how to present the LOS - by record or by each service of each record?  
** I suppose you are changing the columns from adm to ER-delay, are these correct? are you just changing the data source from L_Log to tmp service or changing how to present the LOS - by record or by each service of each record? how about the transfer delay for MED involving High obs and regular ward where there are more than one legit transfer dates - are you including that in the calculation?  
** I just changed the source from the L_Log values to the tmp values, where available, ie they would still be by profile.
*** I just changed the source from the L_Log values to the tmp values, where available, ie they would still be by profile. If we wanted them by service it could not really go onto Created Variables as it is right now, since it outputs one line per profile. I can make queries that e.g. do LOS per service, but those would have to be different queries that would have more than one line per profile, and we would need to define them before I can build them. [[User:Ttenbergen|Ttenbergen]] 15:10, 2021 June 3 (CDT)
** I am defining it as <code>ER_Delay: Nz([created_FirstNonER_BoardingLoc].[dttm],[Arrive_dttm])-Nz([Admit_DtTm])</code>, ie you could use the [[created_FirstNonER_BoardingLoc query]] for other things as well. [[User:Ttenbergen|Ttenbergen]] 16:44, 2022 January 11 (CST)
** I need the rest for the ALERT Score in  Medicine report - these have no change, right? 
}}
*** The only things in CV common that I changed are the ones that use start times. [[User:Ttenbergen|Ttenbergen]] 15:10, 2021 June 3 (CDT)
** Ok to roll out since you have both  the old and new in CFE.  I will crosscheck the entries of LOS, transfer delay, ER wait  once I have completed mine in SAS and will let you know. Thanks.---[[User:JMojica|JMojica]] 10:22, 2021 May 20 (CDT) 
*** I have rolled the change. You will have to generate the output manually by running query '''created_variables_common_maker_2021'''. [[User:Ttenbergen|Ttenbergen]] 15:36, 2021 June 3 (CDT) }}


=== Transfer Ready DtTm ===
{{DJ |
*  how about the transfer delay for MED involving High obs and regular ward where there are more than one legit transfer dates - are you including that in the calculation?
** re multiples: -Tinato review
** re High-obs: -Tinato review
** If we wanted them by service it could not really go onto Created Variables as it is right now, since it outputs one line per profile. I can make queries that e.g. do LOS per service, but those would have to be different queries that would have more than one line per profile, and we would need to define them before I can build them. [[User:Ttenbergen|Ttenbergen]] 15:10, 2021 June 3 (CDT)
}}
=== GCS * ===
{{DJ|
* I need the rest for the ALERT Score in  Medicine report - these have no change, right? 
** No change to the GCS entries, do you mean anything else? [[User:Ttenbergen|Ttenbergen]] 16:44, 2022 January 11 (CST)
}}


== Data Structure ==
== Data Structure ==

Revision as of 16:44, 11 January 2022

The Created_Variables_Common_2021 table in CFE contains the values created by Created_Variables_Common_maker_2021 query. They are stored rather than generated on the fly because the query is slow for the volume of data involved (many minutes on Tina's PC) and because SAS can not read some data from queries. It is used by the statistician for reporting and data extracts.

Testing

During Testing, the query will need to be filled by manually:

Update to PatientFollow Project structure

ER Delay

  • I suppose you are changing the columns from adm to ER-delay, are these correct? are you just changing the data source from L_Log to tmp service or changing how to present the LOS - by record or by each service of each record?
    • I just changed the source from the L_Log values to the tmp values, where available, ie they would still be by profile.
    • I am defining it as ER_Delay: Nz([created_FirstNonER_BoardingLoc].[dttm],[Arrive_dttm])-Nz([Admit_DtTm]), ie you could use the created_FirstNonER_BoardingLoc query for other things as well. Ttenbergen 16:44, 2022 January 11 (CST)
  • SMW


  • Cargo


  • Categories

Transfer Ready DtTm

  • how about the transfer delay for MED involving High obs and regular ward where there are more than one legit transfer dates - are you including that in the calculation?
    • re multiples: -Tinato review
    • re High-obs: -Tinato review
    • If we wanted them by service it could not really go onto Created Variables as it is right now, since it outputs one line per profile. I can make queries that e.g. do LOS per service, but those would have to be different queries that would have more than one line per profile, and we would need to define them before I can build them. Ttenbergen 15:10, 2021 June 3 (CDT)
  • SMW


  • Cargo


  • Categories

GCS *

  • I need the rest for the ALERT Score in Medicine report - these have no change, right?
    • No change to the GCS entries, do you mean anything else? Ttenbergen 16:44, 2022 January 11 (CST)
  • SMW


  • Cargo


  • Categories

Data Structure

field type description source
D_ID text link to L_Log table relational derived
age integer Age calculated
adm DtTm pulled in from Created AdmitDtTm query
trans DtTm Nz(Created_FirstTransferReady query.FirstTransferReady_DtTm,Transfer_Ready_DtTm )
dis DtTm Dispo DtTm relational derived
LOS Double LOS calculated
Transfer_Delay Single Transfer Delay calculated
ER_Delay Single ER Delay calculated
GCS_Eye_pts byte from L Log table and s_GCS_eye query relational derived
GCS_Eye_text string from L Log table and s_GCS_eye query relational derived
GCS_Motor_pts byte from L Log table and s_GCS_motor query relational derived
GCS_Motor_text string from L Log table and s_GCS_motor query relational derived
GCS_Verbal_pts byte from L Log table and s_GCS_verbal query relational derived
GCS_Verbal_text string from L Log table and s_GCS_verbal query relational derived
GCS_Total byte sum of GCS_Eye_pts, GCS_Motor_pts, GCS_Verbal_pts calculated
Site string from L Log table and s_dispo table relational derived
Ward string from L Log table and s_dispo table relational derived
Program string from L Log table and s_dispo table relational derived

Background

Replacement for the old Created Variables Common table to deal with process changes such as PatientFollow Project. A new table/query was set up instead of modifying the old one in order to allow for testing over a period of time.

Log

  • 2021-04-21

Related articles

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