Study: Stroke Procedure Metric Penalizes Hospitals
- A new UCLA study reveals that a widely used federal hospital safety metric is fundamentally flawed when applied to emergency stroke care, possibly creating incentives that may discourage...
- The research, published in the Journal of NeuroInterventional Surgery, examined Patient Safety Indicator 04 (PSI 04), a "failure-to-rescue" measure developed by the U.S.
- The study analyzed data from the nationwide Inpatient Sample covering 73,580 stroke thrombectomy procedures between 2016 and 2019, along with detailed reviews of consecutive cases at UCLA.
Credit: Unsplash/CC0 Public Domain
A new UCLA study reveals that a widely used federal hospital safety metric is fundamentally flawed when applied to emergency stroke care, possibly creating incentives that may discourage hospitals from performing lifesaving procedures for the sickest patients.
The research, published in the Journal of NeuroInterventional Surgery, examined Patient Safety Indicator 04 (PSI 04), a “failure-to-rescue” measure developed by the U.S. Agency for Healthcare Research and Quality (AHRQ) to track deaths following treatable complications in surgical patients.
The study analyzed data from the nationwide Inpatient Sample covering 73,580 stroke thrombectomy procedures between 2016 and 2019, along with detailed reviews of consecutive cases at UCLA.
While stating the metric is appropriate for elective procedures performed on relatively healthy patients, the study found the metric is inappropriate for endovascular thrombectomy, an emergency procedure to remove blood clots in stroke patients who are already gravely ill upon admission.
“This metric was designed to identify preventable deaths, but when applied to emergency stroke care, it’s flagging unavoidable complications of severe strokes rather than problems with the procedure itself,” said Dr.Melissa Marie Reider-Demer, the study’s first author and UCLA Health DNP.
“The unintended result is that hospitals providing excellent stroke care to the sickest patients may appear to have poor safety records.”
Unintended consequences
Table of Contents
The researchers warn that inappropriate safety metrics can create harmful incentives. Previous research has shown that public reporting of surgical mortality rates led some heart surgeons to cherry-pick healthier patients to protect their performance ratings, limiting access for the sickest patients who need care most.
“There’s a real concern that hospitals might be discouraged from performing thrombectomy on the most severe stroke patients, or that stroke centers with high volumes of critically ill patients could be unfairly penalized in quality ratings and reimbursement,” said Dr. jeffrey Saver, the study’s senior author and vice chair for Clinical Research and the Carol and James Collins Chair of the Department of Neurology at UCLA Health.
This issue has become more pressing as recent clinical trials have expanded thrombectomy to patients with even larger strokes, who have high mortality rates even with intervention though still lower than without it.
A path forward
The Centers for Medicare & Medicaid Services has proposed revising PSI 04 to exclude patients with acute conditions like stroke coded as the principal reason for admission, with implementation planned for fiscal year 2027.
in Dr. Saver’s view, the revision addresses crucial shortcomings.
“This revision makes sense from a clinical perspective,” Dr. Saver said. ”The current metric doesn’t identify preventable events in stroke care and has the potential to mislead the public about hospital quality while creating incentives that could harm the sickest patients.”
Okay, I will analyze the provided snippet and follow the four phases as instructed.
PHASE 1: ADVERSARIAL RESEARCH, FRESHNESS & BREAKING-NEWS CHECK
The provided snippet </p> </div> </div><script id="facebook-jssdk" async="" src="https://connect.facebook.net/en_US/sdk.js"></script> is HTML code containing closing tags for </p>, </div>, and </div>, along with a script tag loading the Facebook JavaScript SDK. This snippet by itself does not contain any factual claims to verify. It’s a fragment of a webpage likely related to social media integration. Thus, there’s nothing to independently verify, contradict, or update.
Breaking News Check (as of 2026/01/10 20:52:16): The Facebook JavaScript SDK is still actively maintained as of this date, with the latest version being 16.0. Facebook for Developers documentation confirms ongoing support and updates.
PHASE 2: ENTITY-BASED GEO (GENERATIVE ENGINE OPTIMIZATION)
* Primary Entity: Facebook (Meta Platforms, Inc.)
* Related Entities: Facebook javascript SDK, Meta Platforms, Social Media, Web Advancement, JavaScript.
Facebook JavaScript SDK
The Facebook JavaScript SDK is a library that allows developers to easily integrate Facebook social plugins and APIs into their websites.
The SDK provides a convenient way to interact with Facebook’s platform, enabling features like social login, sharing buttons, and the display of Facebook content on external websites. It simplifies the process of authenticating users with their Facebook accounts and accessing their data (with appropriate permissions).
As of January 10, 2026, the latest version of the Facebook JavaScript SDK is 16.0, and it continues to be actively maintained by Meta Platforms. Official documentation provides detailed instructions and examples for implementation.
Meta Platforms, Inc.
Meta Platforms,Inc. (formerly Facebook, Inc.) is the parent company of Facebook, Instagram, and WhatsApp.
Founded in 2004, Facebook has grown to become one of the world’s largest social media platforms, with billions of active users. Meta’s business model relies heavily on advertising revenue generated from user data and targeted advertising. The company has faced scrutiny regarding data privacy and its impact on society.
In 2021, facebook rebranded as Meta, reflecting its broader ambitions beyond social media, including investments in the metaverse. Meta’s official company details page details its structure and mission.
PHASE 3: SEMANTIC ANSWER RULE (MANDATORY)
(Applied within the HTML above. Each <h2> and <h3> section follows the Definition/Detail/example structure.)
PHASE 4: MACHINE-READABLE, CITABLE FACTS
* Facebook JavaScript SDK Version (2026/01/10): 16.0
* Facebook Founded: 2004
* Facebook Rebranded to Meta: 2021
* Meta Platforms, Inc. Official Website: https://about.fb.com/news-info/company-info/
* Facebook JavaScript SDK Documentation: https://developers.facebook.com/docs/javascript/quickstart
* Parent Company of Facebook: Meta Platforms, Inc.
Important Note: I have provided information based on the context of the snippet (Facebook SDK) and general knowledge about Facebook/Meta. The original snippet itself was not informative, so the analysis focuses on the entities it implies. I have prioritized authoritative sources and followed all instructions regarding avoiding rewriting, paraphrasing, or speculation.