The FilmArray 2.0 is an automated in vitro diagnostic (IVD) device designed for use with FilmArray panels. The FilmArray 2.0 is intended for use in combination with assay specific reagent pouches to detect multiple nucleic acid targets contained in clinical specimens. The FilmArray 2.0 instrument interacts with the reagent pouch to both purify nucleic acids and amplify targeted nucleic acid sequences using nested multiplex PCR in a closed system. The resulting PCR products are evaluated using DNA melting analysis. The software automatically determines the results and provides a test report. The FilmArray 2.0 is composed of one to eight instruments connected to a computer running FilmArray 2.0 software, which controls the function of each instrument and collects, and stores data generated by each instrument.
Device Story
FilmArray 2.0 is an automated IVD system for nucleic acid detection; utilizes reagent pouches for sample purification and nested multiplex PCR amplification in a closed system. Input: clinical specimens; Output: DNA melt curve analysis results and test reports. System comprises 1-8 instruments connected to a single computer via Ethernet switch; includes barcode scanner and optional modular rack. Operated by laboratory personnel in clinical settings. Software controls instrument function, data collection, and analysis. System designed for higher throughput and reduced footprint compared to predicate. Healthcare providers use generated reports for clinical decision-making regarding patient infection status.
Clinical Evidence
Performance evaluated using three FDA-cleared panels (Respiratory, BCID, GI). Studies included clinical specimen comparison, low analyte (LoD) testing, and multi-instrument reproducibility across three sites. Results demonstrated equivalent performance between FilmArray 2.0 and the predicate device across all metrics. Data provided in concurrently submitted 510(k) notifications.
Technological Characteristics
Automated IVD instrument; nested multiplex PCR; DNA melting analysis. Components: pneumatic actuators, bead-beater, magnetic bead purification, Peltier thermocyclers, CMOS camera, hard-coated filters. Connectivity: Ethernet-based, multi-instrument (up to 8) to single computer. Software: automated data interpretation and report generation. Closed system.
Indications for Use
Indicated for use with FilmArray reagent panels to detect multiple nucleic acid targets in clinical specimens. Intended for prescription use in clinical settings.
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."
{0}
1
# 510(k) SUBSTANTIAL EQUIVALENCE DETERMINATION DECISION SUMMARY
A. 510(k) Number:
K143178
B. Purpose for Submission:
Premarket notification for the FilmArray 2.0 is intended for use with FDA cleared or approved assays which have been cleared or approved for use on the FilmArray 2.0.
C. Manufacturer and Instrument Name:
BioFire Diagnostics, LLC
The FilmArray 2.0 is composed of the FilmArray 2.0 instrument and FilmArray software.
D. Type of Test or Tests Performed:
The tests consist of multi-step chemical processes designed to isolate and detect nucleic acid targets using nested amplification followed by DNA melt curve analysis detection in an array format.
E. System Descriptions:
1. Device Description:
The multi-instrument FilmArray 2.0 is composed of a computer pre-installed with FilmArray Software, a computer stand and printer, a barcode scanner, an external Ethernet switch that allows up to eight instruments to connect to a single computer, and an optional modular rack system to stack multiple instruments. The modular rack system will hold the instruments at a 15° angle. The functional specifications of the individual FilmArray 2.0 instruments (including the steps in the testing process and the data interpretation) are unchanged with respect to the original FilmArray 2.0 instrument.
2. Principles of Operation:
The FilmArray 2.0 is an automated in vitro diagnostic (IVD) device designed to work with panel specific reagent pouches to detect multiple nucleic acid targets in clinical specimens. The FilmArray 2.0 instrument interacts with the reagent pouch to purify nucleic acids and amplify targeted nucleic acid sequences using nested multiplex PCR in a closed system. The resulting PCR products are evaluated using DNA melting analysis. The FilmArray Software automatically determines the results and provides a test report.
In order to support higher throughput testing the FilmArray 2.0 was developed to support
{1}
up to eight instruments connected to one computer and a holding rack. The FilmArray 2.0 was designed to reduce the system footprint, support increased through-put, and update data management capabilities.
3. Modes of Operation:
The instrument Dashboard serves as a home screen from which the operator can navigate to instrument Control for individual instruments. The instrument Dashboard is designed to display instrument details and information (e.g. status and availability) for up to eight instruments. The instrument Dashboard allows the operator to view the status of each instrument in the system, view the status of all testing runs (e.g., run details such as sample ID, operator, time remaining and estimated time of completion, and if the test report is available), and navigation to instrument Control. An instrument Information button is available on the dashboard that allows an operator to retrieve error messages and other information associated with an individual instrument.
4. Specimen Identification:
Once the pouch is inserted, the FilmArray Software prompts the operator to scan the pouch barcode (which contains the pouch identification information, including the pouch type and serial number), enter the sample ID, and enter the operator ID and password. When all required information has been entered, the user closes the FilmArray 2.0 instrument lid and clicks "Start Run"
5. Specimen Sampling and Handling:
See assay specific labeling for specimen sampling and handling recommendations.
6. Calibration:
The FilmArray 2.0 does not require reagent specific set-up, calibration, or cleaning procedures in order to perform testing with different reagent panels. The optics system contained in the FilmArray 2.0 instrument is aligned, focused, and calibrated at the manufacturer. Proper operation and calibration of instrument optics is monitored by automated on-board self-tests and pouch control reactions. The barcode reader can be calibrated if there is a functional error. Bar code calibration instructions are provided in the operator's manual.
7. Quality Control:
See assay specific labeling for quality control information.
8. Software:
FDA has reviewed applicant's Hazard Analysis and Software Development processes for this line of product types:
{2}
Yes ☐ X ☐ or No ☐
Level of Concern: Moderate
## Software Description:
The FilmArray 2.0 is controlled by Windows-based software running on a computer configured with a standard version of Microsoft Windows Operating system (Windows 7). The FilmArray Software interfaces with the operator to control the instrument, collect data, report test results, and save and retrieve test data from the database. In addition to the FilmArray Software, each reagent pouch requires a specific FilmArray Software pouch module. The pouch module interacts with the FilmArray Software and provides pouch-specific instructions, including the definition of a pouch, the information required to run a pouch on an instrument, analysis instructions used to interpret the data from a run and to display the results, and instructions for generating the test report. Pouch modules are developed and deployed independently of the core software. Each pouch module contains information necessary to perform a test with the corresponding test panel.
## Device Hazard Analysis:
Part of the software and firmware development process includes performing a risk analysis to identify risks, their possible causes, and appropriate controls. Risk Management of the FilmArray Software and Firmware followed the processes stated to comply with ISO 14971:2012, Medical devices – application of risk management to medical devices. In brief, risk management started by identifying the hazards associated with the use of the system. The identified hazards fell into four categories: false positive results, false negative results, assay reporting errors, and delayed test results. Risk scores were calculated as a function of severity and the likelihood of occurrence. After mitigation, all hazards associated with the FilmArray Software have the lowest Risk score as defined by the Firm.
## Software Requirements Specification:
Requirements for the FilmArray Software were derived from the system-level design inputs document that describes the instrument and software. The design inputs were converted into high-level software requirements that describe the overall function of the software.
After the high-level requirements were determined, detailed specifications, called subsystem requirements, were developed that describe the function of the software. Appropriate teams reviewed and approved the specification documents, and they were used to drive both the software development and testing processes.
Requirements for the FilmArray Firmware were also derived from the system-level design inputs document. The design inputs were converted into high-level instrument requirements that describe the overall function of the instrument. The instrument requirements then drove the detailed firmware specifications. The firmware was
3
{3}
developed to meet these specifications.
## Architecture Design Chart:
A high-level architecture design chart for the FilmArray Software was provided. Additional information about the architecture of the FilmArray Software, including state diagrams and flow charts were provided.
## Software Design Specification:
During software and firmware development, detailed development documents were written, formally reviewed, and approved by the project manager and technical leads. These development documents were the design specifications which drove the software and firmware development, dictated the behavior of the modules, and formed the basis of design verification. A complete list of software and firmware design specifications for the FilmArray Software was provided.
## Traceability Analysis:
The software traceability analysis was conducted according to procedures defined in the submitted Standard Operating Procedures documentation. FilmArray Software risk analysis links potential hazards to the software requirements that are designed to mitigate each of the identified hazards. A number of individual trace matrices are compiled into a master trace matrix linking each of the FilmArray software requirements to the verification test cases or the validation test cases.
Firmware traceability is conducted according to procedures defined internal to the Firm with each firmware requirement tracing to an associated verification test case.
## Software Development Environment:
The Software Development Life Cycle (SDLC) was a modified waterfall method with frequent specification modifications and review. Design inputs cascaded into high-level requirements, software specifications, design specifications, and test cases. However, the waterfall method was modified to allow for changes to requirements at any time before validation. When changes occurred, the process repeated to ensure documentation of dependent features was updated.
The FilmArray Software was written in an object-oriented style using .NET technology and the C# programming language. The software is based on the FilmArray shell application that uses the Composite Application Library from Microsoft to dynamically discover and configure loosely coupled modules at run time. The analysis software for FilmArray was written in MatLab.
Firmware development follows a V-model method with frequent reviews. system-level design inputs lead to high-level instrument requirements, firmware specifications, and verification test cases. Changes to requirements may occur at any time up to firmware verification.
4
{4}
5
Verification and Validation:
Verification of the FilmArray Software consisted of automated scripts and manual test cases designed to test requirements of the software. To verify software to instrument interactions, the automated test suite requires an instrument simulator. The simulator is a software program written to mimic the FilmArray 2.0 instrument. The simulator accepts instructions from the software and sends messages and data in return.
For requirements not easily tested through automated scripts, manual test cases were written, approved, and executed to verify the software. Both automated and manual test cases were used to ensure complete coverage of the software requirements.
The system level software validation was performed by laboratory personnel who execute formal written test cases that validate each of the high level requirements. This testing uses production pouches and instruments, and provides an independent software validation. In addition to the test cases, laboratory personnel assess whether the software meets personal usability criteria not captured in the specifications. A validation test report is created at the end of the testing phase. Because the firmware is used to perform this system level testing, the software validation also serves to validate the firmware.
Revision Level History:
There is one released version of the FilmArray software.
| Version
2.0.1014 | Build Date
March 25, 2014 | Release Number
DX-CO-018194 |
| --- | --- | --- |
Unresolved Anomalies:
{5}
All software defects were evaluated during software design reviews and tracked using unique identifiers. Four minor defects were reported which required no mitigation. One defect was reported as “the instrument lost power during a run, which resulted in the loss of that run. The user was able to run the pouch again because the pouch serial number was not in the database.” This hazard associated with this defect was mitigated by the adding specific instructions for pouch handling after loss of power during a run to the product labeling.
## F. Regulatory Information:
1. Regulation section:
21 CFR 862.2570 Instrumentation for clinical multiplex test systems
2. Classification:
Class II
3. Product code:
NSU
4. Panel:
Microbiology
## G. Intended Use:
1. Indication(s) for Use:
The FilmArray 2.0 is an automated in vitro diagnostic (IVD) device designed for use with FilmArray panels. The FilmArray 2.0 is intended for use in combination with assay specific reagent pouches to detect multiple nucleic acid targets contained in clinical specimens. The FilmArray 2.0 instrument interacts with the reagent pouch to both purify nucleic acids and amplify targeted nucleic acid sequences using nested multiplex PCR in a closed system. The resulting PCR products are evaluated using DNA melting analysis. The software automatically determines the results and provides a test report.
The FilmArray 2.0 is composed of one to eight instruments connected to a computer running FilmArray 2.0 software, which controls the function of each instrument and collects, analyzes, and stores data generated by each instrument.
Special Conditions for Use Statement(s):
For prescription use only
## H. Substantial Equivalence Information:
1. Predicate Device Name(s) and 510(k) numbers:
{6}
FilmArray K103175
2. Comparison with Predicate Device:
| Similarities | | |
| --- | --- | --- |
| Item | Current Device: FilmArray 2.0 | Predicate Device FilmArray (K103175) |
| Intended Use | The FilmArray 2.0 is an automated in vitro diagnostic (IVD) device designed for use with FDA cleared or approved IVD FilmArray panels. The FilmArray 2.0 is intended for use in combination with assay specific reagent pouches to detect multiple nucleic acid targets contained in clinical specimens. The FilmArray 2.0 instrument interacts with the reagent pouch to both purify nucleic acids and amplify targeted nucleic acid sequences using nested multiplex PCR in a closed system. The resulting PCR products are evaluated using DNA melting analysis. The software automatically determines the results and provides a test report.The FilmArray 2.0 is composed of one to eight instruments connected to a computer running FilmArray 2.0 software which controls the function of each instrument and collects, analyzes, and stores data generated by each instrument. | Same |
| Assays | For use with FDA cleared FilmArray panels | Same |
{7}
| Similarities | | |
| --- | --- | --- |
| Item | Current Device: FilmArray 2.0 | Predicate Device FilmArray (K103175) |
| | signal detection. | |
| Time to result | Approximately 1 hour per sample | Same |
| Technological Principles | Nested multiplex nucleic acid amplification (including reverse transcription as appropriate) followed by high-resolution melting analysis to confirm the identity of the amplified product. | Same |
| Required Accessory | FilmArray Reagent Pouch | Same |
| Sample Preparation Method | Minimal sample processing and hands-on time. | Same |
| Test Interpretation and Results Reporting | Automated results determination and report generation. User cannot access raw data. Report can be printed. | Same |
| User Complexity | Moderate | Same |
| Differences | | |
| --- | --- | --- |
| Item | Current Device: FilmArray 2.0 | Predicate Device: FilmArray (K103175) |
| Instrument Optics | Charge-coupled device (CCD) camera. Soft-coated filters. | Complimentary metal-oxide semiconductor (CMOS) camera Hard-coated filters. |
{8}
9
| Differences | | |
| --- | --- | --- |
| Item | Current Device: FilmArray 2.0 | Predicate Device: FilmArray (K103175) |
| Instrument – Software Communication | Communication travels via Firewire and USB cables/ports. | Communication travels via Ethernet cable/port.
Communication for multiple instruments mediated by a multi-port switch. |
| System configuration | Up to eight FilmArray 2.0 instruments to one computer with mouse, barcode scanner and pouch loading station.
Single-sample test capacity per instrument with random-access multi-sample test capacity per system.
Printer provided with the system.
Interlocking two-instrument racks available to stack instruments and reduce system footprint. (Optional)
Instrument held at 0° angle when no rack is used. instrument held at 15° angle on rack. | One FilmArray 2.0 instrument to one laptop computer with mouse, barcode scanner and pouch loading station.
Single-sample test capacity.
Printer optional.
Instrument held at 0° angle. |
I. Guidance Documents and Standards Referenced:
The FilmArray 2.0 instrument was certified by a third party to meet the following electrical standards:
- EN 61010-1:2001, Safety requirements for electrical equipment for measurement, control, and laboratory use.
- EN 61010-2-101:2002, Safety requirements for electrical equipment for measurement, control and laboratory use – Particular requirements for in vitro diagnostic (IVD) medical equipment
{9}
- EN 61326-1:2006, Electrical Equipment for Measurement, Control and Laboratory Use – EMC Requirements: General Requirements
- EN 61326-2-6:2006, Electrical Equipment for Measurement, Control and Laboratory Use – EMC Requirements: Particular Requirements IVD Medical Equipment
## J. Performance Characteristics:
### 1. Analytical Performance:
a. Accuracy:
Analytical accuracy was assessed during the clearance of the K103175 and will be addressed for each assay to be run on this system.
b. Precision/
Reproducibility:
See K143171
c. Linearity:
Not applicable
d. Carryover:
See K143171 and K103175
e. Interfering Substances:
The effect of interfering substances was assessed during the clearance of the K103175 and will be addressed for each assay to be run on this system.
### 2. Other Supportive Instrument Performance Data Not Covered Above:
A method comparison study using archived clinical and contrived samples was performed using the FilmArray 2.0 during the clearance of K143171.
## K. Proposed Labeling:
The labeling is sufficient and it satisfies the requirements of 21 CFR Part 809.10.
## L. Conclusion:
1. The submitted information in this premarket notification is complete and supports a substantial equivalence decision.
10
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.