Authorized purpose: Adjunctive assessment of severe aortic stenosis using transthoracic echocardiography data; an interpreting physician uses the output to facilitate diagnosis and must not rely on it alone for patient management.
Clinical role
Post-acquisition echocardiography decision support during physician review and final report generation, using clinician-reviewed measurements as an adjunct to current clinical practice guidelines.
Images and patients
Ultrasound · Heart, left ventricular outflow tract, and aortic valve
Key limitation
Keep in mind: Not intended for patients under 18 years of age or patients who have undergone aortic-valve replacement. A minimum input set is required for a valid probability output. Results are adjunctive and patient-management decisions must not be made solely from the device. The packet describes the algorithm as using available echo measurements rather than traditional LVOT measurements for the phenotype probability.
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: Adjunctive assessment of severe aortic stenosis using transthoracic echocardiography data; an interpreting physician uses the output to facilitate diagnosis and must not rely on it alone for patient management.
Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Heart, left ventricular outflow tract, and aortic valve Input: Resting transthoracic echocardiogram measurements plus basic patient demographics including age and body surface area from height and weight; inputs are reviewed and approved by a trained clinical user. The packet also allows CSV upload for retrospective analysis.
Who uses it?Intended users: Board-certified cardiologists who review echocardiograms during evaluation and diagnosis of structural heart disease, specifically aortic stenosis.
What does the software produce?Output: A high, medium, or low severe-AS phenotype probability based on predicted aortic valve area of 1.0 cm2 or less, plus a guideline assessment based on aortic-jet peak velocity, aortic-valve mean gradient, and aortic-valve area.
What is its most important limitation?Key limitation: Not intended for patients under 18 years of age or patients who have undergone aortic-valve replacement. A minimum input set is required for a valid probability output. Results are adjunctive and patient-management decisions must not be made solely from the device. The packet describes the algorithm as using available echo measurements rather than traditional LVOT measurements for the phenotype probability.
Clinical takeaway. Clinical role: Adjunctive assessment of severe aortic stenosis using transthoracic echocardiography data; an interpreting physician uses the output to facilitate diagnosis and must not rely on it alone for patient management.
Evidence takeaway. Evidence from the reviewed source record: FDA standalone testing used 6,268 retrospective studies with a reference standard based on U.S. board-certified cardiologist review of severe AS defined as AVA <=1.0 cm2; 2,483 were severe and 3,779 were not. The primary endpoint was AUROC 0.948 (95% CI 0.943-0.952). At the high-probability threshold, sensitivity was 0.801 (95% CI 0.786-0.818) and specificity was 0.923 (95% CI 0.915-0.932); low, medium, and high outputs also had DLRs of 0.067, 0.935, and 10.3. A separate one-site five-reader MRMC study used 200 TTE studies and reported assisted versus unassisted reader AUROC of 0.883 versus 0.865 and Fleiss kappa of 0.667 versus 0.641.
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
Adjunctive assessment of severe aortic stenosis using transthoracic echocardiography data; an interpreting physician uses the output to facilitate diagnosis and must not rely on it alone for patient management.
Post-acquisition echocardiography decision support during physician review and final report generation, using clinician-reviewed measurements as an adjunct to current clinical practice guidelines.
Resting transthoracic echocardiogram measurements plus basic patient demographics including age and body surface area from height and weight; inputs are reviewed and approved by a trained clinical user. The packet also allows CSV upload for retrospective analysis.
A high, medium, or low severe-AS phenotype probability based on predicted aortic valve area of 1.0 cm2 or less, plus a guideline assessment based on aortic-jet peak velocity, aortic-valve mean gradient, and aortic-valve area.
Routine clinical care and structural-heart-disease echocardiography; the device is described as stand-alone cloud-based software and the facility type is not specified.
Not intended for patients under 18 years of age or patients who have undergone aortic-valve replacement. A minimum input set is required for a valid probability output. Results are adjunctive and patient-management decisions must not be made solely from the device. The packet describes the algorithm as using available echo measurements rather than traditional LVOT measurements for the phenotype probability.
FDA standalone testing used 6,268 retrospective studies with a reference standard based on U.S. board-certified cardiologist review of severe AS defined as AVA <=1.0 cm2; 2,483 were severe and 3,779 were not. The primary endpoint was AUROC 0.948 (95% CI 0.943-0.952). At the high-probability threshold, sensitivity was 0.801 (95% CI 0.786-0.818) and specificity was 0.923 (95% CI 0.915-0.932); low, medium, and high outputs also had DLRs of 0.067, 0.935, and 10.3. A separate one-site five-reader MRMC study used 200 TTE studies and reported assisted versus unassisted reader AUROC of 0.883 versus 0.865 and Fleiss kappa of 0.667 versus 0.641.
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 standalone testing used 6,268 retrospective studies with a reference standard based on U.S. board-certified cardiologist review of severe AS defined as AVA <=1.0 cm2; 2,483 were severe and 3,779 were not. The primary endpoint was AUROC 0.948 (95% CI 0.943-0.952). At the high-probability threshold, sensitivity was 0.801 (95% CI 0.786-0.818) and specificity was 0.923 (95% CI 0.915-0.932); low, medium, and high outputs also had DLRs of 0.067, 0.935, and 10.3. A separate one-site five-reader MRMC study used 200 TTE studies and reported assisted versus unassisted reader AUROC of 0.883 versus 0.865 and Fleiss kappa of 0.667 versus 0.641.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
EchoSolv AS regulatory performance study summary
DesignStand-alone performance and reader study (ACR AI Central category)
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K241245
Samplen=6268
IndependenceIndependence not established
K241245
ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.
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 K241245. 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.
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: Resting transthoracic echocardiogram measurements plus basic patient demographics including age and body surface area from height and weight; inputs are reviewed and approved by a trained clinical user. The packet also allows CSV upload for retrospective analysis.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: Standalone cloud-based software using third-party systems for input and output; it can send datasets to the application and integrate outputs into end-user PACS or reporting software. CSV input is for retrospective analysis only. Exact interfaces, hosting boundaries, and local compatibility are not established.
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: The exact FDA package describes EchoSolv AS as standalone, cloud-based decision support software. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "EchoSolv AS is a standalone, cloud-based decision support software which is intended to be used by board certified". 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.
Source context, not route validation: A high, medium, or low severe-AS phenotype probability based on predicted aortic valve area of 1.0 cm2 or less, plus a guideline assessment based on aortic-jet peak velocity, aortic-valve mean gradient, and aortic-valve area.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: A high, medium, or low severe-AS phenotype probability based on predicted aortic valve area of 1.0 cm2 or less, plus a guideline assessment based on aortic-jet peak velocity, aortic-valve mean gradient, and aortic-valve area.
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.
The exact FDA package describes EchoSolv AS as standalone, cloud-based decision support software. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "EchoSolv AS is a standalone, cloud-based decision support software which is intended to be used by board certified". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Standalone cloud-based software using third-party systems for input and output; it can send datasets to the application and integrate outputs into end-user PACS or reporting software. CSV input is for retrospective analysis only. Exact interfaces, hosting boundaries, and local compatibility are not established.
Echo IQ's trust center states a SOC 2 Type II program and independently verified HIPAA compliance for protecting the confidentiality, integrity and availability of customer data.
Vendor-wide
Checked 2026-10-27
Vendor trust center statements (trust.echoiq.ai); underlying attestations are request-gated and were not read. Exact-release scope is not established.
ACR AI Central provides an exact-submission model card for EchoSolv AS; FDA labeling remains controlling for clinical use, limitations, and performance.
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.
Exact FDA record reviewedStatus
2026-09-20Last searched
24Fields 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-08 - Exact FDA submission
No public price or quote for the exact K241245 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-08 - 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-08 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
Monitoring: Not verified - checked 2026-09-08 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
Authorized purpose: Alturion Series diagnostic ultrasound systems acquire and display ultrasound images and fluid-flow information for the labeled fetal, abdominal, cardiac, cephalic, obstetric, musculoskeletal, ophthalmic, urologic, vascular, small-organ, and lung examinations.
Modality
Ultrasound
Anatomy
Fetus; abdomen; pelvis; small organs; head; heart; peripheral vessels; musculoskeletal anatomy; ophthalmic; urologic organs; and lung
Authorized purpose: WatchMate Software v1.2.0 processes transesophageal echocardiography data to reconstruct the left atrial appendage and assist preprocedural planning and device sizing during left-atrial-appendage closure.
Authorized purpose: Guides medical professionals acquiring ten standard 2D transthoracic echocardiographic views in adults requiring a cardiac ultrasound examination; acquired images require qualified clinical interpretation.
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.