21 CFR 884.5370 — Device, Fertility Diagnostic, Contraceptive, Software Application

Obstetrics/Gynecology (OB) · Part 884 Subpart F—Obstetrical and Gynecological Therapeutic Devices · § 884.5370

Identification

A software application for contraception is a device that provides user-specific fertility information for preventing a pregnancy. This device includes an algorithm that performs analysis of patient-specific data (e.g., temperature, menstrual cycle dates) to distinguish between fertile and non-fertile days, then provides patient-specific recommendations related to contraception.

Classification Rationale

Class II (special controls). The special controls for this device are:

Product Codes

Special Controls

PYT — Device, Fertility Diagnostic, Contraceptive, Software Application

1. Clinical performance testing must demonstrate the contraceptive effectiveness of the software in the intended use population. 2. Human factors performance evaluation must be provided to demonstrate that the intended users can self-identify that they are in the intended use population and can correctly use the application, based solely on reading the directions for use for contraception. 3. Software verification, validation, and hazard analysis must be performed. Documentation must include the following: a. A cybersecurity vulnerability and management process to assure software functionality; and b. A description of the technical parameters of the software, including the algorithm used to determine fertility status and alerts for user inputs outside of expected ranges. 4. Labeling must include: The following warnings and precautions: a. i. A statement that no contraceptive method is 100% effective. ii. A statement that another form of contraception (or abstinence) must be used on days specified by the application. iii. Statements of any factors that may affect the accuracy of the contraceptive information. iv. A warning that the application cannot protect against sexually transmitted infections. b. Hardware platform and operating system requirements. Instructions identifying and explaining how to use the software application, including C. required user inputs and how to interpret the application outputs. d. A summary of the clinical validation study and results, including effectiveness of the application as a stand-alone contraceptive and how this effectiveness compares to other forms of legally marketed contraceptives.

De Novo Order DEN170052

PYT — Device, Fertility Diagnostic, Contraceptive, Software Application

*Classification.* Class II (special controls). The special controls for this device are:(1) Clinical performance testing must demonstrate the contraceptive effectiveness of the software in the intended use population. (2) Human factors performance evaluation must be provided to demonstrate that the intended users can self-identify that they are in the intended use population and can correctly use the application, based solely on reading the directions for use for contraception. (3) Software verification, validation, and hazard analysis must be performed. Documentation must include the following: (i) A cybersecurity vulnerability and management process to assure software functionality; and (ii) A description of the technical parameters of the software, including the algorithm used to determine fertility status and alerts for user inputs outside of expected ranges. (4) Labeling must include: (i) The following warnings and precautions: (A) A statement that no contraceptive method is 100% effective. (B) A statement that another form of contraception (or abstinence) must be used on days specified by the application. (C) Statements of any factors that may affect the accuracy of the contraceptive information. (D) A warning that the application cannot protect against sexually transmitted infections. (ii) Hardware platform and operating system requirements. (iii) Instructions identifying and explaining how to use the software application, including required user inputs and how to interpret the application outputs. (iv) A summary of the clinical validation study and results, including effectiveness of the application as a stand-alone contraceptive and how this effectiveness compares to other forms of legally marketed contraceptives.

eCFR

PYT — Device, Fertility Diagnostic, Contraceptive, Software Application

(1) Clinical performance testing must demonstrate the contraceptive effectiveness of the software in the intended use population. (2) Human factors performance evaluation must be provided to demonstrate that the intended users can self-identify that they are in the intended use population and can correctly use the application, based solely on reading the directions for use for contraception. (3) Software verification, validation, and hazard analysis must be performed. Documentation must include the following: (i) A cybersecurity vulnerability and management process to assure software functionality; and (ii) A description of the technical parameters of the software, including the algorithm used to determine fertility status and alerts for user inputs outside of expected ranges. (4) Labeling must include: (i) The following warnings and precautions: (A) A statement that no contraceptive method is 100% effective. (B) A statement that another form of contraception (or abstinence) must be used on days specified by the application. (C) Statements of any factors that may affect the accuracy of the contraceptive information. (D) A warning that the application cannot protect against sexually transmitted infections. (ii) Hardware platform and operating system requirements. (iii) Instructions identifying and explaining how to use the software application, including required user inputs and how to interpret the application outputs. (iv) A summary of the clinical validation study and results, including effectiveness of the application as a stand-alone contraceptive and how this effectiveness compares to other forms of legally marketed contraceptives.

Ecfr Llm