Authorized purpose: AIRAscore automatically labels, visualizes and quantifies segmentable brain structures from MR images, replacing manual volume measurement and providing reference-adjusted reports and annotated images for expert physician evaluation.
Clinical role
Segmentation and volumetric measurement
Images and patients
MRI · Brain
Key limitation
Keep in mind: Incoming MRI must meet technical requirements. Expert physicians evaluate reports and control images. Networks remain static during a software version. The described input is single-time-point T1 with optional FLAIR, not the predicate's CT or longitudinal input scope.
Clinical detailsPurpose, 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: AIRAscore automatically labels, visualizes and quantifies segmentable brain structures from MR images, replacing manual volume measurement and providing reference-adjusted reports and annotated images for expert physician evaluation.
Which images or clinical context are in scope?Modality: MRI Anatomy or clinical context: Brain Input: DICOM T1-weighted and optional FLAIR MR images from a single time point, checked against technical requirements before segmentation.
Who uses it?Intended users: Licensed physicians with expert knowledge in neuroanatomy and MR imaging of the head
What does the software produce?Output: Encapsulated PDF DICOM reports and Secondary Capture annotated images; structure reports include raw/intracranial-volume-relative values and reference percentiles. AIRAscore MS additionally reports white-matter lesion number, volume and juxtacortical/periventricular/infratentorial categories.
What is its most important limitation?Key limitation: Incoming MRI must meet technical requirements. Expert physicians evaluate reports and control images. Networks remain static during a software version. The described input is single-time-point T1 with optional FLAIR, not the predicate's CT or longitudinal input scope.
Clinical takeaway. Clinical role: AIRAscore automatically labels, visualizes and quantifies segmentable brain structures from MR images, replacing manual volume measurement and providing reference-adjusted reports and annotated images for expert physician evaluation.
Evidence takeaway. Evidence from the reviewed source record: Exact-submission technical validation is described without enough numerical detail for comparative performance. Stored publications remain unresolved version leads.
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
AIRAscore automatically labels, visualizes and quantifies segmentable brain structures from MR images, replacing manual volume measurement and providing reference-adjusted reports and annotated images for expert physician evaluation.
Encapsulated PDF DICOM reports and Secondary Capture annotated images; structure reports include raw/intracranial-volume-relative values and reference percentiles. AIRAscore MS additionally reports white-matter lesion number, volume and juxtacortical/periventricular/infratentorial categories.
Incoming MRI must meet technical requirements. Expert physicians evaluate reports and control images. Networks remain static during a software version. The described input is single-time-point T1 with optional FLAIR, not the predicate's CT or longitudinal input scope.
Exact FDA submission
Checked 2026-09-05
The baseline's broad scanner-manufacturer label does not establish compatibility of every scanner/protocol. Current v3.1.0 contraindications are retained separately at family scope.
Exact-submission technical validation is described without enough numerical detail for comparative performance. Stored publications remain unresolved version leads.
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
Exact-submission technical validation is described without enough numerical detail for comparative performance. Stored publications remain unresolved version leads.
Disease-detection sensitivity with tested-version and population context was not established from this volumetry summary.
Reported specificity
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-05
No numerical disease-detection specificity for K223180 was established.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K223180 AIRAscore accuracy, reproducibility and software validation
DesignManufacturer accuracy comparison to manually labeled ground truth, test-retest reproducibility and software validation
PopulationBrain MR images across target population and scanner manufacturers; sample details not reported in reviewed summary
Scopeexact submission
Tested versionAIRAscore configuration described in K223180
IndependenceSponsor or vendor study
K223180
No numerical performance estimate or independent clinical outcome is inferred.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-04
No native submission-identifier match was found in the checked openFDA radiology recall snapshot. Product-name, manufacturer, and adverse-event searches remain necessary; this does not establish that no recall or safety report exists.
Pricing & contractsPublic price, contract terms, and reimbursement
IT implementationDeployment, 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.
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.
Acquisition/source
Source context, not route validation: DICOM T1-weighted and optional FLAIR MR images from a single time point, checked against technical requirements before segmentation.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: A DICOM storage SCU sends generated reports to a defined storage SCP, usually the referring physician's PACS; annotated DICOM images support expert inspection.
Scope: Exact FDA submission.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: Software as a service running on AIRAmed internal servers, with dedicated accessory interfaces for sending and receiving DICOM data.
Scope: Exact FDA submission. Preserves the source-backed cloud baseline. Current region, retention, availability and commercial configuration need confirmation.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: Encapsulated PDF DICOM reports and Secondary Capture annotated images; structure reports include raw/intracranial-volume-relative values and reference percentiles. AIRAscore MS additionally reports white-matter lesion number, volume and juxtacortical/periventricular/infratentorial categories.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Encapsulated PDF DICOM reports and Secondary Capture annotated images; structure reports include raw/intracranial-volume-relative values and reference percentiles. AIRAscore MS additionally reports white-matter lesion number, volume and juxtacortical/periventricular/infratentorial categories.
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.
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.
Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
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.
A DICOM storage SCU sends generated reports to a defined storage SCP, usually the referring physician's PACS; annotated DICOM images support expert inspection.
The official v3.1.0-rev2 IFU describes optional DICOM SR reports (disabled by default), error reports to PACS and required physician quality review. It excludes patients under 18 and specified structural brain abnormalities, and cautions against contrast-enhanced input.
product family · checked 2026-09-05
European IFU exported April 16, 2026; no exact K223180 release linkage. These later-release functions and exclusions are not silently assigned to the 2023 clearance.
Sources & review detailsFDA 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.
This audit distinguishes completed source review from fields that have not yet been researched.
Human reviewedStatus
2026-09-05Last searched
20Fields reviewed
11Source classes checked
2Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
Stored titles/dates screened: scan-rescan software comparison and CE-certified tool in SPG4 are possible family evidence, but neither metadata record establishes the K223180 release. Live PMID 40813790 was blank; 36543827 returned a browser-check page. No publication or trial result promoted; full-text/version assessment remains unresolved. Stored trial array empty. The current discovery snapshot contains 2 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, literature index, trial registry, stored candidate metadata, stored recall candidates, 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-05 - Exact FDA submission
Reviewed FDA and vendor IFU material does not establish an exact price, unit, term, minimum commitment or included support.
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-10-26 - Exact FDA submission
Bounded web search on 2026-10-26 (query: "AIRAmed reimbursement CPT"; top results reviewed) found no vendor or payer page stating coding, coverage or payment for this product. No result was a vendor or payer page naming this product with coding or payment; any results were general billing guidance. This records what was found, not that none exists.
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 verified - checked 2026-09-05 - Exact FDA submission
A data-transfer description and current IFU are not a scoped current security attestation for the K223180 deployment.
Installation timeline: Not yet reviewed
Training: Not verified - checked 2026-09-05 - Exact FDA submission
Required physician expertise is established, but exact-release training curriculum and competency/support terms are not.
Monitoring: Not verified - checked 2026-09-05 - Exact FDA submission
Editorial acceptance questions concern segmentation quality, DICOM age/sex integrity, failed-input reports and update comparability; no monitoring service is verified.
Authorized purpose: ANDI 2.2 processes brain MR images for atlas-assisted visualization, segmentation and volumetric quantification, presenting adjunctive DICOM-readable information for trained medical professionals; it does not predict, diagnose or interpret brain health.
Authorized purpose: Morph automatically labels, visualizes, and volumetrically quantifies segmentable brain structures from MR images and may compare measurements with reference percentile data; it is adjunctive and not the sole basis for final decisions.
Authorized purpose: Brain MRI morphometry and white matter hyperintensity quantification, including normative comparison and longitudinal change assessment for clinician review.
Authorized purpose: Adjunctive quantitative brain MRI analysis that compares patient measures with normative and longitudinal references; a physician reviews all results and makes the clinical decision.
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.
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.