Incident: Unwanted Pregnancies Due to Birth Control App Failure.

Published Date: 2018-01-18

Postmortem Analysis
Timeline 1. The software failure incident involving the Natural Cycles birth control app happened between September to December 2017 as reported in Article 66930. 2. Published on 2018-01-18 08:00:00+00:00. 3. The incident occurred between September to December 2017.
System 1. Natural Cycles app - The software application designed to track menstrual cycles and provide contraceptive advice failed to prevent unwanted pregnancies among its users [66930].
Responsible Organization 1. Natural Cycles app [66930]
Impacted Organization 1. Women relying on the Natural Cycles app for contraception [66930]
Software Causes 1. The software cause of the failure incident in this case was the algorithm used by the Natural Cycles app to calculate the users' menstrual cycle and determine when they can have sex without protection, leading to unwanted pregnancies among users relying on the app for contraception [66930].
Non-software Causes 1. Lack of user understanding or compliance with the app's requirements, such as consistently inputting temperature data [66930]. 2. Potential limitations or inaccuracies in the app's algorithm or methodology for calculating menstrual cycles and fertile periods [66930]. 3. Overreliance on the app as the sole method of contraception without additional precautions or verification [66930].
Impacts 1. The software failure incident of the Natural Cycles app led to 37 cases of unwanted pregnancies among women relying on the app for contraception, as reported by a hospital in Stockholm [66930].
Preventions 1. Implementing more rigorous testing procedures to identify and address any potential algorithmic flaws or inaccuracies in the app [66930]. 2. Conducting thorough user education and training to ensure that users understand the limitations and effectiveness of the app, as well as the importance of using additional contraceptive methods if necessary [66930]. 3. Regularly updating the app based on user feedback and reported incidents to continuously improve its accuracy and effectiveness in preventing unwanted pregnancies [66930].
Fixes 1. Implementing additional verification methods or reminders within the app to ensure users are consistently inputting accurate data, which could help improve the accuracy of the algorithm and reduce the risk of miscalculations leading to unwanted pregnancies [66930].
References 1. Swedish public broadcaster SVT [66930]

Software Taxonomy of Faults

Category Option Rationale
Recurring one_organization (a) The software failure incident related to the Natural Cycles birth control app has happened again within the same organization. The article mentions that 37 out of 668 women seeking an abortion at one of Stockholm's largest hospitals from September to December 2017 were relying on Natural Cycles for birth control, leading to unwanted pregnancies. This indicates a failure of the app within the organization itself [66930]. (b) There is no specific mention in the article about the software failure incident happening at other organizations or with their products and services.
Phase (Design/Operation) design, operation (a) The software failure incident related to the design phase can be attributed to the fact that the birth control app, Natural Cycles, which relies on hi-tech algorithms for contraception, was reported to Swedish authorities after 37 cases of unwanted pregnancies were found among women using the app for birth control [66930]. (b) The software failure incident related to the operation phase can be seen in the misuse or reliance on the app for contraception by women, leading to unwanted pregnancies. The app requires women to input their temperature daily and calculates their menstrual cycle to inform them when they can have unprotected sex. However, the reported cases of unwanted pregnancies among users indicate a failure in the operation or use of the system [66930].
Boundary (Internal/External) within_system (a) within_system: The software failure incident related to the Natural Cycles birth control app can be categorized as within_system. The failure originated from within the system itself, specifically from the algorithm and methodology used by the app to calculate the users' menstrual cycle and determine safe periods for unprotected sex. The issue of unwanted pregnancies among women relying on the app for contraception indicates a failure within the system's design or functionality, leading to ineffective contraceptive outcomes [66930]. (b) outside_system: The software failure incident does not appear to be primarily attributed to factors originating from outside the system. The reported cases of unwanted pregnancies were directly linked to the app's performance and effectiveness in providing contraception, rather than external influences beyond the control of the app itself [66930].
Nature (Human/Non-human) non-human_actions (a) The software failure incident in this case can be attributed to non-human actions, specifically the failure of the Natural Cycles app algorithm to effectively prevent unwanted pregnancies. The app relies on hi-tech algorithms to calculate users' menstrual cycles and inform them when they can have sex without protection. The issue arose from the app's inability to accurately predict fertile days, leading to unintended pregnancies among users [66930].
Dimension (Hardware/Software) software (a) The software failure incident related to hardware: The article does not mention any hardware-related issues contributing to the failure incident. (b) The software failure incident related to software: The failure incident in this case is related to the software itself, specifically the Natural Cycles app. The app, which combines algorithms with the rhythm method for contraception, has been reported to have resulted in 37 cases of unwanted pregnancies among women relying on it for birth control [66930]. This indicates a failure in the software's effectiveness in preventing unplanned pregnancies, which is a software-related issue.
Objective (Malicious/Non-malicious) non-malicious (a) The software failure incident related to the Natural Cycles birth control app can be categorized as non-malicious. The failure was not due to any malicious intent but rather stemmed from the app's effectiveness in preventing unwanted pregnancies. The app, which relies on algorithms and user input to calculate fertility cycles, was reported to have resulted in 37 cases of unwanted pregnancies among women using it for contraception [66930]. The company behind the app, Natural Cycles, responded to the reported cases and acknowledged the issue, stating that they deeply care about unplanned pregnancies among their users and are addressing each reported case [66930].
Intent (Poor/Accidental Decisions) poor_decisions (a) The intent of the software failure incident related to poor decisions can be inferred from the article. Natural Cycles, the birth control app, faced criticism and reported cases of unwanted pregnancies among women relying on the app for contraception. The app claimed to be 93% effective with typical use but was reported to have 37 cases of unwanted pregnancies among women seeking abortions at a hospital in Stockholm. This indicates that there may have been poor decisions in the development or implementation of the app that led to this software failure incident [66930]. (b) The intent of the software failure incident related to accidental decisions can also be considered. The company behind the app, Natural Cycles, stated that they deeply care every time one of their users becomes pregnant unplanned and that they are responding to each reported case. This suggests that the unwanted pregnancies resulting from the app were unintended consequences rather than deliberate actions. It indicates that the failure may have been due to accidental decisions or unforeseen outcomes rather than intentional actions [66930].
Capability (Incompetence/Accidental) development_incompetence, accidental (a) The software failure incident related to the Natural Cycles birth control app can be attributed to development incompetence. The app, which claims to be 93% effective with typical use, was reported to Swedish authorities after 37 cases of unwanted pregnancies among women relying on the app for contraception were discovered at a hospital in Stockholm [66930]. This incident highlights potential shortcomings in the development process or the algorithm used by the app, leading to unintended consequences for the users. (b) The software failure incident can also be considered as accidental, as the company behind the app, Natural Cycles, stated that they deeply care every time one of their users becomes pregnant unplanned and that they are responding to each reported case [66930]. This suggests that the unwanted pregnancies were not intentional or planned by the company, indicating an accidental aspect to the failure incident.
Duration temporary The software failure incident related to the Natural Cycles birth control app can be categorized as a temporary failure. The app was reported to Swedish authorities after a hospital found 37 cases of unwanted pregnancies among women relying on the app for contraception [Article 66930]. The company behind the app, Natural Cycles, stated that they were responding to each reported case of unwanted pregnancy, indicating that the failure was due to contributing factors introduced by certain circumstances but not all.
Behaviour omission, value, other (a) crash: The software failure incident in this case does not involve a crash where the system loses state and does not perform any of its intended functions. The app, Natural Cycles, is still operational and functioning, but the issue lies in its effectiveness as a contraceptive method leading to unwanted pregnancies [66930]. (b) omission: The software failure incident can be categorized under omission as the system, in this case, the Natural Cycles app, is omitting to perform its intended function of providing effective contraception. This omission has resulted in unwanted pregnancies among women relying on the app for birth control [66930]. (c) timing: The software failure incident is not related to timing issues where the system performs its intended functions correctly but too late or too early. The issue with the Natural Cycles app is more about the effectiveness of its contraceptive method rather than timing-related failures [66930]. (d) value: The software failure incident can be attributed to a value failure as the system, the Natural Cycles app, is performing its intended function of providing contraceptive information, but the information provided is incorrect or not effective in preventing unwanted pregnancies. This discrepancy in the value provided by the app has led to the reported cases of failed contraception [66930]. (e) byzantine: The software failure incident is not characterized by a byzantine behavior where the system behaves erroneously with inconsistent responses and interactions. The issue with the Natural Cycles app is more straightforward in terms of its failure to effectively prevent unwanted pregnancies rather than exhibiting inconsistent or erratic behavior [66930]. (f) other: The software failure incident can be categorized as a failure related to the efficacy of the contraceptive method provided by the app. The issue is not related to a technical malfunction or erratic behavior of the system but rather the discrepancy between the claimed effectiveness of the app and the actual outcomes experienced by users [66930].

IoT System Layer

Layer Option Rationale
Perception None None
Communication None None
Application None None

Other Details

Category Option Rationale
Consequence theoretical_consequence, other (a) death: There is no mention of any deaths resulting from the software failure incident in the provided article [66930]. (b) harm: The article does not mention any physical harm caused to individuals due to the software failure incident [66930]. (c) basic: The software failure did not impact people's access to food or shelter as per the article [66930]. (d) property: The software failure did not result in any impact on people's material goods, money, or data [66930]. (e) delay: There is no indication of any activity being postponed due to the software failure incident [66930]. (f) non-human: The software failure incident primarily affected the users of the birth control app, who experienced unwanted pregnancies, but there is no mention of non-human entities being impacted [66930]. (g) no_consequence: The software failure incident resulted in unwanted pregnancies among users of the birth control app, indicating a real consequence [66930]. (h) theoretical_consequence: The article discusses the potential consequences of unwanted pregnancies resulting from the software failure incident, such as the number of unplanned pregnancies increasing as the user base grows [66930]. (i) other: The software failure incident led to 37 cases of unwanted pregnancies among women relying on the app for contraception, which is a significant consequence not covered in the options (a) to (h) [66930].
Domain health (a) The failed system in this incident is related to the health industry. The software failure incident involves a birth control app called Natural Cycles, which is used by women for contraception [66930].

Sources

Back to List