FDA-cleared profile

Ezra Flash

Ezra AI, Inc. · MRI · FDA-cleared (510(k))

Authorized purpose: Ezra Flash enhances non-contrast MRI by reducing noise on supported 1.5T and 3T Siemens or GE systems for adults, including head sagittal T1 and axial T2 or FLAIR, abdomen axial or coronal T2, and pelvis sagittal, axial, or coronal T2 studies.

Clinical role
MRI image enhancement or post-processing support before routine professional interpretation.
Images and patients
MRI · Head, abdomen, and pelvis
Key limitation
Keep in mind: Supported field strength, scanner, image size, anatomy, sequence, input quality, and processing options are release-specific.

Overview status: Source-reviewed overview

Report a correction
Clinical details Purpose, workflow fit, evidence, and safety record

Workflow navigation pilot

Workflow role has not yet been reviewed for this navigation pilot.

A tag identifies a documented role; it does not establish compatibility or local acceptance. Methods and sources

  • What does this software do?Authorized purpose: Ezra Flash enhances non-contrast MRI by reducing noise on supported 1.5T and 3T Siemens or GE systems for adults, including head sagittal T1 and axial T2 or FLAIR, abdomen axial or coronal T2, and pelvis sagittal, axial, or coronal T2 studies.
  • Which images or clinical context are in scope?Modality: MRI Anatomy or clinical context: Head, abdomen, and pelvis Input: Supported DICOM MRI images and release-specific processing parameters.
  • Who uses it?Intended users: Qualified MRI technologists and interpreting physicians.
  • What does the software produce?Output: Processed or enhanced MR image objects for review against the source study and downstream archival.
  • What is its most important limitation?Key limitation: Supported field strength, scanner, image size, anatomy, sequence, input quality, and processing options are release-specific.

Clinical takeaway. Clinical role: Ezra Flash enhances non-contrast MRI by reducing noise on supported 1.5T and 3T Siemens or GE systems for adults, including head sagittal T1 and axial T2 or FLAIR, abdomen axial or coronal T2, and pelvis sagittal, axial, or coronal T2 studies.

Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports software verification, validation, and usability testing and main performance testing, stated only as thresholds without measured values or dataset counts: SNR of selected ROIs on average improved by ≥ 5% and CNR by > 0% after enhancement versus original MR images, and mean Likert results greater than or equal to 0.5 Likert scale points for enhanced versus original images. It states the test results demonstrated the device performs to its intended use. Results are as reported in the FDA submission, not independent validation.

Evidence context

Evidence context not reviewed for this FDA record.

Public-label constraints

Label constraints have not been reviewed for this exact FDA record. Unknown is not all ages or evidence of unsuitability.

Public-label constraints, not patient-level eligibility or a medical recommendation. Training and evaluation populations are separate. Read the original labeling and confirm the exact release and protocol.

Purpose
Ezra Flash enhances non-contrast MRI by reducing noise on supported 1.5T and 3T Siemens or GE systems for adults, including head sagittal T1 and axial T2 or FLAIR, abdomen axial or coronal T2, and pelvis sagittal, axial, or coronal T2 studies.
  • Exact FDA submission
  • Checked 2026-09-04
Workflow role
MRI image enhancement or post-processing support before routine professional interpretation.
  • Exact FDA submission
  • Checked 2026-09-04
Required input
Supported DICOM MRI images and release-specific processing parameters.
  • Exact FDA submission
  • Checked 2026-09-04
Output and clinician action
Processed or enhanced MR image objects for review against the source study and downstream archival.
  • Exact FDA submission
  • Checked 2026-09-04
Care setting
MRI departments or image-processing workstations using supported DICOM MRI workflows.
  • Exact FDA submission
  • Checked 2026-09-04
Intended users
Qualified MRI technologists and interpreting physicians.
  • Exact FDA submission
  • Checked 2026-09-04
Limitations
Supported field strength, scanner, image size, anatomy, sequence, input quality, and processing options are release-specific.
  • Exact FDA submission
  • Checked 2026-09-04
Evidence summary
The exact FDA document reports software verification, validation, and usability testing and main performance testing, stated only as thresholds without measured values or dataset counts: SNR of selected ROIs on average improved by ≥ 5% and CNR by > 0% after enhancement versus original MR images, and mean Likert results greater than or equal to 0.5 Likert scale points for enhanced versus original images. It states the test results demonstrated the device performs to its intended use. Results are as reported in the FDA submission, not independent validation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "The Ezra Flash has been developed in a manner consistent with accepted standards for software development and evaluated in accordance with design specifications and applicable performance standards through software verification, validation, and usability testing." … "Ezra performed the following main performance testing for Ezra Flash:". Read from the exact FDA decision document on 2026-11-14.

Evidence

Performance evidence

Metrics are shown only when they are tied to a source, endpoint, population, and tested product version. Candidate literature without exact product and version linkage is not shown as product evidence.

Evidence summary
The exact FDA document reports software verification, validation, and usability testing and main performance testing, stated only as thresholds without measured values or dataset counts: SNR of selected ROIs on average improved by ≥ 5% and CNR by > 0% after enhancement versus original MR images, and mean Likert results greater than or equal to 0.5 Likert scale points for enhanced versus original images. It states the test results demonstrated the device performs to its intended use. Results are as reported in the FDA submission, not independent validation.
  • FDA source
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "The Ezra Flash has been developed in a manner consistent with accepted standards for software development and evaluated in accordance with design specifications and applicable performance standards through software verification, validation, and usability testing." … "Ezra performed the following main performance testing for Ezra Flash:". Read from the exact FDA decision document on 2026-11-14.

Reported sensitivity
Not established in reviewed sources
  • Reviewed sources checked
  • Exact FDA submission
  • Checked 2026-09-04

No exact submission-linked sensitivity endpoint with a verified population, threshold, tested version, and source was promoted.

Reported specificity
Not established in reviewed sources
  • Reviewed sources checked
  • Exact FDA submission
  • Checked 2026-09-04

No exact submission-linked specificity endpoint with a verified population, threshold, tested version, and source was promoted.

No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.

K242334 FDA evidence package for Ezra Flash

  • DesignFDA 510(k) decision evidence package reviewed for exact submission identity and labeled scope
  • PopulationLabeled population and configuration described in the K242334 FDA decision material
  • Scopeexact submission
  • Tested versionEzra Flash configuration described in K242334
  • IndependenceSponsor or vendor study

K242334

Manufacturer evidence submitted for the exact FDA decision. It is not independent clinical validation, and local technical, clinical, privacy, security, and workflow acceptance remains necessary.

Safety and lifecycle

Postmarket record

Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.

Postmarket safety review
The 2026-09-02 openFDA device-recall snapshot contained no record matched to K242334 by exact native submission identifier. This does not exclude product-family, later, or adverse-event information.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-04

Exact-identifier review does not prove absence of all product-family safety signals.

Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not publicly available: Reviewed sources do not publish an exact-product procurement price with a stated offer scope.

Reimbursement

Reimbursement
No separate named-product Medicare payment was identified in the reviewed CMS coverage material. Evaluate the product within the applicable imaging, procedural, or surgical service line and verify payer, site-of-service, and coding assumptions independently.
  • Service-level, not product-specific
  • Checked 2026-09-04

No product-specific code

No separate named-product payment identified in reviewed public material

Centers for Medicare & Medicaid Services · United States

Build a local total-cost and value model; do not infer reimbursement from FDA clearance or approval.

IT implementation Deployment, interfaces, data handling, and support

System and version relationships

Match the AI release, system build, configuration and region. Source documentation does not establish acceptance of an installed system.

No specific system/version pairing has completed review for this FDA record. A broad DICOM or product-family statement does not establish a named viewer build's support.

Review Merge, Visage, Sectra, AGFA and IntelePACS context

Integration chain: evidence at each hop

Public source context, not tested interoperability. Each hop needs its own release/configuration evidence. Missing or unavailable routes are not documented incompatibility. All local tests are planned, not passed; no installed-system acceptance is recorded.

Acquisition/source → routing → AI processing → returned objects → viewer/worklist/report → support owner

No specific route context has been source-reviewed for this record. Obtain both endpoint builds and documents; this is not a finding of incompatibility.

  1. Acquisition/source

    Source context, not route validation: Supported DICOM MRI images and release-specific processing parameters.

    Scope: Exact FDA submission.

    Confirm scanner/model, protocol, series completeness and both software builds.

    Field checked 2026-09-04 · FDA 510(k) decision material K242334: Ezra Flash

  2. Routing

    Source context, not route validation: The exact FDA package describes Ezra Flash receiving DICOM-compliant MR image inputs and delivering enhanced images as DICOM files, with receipt and delivery depending on other software systems and enhanced images viewed on existing PACS workstations. Interface versions and local compatibility require confirmation.

    Scope: Exact FDA submission. Packet wording: "Ezra Flash receives DICOM-compliant non-contrast MR image inputs acquired on 1.5-Tesla and 3-Tesla scanners" … "The receipt of original DICOM image files and delivery of enhanced images as DICOM files depends on other soft- ware systems.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

    Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.

    Field checked 2026-11-14 · FDA 510(k) decision material K242334: Ezra Flash

  3. AI processing

    Source context, not route validation: The exact FDA package describes Ezra Flash as a software package that operates on off-the-shelf hardware with a Linux operating system. Current hosting, data flow, and commercial configuration require vendor confirmation.

    Scope: Exact FDA submission. Packet wording: "Physical Char- Software package that op- Same Same acteristics erates on off-the-shelf hard- ware." … "Operating Sys- Linux Same Same tem". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

    Confirm processing location, queue ownership, exclusions and exact AI build.

    Field checked 2026-11-14 · FDA 510(k) decision material K242334: Ezra Flash

  4. Returned objects

    Source context, not route validation: Processed or enhanced MR image objects for review against the source study and downstream archival.

    Scope: Exact FDA submission.

    Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.

    Field checked 2026-09-04 · FDA 510(k) decision material K242334: Ezra Flash

  5. Viewer/worklist/report

    Unresolved route: Processed or enhanced MR image objects for review against the source study and downstream archival.

    Scope: Exact FDA submission.

    Confirm the named viewer/worklist/report build, display behavior and report transfer. Output support alone does not establish this endpoint. The displayed source describes output, not validated end-to-end delivery.

    Field checked 2026-09-04 · FDA 510(k) decision material K242334: Ezra Flash

  6. Support owner

    Unresolved route: Not established for the exact route.

    Scope: Scope not established.

    Name the local, platform and AI supplier support owners and escalation path.

Planned local route tests

No tests below have been performed or accepted.

  1. Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
  2. Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
  3. Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
  4. Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
  5. Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
  6. Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
  7. Updates and rollback (planned). Define version change control, revalidation triggers, stop-use criteria and a tested rollback route.

Local implementation checklist

Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.

Open the printable evaluation checklist

Deployment
The exact FDA package describes Ezra Flash as a software package that operates on off-the-shelf hardware with a Linux operating system. Current hosting, data flow, and commercial configuration require vendor confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Physical Char- Software package that op- Same Same acteristics erates on off-the-shelf hard- ware." … "Operating Sys- Linux Same Same tem". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Integration
The exact FDA package describes Ezra Flash receiving DICOM-compliant MR image inputs and delivering enhanced images as DICOM files, with receipt and delivery depending on other software systems and enhanced images viewed on existing PACS workstations. Interface versions and local compatibility require confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Ezra Flash receives DICOM-compliant non-contrast MR image inputs acquired on 1.5-Tesla and 3-Tesla scanners" … "The receipt of original DICOM image files and delivery of enhanced images as DICOM files depends on other soft- ware systems.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Training
Only qualified mri technologists and interpreting physicians should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
  • Exact FDA submission
  • Checked 2026-09-04

Release and scope verification

Map the installed model, build, options, population, anatomy, inputs, outputs, and enabled functions to K242334 before acceptance.

exact submission · checked 2026-09-04

Later product-family features are not evidence that this cleared release includes them.

Interoperability acceptance

Exact public integration details remain incomplete; establish and test the supported input, output, identity, routing, archive, report, and downtime contract locally.

exact submission · checked 2026-09-04

Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.

Clinical acceptance

Use a signed local test set for the exact labeled population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. Supported field strength, scanner, image size, anatomy, sequence, input quality, and processing options are release-specific.

exact submission · checked 2026-09-04

Define stop-use, escalation, rollback, and revalidation triggers before production use.

Economic evaluation

Model capital and recurring cost against net staff time after review, throughput, repeat imaging or rework, room time, consumables, infrastructure, training, service, downtime, upgrade, and replacement costs.

product family · checked 2026-09-04

No exact-product price was found in reviewed public material; productivity or value claims require local evidence.

Lifecycle monitoring

Monitor by exact hardware, software, model, and algorithm version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates.

exact submission · checked 2026-09-04

Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. No exact native-submission recall record was found in the checked snapshot; this does not exclude other product-family or later signals.

Sources & review details FDA identity, research record, source ledger, and history

Regulatory identity

FDA record and catalog context

The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.

FDA submission
K242334
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
MRI
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Anatomy
Head, abdomen, and pelvis
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2025-01-02
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
FDA status
FDA-cleared
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31

Research record

What has been checked

This audit distinguishes completed source review from fields that have not yet been researched.

Exact FDA record reviewedStatus
2026-09-20Last searched
27Fields reviewed
12Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads

The refreshed discovery snapshot contains no PubMed or ClinicalTrials.gov candidates; no external evidence was promoted. The current discovery snapshot contains 0 PubMed and 0 ClinicalTrials.gov candidate records; its dated, count-matched human screening remains current. Unlinked candidates remain quarantined. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.

Candidate leads were screened against the exact product and tested version. Unlinked records remain quarantined.

Source classes: fda ai list, fda decision summary, fda decision material, peer reviewed literature, clinical trial registry, reimbursement policy, fda device recall, literature index, trial registry, pubmed, clinical trials, openfda device recall

Field review details

Recorded state, verification date, notes and sources for fields without a publishable value. Conflicting records stay explicitly unsettled here; no plain settled value is shown for them.

  • Public pricing: Not publicly available - checked 2026-09-04 - Exact FDA submission

    No public list price for the exact cleared configuration was found. Obtain a written quote separating license or hardware basis, implementation, interfaces, infrastructure, training, service, upgrades, renewal, consumables, and exit costs.

  • Pricing model: Not yet reviewed
  • Setup and integration fees: Not yet reviewed
  • Recurring fees: Not yet reviewed
  • Minimum commitment: Not yet reviewed
  • Contract duration: Not yet reviewed
  • Renewal terms: Not yet reviewed
  • Cancellation terms: Not yet reviewed
  • Support and service terms: Not yet reviewed
  • Trial or pilot terms: Not yet reviewed
  • Data hosting location: Not yet reviewed
  • Data retention: Not yet reviewed
  • Documented data use: Not yet reviewed
  • Hardware requirements: Not yet reviewed
  • Network requirements: Not yet reviewed
  • Identity and access: Not yet reviewed
  • Security: Not publicly available - checked 2026-09-04 - Exact FDA submission

    Public materials reviewed for this exact release do not establish the complete security posture. Request data-flow, identity, audit, encryption, retention, remote-access, vulnerability-management, backup, and incident-response evidence.

  • Installation timeline: Not yet reviewed
  • Monitoring: Not publicly available - checked 2026-09-04 - Exact FDA submission

    The exact FDA decision and checked recall snapshot do not establish a complete local postmarket monitoring protocol. Track version, population, anatomy, protocol, input quality, edits, failures, repeats, downstream effects, downtime, incidents, recalls, and updates locally.

6 sources - 3 history items

Source ledger

  1. FDA 510(k) decision material K242334: Ezra Flash

    U.S. Food and Drug Administration - Published 2025-01-02 - Accessed 2026-09-04

    Scope: identity, purpose, clinicalUse, modality, anatomy, intendedUsers, careSetting, workflowRole, input, output, limitations, evidenceSummary

  2. Artificial Intelligence-Enabled Medical Devices

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, modalityContext

  3. PubMed biomedical literature index

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery

  4. ClinicalTrials.gov study registry

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery, studyStatus

  5. Medicare Coverage Database

    Centers for Medicare & Medicaid Services - Accessed 2026-09-01

    Scope: coverage, codingContext

  6. openFDA Device Recall API

    U.S. Food and Drug Administration - Accessed 2026-09-02

    Scope: recallDiscovery, nativeSubmissionMatching

Research history

  1. K242334 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    fda record reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K253690

LungMaps

Siemens Healthineers AG

Authorized purpose: LungMaps processes one or more 2D lung MRI time series to support radiologist interpretation of ventilation and perfusion maps; it is not the sole source for diagnosis.

Modality
MRI
Anatomy
Chest/Lung
Decision
2026-06-15
FDA-cleared K260113

uMR Astra

Shanghai United Imaging Healthcare Co., Ltd.

Authorized purpose: uMR Astra is a diagnostic MR system for cross-sectional and spectroscopic imaging of the labeled head, body, and extremities.

Modality
MRI
Anatomy
Head; body; and extremities
Decision
2026-05-22
FDA-cleared K260746

S-scan Open (100001800)

Esaote, S.p.A.

Authorized purpose: S-scan Open is an Esaote MR system for diagnostic image acquisition, reconstruction, display, and professional interpretation within the labeled scanner, coil, sequence, and anatomy scope.

Modality
MRI
Anatomy
Multi-region
Decision
2026-03-27

Correct this exact record

Copy this public context and add the field, proposed wording and original source before sending. Nothing here is submitted automatically. Form-specific prefill has not been verified.

Open existing correction destination

Permission to display a submission is not evidence verification. A submission enters editorial review; it does not approve a public change. Form availability, data entry, receipt, review and publication are separate steps. Data entry and receipt remain unverified.

Accepted repository change history

No entry has been added to this scoped change history for this record. This is not proof that the record never changed.

Correction policy and limits · Public repository change history