Authorized purpose: Support trained professionals in visualizing, evaluating, measuring, and reporting liver and physician-identified liver lesions on multiphase CT; it does not generate diagnoses or potential findings directly.
Clinical role
Semi-automated liver segmentation and quantitative measurement aid with manual seed-point and boundary editing and report generation.
Images and patients
CT/CTA · Liver and physician-identified liver lesions.
Key limitation
Keep in mind: Does not generate diagnoses or potential findings directly; qualified professionals make image interpretations and clinical decisions. The stated multiphase CT, slice-thickness <= 3.0 mm, adult, and DICOM scope applies. Installation and deployment are described as being carried out by VinBrain and trained technicians.
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: Support trained professionals in visualizing, evaluating, measuring, and reporting liver and physician-identified liver lesions on multiphase CT; it does not generate diagnoses or potential findings directly.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Liver and physician-identified liver lesions. Input: Multiphase DICOM CT images with slice thickness <= 3.0 mm from patients older than 22 years; contrast-enhanced CT scans were used in the reported validation.
Who uses it?Intended users: Trained professionals including physicians and technicians; VinBrain and trained technicians carry out installation and deployment.
What does the software produce?Output: Editable liver segmentation mask; manual or physician-identified lesion segmentation; liver volume, lesion volume, maximum lesion diameter, lesion position, visualization, multiplanar reconstruction, and reporting outputs.
What is its most important limitation?Key limitation: Does not generate diagnoses or potential findings directly; qualified professionals make image interpretations and clinical decisions. The stated multiphase CT, slice-thickness <= 3.0 mm, adult, and DICOM scope applies. Installation and deployment are described as being carried out by VinBrain and trained technicians.
Clinical takeaway. Clinical role: Support trained professionals in visualizing, evaluating, measuring, and reporting liver and physician-identified liver lesions on multiphase CT; it does not generate diagnoses or potential findings directly.
Evidence takeaway. Evidence from the reviewed source record: FDA K241543 reports validation on 450 contrast-enhanced CT scans from 150 patients (age 60 +/- 12) at U.S. medical institutions, with ground truth from three U.S. board-certified radiologists. Liver segmentation had mean Dice 0.9649 (95% CI 0.9631-0.9667) and HD95 1.7061 (95% CI 1.5595-1.8526). Liver-volume measurement mean volume error was 2.7269% (95% CI 2.4308%-3.0230%). Subgroup and scanner analyses were also reported; no sensitivity or specificity disease-classification endpoint was reported.
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
Support trained professionals in visualizing, evaluating, measuring, and reporting liver and physician-identified liver lesions on multiphase CT; it does not generate diagnoses or potential findings directly.
Multiphase DICOM CT images with slice thickness <= 3.0 mm from patients older than 22 years; contrast-enhanced CT scans were used in the reported validation.
Does not generate diagnoses or potential findings directly; qualified professionals make image interpretations and clinical decisions. The stated multiphase CT, slice-thickness <= 3.0 mm, adult, and DICOM scope applies. Installation and deployment are described as being carried out by VinBrain and trained technicians.
FDA K241543 reports validation on 450 contrast-enhanced CT scans from 150 patients (age 60 +/- 12) at U.S. medical institutions, with ground truth from three U.S. board-certified radiologists. Liver segmentation had mean Dice 0.9649 (95% CI 0.9631-0.9667) and HD95 1.7061 (95% CI 1.5595-1.8526). Liver-volume measurement mean volume error was 2.7269% (95% CI 2.4308%-3.0230%). Subgroup and scanner analyses were also reported; no sensitivity or specificity disease-classification endpoint was reported.
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 K241543 reports validation on 450 contrast-enhanced CT scans from 150 patients (age 60 +/- 12) at U.S. medical institutions, with ground truth from three U.S. board-certified radiologists. Liver segmentation had mean Dice 0.9649 (95% CI 0.9631-0.9667) and HD95 1.7061 (95% CI 1.5595-1.8526). Liver-volume measurement mean volume error was 2.7269% (95% CI 2.4308%-3.0230%). Subgroup and scanner analyses were also reported; no sensitivity or specificity disease-classification endpoint was reported.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
DrAid™ for Liver Segmentation regulatory performance study summary
DesignStand-Alone Performance
PopulationAdult
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K241543
Samplen=450
IndependenceIndependence not established
K241543
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 K241543. 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: Multiphase DICOM CT images with slice thickness <= 3.0 mm from patients older than 22 years; contrast-enhanced CT scans were used in the reported validation.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: Web-based application running on standard hospital/clinic workstations with DICOM CT processing, viewer/manual editing, reporting, and results export. The exact PACS, RIS, EHR interface and hosting model are not established by the packet.
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 DrAid for Liver Segmentation as a web-based application running on standard hospital/clinic workstations, with installation and deployment carried out by VinBrain and trained technicians. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "Web-based application running on standard hospital/clinic workstations" … "The installation and deployment of the software medical device should be carried out by VinBrain and trained technicians.". 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.
Unresolved route: Editable liver segmentation mask; manual or physician-identified lesion segmentation; liver volume, lesion volume, maximum lesion diameter, lesion position, visualization, multiplanar reconstruction, and reporting outputs.
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 DrAid for Liver Segmentation as a web-based application running on standard hospital/clinic workstations, with installation and deployment carried out by VinBrain and trained technicians. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Web-based application running on standard hospital/clinic workstations" … "The installation and deployment of the software medical device should be carried out by VinBrain and trained technicians.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Web-based application running on standard hospital/clinic workstations with DICOM CT processing, viewer/manual editing, reporting, and results export. The exact PACS, RIS, EHR interface and hosting model are not established by the packet.
ACR AI Central provides an exact-submission model card for DrAid™ for Liver Segmentation; 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
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 K241543 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
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: AI-CVD provides automated quantitative CT-derived anatomical and density measurements for clinician review, including calcium scores, cardiac and vascular measurements, lung and liver density, bone mineral density, and muscle/fat composition; it is opportunistic decision support, not diagnostic interpretation or risk prediction.
Authorized purpose: uOmnispace.CT provides healthcare institutions with tools to view, manipulate, evaluate, and analyze medical CT images, including colon, lung, vessel, brain, cardiac, liver, rib, spine, dual-energy, perfusion, and cardiovascular applications described in the exact FDA submission.
Modality
CT/CTA
Anatomy
Colon, lungs and airway, vessels, brain, heart, liver, ribs, spine, and other CT regions
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.