FD&C Act section 520(o), software functions excluded from the device definition, with section 201(h)
21 U.S.C. § 360j(o), read with 21 U.S.C. § 321(h)
In force since .
An AI sector rules rule binding private bodies.
- Obligation class
- Licensing, Reporting
As of .
What it requires
- This provision sets no duty of its own: it removes five kinds of software function from the definition of device in section 201(h), and a software function that meets the definition and falls outside those exclusions is a device under the Federal Food, Drug, and Cosmetic Act.
- Treat a software function as a device if it is intended for use in the diagnosis of disease or other conditions, or in the cure, mitigation, treatment, or prevention of disease, or to affect the structure or any function of the body, and it meets none of the exclusions in section 520(o)(1) (administrative support of a health care facility, maintaining or encouraging a healthy lifestyle unrelated to disease, electronic patient records, displaying clinical laboratory test or other device data and results, and clinical decision support).
- Do not rely on the clinical decision support exclusion if the function is intended to acquire, process, or analyze a medical image or a signal from an in vitro diagnostic device or a pattern or signal from a signal acquisition system, or if it is not intended to let the health care professional independently review the basis for its recommendations so that the professional does not rely primarily on them to make a clinical diagnosis or treatment decision regarding an individual patient.
- Treat a software function described in section 520(o)(1)(C), (D), or (E) as a device from the date a final order of the Secretary identifies it, after notice in the Federal Register and at least 30 calendar days for public comment, on a finding that its use would be reasonably likely to have serious adverse health consequences.
- If you are required to register and propose to begin introducing a software function that is a device into interstate commerce for commercial distribution, report to the Secretary or an accredited person at least ninety days beforehand the class in which the device is classified and the action you took to comply with the requirements of section 514 or 515 that apply to it (section 510(k)).
- If your software function is a class III device that requires premarket approval, hold an approved application for premarket approval under section 515 before you market it, unless it is exempt under section 520(g).
- Do not introduce or deliver for introduction into interstate commerce a device that is adulterated or misbranded, and do not adulterate or misbrand a device in interstate commerce (section 301(a) and (b)).
These lines are LexLint's reading of the law's text, as of .
If you get it wrong
Criminal exposureYes
Criminal exposure note
A violation of section 301 is punishable by imprisonment for not more than one year or a fine of not more than $1,000, or both; a repeat violation, or one committed with intent to defraud or mislead, by imprisonment for not more than three years or a fine of not more than $10,000, or both (21 U.S.C. 333(a)).
Who enforces it
Enforcement body
United States, through the Secretary of Health and Human Services
Settledness
- As of
- Open questions
- Does a function that gives a health care professional a single diagnostic or treatment recommendation satisfy the requirement in section 520(o)(1)(E)(iii) that it enable the professional to independently review the basis for the recommendations?
What this law does
Section 201(h) of the Federal Food, Drug, and Cosmetic Act, which defines a device, states that the term does not include software functions excluded under section 520(o).
Section 520(o)(1)(A) excludes a software function intended for administrative support of a health care facility, including the processing and maintenance of financial records, claims or billing information, appointment schedules, business analytics, information about patient populations, admissions, practice and inventory management, analysis of historical claims data to predict future utilization or cost-effectiveness, determination of health benefit eligibility, population health management, and laboratory workflow.
Section 520(o)(1)(B) excludes a software function intended for maintaining or encouraging a healthy lifestyle that is unrelated to the diagnosis, cure, mitigation, prevention, or treatment of a disease or condition. Section 520(o)(1)(C) excludes a software function that serves as electronic patient records, to the extent the records are intended to transfer, store, convert formats, or display the equivalent of a paper medical chart.
The electronic-records exclusion applies only if the function is not intended to interpret or analyze patient records, including medical image data, for the purpose of the diagnosis, cure, mitigation, prevention, or treatment of a disease or condition.
Section 520(o)(1)(D) excludes a software function for transferring, storing, converting formats, or displaying clinical laboratory test or other device data and results, findings by a health care professional about that data, general information about those findings, and general background information about the laboratory test or other device.
The data-display exclusion does not cover a function intended to interpret or analyze clinical laboratory test or other device data, results, and findings. Section 520(o)(1)(E), the clinical decision support exclusion, does not cover a function intended to acquire, process, or analyze a medical image or a signal from an in vitro diagnostic device or a pattern or signal from a signal acquisition system.
The clinical decision support exclusion reaches a function intended for supporting or providing recommendations to a health care professional about prevention, diagnosis, or treatment of a disease or condition.
It also requires that the function enable the health care professional to independently review the basis for the recommendations so that it is not the intent that the professional rely primarily on any of them to make a clinical diagnosis or treatment decision regarding an individual patient.
For a product with an excluded software function and a function that meets the device definition, the Secretary shall not regulate the excluded software function as a device, but may assess its impact on the device function when assessing the device function's safety and effectiveness.
A software function described in paragraph (1)(C), (D), or (E) is not excluded from the device definition if the Secretary finds that its use would be reasonably likely to have serious adverse health consequences and identifies it in a final order issued after notice in the Federal Register and a comment period of not less than 30 calendar days.
Nothing in section 520(o) limits the Secretary's authority to regulate software as a device if the software meets the criteria under section 513(a)(1)(C). The provision narrows the definition of device in section 201(h) and sets no duty of its own.
A person required to register who proposes to begin introducing a device intended for human use into interstate commerce for commercial distribution must, at least ninety days beforehand, report to the Secretary or an accredited person the class in which the device is classified and the action taken to comply with the requirements of section 514 or 515 that apply to it.
A class III device that is subject to a premarket approval order, or is class III by operation of section 513(f), must have an approved application for premarket approval unless exempt under section 520(g). Section 301(a) prohibits the introduction or delivery for introduction into interstate commerce of a device that is adulterated or misbranded.
A person who violates section 301 shall be imprisoned for not more than one year or fined not more than $1,000, or both, and for a repeat violation or one committed with intent to defraud or mislead, imprisoned for not more than three years or fined not more than $10,000, or both. Proceedings for the enforcement of the Act, or to restrain violations of it, are brought by and in the name of the United States. Section 3060(a) of Public Law 114-255 added subsection (o) to section 520. Public Law 114-255 was enacted on .
When LexLint raises it
When your app profile says your app distributes a software product or makes health care decisions.