Updated:
ML Heart Alert Software: What the FDA Class II Rule Means
FDA now has a class II category for machine-learning heart alert software. Questions nurses and administrators can ask before go-live.
An alert that says a patient may have a heart condition changes what a nurse does next. Before software like that reaches a unit, hospital leaders need to know what the FDA has actually required of it. A rule published in the Federal Register on September 11, 2026 puts one kind of this software into a defined category. This post summarizes the rule in plain language. It is general information, not legal advice.
What the rule does
According to the Federal Register notice (document 2026-18612, effective September 11, 2026), FDA added 21 CFR 870.2380, “cardiovascular machine learning-based notification software,” as a class II device with special controls. The rule describes software that uses machine learning to estimate how likely a cardiovascular disease or condition is, to support referral or diagnostic follow-up. It flags one condition from one or more non-invasive physiological inputs during routine care. It is not meant to give diagnostic-quality output or to detect arrhythmias. The notice also says the device type is not exempt from premarket notification (510(k)).
What the special controls ask of the maker
The notice lists four groups of special controls:
- Clinical performance testing on real-world data from a representative population, separate from the training data, including results by subgroup and testing at three or more geographically diverse sites.
- Software verification and hazard analysis, including how sensor hardware affects performance and how poor input quality or user error is handled.
- Human factors assessment of the risk that intended users misread the output.
- Labeling that states known limits, interpretation guidance, and compatible sensor data.
Two labeling points matter on a ward. The label must warn users not to rely on a negative result to rule out follow-up, and must say the output does not replace a full clinical evaluation.
Questions a hospital team can ask
These come straight from the points above:
- Was performance tested on patients like ours, and at sites other than where the model was built?
- What happens when the sensor signal is poor? Who sees that, and what does the alert look like?
- When the software stays silent, how do we make sure staff still follow our usual assessment?
- Who is expected to act on an alert, and how fast?
Answers to the last two belong in your own workflow plan, not the vendor’s brochure. Confirm details with your compliance staff and clinical leaders.
Key takeaways
- FDA classified machine learning-based cardiovascular notification software as class II (21 CFR 870.2380), effective September 11, 2026.
- The software suggests a condition may be present so a clinician can follow up. It is not meant to give diagnostic-quality output.
- A negative result should not be used to rule out follow-up, according to the required labeling.
- “Cleared” does not mean “right for our patients”: ask about subgroup results, sensor quality, and who acts on an alert.
This site provides general information for research and education. It is not medical advice and does not replace diagnosis or guidance for any specific patient. It is not legal advice.