<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>FailSystems changelog</title>
  <link href="https://failsystems.health201.com/"/>
  <link href="https://failsystems.health201.com/atom.xml" rel="self"/>
  <id>https://failsystems.health201.com/</id>
  <updated>2026-09-27T00:00:00+00:00</updated>
  <author><name>Health 201</name></author>
  <entry><title>Accuracy review: classifications, tiers and sources corrected</title><link href="https://failsystems.health201.com/method/#tiers-rule"/><id>https://failsystems.health201.com/changelog/#2026-09-27-0</id>
    <updated>2026-09-27T00:00:00+00:00</updated><summary>Tiers reassigned by a documented rule (most ransomware and IT outages are tier 2, not 3); AWS 2025 moved from Power to Connectivity; studies, experiments and non-clinical analogues are now labelled and carry no tier; wrong-output failures no longer read as a fall to tier 0. Second sources added for Princeton Community Hospital, Katrina/Memorial and the sepsis-alert case, whose accounts are shown where they differ. Contec entry now includes independent analyses disputing the backdoor label. Joint Commission alarm goal updated to NPG.01.05.01. Homepage scores marked as draft.</summary></entry>
  <entry><title>New incident: Patient dies while a heart monitor&#x27;s crisis alarm is switched off</title><link href="https://failsystems.health201.com/incidents/mgh-monitor-alarm-off-2010/"/><id>https://failsystems.health201.com/changelog/#2026-09-27-1</id>
    <updated>2026-09-27T00:00:00+00:00</updated><summary>Massachusetts General Hospital, January 2010, from Boston Globe reporting; its limitation (no inspection record found) is stated on the page.</summary></entry>
  <entry><title>FailSystems becomes a sourced reference</title><link href="https://failsystems.health201.com/"/><id>https://failsystems.health201.com/changelog/#2026-09-26-2</id>
    <updated>2026-09-26T00:00:00+00:00</updated><summary>Every failure layer now has its own page: how it fails, the incidents behind it, how you&#x27;d know, defenses at each degradation tier, US standards, the EU/UK position, a v0.1 severity score and open questions. 38 incidents and 205 sources, every link opened and checked.</summary></entry>
  <entry><title>Degradation tiers: the layer × tier matrix</title><link href="https://failsystems.health201.com/tiers/"/><id>https://failsystems.health201.com/changelog/#2026-09-26-3</id>
    <updated>2026-09-26T00:00:00+00:00</updated><summary>What must hold for each of the six layers at each of the four tiers, plus the evidence on rehearsal and on coming back up.</summary></entry>
  <entry><title>Nightly evidence pipeline switched on</title><link href="https://failsystems.health201.com/method/#updates"/><id>https://failsystems.health201.com/changelog/#2026-09-26-4</id>
    <updated>2026-09-26T00:00:00+00:00</updated><summary>New incidents and sources are found, verified and added automatically; changes to page text and scores wait for human review.</summary></entry>
  <entry><title>Disclaimer added</title><link href="https://failsystems.health201.com/method/#disclaimer"/><id>https://failsystems.health201.com/changelog/#2026-09-26-5</id>
    <updated>2026-09-26T00:00:00+00:00</updated><summary>FailSystems is an aggregation and synthesis of published sources for information only: not consulting or professional advice, and no approach fits every organisation.</summary></entry>
  <entry><title>Incident contacts replace the crisis-line box</title><link href="https://failsystems.health201.com/"/><id>https://failsystems.health201.com/changelog/#2026-09-26-6</id>
    <updated>2026-09-26T00:00:00+00:00</updated><summary>The footer now points to the right authorities for a live incident: 911, CISA and the FBI for cyberattacks, local emergency management (which escalates to state and FEMA), and FDA MedWatch for devices.</summary></entry>
  <entry><title>Correction: Connectivity &amp; data</title><link href="https://failsystems.health201.com/layers/connectivity/#detect"/><id>https://failsystems.health201.com/changelog/#2026-09-26-7</id>
    <updated>2026-09-26T00:00:00+00:00</updated><summary>The response-time threshold for a functional downtime is an hourly mean over 5 seconds (or 3 SD above the mean) per ONC&#x27;s SAFER guide; under 2 seconds is SAFER&#x27;s target, not the downtime threshold. Also reworded the extended-downtime failure mode to state the Joint Commission&#x27;s four-week guidance directly. Found by the first local fact-check.</summary></entry>
  <entry><title>FailSystems launched</title><link href="https://failsystems.health201.com/"/><id>https://failsystems.health201.com/changelog/#2026-08-03-8</id>
    <updated>2026-08-03T00:00:00+00:00</updated><summary>Landing page with the failure taxonomy and degradation tiers.</summary></entry>
</feed>
