FORUM FORUM ARCHIVE FORUM ARCHIVE & VIEWER FORUM ASSIST MATCH
K122938 · Carl Zeiss Meditec, AG · NFJ · Nov 2, 2012 · Radiology
Device Facts
Record ID
K122938
Device Name
FORUM FORUM ARCHIVE FORUM ARCHIVE & VIEWER FORUM ASSIST MATCH
Applicant
Carl Zeiss Meditec, AG
Product Code
NFJ · Radiology
Decision Date
Nov 2, 2012
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 892.2050
Device Class
Class 2
Attributes
Software as a Medical Device, 3rd-Party Reviewed
Indications for Use
FORUM is a software system intended for use in storage, management, processing, and display of patient, diagnostic, video and image data and measurement from computerized diagnostic instruments or documentation systems through networks. It is intended to work with other FORUM applications. FORUM is intended for use in review of patient, diagnostic and image data and measurement by trained healthcare professionals.
Device Story
FORUM is a client-server software system for ophthalmic image and data management. It ingests diagnostic data (images, videos, reports, raw data) from networked ophthalmic instruments via DICOM interface. The server archives data; the client application provides a GUI for administration and review. FORUM Viewer allows clinicians to display data, perform manual line measurements on fundus images using DICOM header scaling, and add comments. It supports modality worklist scheduling and integrates with EMR/HIS systems via HL7. The system facilitates clinical workflow by centralizing patient records, enabling remote access via VPN, and identifying duplicate records via the FORUM ASSIST match accessory. Clinicians use the output to review diagnostic findings and support clinical decision-making.
Clinical Evidence
Bench testing only. Performance testing confirmed DICOM compliance and verified the accuracy of the line measurement functionality. No clinical data was required or provided.
Technological Characteristics
Client-server software architecture; central database for storage of ophthalmic diagnostic documents. Connectivity via LAN/network using DICOM and HL7 standards. Features include GUI-based image review, modality worklist, and manual line measurement tools. Remote access supported via VPN.
Indications for Use
Indicated for use by trained healthcare professionals for the storage, management, processing, and review of patient, diagnostic, video, and image data from ophthalmic diagnostic instruments.
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}------------------------------------------------
# SECTION 5.
# 510(K) SUMMARY
5. 510(K) SUMMARY
## 510(k) SUMMARY (per 21 CFR §807.92)
NOV 2 2012
## FORUM™
## GENERAL INFORMATION
| Manufacturer: | Carl Zeiss Meditec AG<br>Goeschwitzer Strasse 51-52<br>D-07745 Jena, Germany<br>+49 3641220-667 (phone)<br>+49 3541220-756 (fax)<br>Establishment Registration Number: 9615030 |
|-------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Contact Person: | Judith A. Brimacombe<br>Director, Clinical/Regulatory Affairs<br>Carl Zeiss Meditec, Inc.<br>5160 Hacienda Drive<br>Dublin, CA 94568<br>(925) 557-4616 Phone<br>(925) 557-4259 Fax<br>E-mail: j.brimacombe@meditec.zeiss.com |
| Date prepared: | October 17, 2012 |
| Device | System, Image Management, Ophthalmic |
| Classification: | 21 CFR 892.2050 |
| Device Class: | II |
| Product Code: | NFJ |
| Common Name: | Picture Archiving and Communications System |
| Trade/Proprietary Name: | FORUM™, FORUM Archive, FORUM Archive & Viewer |
{1}------------------------------------------------
## SECTION 5.
## 510(K) SUMMARY
#### PREDICATE DEVICES:
| Company: | Carl Zeiss Surgical GmbH |
|----------|------------------------------|
| Device: | FORUM |
| | (K090439) |
| Company: | Topcon Medical Systems, Inc. |
| Device: | Synergy |
| | (K093313) |
#### INDICATIONS FOR USE
FORUM is a software system intended for use in storage, management, processing, and display of patient, diagnostic, video and image data and measurement from computerized diagnostic instruments or documentation systems through networks. It is intended to work with other FORUM applications.
FORUM is intended for use in review of patient, diagnostic and image data and measurement by trained healthcare professionals.
#### DEVICE DESCRIPTION
FORUM is a computer software system designed for storage, processing, and review of images, videos and reports originating from computerized diagnostic instruments or other documentation systems.
FORUM is available in two different product variants: FORUM Archive and FORUM Archive & Viewer.
The FORUM Archive consists of a server and a client application. The server offers a DICOM interface to diagnostic instruments via a network. On this server, medical documents including reports, images, videos or raw data and patient data are archived. All data can be retrieved via the network by instruments or other applications using the DICOM interface. The client application provides a graphical user interface (GUI) for administering the server and the data stored therein.
FORUM Viewer serves as an additional module to the client application that allows health care professionals to display and review the data stored in FORUM Archive. FORUM Viewer enables health care professionals to perform measurements in fundus images, based on the scaling information which is provided in the DICOM header and add comments to the saved data. FORUM Viewer provides the option for data transfer to and from other FORUM installations and the ability to import non-DICOM data. FORUM Viewer also includes a modality worklist (scheduling).
{2}------------------------------------------------
## SECTION 5.
# 510(K) SUMMARY
FORUM Archive & Viewer provides the following workflow cycle:
- Receive patient demographic data from the leading systems, Electronic Medical Record ● (EMR) or Hospital Information Systems (HIS) and enter these manually into FORUM
- Transfer patient demographic data from FORUM to diagnostic instruments via modality . worklist (scheduling)
- Receive and archive exam data from diagnostic instruments ●
- Enable health care professionals to display and review exam data through FORUM . Viewer
FORUM also interfaces with other FORUM applications such as FORUM ASSIST match. This accessory software provides an improved workflow to identify potential duplicates of patient records that may then be merged using a merge operation already available on FORUM. The relevant supporting documentation for this software is provided within this 510(k).
#### SUBSTANTIAL EQUIVALENCE
It is the opinion of Carl Zeiss Meditec AG that the new version of FORUM (3.0) is substantially equivalent to the predicate devices FORUM (K090439) and Synergy (K093313). The indications for use statement for FORUM are similar to the indications for use of the predicate devices cited in this application. The technological comparison demonstrates that FORUM is functionally equivalent to the predicate devices.
The similarities and differences between the subject device FORUM and the predicate devices and how these differences do not impact the safety and effectiveness of the device are provided below.
- FORUM and the predicate devices comprise of a central database to store . diagnostic documents.
- FORUM and the predicate devices are client-server systems that provide a . software application (client) to view the stored data in the database (server).
- . FORUM and the predicate devices provide the management, storage and processing and display of patient, diagnostic, video and image data.
- . FORUM and the predicate devices can connect to LAN and have DICOM . interface.
- FORUM and the predicate device Synergy provide the measurement functionality . in imported images whereas the predicate device FORUM (K090439) does not. FORUM provides a line measurement in fundus images, whereas the predicate device Synergy provides line and area measurements of retinal images.
{3}------------------------------------------------
## 510(K) SUMMARY
Additionally, the predicate device Synergy also provides OCT Retinal and RNFL thickness measurement functions. The line measurement function in FORUM has been verified and validated and the results indicate that the difference does not raise new questions of safety and effectiveness.
- FORUM and the predicate device Synergy provide interface with Electronic . Medical Records (EMRs) or Practice Management Systems whereas the predicate device FORUM (K090439) does not. This function in FORUM uses the HL7 standard. HL7 is an established protocol, which has been verified with FORUM and the results indicate that the difference does not raise new questions of safety and effectiveness.
- FORUM and the predicate device FORUM (K090439) do not provide access to . patient data remotely via the internet. Remote access of data can only be done via the Virtual Private Network (VPN) whereas the predicate device Synergy provides data access remotely via the internet. The difference in this function does not raise new questions of safety and effectiveness.
Evaluation performed on FORUM supports the indications for use statement, demonstrates that the device is substantially equivalent to the predicate devices. The technological characteristics of FORUM are similar to those of the predicate devices. The minor differences between FORUM and the predicate devices are insignificant and do not impact the safety and effectiveness of the device.
#### TECHNOLOGICAL CHARACTERISTICS
The fundamental technological characteristics of the new version of FORUM (3.0) are similar to those of the predicate devices, FORUM (K090439) and Synergy (K093313). All systems comprise a central database to store diagnostic documents (i.e. retinal images and reports of other ophthalmic diagnostic devices). These documents are imported from the diagnostic devices via a network connection.
All systems are client-server systems which provide a software application (client) to view the data stored in the database (server). FORUM Viewer allows the user to search for patient records and display these for comparison purposes. FORUM interfaces with other FORUM applications, devices and systems. The client software can be used to access the database from a remote location via network.
FORUM and the predicate devices all serve the same principal purpose of clinical usage and provide a wide range of comparable functionality for their users.
{4}------------------------------------------------
s
.
# SECTION 5.
# 510(K) SUMMARY
#### PERFORMANCE DATA
Performance testing was conducted on FORUM and was found to perform as intended. FORUM is DICOM compliant according to its DICOM conformance statement.
#### SUMMARY
As described in this 510(k) Summary, all testing deemed necessary was conducted on FORUM to ensure that the device is as safe and effective as the predicate devices.
{5}------------------------------------------------
Image /page/5/Picture/0 description: The image shows the logo for the Department of Health & Human Services - USA. The logo is a circular seal with the words "DEPARTMENT OF HEALTH & HUMAN SERVICES - USA" around the perimeter. Inside the circle is a stylized image of an eagle with its wings spread. The eagle is made up of three curved lines.
#### DEPARTMENT OF HEALTH & HUMAN SERVICES
Public Health Service
Food and Drug Administration 10903 New Hampshire Avenue Document Control Center - WO66-G609 Silver Spring, MD 20993-002
Regulatory Technology Services, LLC c/o Mark Job 1394 25th Street NW Buffalo, MN 55313
Re: 510(k) Number: K122938
Trade/Device Name: FORUM Archive, FORUM Archive & Viewer Regulation Number: 21 CFR 892.2050 Regulation Name: Picture archiving and communications system Regulatory Class: Class II Product Code: NFJ Dated: October 18, 2012 Received: October 19, 2012
Dear Mr. Job:
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. 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 (reporting of medical
OV 2 200
{6}------------------------------------------------
device-related adverse events) (21 CFR 803); good manufacturing practice requirements as set forth in the quality systems (OS) regulation (21 CFR Part 820); and if applicable, the electronic product radiation control provisions (Sections 531-542 of the Act); 21 CFR 1000-1050.
If you desire specific advice for your device on our labeling regulation (21 CFR Part 801), please go to http://www.fda.gov/AboutFDA/CentersOffices/CDRH/CDRHOffices/ucm115809.htm for the Center for Devices and Radiological Health's (CDRH's) Office of Compliance. Also, please note the regulation entitled, "Misbranding by reference to premarket notification" (21CFR Part 807.97). For questions regarding the reporting of adverse events under the MDR regulation (21 CFR Part 803), please go to
http://www.fda.gov/MedicalDevices/Safety/ReportaProblem/default.htm for the CDRH's Office of Surveillance and Biometrics/Division of Postmarket Surveillance.
You may obtain other general information on your responsibilities under the Act from the Division of Small Manufacturers. International and Consumer Assistance at its toll-free number (800) 638-2041 or (301) 796-7100 or at its Internet address http://www.fda.gov/MedicalDevices/ResourcesforYou/Industry/default.htm.
Sincerely vours.
Kesia Alexander
Malvina B. Eydelman, M.D. Division of Ophthalmic and Ear, Nose and Throat Devices Office of Device Evaluation
Center for Devices and Radiological Health
Enclosure
{7}------------------------------------------------
#### SECTION 4.
# INDICATIONS FOR USE STATEMENT
#### 4. INDICATIONS FOR USE STATEMENT
510(k) Number (if known): K/22938
FORUM™M Device Name:
Indications for Use:
FORUM is a software system intended for use in storage, management, processing, and display of patient, diagnostic, video and image data and measurement from computerized diagnostic instruments or documentation systems through networks. It is intended to work with other FORUM applications.
FORUM is intended for use in review of patient, diagnostic and image data and measurement by trained healthcare professionals.
Prescription Use X (Part 21 CFR 801 Subpart D)
AND/OR
Over-The-Counter Use (21 CFR 801 Subpart C)
(PLEASE DO NOT WRITE BELOW THIS LINE-CONTINUE ON ANOTHER PAGE IF NEEDED)
Concurrence of CDRH, Office of Device Evaluation (ODE)
Eldridge Sim Off
Page of of __
(Division Sign-Off) (Division of Ophthalmic, Neurological and Ear, Nose and Throat Devices
K122938
510(k) Number
510(k) Number
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.