BD Phoenix Automated Microbiology System - GN Ceftazidime/avibactam (0.25/4- 32/4ug/mL)
K163637 · Becton Dickinson & Company · LON · Mar 21, 2017 · Microbiology
Device Facts
Record ID
K163637
Device Name
BD Phoenix Automated Microbiology System - GN Ceftazidime/avibactam (0.25/4- 32/4ug/mL)
Applicant
Becton Dickinson & Company
Product Code
LON · Microbiology
Decision Date
Mar 21, 2017
Decision
SESE
Submission Type
Traditional
Regulation
21 CFR 866.1645
Device Class
Class 2
Indications for Use
The BD Phoenix Automated Microbiology System is intended for the in vitro rapid identification (ID) and quantitative determination of antimicrobial susceptibility by minimal inhibitory concentration (MIC) of Gram Negative aerobic and facultative anaerobic bacteria belonging to the family Enterobacteriaceae and non-Enterobacteriaceae.
Device Story
System performs automated antimicrobial susceptibility testing (AST) for Gram-negative bacteria. Input: pure bacterial culture suspension in AST broth (cation-adjusted Mueller-Hinton with 0.010% Tween 80) standardized to 0.5 McFarland. Process: broth microdilution in molded polystyrene trays containing dried antimicrobial agents and redox indicator; continuous incubation at 35°C; instrument monitors growth via redox indicator color change (blue to pink) and turbidity every 20 minutes. Output: MIC values and category interpretations (S, I, R). Used in clinical microbiology laboratories; operated by trained technicians. Software-driven 'EXPERT' system interprets reactions based on organism ID and CLSI rules. Benefits: rapid, standardized, automated susceptibility determination to guide antibiotic therapy.
Clinical Evidence
Performance evaluated using clinical, stock, and challenge isolates across multiple US sites. Comparison against CLSI reference broth microdilution method. Results: 1348 isolates tested; Essential Agreement (EA) 97.8%; Category Agreement (CA) 99.3%. Reproducibility study across three sites showed >95% agreement (+/- 1 dilution).
Technological Characteristics
Broth microdilution method using molded polystyrene trays with 136 wells. Redox indicator (colorimetric oxidation-reduction) for growth detection. Energy source: electrical (instrument). Connectivity: networked (BD Phoenix instrument). Software: V5.83A or higher. Inoculum preparation: PhoenixSpec nephelometer or BD Phoenix AP instrument. Sterilization: not specified.
Indications for Use
Indicated for in vitro quantitative determination of antimicrobial susceptibility (MIC) of Gram-negative aerobic and facultative anaerobic bacteria (Enterobacteriaceae and Non-Enterobacteriaceae) and Gram-positive bacteria (Staphylococcus, Enterococcus, Streptococcus) from pure culture. Ceftazidime/avibactam is indicated for Citrobacter freundii complex, Citrobacter koseri, Escherichia coli, Enterobacter aerogenes, Enterobacter cloacae, Klebsiella pneumoniae, Klebsiella oxytoca, Proteus spp., and Pseudomonas aeruginosa.
Regulatory Classification
Identification
A fully automated short-term incubation cycle antimicrobial susceptibility system is a device that incorporates concentrations of antimicrobial agents into a system for the purpose of determining in vitro susceptibility of bacterial pathogens isolated from clinical specimens. Test results obtained from short-term (less than 16 hours) incubation are used to determine the antimicrobial agent of choice to treat bacterial diseases.
Special Controls
*Classification.* Class II (special controls). The special control for this device is FDA's guidance document entitled “Class II Special Controls Guidance Document: Antimicrobial Susceptibility Test (AST) Systems; Guidance for Industry and FDA.”
{0}
1
# 510(k) SUBSTANTIAL EQUIVALENCE DETERMINATION DECISION SUMMARY ASSAY ONLY TEMPLATE
A. 510(k) Number:
K163637
B. Purpose for Submission:
Addition of ceftazidime/avibactam to the BD Phoenix Gram Negative ID/AST and AST only Phoenix panels
C. Measurand:
Ceftazidime/avibactam 0.25/4 – 32/4 µg/mL
D. Type of Test:
Antimicrobial Susceptibility Test (Quantitative) colorimetric, oxidation-reduction, growth based
E. Applicant:
Becton, Dickinson and Company
F. Proprietary and Established Names:
BD Phoenix™ Automated Microbiology System- GN Ceftazidime/avibactam (0.25/4-32/4µg/mL)
G. Regulatory Information:
1. Regulation section:
21 CFR 866.1645 – Short-Term Antimicrobial Susceptibility Test System
2. Classification:
Class II
3. Product code:
LON – System, Test, Automated, Antimicrobial Susceptibility, Short Incubation
{1}
4. Panel:
83 Microbiology
H. Intended Use:
1. Intended use(s):
The BD Phoenix Automated Microbiology System is intended for the in vitro rapid identification (ID) and quantitative determination of antimicrobial susceptibility by minimal inhibitory concentration (MIC) of Gram Negative aerobic and facultative anaerobic bacteria belonging to the family Enterobacteriaceae and non-Enterobacteriaceae.
2. Indication(s) for use:
The BD Phoenix™ Automated Microbiology System is intended for in vitro quantitative determination of antimicrobial susceptibility by minimal inhibitory concentration (MIC) of most Gram-negative aerobic and facultative anaerobic bacterial isolates from pure culture for Enterobacteriaceae and Non-Enterobacteriaceae and most Gram-positive bacteria isolates from pure culture belonging to the genera Staphylococcus, Enterococcus and Streptococcus.
Ceftazidime/avibactam has been shown to be active in vitro against most strains of microorganisms listed below, as described in the FDA-approved package inserts for this antimicrobial agent.
Active in vitro and in Clinical Infections Against:
- Citrobacter freundii complex
- Citrobacter koseri
- Escherichia coli
- Enterobacter aerogenes
- Enterobacter cloacae
- Klebsiella pneumoniae
- Klebsiella oxytoca
- Proteus spp.
- Pseudomonas aeruginosa
Active in vitro but clinical significance is unknown:
- Morganella morganii
- Providencia stuartii
- Serratia marcescens
2
{2}
3
3. Special conditions for use statement(s):
For prescription use only
Limitations:
- The ability of the Phoenix System to detect resistance in the following combination(s) is unknown because a sufficient number of resistant strains were not encountered at the time of comparative clinical testing:
Ceftazidime/avibactam
Isolates other than Klebsiella pneumoniae and Pseudomonas aeruginosa
- Ceftazidime/avibactam: Providencia stuartii - Due to the lack of an intermediate breakpoint, three out of four major errors which occurred for P. stuartii were within essential agreement when compared to the reference method. The adjusted error rate was 3.4%. Testing should be repeated using an alternative testing/reference method prior to reporting results for the drug with Providencia stuartii when the Phoenix MIC is 16/4 µg/mL.
- Enzyme group characterization was not available at the time of comparative testing, and therefore the performance of the BD Phoenix ceftazidime/avibactam is unknown for Pseudomonas aeruginosa in the presence AmpC, or lacking outer membrane porin (OprD).
4. Special instrument requirements:
BD Phoenix Instrument and software (V5.83A or higher)
BD PhoenixSpec Nephelometer
BD Phoenix AP instrument
I. Device Description:
This submission is for a single drug in the gram negative ID/AST or AST only panel. The ID System was not reviewed.
The Phoenix AST method is a broth based microdilution test. The Phoenix panel is a sealed and self-inoculating molded polystyrene tray, with 136 micro-wells containing dried reagents. The ID/AST combination panel includes an ID side (51 wells) with dried substrates for bacterial identification and an AST side (85 wells). The AST panel contains a wide range of two-fold doubling dilution concentrations of antimicrobial agents and growth and fluorescent controls at appropriate well locations. The AST panel does not include wells for isolate identification.
The Phoenix System utilizes a redox indicator for the detection of organism growth in the presence of an antimicrobial agent. The organism to be tested must be a pure culture and be preliminarily identified as gram positive or gram negative. Colonies are then
{3}
suspended in ID broth, and equated to a 0.5 McFarland suspension using a nephelometer device. A further dilution is made into AST broth (a cation-adjusted formulation of Mueller-Hinton broth containing 0.010% Tween 80), to which the redox-buffered oxidation-reduction AST indicator solution is added producing a blue color in the wells. The concentration of organisms in the final AST broth suspension is approximately 5 X 10⁵ CFU/mL.
The Phoenix AST Broth is poured into the inoculation port of the AST panel and the inoculum flows into the panel, filling panel wells. Polyethylene caps are applied to seal the inoculation ports. An air admittance port is located in the panel lid to ensure adequate oxygen tension in the panel for the duration of the test. Inoculated panels are barcode scanned and loaded into the BD Phoenix Automated Microbiology System instrument where panels are continuously incubated at 35°C ± 1°C.
Continuous measurements of changes to the indicator as well as bacterial turbidity are used in the determination of bacterial growth. The instrument takes readings every 20 minutes. Organisms growing in the presence of a given antimicrobial agent reduce the indicator (changing it to a pink color). This signals organism growth and resistance to that antimicrobial agent. Organisms killed or inhibited by the antimicrobial agent do not cause reduction of the indicator and therefore do not produce a color change. The Phoenix instrument reads and records the results of the antimicrobial tests contained in the panel and interprets the reactions (based on the organism identification) to give a minimal inhibitory concentration (MIC) value and category interpretations (susceptible, intermediate, resistant or not susceptible). AST results are available within 4 to 16 hours. This is an autoread result; no manual readings are possible with this system.
Additional comments concerning specific organism/antimicrobial combinations is provided from the software-driven "EXPERT" system, using rules derived from CLSI documentation.
## J. Substantial Equivalence Information:
1. Predicate device name(s):
VITEK 2 Gram Negative Doxycycline
2. Predicate 510(k) number(s):
K121546
3. Comparison with predicate:
{4}
Table 1: Similarities and Differences of the BD Phoenix Ceftazidime/avibactam and the Predicate
| Similarities | | |
| --- | --- | --- |
| Item | Device BD Phoenix Automated Microbiology System (Ceftazidime/avibactam) | Predicate VITEK 2 Gram Negative Doxycycline (K121546) |
| Intended Use | Determination of in vitro antimicrobial susceptibility testing of aerobic and facultative anaerobic Gram-negative and Gram-positive bacteria | Same |
| Source of Microorganisms for Testing | Bacterial colonies isolated from culture | Same |
| Incubation Time | Short-term (<16 hours) | Same |
| Results | MIC and interpretive criteria (i.e., susceptible, intermediate, resistant and non-susceptible) | Same |
| Technology | Automated growth-based detection | Same |
| Differences | | |
| MIC Results Achieved | Antimicrobials in serial doubling dilutions | Computer assisted extrapolation of doubling dilutions |
| Technology | Automated growth detection enhanced by use of a redox indicator (colorimetric oxidation-reduction) | Automated growth detection using an attenuation of light measured by an optical scanner |
| Antimicrobial | Ceftazidime/avibactam | Doxycycline |
# K. Standard/Guidance Document Referenced (if applicable):
- CLSI M7-A10 "Methods for Dilution Antimicrobial Susceptibility Tests for Bacteria that Grow Aerobically"
- CLSI M100-S26 "Performance Standards for Antimicrobial Susceptibility Testing"
- Class II Special Controls Guidance Document: Antimicrobial Susceptibility Test Systems; Guidance for Industry and FDA
{5}
# L. Test Principle:
The BD Phoenix Automated Microbiology System is a broth based microdilution method that utilizes a redox indicator (colorimetric oxidation-reduction) to enhance detection of organism growth. The MIC is determined by comparing growth in wells containing serial two-fold dilutions of an antibiotic to the growth in "growth control wells" that contain no antibiotic.
# M. Performance Characteristics (if/when applicable):
# 1. Analytical performance:
# a. Precision/Reproducibility:
Reproducibility testing was conducted at three clinical trial sites. Testing was performed using inocula prepared manually using the PhoenixSpec nephelometer and the automated BD Phoenix AP instrument. The mode MIC value was determined and the reproducibility was calculated based on MIC values falling within $\pm 1$ dilution of the mode MIC value.
Fourteen organisms with on-scale ceftazidime/avibactam modal MIC values were provided to the testing sites by BD with isolate identification and expected MIC result blinded to the testers. Isolates were tested in triplicate on three separate days.
14 isolates x 3 replicates x 3 sites x 3 days= 378 data points
Results of the inter-site and intra-site reproducibility studies were acceptable and demonstrated best case and worst case results of greater than $95\%$ . There were no off-scale MIC results. A summary of the reproducibility study performance is shown in Table 2 below.
Table 2: Summary of Reproducibility Studies
| BD Phoenix Instrument Platform | Inoculation Method | Reproducibility |
| --- | --- | --- |
| BD Phoenix | Phoenix AP Instrument | 97.9% (370/378) |
| | Manual PhoenixSpec Nephelometer | 99.2% (375/378) |
# b. Linearity/assay reportable range:
Not applicable
# c. Traceability, Stability, Expected values (controls, calibrators, or methods):
Testing of the FDA and CLSI recommended quality control (QC) strains, $E.$ coli
{6}
ATCC 25922, E. coli ATCC 35218, K. pneumoniae ATCC 700603, and P. aeruginosa ATCC 27853 were performed each day of the challenge and clinical study testing with the reference method and with the BD Phoenix Systems. The inocula were standardized using both the Phoenix AP instrument and PhoenixSpec Nephelometer (manual). A sufficient number of tests were performed and all quality control results for the BD Phoenix fell within the acceptable ranges as per the FDA drug label, demonstrating that the BD Phoenix System can consistently produce quality control results in the recommended range for ceftazidime/avibactam. Results demonstrate that acceptable results were achieved $>95\%$ of the time by both Phoenix AP and manual inoculum preparation methods as shown in Table 3 below.
Table 3: Summary of Quality Control Results
| ORGANISM | conc.a(μg/mL) | Reference | Inoculum Preparation | |
| --- | --- | --- | --- | --- |
| | | | Manual (PhoenixSpec) | Phoenix AP |
| P. aeruginosaATCC 27853Expected Range:0.5/4 - 4/4μg/mL | ≤0.25 | | | |
| | 0.5 | | | |
| | 1 | 75 | | |
| | 2 | 55 | 134 | 82 |
| | 4 | 1 | 2 | |
| | 8 | | | |
| | 16 | | | |
| | 32 | | | |
| | >32 | | | |
| | | | | |
| E. coliATCC 25922Expected Range:0.06/4 - 0.5/4μg/mL(Phoenix:≤0.25/4- 0.5/4μg/mL) | ≤0.25c | 130 | 127 | 74 |
| | 0.5 | | 7 | 11 |
| | 1 | | | |
| | 2 | | | |
| | 4 | | | |
| | 8 | | | |
| | 16 | | | |
| | 32 | | | |
| | >32 | | 1 | |
| | | | | |
| E. coliATCC 35218Expected Range:0.03/4 - 0.12/4μg/mL(Phoenix:≤0.25/4μg/mL) | ≤0.25c | 130 | 133 | 81 |
| | 0.5 | | 1 | |
| | 1 | 1 | | |
| | 2 | | | |
| | 4 | | | |
| | 8 | | | |
| | 16 | | | |
| | 32 | | | |
| | >32 | | | |
{7}
Table 3: Summary of Quality Control Results (continued)
| ORGANISM | conc.a(μg/mL) | Reference | Inoculum Preparation | |
| --- | --- | --- | --- | --- |
| | | | Manual (PhoenixSpec) | Phoenix AP |
| | | | | |
| K. pneumoniaeATCC 700603bExpected Range:0.25/4 - 2/4 μg/mL(Phoenix:≤0.25/4- 2/4μg/mL) | ≤0.25c | 3 | 1 | |
| | 0.5 | 118 | 56 | 23 |
| | 1 | 8 | 75 | 29 |
| | 2 | 1 | | |
| | 4 | | | |
| | 8 | | | |
| | 16 | | 1 | |
| | 32 | | | |
| | >32 | | | |
a MIC for ceftazidime in the presence of a fixed concentration of $4\mu \mathrm{g / mL}$ of avibactam.
b K. pneumoniae ATCC 700603 should be tested against ceftazidime and avibactam and ceftazidime alone to confirm the activity of avibactam in the combination and to ensure that the plasmid encoding the beta-lactamase has not been lost in this strain. The acceptable range for ceftazidime alone is greater than $16~\mu \mathrm{g / mL}$
c The lowest dilution of the BD Phoenix Automated Microbiology System ceftazidime/avibactam MIC range is $\leq 0.25\mu \mathrm{g / mL}$ . Obtaining this value was considered as an indicator that the quality control test results were acceptable.
The expected range of Pseudomonas aeruginosa ATCC 27853 is $0.5/4 - 4/4\mu \mathrm{g} / \mathrm{mL}$ . All $P_{\cdot}$ aeruginosa results were on-scale and within the MIC reporting range of Phoenix ceftazidime/avibactam. However, the Phoenix MIC reporting range is $0.25/4$ to $32/4\mu \mathrm{g} / \mathrm{mL}$ and does not provide results lower than $0.25/4\mu \mathrm{g} / \mathrm{mL}$ to cover the expected range of $E.$ coli ATCC 35218 ( $0.03/4 - 0.12/4$ ), the lower end of the expected ranges for $E.$ coli ATCC 25922 ( $0.06/4$ ), and $K.$ pneumoniae ATCC 700603 ( $0.25/4$ ). A MIC value of $\leq 0.25/4\mu \mathrm{g} / \mathrm{mL}$ indicated that the results for these three QC organisms were acceptable.
The footnote below is included in Table 1, Quality Control Organisms and Expected Results of the BD Phoenix ceftazidime/avibactam package insert.
- "The lowest dilution of the BD Phoenix Automated Microbiology System ceftazidime/avibactam MIC range is $\leq 0.25 / 4\mu \mathrm{g} / \mathrm{mL}$ . Obtaining this value was considered as an indicator that the quality control test results were acceptable."
In addition, $K.$ pneumoniae ATCC 700603 is recommended to test against ceftazidime alone to ensure the presence of the plasmid encoding beta-lactamase when testing this beta-lactam/beta-lactamase inhibitor combination, ceftazidime/avibactam. The acceptable result for ceftazidime alone is greater than $16\mu \mathrm{g / mL}$ . The footnote below is included in Table 1, Quality Control Organisms and Expected Results of the BD Phoenix ceftazidime/avibactam package insert.
{8}
- “K. pneumoniae ATCC 700603 should be tested against ceftazidime and avibactam and ceftazidime alone to confirm the activity of avibactam in the combination and to ensure that the plasmid encoding the beta-lactamase has not been lost in this strain. The acceptable range for ceftazidime alone is greater than 16 µg/mL.”
Growth Rate: Seven isolates failed to grow during the clinical study. The overall growth rate during the clinical studies was 99.5%.
Purity Check Plates: Purity check plates were inoculated from the standardized organism suspensions for both the Phoenix and reference methods. Any isolate that showed mixed growth on the purity check plate was considered noncompliant and not included in result analysis.
Inoculum Density Control: The PhoenixSpec Nephelometer was used to prepare the inocula for testing of the clinical, challenge, reproducibility and QC isolates. The same inoculum suspension was used for both the Phoenix System and the reference method testing. The BD Phoenix AP instrument was used to standardize the inocula for challenge, QC, and reproducibility isolates. Validation data for both the PhoenixSpec and the Phoenix AP instrument was provided and found to be acceptable.
d. Detection limit:
Not applicable
e. Analytical specificity:
Not applicable
f. Assay cut-off:
Not applicable
2. Comparison studies:
a. Method comparison with predicate device:
The accuracy of results obtained with the Phoenix System was determined by comparison to the CLSI-recommended broth dilution method (reference method). Reference panels were prepared according to CLSI M07-A10 guidelines. In addition, specific to ceftazidime/avibactam, reference panels need to be read within 18 hours of incubation because of degradation of ceftazidime activity by 24 hours. During the comparative studies, the reference results were read after 16 to 18 hours of incubation. Sites performed testing on Gram negative isolates using Phoenix and reference panel formats appropriate for gram negative organisms. Antimicrobial
{9}
agents in the test and reference panels had identical dilution ranges which were appropriate for the interpretive breakpoints of the drug. Testing was performed using at least two different production lots of Phoenix panels, AST broth and AST indicator at each study site. A minimum of three different lots of the Phoenix panel were used across all sites for the entire study. Phoenix and reference panels were inoculated using the same organism suspension.
Growth in the Phoenix panels was determined from data recorded by the instrument. Performance was analyzed using FDA breakpoints for ceftazidime/avibactam, and results were compared to results obtained by the broth microdilution reference method based on the guidelines provided in the Class II Special Controls Guidance Document: Antimicrobial Susceptibility Test (AST) Systems.
A total of 1216 clinical isolates were tested at the three study sites and included both fresh and stock isolates. Stock isolates comprised 9.0% of total isolates tested. Clinical isolates tested included representatives of species listed in the FDA pharmaceutical drug label and were tested using inocula prepared by the PhoenixSpec nephelometer (manual method).
A total of 132 unique challenge isolates with expected results (expected MIC value of each isolate was the mode after testing with the reference broth dilution multiple times) were also supplied to the testing sites by the sponsor. Challenge isolates were obtained from BD's internal collection and from external laboratories. The challenge isolates were randomized and divided equally among the testing sites. Results obtained for Challenge isolates using the Phoenix System were compared to expected MIC results. Identification and expected results were masked to the study sites. The inocula for the challenge isolates were prepared using both the PhoenixSpec Nephelometer (manual method) and the Phoenix AP (automated method).
The performance evaluation summary of essential and categorical agreement results for clinical and challenge isolates with inocula prepared using the PhoenixSpec nephelometer (manual method) is shown in Table 4 below.
10
{10}
Table 4: Performance of BD Phoenix with Clinical and Challenge Isolates- Manual Inoculum Preparation†
| Ceftazidime/avibactam | EA Total | EA N | EA % | Eval EA Total | Eval EA N | Eval EA % | CA N | CA % | #R | Maj | Vmj |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| | Enterobacteriaceae ≤8/4 (Susceptible), ≥16/4 (Resistant) | | | | | | | | | | |
| Clinical | 1083 | 1061 | 98.0 | 110 | 100 | 90.9 | 1077 | 99.4 | 1 | 6 | 0 |
| Challenge | 108 | 107 | 99.1 | 32 | 32 | 100 | 108 | 100 | 12 | 0 | 0 |
| Combined | 1191 | 1168 | 98.1 | 142 | 132 | 93.0 | 1185 | 99.5 | 13 | 6 | 0 |
| | P. aeruginosa ≤8/4 (Susceptible), ≥16/4 (Resistant) | | | | | | | | | | |
| Clinical | 133 | 126 | 94.7 | 130 | 125 | 96.2 | 129 | 97.0 | 1 | 4 | 0 |
| Challenge | 24 | 24 | 100 | 17 | 17 | 100 | 24 | 100 | 9 | 0 | 0 |
| Combined | 157 | 150 | 95.5 | 147 | 142 | 96.6 | 153 | 97.5 | 10 | 4 | 0 |
| | Enterobacteriaceae + P. aeruginosa | | | | | | | | | | |
| Clinical | 1216 | 1187 | 97.6 | 240 | 225 | 93.8 | 1206 | 99.2 | 2 | 10 | 0 |
| Challenge | 132 | 131 | 99.2 | 49 | 49 | 100 | 132 | 100 | 21 | 0 | 0 |
| Total | 1348 | 1318 | 97.8 | 289 | 274 | 94.8 | 1338 | 99.3 | 23 | 10 | 0 |
$^{\dagger}$ EA - Essential Agreement (+/- 1 doubling dilution)
CA - Category Agreement
EVAL - Evaluable isolates
R - Resistant isolates
Maj - Major discrepancies
Vmj - Very major discrepancies
NOTE: There are no minor discrepancy calculations due to lack of intermediate category for ceftazidime/avibactam
Essential Agreement (EA) occurs when there is agreement between the result of the reference method and that of BD Phoenix within plus or minus one serial two-fold dilution of the antibiotic. Evaluable results are those that are on scale for both the BD Phoenix panel and the reference method. Category Agreement (CA) occurs when the interpretation of the result of the reference method agrees exactly with the interpretation of the BD Phoenix result.
The Phoenix ceftazidime/avibactam performance met the acceptance criteria for Enterobacteriaceae and Pseudomonas aeruginosa with overall EA and CA greater than or equal to $90\%$ . Due to lack of intermediate category, there are no minor discrepancy calculations for ceftazidime/avibactam. There were no very major discrepancies. The major (maj) discrepancy rate was $0.5\%$ (6/1178) and $2.7\%$ (4/147) for Enterobacteriaceae and Pseudomonas aeruginosa respectively. When stratified by organisms, a high maj discrepancy rate was observed with Providencia stuartii.
Providencia stuartii: There were four maj discrepancies (13.8%, 4/29) observed. Of the four maj discrepancies, three were at the reference breakpoints of $8\mu \mathrm{g} / \mathrm{mL}$ but within EA (i.e., resistant Phoenix MIC at $16\mu \mathrm{g} / \mathrm{mL}$ ). Taking into consideration the three values within essential agreement, the maj discrepancy rate became $3.4\%$ (1/29) for P. stuartii. The concern for major discrepancies is addressed in the limitations section:
"Ceftazidime/avibactam: Providencia stuartii - Due to the lack of an intermediate breakpoint, three out of four major errors which occurred for $P$ stuartii were within essential agreement when compared to the reference method. The adjusted error rate was $3.4\%$ . Testing should be repeated using an alternative testing/reference method prior to reporting results for the drug with Providencia stuartii when the Phoenix MIC is $16/4\mu \mathrm{g} / \mathrm{mL}$ ."
{11}
Resistant Isolates: There were a total of 23 resistant isolates in the evaluation of ceftazidime/avibactam. However, ten isolates each were from K. pneumoniae and P. aeruginosa. A limitation of insufficient resistant isolates was included:
"The ability of the Phoenix System to detect resistance in the following combination(s) is unknown because a sufficient number of resistant strains were not encountered at the time of comparative clinical testing:
Ceftazidime/avibactam Isolates other than Klebsiella pneumoniae and Pseudomonas aeruginosa"
The challenge organisms were also tested using suspensions prepared by the Phoenix AP instrument. The comparison between manual (PhoenixSpec) method and Phoenix AP is shown in Table 5 below. The overall % EA and % CA consistently met the acceptance criteria of greater than or equal to 90%. There were no very major or major discrepancies with either inoculation method.
Table 5: Comparison of Inoculation Methods with Challenge Isolates
| Ceftazidime/ avibactam | EA Total | EA N | EA % | Eval EA Total | Eval EA N | Eval EA % | CA N | CA % | #R | Maj | Vmj |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| | Enterobacteriaceae ≤8/4 (Susceptible), ≥16/4 (Resistant) | | | | | | | | | | |
| Manual (PhoenixSpec) | 108 | 107 | 99.1 | 32 | 32 | 100 | 108 | 100 | 12 | 0 | 0 |
| Phoenix AP | 108 | 107 | 99.1 | 32 | 32 | 100 | 108 | 100 | 12 | 0 | 0 |
| | P. aeruginosa ≤8/4 (Susceptible), ≥16/4 (Resistant) | | | | | | | | | | |
| Manual (PhoenixSpec) | 24 | 24 | 100 | 17 | 17 | 100 | 24 | 100 | 9 | 0 | 0 |
| Phoenix AP | 24 | 24 | 100 | 17 | 17 | 100 | 24 | 100 | 9 | 0 | 0 |
# MIC Trends:
The claimed Enterobacteriaceae and Pseudomonas aeruginosa organisms were also evaluated for trending. This trending calculation takes into account MIC values that are determined to be $\leq 1$ and $\geq 1$ doubling dilutions compared to the reference method irrespective whether the device MIC values are on-scale or not. The trending analysis is shown in Table 6.
{12}
Table 6: Trending Analysis of Evaluable Clinical and Challenge Isolates
| Ceftazidime/avibactam 0.25/4 – 32/4 μg/mL | Totala | Difference in MIC as Compared to the CLSI Reference Method | | | | |
| --- | --- | --- | --- | --- | --- | --- |
| | | ≤2 dil. lower | 1 dil. lower | Exact | 1 dil. higher | ≥2 dil. higher |
| (Enterobacteriaceae + P. aeruginosa) | 460 | 7 | 43 | 160 (34.78%) | 227 | 23 |
| | | 50 (10.87%)b 95% CI (8.34% to 14.04%) | | | 250 (54.35%)b 95% CI (49.78% to 58.85%) | |
a Total number of evaluable results for trending analysis
b Difference between isolates trending lower and isolates trending higher: -43.48 ; 95% CI (-48.64% to - 37.91%)
A trend towards higher MIC was observed with claimed Enterobacteriaceae isolates and P. aeruginosa when compared to the CLSI broth microdilution reference method. This trending and the potential for occurrence of major discrepancies for ceftazidime/avibactam when testing clinical and challenge isolate results with the Phoenix ceftazidime/avibactam was addressed by adding the following footnote:
"BD Phoenix ceftazidime/avibactam MIC values tended to be in exact agreement or at least one doubling dilution higher when testing Enterobacteriaceae or P. aeruginosa compared to the reference broth micro-dilution."
## Enzyme Group Characterization/Resistance Markers Information
Enterobacteriaceae with beta-lactamases were included in the ceftazidime/avibactam comparative studies. They were AmpC (6), KPC (16), OXA (9), CTX-M (8), TEM (14), and SHV (8). The Enterobacteriaceae included Citrobacter freundii, Enterobacter aerogenes, Enterobacter cloacae, E. coli, Klebsiella oxytoca, Klebsiella pneumoniae and Proteus mirabilis.
The study indicated that when beta-lactamases were known, eight K. pneumoniae demonstrated ceftazidime/avibactam resistance (>32/4μg/mL) in the presence of AmpC, KPC, OXA, CTX-M, TEM, and/or SHV. However, twelve K. pneumoniae showed susceptibility to ceftazidime/avibactam with MIC values range from ≤0.25/4 to 4/4μg/mL in the presence of KPC, OXA, CTX-M, TEM, and/or SHV.
In addition, seven metallo-beta-lactamase producing Pseudomonas aeruginosa were tested and demonstrated resistance (≥32/4μg/mL) to ceftazidime/avibactam. The following limitation was added to the ceftazidime/avibactam labeling regarding other resistance markers and enzyme characterization:
"Enzyme group characterization was not available at the time of comparative testing, and therefore the performance of the BD Phoenix ceftazidime/avibactam is unknown for Pseudomonas aeruginosa in the presence AmpC, or lacking outer membrane porin (OprD)."
{13}
b. Matrix comparison:
Not applicable
3. Clinical studies:
a. Clinical Sensitivity:
Not applicable
b. Clinical specificity:
Not applicable
c. Other clinical supportive data (when a. and b. are not applicable):
Not applicable
4. Clinical cut-off:
Not applicable
5. Expected values/Reference range:
The FDA interpretive categories for susceptible(S) and resistant (R) as listed below were used to evaluate all performance data.
Enterobacteriaceae ≤ 8/4 μg/mL (susceptible), ≥ 16/4 μg/mL (Resistant)
Pseudomonas aeruginosa ≤ 8/4 μg/mL (susceptible), ≥ 16/4 μg/mL (Resistant)
N. Proposed Labeling:
The labeling is sufficient and it satisfies the requirements of 21 CFR Part 809.10.
O. Conclusion:
The submitted information in this premarket notification is complete and supports a substantial equivalence decision.
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.