The HyperVue Software is intended to be used only with compatible HyperVue Imaging Systems and Starlight Imaging Catheter. The HyperVue Imaging System is intended for the imaging of coronary arteries and is indicated in patients who are candidates for transluminal interventional procedures. The Starlight Imaging Catheter is intended for use in vessels 2.0 to 5.2 mm in diameter. The Starlight Imaging Catheter is not intended for use in a target vessel which has undergone a previous bypass procedure. The NIRS capability of the HyperVue Imaging System is intended for the detection of lipid core containing plaques of interest. The NIRS capability of the HyperVue Imaging System is intended for the assessment of coronary artery lipid core burden. The NIRS capability of the HyperVue Imaging System is intended for the identification of patients and plaques at increased risk of major adverse cardiac events.
Device Story
HyperVue Software (v2.0) operates on HyperVue Imaging System using Starlight Imaging Catheter to acquire/process OCT-NIRS data. System delivers infrared light to coronary tissue; measures reflections to construct high-resolution, real-time images. Used in cardiac catheterization labs by physicians/healthcare professionals. Software provides user interface for clinical workflows, automated measurement tools (border contours, cross-sectional area, percent stenosis), and image storage. New functionality enables DICOM data export to hospital PACS servers. Physicians evaluate images alongside other clinical tests to assess coronary arteries, identify lipid core plaques, and determine risk of major adverse cardiac events. Benefits include improved visualization and data integration for interventional decision-making.
Clinical Evidence
Bench testing only. Software verification and validation performed per 21 CFR 820.30, including unit, integration, system-level, regression, and cybersecurity testing (static analysis, vulnerability scanning, penetration testing). All pre-determined acceptance criteria met.
Technological Characteristics
Windows-based (Windows Enterprise IoT) software. Infrared light-based OCT-NIRS sensing. Connectivity: Networked (DICOM export to PACS). Cybersecurity: Robust controls implemented per FDA guidance, including threat modeling and security control verification. Software version 2.0.
Indications for Use
Indicated for patients who are candidates for transluminal interventional procedures requiring coronary artery imaging. Starlight Imaging Catheter use restricted to vessels 2.0 to 5.2 mm in diameter; contraindicated in target vessels with previous bypass procedures.
Regulatory Classification
Identification
An ultrasonic pulsed echo imaging system is a device intended to project a pulsed sound beam into body tissue to determine the depth or location of the tissue interfaces and to measure the duration of an acoustic pulse from the transmitter to the tissue interface and back to the receiver. This generic type of device may include signal analysis and display equipment, patient and equipment supports, component parts, and accessories.
Special Controls
*Classification.* Class II (special controls). A biopsy needle guide kit intended for use with an ultrasonic pulsed echo imaging system only is exempt from the premarket notification procedures in subpart E of part 807 of this chapter subject to the limitations in § 892.9.
{0}
FDA U.S. FOOD & DRUG ADMINISTRATION
July 16, 2025
SpectraWAVE, Inc.
Ankit Shah
Sr. Manager Regulatory Affairs
12 Oak Park Drive
Bedford, Massachusetts 01730
Re: K251198
Trade/Device Name: HyperVue™ Software
Regulation Number: 21 CFR 892.1560
Regulation Name: Ultrasonic Pulsed Echo Imaging System
Regulatory Class: Class II
Product Code: NQQ
Dated: April 17, 2025
Received: April 17, 2025
Dear Ankit Shah:
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}
K251198 - Ankit Shah
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 System (QS) regulation (21 CFR Part 820), which includes, but is not limited to, 21 CFR 820.30, Design controls; 21 CFR 820.90, Nonconforming product; and 21 CFR 820.100, Corrective and preventive action. Please note that regardless of whether a change requires premarket review, the QS regulation requires device manufacturers to review and approve changes to device design and production (21 CFR 820.30 and 21 CFR 820.70) and document changes and approvals in the device master record (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 systems (QS) regulation (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}
K251198 - Ankit Shah
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,
# Aneesh S. Deoras -S
Aneesh Deoras
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}
| 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. | K251198 | ? |
| Please provide the device trade name(s). | | ? |
| HyperVue™ Software | | |
| Please provide your Indications for Use below. | | ? |
| The HyperVue Software is intended to be used only with compatible HyperVue Imaging Systems and Starlight Imaging Catheter.
The HyperVue Imaging System is intended for the imaging of coronary arteries and is indicated in patients who are candidates for transluminal interventional procedures.
The Starlight Imaging Catheter is intended for use in vessels 2.0 to 5.2 mm in diameter.
The Starlight Imaging Catheter is not intended for use in a target vessel which has undergone a previous bypass procedure.
The NIRS capability of the HyperVue Imaging System is intended for the detection of lipid core containing plaques of interest.
The NIRS capability of the HyperVue Imaging System is intended for the assessment of coronary artery lipid core burden.
The NIRS capability of the HyperVue Imaging System is intended for the identification of patients and plaques at increased risk of major adverse cardiac events. | | |
| 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) | ? |
HyperVue™ Software
{4}
510(k) Summary
# 510(k) Summary
This summary of 510(k) safety and effectiveness information is being submitted in accordance with the requirements of SMDA 1990 and 21 CFR 807.92.
# 1. Submitter Name & Address:
510(k) Owner: SpectraWAVE, Inc.
Address: 12 Oak Park Drive
Bedford, MA 01730
(781) 701-8148
Official Contact: Ankit K. Shah
Senior Manager Regulatory Affairs
(323) 401 6480
ashah@spectrawave.com
Date Prepared: 4/15/2025
510(k) Number: K251198
# 2. Device Name:
| Trade Name | HyperVue™ Software |
| --- | --- |
| Common Name | Optical Coherence Tomography Imaging System |
| Classification Name | System, Imaging, Optical Coherence Tomography |
| Regulation Number | 21 CFR 892.1560 |
| Product Code | NQQ |
| Classification | Class II |
# 3. Predicate Device:
- Predicate Device: K230691, HyperVue Imaging System
- Recall Status: The predicate device (K230691) has not been subject to a design-related recall.
# 4. Device Description:
The HyperVue Software (2.0) is resident on the HyperVue Imaging System (K230691) and is used with the Starlight Imaging Catheter (K243016). The HyperVue Software provides a user interface for executing clinical workflows, acquiring and processing
K251198
Premarket Notification, HyperVue™ Software
{5}
OCT-NIRS data, and exporting patient data. The software update introduces the ability to connect to hospital PACS servers for data export.
## Indications for Use Statement:
The HyperVue Software is intended to be used only with compatible HyperVue Imaging Systems and Starlight Imaging Catheter.
The HyperVue Imaging System is intended for the imaging of coronary arteries and is indicated in patients who are candidates for transluminal interventional procedures.
The Starlight Imaging Catheter is intended for use in vessels 2.0 to 5.2 mm in diameter.
The Starlight Imaging Catheter is not intended for use in a target vessel which has undergone a previous bypass procedure.
The NIRS capability of the HyperVue Imaging System is intended for the detection of lipid core containing plaques of interest.
The NIRS capability of the HyperVue Imaging System is intended for the assessment of coronary artery lipid core burden.
The NIRS capability of the HyperVue Imaging System is intended for the identification of patients and plaques at increased risk of major adverse cardiac events
## 5. Technological Characteristics:
The HyperVue Software has same intended use, indications for use, functionality, and operating principle as the predicate device. Differences, such as the ability to connect to PACS servers and historical software and algorithm changes do not raise new questions of safety and effectiveness.
| | PREDICATE DEVICE
SpectraWAVE, Inc.
HyperVue Imaging System
(K230691) | SUBJECT DEVICE
SpectraWAVE, Inc.
HyperVue™ Software (2.0) | Comparison |
| --- | --- | --- | --- |
| Product Code | Classification Product Code:
NQQ,
Subsequent Product Code:
ORD, OGZ, IYO | Classification Product Code:
NQQ | Same Classification Product Code |
| Intended Use | The HyperVue™ Imaging System and the SpectraWAVE Starlight™ Imaging Catheter are intended for the imaging of | The HyperVue™ Imaging System Software is used withing the HyperVue Imaging System which is used with the Starlight™ Imaging Catheter | Same |
K251198
Premarket Notification, HyperVue™ Software
{6}
| | PREDICATE DEVICE
SpectraWAVE, Inc.
HyperVue Imaging System
(K230691) | SUBJECT DEVICE
SpectraWAVE, Inc.
HyperVue™ Software (2.0) | Comparison |
| --- | --- | --- | --- |
| | coronary arteries. | intended for the imaging of coronary arteries. | |
| Intended Users | Physicians and healthcare professionals | Physicians and healthcare professionals | Same |
| Operational Environment | Cardiac catheterization laboratory | Cardiac catheterization laboratory | Same |
| Primary Functions | Delivers energy (infrared light) to the tissue.
Measures the depth and pattern of reflections from the tissue from the return near-infrared light to create high-resolution, real-time images.
Stores images for evaluation and review. | Measures the depth and pattern of reflections from the tissue from the return near-infrared light to create high-resolution, real-time images.
Stores images for evaluation and review. | Same |
| Image Creation, Display and Storage | Process reflected optical signals to construct images.
Display images.
Store images. | Process reflected optical signals to construct images.
Display images.
Store images. | Different
The difference compared to the predicate device includes extending the export feature to allow transferring DICOM format data to network connected hospital PACS servers |
| Measure Vessel Linear Dimensions | Calculate and display vessel diameter at user specified locations within the displayed image | Calculate and display vessel diameter at user specified locations within the displayed image | Same |
| Calculate Vessel Physical Parameters | Calculate and display mathematical comparisons of image data such as % reduction from average, length of narrowing, cross-sectional area. | Calculate and display mathematical comparisons of image data such as % reduction from average, length of narrowing, cross-sectional area. | Same |
| Use of Results | Physicians evaluate the images in combination with other tests and evaluations to | Physicians evaluate the images in combination with other tests and evaluations to | Same |
K251198
Premarket Notification, HyperVue™ Software
Page 3 of 5
{7}
| | PREDICATE DEVICE
SpectraWAVE, Inc.
HyperVue Imaging System
(K230691) | SUBJECT DEVICE
SpectraWAVE, Inc.
HyperVue™ Software (2.0) | Comparison |
| --- | --- | --- | --- |
| | assess the patient's coronary arteries. | assess the patient's coronary arteries. | |
| Operating System (OS) | Windows-based (Windows Enterprise IoT) | Windows-based (Windows Enterprise IoT) | Same |
| User Convenience Features | Computer-aided measurement tools, such as border contours, computation of cross-sectional area, user-selectable image overlays, and percent stenosis.
Display of live angiography imagery on the HyperVue Imaging System display monitors. | Computer-aided measurement tools, such as border contours, computation of cross-sectional area, user-selectable image overlays, and percent stenosis.
Display of live angiography imagery on the HyperVue Imaging System display monitors. | Different
New Features added include:
Export feature allowing transferring DICOM format data to network connected hospital PACS servers |
## 6. Performance Data:
## 6.1 Non-Clinical Testing:
HyperVue software was tested in accordance with an established test plan that fully evaluated all functions performed by the software. Design verification documents were developed to provide evidence for unit, integration, system level, regression, information security, and validation software tests. In addition to the software verification, cybersecurity testing including Static Code Analysis, Vulnerability Scanning, Penetration Testing, verification of Security Controls, and interoperability assessment was performed as per FDA guidance "Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions". Additionally, User Requirement, Design Requirement, and Cybersecurity test reports were developed. The HyperVue software passed all pre-determined acceptance criteria identified in the test plan.
Verification and validation testing were completed in accordance with the company's Design Control process in compliance with 21 CFR Part 820.30, which included testing that fulfills the requirements of FDA "Guidance on Software Contained in Medical Devices". Potential security and safety related risk which includes unauthorized system access and misuse of patient data arising from the new or updated features were analyzed and satisfactorily mitigated by implementing and testing robust cybersecurity
K251198
Premarket Notification, HyperVue™ Software
{8}
controls consistent with the SpectraWAVE's SPDF and the Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions. threat model. Instructions for Cybersecurity and Account Settings were included in the device labeling for the HyperVue Software.
HyperVue is substantially equivalent in design concepts, technologies and operating principle to the identified predicate. This version of the HyperVue software does not present any new questions of safety or effectiveness.
7. Conclusion and Statement of Equivalence:
The information presented in this 510(k) submission demonstrates that the HyperVue Software is as safe and as effective, and performs as well as or better than the predicate device, and is therefore considered substantially equivalent to the predicate device.
K251198
Premarket Notification, HyperVue™ Software
Page 5 of 5
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.