Authorized purpose: SubtleSYNTH is a software medical device consisting of a machine-learning algorithm that synthesizes a SynthSTIR contrast image from T1-weighted and T2-weighted spine MR images.
Clinical role
Medical-image processing, segmentation, enhancement, measurement, quantification, visualization, or reporting support under professional review.
Images and patients
MRI · Spine
Key limitation
Keep in mind: The synthesized image is dependent on the exact input sequences, scanner, patient, anatomy, and released software. It must be reviewed with the source images and does not establish universal diagnostic performance or clinical outcomes.
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: SubtleSYNTH is a software medical device consisting of a machine-learning algorithm that synthesizes a SynthSTIR contrast image from T1-weighted and T2-weighted spine MR images.
Which images or clinical context are in scope?Modality: MRI Anatomy or clinical context: Spine Input: Supported medical images, DICOM metadata, patient and protocol information, and release-specific user inputs.
Who uses it?Intended users: Qualified healthcare professionals trained for the exact represented anatomy, modality, and workflow.
What does the software produce?Output: Images, segmentations, measurements, models, calculations, overlays, or reports that require professional review.
What is its most important limitation?Key limitation: The synthesized image is dependent on the exact input sequences, scanner, patient, anatomy, and released software. It must be reviewed with the source images and does not establish universal diagnostic performance or clinical outcomes.
Clinical takeaway. Clinical role: SubtleSYNTH is a software medical device consisting of a machine-learning algorithm that synthesizes a SynthSTIR contrast image from T1-weighted and T2-weighted spine MR images.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA 510(k) decision material for K241329 identifies SubtleSYNTH (1.x) and describes the indicated use summarized in this dossier. It is regulatory evidence for the exact submission, not independent clinical validation. No performance or outcome claim is promoted without exact product and version linkage.
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
SubtleSYNTH is a software medical device consisting of a machine-learning algorithm that synthesizes a SynthSTIR contrast image from T1-weighted and T2-weighted spine MR images.
The synthesized image is dependent on the exact input sequences, scanner, patient, anatomy, and released software. It must be reviewed with the source images and does not establish universal diagnostic performance or clinical outcomes.
The exact FDA 510(k) decision material for K241329 identifies SubtleSYNTH (1.x) and describes the indicated use summarized in this dossier. It is regulatory evidence for the exact submission, not independent clinical validation. No performance or outcome claim is promoted without exact product and version linkage.
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 510(k) decision material for K241329 identifies SubtleSYNTH (1.x) and describes the indicated use summarized in this dossier. It is regulatory evidence for the exact submission, not independent clinical validation. No performance or outcome claim is promoted without exact product and version linkage.
Sensitivity is not a product-wide endpoint for this system or software function. Compare only an exact endpoint, threshold, population, version, and source if later verified.
Reported specificity
Not applicable
Not applicable
Not applicable
Checked 2026-09-04
Specificity is not a product-wide endpoint for this system or software function. Compare only an exact endpoint, threshold, population, version, and source if later verified.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K241329 FDA decision evidence for SubtleSYNTH (1.x)
DesignFDA 510(k) substantial-equivalence review of the exact submission, device description, indications, and verification or validation documentation.
PopulationSpine
Scopeexact submission
Tested versionSubtleSYNTH (1.x)
IndependenceSponsor or vendor study
K241329
The FDA decision material is manufacturer-submitted regulatory evidence. It is not independent clinical validation, and local technical, clinical, privacy, security, and workflow acceptance remains necessary.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
The 2026-09-02 openFDA device-recall snapshot contained no record matched to K241329 by exact native submission identifier. This does not exclude product-family, later, or adverse-event information.
Public source
Exact FDA submission
Checked 2026-09-04
Exact-identifier review does not prove absence of all product-family safety signals.
No separate named-product Medicare payment was identified in the reviewed CMS coverage material. Evaluate the product within the applicable imaging, procedural, surgical, or diagnostic service line and verify payer, site-of-service, and coding assumptions independently.
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: Supported medical images, DICOM metadata, patient and protocol information, and release-specific user inputs.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact FDA package describes studies sent from the scanner via DICOM to a compatible medical device data system (MDDS), which makes images available to SubtleSYNTH and sends the SynthSTIR image back to PACS or another DICOM node. Interface versions and local compatibility require confirmation.
Scope: Exact FDA submission. Packet wording: "Once a MR scan is acquired, a technologist sends the study from the scanner to a compatible medical device data system (MDDS) via the DICOM protocol." … "The compatible MDDS, then, makes the images available to SubtleSYNTH for processing.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The exact FDA decision material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-04 ·
Returned objects
Source context, not route validation: Images, segmentations, measurements, models, calculations, overlays, or reports that require professional review.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Images, segmentations, measurements, models, calculations, overlays, or reports that require professional review.
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 studies sent from the scanner via DICOM to a compatible medical device data system (MDDS), which makes images available to SubtleSYNTH and sends the SynthSTIR image back to PACS or another DICOM node. Interface versions and local compatibility require confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Once a MR scan is acquired, a technologist sends the study from the scanner to a compatible medical device data system (MDDS) via the DICOM protocol." … "The compatible MDDS, then, makes the images available to SubtleSYNTH for processing.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Subtle Medical's current compliance page lists an annual SOC 2 Type II + HIPAA security audit, and ISO 13485:2016 (valid until 2027-07-12) and ISO/IEC 42001:2023 (valid until 2028-07-17) certificates. The page gives no audit period or report scope, and the SOC 2 report was not read.
Vendor-wide
Checked 2026-10-25
Vendor-wide statement, not an independent attestation. It does not establish certificate or report scope for this exact release, expiry, data location, retention, identity and access, or incident-response terms for a deployed configuration. Obtain these from the vendor.
Only qualified healthcare professionals trained for the exact represented anatomy, modality, and workflow should operate or interpret this product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor by exact hardware, software, model, algorithm, reconstruction, or configuration version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates. Track these product-specific limits: The synthesized image is dependent on the exact input sequences, scanner, patient, anatomy, and released software. It must be reviewed with the source images and does not establish universal diagnostic performance or clinical outcomes.
Map installed model, build, options, population, anatomy, inputs, outputs, and enabled functions to K241329 before acceptance. Later family features are not evidence for this exact submission.
The exact FDA material does not establish a complete interoperability contract. Establish and test supported input, output, identity, routing, archive, and downtime behavior locally.
The exact FDA material does not establish hosting, deployment topology, availability, upgrade path, or service responsibility. Obtain site-specific evidence before procurement.
Use a signed local test set for the supported population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. The synthesized image is dependent on the exact input sequences, scanner, patient, anatomy, and released software. It must be reviewed with the source images and does not establish universal diagnostic performance or clinical outcomes.
exact submission · checked 2026-09-04
Define stop-use, escalation, rollback, and revalidation triggers before production use.
Model capital and recurring cost against net staff time after review, throughput, repeat imaging or rework, room time, consumables, infrastructure, training, service, downtime, upgrade, and replacement costs. No exact-product price was found.
Monitor by exact hardware, software, model, algorithm, reconstruction, or configuration version; patient population; anatomy; protocol; operator; input quality; output edits or overrides; failed studies; repeat acquisition or rework; downstream impact; downtime; incidents; recalls; and updates. Track these product-specific limits: The synthesized image is dependent on the exact input sequences, scanner, patient, anatomy, and released software. It must be reviewed with the source images and does not establish universal diagnostic performance or clinical outcomes.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes.
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.
Human reviewedStatus
2026-09-20Last searched
33Fields reviewed
13Source 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, vendor product page, fda decision material, peer reviewed literature, clinical trial registry, reimbursement policy, 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 publicly available - checked 2026-09-04 - Exact FDA submission
No public list price for the exact cleared or approved configuration was found. Obtain a written quote separating hardware or license basis, implementation, interfaces, infrastructure, training, service, upgrades, renewal, consumables, and exit costs.
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
Deployment: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact FDA decision material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
Authorized purpose: Semi-automatic lumbar MRI segmentation and area and distance measurements with radiologist-approved PDF report to PACS; adjunct only.
Authorized purpose: MRI-based BoneMRI v1.6 image enhancement for visualizing pelvic and L3-S1 lumbar bone structures with enhanced contrast; not for tumor diagnosis or monitoring and not a CT replacement.
Authorized purpose: CoLumbo is an image post-processing and measurement software tool that provides quantitative spine measurements from previously-acquired DICOM lumbar spine Magnetic Resonance (MR) images for users' review, analysis, and interpretation. It provides the following functionality to assist users in visualizing, measuring and documenting out-of range measurements:- Feature segmentation;- Feature measurement;- Threshold-based labeling of out-of-range measurement; and- Export of measurement results to a written report for user's review, revise and approval. Columbo does not produce or recommend any type of medical diagnosis or treatment. Instead, it simply helps users to more easily identify and classify features in lumbar MR images and compile a report. The user is responsible forconfirming/modifying settings, reviewing and verifying the software-generated measurements, inspecting out-of-range measurements, and approving draft report content using their medical judgment and discretion. The device is intended to be used only by hospitals and other medical institutions. Only DICOM images of MRI acquired from lumbar spine exams of patients aged 18 and above are considered to be valid input. CoLumbo does not support DICOM images of patients that are pregnant, undergo MRI scan with contrast media, or have post-operational complications, scoliosis, tumors, infections, fractures.
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.