AdvaView is a software application used for reference and diagnostic viewing and analysis of multi-modality medical imaging and non-imaging data (e.g., video information) with associated reports and information. AdvaView enables qualified healthcare professionals, including (but not limited to) physicians, surgeons, nurses, and administrators to receive and view patient images, documents, and data. AdvaView allows qualified users to perform simple and complex image manipulations (including window/level, markups, 3D visualization) and measurements. Not intended for primary diagnosis of mammographic images. Not intended for diagnostic use on mobile devices.
Device Story
AdvaView is a zero-footprint, web browser-based medical image viewer; enables access, manipulation, and measurement of multi-modality DICOM images (US, CT, MRI, X-Ray). Operates as a client-side application integrating with external PACS via RESTful APIs; delegates storage, authentication, and encryption to system integrators. Features include window/level adjustment, 3D visualization (MIP, MPR), annotation tools (pencil, ROI, spline, livewire), and clinical measurements (Cobb angle, spine-labeling, cardiothoracic ratio). Used by radiologists, technologists, physicians, and nurses in clinical settings to support diagnostic workflows. Output displayed on web browser; assists clinicians in image interpretation and clinical decision-making.
Clinical Evidence
Bench testing only. No clinical data was required. Verification and validation included manual testing of measurement tool accuracy using calibrated and un-calibrated phantom DICOM images. Statistical analysis (mean, standard deviation, standard error, one-tailed t-test) confirmed measurement accuracy within +/- 1 unit tolerance across zoom levels.
Technological Characteristics
Software-only, zero-footprint, web browser-based DICOM viewer. Architecture: client-side application using RESTful APIs for integration with external PACS/infrastructure. Features: multi-modality support (US, CT, MRI, X-Ray), 3D visualization (MIP, MPR), and measurement tools. Connectivity: networked via secured browser interface. Deployment: client-server integration model.
Indications for Use
Indicated for reference and diagnostic viewing/analysis of multi-modality medical images and non-imaging data by qualified healthcare professionals (physicians, surgeons, nurses, administrators). Intended for use in adolescents (12+ years) and adults. Contraindicated for primary diagnosis of mammographic images and diagnostic use on mobile devices.
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}
**FDA** U.S. FOOD & DRUG
ADMINISTRATION
August 14, 2026
Advahealth Solutions, LLC
% Meritxell Martinez
Senior Regulatory Affairs Specialist
Innolitics, LLC
1101 W. 34th St.
#550
AUSTIN TX 78705
Re: K262449
Trade/Device Name: AdvaView
Regulation Number: 21 CFR 892.2050
Regulation Name: Medical Image Management And Processing System
Regulatory Class: Class II
Product Code: LLZ
Dated: July 16, 2026
Received: July 16, 2026
Dear Meritxell Martinez:
We have reviewed your section 510(k) premarket notification of intent to market the device referenced above and have determined the device is substantially equivalent (for the indications for use stated in the enclosure) to legally marketed predicate devices marketed in interstate commerce prior to May 28, 1976, the enactment date of the Medical Device Amendments, or to devices that have been reclassified in accordance with the provisions of the Federal Food, Drug, and Cosmetic Act (the Act) that do not require approval of a premarket approval application (PMA). You may, therefore, market the device, subject to the general controls provisions of the Act. Although this letter refers to your product as a device, please be aware that some cleared products may instead be combination products. The 510(k) Premarket Notification Database available at https://www.accessdata.fda.gov/scripts/cdrh/cfdocs/cfpmn/pmn.cfm identifies combination product submissions. The general controls provisions of the Act include requirements for annual registration, listing of devices, good manufacturing practice, labeling, and prohibitions against misbranding and adulteration. Please note: CDRH does not evaluate information related to contract liability warranties. We remind you, however, that device labeling must be truthful and not misleading.
If your device is classified (see above) into either class II (Special Controls) or class III (PMA), it may be subject to additional controls. Existing major regulations affecting your device can be found in the Code of Federal Regulations, Title 21, Parts 800 to 898. In addition, FDA may publish further announcements concerning your device in the Federal Register.
U.S. Food & Drug Administration
10903 New Hampshire Avenue
Silver Spring, MD 20993
www.fda.gov
{1}
K262449 - Meritxell Martinez
Page 2
Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device" (https://www.fda.gov/media/99812/download) and "Deciding When to Submit a 510(k) for a Software Change to an Existing Device" (https://www.fda.gov/media/99785/download).
Your device is also subject to, among other requirements, the Quality Management System Regulation (QMSR) (21 CFR Part 820), which includes, but is not limited to, ISO 13485 clause 7.3 (Design controls), ISO 13485 clause 8.3 (Nonconforming product), ISO 13485 clause 8.5.2 (Corrective action), and ISO 13485 clause 8.5.3 (Preventative action). Please note that regardless of whether a change requires premarket review, the QMSR requires device manufacturers to review and approve changes to device design and production (ISO 13485 clause 7.3 and ISO 13485 clause 7.5) and document changes and approvals in the Medical Device File (ISO 13485 clause 4.2.3).
Please be advised that FDA's issuance of a substantial equivalence determination does not mean that FDA has made a determination that your device complies with other requirements of the Act or any Federal statutes and regulations administered by other Federal agencies. You must comply with all the Act's requirements, including, but not limited to: registration and listing (21 CFR Part 807); labeling (21 CFR Part 801); medical device reporting (reporting of medical device-related adverse events) (21 CFR Part 803) for devices or postmarketing safety reporting (21 CFR Part 4, Subpart B) for combination products (see https://www.fda.gov/combination-products/guidance-regulatory-information/postmarketing-safety-reporting-combination-products); good manufacturing practice requirements as set forth in the Quality Management System Regulation (QMSR) (21 CFR Part 820) for devices or current good manufacturing practices (21 CFR Part 4, Subpart A) for combination products; and, if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR Parts 1000-1050.
All medical devices, including Class I and unclassified devices and combination product device constituent parts are required to be in compliance with the final Unique Device Identification System rule ("UDI Rule"). The UDI Rule requires, among other things, that a device bear a unique device identifier (UDI) on its label and package (21 CFR 801.20(a)) unless an exception or alternative applies (21 CFR 801.20(b)) and that the dates on the device label be formatted in accordance with 21 CFR 801.18. The UDI Rule (21 CFR 830.300(a) and 830.320(b)) also requires that certain information be submitted to the Global Unique Device Identification Database (GUDID) (21 CFR Part 830 Subpart E). For additional information on these requirements, please see the UDI System webpage at https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance/unique-device-identification-system-udi-system.
Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21 CFR 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to https://www.fda.gov/medical-devices/medical-device-safety/medical-device-reporting-mdr-how-report-medical-device-problems.
For comprehensive regulatory information about medical devices and radiation-emitting products, including information about labeling regulations, please see Device Advice (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-assistance) and CDRH Learn (https://www.fda.gov/training-and-continuing-education/cdrh-learn). Additionally, you may contact the Division of Industry and Consumer Education (DICE) to ask a question about a specific regulatory topic. See the DICE website (https://www.fda.gov/medical-devices/device-advice-comprehensive-regulatory-
{2}
K262449 - Meritxell Martinez
Page 3
assistance/contact-us-division-industry-and-consumer-education-dice) for more information or contact DICE by email (DICE@fda.hhs.gov) or phone (1-800-638-2041 or 301-796-7100).
Sincerely,
, for
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
Enclosure
{3}
| Indications for Use | | |
| --- | --- | --- |
| Please type in the marketing application/submission number, if it is known. This textbox will be left blank for original applications/submissions. | | K262449 ? |
| Please provide the device trade name(s). | | ? |
| AdvaView | | |
| Please provide your Indications for Use below. | | ? |
| AdvaView is a software application used for reference and diagnostic viewing and analysis of multi-modality medical imaging and non-imaging data (e.g., video information) with associated reports and information. AdvaView enables qualified healthcare professionals, including (but not limited to) physicians, surgeons, nurses, and administrators to receive and view patient images, documents, and data. AdvaView allows qualified users to perform simple and complex image manipulations (including window/level, markups, 3D visualization) and measurements. | | |
| Not intended for primary diagnosis of mammographic images. | | |
| Not intended for diagnostic use on mobile devices. | | |
| Please select the types of uses. | ☑ Prescription Use (21 CFR 801 Subpart D) ☐ Over-The-Counter Use (21 CFR 801 Subpart C) | ? |
| Please select the age group(s) for which the device(s) is to be used. | ☐ Neonates/Newborns (Birth to < 29 days old) ☐ Infants (29 days old to < 2 years old) ☐ Children (2 years old to < 12 years old) ☑ Adolescents (12 years old to < 22 years old) ☑ Adults (22 years old and greater) | ? |
{4}
**ADVA**^{}[] Health
K262449
**510(k) Summary**
## 1. SUBMITTER INFORMATION
| Company Name | AdvaHealth Solutions |
| --- | --- |
| Address | 331 2nd Avenue Suite 400, Minneapolis, MN 55401 US |
| Company Contact | Imad Nijim, CEO |
| Email | imad.nijim@advahealthsolutions.com |
| Primary Correspondent | Meritxell Martinez, Innolitics |
| Email | fda@innolitics.com |
| Date Prepared | July 16th, 2026 |
## 2. DEVICE INFORMATION
| **Trade Name** | AdvaView |
| --- | --- |
| **Common Name** | DICOM Viewer |
| **Product Code** | LLZ |
| **Regulation Number** | 892.2050 |
| **Classification Name** | Picture archiving and communications system |
| **Class** | Class II |
| **Panel** | Radiology |
## 3. PREDICATE DEVICE INFORMATION
| **Predicate Device Name** | FlexView Diagnostic |
| --- | --- |
| **Manufacturer** | AdvaHealth Solutions |
Page 1 of 6
{5}
ADVA Health
510(k) Summary
| **510(k) Number** | K233226 |
| --- | --- |
| **Product Code** | LLZ |
| **Regulation Number** | 892.2050 |
| **Classification Name** | Picture archiving and communications system |
| **Regulatory Class** | Class II |
| **Review Panel** | Radiology |
## 4. DEVICE DESCRIPTION
AdvaView is a medical image viewer which allows, reviewing, manipulating, and visualizing medical multi-modality image data in DICOM format and other data. AdvaView is a server-based solution that may integrate with healthcare facility software systems and display DICOM images. AdvaView enables healthcare professionals to access, manipulate, and measure DICOM images and collaborate using diagnostic-quality medical images without installing client software.
The AdvaView application has the following primary features and functions:
- Zero-footprint web browser-based
- Allows access to images for all participants in the healthcare process, including radiologists, technologists, physicians, nurses, and other patient care practitioners
- Contains functionality to view, annotate, and measure images
- Contains industry-standard tools for image manipulation, annotation, and measurements
- Advanced image manipulation functions like view synchronization across series, 3D visualization such as MIP and MPR
- Encrypted transmission of medical images through secured networks
- HIPAA-compliant data management, including centralized storage of user activities via audit trails
Page 2 of 6
{6}
**ADVA**^{}[] Health
**510(k) Summary**
AdvaView is a configurable, software-only, web browser-based medical image viewer that displays and processes digital medical images and associated medical information to support clinical workflows.
AdvaView functions as a client application, enabling users to access, retrieve, and interact with imaging data through interfaces and APIs.
## **4.1. Key Marketing Claims**
AdvaView is a zero-footprint web viewer for medical images. AdvaView allows easy access to image data through systems that implement the prescribed API Specifications.
## **5. INDICATIONS FOR USE**
AdvaView is a software application used for reference and diagnostic viewing and analysis of multi-modality medical imaging and non-imaging data (e.g., video information) with associated reports and information. AdvaView enables qualified healthcare professionals, including (but not limited to) physicians, surgeons, nurses, and administrators to receive and view patient images, documents, and data. AdvaView allows qualified users to perform simple and complex image manipulations (including window/level, markups, 3D visualization) and measurements.
**Not intended for primary diagnosis of mammographic images.**
**Not intended for diagnostic use on mobile devices.**
## **6. PREDICATE DEVICE COMPARISON**
### **6.1. Summary of Technological Characteristics Comparison**
AdvaView is a modification of the predicate device, FlexView Diagnostic (K233226), submitted under the Special 510(k) pathway. The subject and predicate devices have the same intended use and the same fundamental scientific technology: both are web browser-based, multi-modality medical image viewers that load, display, manipulate, annotate, and measure DICOM images and associated data, and both rely on an existing PACS as the source of imaging studies. Both provide the same core review capabilities, including window/level adjustment,
Page 3 of 6
{7}
ADVA Health
510(k) Summary
image view controls (rotate, pan, and zoom), measurement functions, text annotations, report generation, and DICOM windowing, and both support the same imaging modalities (US, CT, MRI, and X-Ray).
The principal technological difference between the two devices is a change in deployment architecture. FlexView Diagnostic was deployed as a hosted, multi-tenant platform that operated self-managed backend infrastructure. AdvaView has been re-implemented as a client-side, zero-footprint viewer that runs within the web browser and integrates with external systems for image storage, configuration, authentication, and supporting services through defined RESTful API interfaces. Consistent with this architecture, functions that were previously performed by the self-operated backend (e.g., patient-data storage and confidentiality, service availability, in-transit encryption, and user authentication and access control) are delegated to the system integrator and the third-party PACS. This is a change in how the software is deployed and integrated rather than a change in the methods by which images are rendered, manipulated, or measured. The fundamental scientific technology of the viewer is unchanged.
AdvaView also adds a set of viewer features that extend the functionality of the predicate. These fall into four categories:
- Image display and projection functions, including Maximum, Minimum, and Average Intensity Projection modes, a viewport scale overlay, and scrollbar.
- Region-of-interest and measurement tools, including ellipse, rectangle, circle, and freehand ROI tools; spline and livewire contour tools; and Cobb angle, spine-labeling, and cardiothoracic ratio (CTR) tools.
- Annotation and workspace customization, including a pencil annotation tool, an annotation show/hide toggle, hanging-protocol configuration, multiple-monitor support, and configurable thumbnail location, radial menu, toolbars, viewport labels, and mouse bindings.
- Input-handling robustness, through validation of DICOM input received from external systems.
These differences between the subject and predicate devices do not alter the intended use and do not raise new questions of safety or effectiveness.
Page 4 of 6
{8}
**ADVA**^{}[] Health
**510(k) Summary**
## **7. DISCUSSION OF PERFORMANCE TESTING**
### **7.1. Software Verification and Validation**
Software verification and validation testing were conducted on the AdvaView system and documentation was provided as recommended by FDA’s 2023 Guidance for Industry and FDA Staff, “Content of Premarket Submissions for Device Software Functions.”
The software verification and validation testing verified that the design requirements were successfully met. The intended use and user needs were successfully validated.
#### **7.1.1. Measurement Accuracy**
Verification of AdvaView included manual testing of the accuracy of the measurement tools using phantom (calibrated and un-calibrated) DICOM images.
Measurement accuracy testing involved evaluating the difference (i.e., delta) between the expected length and the measurement entered by the user. Delta results were calibrated to +/- 1 units, which is equivalent to +/- 1 units relative to the acquisition size and display resolution. This calibration ensured consistent accuracy across different zoom levels.
Acceptance criteria for this test included statistical analyses such as mean, standard deviation, standard error and a one tailed t-test. Verification testing for all measurement tools passed the predetermined acceptance criteria.
### **7.2. Conclusion**
AdvaView is a modification of AdvaHealth Solutions’ own legally marketed device, FlexView Diagnostic (K233226), submitted under the Special 510(k) pathway. AdvaView retains the same intended use and the same fundamental scientific technology as the predicate: both are zero-footprint, web browser-based, multi-modality medical image viewers that load, display, manipulate, annotate, and measure DICOM images and associated data, and both rely on an existing PACS as the source of imaging studies.
The modifications comprise a change in deployment architecture together with a set of additional viewer features. Each modification was evaluated under the manufacturer’s design control procedures using well-established methods, and the associated risk analysis,
Page 5 of 6
{9}

## 510(k) Summary
verification, and validation activities demonstrate that the changes were adequately verified and validated. No clinical testing was necessary to support the modifications. The results confirm that the modifications do not alter the intended use and do not raise new questions of safety or effectiveness relative to the predicate.
Based on the risk analysis, the verification and validation results, and the technological characteristics comparison presented above, AdvaView is substantially equivalent to FlexView Diagnostic (K233226).
Page 6 of 6
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.