| Recurring |
multiple_organization |
(a) In the article, it is mentioned that |
| Phase (Design/Operation) |
unknown |
The articles do not provide specific information about a software failure incident related to the development phases of design or operation. |
| Boundary (Internal/External) |
within_system |
The software failure incident described in the articles is primarily related to within_system factors. The incident involved errors in the software and operation of medical radiation devices, leading to overradiation and substandard treatment of cancer patients [17]. The mistakes were attributed to the lack of experience in using the high-powered radiation machines, inadequate training, software bugs, and the failure of hospitals to implement proper checking protocols and safety procedures [17]. Additionally, the incident highlighted issues with outdated safety protocols, lack of financial support for operating sophisticated devices safely, and the sale of machines with software bugs by manufacturers [17]. These factors point to failures originating from within the system, such as inadequate training, outdated protocols, and software issues. |
| Nature (Human/Non-human) |
non-human_actions, human_actions |
(a) The software failure incident occurring due to non-human actions:
- The articles highlight instances where software failures occurred due to factors introduced without human participation, such as miscalibrated machines that overradiated patients [17].
- In one case, a linear accelerator at a hospital was set up incorrectly, leading to the overradiation of brain cancer patients [17].
- The articles also mention cases where software glitches or design flaws in treatment planning software led to incorrect radiation doses being administered to patients [17].
- Manufacturers sometimes released new equipment with software bugs or glitches, causing incorrect treatment of patients [17].
(b) The software failure incident occurring due to human actions:
- Human actions also played a significant role in software failures, such as when medical personnel compensated for using the wrong type of CT treatment scan by doing a "work around," leading to miscalculations affecting all treatments [17].
- In another case, a medical physicist failed to catch a dosage mistake made by an oncologist, resulting in a patient being overdosed with radioactive seeds [17].
- The articles also mention instances where human errors, such as entering incorrect magnification factors into treatment planning computers, led to patients receiving incorrect doses of radiation [17].
- Lack of proper training, supervision, and oversight of medical personnel contributed to software failures in radiation therapy incidents [17]. |
| Dimension (Hardware/Software) |
unknown |
The articles do not provide specific information about software or hardware failures in the context of the incidents described. Therefore, it is unknown whether the incidents were related to hardware or software failures. |
| Objective (Malicious/Non-malicious) |
unknown |
The articles do not provide information about a software failure incident related to a malicious or non-malicious objective. |
| Intent (Poor/Accidental Decisions) |
poor_decisions, accidental_decisions |
The articles provide information related to both poor decisions and accidental decisions contributing to the software failure incidents:
(a) poor_decisions: The incidents highlight poor decisions made by hospitals, manufacturers, and regulators that contributed to the software failure incidents. For example, hospitals lacked proper training and quality control for administering treatments using new technology, manufacturers sold machines with software bugs, and government regulators were slow to respond to the increasing risks associated with advanced technology [17].
(b) accidental_decisions: The incidents also involve accidental decisions or mistakes that led to software failures. For instance, in one case, a hospital used the wrong type of CT treatment scan due to unfamiliarity with the treatment planning software, resulting in miscalculations affecting all treatments [17]. Additionally, a physicist entered an incorrect magnification factor into the treatment planning computer, leading to a patient receiving twice the prescribed dose multiple times [17]. |
| Capability (Incompetence/Accidental) |
development_incompetence, accidental |
The articles provide information related to both development incompetence and accidental factors contributing to software failure incidents:
(a) development_incompetence:
- The incidents highlighted the vulnerability of patient safeguards due to the lack of experience in using new machines generating high-powered beams of radiation, leading to overradiation and substandard treatment of cancer patients [17].
- Hospitals were found to lack the necessary financial support to operate sophisticated devices safely, and manufacturers sometimes sold machines before all software bugs were identified and removed [17].
- The incidents at various hospitals revealed that medical personnel lacked the training and knowledge to safely administer treatments using advanced technology like I.M.R.T., and quality control was virtually nonexistent [17].
(b) accidental:
- The incidents at various hospitals, such as overdosing cancer patients with radiation, were accidental in nature, stemming from mistakes made during treatment planning and delivery processes [17].
- Errors in treatment planning software, miscalculations, and deviations from established procedures were accidental factors contributing to the overradiation and substandard treatment of patients [17]. |
| Duration |
unknown |
The articles do not specifically mention a software failure incident that can be categorized as either permanent or temporary. |
| Behaviour |
crash, omission, timing, value, other |
(a) crash: The incident at the Moffitt Cancer Center in Tampa, Florida, involved a miscalibrated machine that overradiated 77 brain cancer patients by 50 percent in 2004 and 2005, indicating a crash where the system lost its state and did not perform its intended functions [17].
(b) omission: The incident at Akron General Hospital in Ohio involved a patient being overdosed with high-dose radioactive seeds due to a physicist entering an incorrect magnification factor into the treatment planning computer, resulting in the system omitting to perform its intended functions correctly [17].
(c) timing: The incident involving Landreaux A. Donaldson at Mary Bird Perkins Cancer Center in Baton Rouge, Louisiana, highlighted a timing failure where the linear accelerator delivered radiation in a radically different way, prompting medical personnel to compensate with a departure from established procedure, but due to unfamiliarity with the treatment planning software, a miscalculation affected all 38 treatments over two months [17].
(d) value: The incident at Christus Spohn Hospital in Corpus Christi, Texas, involving George Garst being overdosed and seriously injured during his prostate cancer treatment, showcased a value failure where the system performed its intended functions incorrectly, resulting in severe injuries to the patient [17].
(e) byzantine: The articles do not provide specific information about a byzantine behavior of the software failure incident.
(f) other: The incident at the Veterans Affairs Medical Center in East Orange, New Jersey, revealed a failure in the behavior of the system where |