Accessory acquisition, reconstruction, and display of cardiovascular MR images on compatible 1.5T and 3T whole-body MRI systems for trained-physician interpretation.
Clinical role
Accessory MRI acquisition, reconstruction, and display for cardiovascular MR examinations.
Images and patients
MRI · Heart/Cardiovascular
Key limitation
The software is an accessory to specified compatible MRI systems; trained-physician interpretation remains required and compatibility outside the labeled systems is not established.
Overview status: Field-derived fact summary This section is assembled from the sourced field records below; it is not a source-reviewed editorial overview.
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
Imaging and anatomyMRI · Heart/Cardiovascular
Workflow roleAccessory MRI acquisition, reconstruction, and display for cardiovascular MR examinations.
Required inputMR signal data acquired through supported RTHawk cardiovascular protocols on compatible 1.5T or 3T systems.
Output and human actionStatic and dynamic cardiovascular MR images and supported flow measurements for trained-physician interpretation.
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
Accessory acquisition, reconstruction, and display of cardiovascular MR images on compatible 1.5T and 3T whole-body MRI systems for trained-physician interpretation.
The software is an accessory to specified compatible MRI systems; trained-physician interpretation remains required and compatibility outside the labeled systems is not established.
Exact FDA submission
Checked 2026-09-19
Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.
The exact FDA document reports only non-clinical tests under design controls: code and design reviews, unit and integration level testing, verification testing including system and manual testing, safety testing including SAR, dB/dt, and acoustic noise, performance testing including SNR and uniformity, and validation testing, with the device designed to comply with FDA recognized consensus standards. The document describes no clinical testing and gives no quantitative results. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "9.0 Performance Data - Discussion of Non-Clinical Tests Design controls quality assurance measures during the development of RTHawk include:" … "Code reviews ● Design reviews ● Unit and integration level testing ● Verification testing, including System and Manual testing ● Safety testing, including SAR, dB/dt, and acoustic noise ● Performance testing, including SNR and uniformity ● Validation testing". Read from the exact FDA decision document on 2026-11-14.
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
The exact FDA document reports only non-clinical tests under design controls: code and design reviews, unit and integration level testing, verification testing including system and manual testing, safety testing including SAR, dB/dt, and acoustic noise, performance testing including SNR and uniformity, and validation testing, with the device designed to comply with FDA recognized consensus standards. The document describes no clinical testing and gives no quantitative results. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "9.0 Performance Data - Discussion of Non-Clinical Tests Design controls quality assurance measures during the development of RTHawk include:" … "Code reviews ● Design reviews ● Unit and integration level testing ● Verification testing, including System and Manual testing ● Safety testing, including SAR, dB/dt, and acoustic noise ● Performance testing, including SNR and uniformity ● Validation testing". Read from the exact FDA decision document on 2026-11-14.
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 K183274. 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: MR signal data acquired through supported RTHawk cardiovascular protocols on compatible 1.5T or 3T systems.
Scope: Exact FDA submission. Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: RTHawk operates alongside the compatible scanner console as an acquisition, reconstruction, and display accessory.
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 RTHawk running on a stand-alone Linux-based computer workstation connected by a private ethernet network to the MR scanner computer, with additional software installed on the MR scanner computer. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "RTHawk is designed to run on a stand-alone linux-based computer workstation, color monitor, keyboard and mouse." … "A private ethernet network connects the RTHawk workstation to the MR scanner computer.". 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: Static and dynamic cardiovascular MR images and supported flow measurements for trained-physician interpretation.
Scope: Exact FDA submission. Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Static and dynamic cardiovascular MR images and supported flow measurements for trained-physician interpretation.
Scope: Exact FDA submission. Exact FDA decision-summary packet reviewed on 2026-09-19; existing wording is supported without expansion.
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 RTHawk running on a stand-alone Linux-based computer workstation connected by a private ethernet network to the MR scanner computer, with additional software installed on the MR scanner computer. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "RTHawk is designed to run on a stand-alone linux-based computer workstation, color monitor, keyboard and mouse." … "A private ethernet network connects the RTHawk workstation to the MR scanner computer.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The 510(k) summary states that when interpreted by a trained physician, the images produced by RTHawk provide information that may assist in the determination of a diagnosis.
Exact FDA submission
Checked 2026-10-27
User qualification wording only; the summary specifies no training program or training offering for this device.
Vista AI describes RTHawk as a real-time MRI acquisition and reconstruction engine; the reviewed page is explicitly research-use context and does not establish current clinical configuration terms.
product family · checked 2026-09-08
Confirm exact-release availability, interfaces, hosting, security, support, and commercial terms during procurement.
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-19Last searched
20Fields reviewed
10Source classes checked
0Awaiting review PubMed leads
0Awaiting review trial leads
0Unreviewed FDA recall leads
Recovered from the prior exact-submission extraction and normalized under the current provenance rules. Exact FDA support assessed on 2026-09-19. Packet-supported facts: purpose, modality, anatomy, input, output, limitations; packet-unavailable facts: intendedUsers, evidenceSummary. Candidate literature and postmarket candidates remain in their existing review state. Automated exact-name discovery found 0 PubMed and 0 ClinicalTrials.gov candidate records. Candidates require human product and version matching; zero candidates is not evidence that no studies exist. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.
Candidate leads remain unpublished until a human confirms the exact product and tested version.
Source classes: fda ai list, fda decision summary, vendor research page, 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-08 - Exact FDA submission
No public price or quote for the exact K183274 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
Security: Not verified - checked 2026-09-08 - 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-08 - Exact FDA submission
Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.
Authorized purpose: Myomics assists qualified medical professionals with viewing, post-processing and qualitative/quantitative evaluation of 3T cardiovascular MR images in DICOM format, including heart and adjacent-vessel measurements; semi-automated machine-learning workflows are intended for adults and contribute to comprehensive diagnostic decision-making.
Sonic DL is deep-learning MRI reconstruction for highly undersampled or accelerated cardiac acquisitions on compatible GE 1.5T and 3.0T MRI systems for pediatric and adult patients.
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.