AI/ML, Software as a Medical Device, Real-World Evidence
Real-World Evidence
Submission
Device
Sponsor
RWD Sources
RWE Use Summary
Key Tags
K182875 · Jul 10, 2019
DeepCT
Deep01 Limited
Retrospective radiology records (21,603 patients) from three hospital systems (Tri-Service General Hospital, Kaohsiung Veterans General Hospital, and National Taiwan University Hospital)
Retrospective clinical image data were used to train the deep learning algorithm (ResNet) for the DeepCT device.
Retrospective data; Algorithm training; Radiology records
Clinical Evidence
Study Design
Population
Comparator
Key Endpoints
DeepCT Model Training Dataset; Retrospective cohort; Follow-up/Duration: 2007-2017; Study Period: 2007-2017
Patients undergoing head CT scans; Sample Size: 21,603 patients; Number of Sites: 3
21,603 patients who underwent head CT scans between 2007 and 2017.
—
Retrospective, multicenter, multinational study of 260 cases from 5 clinical sites (2 US and 3 OUS).
—
Indications for Use
DeepCT is a notification-only, parallel workflow tool for use by hospital networks and trained clinicians to identify and communicate images of specific patients to a specialist, independent of standard of care workflow. DeepCT uses an artificial intelligence algorithm to analyze images for findings suggestive of a pre-specified clinical condition and to notify an appropriate medical specialist of these findings in parallel to standard of care image interpretation. Identification of suspected findings is not for diagnostic use beyond notification. Specifically, the device analyzes non-contrast CT images of the brain acquired in the acute setting and sends notifications to a specialist that a suspected ICH (intracranial hemorrhage) has been identified and recommends review of those images. Notified clinicians are responsible for viewing non-contrast CT images of the brain on a diagnostic viewer and engaging in appropriate patient evaluation and relevant discussion with a treating specialist before making care-related decisions or requests. DeepCT is limited to analysis of imaging data and should not be used in-lieu of full patient evaluation or relied upon to make or confirm diagnosis.
Device Story
DeepCT is a software-only radiological triage and notification tool used in hospital emergency rooms. It processes non-contrast head CT DICOM images to identify findings suggestive of intracranial hemorrhage (ICH). The system consists of Image Forwarding Software (transmits DICOMs via secure channel) and an Image Processing and Analysis Server (runs AI algorithm). If ICH is suspected, the system sends a notification to a specialist. The workflow operates in parallel to standard clinical care; it does not replace standard image interpretation. Clinicians receive notifications and must view original images on a diagnostic viewer to perform independent evaluations. The device aims to improve triage efficiency by alerting specialists to potential ICH cases, potentially accelerating time-to-treatment for acute patients.
Clinical Evidence
Retrospective, multicenter, multinational study (260 cases; 5 sites: 2 US, 3 OUS). Primary endpoint: identify ICH in non-contrast head CT. Results: Sensitivity 93.8% (95% CI: 88.3%-96.8%), Specificity 92.3% (95% CI: 86.4%-95.7%). Secondary endpoint: processing time (30.6s, 95% CI: 25.8-35.4s).
Technological Characteristics
Software-only device. Deep residual convolutional neural network (ResNet-34 architecture). Connectivity: DICOM transmission via secure channel. Deployment: Image Forwarding Software (client) and Image Processing and Analysis Server. Development environment: PyTorch.
Indications for Use
Indicated for hospital networks and trained clinicians to identify and communicate non-contrast head CT images suggestive of intracranial hemorrhage (ICH) in acute settings. Not for diagnostic use; intended for triage/notification only. Requires clinician review of images on diagnostic viewer before clinical decision-making.
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}------------------------------------------------
Image /page/0/Picture/0 description: The image contains the logo of the U.S. Food and Drug Administration (FDA). On the left is the Department of Health & Human Services logo. To the right of that is the FDA logo, which is a blue square with the letters "FDA" in white. To the right of the blue square is the text "U.S. FOOD & DRUG ADMINISTRATION" in blue.
July 10, 2019
Deep01 Limited % Mr. William Lai Medical Regulatory Affairs Specialist Rm. 5, 11F., No.162, Sec. 4, Roosevelt Rd. Taipei City, Taiwan 10091 TAIWAN
Re: K182875
Trade/Device Name: DeepCT Regulation Number: 21 CFR 892.2080 Regulation Name: Radiological computer aided triage and notification software Regulatory Class: Class II Product Code: QAS Dated: June 7, 2019 Received: June 7, 2019
Dear Mr. Lai:
We have reviewed your Section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database located at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting of medical device-related adverse events) (21 CFR 803) for
{1}------------------------------------------------
devices or postmarketing safety reporting (21 CFR 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reportingcombination-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 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR Part 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-device-safety/medical-device-reportingmdr-how-report-medical-device-problems.
For comprehensive regulatory information about mediation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medicaldevices/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-device-advice-comprehensive-regulatoryassistance/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.
For
Thalia T. Mills, Ph.D. Director Division of Radiological Health OHT7: Office of In Vitro Diagnostics and Radiological Health Office of Product Evaluation and Quality Center for Devices and Radiological Health
Enclosure
{2}------------------------------------------------
## Indications for Use
510(k) Number (if known) K182875
Device Name DeepCT
#### Indications for Use (Describe)
DeepCT is a notification-only, parallel workflow tool for use by hospital networks and trained clinicians to identify and communicate images of specific patients to a specialist, independent of standard of care workflow. DeepCT uses an artificial intelligence algorithm to analyze images for findings suggestive of a pre-specified clinical condition and to notify an appropriate medical specialist of these findings in parallel to standard of care image interpretation. Identification of suspected findings is not for diagnostic use beyond notification. Specifically, the device analyzes non-contrast CT images of the brain acquired in the acute setting and sends notifications to a specialist that a suspected ICH (intracranial hemorrhage) has been identified and recommends review of those images. Notified clinicians are responsible for viewing non-contrast CT images of the brain on a diagnostic viewer and engaging in appropriate patient evaluation and relevant discussion with a treating specialist before making care-related decisions or requests. DeepCT is limited to analysis of imaging data and should not be used in-lieu of full patient evaluation or relied upon to make or confirm diagnosis.
| Type of Use (Select one or both, as applicable) | |
|-------------------------------------------------|--|
|-------------------------------------------------|--|
X 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."
{3}------------------------------------------------
# DeepCT (Ver. 4.1.4) 510(k) Summary K182875
{4}------------------------------------------------
## I. SUBMITTER
Deep01 Limited
Rm. 5, 11F., No.162, Sec. 4, Roosevelt Rd., Taipei City 10091, Taiwan (R.O.C.)
Tel: +886-2-2365-9959
Contact Person: William Lai
Date Prepared: Sep 26, 2018
## II. DEVICE
Name of Device: DeepCT
Common or Usual Name: Radiological Computer-Assisted Triage And Notification Software
Classification Name: Radiological Computer-Assisted Triage And Notification Software (21 CFR 892.2080)
Regulatory Class: II
Product Code: QAS
## III. PREDICATE DEVICE
DEN170073, ContaCT
K180647, BriefCase
#### IV. DEVICE DESCRIPTION
This software is used to analyze the head computed tomography image of a patient suspected of having intracranial hemorrhage and/or hematoma (hereinafter referred to as "ICH"). Provide a "present" situation (with ICH) notification, send a text message to the user.
For example, after the finished CT scan of the patient, it will produce relevant CT information (including brain DICOM file). Relevant hospital personnel can use this software to perform AI analysis and interpretation of the DICOM file. During and after the software analysis, relevant hospital personnel can continue the general analysis procedure. If the result of the analysis is "present" (with ICH), relevant hospital personnel will receive a notification message. The use process is parallel to the
{5}------------------------------------------------
general medical treatment process and does not involve or affect patient care procedures.
When the software is not used, medical personnel perform a general image interpretation process. When using this software, medical personnel can refer to the interpretation results of this software and perform a general image interpretation process.
DeepCT (Ver. 4.1.4) is a software-only device that uses two components: (1) Image Forwarding Software and (2) Image Processing and Analysis Server.
(1) The Image Forwarding Software is configured by the hospital to be used on a computer and is responsible for transmitting a copy of DICOM files from the local through a secured channel to the Image Processing and Analysis Server.
When the Image Forwarding Software receives the interpretation result from the Image Processing and Analysis Server, it shows the result on the screen. If there is a suggestive of ICH, the Image Forwarding Software sends a notification to the specialist identifying the study of interest. While the software informs the notification process, no other diagnostic information is generated from the software or available to the user beyond the notification.
(2) The Image Processing and Analysis Server is responsible for receiving, assembling, processing, analyzing and storing DICOM images. This component includes the algorithm that is responsible for identifying and quantifying image characteristics that are consistent with a ICH and transmit the result back to the Image Forwarding Software.
Environment of Use: Hospital emergency room
The head CT scan is imaged as a series of DICOM data used as inputs for model training, performance validation and product qualification. The Tri-Service General Hospital Institutional Review Board, Kaohsiung Veterans General Hospital Institutional Review Board and National Taiwan University Hospital Research Ethics Committee all approved and consented the use of the retrospective image data for DeepCT development and deployment without relevant ethical concern. Radiology records were collected from 21,603 patients who underwent head CT scans between 2007 and 2017.
A deep residual convolutional neural network (aka Residual Network or ResNet for short, see Kaiming He et al. https://arxiv.org/abs/1512.03385)
{6}------------------------------------------------
was adopted as the core learning model. By repeatedly applying residual connection, the ResNet model can ease the training of networks that are substantially deeper, effectively help the convergence of the model and gain the accuracy with deep neural networks. The model was trained with a categorical cross-entropy loss with Adam optimizer. Data augmentation was introduced to motivate the model to learn the rotated and translated images. Our DeepCT system was trained with PyTorch, an open source deep learning software library (https://pytorch.org).
Same model with three different layer size, 18, 34, 52, respectively, were trained to cross evaluate the model performance. 34-layer Residual Network was chose as the final model since it got the best tradeoff between performance and computation complexity. We saw little performance gain by extending from 34 to 52 layers.
## V. INDICATIONS FOR USE
DeepCT (Ver. 4.1.4) is notification-only, parallel workflow tool for use by hospital networks and trained clinicians to identify and communicate images of specific patients to a specialist, independent of standard of care workflow.
DeepCT (Ver. 4.1.4) uses an artificial intelligence algorithm to analyze images for findings suggestive of a pre-specified clinical condition and to notify an appropriate medical specialist of these findings in parallel to standard of care image interpretation. Identification of suspected findings is not for diagnostic use beyond notification. Specifically, the device analyzes non-contrast CT images of the brain acquired in the acute setting and sends notifications to a specialist that a suspected ICH has been identified and recommends review of those images.
Notified clinicians are responsible for viewing non-contrast CT images of the brain on a diagnostic viewer and engaging in appropriate patient evaluation and relevant discussion with a treating specialist before making care-related decisions or requests. DeepCT (Ver. 4.1.4) is limited to analysis of imaging data and should not be used in-lieu of full patient evaluation or relied upon to make or confirm diagnosis.
The Indications for Use statement for this device is not identical to the predicate device; however, the differences do not alter the intended therapeutic use of the device nor do they affect the safety and effectiveness of the device relative to the predicate. The user will receive the message of the result of interpretation, and he/she must use computer (not mobile device) to check complete image to make independent diagnosis. By providing different training to the artificial intelligence, it will
{7}------------------------------------------------
perform different interpretation to different evaluation target in different image format.
VI. COMPARISON OF TECHNOLOGICAL CHARACTERISTICS WITH THE PREDICATE DEVICE
Similarities:
Both ContaCT and DeepCT (Ver. 4.1.4):
Are to identify and communicate CT images of specific patients to a specialist, independent of standard of care workflow.
Use artificial intelligence algorithm to analyze images for findings suggestive of a pre-specified clinical condition and to notify an appropriate medical specialist of these findings in parallel to standard of care image interpretation and recommends review of those images.
Process images intended to aid in prioritization and triage of radiological medical images.
Are not for diagnostic use beyond notification.
Send notifications to a specialist. Those notifications work in parallel to the standard of care. They prompt the specialist to start preemptive triage of a notified case, upon which he may decide after observing the preview on his desktop, to turn to the local PACS to perform the evaluation. If a notification is rejected, the case still remains in the queue to be handled per the standard of care.
Are limited to analysis of imaging data and should not be used in-lieu of full patient evaluation or relied upon to make or confirm diagnosis; and,
Notified clinicians are responsible for viewing CT images of the brain on a diagnostic viewer and engaging in appropriate patient evaluation and relevant discussion with a treating specialist before making care-related decisions or requests.
## Differences:
ContaCT preview images through a mobile application while DeepCT (Ver. 4.1.4) does not.
{8}------------------------------------------------
This difference does not affect safety and effectiveness, since no matter which software the user use, the user will receive the message of the result of interpretation, and he/she must use computer (not mobile device) to check complete image to make independent diagnosis.
DeepCT (Ver. 4.1.4) interprets non-contrast CT images for suspected ICH, while ContaCT interprets CT angiogram images for suspected large vessel occlusion.
This is simply the difference in evaluation target and image format. Both of them are to interpret by artificial intelligence. By providing different training to the artificial intelligence, it will perform different interpretation to different evaluation target in different image format. This difference does not affect safety and effectiveness. The performance evaluation results show that the performance of the two is equivalent.
## VII. PERFORMANCE DATA
The following performance data were provided in support of the substantial equivalence determination.
## Performance Testing
Deep01 conducted a retrospective, multicenter, multinational study with the DeepCT software with the primary endpoint to evaluate the software's performance in identifying non-contrast CT head images containing ICH findings in 260 cases from 5 clinical sites (2 US and 3 OUS). There are 130 cases in US study and 130 cases in OUS study. There was approximately an equal number of positive and negative cases (images with ICH versus without ICH) included in the analysis.
Sensitivity and specificity exceeded the 80% performance goal. Specifically, sensitivity was observed to be 93.8% (95% CI: 88.3%-96.8%) and specificity was observed to be 92.3% (95% Cl: 86.4%-95.7%).
In addition, a secondary endpoint measure was DeepCT's processing time.
The DeepCT processing time includes the time from browsing and selecting dicom files to the notification of the interpretation result. DeepCT processing time has been documented for all 122 cases.
{9}------------------------------------------------
The processing time is 30.6 seconds (95% Cl: 25.8-35.4 seconds), which is lower than the processing time reported by the Aidoc BriefCase device.
In summary, performance validation data establish the achievement of effective triage by the DeepCT image analysis algorithm as well as effective notification functionality of the DeepCT application.
## Software Verification and Validation Testing
Software verification and validation testing were conducted and documentation was provided as recommended by FDA's Guidance for Industry and FDA Staff, "Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices."
## VIII. CONCLUSIONS
The performance data support the safety of the device and the software verification and validation demonstrate that the DeepCT (Ver. 4.1.4) device should perform as intended in the specified use conditions.
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.