AFFYMETRIX GENECHIP MICROARRAY INSTRUMENTATION SYSTEM
DEN040012 · Affymetrix, Inc. · NSU · Dec 23, 2004 · Clinical Chemistry
Device Facts
Record ID
DEN040012
Device Name
AFFYMETRIX GENECHIP MICROARRAY INSTRUMENTATION SYSTEM
Applicant
Affymetrix, Inc.
Product Code
NSU · Clinical Chemistry
Decision Date
Dec 23, 2004
Decision
DENG
Submission Type
Post-NSE
Regulation
21 CFR 862.2570
Device Class
Class 2
Indications for Use
The Affymetrix GeneChip® Microarray Instrumentation System consisting of GeneChip® 3000Dx scanner with autoloader, FS450Dx fluidics station and GCOSDx software is intended to measure fluorescence signals of labeled DNA target hybridized to GeneChip® arrays.
Device Story
System processes GeneChip microarrays; includes FS450Dx Fluidics Station, GCS3000Dx Scanner, and GCOSDx software. Fluidics Station performs hybridization, washing, and staining using automated scripts. Scanner uses wide-field, epifluorescent, confocal laser microscopy to image chips. Software controls instruments, captures images, performs grid alignment, and computes intensity values for probe cells. Output is .cel file containing intensity data, passed to assay-specific software for clinical result reporting. Used in clinical laboratory settings by trained operators. System automates sample handling via autoloader. Benefits include standardized, reproducible measurement of fluorescence signals across multiple analytes to aid in diagnosis.
Clinical Evidence
Bench testing only. Evaluated system reproducibility, uniformity, and scanner performance using synthetic control oligonucleotides. Study design: fully nested, replicated full factorial (3 fluidics stations, 3 scanners, 36 arrays). Primary metrics: discrimination score (PM vs MM), intra/inter-chip, intra/inter-scanner, and intra/inter-fluidics station CVs. Results: global uniformity <10% CV, local uniformity <1% CV. Between-scan CVs 0.3-5.2%. ANOVA showed no statistically significant variability (p>0.05) introduced by system components. Feature displacement <2.5 microns.
Technological Characteristics
System includes FS450Dx fluidics station (pump, valve, thermo-electric system), GCS3000Dx confocal scanning laser microscope, and autoloader. Connectivity: workstation-based. Software: GCOSDx (C++). Operates on Windows 2000/XP. Data output: .dat (image) and .cel (intensity) files. No user calibration required.
Indications for Use
Indicated for use with separately cleared GeneChip microarray assays to measure fluorescence signals of labeled DNA targets hybridized to arrays.
Regulatory Classification
Identification
Instrumentation for clinical multiplex test systems is a device intended to measure and sort multiple signals generated by an assay from a clinical sample. This instrumentation is used with a specific assay to measure multiple similar analytes that establish a single indicator to aid in diagnosis. Such instrumentation may be compatible with more than one specific assay. The device includes a signal reader unit, and may also integrate reagent handling, hybridization, washing, dedicated instrument control, and other hardware components, as well as raw data storage mechanisms, data acquisition software, and software to process detected signals.
Special Controls
*Classification.* Class II (special controls). The device is exempt from the premarket notification procedures in subpart E of part 807 of this chapter subject to the limitations in § 862.9. The special control is FDA's guidance document entitled “Class II Special Controls Guidance Document: Instrumentation for Clinical Multiplex Test Systems.” See § 862.1(d) for the availability of this guidance document.
The special control is FDA's guidance document entitled "Class II Special Controls Guidance Document: Instrumentation for Clinical Multiplex Test Systems."
Submission Summary (Full Text)
{0}------------------------------------------------
## 510(k) SUBSTANTIAL EQUIVALENCE DETERMINATION DECISION SUMMARY INSTRUMENT ONLY TEMPLATE
## A. 510(k) Number:
k042279
## B. Purpose for Submission:
Clearance of new device
### C. Manufacturer and Instrument Name:
Affymetrix GeneChip Microarray Instrumentation System
### D. Type of Test or Tests Performed:
Hybridization, washing, scanning, and data analysis of GeneChip microarrays
### E. System Descriptions:
### 1. Device Description:
The Affymetrix GeneChip Microarray Instrumentation System is designed to work with microarrays based on Affymetrix GeneChip ® technology.
## FS450Dx Fluidics Station
The FS450Dx (Fluidics Station) is an instrument consisting of four modules installed in a single Station or housing. Each module holds a single GeneChip microarray and performs the functions required for hybridization, washing, and staining of that array.
Up to 8 stations communicate to a workstation.
Each module contains controls the addition of target and staining fluids to the array cartridge and subsequent washing of the array. The module contains a pump, valve, thermo-electric system, and LCD that are controlled by scripts selected by the system operator and automatically downloaded to each module, then stored in the module's electronic memory.
## GCS3000Dx Scanner
The GCC3000Dx Scanner is a wide-field, epifluorescent, confocal, scanning laser microscope which scans the chip after the staining process performed by the Fluidics Station. Array cartridges are loaded into the scanner by an automatic handler (the Autoloader) prior to scanning, and returned to the handler after scanning is complete.
{1}------------------------------------------------
# GCOSDx Software
The GeneChip® Operating Software (GCOSDx) provides the interface between the user and instrument systems. It is the software that provides instrument control and the application for processing arrays and data collection. Upon completion of scanning of the array, data is passed through GCOSDx to the assay specific software component that contains the algorithms and reporting functions to produce a clinical result.
- 2. Principles of Operation:
- a. Device Features Controlled by Software
- i. The GeneChip® Operating Software (GCOSDx) provides the interface between the user and the instruments. GCOSDx controls the FS450Dx, GCS3000Dx and the AutoLoaderDx. GCOSDx may also be used to monitor the operations being performed by each instrument.
- ii. GCOSDx controls the fluidics station using fluidics scripts specific to the assay being performed. Fluidics scripts are written to a directory specified during GCOSDx installation.
- iii. GCOSDx aids and controls scanner movement and image capture including grid alignment. GCOSDx displays a picture of the scan image in an image window on the computer workstation. The software represents the fluorescence intensity values from each pixel on the array in a grayscale or pseudocolor mode. This image is saved as a ".dat" file format.
- iv. GCOSDx then uses an alignment algorithm to superimpose a grid on the image to delineate probe cells. The alignment algorithm uses a checkerboard image of control probes, located at the corners of the probe array to superimpose the grid on the scanned image. GCOSDx generates cell intensity data from the image data. The cell analysis algorithm analyzes the image data and computes a single intensity value for each probe cell on the array. This data is saved as a ".cel" file. It is the ".cel" file that is handed to the assay specific software for final data analysis and result reporting.
- b. Operational Environment (Off-The-Shelf Software)
GCOSDx is programmed in C++. GCOSDx functions on MicroSoft® Windows® 2000 SP3 or SP4 Operating System. The work stations also include Internet Explorer 6.0, Office XP and MDAC 2.7 SP1. The operating system will be moved to MicroSoft® XP in the near future. Prior to this shift. the appropriate validations will be performed. Dell workstations included with the system must have 750 MHz to 3.0 GHz Processor speed as well as 256 Mbyte to 1 Gbyte Memory and a 10 Gbyte to 80 Gbyte Hard Drive.
- 3. Modes of Operation:
batch - the scanner automatically loads and unloads chips from the autoloader
{2}------------------------------------------------
## 4. Specimen Identification:
The operator enters patients ID information in tied to a barcode on the chip. The barcode is scanned at the level of the fluidics station and the scanner.
- 5. Specimen Sampling and Handling:
Specimens are processed according to assay instructions. Reagents specific to each assay and fluidics protocol are manually loaded onto the fluidics station.
- 6. Calibration:
Installation and calibration are performed by the sponsor. No user calibration required.
- 7. Quality Control:
Quality control is addressed for each specific assay to be run on the system (separately cleared)
- 8. Software:
FDA has reviewed applicant's Hazard Analysis and Software Development processes for this line of product types:
Yes__3_____ or No_____________________________________________________________________________________________________________________________________________________________
# F. Regulatory Information:
- 1. Regulation section:
None
- 2. Classification:
Class III
- 3 Product code:
NSU, Instrumentation for Clinical Multiplex Test Systems
- 4. Panel:
Clinical Chemistry (75)
{3}------------------------------------------------
# G. Intended Use:
- 1. Indication(s) for Use:
The Affymetrix GeneChip® Microarray Instrumentation System consisting of GeneChip® 3000Dx scanner with autoloader, FS450Dx fluidics station and GCOSDx software is intended to measure fluorescence signals of labeled DNA target hybridized to GeneChip® arrays.
- 2. Special Conditions for Use Statement(s):
For use with separately cleared GeneChip microarray assays
# H. Substantial Equivalence Information:
- 1. Predicate Device Name(s) and 510(k) numbers:
This device has no predicate device.
- 2. Comparison with Predicate Device:
This device has no predicate device.
# I. Special Control/Guidance Document Referenced (if applicable):
FDA Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices
# J. Performance Characteristics:
- 1. Analytical Performance:
- a. Accuracy:
Not applicable - accuracy for each assay to be run on this system will be assessed during the clearance of the assay.
- b. Precision/Reproducibility:
For the reproducibility study, intensity readings generated by Scanner 3000Dx were not changed, manipulated or revised after scanning was completed. Raw .CEL file data was used for the analysis of uniformity, and calculation of intra- and inter-chip, intra- and inter-scanner and intra- and inter-fluidics and fluidics port reproducibility (CV, correlation coefficients). ANOVA analysis to establish whether there are any random effects of FS. FS port or scanner was performed post-data analysis. No arrays were scaled to a fixed value nor normalized since the study was designed to observe variability
{4}------------------------------------------------
in all system components with raw data. (Scaling and normalization are tools for controlling differences between arrays and scanners.)
## Array design:
Two different array types were used in order to assess instrumentation performance:
- The first array was used to assess scanner performance alone (without the . hybridization step). The 32x32 cell array was designed to have photobleaching stability and can be scanned over 100 times. A single array was scanned at the study start and in-between every 2 scans, on each of 3 scanners tested, leading to total of 12 scans (4 scans per scanner). This experiment was used to demonstrate uniformity of the scanner performance by calculating CV for global (<10% CV) and local uniformity (<1% CV; each 400 uM2 gridded cell with surrounding 4 cells; averaged over alternating cells of the 32x32 array).
- The second array was used to assess overall system performance using a single chip lot.
Probes: Control probes - random generated synthetic sequence. On the array this probes is located in a specific pattern across the array. Chip probe length of varies from 16-25mer. Probes were used for grid alignment, and to evaluate variability introduced by hybridization. Discrimination controls - 4 control probe sets; 30 tiled Perfect Match (PM) / Mismatch (MM) probe pairs for each. Probes on array are
complementary to one of four 5'-biotinylated oligonucleotides. These probes were used to measure discrimination of PM from MM.
# Sample type:
Target - Hybridization Cocktail: two target sets (for control and discrimination, respectively) at concentrations 0.1, 0.5, 1 and 3nM were pooled and spiked into hybridization buffer.
Single lots of buffer, oligonucleotides, and reagents were used.
## Study design:
Goal: to generate reproducibility data for consistent system performance independent of assav type.
Primary metric - discrimination score (PM vs. MM).
Design: components-of-variance (random effects) replicated full factorial fully nested. One target aliquot was hybridized to 12 chips on 3 Fluidics Stations (12 ports) - each array was scanned in duplicate on each of 3 scanners 3000Dx (6 scans/chip), resulting in 72 scans of the same test material.
Methods:
Hybridization - 30 minutes: all data collection within 1 week
Replicate samples processed sequentially (3 replicates/aliquots)
2 scans per array - 2 separate .DAT files
ANOVA (Analysis of Variance) analysis
{5}------------------------------------------------
Data generated:
- Feature position check -The scanner introduced no more than 2.5 microns of feature displacement.
- Intra-chip local and global uniformity data (CV of fluorescent features on the array)
The intensities of the features which were tiled on the array at different positions were measured. There were 643 identical features on the array that were distributed across the array. The signal %CV for all of the features for the control oligonucleotide demonstrated that the features were hybridized uniformly on the array. The overall average of CVs for 72 images was 8.0%. Since the variability of signal for the hybridized control oligonucleotide was measured, the %CV reflects the cumulative variability of all system components, including user handling. Hybridization uniformity was consistent across 36 arrays.
### Between-scan %CVs
Percent CVs of bright feature signal over time, of the array, for each of the three scanners were provided. Data from each scanner were derived from the four scans of the same array during the study. The between-scan %CV range for all bright features was 4.2-5.2% for scanner 1, 3.2-4.0% for scanner 2, and 0.3-1.9% for scanner 3.
### Between-scanner %CVs
Percent CVs of bright feature signals over time, of the same array, across the three scanners are shown below. Data from all three scanners were derived from the same time point of the same array during the study. The %CV ranges for all bright feature signals across the scanners at the different time points were as follows:
| Time point | % CV Range |
|------------|------------|
| 1 | 4.4 - 6.8 |
| 2 | 5.0 - 7.4 |
| 3 | 5.7 - 9.2 |
| 4 | 8.9 - 10.9 |
- Discrimination score: normalized difference between intensity from targets bound to PM and ones bound to MM. Intrinsic binding affinities (e.g. GC content function) are designed to be factored out: the discrimination score is a measure of the amount and quality of information from a probe pair, and is background corrected. Results: 36 average discrimination scores from all arrays fell within 95% confidence interval (average = ave of 2 scanned images/array x 36 arrays).
- ANOVA - looking at random effects of FS, FS port and scanner - P-values >0.05 => no statistically significant variability introduced.
- Chip-to-chip % CV :
The average signal of the duplicate scans for 36 arrays for every feature from the
{6}------------------------------------------------
control oligonucleotides was used to determine their variation, independently. Figures 1 and 2 below demonstrate the variation of the perfect match and mismatch features, respectively. One perfect match feature had a signal CV > 13% while no mismatch features had signal variation >15%.
- c. Linearity:
Not applicable - linearity for each assay to be run on this system will be assessed during the clearance of the assay
- d. Carryover:
Not applicable - carryover for each assay to be run on this system will be assessed during the clearance of the assay
- Interfering Substances: e.
Not applicable - interferences for each assay to be run on this system will be evaluated during the clearance of the assay
- 2. Other Supportive Instrument Performance Data Not Covered Above:
# K. Proposed Labeling:
The labeling is sufficient and it satisfies the requirements of 21 CFR Part 809.10.
# L. Conclusion:
This device has no predicate device. However, the submitted information in this premarket notification is complete, and this device would be a good candidate for de novo classification and clearance.
# Note: This device was declared NSE for lack of a predicate. On November 3, 2004, the sponsor petitioned to have this device reclassified into Class II via the de novo classification process. FDA has reviewed the sponsor's petition and has proposed the following classification:
& 862.2570 Instrumentation for Clinical Multiplex Test Systems.
(a) Identification. Instrumentation for clinical multiplex test systems is a device intended to measure and sort multiple signals generated by an assay from a clinical sample. This instrumentation is used with a specific assay to measure multiple similar analytes that establish a single indicator to aid in diagnosis. Such instrumentation may be compatible with more than one specific assay. The device includes a signal reader unit, and may also integrate reagent handling, hybridization, washing, dedicated instrument control, and other
{7}------------------------------------------------
hardware components, as well as raw data storage mechanisms, data acquisition software, and software to process detected signals.
(b) Classification. Class II (special controls). The special control is FDA's guidance document entitled "Class II Special Controls Guidance Document: Instrumentation for Clinical Multiplex Test Systems." See § 862.1(d) for the availability of this guidance document.
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.