FDA-cleared profile

MEDO ARIA

Medo.ai · Ultrasound · FDA-cleared (510(k))

Authorized purpose: Uses machine learning to view and quantify ultrasound image data to aid trained medical professionals in diagnosing developmental dysplasia of the hip.

Clinical role
Measurement or quantification
Images and patients
Ultrasound · Hip
Key limitation
Keep in mind: For neonates and infants age 0-12 months, with user-modifiable landmarks; submission-era cloud architecture does not establish current deployment.

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: Uses machine learning to view and quantify ultrasound image data to aid trained medical professionals in diagnosing developmental dysplasia of the hip.
  • Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Hip Input: Imported DICOM ultrasound images from scanners, including 2D and 3D ultrasound.
  • Who uses it?Intended users: Trained medical professionals and qualified users.
  • What does the software produce?Output: Alpha-angle and acetabular-coverage or distance-ratio measurements, Hip Graf classification, landmark tools, image visualization, and reports.
  • What is its most important limitation?Key limitation: For neonates and infants age 0-12 months, with user-modifiable landmarks; submission-era cloud architecture does not establish current deployment.

Clinical takeaway. Clinical role: Uses machine learning to view and quantify ultrasound image data to aid trained medical professionals in diagnosing developmental dysplasia of the hip.

Evidence takeaway. Evidence from the reviewed source record: Software verification and validation against specifications and standards, including IEC 62304 and FDA software guidance; no quantitative clinical-performance study was reported.

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
Uses machine learning to view and quantify ultrasound image data to aid trained medical professionals in diagnosing developmental dysplasia of the hip.
  • Exact FDA submission
  • Checked 2026-09-15

Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.

Workflow role
Measurement or quantification
  • Exact FDA submission
  • Checked 2026-08-31

Conservative normalization of explicit wording in an exact-submission source.

Required input
Imported DICOM ultrasound images from scanners, including 2D and 3D ultrasound.
  • Exact FDA submission
  • Checked 2026-09-15

FDA packet input scope.

Output and clinician action
Alpha-angle and acetabular-coverage or distance-ratio measurements, Hip Graf classification, landmark tools, image visualization, and reports.
  • Exact FDA submission
  • Checked 2026-09-15

FDA packet output scope.

Care setting
Pediatric
  • Exact FDA submission
  • Checked 2026-09-01

Patient-population text reported in the exact-submission ACR model card; institutional setting may still require vendor confirmation.

Intended users
Trained medical professionals and qualified users.
  • Exact FDA submission
  • Checked 2026-09-15

FDA packet user scope; do not narrow to radiologists only.

Limitations
For neonates and infants age 0-12 months, with user-modifiable landmarks; submission-era cloud architecture does not establish current deployment.
  • Exact FDA submission
  • Checked 2026-09-15

Exact packet boundary.

Evidence summary
Software verification and validation against specifications and standards, including IEC 62304 and FDA software guidance; no quantitative clinical-performance study was reported.
  • Exact FDA submission
  • Checked 2026-09-15

Packet testing description, not clinical-performance evidence.

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
Software verification and validation against specifications and standards, including IEC 62304 and FDA software guidance; no quantitative clinical-performance study was reported.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-15

Packet testing description, not clinical-performance evidence.

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 K200356. 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: Imported DICOM ultrasound images from scanners, including 2D and 3D ultrasound.

    Scope: Exact FDA submission. FDA packet input scope.

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

    Field checked 2026-09-15 · FDA K200356: MEDO ARIA

  2. Routing

    Source context, not route validation: The exact-submission ACR model card explicitly references DICOM in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.

    Scope: Exact FDA submission. Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.

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

    Field checked 2026-09-01 · MEDO ARIA model card (K200356)

  3. AI processing

    Unresolved route: Not established for the exact route.

    Scope: Exact FDA submission. The reviewed sources do not establish the current exact-release hosting topology, data flow, region, tenancy, or disaster-recovery configuration.

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

    Field checked 2026-09-09 ·

  4. Returned objects

    Source context, not route validation: Alpha-angle and acetabular-coverage or distance-ratio measurements, Hip Graf classification, landmark tools, image visualization, and reports.

    Scope: Exact FDA submission. FDA packet output scope.

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

    Field checked 2026-09-15 · FDA K200356: MEDO ARIA

  5. Viewer/worklist/report

    Unresolved route: Alpha-angle and acetabular-coverage or distance-ratio measurements, Hip Graf classification, landmark tools, image visualization, and reports.

    Scope: Exact FDA submission. FDA packet output scope.

    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-15 · FDA K200356: MEDO ARIA

  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

Integration
The exact-submission ACR model card explicitly references DICOM in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
  • Exact FDA submission
  • Checked 2026-09-01

Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.

Training
The 510(k) summary states MEDO ARIA is designed to view and quantify ultrasound image data using machine learning techniques to aid trained medical professionals in diagnosis of developmental dysplasia of the hip (DDH), and that the device is intended to be used on neonates and infants aged 0 to 12 months.
  • Exact FDA submission
  • Checked 2026-10-29

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

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

Scanner manufacturers: All

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 MEDO ARIA; 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
K200356
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
Ultrasound
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-15

FDA ultrasound scope.

Anatomy
Hip
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-15

FDA developmental-dysplasia hip scope.

Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2020-06-11
  • 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
22Fields reviewed
10Source 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, fda decision summary packet, 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 K200356 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.

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

    The reviewed sources do not establish the current exact-release hosting topology, data flow, region, tenancy, or disaster-recovery configuration.

  • 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-09 - Exact FDA submission

    Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.

  • Installation timeline: Not yet reviewed
  • 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.

7 sources - 3 history items

Source ledger

  1. FDA K200356: MEDO ARIA

    U.S. Food and Drug Administration - Published 2020-06-11 - Accessed 2026-09-09

    Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, purpose, intendedUsers, input, output, limitations, evidenceSummary

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. MEDO ARIA model card (K200356)

    American College of Radiology - Published 2026-08-17 - Accessed 2026-09-01

    Scope: intendedUsers, careSetting, output, limitations, integration, anatomy, 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 K200356

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

    Scope: postmarketSafety

Research history

  1. K200356 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 K252237

EdgeFlow UW20

Edgecare, Inc.

Authorized purpose: EdgeFlow UW20 is a wearable ultrasound system for noninvasive periodic bladder-volume measurement in adults with BMI no greater than 30.

Modality
Ultrasound
Anatomy
Urinary bladder
Decision
2026-04-17
FDA-cleared K253535

Ligence Heart

Ligence Uab

Ligence Heart is a fully automated software platform that processes, analyses and makes measurements on acquired transthoracic cardiac ultrasound images, automatically producing a full report with measurements of several key cardiac structural and functional parameters. The data produced by this software is intended to be used to support qualified cardiologists or sonographers for clinical decision making. Ligence Heart is indicated for use in adult patients. Ligence Heart has not been validated for the assessment of congenital heart disease, valve disease, pericardial disease, and/or intra-cardiac lesions (e.g., tumors, thrombi). Limitations: Poor image capture will lead to poor annotations and subsequent measurements. Multiple image quality algorithms are used to filter out images of poor quality. Our software complements good patient care and does not exempt the user from the responsibility to provide supervision, clinically review the patient, and make appropriate clinical decisions. If no gender is present, female referenced guideline values will be used for conclusions. If Body Surface Area (BSA) is not present, indexed values cannot be provided. During image acquisition, inappropriate use of the echo machine, use of non-cardiac ultrasound probes, or use of suboptimal settings (e.g., gain, contrast, depth) may lead to lower accuracy of the software. Ligence Heart has not been validated in patients with prosthetic or surgically altered cardiac valves, implantable intracardiac devices, or irregular (non-sinus) rhythm; these conditions may affect automated measurement accuracy.

Modality
Ultrasound
Anatomy
Heart/Cardiovascular
Decision
2026-02-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