AI/ML, Software as a Medical Device, Real-World Evidence
Real-World Evidence
Submission
Device
Sponsor
RWD Sources
RWE Use Summary
Key Tags
K202928 · Apr 2, 2021
DV. Target
Deepvoxel, Inc.
In-house clinical dataset (retrospective collection from City of Hope); Public medical image archive (TCIA)
Retrospective clinical data was used to evaluate the auto-contouring accuracy of the device by comparing device-generated contours against actual clinical contouring results (ground truth).
Comparison Study 2; Retrospective performance evaluation; Follow-up/Duration: Not applicable; Study Period: Retrospective
Patients undergoing radiation therapy (CT images); Number of Sites: 1 (City of Hope)
Predicate device (Workflow Box)
Auto-contouring accuracy (DICE score)
AI Performance
Output
Algorithm
Acceptance
Observed
Dev DS
Dev Readers
Test DS
Test Readers
Organ-at-risk (OAR) contouring
—
—
—
—
—
Comparison Study 1: Public validation dataset (64% US). Comparison Study 2: In-house clinical dataset (City of Hope). Comparison Study 3: Public validation dataset (64% US).
3 (board-certified physicians)
Indications for Use
DV.Target is a software application that enables the routing of DICOM-compliant data (CT Images) to automatic image processing workflows, using machine learning-based algorithms to automatically delineate organs-at-risk (OARs). Contours generated by DV.Target may be used as an input to clinical workflows for treatment planning in radiation therapy. DV.Target is intended to be used by trained medical professionals including radiologists, radiation oncologists, dosimetrists, and physicists. DV.Target does not provide a user interface for data visualization. Image data uploaded, auto-contouring results, and other functionalities are managed via an administration interface. Thus, it is required that DV.Target be used in conjunction with appropriate software, such as a treatment planning system (TPS), to review, edit, and approve for all contours generated by DV.Target. DV.Target is only intended for normal organ contouring, not for tumor or clinical target volume contouring.
Device Story
DV.Target is a standalone software application for radiation therapy workflows. It receives DICOM-compliant CT images as input and uses machine learning-based algorithms to automatically delineate 49 organs-at-risk (OARs) across the head & neck, thorax, and abdomen & pelvis. The device operates on a specialized server within a local hospital network. It lacks a visualization interface; users manage data routing, auto-contouring, and output (RTSTRUCT files) via an administration interface. The device requires integration with third-party software, such as a treatment planning system (TPS), where clinicians review, edit, and approve the generated contours. By automating the time-consuming manual contouring process, the device facilitates efficient radiation therapy treatment planning.
Clinical Evidence
No clinical data. Bench testing included three comparison studies using public (TCIA) and in-house clinical datasets. Performance evaluated via Dice-Sørensen coefficients (DICE) comparing device-generated contours against ground truth (consensus of three board-certified physicians). Studies demonstrated non-inferiority of DV.Target to predicate (K181572) for 19 overlapping OARs and to reference device (K182624) for 30 non-overlapping OARs. Statistical analysis included histograms, Box and Whisker plots, Bland-Altman plots, and non-inferiority tests.
Technological Characteristics
Standalone software application; runs on Ubuntu or Windows server. Inputs: DICOM CT images. Outputs: RTSTRUCT files. Connectivity: TCP/IP, SCP. Algorithm: Machine learning-based auto-contouring. No energy delivery. No visualization interface. Requires DICOM 3.0 compliance for scanner and TPS integration.
Indications for Use
Indicated for trained medical professionals (radiologists, radiation oncologists, dosimetrists, physicists) to automatically delineate normal organs-at-risk (OARs) on CT images for radiation therapy treatment planning. Not for tumor or clinical target volume contouring.
Regulatory Classification
Identification
A medical image management and processing system is a device that provides one or more capabilities relating to the review and digital processing of medical images for the purposes of interpretation by a trained practitioner of disease detection, diagnosis, or patient management. The software components may provide advanced or complex image processing functions for image manipulation, enhancement, or quantification that are intended for use in the interpretation and analysis of medical images. Advanced image manipulation functions may include image segmentation, multimodality image registration, or 3D visualization. Complex quantitative functions may include semi-automated measurements or time-series measurements.
Special Controls
*Classification.* Class II (special controls; voluntary standards—Digital Imaging and Communications in Medicine (DICOM) Std., Joint Photographic Experts Group (JPEG) Std., Society of Motion Picture and Television Engineers (SMPTE) Test Pattern).
{0}------------------------------------------------
April 2, 2021
Image /page/0/Picture/1 description: The image shows the logo of the U.S. Food and Drug Administration (FDA). The logo consists of two parts: a symbol on the left and the FDA acronym with the agency's name on the right. The symbol on the left is a stylized representation of the Department of Health and Human Services emblem. To the right of the symbol is a blue square containing the acronym "FDA" in white, followed by the words "U.S. FOOD & DRUG ADMINISTRATION" in blue.
Deepvoxel, Inc. % Albert Rego, Ph.D. Consultant Albert Rego, Ph.D., Inc. 27001 La Paz Road, Suite #314 MISSION VIEJO CA 92691
Re: K202928
Trade/Device Name: DV.Target Regulation Number: 21 CFR 892.2050 Regulation Name: Picture archiving and communications system Regulatory Class: Class II Product Code: QKB Dated: February 19, 2021 Received: March 2, 2021
Dear Dr. Rego:
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) K202928
Device Name DV.Target
#### Indications for Use (Describe)
DV.Target is a software application that enables the routing of DICOM-compliant data (CT Images) to automatic image processing workflows, using machine learning-based algorithms to automatically delineate organs-at-risk (OARs). Contours generated by DV.Target may be used as an input to clinical workflows for treatment planning in radiation therapy.
DV.Target is intended to be used by trained medical professionals including radiologists, radiation oncologists, dosimetrists, and physicists.
DV.Target does not provide a user interface for data visualization. Image data uploaded, auto-contouring results, and other functionalities are managed via an administration interface. Thus, it is required that DV.Target be used in conjunction with appropriate software, such as a treatment planning system (TPS), to review, edit, and approve for all contours generated by DV.Target.
DV.Target is only intended for normal organ contouring, not for tumor or clinical target volume contouring.
| Type of Use (Select one or both, as applicable) | |
|------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------|
| <span> Prescription Use (Part 21 CFR 801 Subpart D) </span> | <span> Over-The-Counter Use (21 CFR 801 Subpart C) </span> |
#### 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}------------------------------------------------
Image /page/3/Picture/0 description: The image contains the logo for Deep Voxel. The logo consists of a blue square with a smaller, light blue cube extending from one of its corners. To the right of the logo, the words "DEEP VOXEL" are written in a blue, sans-serif font.
# 510(k) Summary of Safety and Effectiveness
The assigned 510(k) Number: K202928
# 1. Submitter
| Applicant Information: | DeepVoxel Inc.<br>22 Talisman<br>Irvine, CA 92620 |
|------------------------|-----------------------------------------------------------------------------------|
| Phone:<br>Email: | 858-281-8029<br>support@deep-voxel.com |
| Contact Person: | Dr. Albert Rego<br>27001 La Paz Road, Suite #314<br>Mission Viejo, CA, 92691, USA |
| Date Prepared: | April 1, 2021 |
# 2. Device Name
| Trade Name: | DV.Target |
|----------------------|--------------------------------------------------------------|
| Device Common Name: | Radiological Image Processing Software For Radiation Therapy |
| Regulation Number: | 21 CFR 892.2050 |
| Product Code: | QKB |
| Classification Name: | Picture archiving and communications system |
| Regulation Class: | Class II |
{4}------------------------------------------------
Image /page/4/Picture/0 description: The image contains the logo for Deep Voxel. The logo consists of a blue square with a smaller, light blue square attached to one of its corners, creating a 3D effect. To the right of the square is the text "DEEP VOXEL" in a sans-serif font, with both words in the same blue color as the square.
# 3. Identification of Predicate Device
#### Predicate Device
#### Table 1. Identification of Predicate Device.
| Device trade<br>name | 510(k)<br>number | Date of<br>clearance | Classification<br>name | Product<br>code | Regulation | Class | Classification<br>panel | Submitter's<br>name |
|------------------------------------------------------------------------------------------------|------------------|----------------------|-------------------------------------------------------|-----------------|-------------------|----------|-------------------------|-----------------------|
| Workflow<br>BoxTM<br>(including<br>DLCExpert™,<br>Embrace:CT™,<br>Embrace:MR™,<br>Re:Contour™) | K181572 | July 10,<br>2018 | Picture<br>Archiving and<br>Communicatio<br>ns System | LLZ | 21CFR<br>892.2050 | Class II | Radiology | Mirada<br>Medical Ltd |
#### Reference Device
MIM - MRT Dosimetry, K182624
### 4. Indications for use
DV.Target is a software application that enables the routing of DICOM-compliant data (CT Images) to automatic image processing workflows, using machine learning-based algorithms to automatically delineate organs-at-risk (OARs). Contours generated by DV.Target may be used as an input to clinical workflows for treatment planning in radiation therapy.
DV.Target is intended to be used by trained medical professionals including radiologists, radiation oncologists, dosimetrists, and physicists.
DV.Target does not provide a user interface for data visualization. Image data uploaded, autocontouring results, and other functionalities are managed via an administration interface. Thus, it is required that DV.Target be used in conjunction with appropriate software, such as a treatment planning system (TPS), to review, edit, and approve for all contours generated by DV.Target.
DV.Target is only intended for normal organ contouring, not for tumor or clinical target volume contouring.
# 5. Device Description
The proposed device, DV.Target, is a standalone software that is designed to be used by trained medical professionals to automatically delineate organs-at-risk (OARs) on CT images. This OARs delineation function, often referred as auto-contouring, is intended to facilitate radiation therapy workflows. Supported image modalities include CT and RTSTURCT.
{5}------------------------------------------------
Image /page/5/Picture/0 description: The image contains the logo for Deep Voxel. The logo consists of a blue square with a smaller, light blue square attached to the bottom right corner. To the right of the logo, the words "DEEP VOXEL" are written in a blue, sans-serif font.
DV.Target can automatically delineate major OARs in three anatomical sites --- Head & Neck, Thorax, and Abdomen & Pelvis. It receives CT images in DICOM format as input and automatically generates the contours of OARs, which are stored in DICOM format and in RTSTRUCT modality.
The deployment environment of the proposed device is recommended to be a local network with an existing hospital-grade IT system in place. DV.Target should be installed on a specialized server supporting deep learning processing. After installation, users can login to the DV.Target administration interface via browsers from their local computers. All activities, including autocontouring, are operated by users through the administration interface.
In addition to auto-contouring, DV.Target also has the following auxiliary functions:
- User interface for receiving, updating and transmitting medical images in DICOM format;
- User management;
- Processed image management and output (RTSTRUCT) file management.
Once data is routed to DV.Target auto-contouring workflows, no user interaction is required, nor provided. The image data, auto-contouring results, and other functionalities can be managed by DV.Target users via an administration user interface. Third-party image visualization and editing software, such as a treatment planning system (TPS), must be used to facilitate the review and editing of contours generated by DV.Target.
DV.Target can delineate the following 49 OARs distributed across three anatomic sites (Table 2):
| Anatomic Site | OARs | No. of OARs |
|---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------|
| Head & Neck | Brachial plexus, Brain Stem, Constrictor naris, Ear Left, Ear Right, Eye Left,<br>Eye Right, Hypophysis, Larynx, Lens Left, Lens Right, Mandible, Optic<br>chiasm, Optic nerve Left, Optic nerve Right, Oral cavity, Parotid Left,<br>Parotid Right, Sublingual gland, Submandibular gland Left,<br>Submandibular gland Right, Spinal Cord, Temporal Lobe Left, Temporal<br>Lobe Right, Temporomandibular joint Left, Temporomandibular joint<br>Right, Thyroid, Trachea | 28 |
| Thorax | Esophagus, Heart, Lung Left, Lung Right, Spinal Cord, Trachea | 6 |
| Abdomen &<br>Pelvis | Bladder, Duodenum, Gallbladder, Femur Left, Femur Right, Kidney Left,<br>Kidney Right, Large Bowel, Liver, Pancreas, Rectum, Small Bowel, Spleen,<br>Spinal Cord, Stomach | 15 |
{6}------------------------------------------------
Image /page/6/Picture/0 description: The image shows the logo for Deep Voxel. The logo consists of a blue square with a smaller, light blue cube attached to one of its corners. To the right of the logo is the text "DEEP VOXEL" in a sans-serif font, also in blue.
### 6. Comparison of Indications for Use with Predicate Device
Both the proposed and predicate devices are software applications designed to be used by trained medical professionals within a hospital environment, and are indicated for the creation of contours for use in clinical workflows for the purpose of radiation therapy treatment planning.
Both the predicate and proposed devices support contouring based on machine learning techniques, whereas the predicate device additionally supports atlas-based contouring and registration-based re-contouring.
Both the proposed and predicate devices are designed to interoperate via DICOM objects and to network with other DICOM capable devices such as PACS and Radiation Treatment Planning Systems.
Both the proposed and predicate devices do not facilitate the display or visualization of the data by users. Reviewing and editing of contouring results cannot be performed within both devices.
Both the proposed and predicate devices require users to confirm and review generated contours in a separate image visualization system.
In summary, DeepVoxel Inc. believes the intended use of the proposed device is substantially equivalent to the predicate device, excepting the registration-based features in the predicate device, which are not applicable to the proposed device.
| Table 3. Comparison of Indications for Use with Predicate Device. | | |
|-------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| | Proposed Device | Predicate Device |
| Indications<br>for use | DV.Target is a software application that enables the routing of image data (CT Images) to automatic image processing workflows, using machine learning learning-based algorithms to automatically delineate OARs (Organs-at-risk). Contours generated by DV.Target may be used as an input to clinical workflows for treatment planning in radiation therapy. DV.Target is intended to be used by trained medical professionals including radiologists, radiation oncologists, dosimetrists, and physicists. | Workflow Box is a software system designed to allow users to route DICOM-compliant data to and from automated processing components. Supported modalities include CT, MR, RTSTRUCT. Workflow Box includes processing components for automatically contouring imaging data using deformable image registration to support atlas-based contouring, re-contouring of the same patient and machine learning based contouring. Workflow Box is a data routing and image processing tool which automatically applies contours to data which is sent to one or more of the included image processing workflows. |
### 3. Comparison of Indications for Use with Predicate Device
{7}------------------------------------------------
Image /page/7/Picture/0 description: The image contains the logo for Deep Voxel. The logo consists of a blue square with a white square cut out of the center. To the right of the square is the text "DEEP VOXEL" in a sans-serif font.
| • DV.Target does not provide a user interface for data visualization. The<br>image data uploaded, auto-contouring results and other<br>functionalities are managed via an administration interface. Thus, it is<br>required that DV.Target be used in conjunction with appropriate<br>software, such as a treatment planning system (TPS), to review, edit<br>and approve for all contours generated by DV.Target. | Contours generated by Workflow Box may be used as an input to clinical<br>workflows including, but not limited to, radiation therapy treatment planning.<br>• Workflow Box must be used in conjunction with appropriate software<br>to review and edit results generated automatically by Workflow<br>Box components, for example image visualization software must be used to<br>facilitate the review and edit of contours generated by Workflow Box component<br>applications. |
|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| • DV.Target is only intended for normal organ contouring, not for tumor or<br>clinical target volume contouring. | • Workflow Box is intended to be used by trained medical professionals.<br>• Workflow Box is not intended to automatically detect lesions. |
# 7. Comparison of Technological Characteristics with Predicate Device
#### Table 4. Comparison of Technological Characteristics with Predicate Device.
| Characteristic | Proposed Device | Predicate Device |
|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------|
| Device Name | DV.Target | Workflow Box (K181572) |
| Regulation No. | No. 21CFR 892.2050 | No. 21CFR 892.2050 |
| Classification Name | Picture archiving and<br>communications system | Picture archiving and<br>communications system |
| Product Code | QKB | LLZ |
| Class | II | II |
| Target Population | Any patient type for whom<br>relevant modality scan data is<br>available. | Any patient type for whom<br>relevant modality scan data is<br>available. |
| Where Used | Clinical/Hospital environment | Clinical/Hospital environment |
| Target Users | Designed to be used by trained<br>clinicians | Designed to be used by trained<br>clinicians |
| Energy Used and/or<br>Delivered | None - software only<br>application. The software<br>application does not deliver or<br>depend on energy delivered to or<br>from patients | None - software only application.<br>The software application does not<br>deliver or depend on energy<br>delivered to or from patients |
{8}------------------------------------------------
Image /page/8/Picture/0 description: The image shows the logo for Deep Voxel. The logo consists of a blue square with a smaller, light blue cube extending from the bottom right corner. To the right of the logo are the words "DEEP VOXEL" in a blue sans-serif font. The logo is simple and modern, and the colors are calming and professional.
22 Talisman, Irvine, CA, 92620
858-281-8029
| Data Visualization | None - the proposed device has<br>no data visualization<br>functionality. All data processing<br>is automated and does not<br>require user interaction. A<br>control interface is provided for<br>system administration and<br>configuration only. | None - the predicate device has<br>no data visualization functionality.<br>All data processing is automated<br>and does not require user<br>interaction. A control interface is<br>provided for system<br>administration and configuration<br>only. |
|------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Regions and Volumes<br>of Interest (ROI) | Machine learning-based<br>contouring | Atlas-based contouring,<br>registration-based re-contouring,<br>machine learning-based<br>contouring |
| ROI measurements<br>and quantification | Not applicable | Not applicable |
| Image Registration | Not applicable | Registration for the purposes of<br>re-planning/re-contouring and<br>atlas based contouring. |
| Label/labeling | Conform with 21CFR Part 801 | Conform with 21CFR Part 801 |
| Operating System | Ubuntu, Windows | Windows |
| Algorithm | Machine learning-based | Machine learning-based and Atlas-<br>based |
| Supported Modalities | CT, RTSTRUCT | CT, MR, RTSTRUCT |
| Reporting and data<br>routing | Supports automatic routing<br>images to processing workflow.<br>No customized options for the<br>user | Supports routing and distribution<br>of images to other DICOM nodes<br>including to custom executables<br>determined by the user |
| Communications/<br>Networking | TCP/IP and SCP | TCP/IP and SCP |
| Compatible Scanner<br>Models | No Limitation on scanner model,<br>DICOM 3.0 compliance required | No Limitation on scanner model,<br>DICOM 3.0 compliance required |
| Compatible Treatment<br>Planning System | No Limitation on TPS model,<br>DICOM 3.0 compliance required | No Limitation on TPS model,<br>DICOM 3.0 compliance required |
The predicate device and the proposed device are both standalone software applications for medical image processing. Both devices process DICOM image data and include design features to enable automatic delineation of contours on input image data.
Both the proposed and predicate devices utilize algorithms to automatically generate regions of interest structures/contours. The predicate device also utilizes image registration for atlas-based contouring and re-contouring.
{9}------------------------------------------------
Image /page/9/Picture/0 description: The image contains the logo for Deep Voxel. The logo consists of a blue square with a white square cut out of the center. There is a small blue cube in the bottom right corner of the square. To the right of the square is the text "DEEP VOXEL" in blue.
Both devices are compatible with the same use environments and utilize the same networking technology. The predicate device operates on Microsoft Windows operating systems, while the proposed device can operate on both Microsoft Windows and Ubuntu (a Linux distribution) operating systems.
19 OARs (hereinafter referred to as "overlapping OARs") are delineated by both the proposed and predicate devices. However, there are additional 30 OARs only delineated by the proposed device, and 16 OARs only delineated by the predicate device.
The proposed device offers a subset of the image processing technical features presented by the predicate device. The shared features are substantially equivalent to the predicate device and do not present any additional or new risks when compared to the predicate device.
# 8. Non-Clinical Test Conclusion
In summary, we have conducted three Comparison Studies to evaluate the performance of the proposed device:
- Comparison Study 1: Conducted between the proposed and predicate devices on a public validation dataset (64% are from the US) to evaluate the auto-contouring accuracy of 19 overlapping OARs (OARs delineated by both devices).
- Comparison Study 2: Conducted between the proposed and predicate devices on an in-house clinical dataset to evaluate the auto-contouring accuracy of the overlapping OARs.
- Comparison Study 3: Conducted between the proposed device and a reference device (MIM -MRT Dosimetry 510(k) Number K182624) on the public validation data (64% are from the US) to evaluate the auto-contouring accuracy of 30 non-overlapping OARs (OARs delineated by the proposed device, but not by the predicate).
The validation data used in these studies consists of two independent dataset collected from a large medical images archive --- TCIA and b) a clinical in-house dataset collected retrospectively from the City of Hope (our primary validation site). A comprehensive characteristic analysis of validation data to demonstrate the representativeness of the intended patient population is presented and related backgrounds are introduced. The ground truth OARs contours on the public validation data were generated from the consensus of three board-certified physicians. The ground truth contours on the in-house clinical data (collected retrospectively) were based on actual clinical contouring results.
All validation data described above were invisible in model training. The Dice-Sørensen coefficients (DICE score) were calculated and used to evaluate contouring accuracies by comparing devicegenerated contours with ground truth contours. A systematic statistical methodology, including data presentation (histogram, Box and Whisker plot, and Bland-Altman plot) and statistical inferences
{10}------------------------------------------------
Image /page/10/Picture/0 description: The image contains the logo for Deep Voxel. The logo consists of a blue square with a white square cut out of the center. A light blue shape is in the bottom right corner of the square. To the right of the logo is the text "DEEP VOXEL" in a blue sans-serif font.
(i.e. the non-inferiority tests), is established as the guidelines for data analysis in the three Comparison Studies.
We have presented detailed results from the three Comparison Studies. In each of the studies, we observed the following results: a) The DICE scores from the proposed and the predicate/reference devices both have a central tendency (DICE Score differences can be approximated by the normal distribution) and have a good agreement with each other (from histograms and Bland-Altman plots). b) The DICE scores of the proposed device are generally higher than those of the predicate/reference device (from the Box and Whisker plots). c) The confidence interval of performance differences between the proposed and the predicate/reference devices are within the non-inferiority margin for all compared OARs. Hence the statement that the proposed device is noninferior to the predicate/reference device is established. Additionally, we demonstrate that the performance of the proposed device on the non-overlapping OARs is similar to its performance on the overlapping OARs (Comparison Study 3b).
We draw the following conclusions from these studies:
- DV.Target is non-inferior to the predicate device Mirada on all 19 overlapping OARs. This conclusion is supported by Comparison Studies 1&2, based on validation data from different sites and with independent annotations.
- . DV.Target is non-inferior to the reference device MIM on the 30 non-overlapping OARs. The performance of DV.Target on the non-overlapping OARs is similar to its performance on the overlapping OARs. This is supported by Comparison Studies 3a & 3b.
According to these results, we conclude that the performance of the proposed device is substantially equivalent to the performance of the predicate device.
# 9. Clinical Test Conclusion
No clinical study is included in this submission.
# 10. Substantially Equivalent (SE) Conclusion
Based on the comparison and analysis above, DeepVoxel Inc. believes that the proposed device can be determined to be Substantially Equivalent (SE) to the predicate device.
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.