Authorized purpose: Adjunct to diagnostic stress echocardiography for patients undergoing assessment for coronary artery disease; an interpreting physician uses the output as information that may assist diagnosis, not as the sole basis for management.
Clinical role
User-reviewed ROI/contour and machine-learning decision-support/reporting aid for stress echocardiography; it is an adjunct and not for primary diagnosis.
Images and patients
Ultrasound · Heart, especially the left ventricle and stress-echocardiographic A2C, A4C, and mid-ventricular SAX views.
Key limitation
Keep in mind: Patient management must not rely solely on the analysis. The packet states that v1.0.2 was not validated in patients with prior CABG and is not intended for mild or moderate myocardial ischemia, coronary-disease localization, myocardial perfusion, myocardial viability, or valve disease.
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: Adjunct to diagnostic stress echocardiography for patients undergoing assessment for coronary artery disease; an interpreting physician uses the output as information that may assist diagnosis, not as the sole basis for management.
Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Heart, especially the left ventricle and stress-echocardiographic A2C, A4C, and mid-ventricular SAX views. Input: Anonymized DICOM 3.0-compliant stress-echocardiography datasets containing apical two-chamber, apical four-chamber, and mid-ventricular short-axis views at rest and peak stress, with required view labels/metadata.
Who uses it?Intended users: Interpreting physicians; trained operators review and approve the automatically generated contour traces.
What does the software produce?Output: Automatically detected LV endocardial contours reviewed and approved by trained operators, geometric parameters, and a report with a two-level categorical assessment of whether the stress-echo ROIs suggest a higher or lower possibility of significant CAD, defined in the packet as >=70% stenosis in specified coronary segments.
What is its most important limitation?Key limitation: Patient management must not rely solely on the analysis. The packet states that v1.0.2 was not validated in patients with prior CABG and is not intended for mild or moderate myocardial ischemia, coronary-disease localization, myocardial perfusion, myocardial viability, or valve disease.
Clinical takeaway. Clinical role: Adjunct to diagnostic stress echocardiography for patients undergoing assessment for coronary artery disease; an interpreting physician uses the output as information that may assist diagnosis, not as the sole basis for management.
Evidence takeaway. Evidence from the reviewed source record: FDA K201555 reports performance testing for reader improvement, inter-operator agreement, and native system performance. The primary reader-performance increase was AUROC difference 0.054 (95% CI 0.032-0.077; p=0.02), exceeding the predicate comparison. Native system AUROC was 0.927, with sensitivity 0.844 (95% CI 0.739-0.950) and specificity 0.927 (95% CI 0.878-0.976). Kendall Tau-B agreement increased from 0.58 (95% CI 0.48-0.69) unaided to 0.82 (95% CI 0.72-0.93) with EchoGo Pro (p<0.001). AUROC and agreement are distinct from sensitivity and specificity; the reviewed packet text does not state the performance cohort size.
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
Adjunct to diagnostic stress echocardiography for patients undergoing assessment for coronary artery disease; an interpreting physician uses the output as information that may assist diagnosis, not as the sole basis for management.
User-reviewed ROI/contour and machine-learning decision-support/reporting aid for stress echocardiography; it is an adjunct and not for primary diagnosis.
Automatically detected LV endocardial contours reviewed and approved by trained operators, geometric parameters, and a report with a two-level categorical assessment of whether the stress-echo ROIs suggest a higher or lower possibility of significant CAD, defined in the packet as >=70% stenosis in specified coronary segments.
Patient management must not rely solely on the analysis. The packet states that v1.0.2 was not validated in patients with prior CABG and is not intended for mild or moderate myocardial ischemia, coronary-disease localization, myocardial perfusion, myocardial viability, or valve disease.
FDA K201555 reports performance testing for reader improvement, inter-operator agreement, and native system performance. The primary reader-performance increase was AUROC difference 0.054 (95% CI 0.032-0.077; p=0.02), exceeding the predicate comparison. Native system AUROC was 0.927, with sensitivity 0.844 (95% CI 0.739-0.950) and specificity 0.927 (95% CI 0.878-0.976). Kendall Tau-B agreement increased from 0.58 (95% CI 0.48-0.69) unaided to 0.82 (95% CI 0.72-0.93) with EchoGo Pro (p<0.001). AUROC and agreement are distinct from sensitivity and specificity; the reviewed packet text does not state the performance cohort size.
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 K201555 reports performance testing for reader improvement, inter-operator agreement, and native system performance. The primary reader-performance increase was AUROC difference 0.054 (95% CI 0.032-0.077; p=0.02), exceeding the predicate comparison. Native system AUROC was 0.927, with sensitivity 0.844 (95% CI 0.739-0.950) and specificity 0.927 (95% CI 0.878-0.976). Kendall Tau-B agreement increased from 0.58 (95% CI 0.48-0.69) unaided to 0.82 (95% CI 0.72-0.93) with EchoGo Pro (p<0.001). AUROC and agreement are distinct from sensitivity and specificity; the reviewed packet text does not state the performance cohort size.
Native EchoGo Pro system sensitivity: 0.844 (95% CI 0.739-0.950) in the FDA performance testing.
FDA source
Exact FDA submission
Checked 2026-09-09
This is a native system endpoint; the primary reader AUROC delta and Kendall Tau-B agreement are separate measures, and the packet text reviewed here does not state the cohort size.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
EchoGo Pro regulatory performance study summary
DesignStand-Alone Performance
PopulationPopulation described in the exact-submission ACR model card
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K201555
IndependenceIndependence not established
K201555
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 K201555. 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: Anonymized DICOM 3.0-compliant stress-echocardiography datasets containing apical two-chamber, apical four-chamber, and mid-ventricular short-axis views at rest and peak stress, with required view labels/metadata.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: DICOM 3.0 input, Windows operation on off-the-shelf hardware, and a report returned to the physician are described; a specific PACS, RIS, EHR, routing interface, or local compatibility configuration is 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 software that shares with its predicate the technological element of operating on off-the-shelf hardware. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "the subject and predicate devices are based on the following same technological elements:" … "Operates on off the shelf hardware". 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: Automatically detected LV endocardial contours reviewed and approved by trained operators, geometric parameters, and a report with a two-level categorical assessment of whether the stress-echo ROIs suggest a higher or lower possibility of significant CAD, defined in the packet as >=70% stenosis in specified coronary segments.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Automatically detected LV endocardial contours reviewed and approved by trained operators, geometric parameters, and a report with a two-level categorical assessment of whether the stress-echo ROIs suggest a higher or lower possibility of significant CAD, defined in the packet as >=70% stenosis in specified coronary segments.
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 software that shares with its predicate the technological element of operating on off-the-shelf hardware. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "the subject and predicate devices are based on the following same technological elements:" … "Operates on off the shelf hardware". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
DICOM 3.0 input, Windows operation on off-the-shelf hardware, and a report returned to the physician are described; a specific PACS, RIS, EHR, routing interface, or local compatibility configuration is not established.
Ultromics announces it has received ISO 27001 certification for information security management, covering secure management of personal healthcare information and other data to the standard's requirements.
Vendor-wide
Checked 2026-10-27
Vendor statement (press release dated 2020-01-16); the certificate was not read. A SafeBase trust center exists at trust.ultromics.com. Applicant variants 'Ultromics Ltd' and 'Ultromics Limited' are the same distinctive name. Exact-release scope is not established.
ACR AI Central provides an exact-submission model card for EchoGo Pro; 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
23Fields reviewed
9Source classes checked
3Screened PubMed leads
1Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains 3 PubMed and 1 ClinicalTrials.gov candidate records. Discovery metadata alone does not establish exact tested-product, version, population, and endpoint applicability, so all candidates remain quarantined and none was promoted. The current discovery snapshot contains 3 PubMed and 1 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 K201555 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
Training: Not verified - checked 2026-09-09 - Exact FDA submission
Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.
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.
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.