The HemoSphere Nano™ Monitor when used with a compatible non-invasive finger cuff is indicated for adult patients (≥ 18 years of age) in whom cardiac function parameters need to be evaluated as part of a patient's assessment. The HemoSphere Nano™ Monitor and compatible finger cuffs non-invasively measure blood pressure and associated hemodynamic parameters. The HemoSphere Nano™ Monitor is intended to be used in a setting where healthcare is administered by qualified personnel or trained clinicians. The HemoSphere Nano™ Monitor is intended for use with compatible non-invasive finger cuff for noninvasive measurement of blood pressure and associated hemodynamic parameters.
Device Story
Hand-held monitor; collects arterial pressure waveform data via connected non-invasive finger cuff (Acumen IQ Plus); utilizes volume-clamp methodology to transform pressure signals into blood pressure and hemodynamic parameters; displays data for up to 10 minutes for spot-check/point-in-time assessment; used in healthcare settings by qualified personnel/clinicians; no physiological alarms; provides unified, compact solution by integrating ClearSight module and pressure controller into monitor body; output used by clinicians for patient assessment; benefits include portable, non-invasive hemodynamic monitoring.
Clinical Evidence
Bench testing only. Verification and validation activities confirmed performance specifications met. Bench simulation and volunteer/participant data used to test measured and derived parameters. Usability study conducted per IEC 62366.
Technological Characteristics
Hand-held monitor; volume-clamp principle of operation; rechargeable battery; integrated pump and manifold; compatible with Acumen IQ Plus finger cuffs. Complies with IEC 60601-1, IEC 60601-1-2, IEC 60601-1-6, IEC 60601-1-8, IEC 62304, IEC 62366, IEC 60601-2-57, and ISO 81060-2.
Indications for Use
Indicated for adult patients (≥ 18 years) requiring evaluation of cardiac function parameters as part of clinical assessment.
Regulatory Classification
Identification
A programmable diagnostic computer is a device that can be programmed to compute various physiologic or blood flow parameters based on the output from one or more electrodes, transducers, or measuring devices; this device includes any associated commercially supplied programs.
{0}
FDA U.S. FOOD & DRUG ADMINISTRATION
February 24, 2026
Edwards Lifesciences, LLC.
Kshama Pai
Manager, Regulatory Affairs
One Edwards Way
Irvine, California 92614
Re: K253186
Trade/Device Name: HemoSphere Nano Monitor (HSNANO1)
Regulation Number: 21 CFR 870.1425
Regulation Name: Programmable Diagnostic Computer
Regulatory Class: Class II
Product Code: DQK, DXN
Dated: January 26, 2026
Received: January 26, 2026
Dear Kshama Pai:
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 (the 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 available 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.
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K253186 - Kshama Pai
Page 2
Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device" (https://www.fda.gov/media/99812/download) and "Deciding When to Submit a 510(k) for a Software Change to an Existing Device" (https://www.fda.gov/media/99785/download).
Your device is also subject to, among other requirements, the Quality Management System Regulation (QMSR) (21 CFR Part 820), which includes, but is not limited to, ISO 13485 clause 7.3 (Design controls), ISO 13484 clause 8.3 (Nonconforming product), and ISO 13485 clause 8.5 (Corrective and preventative action). Please note that regardless of whether a change requires premarket review, the QMSR requires device manufacturers to review and approve changes to device design and production (ISO 13485 clause 7.3 and 21 CFR 820.70) and document changes and approvals in the Medical Device File (21 CFR 820.181).
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 (reporting of medical device-related adverse events) (21 CFR Part 803) for devices or postmarketing safety reporting (21 CFR Part 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reporting-combination-products); good manufacturing practice requirements as set forth in the Quality Management System Regulation (QMSR) (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR Part 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR Parts 1000-1050.
All medical devices, including Class I and unclassified devices and combination product device constituent parts are required to be in compliance with the final Unique Device Identification System rule ("UDI Rule"). The UDI Rule requires, among other things, that a device bear a unique device identifier (UDI) on its label and package (21 CFR 801.20(a)) unless an exception or alternative applies (21 CFR 801.20(b)) and that the dates on the device label be formatted in accordance with 21 CFR 801.18. The UDI Rule (21 CFR 830.300(a) and 830.320(b)) also requires that certain information be submitted to the Global Unique Device Identification Database (GUDID) (21 CFR Part 830 Subpart E). For additional information on these requirements, please see the UDI System webpage at https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/unique-device-identification-system-udi-system.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-devices/medical-device-safety/medical-device-reporting-mdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). 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 (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-
{2}
K253186 - Kshama Pai
Page 3
assistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
# STEPHEN C. BROWNING -S
LCDR Stephen Browning
Assistant 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
{3}
Page 1 of 1
| Indications for Use | | |
| --- | --- | --- |
| Please type in the marketing application/submission number, if it is known. This textbox will be left blank for original applications/submissions. | K253186 | ? |
| Please provide the device trade name(s). | | ? |
| HemoSphere Nano Monitor (HSNANO1) | | |
| Please provide your Indications for Use below. | | ? |
| The HemoSphere Nano™ Monitor when used with a compatible non-invasive finger cuff is indicated for adult patients (≥ 18 years of age) in whom cardiac function parameters need to be evaluated as part of a patient's assessment. The HemoSphere Nano™ Monitor and compatible finger cuffs non-invasively measure blood pressure and associated hemodynamic parameters. | | |
| Please select the types of uses (select one or both, as applicable). | ☑ Prescription Use (Part 21 CFR 801 Subpart D) | ? |
| | ☐ Over-The-Counter Use (21 CFR 801 Subpart C) | |
{4}
510(k) Summary – HemoSphere Nano Monitor
I. **Submitter:**
Sponsor: Edwards Lifesciences LLC
One Edwards Way
Irvine, CA 92614
Establishment Registration Number: 2015691
Contact Person: Kshama Pai
Manager, Regulatory Affairs
17200 Laguna Canyon Road,
Irvine, CA 92618
kshama.pai@bd.com
+1 (949) 628-0467
Date Prepared: January 23, 2026
II. **Device Information:**
Platform Name: HemoSphere Nano Monitoring System
Trade Name: HemoSphere Nano Monitor (HSNANO1)
Common Name: Computer, diagnostic, programmable
Noninvasive blood pressure measurement system
Classification Name: DQK Computer, diagnostic, programmable 21CFR 870.1425
DXN System, Measurement, Blood-Pressure, Non-Invasive 21 CFR 870.1130
III. **Predicate Device:**
Primary Predicate Device:
The HemoSphere Advanced Monitoring Platform (K243781 cleared July 23, 2025) is being utilized as the primary predicate for substantial equivalence to the inherent use and basic device functionality of non-invasive hemodynamic monitoring, the principle of operation of core ClearSight technology, the hemodynamic parameters measured, and compatible finger cuffs. The indications for use relative to non-invasive blood pressure hemodynamic monitoring are also equivalent between the subject device and primary predicate.
K253186
Page 1 of 6
{5}
IV. Device Description:
Device Description: The HemoSphere Nano Monitor is a hand-held monitoring device that measures the arterial pressure waveform collected from a connected non-invasive finger cuff and displays blood pressure and derived hemodynamic parameters. These parameters are continuously displayed for up to a period of 10 minutes, serving as a series of spot-check or point-in-time measurements. As such, the device does not feature any physiological alarms. It is compatible for use with the single use Acumen IQ Plus finger cuff (AIQCA2; cleared via K243781).
The HemoSphere Nano Monitor utilizes the same principle of operation, algorithms, and mechanism for non-invasive monitoring hemodynamic parameters as the primary predicate, HemoSphere Advanced Monitoring Platform (K243781). When compared to the primary predicate, the subject device introduces a new hardware configuration with a smaller form factor. This new hardware configuration is powered by a rechargeable battery and features a smaller display to enable the product to be handheld. Contrary to the predicate which incorporates a modular approach, the subject integrates all existing non-invasive technology (i.e., the ClearSight Module and Pressure Controller) into the HemoSphere Nano Monitor body itself to provide a unified and compact solution for non-invasive hemodynamic monitoring.
V. Indications for Use:
Indications for Use: The HemoSphere Nano™ Monitor when used with a compatible non-invasive finger cuff is indicated for adult patients (≥ 18 years of age) in whom cardiac function parameters need to be evaluated as part of a patient assessment. The HemoSphere Nano™ Monitor and compatible finger cuffs noninvasively measure blood pressure and associated hemodynamic parameters.
Intended Use: The HemoSphere Nano™ Monitor is intended to be used in a setting where healthcare is administered by qualified personnel or trained clinicians. The HemoSphere Nano™ Monitor is intended for use with compatible non-invasive finger cuff for noninvasive measurement of blood pressure and associated hemodynamic parameters.
K253186
Page 2 of 6
{6}
VI. Comparison with predicate device(s):
Comparison of indications
The HemoSphere Nano Monitor (subject) and HemoSphere Advanced Monitoring Platform (predicate) have the following similarities:
- Subject and predicate have the same intended use, i.e., non-invasive measurement of blood pressure and associated hemodynamic parameters. No new functionality is being added as a result of this submission.
- Subject and predicate have the same indications as they are intended for use in adult patients (≥ 18 years of age) in whom cardiac function parameters need to be evaluated for patient assessment.
- Both subject and predicate devices are prescription use (Rx) devices that are intended for use by healthcare professionals only.
Comparison of technological characteristics
The ClearSight continuous non-invasive blood pressure monitoring principle based on volume-clamp methodology is the fundamental technological principle for both subject and predicate devices.
At a high-level, the HemoSphere Nano Monitor (subject) and HemoSphere Advanced Monitoring Platform (predicate) have the following similarities:
- Subject and predicate have the same principle of operation and technological characteristics relative to non-invasive blood pressure measurement.
- The subject utilizes the same existing CNIBP Technology (i.e., same volume-clamp principle of operation and cleared algorithms) to measure arterial blood pressure.
- Subject provides the same derived hemodynamic parameters for display as the predicate. No new parameters are being added as a result of this submission. The performance requirements and specifications are equivalent between the subject and predicate device.
- Subject and predicate both use the same accessories i.e., Acumen IQ Plus finger cuffs.
K253186
Page 3 of 6
{7}
The HemoSphere Nano Monitor (subject) and HemoSphere Advanced Monitor (predicate) have the following differences:
- The predicate HemoSphere Advanced Monitoring Platform is modular and supports hemodynamic monitoring via invasive, minimally invasive and non-invasive modalities, whereas the subject only utilizes a subset of the overall functionality of the predicate (i.e., non-invasive hemodynamic monitoring).
- The subject has a streamlined GUI for display of CNIBP parameters only (i.e., subset of the GUI features of the predicate).
- The subject has a smaller form factor that integrates the CNIBP machinery (i.e., pump and manifold) into the monitor body to enable the device to be hand-held. This difference in size does not change the overall intended purpose as it does not have an impact on the CNIBP functionality or the associated performance specifications. Testing was performed to show the same performance specifications are met.
- Unlike the predicate which is intended for short-term continuous hemodynamic monitoring with alarms, the real-time data available on the subject is meant for transient use and spot-checking without physiological alarms in healthcare settings. These differences do not change the overall intended purpose as both have the purpose of non-invasive blood pressure monitoring. Additionally, both the subject and predicate devices are prescription use (Rx) devices that are intended for use by healthcare professionals only.
VII. Performance Data and Conclusion:
Performance Data (Bench and/or Clinical):
The following verification and validation activities were performed in support of a substantial equivalence determination for the subject HemoSphere Nano Monitor (new hardware configuration) to the predicate devices and to ensure the safety and effectiveness of the HemoSphere Nano Monitor.
System Verification (Non-clinical performance)
Completion of all verification and validation activities demonstrated that the subject device and its software meet their predetermined design and performance specifications. Verification activities performed confirmed that the differences in design, specifications, and materials do not adversely affect the safety and effectiveness of the subject device.
Mechanical, electrical, and system integration testing were successfully conducted to ensure the device met its requirements and to verify the safety and effectiveness of the device. System integration testing also ensured that the subject HemoSphere Nano Monitor functions as intended when
K253186
Page 4 of 6
{8}
connected to the Acumen IQ Plus finger cuffs. Bench testing was performed to verify the pneumatic pressure accuracy requirements pertaining to ClearSight technology were met and that the embedded algorithms were reliably translated and integrated. Measured and derived parameters were tested using a bench simulation and volunteer/participant data. All tests passed.
## Electrical Safety and Electromagnetic Compatibility (EMC)
Electrical safety and EMC testing were conducted on the subject HemoSphere Nano Monitoring Platform, consisting of the HemoSphere Nano Monitor and the Acumen IQ Plus finger cuff. The system complies with the IEC 60601-1, IEC 60601-1-2, IEC 60601-1-6, IEC 60601-1-8, IEC 62304, IEC 62366, IEC 60601-2-57, and ISO 81060-2. All tests passed.
## Software Verification
Software verification was performed per IEC 62304 and FDA’s Guidance, Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices (issued June 14, 2023), and General Principles of Software Validation (issued January 11, 2002). The HemoSphere Nano software was tested at a sub-system level to ensure the safety of the device. All tests passed.
Cybersecurity requirements and documentation for the HemoSphere Nano monitoring system were developed and assessed at system level in accordance with FDA’s Guidance, Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions (issued June 27, 2025). All cybersecurity risks were mitigated to an acceptable risk level based on the risk assessment.
## Usability Study
A Usability study was conducted per IEC 62366 and FDA’s guidance document, Applying Human Factors and Usability Engineering to Medical Devices (issued February 3, 2016), to investigate primary operating functions and critical tasks of the system for any usability issues that may lead to patient or user harm. The successful results provide objective evidence that the system is safe and effective with respect to the intended users, uses, and use environments.
## Conclusions
## Overall Conclusion:
The subject HemoSphere Nano Monitor has successfully passed functional and performance testing, including validation, software verification and validation, bench, and usability testing. Completion of all performance verification and validation activities demonstrated that the subject device meets their predetermined design and performance specifications. Verification activities performed confirmed that the
K253186
Page 5 of 6
{9}
differences in the features and design do not raise different questions of safety and effectiveness. The testing performed demonstrates that the HemoSphere Nano Monitor is substantially equivalent to its legally marketed predicate device.
K253186
Page 6 of 6
Predicate graph will load when search results are available.
Embedding visualization will load when search results are available.
PDF viewer will load when search results are available.
Loading panels...
Select an item from Submissions
Click any panel, subpart, regulation, product code, or device to see details here.
Section Matches
Results will appear here.
Product Code Matches
Results will appear here.
Special Control Matches
Results will appear here.
Loading collections...
Loading
My Alerts
You will receive email notifications based on the filters and frequency you set for each alert.
Sort by:
Create Alert
Search Filters
Agent Token
Create a read-only bearer token for Claude, ChatGPT, or other agents that can call HTTP APIs.
Copy this now. It will not be shown again.
Connected apps
Apps you authorized through browser sign-in. Disconnecting revokes their access immediately.
Learn the FDA Browser
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.