Input or output interoperability
DICOM is explicitly referenced in the described input, output, or workflow.
exact submission · checked 2026-09-01The model card does not establish every supported DICOM object, transfer method, or local interface.
FDA-cleared profile
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.
Overview status: Source-reviewed overview
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
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 not reviewed for this FDA record.
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.
Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.
Conservative normalization of explicit wording in an exact-submission source.
FDA packet input scope.
FDA packet output scope.
Patient-population text reported in the exact-submission ACR model card; institutional setting may still require vendor confirmation.
FDA packet user scope; do not narrow to radiologists only.
Exact packet boundary.
Packet testing description, not clinical-performance evidence.
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.
Packet testing description, not clinical-performance evidence.
This field has not been curated yet.
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
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Price not public here; enter your quote
Not verified: Pricing information is recorded but not verified against a resolving source.
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.
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
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)
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 ·
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
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
Unresolved route: Not established for the exact route.
Scope: Scope not established.
Name the local, platform and AI supplier support owners and escalation path.
No tests below have been performed or accepted.
Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.
Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
User qualification wording only; the summary specifies no training program or training offering for this device.
DICOM is explicitly referenced in the described input, output, or workflow.
exact submission · checked 2026-09-01The model card does not establish every supported DICOM object, transfer method, or local interface.
Scanner manufacturers: All
exact submission · checked 2026-09-01Confirm currently supported software versions, protocols, and site-specific acquisition configurations.
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-09Regulatory identity
The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.
FDA ultrasound scope.
FDA developmental-dysplasia hip scope.
Research record
This audit distinguishes completed source review from fields that have not yet been researched.
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
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.
No public price or quote for the exact K200356 configuration was established in this review.
No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.
The reviewed sources do not establish the current exact-release hosting topology, data flow, region, tenancy, or disaster-recovery configuration.
Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
7 sources - 3 history items
Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, purpose, intendedUsers, input, output, limitations, evidenceSummary
Scope: regulatoryIdentity, modalityContext
Scope: intendedUsers, careSetting, output, limitations, integration, anatomy, implementationCapabilities
Scope: evidenceDiscovery
Scope: evidenceDiscovery, studyStatus
Scope: recallDiscovery, nativeSubmissionMatching
Scope: postmarketSafety
Regulatory record
510(k)
Research record
fda record reviewed
Editorial review
Source-reviewed editorial overlay
Alternatives
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.
Clarius Mobile Health Corp.
Authorized purpose: Semi-automated measurement of left ventricular ejection fraction during cardiac ultrasound.
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.
Exo Imaging
Authorized purpose: Provides AI-assisted cardiac, lung and abdominal quality feedback and measurements; users remain responsible for scan quality and diagnosis and must not rely solely on the software.
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 destinationPermission 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.
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