FDA-cleared profile

LiverSmart

Resonance Health Analysis Services Pty Ltd · MRI · FDA-cleared (510(k))

Authorized purpose: Measures liver iron concentration for specified iron-overload and thalassemia/sickle-cell indications; assesses VLFF, PDFF, and steatosis grade for suspected or confirmed fatty liver disease; physician-interpreted results may support weight-loss monitoring and living-donor assessment.

Clinical role
Software that takes a user-uploaded zipped folder of HepaFat-AI and FerriSmart DICOM images, automatically sorts and sends the MRI datasets to those devices, and generates one summary report combining their results; no user input is required for the analysis.
Images and patients
MRI · Liver
Key limitation
Keep in mind: Required predicate-device acquisition protocols; detected input anomalies stop analysis; additional exact FDA limitations are unknown.

Overview status: Source-reviewed overview

Report a correction
Clinical details Purpose, 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: Measures liver iron concentration for specified iron-overload and thalassemia/sickle-cell indications; assesses VLFF, PDFF, and steatosis grade for suspected or confirmed fatty liver disease; physician-interpreted results may support weight-loss monitoring and living-donor assessment.
  • Which images or clinical context are in scope?Modality: MRI Anatomy or clinical context: Liver Input: A zipped folder of HepaFat-AI and FerriSmart DICOM images acquired under their respective MRI protocols; no user analysis input is required.
  • Who uses it?Intended users: Radiologists; trained physician interpretation is required for conditional fat-assessment uses.
  • What does the software produce?Output: A consolidated HTML/PDF report containing liver iron concentration, VLFF, PDFF, steatosis grade, confidence intervals, and normal ranges.
  • What is its most important limitation?Key limitation: Required predicate-device acquisition protocols; detected input anomalies stop analysis; additional exact FDA limitations are unknown.

Clinical takeaway. Clinical role: Measures liver iron concentration for specified iron-overload and thalassemia/sickle-cell indications; assesses VLFF, PDFF, and steatosis grade for suspected or confirmed fatty liver disease; physician-interpreted results may support weight-loss monitoring and living-donor assessment.

Evidence takeaway. Evidence from the reviewed source record: Special 510(k) combination of K182218 and K201039; FDA packet reports anomaly detection and identical predicate results, with no new standalone clinical-performance dataset 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
Measures liver iron concentration for specified iron-overload and thalassemia/sickle-cell indications; assesses VLFF, PDFF, and steatosis grade for suspected or confirmed fatty liver disease; physician-interpreted results may support weight-loss monitoring and living-donor assessment.
  • Exact FDA submission
  • Checked 2026-09-19

Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.

Workflow role
Software that takes a user-uploaded zipped folder of HepaFat-AI and FerriSmart DICOM images, automatically sorts and sends the MRI datasets to those devices, and generates one summary report combining their results; no user input is required for the analysis.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "LiverSmart automatically sorts and sends magnetic resonance imaging (MRI) datasets to each of the existing HepaFat-AI and FerriSmart devices and then receives results from those devices to generate a summary report" … "To conduct analysis, the user simply uploads a single zipped folder containing HepaFat-AI and FerriSmart DICOM images, acquired in accordance with their respective acquisition protocols, to the LiverSmart software. No user input is required for the analysis thereby minimising the impact of human error.". Read from the exact FDA decision document on 2026-11-14.

Required input
A zipped folder of HepaFat-AI and FerriSmart DICOM images acquired under their respective MRI protocols; no user analysis input is required.
  • Exact FDA submission
  • Checked 2026-09-19

FDA device description.

Output and clinician action
A consolidated HTML/PDF report containing liver iron concentration, VLFF, PDFF, steatosis grade, confidence intervals, and normal ranges.
  • Exact FDA submission
  • Checked 2026-09-19

FDA report-content table.

Care setting
Individuals with confirmed or suspected systemic iron overload or fatty liver disease, transfused thalassemia and sickle cell patients, weight-loss patients, and living liver donors; the FDA document does not specify a facility type.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "measure liver iron concentration in individuals with confirmed or suspected systemic iron overload; (ii) monitor liver iron burden in transfusion dependent thalassemia patients and patients with sickle cell disease receiving blood transfusions;" … "Assess the volumetric liver fat fraction, proton density fat fraction and steatosis grade in individuals with confirmed or suspected fatty liver disease.". Read from the exact FDA decision document on 2026-11-14.

Intended users
Radiologists; trained physician interpretation is required for conditional fat-assessment uses.
  • Exact FDA submission
  • Checked 2026-09-19

FDA comparison-table user and interpretation scope.

Limitations
Required predicate-device acquisition protocols; detected input anomalies stop analysis; additional exact FDA limitations are unknown.
  • Exact FDA submission
  • Checked 2026-09-19

FDA packet data-preparation and protocol boundary.

Evidence summary
Special 510(k) combination of K182218 and K201039; FDA packet reports anomaly detection and identical predicate results, with no new standalone clinical-performance dataset reported.
  • Exact FDA submission
  • Checked 2026-09-19

Submission verification summary; no independent clinical-performance claim.

Evidence

Performance evidence

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
Special 510(k) combination of K182218 and K201039; FDA packet reports anomaly detection and identical predicate results, with no new standalone clinical-performance dataset reported.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-19

Submission verification summary; no independent clinical-performance claim.

Reported sensitivity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

Reported specificity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

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 K213776. 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.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-09
Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not verified: Pricing information is recorded but not verified against a resolving source.

Reimbursement

IT implementation Deployment, 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.

Review Merge, Visage, Sectra, AGFA and IntelePACS context

Integration chain: evidence at each hop

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.

  1. Acquisition/source

    Source context, not route validation: A zipped folder of HepaFat-AI and FerriSmart DICOM images acquired under their respective MRI protocols; no user analysis input is required.

    Scope: Exact FDA submission. FDA device description.

    Confirm scanner/model, protocol, series completeness and both software builds.

    Field checked 2026-09-19 · FDA K213776: LiverSmart

  2. Routing

    Source context, not route validation: The exact-submission ACR model card explicitly references DICOM in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.

    Scope: Exact FDA submission. Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.

    Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.

    Field checked 2026-09-01 · LiverSmart model card (K213776)

  3. AI processing

    Source context, not route validation: The exact FDA package describes the LiverSmart hosting platform as cloud-based or on-site hosting in the subject-device column of its comparison table. Current hosting, data flow, and commercial configuration require vendor confirmation.

    Scope: Exact FDA submission. Packet wording: "LiverSmart (Subject Device) FerriSmart (Predicate) HepaFat-AI (Predicate)" … "Hosting platform Cloud-based or on-site hosting Cloud-based or on-site hosting Cloud-based or onsite platform". 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.

    Field checked 2026-11-14 · FDA K213776: LiverSmart

  4. Returned objects

    Source context, not route validation: A consolidated HTML/PDF report containing liver iron concentration, VLFF, PDFF, steatosis grade, confidence intervals, and normal ranges.

    Scope: Exact FDA submission. FDA report-content table.

    Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.

    Field checked 2026-09-19 · FDA K213776: LiverSmart

  5. Viewer/worklist/report

    Unresolved route: A consolidated HTML/PDF report containing liver iron concentration, VLFF, PDFF, steatosis grade, confidence intervals, and normal ranges.

    Scope: Exact FDA submission. FDA report-content table.

    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.

    Field checked 2026-09-19 · FDA K213776: LiverSmart

  6. Support owner

    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.

  1. Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
  2. Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
  3. Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
  4. Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
  5. Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
  6. Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
  7. 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.

Open the printable evaluation checklist

Deployment
The exact FDA package describes the LiverSmart hosting platform as cloud-based or on-site hosting in the subject-device column of its comparison table. Current hosting, data flow, and commercial configuration require vendor confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "LiverSmart (Subject Device) FerriSmart (Predicate) HepaFat-AI (Predicate)" … "Hosting platform Cloud-based or on-site hosting Cloud-based or on-site hosting Cloud-based or onsite platform". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Integration
The exact-submission ACR model card explicitly references DICOM in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
  • Exact FDA submission
  • Checked 2026-09-01

Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.

Input or output interoperability

DICOM is explicitly referenced in the described input, output, or workflow.

exact submission · checked 2026-09-01

The model card does not establish every supported DICOM object, transfer method, or local interface.

Supported acquisition environment

Scanner manufacturers: All

exact submission · checked 2026-09-01

Confirm currently supported software versions, protocols, and site-specific acquisition configurations.

ACR exact-submission catalog context

ACR AI Central provides an exact-submission model card for LiverSmart; FDA labeling remains controlling for clinical use, limitations, and performance.

exact submission · checked 2026-09-09
Sources & review details FDA 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.

FDA submission
K213776
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
MRI
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-19

FDA magnetic-resonance scope.

Anatomy
Liver
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-19

Exact FDA anatomical site.

Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2021-12-29
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
FDA status
FDA-cleared
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31

Research record

What has been checked

This audit distinguishes completed source review from fields that have not yet been researched.

Exact FDA record reviewedStatus
2026-09-20Last searched
23Fields reviewed
10Source 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, 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-09 - Exact FDA submission

    No public price or quote for the exact K213776 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
  • Security: Not verified - checked 2026-09-09 - 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-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.

7 sources - 3 history items

Source ledger

  1. FDA K213776: LiverSmart

    U.S. Food and Drug Administration - Published 2021-12-29 - Accessed 2026-09-09

    Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, purpose, intendedUsers, input, output, limitations, evidenceSummary, deployment

  2. Artificial Intelligence-Enabled Medical Devices

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, modalityContext

  3. LiverSmart model card (K213776)

    American College of Radiology - Published 2026-08-17 - Accessed 2026-09-01

    Scope: intendedUsers, output, limitations, integration, anatomy, implementationCapabilities

  4. PubMed biomedical literature index

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery

  5. ClinicalTrials.gov study registry

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery, studyStatus

  6. openFDA Device Recall API

    U.S. Food and Drug Administration - Accessed 2026-09-02

    Scope: recallDiscovery, nativeSubmissionMatching

  7. openFDA exact recall query for K213776

    U.S. Food and Drug Administration - Accessed 2026-09-09

    Scope: postmarketSafety

Research history

  1. K213776 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    fda record reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K253413

LiverMultiScan (v6.0)

Perspectum, Ltd.

Authorized purpose: LiverMultiScan v6.0 is MR diagnostic software for non-invasive liver-health assessment that generates, displays, and supports review of MR data and quantitative cT1, PDFF, and LIC metrics or composite images for trained healthcare-professional interpretation.

Modality
MRI
Anatomy
Liver
Decision
2026-03-09
FDA-cleared K231459

HepaFatSmart (V2.0.0)

Resonance Health Analysis Services Pty Ltd

Authorized purpose: Provide quantitative volumetric liver fat fraction, proton-density fat fraction, and steatosis grading to support clinical diagnosis and subsequent management decisions for confirmed or suspected fatty liver disease or metabolic syndromes and to aid living-donor liver-transplant assessment and screening, with results interpreted by a trained physician.

Modality
MRI
Anatomy
Liver
Decision
2023-06-20
FDA-cleared K213960

LiverMultiScan v5 (LMSv5)

Perspectum

Authorized purpose: LiverMultiScan v5 (LMSv5) is indicated for use as a magnetic resonance diagnostic device software application for noninvasive liver evaluation that enables the generation, display and review of 2D magnetic resonance medical image data and pixel maps for MR relaxation times.LMSv5 is designed to utilize DICOM 3.0 compliant magnetic resonance image datasets, acquired from compatible MRSystems, to display the internal structure of the abdomen including the liver. Other physical parameters derived from the images may also be produced.LMSv5 provides several tools, such as automated liver segmentation and region of interest (ROI) placements, to be used for the assessment of selected regions of an image. Quantitative assessment of selected regions includes the determination of triglyceride fat fraction in the liver (PDFF), T2*, LIC (Liver Iron Concentration) and iron corrected T1(cT1) measurements. These images and the physical parameters derived from the images, when interpreted by a trained clinician, yield information that may assist in diagnosis.

Modality
MRI
Anatomy
Liver
Decision
2022-09-06
FDA-cleared K203280

Hepatica v1 (Hepatica v1.0.0)

Perspectum Ltd.

Authorized purpose: Hepatica (Hepatica v1) is a post-processing medical device software that presents quantified metrics which may contribute to the assessment of a patient's liver health. Hepatica (Hepatica v1) uses image visualization and analysis tools to process DICOM 3.0 compliant magnetic resonance image datasets to produce semi-automatic segmented 3D models of the liver based on the work of Couinaud and the Brisbane 2000 terminology. For each identified Couinaud segment, volumetric data is determined and reported. Hepatica (Hepatica v1) may also report iron corrected-T1 (cT1) and PDFF calculated using the IDEAL method from multi-slice acquisitions, on a per segment basis, over the whole liver. Both metrics present numerical values of different fundamental liver tissue characteristics that can be used as measures of liver tissue health. Hepatica (Hepatica v1) provides trained clinicians with additional information to evaluate the volume and health of patient's liver on a segmental basis. It is not intended to replace the established procedures for the assessment of patient's liver health. However, information gathered through existing diagnostic tests, clinical evaluation of the patient, as well Hepatica (Hepatica v1), may support surgical decision making.

Modality
MRI
Anatomy
Liver
Decision
2021-01-12

Correct this exact record

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.

Open existing correction destination

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.

Correction policy and limits · Public repository change history