Acumen Hypotension Prediction Index – EV1000 Clinical Platform, Acumen Hypotension Prediction Index – HemoSphere Advanced Monitoring Platform, Acumen Hypotension Prediction Index – HemoSphere Advanced Monitoring Platform - Pressure
Applicant
Edwards Lifeciences, LLC
Product Code
QAQ · Cardiovascular
Decision Date
May 21, 2019
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 870.2210
Device Class
Class 2
Attributes
AI/ML
AI Performance
Output
Algorithm
Acceptance
Observed
Dev DS
Dev Readers
Test DS
Test Readers
Hypotension Prediction
—
—
—
—
—
—
—
Indications for Use
The Edwards Lifesciences Acumen Hypotension Prediction Index feature provides the clinician with physiological insight into a patient's likelihood of future hypotensive events (defined as mean arterial pressure < 65 mmHg for at least one minute in duration) and the associated hemodynamics. The Acumen HPI feature is intended for use in surgical or non-surgical patients receiving advanced hemodynamic monitoring. The Acumen HPI feature is considered to be additional quantitative information regarding the patient's physiological condition for reference only and no therapeutic decisions should be made based solely on the Hypotension Prediction Index (HPI) parameter.
Device Story
Software feature for EV1000 and HemoSphere monitoring platforms; inputs arterial pressure waveforms from radial arterial catheter via FloTrac IQ or Acumen IQ transducer. Calculates Hypotension Prediction Index (HPI) representing likelihood of hypotensive event (MAP < 65 mmHg) within 15 minutes; scale 0-100. Also calculates Dynamic Arterial Elastance (Eadyn) and Systolic Slope (dP/dt). Used in clinical settings by clinicians to gain physiological insight; provides adjunctive quantitative information. Does not replace clinical judgment; therapeutic decisions require review of patient hemodynamics. Benefits include early identification of potential hypotension, allowing proactive clinical management.
Clinical Evidence
Clinical performance data provided to demonstrate substantial equivalence for use in non-surgical patients. Data supports that the HPI software performance in non-surgical patients is equivalent to its performance in surgical patients.
Technological Characteristics
Software-based feature running on EV1000 and HemoSphere monitoring platforms. Uses arterial pressure waveform data from extravascular blood pressure transducers. Provides HPI, Eadyn, and dP/dt parameters. No hardware modifications from predicate.
Indications for Use
Indicated for surgical or non-surgical patients receiving advanced hemodynamic monitoring to provide insight into the likelihood of future hypotensive events (MAP < 65 mmHg for at least one minute).
Regulatory Classification
Identification
The adjunctive predictive cardiovascular indicator is a prescription device that uses software algorithms to analyze cardiovascular vital signs and predict future cardiovascular status or events. This device is intended for adjunctive use with other physical vital sign parameters and patient information and is not intended to independently direct therapy.
Special Controls
*Classification.* Class II (special controls). The special controls for this device are:(1) A software description and the results of verification and validation testing based on a comprehensive hazard analysis and risk assessment must be provided, including:
(i) A full characterization of the software technical parameters, including algorithms;
(ii) A description of the expected impact of all applicable sensor acquisition hardware characteristics and associated hardware specifications;
(iii) A description of sensor data quality control measures;
(iv) A description of all mitigations for user error or failure of any subsystem components (including signal detection, signal analysis, data display, and storage) on output accuracy;
(v) A description of the expected time to patient status or clinical event for all expected outputs, accounting for differences in patient condition and environment; and
(vi) The sensitivity, specificity, positive predictive value, and negative predictive value in both percentage and number form.
(2) A scientific justification for the validity of the predictive cardiovascular indicator algorithm(s) must be provided. This justification must include verification of the algorithm calculations and validation using an independent data set.
(3) A human factors and usability engineering assessment must be provided that evaluates the risk of misinterpretation of device output.
(4) A clinical data assessment must be provided. This assessment must fulfill the following:
(i) The assessment must include a summary of the clinical data used, including source, patient demographics, and any techniques used for annotating and separating the data.
(ii) The clinical data must be representative of the intended use population for the device. Any selection criteria or sample limitations must be fully described and justified.
(iii) The assessment must demonstrate output consistency using the expected range of data sources and data quality encountered in the intended use population and environment.
(iv) The assessment must evaluate how the device output correlates with the predicted event or status.
(5) Labeling must include:
(i) A description of what the device measures and outputs to the user;
(ii) Warnings identifying sensor acquisition factors that may impact measurement results;
(iii) Guidance for interpretation of the measurements, including a statement that the output is adjunctive to other physical vital sign parameters and patient information;
(iv) A specific time or a range of times before the predicted patient status or clinical event occurs, accounting for differences in patient condition and environment;
(v) Key assumptions made during calculation of the output;
(vi) The type(s) of sensor data used, including specification of compatible sensors for data acquisition;
(vii) The expected performance of the device for all intended use populations and environments; and
(viii) Relevant characteristics of the patients studied in the clinical validation (including age, gender, race or ethnicity, and patient condition) and a summary of validation results.
FloTrac IQ or Acumen IQ extravascular blood pressure transducer (K152980)
Submission Summary (Full Text)
{0}------------------------------------------------
Image /page/0/Picture/0 description: The image contains the logo of the U.S. Food and Drug Administration (FDA). The logo consists of two parts: the Department of Health & Human Services logo on the left and the FDA logo on the right. The FDA logo features the letters "FDA" in a blue square, followed by the words "U.S. FOOD & DRUG ADMINISTRATION" in blue text.
Edwards Lifeciences, LLC Lisa Gilman Senior Manager, Regulatory Affairs One Edwards Way Irvine, California 92614
Re: K183646
Trade/Device Name: Acumen Hypotension Prediction Index Regulation Number: 21 CFR 870.2210 Regulation Name: Adiunctive Predictive Cardiovascular Indicator Regulatory Class: Class II Product Code: QAO Dated: May 16, 2019 Received: May 17, 2019
Dear Lisa Gilman:
We have reviewed your Section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database located at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting of medical device-related adverse events) (21 CFR 803) for devices or postmarketing safety reporting (21 CFR 4, Subpart B) for combination products (see
{1}------------------------------------------------
https://www.fda.gov/CombinationProducts/GuidanceRegulatoryInformation/ucm597488.html; good manufacturing practice requirements as set forth in the quality systems (OS) regulation (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR Part 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to http://www.fda.gov/MedicalDevices/Safety/ReportaProblem/default.htm.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/MedicalDevices/DeviceRegulationandGuidance/) and CDRH Learn (http://www.fda.gov/Training/CDRHLearn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (http://www.fda.gov/DICE) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
Matthew Hillebrenner Director Division of Cardiac Electrophysiology, Diagnostics and Monitoring Devices Office of Cardiovascular Devices Office of Product Evaluation and Quality Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
## Indications for Use
510(k) Number (if known) K183646
Device Name Acumen Hypotension Prediction Index
#### Indications for Use (Describe)
The Edwards Lifesciences Acumen Hypotension Prediction Index feature provides the clinician with physiological insight into a patient's likelihood of future hypotensive events (defined as mean arterial pressure < 65 mmHg for at least one minute in duration) and the associated hemodynamics. The Acumen HPI feature is intended for nonsurgical patients receiving advanced hemodynamic monitoring. The Acumen HPI feature is considered to be additional quantitative information regarding the patient's physiological condition for reference only and no therapeutic decisions should be made based solely on the Hypotension Prediction Index (HPI) parameter.
| Type of Use (Select one or both, as applicable) | |
|-------------------------------------------------------------------------------|------------------------------------------------------------------------------|
| <div> <span> </span> Prescription Use (Part 21 CFR 801 Subpart D) </div> | <div> <span> </span> Over-The-Counter Use (21 CFR 801 Subpart C) </div> |
### CONTINUE ON A SEPARATE PAGE IF NEEDED.
This section applies only to requirements of the Paperwork Reduction Act of 1995.
#### *DO NOT SEND YOUR COMPLETED FORM TO THE PRA STAFF EMAIL ADDRESS BELOW.*
The burden time for this collection of information is estimated to average 79 hours per response, including the time to review instructions, search existing data sources, gather and maintain the data needed and complete and review the collection of information. Send comments regarding this burden estimate or any other aspect of this information collection, including suggestions for reducing this burden, to:
> Department of Health and Human Services Food and Drug Administration Office of Chief Information Officer Paperwork Reduction Act (PRA) Staff PRAStaff@fda.hhs.gov
"An agency may not conduct or sponsor, and a person is not required to respond to, a collection of information unless it displays a currently valid OMB number."
{3}------------------------------------------------
# SECTION 5 – 510(k) SUMMARY
| Acumen™ Hypotension Prediction Index | |
|----------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| 510(k)<br>Submitter | Edwards Lifesciences, LLC |
| Contact<br>Person | Lisa Gilman |
| Date Prepared | May 17, 2019 |
| Trade Name | Acumen™ Hypotension Prediction Index |
| Common<br>Name | Adjunctive Predictive Cardiovascular Indicator |
| Classification<br>Name | Adjunctive Predictive Cardiovascular Indicator |
| Regulation<br>Class / Product<br>Code | 21 CFR 870.2210/Class II/QAQ |
| Predicate<br>Device(s) | Acumen Hypotension Prediction Index, DEN160044 |
| Device<br>Description | The Acumen Hypotension Prediction Index Feature (DEN160044) consists<br>of software running on the Edwards Lifesciences EV1000 Clinical Platform<br>(DEN160044) and HemoSphere Advanced Monitoring Platform (K180881)<br>paired with the FloTrac IQ or Acumen IQ extravascular blood pressure<br>transducer (K152980) and a radial arterial catheter. The software includes<br>the Acumen Hypotension Prediction Index (HPI), the Dynamic Arterial<br>Elastance Parameter (Eadyn), the Systolic Slope Parameter (dP/dt), and<br>additional graphical user interface features.<br>The Acumen Hypotension Prediction Index is an index related to the<br>likelihood of a patient experiencing a hypotensive event (defined as mean<br>arterial pressure (MAP) $ < 65 $ mmHg for one minute in duration) within 15<br>minutes, where zero (0) indicates low likelihood and one hundred (100)<br>indicates high likelihood. The Acumen Hypotension Prediction Index, HPI,<br>should not be used exclusively to treat patients. A review of the patient's<br>hemodynamics is recommended prior to initiating treatment. |
| Indications for<br>Use/Intended<br>Use | The Edwards Lifesciences Acumen Hypotension Prediction Index feature<br>provides the clinician with physiological insight into a patient's likelihood<br>of future hypotensive events (defined as mean arterial pressure < 65 mmHg<br>for at least one minute in duration) and the associated hemodynamics. The<br>Acumen HPI feature is intended for use in surgical or non-surgical patients<br>receiving advanced hemodynamic monitoring. The Acumen HPI feature is<br>considered to be additional quantitative information regarding the patient's<br>physiological condition for reference only and no therapeutic decisions<br>should be made based solely on the Hypotension Prediction Index (HPI)<br>parameter. |
| Comparison to<br>Predicate<br>Device | The Acumen™ Hypotension Prediction Index Feature Software<br>(DEN160044, granted March 16, 2018)<br><br>Modifications<br>The labeling of the EV1000A Clinical Platform and the<br>HemoSphere Advanced Monitoring Platform has been modified to<br>expand the indications for use from surgical [operating room (OR)]<br>patients to surgical or non-surgical patients. The graphical user interface of the EV1000A Clinical Platform and<br>the HemoSphere Advanced Monitoring Platform has been modified<br>to define:<br>dP/dt parameter as systolic slope; and, Eadyn parameter as dynamic arterial elastance. There are no modifications to the hardware of the monitoring<br>platforms. |
| Performance<br>Data | Clinical Performance<br>Clinical performance data were provided to demonstrate substantial<br>equivalence of use of the Acumen™ Hypotension Prediction Index<br>software. |
| Conclusion | Overall Conclusion<br>The clinical performance data demonstrate that the Acumen™ Hypotension<br>Prediction Index software used in non-surgical patients is substantially<br>equivalent to use in surgical patients. |
{4}------------------------------------------------
Two short videos show you everything — or skip straight to the written tutorial if you'd rather read. You can reopen this any time from the Tutorial button in the top bar.
Part 1 — Search, results, and everyday workflows 16 min
Part 2 — Embeddings: the galaxy map 3 min
1. Search: exact and fuzzy
Type a phrase like "coronary artery calcification" into the search box. You get two kinds of results. Exact results match the literal phrase — prefix searches work ("coronary artery calcificati") but suffix searches do not. Fuzzy results match on the meaning and intent of your phrase rather than the exact words, and are sorted by relevance score. Hover over the Exact or Fuzzy badge on any row to see exactly why it matched.
Use the checkboxes above the results to narrow: SaMD keeps only software-only devices, AI / ML keeps only devices with AI.
Exact vs. fuzzy search: what's the difference?
Exact matches on the literal phrase (prefix search works, suffix does not). Fuzzy matches on the meaning and intent of the phrase rather than the exact words. Hover over the badge on any row to see why it matched.
You search "coronary artery calcification" and want only software devices with AI. What two filters do you apply?
Narrow by SaMD (software-only devices), then narrow by AI/ML (devices with AI).
2. The results table
Scroll right in the results table. The intended use is extracted for you — no need to open the PDF. The device story gives a high-level snapshot of what the device does and how it's used. The AI Performance sub-table shows each output name, acceptance criteria, observed values, and development/test dataset descriptions — the same format Innolitics uses for regulatory strategy outputs, and the fastest high-level fingerprint of an AI device. It is AI-generated but has been very reliable in practice.
Where do you find a device's intended use without opening the PDF?
Scroll right in the search results table. The intended use column is extracted for you; no need to dig into the 510(k) summary PDF.
What does the AI Performance sub-table show, and why is it useful?
Output name, acceptance criteria, observed values, development dataset description, and test dataset description. It's the same format we use for regulatory strategy output and Fast 510(k) input, and the fastest high-level fingerprint of an AI device. AI-generated but reliable in practice.
3. Judging fuzzy relevance
Fuzzy results trail off in relevance as you scroll. Use three signals to decide how far down to go: the fuzzy badge explanations, the intended use column, and whether your target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, you're past the relevant zone. A top hit with a low score (~0.4) and a stretched explanation is a hint the closest predicates are far away — the project may be headed for De Novo. Note the fuzzy search is a pattern match: it doesn't handle negation ("not") well, and hardware devices can appear — filter by SaMD/AI ML to cut them.
How do you judge how far down fuzzy search results to go?
Use the relevancy signals: the fuzzy badge explanations, the intended use column, and whether the target output (e.g., Cobb angle) still appears in the AI Performance sub-table. Once it stops appearing, results are trailing off in relevancy.
4. Device detail page: chat and citations
Click a device name to open its detail page: device facts on the left, a chat window on the right. Ask something like "Describe the training data". The answer carries little citation bubbles — click one to jump to the highlighted passage in the source PDF, so you can verify every AI answer against the document. There's also a Download PDF button for sharing.
How do you verify an AI chat answer on the device detail page?
Click the citation bubbles to jump to the relevant highlight in the source document.
Reading rule for every project: how many summaries do you read in full?
At least the three most relevant 510(k) or De Novo summaries, in full. After that, use targeted chat questions to confirm your memory quickly. The tool supports this professional habit — it doesn't replace it.
5. Side-by-side comparison
Select multiple rows in the results table (aim for under ~10), then open the PDF Viewer tab. Ask one question — it goes to all selected devices in parallel, each with citations. This is the fastest way to compare and contrast devices: training data, PCCP scope, how they handled adding new scanners, and so on.
What does the side-by-side PDF viewer mode do?
Select multiple devices, open the PDF viewer tab, and ask one question (e.g., "Describe the training data"). It queries all selected devices simultaneously with citations, so you can compare and contrast quickly.
6. Collections
With rows selected, go to the Collections tab and create a labeled collection (e.g., "Cobb Angle Project"). Reload that selection any time — before a client call, pull up the collection and ask questions across all of its devices at once.
How do you save a set of selected devices for later use?
Select the rows, go to the Collections tab, and create a labeled collection (e.g., "Cobb Angle Project"). You can reload the selection anytime and carry it into the PDF viewer and other tabs that support selections.
7. Product codes and the regulations tree
Click a product code in the results to jump to it in the regulations tree — identification text, sibling product codes, and devices you can open in a PDF viewer on the right. Click a regulation number to see its identification, special controls, and related product codes. You can also search by product code or regulation number at the top of the tree. Always read the special controls if any exist for your device — it broadens your search and sharpens pre-kickoff research.
What can you do from the regulations tree view?
Browse product codes and regulation numbers, read the identification text and special controls, browse sibling product codes, open device PDFs on the right, and search by product code or regulation number at the top of the tree.
8. Chart view
Click Show Chart and segment by regulation number (or product code) to see which regulations dominate your result set. Clicking a regulation takes you into the regulations tree. Great for spotting that most matches are, say, hardware laparoscopic devices — a cue to go back and filter.
How do you see which regulations dominate a search result set?
Click "Show Chart" and segment by Regulation Number. Clicking a regulation takes you to the regulations tree.
9. The predicate graph
Open the Predicates tab for a family-tree view of predicate relationships. Click a node to trace its parents and children; selections from search carry over pre-selected. Commonly predicated devices are worth reading — a lot of people predicated them for a reason. The visual lineage is also handy on client calls, e.g. to show how a predicate family evolved and justify why your predicate still holds.
In the predicate graph, why are commonly predicated devices worth reading?
A lot of people predicated them for a reason. Clicking a node traces parents and children, and selections from search carry over pre-selected.
10. Embeddings: the galaxy map
The Embeddings tab plots every matching document in a 2-D "galaxy map" where semantically similar devices cluster together. Hover or click clusters to explore, and let AI label the clusters for you. Embeddings beat product codes for grouping: two devices can carry different product codes (LLZ vs. QIH) yet do the same thing — the embedding captures the meaning of the intended use and device story. This is also exactly how retrieval-augmented generation (RAG) works under the hood, and it makes a great visual on client calls.
Try it yourself
Head to the search page and work through a few of these AI/ML fuzzy searches to build intuition: perivascular fat on CT · aortic valve calcification opportunistic screening on noncontrast CT · breast cancer prediction on digital pathology slides · autism detection · gestational age prediction · a hearing aid that can also detect a pulse · foundation model based analysis of ECG · large language models · penetration test. Watch how the relevance scores, intended use, and AI Performance tables tell you when results stop being meaningful.
