The vRad Viewer software is used with general purpose computing hardware which meets or exceeds minimum specifications. The vRad Viewer is intended to receive, display, and transmit images for clinical purposes. The vRad Viewer is intended for installation on an off-the-shelf PC meeting or exceeding minimum specifications and networked with storage components. The vRad Viewer is intended to serve as the primary user interface for the processing of medical images for presentation on displays appropriate to the medical task beinq performed. The vRad Viewer can process medical images from DICOM modalities, such as X-ray radiography, X-ray computed tomography, magnetic resonance imaging, ultrasound, nuclear medicine, and images from other DICOM-compliant modalities. The vRad Viewer may be used for the display, manipulation, and interpretation of lossless compressed or non-compressed mammography images that have been received in the DICOM "For Presentation" format and may only be used on monitors determined to be appropriate for the desired task.
Device Story
vRad Viewer is SaMD for visualization, manipulation, and interpretation of DICOM medical images; imports data from local storage or remote PACS; operates on off-the-shelf Windows 10 PCs; supports standard input devices (mouse, keyboard, foot pedal, jog-dial). Used by radiologists/clinicians in clinical settings to view, enhance, compress, and quantify images; includes workflow tools like color maps, window/level presets, and overlay schemes. Facilitates clinical decision-making by providing primary user interface for image presentation on appropriate monitors. Benefits include efficient access to diagnostic imaging and customizable viewing environment.
Clinical Evidence
No clinical data. Bench testing only; software verification and validation conducted per FDA guidance; cybersecurity testing performed.
Technological Characteristics
SaMD; Windows 10-based application; runs on off-the-shelf PC hardware; DICOM-compliant; supports lossless/non-compressed mammography; connectivity via network to PACS/storage; software-based image manipulation/enhancement tools.
Indications for Use
Indicated for clinical display, manipulation, and interpretation of DICOM medical images (X-ray, CT, MRI, ultrasound, nuclear medicine, mammography) by healthcare professionals on compatible PC workstations.
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}------------------------------------------------
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.
Virtual Radiologic Corporation % Ellie Reynolds Regulatory Affairs Consultant Proxima Clinical Research 2450 Holcombe Boulevard HOUSTON, TEXAS 77021
July 18, 2024
Re: K241879
Trade/Device Name: vRad Viewer Regulation Number: 21 CFR 892.2050 Regulation Name: Medical image management and processing system Regulatory Class: Class II Product Code: LLZ Dated: June 26, 2024 Received: June 28, 2024
Dear Ellie Reynolds:
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.
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).
{1}------------------------------------------------
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 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-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 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.
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-device-safety/medical-device-reportingmdr-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/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.
Jessica Lamb
Jessica Lamb, PhD 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
{2}------------------------------------------------
# Indications for Use
Submission Number (if known)
K241879
Device Name
vRad Viewer
#### Indications for Use (Describe)
The vRad Viewer software is used with general purpose computing hardware which meets or exceeds minimum specifications. The vRad Viewer is intended to receive, display, and transmit images for clinical purposes. The vRad Viewer is intended for installation on an off-the-shelf PC meeting or exceeding minimum specifications and networked with storage components. The vRad Viewer is intended to serve as the primary user interface for the processing of medical images for presentation on displays appropriate to the medical task beinq performed. The vRad Viewer can process medical images from DICOM modalities, such as X-ray radiography, X-ray computed tomography, magnetic resonance imaging, ultrasound, nuclear medicine, and images from other DICOM-compliant modalities.
The vRad Viewer may be used for the display, manipulation, and interpretation of lossless compressed or non-compressed mammography images that have been received in the DICOM "For Presentation" format and may only be used on monitors determined to be appropriate for the desired task.
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."
{3}------------------------------------------------
| 510(k) Owner: | Virtual Radiologic Corporation<br>11995 Singletree Lane<br>Eden Prairie, MN 55344 |
|------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Official Contact: | Wade Steigauf<br>Telephone: +1-952-595-1249<br>E-mail: Wade.Steigauf@vRad.com |
| Representative Consultant Contact: | Ellie Reynolds, MBE<br>Proxima Clinical Research, Inc.<br>2450 Holcombe Blvd, Suite J<br>Houston, TX 77021<br>Telephone: +1-214-213-0611<br>E-mail: Ellie@ProximaCRO.com |
| Date Summary Prepared: | 18 July 2024 |
| Trade Name: | vRad Viewer |
| Common Name: | System, Image Processing, Radiological |
| Classification: | Class II |
| Classification Number: | 21 CFR 892.2050 |
| Product Code(s): | LLZ |
| Classification Advisory Committee: | Radiology |
{4}------------------------------------------------
### Predicate Device(s):
#### Device Description:
The vRad Viewer is a Software as a Medical Device (SaMD) that imports medical data in the Digital Imaging and Communications and Medicine (DICOM) standard from local storage or remote Picture Archiving and Communications System (PACS) sources. The vRad Viewer is a modified version of the Viewer component cleared as part of vRad PACS with Mammography (K162145). Like the Viewer component of the vRad PACS with Mammography device, the vRad Viewer is intended to allow users to visualize, manipulate, and interpret medical images from X-ray radiography, X-ray computed tomography, MRI, ultrasound, nuclear medicine, and other DICOM-compliant modalities on compatible PC workstations. The vRad Viewer is designed to interface with radiologist workflow applications, such as PACS or caching applications, as well as operate as a standalone image viewer.
The vRad Viewer allows users to perform operations related to the manipulation, enhancement, compression, and quantification of medical images at the command of the operator and based on user preferences. Other workflow tools (e.g., Color Map, Window Level Presets, Overlay Display Schemes) exist within the Viewer to allow for operator customization of display and usage preferences.
The Viewer is a Microsoft Windows-based software application that runs on "off-the-shelf" computers that meet the specified minimum basic computer confiquration for the Viewer and are running Microsoft Windows 10 Operating System (OS). For operator input and control of the software, standard Microsoft Windows-compatible input devices are used, including keyboards of various configurations, multi-button mice, grips, foot pedal controls, the Contour ShuttlePRO (Jog-Dial), etc. The vRad Viewer is not a hardware device; however, a monitor is required to display images and to interface with the software. Image quality may vary depending on the display monitor, and users must utilize a compatible monitor that meets technical specifications required for the tasks intended to be performed by the user.
### Intended Use / Indications for Use:
The vRad Viewer software is used with general purpose computing hardware which meets or exceeds minimum specifications. The vRad Viewer is intended to receive, display, and transmit images for clinical purposes. The vRad Viewer is intended for installation on an off-the-shelf PC meeting or exceeding minimum specifications and networked with storage components. The vRad Viewer is intended to serve as the primary
{5}------------------------------------------------
user interface for the processing of medical images for presentation on displays appropriate to the medical task being performed. The vRad Viewer can process medical images from DICOM modalities, such as X-ray radiography, X-ray computed tomography, magnetic resonance imaging, ultrasound, nuclear medicine, and images from other DICOM-compliant modalities.
The vRad Viewer may be used for the display, manipulation, and interpretation of lossless compressed or non-compressed mammography images that have been received in the DICOM "For Presentation" format and may only be used on monitors determined to be appropriate for the desired task.
# Technological Characteristics:
The technological characteristics of the vRad Viewer are substantially equivalent to the technological characteristics of the predicate device. Both devices may be used to evaluate the same imaging types, provide on-demand access to the image database, and provide image manipulation, annotation, and processing functions. Both devices may also be used to review reports, identify key images, and link a series of images. The predicate device differs from the vRad Viewer in that it consists of 3 primary components: Viewer, Storage, and Cache, while the vRad Viewer only contains the Viewer component. Other minor differences of the vRad Viewer include additional annotation and image viewing tools that are not present in the predicate device and updated operating system and web browser compatibility. Nevertheless, any differences in technological characteristics between the vRad Viewer and the predicate device do not raise any new and different questions in safety and effectiveness, and device performance has been verified through testing.
### Software Testing:
The software used in the vRad Viewer has been determined to require a Basic Level of Documentation. Software verification and validation testing were conducted, and documentation has been provided in accordance with FDA Guidance Document, "Content of Premarket Submission for Device Software Functions."
### Cybersecurity Testing:
Cybersecurity testing for the vRad Viewer was conducted, and documentation has been provided in accordance with FDA Guidance Documents. "Cybersecurity in Medical Devices: Quality System Considerations and Content of Premarket Submissions" and "Select Updates for the Premarket Cybersecurity Guidance: Section 524B of the FD&C Act."
{6}------------------------------------------------
# Conclusion:
In conclusion, the vRad Viewer is demonstrated to be as safe and effective as the identified predicate device. The vRad Viewer has the same intended use, principles of operation, and technological characteristics as the identified predicate device. Any minor differences in technological characteristics do not raise new or different questions regarding its safety and effectiveness when used as labeled. Software and cybersecurity testing demonstrate that the device performs as expected. Thus, the vRad Viewer is substantially equivalent to the identified predicate device.
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.