Internformat: :: Library Catalog

Gespeichert in:

Bibliographische Detailangaben
Hauptverfasser:	Thomsen, Henrik F., Gasparyan, Samvel B., Furberg, Julie F., Tasto, Christoph, Rethemeier, Nicole, Schloemer, Patrick, Wang, Tuo, Jongs, Niels, Du, Yu, Greene, Tom
Format:	Preprint
Veröffentlicht:	2025
Schlagworte:	Methodology
Online-Zugang:	https://arxiv.org/abs/2504.05909
Tags:	Tag hinzufügen Keine Tags, Fügen Sie den ersten Tag hinzu!

_version_	1866916844353355776
author	Thomsen, Henrik F. Gasparyan, Samvel B. Furberg, Julie F. Tasto, Christoph Rethemeier, Nicole Schloemer, Patrick Wang, Tuo Jongs, Niels Du, Yu Greene, Tom
author_facet	Thomsen, Henrik F. Gasparyan, Samvel B. Furberg, Julie F. Tasto, Christoph Rethemeier, Nicole Schloemer, Patrick Wang, Tuo Jongs, Niels Du, Yu Greene, Tom
contents	Win statistics based methods have gained traction as a method for analyzing Hierarchical Composite Endpoints (HCEs) in randomized clinical trials, particularly in cardiovascular and kidney disease research. HCEs offer several key advantages, including increased statistical power, mitigation of competing risks, and hierarchical ranking of clinical outcomes. While, as summary measures, the win ratio (WR) along with the Net Benefit (NB) and the Win Odds (WO) provide a structured approach to analyzing HCEs, several concerns regarding their interpretability remain. In this paper, we present known issues with the WR using simple examples designed to explore the implications for the clinical interpretability of the treatment effect measure in the chronic kidney disease setting. Specifically, we discuss the challenge of defining an appropriate estimand in the context of HCEs using the WR, the difficulties in formulating a relevant causal question underlying the WR, and the dependency of the WR on the variance of its components, which complicates its role as an effect measure. Additionally, we highlight the non-collapsibility and non-transitivity of the WR, further complicating its interpretation. While the WR remains a valuable tool in clinical trials, its inherent limitations must be acknowledged to ensure its proper use in regulatory and clinical decision-making.
format	Preprint
id	arxiv_https___arxiv_org_abs_2504_05909
institution	arXiv
publishDate	2025
record_format	arxiv
spellingShingle	Interpretational challenges of the Win Ratio in analyzing Hierarchical Composite Endpoints in Chronic Kidney Disease Thomsen, Henrik F. Gasparyan, Samvel B. Furberg, Julie F. Tasto, Christoph Rethemeier, Nicole Schloemer, Patrick Wang, Tuo Jongs, Niels Du, Yu Greene, Tom Methodology Win statistics based methods have gained traction as a method for analyzing Hierarchical Composite Endpoints (HCEs) in randomized clinical trials, particularly in cardiovascular and kidney disease research. HCEs offer several key advantages, including increased statistical power, mitigation of competing risks, and hierarchical ranking of clinical outcomes. While, as summary measures, the win ratio (WR) along with the Net Benefit (NB) and the Win Odds (WO) provide a structured approach to analyzing HCEs, several concerns regarding their interpretability remain. In this paper, we present known issues with the WR using simple examples designed to explore the implications for the clinical interpretability of the treatment effect measure in the chronic kidney disease setting. Specifically, we discuss the challenge of defining an appropriate estimand in the context of HCEs using the WR, the difficulties in formulating a relevant causal question underlying the WR, and the dependency of the WR on the variance of its components, which complicates its role as an effect measure. Additionally, we highlight the non-collapsibility and non-transitivity of the WR, further complicating its interpretation. While the WR remains a valuable tool in clinical trials, its inherent limitations must be acknowledged to ensure its proper use in regulatory and clinical decision-making.
title	Interpretational challenges of the Win Ratio in analyzing Hierarchical Composite Endpoints in Chronic Kidney Disease
topic	Methodology
url	https://arxiv.org/abs/2504.05909

if (filemtime($filename) + $maxlifetime < time()) { unlink($filename); $count++; } } return $count; } /** * A function that is called internally when session data is to be saved. * * @param string $sessId The current session ID * @param string $data The session data to write * * @return bool */ protected function saveSession($sessId, $data): bool { $sessFile = $this->path . '/sess_' . $sessId; if ($handle = fopen($sessFile, 'w')) { $return = false; // Lock the file for exclusive access to avoid issues with multiple // processes writing session simultaneously: if (flock($handle, LOCK_EX)) { $return = fwrite($handle, $data); // Make sure that there's no trailing data by truncating the file to // the correct length: ftruncate($handle, strlen($data)); fflush($handle); flock($handle, LOCK_UN); } fclose($handle); if ($return !== false) { return true; } } // If we got this far, something went wrong with the file output... // It is tempting to throw an exception here, but this code is called // outside of the context of exception handling, so all we can do is // echo a message.

// Anecdotal testing Today and Yesterday seems to indicate destroy() // is called by the garbage collector and everything is good. // Something to keep in mind though. return 0; } /** * Write function that is called when session data is to be saved. * * @param string $sessId The current session ID * @param string $data The session data to write * * @return bool */ public function write($sessId, $data): bool { if ($this->writesDisabled) { return true; } return $this->saveSession($sessId, $data); } /** * A function that is called internally when session data is to be saved. * * @param string $sessId The current session ID * @param string $data The session data to write * * @return bool */ abstract protected function saveSession($sessId, $data): bool; }

* * @return void */ public function writeClose() { // The assumption is that we're using PHP's ext/session. // session_write_close() will actually overwrite $_SESSION with an // empty array on completion -- which leads to a mismatch between what // is in the storage object and $_SESSION. To get around this, we // temporarily reset $_SESSION to an array, and then re-link it to // the storage object. // // Additionally, while you _can_ write to $_SESSION following a // session_write_close() operation, no changes made to it will be // flushed to the session handler. As such, we now mark the storage // object isImmutable. $storage = $this->getStorage(); if (! $storage->isImmutable()) { $_SESSION = $storage->toArray(true); session_write_close(); $storage->fromArray($_SESSION); $storage->markImmutable(); } } /** * Attempt to set the session name * * If the session has already been started, or if the name provided fails * validation, an exception will be raised. * * @param string $name * @return SessionManager * @throws Exception\InvalidArgumentException */ public function setName($name) { if ($this->sessionExists()) { throw new Exception\InvalidArgumentException( 'Cannot set session name after a session has already started'

Environment & details:

GET Data empty

POST Data empty

Files empty

Key	Value
language	"de"
ui	"standard"
VUFIND_SESSION	"7dec3999d65386f71b801f7a71662983"

Session

Key	Value
__Laminas	array:2 [`"_REQUEST_ACCESS_TIME" => 1784596331.0228 "_VALID" => array:1 [ "Laminas\Session\Validator\Id" => "7dec3999d65386f71b801f7a71662983" ]`]
SessionState	Laminas\Stdlib\ArrayObject {#938}
FlashMessenger	Laminas\Stdlib\ArrayObject {#1583}
SessionHelper	Laminas\Stdlib\ArrayObject {#1775}

Server/Request Data

Key	Value
REDIRECT_VUFIND_LOCAL_DIR	"/usr/local/vufind/local"
REDIRECT_HTTPS	"on"
REDIRECT_SSL_TLS_SNI	"info.umar.mx"
REDIRECT_STATUS	"200"
VUFIND_LOCAL_DIR	"/usr/local/vufind/local"
HTTPS	"on"
SSL_TLS_SNI	"info.umar.mx"
HTTP_ACCEPT	"/"
HTTP_USER_AGENT	"Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)"
HTTP_COOKIE	"language=de; ui=standard; VUFIND_SESSION=7dec3999d65386f71b801f7a71662983"
HTTP_ACCEPT_ENCODING	"gzip, br, zstd, deflate"
HTTP_HOST	"info.umar.mx"
PATH	"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/snap/bin"
SERVER_SIGNATURE	"<address>Apache/2.4.66 (Ubuntu) Server at info.umar.mx Port 443</address>\n"
SERVER_SOFTWARE	"Apache/2.4.66 (Ubuntu)"
SERVER_NAME	"info.umar.mx"
SERVER_ADDR	"200.23.222.19"
SERVER_PORT	"443"
REMOTE_ADDR	"216.73.216.85"
DOCUMENT_ROOT	"/usr/local/vufind/public"
REQUEST_SCHEME	"https"
CONTEXT_PREFIX	""
CONTEXT_DOCUMENT_ROOT	"/usr/local/vufind/public"
SERVER_ADMIN	"admin@localhost"
SCRIPT_FILENAME	"/usr/local/vufind/public/index.php"
REMOTE_PORT	"47231"
REDIRECT_URL	""" /Record/\n arxiv_https___arxiv_org_abs_2504_05909/Details """
GATEWAY_INTERFACE	"CGI/1.1"
SERVER_PROTOCOL	"HTTP/1.1"
REQUEST_METHOD	"GET"
QUERY_STRING	""
REQUEST_URI	"/Record/%0Aarxiv_https___arxiv_org_abs_2504_05909/Details"
SCRIPT_NAME	"/index.php"
PHP_SELF	"/index.php"
REQUEST_TIME_FLOAT	1784596331.0163
REQUEST_TIME	1784596331

Environment Variables empty

Registered Handlers

0. Whoops\Handler\PrettyPageHandler

Environment & details:

GET Data empty

POST Data empty

Files empty

Key	Value
language	"de"
ui	"standard"
VUFIND_SESSION	"7dec3999d65386f71b801f7a71662983"

Session

Key	Value
__Laminas	array:2 [`"_REQUEST_ACCESS_TIME" => 1784596331.0228 "_VALID" => array:1 [ "Laminas\Session\Validator\Id" => "7dec3999d65386f71b801f7a71662983" ]`]
SessionState	Laminas\Stdlib\ArrayObject {#938}
FlashMessenger	Laminas\Stdlib\ArrayObject {#1583}
SessionHelper	Laminas\Stdlib\ArrayObject {#1775}

Server/Request Data

Key	Value
REDIRECT_VUFIND_LOCAL_DIR	"/usr/local/vufind/local"
REDIRECT_HTTPS	"on"
REDIRECT_SSL_TLS_SNI	"info.umar.mx"
REDIRECT_STATUS	"200"
VUFIND_LOCAL_DIR	"/usr/local/vufind/local"
HTTPS	"on"
SSL_TLS_SNI	"info.umar.mx"
HTTP_ACCEPT	"/"
HTTP_USER_AGENT	"Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; ClaudeBot/1.0; +claudebot@anthropic.com)"
HTTP_COOKIE	"language=de; ui=standard; VUFIND_SESSION=7dec3999d65386f71b801f7a71662983"
HTTP_ACCEPT_ENCODING	"gzip, br, zstd, deflate"
HTTP_HOST	"info.umar.mx"
PATH	"/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/snap/bin"
SERVER_SIGNATURE	"<address>Apache/2.4.66 (Ubuntu) Server at info.umar.mx Port 443</address>\n"
SERVER_SOFTWARE	"Apache/2.4.66 (Ubuntu)"
SERVER_NAME	"info.umar.mx"
SERVER_ADDR	"200.23.222.19"
SERVER_PORT	"443"
REMOTE_ADDR	"216.73.216.85"
DOCUMENT_ROOT	"/usr/local/vufind/public"
REQUEST_SCHEME	"https"
CONTEXT_PREFIX	""
CONTEXT_DOCUMENT_ROOT	"/usr/local/vufind/public"
SERVER_ADMIN	"admin@localhost"
SCRIPT_FILENAME	"/usr/local/vufind/public/index.php"
REMOTE_PORT	"47231"
REDIRECT_URL	""" /Record/\n arxiv_https___arxiv_org_abs_2504_05909/Details """
GATEWAY_INTERFACE	"CGI/1.1"
SERVER_PROTOCOL	"HTTP/1.1"
REQUEST_METHOD	"GET"
QUERY_STRING	""
REQUEST_URI	"/Record/%0Aarxiv_https___arxiv_org_abs_2504_05909/Details"
SCRIPT_NAME	"/index.php"
PHP_SELF	"/index.php"
REQUEST_TIME_FLOAT	1784596331.0163
REQUEST_TIME	1784596331

Environment Variables empty

Registered Handlers

0. Whoops\Handler\PrettyPageHandler

Ähnliche Einträge

Environment & details:

Environment & details: