FDA-cleared profile

Arterys MICA

Arterys Inc. · CT/CTA; MRI · FDA-cleared (510(k))

Authorized purpose: DICOM/non-DICOM image and data management with optional quantitative cardiac MR and oncology lesion evaluation, quantification, follow-up, and documentation support; the software does not directly generate a diagnosis or potential findings.

Clinical role
Image management/viewing and post-processing support for cardiac and oncology workflows, with clinician interpretation and responsibility.
Images and patients
CT/CTA; MRI · Heart and major vessels for the optional Cardio AI module; lung and liver lesions or nodules for the optional Oncology AI module; the base viewer handles broader radiological image data.
Key limitation
Keep in mind: The clinician retains ultimate responsibility for diagnosis and visual comparison; MICA is a complement to standard procedures and does not directly generate a diagnosis or potential findings; mammography is excluded from the stated data-management use.

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: DICOM/non-DICOM image and data management with optional quantitative cardiac MR and oncology lesion evaluation, quantification, follow-up, and documentation support; the software does not directly generate a diagnosis or potential findings.
  • Which images or clinical context are in scope?Modality: CT/CTA; MRI Anatomy or clinical context: Heart and major vessels for the optional Cardio AI module; lung and liver lesions or nodules for the optional Oncology AI module; the base viewer handles broader radiological image data. Input: Pre-existing DICOM CT or MR images from a PACS or scanner plus non-DICOM medical data; Cardio uses multi-slice, multi-phase, and velocity-encoded cardiovascular MR; mammography is excluded.
  • Who uses it?Intended users: Trained healthcare professionals.
  • What does the software produce?Output: Filtered and digitally manipulated images, quantitative measurements, cardiac quantitative data, and oncology lesion presence/absence assessment, evaluation, quantification, follow-up, and documentation; reports can be downloaded to PACS or a computer.
  • What is its most important limitation?Key limitation: The clinician retains ultimate responsibility for diagnosis and visual comparison; MICA is a complement to standard procedures and does not directly generate a diagnosis or potential findings; mammography is excluded from the stated data-management use.

Clinical takeaway. Clinical role: DICOM/non-DICOM image and data management with optional quantitative cardiac MR and oncology lesion evaluation, quantification, follow-up, and documentation support; the software does not directly generate a diagnosis or potential findings.

Evidence takeaway. Evidence from the reviewed source record: FDA performance section reports software verification and validation to specifications and applicable standards, including IEC 62304 and ISO 14971, with no numerical sensitivity, specificity, AUC, or clinical sample-size endpoint disclosed for this submission.

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
DICOM/non-DICOM image and data management with optional quantitative cardiac MR and oncology lesion evaluation, quantification, follow-up, and documentation support; the software does not directly generate a diagnosis or potential findings.
  • Exact FDA submission
  • Checked 2026-09-09
Workflow role
Image management/viewing and post-processing support for cardiac and oncology workflows, with clinician interpretation and responsibility.
  • Exact FDA submission
  • Checked 2026-09-09
Required input
Pre-existing DICOM CT or MR images from a PACS or scanner plus non-DICOM medical data; Cardio uses multi-slice, multi-phase, and velocity-encoded cardiovascular MR; mammography is excluded.
  • Exact FDA submission
  • Checked 2026-09-09
Output and clinician action
Filtered and digitally manipulated images, quantitative measurements, cardiac quantitative data, and oncology lesion presence/absence assessment, evaluation, quantification, follow-up, and documentation; reports can be downloaded to PACS or a computer.
  • Exact FDA submission
  • Checked 2026-09-09
Care setting
Diagnostic and therapy-follow-up imaging workflows; the FDA packet does not specify a facility type.
  • Exact FDA submission
  • Checked 2026-09-09
Intended users
Trained healthcare professionals.
  • Exact FDA submission
  • Checked 2026-09-09
Limitations
The clinician retains ultimate responsibility for diagnosis and visual comparison; MICA is a complement to standard procedures and does not directly generate a diagnosis or potential findings; mammography is excluded from the stated data-management use.
  • Exact FDA submission
  • Checked 2026-09-09
Evidence summary
FDA performance section reports software verification and validation to specifications and applicable standards, including IEC 62304 and ISO 14971, with no numerical sensitivity, specificity, AUC, or clinical sample-size endpoint disclosed for this submission.
  • 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 performance section reports software verification and validation to specifications and applicable standards, including IEC 62304 and ISO 14971, with no numerical sensitivity, specificity, AUC, or clinical sample-size endpoint disclosed for this submission.
  • 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.

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 K182034. 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: Pre-existing DICOM CT or MR images from a PACS or scanner plus non-DICOM medical data; Cardio uses multi-slice, multi-phase, and velocity-encoded cardiovascular MR; mammography is excluded.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-09 · FDA K182034: Arterys MICA

  2. Routing

    Source context, not route validation: Chrome desktop client with a Linux server; accepts DICOM/non-DICOM data from PACS or a scanner and supports DICOM-based reporting/output. The FDA packet does not establish a current cloud deployment or specific local interface versions.

    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 K182034: Arterys MICA

  3. AI processing

    Source context, not route validation: The exact FDA package describes Arterys MICA as client and server software, with the client used in a Chrome desktop web browser on standard personal and business computers and the server software running on the Linux operating system. Current hosting, data flow, and commercial configuration require vendor confirmation.

    Scope: Exact FDA submission. Packet wording: "The software has two components: i) client, and ii) server. The client software (i) can be used in a Chrome desktop web browser." … "The server software (ii) runs on the Linux operating system.". 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 K182034: Arterys MICA

  4. Returned objects

    Source context, not route validation: Filtered and digitally manipulated images, quantitative measurements, cardiac quantitative data, and oncology lesion presence/absence assessment, evaluation, quantification, follow-up, and documentation; reports can be downloaded to PACS or a computer.

    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 K182034: Arterys MICA

  5. Viewer/worklist/report

    Unresolved route: Filtered and digitally manipulated images, quantitative measurements, cardiac quantitative data, and oncology lesion presence/absence assessment, evaluation, quantification, follow-up, and documentation; reports can be downloaded to PACS or a computer.

    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 K182034: Arterys MICA

  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 Arterys MICA as client and server software, with the client used in a Chrome desktop web browser on standard personal and business computers and the server software running on the Linux operating system. Current hosting, data flow, and commercial configuration require vendor confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "The software has two components: i) client, and ii) server. The client software (i) can be used in a Chrome desktop web browser." … "The server software (ii) runs on the Linux operating system.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Integration
Chrome desktop client with a Linux server; accepts DICOM/non-DICOM data from PACS or a scanner and supports DICOM-based reporting/output. The FDA packet does not establish a current cloud deployment or specific local interface versions.
  • Exact FDA submission
  • Checked 2026-09-09
Security
Tempus's responsible disclosure policy commits to vulnerability intake for any of its assets (tempus.com and public internet-facing and cloud infrastructure it operates), coordinated handling with a 90-day disclosure window, timely correction, and a safe-harbor commitment for good-faith research. Arterys' own site states Arterys has joined Tempus as Tempus Radiology.
  • Vendor-wide
  • Checked 2026-10-27

Vendor statement. Entity bridge: arterys.com announces 'Arterys has joined Tempus... as Tempus Radiology'. The Tempus policy is an organizational vulnerability-handling statement; no certification or audit report was read, and exact-release scope is not established.

Training
The 510(k) summary states Arterys MICA is intended to be used as a support tool by trained healthcare professionals to aid in diagnosis, providing image and related information that is interpreted by a trained professional to render findings and/or diagnosis.
  • Exact FDA submission
  • Checked 2026-10-27

User qualification wording only; the summary specifies no training program or training offering for this device.

Monitoring
Tempus' responsible disclosure policy, covering Tempus assets and operated infrastructure, states vulnerability intake with a 90-day coordinated disclosure window and a timely correction commitment.
  • Vendor-wide
  • Checked 2026-10-27

Vendor statement, not an attestation. The policy names Tempus generally and does not scope these commitments to any specific product release; exact-release scope is not established.

ACR exact-submission catalog context

ACR AI Central provides an exact-submission model card for Arterys MICA; 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
K182034
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
CT/CTA; MRI
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-09
Anatomy
Heart and major vessels for the optional Cardio AI module; lung and liver lesions or nodules for the optional Oncology AI module; the base viewer handles broader radiological image data.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-09
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2018-10-17
  • 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
18Fields reviewed
9Source 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, acr ai central product, 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 K182034 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

8 sources - 3 history items

Source ledger

  1. FDA K182034: Arterys MICA

    U.S. Food and Drug Administration - Published 2018-10-17 - 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. Arterys MICA model card (K182034)

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

  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 K182034

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

    Scope: postmarketSafety

  8. Tempus: Responsible Disclosure Policy

    Tempus Labs - Accessed 2026-10-27

    Scope: security

Research history

  1. K182034 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 K192437

Arterys MICA

Arterys Inc.

Authorized purpose: Support-tool image processing for quantitative cardiovascular assessment and oncologic lesion evaluation, quantification, follow-up, and documentation to aid trained healthcare professionals in diagnosis; the software does not directly generate a diagnosis or potential findings.

Modality
CT/CTA; MRI
Anatomy
Heart and major vessels for Cardio AI; oncology lesion anatomy is not further specified in the FDA statement.
Decision
2020-03-25
FDA-cleared K242781

cvi42 Software Application

Circle Cardiovascular Imaging Inc.

Authorized purpose: View, post-process, and qualitatively and quantitatively evaluate cardiovascular MR and CT images in DICOM format to obtain diagnostic information as part of a comprehensive diagnostic decision-making process.

Modality
CT/CTA; MRI
Anatomy
Cardiovascular system; heart, coronary and adjacent vessels, and cardiac valves
Decision
2024-10-15
FDA-cleared K213998

cvi42 Auto Imaging Software Application

Circle Cardiovascular Imaging Inc

Authorized purpose: Viewing, post-processing, qualitative and quantitative evaluation, cardiac measurements, calcium scoring, and evaluation of physician-identified vascular lesions in cardiovascular MR/CT images.

Modality
CT/CTA; MRI
Anatomy
Heart and adjacent cardiovascular vessels
Decision
2022-07-28
FDA-cleared K203744

Arterys MICA

Arterys Inc.

Authorized purpose: Manages, views, processes, stores, transfers, filters, manipulates, and quantitatively measures DICOM and non-DICOM images and data, with optional Cardio AI and Oncology AI support.

Modality
CT/CTA; MRI
Anatomy
Multi-region
Decision
2022-03-14

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