Page values for "Transfer Delay (Critical Care)"

"_pageData" values

1 row is stored for this page

Field	Field type	Value
_modificationDate	`Datetime`	2025-12-07 8:50:58 PM
_categories	List of `String`, delimiter: `\|`	2016 Time and Place changes • Admit/Discharge • Created Variables • Dispo • Indicators • Legacy Content • Length of stay • Questions • Reporting • Reports • Transfer Ready
_pageID	`Integer`	12,903
_pageName	`Page`	Transfer Delay (Critical Care)
_pageTitle	`String`	Transfer Delay (Critical Care)
_pageNamespace	`Integer`	0

1 row is stored for this page

Field	Field type	Value
Derived	`Page`	Transfer Delay (Critical Care)
Components	List of `Page`, delimiter: `;`
Derived_Type	`String`	I

2 rows are stored for this page

Field	Field type	Value
who	`Text`	Julie
question	`Wikitext`	The Dispo location will be used to define the destination. As per Dr. Garland & Dr. Paunovic. I think we discussed at Task that we will do this differently now... right?

Field	Field type	Value
who	`Text`	Julie
question	`Wikitext`	The above is really about stratification, and not the indicator itself. Do you really only use it to stratify delays, or do you also report other indicators such as Length of Stay with it. Even if it is single-use, I think we should probably treat any generated value we use to stratify pretty much as we do Indicators, possibly using the same templates on the wiki. The stratification affects averages and totals, so it needs to be transparent. This is likely a can of worms because there must be much stratification in the reports. Ttenbergen 14:50, 7 December 2025 (CST)

1 row is stored for this page

Field	Field type	Value
Description	`Wikitext`	Transfer Delay is the difference between Dispo_DtTm and #Transfer Ready DtTm in use at different times in decimal days.
CreatedRaw	`Wikitext string`	Created
Program	`Wikitext string`	Critical Care and Medicine
StartDtTm	`Date`	1999-01-15
EndDtTm	`Date`