Rapid OH is a radiological computer aided triage and notification software indicated for suspicion of Obstructive Hydrocephalus (OH) in non-enhanced CT head images of adult patients. The device is intended to assist trained clinicians in workflow prioritization triage by providing notification of suspected findings in head CT images. Rapid OH uses an artificial intelligence algorithm to analyze images and highlight cases with suspected OH on a server or standalone desktop application in parallel to the ongoing standard of care image interpretation. The user is presented with notifications for cases with suspected OH findings. Notifications include compressed preview images, that are meant for informational purposes only and not intended for diagnostic use beyond notification. The device does not alter the original medical image and is not intended to be used as a diagnostic device. The results of Rapid OH are intended to be used in conjunction with other patient information and based on professional judgment, to assist with triage/prioritization of medical images. Notified clinicians are responsible for viewing full images per the standard of care.
Device Story
Rapid OH is a radiological computer-aided triage and notification software (SaMD) operating within the Rapid Platform. It processes non-contrast CT (NCCT) head images in DICOM format. An AI/ML algorithm analyzes images to detect suspected obstructive hydrocephalus (OH). The device operates in parallel to standard-of-care interpretation, providing notifications with compressed preview images to clinicians via PACS, workstation, email, or mobile. It does not alter original images or provide diagnostic results. It serves as a workflow prioritization tool to assist clinicians in identifying urgent cases. Benefits include reduced time to notification (mean 30.3 seconds), facilitating faster clinical review and decision-making for patients with potential OH.
Clinical Evidence
Standalone performance validation using 320 cases (diverse demographics, multiple scanner manufacturers, and various neurological confounders). Ground truth established by 2-3 experts. Primary endpoint: sensitivity 89.5% (95% CI: 0.837-0.935) and specificity 97.6% (95% CI: 0.940-0.991). Secondary endpoint: mean time to notification 30.3 seconds (range 10.5-55.5 seconds).
Technological Characteristics
SaMD; AI/ML-based image processing module. Operates within the integrated Rapid Platform. Inputs: DICOM non-contrast CT head images. Outputs: Notifications, reports, and secondary capture series. Conforms to NEMA PS 3.1-3.20 (DICOM), EN ISO 14971:2019 (risk management), IEC 62304:2006 (software lifecycle), and IEC 62366:2015 (usability).
Indications for Use
Indicated for adult patients with suspected Obstructive Hydrocephalus (OH) in non-enhanced CT head images. Contraindicated for patients with ventriculoperitoneal shunts. Excludes series with missing/improperly ordered slices, data <100kVp or >140kVp, and non-head/neck anatomy.
Regulatory Classification
Identification
Radiological computer aided triage and notification software is an image processing prescription device intended to aid in prioritization and triage of radiological medical images. The device notifies a designated list of clinicians of the availability of time sensitive radiological medical images for review based on computer aided image analysis of those images performed by the device. The device does not mark, highlight, or direct users' attention to a specific location in the original image. The device does not remove cases from a reading queue. The device operates in parallel with the standard of care, which remains the default option for all cases.
Special Controls
Radiological computer aided triage and notification software must comply with the following special controls: 1. Design verification and validation must include: i. A detailed description of the notification and triage algorithms and all underlying image analysis algorithms including, but not limited to, a detailed description of the algorithm inputs and outputs, each major component or block, how the algorithm affects or relates to clinical practice or patient care, and any algorithm limitations. ii. A detailed description of pre-specified performance testing protocols and dataset(s) used to assess whether the device will provide effective triage (e.g., improved time to review of prioritized images for pre-specified clinicians). iii. Results from performance testing that demonstrate that the device will provide effective triage. The performance assessment must be based on an appropriate measure to estimate the clinical effectiveness. The test dataset must contain sufficient numbers of cases from important cohorts (e.g., subsets defined by clinically relevant confounders, effect modifiers, associated diseases, and subsets defined by image acquisition characteristics) such that the performance estimates and confidence intervals for these individual subsets can be characterized with the device for the intended use population and imaging equipment. iv. Standalone performance testing protocols and results of the device. v. Appropriate software documentation (e.g., device hazard analysis; software requirements specification document; software design specification document; traceability analysis; description of verification and validation activities including system level test protocol, pass/fail criteria, and results). 2. Labeling must include the following: i. A detailed description of the patient population for which the device is indicated for use. ii. A detailed description of the intended user and user training that addresses appropriate use protocols for the device. iii. Discussion of warnings, precautions, and limitations must include situations in which the device may fail or may not operate at its expected performance level (e.g., poor image quality for certain subpopulations), as applicable. iv. A detailed description of compatible imaging hardware, imaging protocols, and requirements for input images. v. Device operating instructions. vi. A detailed summary of the performance testing, including: test methods, dataset characteristics, triage effectiveness (e.g., improved time to review of prioritized images for pre-specified clinicians), diagnostic accuracy of algorithms informing triage decision, and results with associated statistical uncertainty (e.g., confidence intervals), including a summary of subanalyses on case distributions stratified by relevant confounders, such as lesion and organ characteristics, disease stages, and imaging equipment.
*Classification.* Class II (special controls). The special controls for this device are:(1) Design verification and validation must include:
(i) A detailed description of the notification and triage algorithms and all underlying image analysis algorithms including, but not limited to, a detailed description of the algorithm inputs and outputs, each major component or block, how the algorithm affects or relates to clinical practice or patient care, and any algorithm limitations.
(ii) A detailed description of pre-specified performance testing protocols and dataset(s) used to assess whether the device will provide effective triage (
*e.g.,* improved time to review of prioritized images for pre-specified clinicians).(iii) Results from performance testing that demonstrate that the device will provide effective triage. The performance assessment must be based on an appropriate measure to estimate the clinical effectiveness. The test dataset must contain sufficient numbers of cases from important cohorts (
*e.g.,* subsets defined by clinically relevant confounders, effect modifiers, associated diseases, and subsets defined by image acquisition characteristics) such that the performance estimates and confidence intervals for these individual subsets can be characterized with the device for the intended use population and imaging equipment.(iv) Stand-alone performance testing protocols and results of the device.
(v) Appropriate software documentation (
*e.g.,* device hazard analysis; software requirements specification document; software design specification document; traceability analysis; description of verification and validation activities including system level test protocol, pass/fail criteria, and results).(2) Labeling must include the following:
(i) A detailed description of the patient population for which the device is indicated for use;
(ii) A detailed description of the intended user and user training that addresses appropriate use protocols for the device;
(iii) Discussion of warnings, precautions, and limitations must include situations in which the device may fail or may not operate at its expected performance level (
*e.g.,* poor image quality for certain subpopulations), as applicable;(iv) A detailed description of compatible imaging hardware, imaging protocols, and requirements for input images;
(v) Device operating instructions; and
(vi) A detailed summary of the performance testing, including: test methods, dataset characteristics, triage effectiveness (
*e.g.,* improved time to review of prioritized images for pre-specified clinicians), diagnostic accuracy of algorithms informing triage decision, and results with associated statistical uncertainty (*e.g.,* confidence intervals), including a summary of subanalyses on case distributions stratified by relevant confounders, such as lesion and organ characteristics, disease stages, and imaging equipment.
{0}
FDA U.S. FOOD & DRUG ADMINISTRATION
September 4, 2025
iSchemaView Inc.
James Rosa
Chief Regulatory and Compliance Officer
1120 Washington Ave.
Suite 200
Golden, CO 80401
Re: K251533
Trade/Device Name: Rapid Obstructive Hydrocephalus, Rapid OH
Regulation Number: 21 CFR 892.2080
Regulation Name: Radiological Computer Aided Triage And Notification Software
Regulatory Class: Class II
Product Code: QAS
Dated: August 5, 2025
Received: August 6, 2025
Dear James Rosa:
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}
K251533 - James Rosa
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-
{2}
K251533 - James Rosa
Page 3
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-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,
Jessica Lamb, Ph.D.
Assistant Director
Imaging Software Team
DHT8B: Division of Radiological Imaging Devices and Electronic Products
OHT8: Office of Radiological Health
Office of Product Evaluation and Quality
Center for Devices and Radiological Health
Enclosure
{3}
DEPARTMENT OF HEALTH AND HUMAN SERVICES
Food and Drug Administration
Indications for Use
Form Approved: OMB No. 0910-0120
Expiration Date: 06/30/2023
See PRA Statement below.
510(k) Number (if known)
K251533
Device Name
Rapid OH
Indications for Use (Describe)
Rapid OH is a radiological computer aided triage and notification software indicated for suspicion of Obstructive Hydrocephalus (OH) in non-enhanced CT head images of adult patients. The device is intended to assist trained clinicians in workflow prioritization triage by providing notification of suspected findings in head CT images.
Rapid OH uses an artificial intelligence algorithm to analyze images and highlight cases with suspected OH on a server or standalone desktop application in parallel to the ongoing standard of care image interpretation. The user is presented with notifications for cases with suspected OH findings. Notifications include compressed preview images, that are meant for informational purposes only and not intended for diagnostic use beyond notification. The device does not alter the original medical image and is not intended to be used as a diagnostic device.
The results of Rapid OH are intended to be used in conjunction with other patient information and based on professional judgment, to assist with triage/prioritization of medical images. Notified clinicians are responsible for viewing full images per the standard of care.
Contraindications/Limitations/Exclusions:
- Rapid OH is intended for use for adult patients.
- Input data image series containing excessive patient motion or metal implants may impact module analysis accuracy, robustness and quality.
- Ventriculoperitoneal shunts are contraindicated
Exclusions:
- Series with missing slices or improperly ordered slices
- data acquired at x-ray tube voltage < 100kVp or > 140kVp.
- data not representing human head or head/neck anatomical regions
Type of Use (Select one or both, as applicable)
☑ Prescription Use (Part 21 CFR 801 Subpart D)
☐ Over-The-Counter Use (21 CFR 801 Subpart C)
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."
FORM FDA 3881 (6/20)
Page 1 of 1
PSC Publishing Services (301) 443-6740
{4}
iSchemaView - Traditional 510(k) Rapid OH
510(k) Summary
# K251533 510(k) Summary
# iSchemaview, Inc.'s Rapid OH
This document contains the $510(\mathrm{k})$ summary for the iSchemaview Rapid OH device. The content of this summary is based on the requirements of 21 CFR Section 807.92(c).
# Applicant Name and Address:
Name: iSchemaview, Inc.
Address: 1120 Washington St., Suite 200
Golden, CO 80401
Official Contact: Jim Rosa
Phone: (303) 704-3374
Email: rosa@ischemaview.com
# Summary Preparation Date:
August 5, 2025
# Device Name and Classification:
Trade Name: Rapid Obstructive Hydrocephalus, Rapid OH
Common Name: Medical image management and processing system
Classification: II
Product Code: Primary: QAS
Regulation No: 21 C.F.R. §892.2080
Classification: Radiology Devices
Panel:
# Predicate Devices:
The iSchemaview Rapid OH Analysis Module is claimed to be substantially equivalent to the legally marketed predicate, Rapid SDH (K232436).
# Device Description:
Rapid OH software device is a radiological computer-aided triage and notification software device using AI/ML. The Rapid OH device is a non-contrast CT (NCCT) processing module which operates within the integrated Rapid Platform to provide a notification of suspected findings of obstructive hydrocephalus (OH). The Rapid OH device is SaMD which analyzes input NCCT images that are provided in DICOM format for notification of suspected findings for workflow prioritization.
# Indications for Use:
Rapid OH is a radiological computer aided triage and notification software indicated for suspicion of Obstructive Hydrocephalus (OH) in non-enhanced CT head images of adult patients. The device is intended to assist trained clinicians in workflow prioritization triage by providing notification of suspected findings in head CT images.
{5}
iSchemaView - Traditional 510(k) Rapid OH
# 510(k) Summary
Rapid OH uses an artificial intelligence algorithm to analyze images and highlight cases with suspected OH on a server or standalone desktop application in parallel to the ongoing standard of care image interpretation. The user is presented with notifications for cases with suspected OH findings. Notifications include compressed preview images, that are meant for informational purposes only and not intended for diagnostic use beyond notification. The device does not alter the original medical image and is not intended to be used as a diagnostic device.
The results of Rapid OH are intended to be used in conjunction with other patient information and based on professional judgment, to assist with triage/prioritization of medical images. Notified clinicians are responsible for viewing full images per the standard of care.
# Contraindications/Limitations/Exclusions:
Rapid OH is intended for use for adult patients.
- Input data image series containing excessive patient motion or metal implants may impact module analysis accuracy, robustness and quality.
- Ventriculoperitoneal shunts are contraindicated
# Exclusions:
- Series with missing slices or improperly ordered slices
data acquired at x-ray tube voltage $< 100\mathrm{kVp}$ or $>140\mathrm{kVp}$ .
data not representing human head or head/neck anatomical regions
# Technological Characteristics and Substantial Equivalence:
Rapid OH is a radiological computer-assisted triage and notification software device. The Rapid OH module is a Non-Contrast Computed Tomography (NCCT) processing module which operates within the integrated Rapid Platform to provide triage and notification prioritization of suspected obstructive hydrocephalus (OH). The Rapid OH module is an AI/ML module. The output of the module is a priority notification to clinicians indicating the suspicion of OH based on positive findings. The Rapid OH module uses the basic services supplied by the Rapid Platform including DICOM processing, job management, imaging module execution and imaging output including the notification and compressed image. The following table summarizes and compares data on the predicate device (K232436) to the Rapid OH software device that is the subject of this Traditional 510(k) submission.
| Parameter | Rapid SDH (K232436) Predicate Device | Rapid OH – Subject Device |
| --- | --- | --- |
| Product Code | QAS | QAS |
| Regulation | 21 CFR §892.2080 | 21 CFR §892.2080 |
| Intended Use/ Indications for Use | Rapid SDH is a radiological computer aided triage and notification software indicated for use in the triage and notification of hemispheric SDH in non-enhanced head images. The device is intended to assist trained radiologists in | Rapid OH is a radiological computer aided triage and notification software indicated for suspicion of Obstructive Hydrocephalus (OH) in non-enhanced CT head images of adult patients. The device is intended to assist trained clinicians in workflow prioritization |
| | the triage and notification of hemispheric SDH in non-enhanced CT head images of adult patients. The device is intended to assist trained radiologists in | |
| Study Design | Randomized Controlled Trial (RCT) (K232436) | Randomized Controlled Trial (RCT) (K232436) |
{6}
iSchemaView - Traditional 510(k) Rapid OH
510(k) Summary
| | workflow triage by providing notification of suspected findings of hemispheric Subdural Hemorrhage (SDH) in head CT images. Rapid SDH uses an artificial intelligence algorithm to analyze images and highlight cases with suspected hemispheric SDH on a server or standalone desktop application in parallel to the ongoing standard of care image interpretation. The user is presented with notifications for cases with suspected hemispheric SDH findings. Notifications include compressed preview images, that are meant for informational purposes only and not intended for diagnostic use beyond notification. The device does not alter the original medical image and is not intended to be used as a diagnostic device. The results of Rapid SDH are intended to be used in conjunction with other patient information and based on professional judgment, to assist with triage/prioritization of medical images. Notified clinicians are responsible for viewing full images per the standard of care. | triage by providing notification of suspected findings in head CT images. Rapid OH uses an artificial intelligence algorithm to analyze images and highlight cases with suspected OH on a server or standalone desktop application in parallel to the ongoing standard of care image interpretation. The user is presented with notifications for cases with suspected OH findings. Notifications include compressed preview images, that are meant for informational purposes only and not intended for diagnostic use beyond notification. The device does not alter the original medical image and is not intended to be used as a diagnostic device. The results of Rapid OH are intended to be used in conjunction with other patient information and based on professional judgment, to assist with triage/prioritization of medical images. Notified clinicians are responsible for viewing full images per the standard of care. Contraindications/Limitations/Exclusions: · Rapid OH is intended for use for adult patients. · Input data image series containing excessive patient motion or metal implants may impact module analysis accuracy, robustness and quality. · Ventriculoperitoneal shunts are contraindicated Exclusions: · Series with missing slices or improperly ordered slices · data acquired at x-ray tube voltage < 100kVp or > 140kVp. |
| --- | --- | --- |
{7}
iSchemaView - Traditional 510(k) Rapid OH
510(k) Summary
| | | data not representing human head or head/neck anatomical regions |
| --- | --- | --- |
| Input Data Requirements | Non-Contrast CT images | Non-Contrast CT images |
| DICOM Compliance | Yes | Yes |
| Anatomical Focus | Head | Head |
| SW | AI ML | AI ML |
| Removal of Cases from worklist queue | No | No |
| Outputs | Notifications, Reports, DICOM Secondary Capture Series | Notifications, Reports, DICOM Secondary Capture Series |
| Notification/ Prioritization | PACS, Workstation, email, mobile | PACS, Workstation, email, mobile |
# AI/ML Module Development:
Algorithm development was performed using 3340 cases from 74 sites, multiple manufactures (Siemens, GE, Toshiba, Philips) and split demographic (M/F, Age) characteristics which have disease variability to support generalization across hospital use cases. The training data and validation data sets are independently managed per internal data management procedures.
# Clinical Characteristics:
The primary users of Rapid OH software are medical professionals who use analysis of brain tissue and artifacts to assess patient conditions on presentation to the hospital for neuro disease symptoms related to obstructive hydrocephalus. Rapid OH is used in workflow prioritization, not to make primary diagnostic or treatment decisions. Rapid OH is for analysis of adult patients.
# Performance Standards:
Rapid OH has been developed in conformance with the following standards, as applicable:
EN ISO 14971:2019 (R2021) Application of Risk Management to Medical Devices
IEC 62304:2006 (R2015) Medical device software - Software lifecycle processes
IEC 62366:2015 (R2020) Application of Usability Engineering to Medical Devices
NEMA PS 3.1 - 3.20 Digital Imaging and Communications in Medicine (DICOM)
# Performance Data:
Rapid OH complies with DICOM (Digital Imaging and Communications in Medicine) - Developed by the American College of Radiology and the National Electrical Manufacturers Association. NEMA PS 3.1 - 3.20; and was tested in accordance with the 820.20 Verification and Validation requirements and successfully passed.
iSchemaView conducted extensive performance validation testing and software verification and validation testing of the Rapid OH device. Final device validation included standalone
{8}
iSchemaView - Traditional 510(k) Rapid OH
510(k) Summary
performance validation. This performance validation testing demonstrated the Rapid OH device provides accurate representation of key processing parameters under a range of clinically relevant conditions associated with the intended use of the software. Software performance, validation and verification testing demonstrated that the Rapid OH device met all design requirements and specifications.
Standalone performance primary endpoint passed with sensitivity (Se) of 89.5% (95% CI:0.837-0.935) and specificity (Sp) of 97.6% (95% CI:0.940-0.991); the secondary endpoint demonstrated time to notification time of 30.3 seconds (range 10.5-55.5 seconds).
The performance validation was performed using 320 cases with diversity amongst demographics (M: 45%, F: 54%); Sites (and manufacturers (GE, Philips, Siemens, Toshiba) and confounders (ICH, Ischemic Stroke, Tumor, Cyst, Aqueductal stenosis, Mass effect, Brain atrophy and Communicating hydrocephalus). Truthing was established using 2:3 experts.
**Prescriptive Statement:**
Caution: Federal law restricts this device to sale by or on the order of a physician.
**Safety & Effectiveness:**
Rapid OH has been designed, verified and validated in compliance with 21 CFR, Part 820.30 requirements and the risk is managed through design meeting the requirements associated with EN ISO 14971:2019 (risk management). Overall risk analysis and design implementation shows the Rapid OH as safe and effective as the predicate.
**Conclusion:**
In conclusion, the Rapid OH software device is substantially equivalent in intended use, technological characteristics, safety and performance characteristics to the legally marketed predicate device, Rapid SDH Software (K232436).
Page 5 of 4
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.
