FDA-cleared profile

SwiftMR

AIRS Medical Inc. · MRI · FDA-cleared (510(k))

Authorized purpose: Accept, enhance, and transfer all-body MR images in DICOM format using noise reduction and image sharpening; it is not intended for mobile devices.

Clinical role
Automatic background post-processing, quality-check, and transfer workflow that is intended not to interrupt routine MR scanning; users monitor status and retrieve enhanced studies.
Images and patients
MRI · All body parts, including the body, cardiac, neuro, and musculoskeletal regions represented in validation.
Key limitation
Keep in mind: The software is not intended for mobile devices and processes DICOM MR images only. The FDA validation used image-quality acceptance criteria rather than disease-detection endpoints: SNR increase thresholds for noise reduction and FWHM-decrease thresholds for sharpening, each required for at least 90% of the applicable dataset.

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: Accept, enhance, and transfer all-body MR images in DICOM format using noise reduction and image sharpening; it is not intended for mobile devices.
  • Which images or clinical context are in scope?Modality: MRI Anatomy or clinical context: All body parts, including the body, cardiac, neuro, and musculoskeletal regions represented in validation. Input: DICOM MR images from all body parts. The validation conditions covered MRI field strengths 0.25T, 0.6T, 1.5T, and 3.0T and T1, T2, T2*, FLAIR, PD, DWI, and MRA protocols across multiple manufacturers.
  • Who uses it?Intended users: Radiology technologists; system administrators control automation and settings, and professional users retrieve and monitor results.
  • What does the software produce?Output: Enhanced DICOM MR images with reduced noise and increased sharpness; denoising level 0-8 and sharpening level 0-5 are described. Enhanced images can be transferred to PACS or an MR device and coexist with original images.
  • What is its most important limitation?Key limitation: The software is not intended for mobile devices and processes DICOM MR images only. The FDA validation used image-quality acceptance criteria rather than disease-detection endpoints: SNR increase thresholds for noise reduction and FWHM-decrease thresholds for sharpening, each required for at least 90% of the applicable dataset.

Clinical takeaway. Clinical role: Accept, enhance, and transfer all-body MR images in DICOM format using noise reduction and image sharpening; it is not intended for mobile devices.

Evidence takeaway. Evidence from the reviewed source record: FDA K230854 reports unit, integration/system, and retrospective clinical-image validation testing; all predetermined criteria were reported as passed. Noise-reduction acceptance required SNR increase of at least 40% for at least 90% of the dataset at level 1, with 1% incremental increases per level. Sharpening acceptance required FWHM reduction of 0.13% for the deep-learning model or 0.43%, 1.7%, 2.3%, 3.6%, or 4.5% for filter levels 1-5, each for at least 90% of the dataset. Validation covered six manufacturers, 0.25T-3.0T field strengths, multiple body regions and protocols, adults and pediatric subjects, and reduced-scan-time images up to 50%. No FDA sensitivity, specificity, diagnostic AUC, or reader-study endpoint is established.

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
Accept, enhance, and transfer all-body MR images in DICOM format using noise reduction and image sharpening; it is not intended for mobile devices.
  • Exact FDA submission
  • Checked 2026-09-09
Workflow role
Automatic background post-processing, quality-check, and transfer workflow that is intended not to interrupt routine MR scanning; users monitor status and retrieve enhanced studies.
  • Exact FDA submission
  • Checked 2026-09-09
Required input
DICOM MR images from all body parts. The validation conditions covered MRI field strengths 0.25T, 0.6T, 1.5T, and 3.0T and T1, T2, T2*, FLAIR, PD, DWI, and MRA protocols across multiple manufacturers.
  • Exact FDA submission
  • Checked 2026-09-09
Output and clinician action
Enhanced DICOM MR images with reduced noise and increased sharpness; denoising level 0-8 and sharpening level 0-5 are described. Enhanced images can be transferred to PACS or an MR device and coexist with original images.
  • Exact FDA submission
  • Checked 2026-09-09
Care setting
Imaging center, clinic, or hospital.
  • Exact FDA submission
  • Checked 2026-09-09
Intended users
Radiology technologists; system administrators control automation and settings, and professional users retrieve and monitor results.
  • Exact FDA submission
  • Checked 2026-09-09
Limitations
The software is not intended for mobile devices and processes DICOM MR images only. The FDA validation used image-quality acceptance criteria rather than disease-detection endpoints: SNR increase thresholds for noise reduction and FWHM-decrease thresholds for sharpening, each required for at least 90% of the applicable dataset.
  • Exact FDA submission
  • Checked 2026-09-09
Evidence summary
FDA K230854 reports unit, integration/system, and retrospective clinical-image validation testing; all predetermined criteria were reported as passed. Noise-reduction acceptance required SNR increase of at least 40% for at least 90% of the dataset at level 1, with 1% incremental increases per level. Sharpening acceptance required FWHM reduction of 0.13% for the deep-learning model or 0.43%, 1.7%, 2.3%, 3.6%, or 4.5% for filter levels 1-5, each for at least 90% of the dataset. Validation covered six manufacturers, 0.25T-3.0T field strengths, multiple body regions and protocols, adults and pediatric subjects, and reduced-scan-time images up to 50%. No FDA sensitivity, specificity, diagnostic AUC, or reader-study endpoint is established.
  • Exact FDA submission
  • Checked 2026-09-09

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
FDA K230854 reports unit, integration/system, and retrospective clinical-image validation testing; all predetermined criteria were reported as passed. Noise-reduction acceptance required SNR increase of at least 40% for at least 90% of the dataset at level 1, with 1% incremental increases per level. Sharpening acceptance required FWHM reduction of 0.13% for the deep-learning model or 0.43%, 1.7%, 2.3%, 3.6%, or 4.5% for filter levels 1-5, each for at least 90% of the dataset. Validation covered six manufacturers, 0.25T-3.0T field strengths, multiple body regions and protocols, adults and pediatric subjects, and reduced-scan-time images up to 50%. No FDA sensitivity, specificity, diagnostic AUC, or reader-study endpoint is established.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-09
Reported sensitivity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

Reported specificity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

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

SwiftMR regulatory performance study summary

  • DesignReader Study
  • PopulationAdult and Pediatric
  • Scopeexact submission
  • Tested version3
  • IndependenceIndependence not established

K230854

ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.

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 exact-identifier FDA recall query returned no native recall record for K230854. This limited result does not establish absence of recalls or other safety information and does not cover later versions, family records, MAUDE reports, corrections, or field notices.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-09
Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not verified: Pricing information is recorded but not verified against a resolving source.

Reimbursement

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: DICOM MR images from all body parts. The validation conditions covered MRI field strengths 0.25T, 0.6T, 1.5T, and 3.0T and T1, T2, T2*, FLAIR, PD, DWI, and MRA protocols across multiple manufacturers.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-09 · FDA K230854: SwiftMR

  2. Routing

    Source context, not route validation: The described automation receives MR DICOM images from PACS or an MRI system, processes them in the background through a server/database workflow, and transfers enhanced DICOM images to PACS or the MR device. Specific interface versions, routing behavior, hosting model, and universal PACS/RIS/EHR compatibility are not established.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-09 · FDA K230854: SwiftMR

  3. AI processing

    Source context, not route validation: The exact FDA package describes SwiftMR as a software device that operates on off-the-shelf, PC-compatible computer hardware, with newly acquired MR images automatically uploaded to the server and registered in a database for processing. Current hosting, data flow, and commercial configuration require vendor confirmation.

    Scope: Exact FDA submission. Packet wording: "Physical Software device that Same as predicate No Difference Characteristics operates on off-the- shelf computer hardware" … "Computer PC Compatible Same as predicate No Difference". 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 K230854: SwiftMR

  4. Returned objects

    Source context, not route validation: Enhanced DICOM MR images with reduced noise and increased sharpness; denoising level 0-8 and sharpening level 0-5 are described. Enhanced images can be transferred to PACS or an MR device and coexist with original images.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-09 · FDA K230854: SwiftMR

  5. Viewer/worklist/report

    Unresolved route: Enhanced DICOM MR images with reduced noise and increased sharpness; denoising level 0-8 and sharpening level 0-5 are described. Enhanced images can be transferred to PACS or an MR device and coexist with original images.

    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-09 · FDA K230854: SwiftMR

  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 SwiftMR as a software device that operates on off-the-shelf, PC-compatible computer hardware, with newly acquired MR images automatically uploaded to the server and registered in a database for processing. Current hosting, data flow, and commercial configuration require vendor confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Physical Software device that Same as predicate No Difference Characteristics operates on off-the- shelf computer hardware" … "Computer PC Compatible Same as predicate No Difference". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Integration
The described automation receives MR DICOM images from PACS or an MRI system, processes them in the background through a server/database workflow, and transfers enhanced DICOM images to PACS or the MR device. Specific interface versions, routing behavior, hosting model, and universal PACS/RIS/EHR compatibility are not established.
  • Exact FDA submission
  • Checked 2026-09-09
Security
AIRS Medical's SwiftMR information security white paper summary states security practices for cloud and on-premises workflows (transport encryption, network access control, application security, identity management, backup, disaster recovery, monitoring) and lists ISO/IEC 27001:2022, GDPR, HIPAA and SOC 2 Type II. Vendor statement about SwiftMR; the full white paper was not read.
  • Vendor-wide
  • Checked 2026-10-25

Vendor statement, not an attestation; exact-release scope is not established.

Input or output interoperability

DICOM is explicitly referenced in the described input, output, or workflow.

exact submission · checked 2026-09-01

The model card does not establish every supported DICOM object, transfer method, or local interface.

Supported acquisition environment

Supported hardware: Unspecified. Scanner manufacturers: Unspecified

exact submission · checked 2026-09-01

Confirm currently supported software versions, protocols, and site-specific acquisition configurations.

ACR exact-submission catalog context

ACR AI Central provides an exact-submission model card for SwiftMR; FDA labeling remains controlling for clinical use, limitations, and performance.

exact submission · checked 2026-09-09
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
K230854
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
MRI
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-09
Anatomy
All body parts, including the body, cardiac, neuro, and musculoskeletal regions represented in validation.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-09
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2023-10-27
  • 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
23Fields reviewed
10Source classes checked
3Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads

The refreshed discovery snapshot contains 3 PubMed and 0 ClinicalTrials.gov candidate records. Discovery metadata alone does not establish exact tested-product, version, population, and endpoint applicability, so all candidates remain quarantined and none was promoted. The current discovery snapshot contains 3 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, acr ai central product, vendor documentation, 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 verified - checked 2026-09-09 - Exact FDA submission

    No public price or quote for the exact K230854 configuration was established in this review.

  • 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
  • Reimbursement: Not publicly available - checked 2026-09-09 - Exact FDA submission

    No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.

  • 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
  • Installation timeline: Not yet reviewed
  • Training: Not verified - checked 2026-09-09 - Exact FDA submission

    Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.

  • Monitoring: Not verified - checked 2026-09-09 - Exact FDA submission

    Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.

8 sources - 3 history items

Source ledger

  1. FDA K230854: SwiftMR

    U.S. Food and Drug Administration - Published 2023-10-27 - Accessed 2026-09-09

    Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, deployment

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. SwiftMR model card (K230854)

    American College of Radiology - Published 2026-06-26 - Accessed 2026-09-01

    Scope: intendedUsers, careSetting, output, limitations, evidenceSummary, integration, anatomy, evidenceStudies, implementationCapabilities

  4. PubMed biomedical literature index

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

    Scope: evidenceDiscovery

  5. ClinicalTrials.gov study registry

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

    Scope: evidenceDiscovery, studyStatus

  6. openFDA Device Recall API

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

    Scope: recallDiscovery, nativeSubmissionMatching

  7. openFDA exact recall query for K230854

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

    Scope: postmarketSafety

  8. AIRS Medical SwiftMR Information Security white paper summary

    AIRS Medical - Accessed 2026-10-25

    Scope: security

Research history

  1. K230854 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 K253077

uOmnispace.MR

Shanghai United Imaging Healthcare Co., Ltd.

Authorized purpose: uOmnispace.MR provides viewing, manipulation, evaluation, and analysis of MR images, including labeled breast, brain, perfusion, vessel, cardiac, diffusion, susceptibility, dynamic, and spectroscopy workflows.

Modality
MRI
Anatomy
Whole body; brain; breast; vessels; and heart
Decision
2026-04-22
FDA-cleared K252084

AI4CMR v2.0

Ai4medimaging Medical Solutions S.A.

Authorized purpose: Cardiac MRI ventricular function and 2D phase-contrast flow quantification

Modality
MRI
Anatomy
Heart/Cardiovascular
Decision
2026-02-11
FDA-cleared K253780

SIGNA™ Bolt

Ge Medical Systems, LLC

Authorized purpose: SIGNA Bolt is a whole-body MRI system for high-resolution diagnostic imaging of the labeled body regions, with supported AI-assisted reconstruction, positioning, and protocol functions.

Modality
MRI
Anatomy
Head, neck, temporomandibular joint, spine, breast, heart, abdomen, pelvis, joints, prostate, vessels, and musculoskeletal anatomy
Decision
2026-02-06
FDA-cleared K253779

SIGNA™ Sprint Select

Ge Medical Systems, LLC

Authorized purpose: SIGNA Sprint Select is a whole-body MRI system for diagnostic imaging of the labeled body regions, with supported AI-assisted reconstruction, positioning, and protocol functions.

Modality
MRI
Anatomy
Head, neck, temporomandibular joint, spine, breast, heart, abdomen, pelvis, joints, prostate, vessels, and musculoskeletal anatomy
Decision
2026-02-05

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