Al Viewer is intended to be used with off the shelf computing devices. Al Viewer supports major desktop browsers such as Microsoft Edge, Chrome, Safari.

Al Viewer can display annotations and measurements as an overlay on images from DICOM objects, and from Al software. The viewer can perform 3D Multi-Planar Reformatting (MPR), 3D Maximum Intensity Projection (MIP) and 3D Volume Rendering (VR). Al Viewer is purposed to aid in reviewing findings through its ability to display clinical documents and reports side by side with the images.

Device Description

Al Viewer is a stand-alone software as medical device (Stand-alone SaMD) for clinicians able to use web browsers at client stations to view DICOM image data. It is intended to provide image and related information to render and interact with Al findings and annotations from Lung Nodule detection Al algorithms, but it does not directly generate any potential findings or diagnosis.

Al Viewer allows trained medical professionals to perform 2D, MPR & 3D image manipulations using the Adjustment Tools, including window level, rotate, flip, pan, stack scroll, and magnify. Al Viewer is also capable of organizing all the images and presenting them in a zero-footprint, web user interface, allowing the users to view images in their preferred layout.

Al Viewer allows trained medical professions with the Al Findings such as accept/reject/edit. Editing tools include selecting descriptive features for findings as well as allowing the physician to control editing quantifiable measurements first computed by AI such as lengths and volumes.

Al Viewer supports major desktop browsers such as Microsoft Edge, Chrome, Safari.

AI/ML Overview

The provided text is a 510(k) summary for the Fovia, Inc. aiCockpit AI Viewer. However, it does not contain the specific details required to fully describe the acceptance criteria and the study that proves the device meets them, as requested in your prompt.

Specifically, the document states: "Software Validation and Verification Testing was conducted, and documentation was provided as recommended by FDA's Guidance for Industry and FDA Staff..." and then lists general testing steps like "Full regression tests..." and "Bug fix verification...". It also explicitly states "Not Applicable" for more detailed information when describing "Non-Clinical and/or Clinical Tests Summary & Conclusions 21 CFR 807.92(b)".

This means the key information you're asking for, such as a table of acceptance criteria, reported device performance, sample sizes, ground truth establishment, and details of comparative effectiveness studies (MRMC or standalone), is not present in the provided text.

Based on the available information, I can only provide a summary of what the document does state about testing:

No specific acceptance criteria or detailed study results are provided in this document. The 510(k) summary indicates that software validation and verification testing was conducted according to FDA guidance, but it does not disclose the acceptance criteria, the reported performance, or the methodologies of these tests in detail.

Here's what can be extracted, acknowledging the significant gaps in information for your request:

1. A table of acceptance criteria and the reported device performance:

Information Not Provided: The document does not specify any quantitative or qualitative acceptance criteria for the aiCockpit AI Viewer's performance. It also does not report specific device performance metrics against any criteria.

2. Sample sized used for the test set and the data provenance (e.g., country of origin of the data, retrospective or prospective):

Information Not Provided: The document does not specify the sample size of any test set used, nor does it provide details about the data provenance (country of origin, retrospective/prospective).

3. Number of experts used to establish the ground truth for the test set and the qualifications of those experts (e.g., radiologist with 10 years of experience):

Information Not Provided: The document does not mention the use of experts to establish a ground truth for a test set, nor does it specify their number or qualifications.

4. Adjudication method (e.g., 2+1, 3+1, none) for the test set:

Information Not Provided: No adjudication method is mentioned in the document.

5. If a multi reader multi case (MRMC) comparative effectiveness study was done, If so, what was the effect size of how much human readers improve with AI vs without AI assistance:

Information Not Provided: The document does not describe any MRMC comparative effectiveness study. The AI Viewer is described as a tool to "render and interact with AI findings and annotations from Lung Nodule detection AI algorithms" and to "display annotations and measurements as an overlay on images from DICOM objects, and from AI software," rather than an AI algorithm itself that would augment human reading for a direct performance comparison.

6. If a standalone (i.e. algorithm only without human-in-the-loop performance) was done:

Information Not Provided: The document describes the aiCockpit AI Viewer as a "stand-alone software as medical device (Stand-alone SaMD)" for clinicians to view DICOM data and interact with AI findings. It explicitly states it "does not directly generate any potential findings or diagnosis." Therefore, a standalone performance of an algorithm itself is not relevant to this specific device's function as a viewer.

7. The type of ground truth used (expert consensus, pathology, outcomes data, etc.):

Information Not Provided: No ground truth information is provided in the document.

8. The sample size for the training set:

Information Not Provided: The document does not discuss any training set, as the device is a viewer for AI findings, not an AI algorithm itself that requires training.

9. How the ground truth for the training set was established:

Information Not Provided: Not applicable, as no training set or ground truth for a training set is mentioned for this device.

What the document does say about testing:

Software Validation and Verification Testing Summary:
- "The verifications of features were performed by members of the product." (No specific roles mentioned for these "members")
- Test Steps Included:
  - Full regression tests executed on the build with all feature implementations to uncover bugs.
  - Bug fix verification for reported issues and regression tests on related features.
  - End-to-end full tests executed on the candidate build to verify all functionalities and fixes.
- Guidance Followed: FDA's Guidance for Industry and FDA Staff, "Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices" and "Content of Premarket Submission for Management of Cybersecurity in Medical Devices."

In conclusion, while the document confirms that software validation and verification testing took place to support the substantial equivalence claim, it does not provide the specific performance data, acceptance criteria, sample sizes, or details about ground truth and expert involvement that your request asks for. This type of detailed information is typically found in the full 510(k) submission and associated test reports, which are not part of this summary document.

Summary

{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.

February 26, 2025

Fovia, Inc. Paula Brown Head of Regulatory P.O. Box 1858 Ross. California 94957

Re: K241546

Trade/Device Name: aiCockpit AI Viewer Regulation Number: 21 CFR 892.2050 Regulation Name: Medical Image Management And Processing System Regulatory Class: Class II Product Code: LLZ Dated: January 24, 2025 Received: January 24, 2025

Dear Paula Brown:

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 (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.

{1}------------------------------------------------

Additional information about changes that may require a new premarket notification are provided in the FDA guidance documents entitled "Deciding When to Submit a 510(k) for a Change to an Existing Device" (https://www.fda.gov/media/99812/download) and "Deciding When to Submit a 510(k) for a Software Change to an Existing Device" (https://www.fda.gov/media/99785/download).

Your device is also subject to, among other requirements, the Quality System (OS) 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 OS 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.

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-device-advicecomprehensive-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-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-regulatory

{2}------------------------------------------------

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,

Samul
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

Submission Number (if known)

K241546

Device Name

aiCockpit Al Viewer

Indications for Use (Describe)

Al Viewer is software for clinical review intended for use in General Radiology and other healthcare imaging applications.

Al Viewer is intended to be used with off the shelf computing devices. Al Viewer supports major desktop browsers such as Microsoft Edge, Chrome, Safari.

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."

{4}------------------------------------------------

510(k) #:	K241546
510(k) Summary	Prepared on: 2025-01-24

Contact Details

Applicant Name	Fovia, Inc.
Applicant Address	P.O. Box 1858 Ross CA 94957 United States
Applicant Contact Telephone	415-328-3358
Applicant Contact	Ms. Paula Brown
Applicant Contact Email	paula.brown@fovia.com

Device Name

Device Trade Name	aiCockpit Al Viewer
Common Name	Medical image management and processing system
Classification Name	System, Image Processing, Radiological
Regulation Number	892.2050
Product Code(s)	LLZ

Legally Marketed Predicate Devices

Predicate #	Predicate Trade Name (Primary Predicate is listed first)	Product Code
K222476	Ramsoft OmegaAl Image Viewer	LLZ

Device Description Summary

Al Viewer supports major desktop browsers such as Microsoft Edge, Chrome, Safari.

Intended Use/Indications for Use

Al Viewer is software for clinical review intended for use in General Radiology and other healthcare imaging applications.

21 CFR 807.92(a)(5)

Al Viewer is intended to be used with off the shelf computing devices. Al Viewer supports major desktop browsers such as Microsoft Edge, Chrome, Safari.

Al Viewer can display annotations and measurements as an overlay on images from DICOM objects, and from Al software. The viewer

{5}------------------------------------------------

can perform 3D Multi-Planar Reformatting (MPR), 3D Maximum Intensity Projection (MIP) and 3D Volume Rendering (VR). Al Viewer is purposed to aid in reviewing findings through its ability to display clinical documents and reports side by side with the images.

Indications for Use Comparison

21 CFR 807.92(a)(5)

21 CFR 807.92(a)(6)

The indications for use are the same

Technological Comparison

The Ramsoft OmegaAl Image Viewer is the predicate device for the Fovia Al Viewer. The two devices are substantially equivalent as they both provide the same functionality and possess the same technological characteristics.

From a high-level overview, both devices can "display annotations and measurements as an overlay on images from DICOM objects, and from Al software" (providing the same functionality) and both devices are based on the same architecture of "Server-based software solution that displays images and reports from a PACS using a zero-footprint application (browser)" (using the same technological characteristics).

From a more detailed level:

1. Both devices are intended for use in Radiology
1. Both devices are zero-footprint web-based JavaScript applications supporting common desktop browsers (e.g., Edge, Chrome, Safari)
1. Both devices display DICOM images
1. Both devices allow common image viewing tools such as Pan, Zoom, Window/Level, Rotate, & Scroll/Paqe
1. Both devices display annotations and measurement results from Al algorithms
1. Both devices allow the physician to control the editing and adjustment of the Al results (annotations and measurements)
1. Both devices provide flexible layout preferences

The only difference between the two devices is that Ramsoft OmegaAl Image Viewer provides more functionality than the Fovia Al Viewer - it could also be described as Fovia Al Viewer being a subset of the Ramsoft OmegaAl Image Viewer. For example:

Ramsoft OmegaAl Image Viewer supports images in a long list of -ology's (including radiology), while the Fovia Al Viewer is intended to be used only in radiology.
Ramsoft OmegaAl Image Viewer supports both Desktop Browser and Mobile environments while Fovia Al Viewer supports only Desktop Browser environments.
Ramsoft OmegaAl Image Viewer can be "used for image manipulation by radiology technologists (as well as radiologists for its other functionality)" while the Fovia Al Viewer is intended to be used by radiologists (for the same functionality at Ramsoft OmegaAl Image Viewer and not by radiology technologists at all).

Conclusion:

The comparison of the Subject Device with the predicate device shows that the aiCockpit Al Viewer software has similar functionality, intended use and technological characteristics as the predicate device. Based on the predicate and the performance testing conducted, the Subject Device is considered substantially equivalent to the predicate device.

Non-Clinical and/or Clinical Tests Summary & Conclusions 21 CFR 807.92(b)

Software Validation and Verification Testing Summary

The performance data provided in the form of test cases as well as verification test reports conducted on the Al Viewer include the following:

The verifications of features were performed by members of the product Al Viewer has been performed with the following steps

· Full regression tests have been executed on the build with the implementations of all features. The purpose is to uncover as much as possible all the potential bugs that could be detected by QA's test scripts.

· Bug fix verification for reported issues and regression test on related features

· End-to-end full tests have been executed on the candidate build for the release to verify all functionalities and fixes.

Not Applicable

{6}------------------------------------------------

Software Verification and Validation Testing was conducted, and documentation was provided as recommended by FDA's Guidance for Industry and FDA Staff, "Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices" and "Content of Premarket Submission for Management of Cybersecurity in Medical Devices." In conclusion, the subject device is considered substantially equivalent to the predicate device

Regulation Number and Section

§ 892.2050 Medical image management and processing system.

(a)
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.(b)
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).