FDA-cleared profile

HepaFat-AI

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

Authorized purpose: HepaFat-AI assesses volumetric liver fat fraction, proton-density fat fraction, and steatosis grade in confirmed or suspected fatty-liver disease, supports monitoring of liver fat during weight loss, and may aid assessment or screening of living liver donors under trained physician interpretation.

Clinical role
Liver segmentation, ROI selection, quantitative mapping, and non-invasive liver assessment support.
Images and patients
MRI · Liver
Key limitation
Keep in mind: Use is limited to the labeled liver-fat and steatosis applications and trained physician interpretation; exact biopsy reference, threshold, sequence, and population limits apply.

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: HepaFat-AI assesses volumetric liver fat fraction, proton-density fat fraction, and steatosis grade in confirmed or suspected fatty-liver disease, supports monitoring of liver fat during weight loss, and may aid assessment or screening of living liver donors under trained physician interpretation.
  • Which images or clinical context are in scope?Modality: MRI Anatomy or clinical context: Liver Input: Supported abdominal or liver DICOM MR studies.
  • Who uses it?Intended users: Trained physicians and clinicians experienced in liver MRI interpretation.
  • What does the software produce?Output: Liver segmentations, ROI values, pixel maps, and liver fat or relaxation measurements.
  • What is its most important limitation?Key limitation: Use is limited to the labeled liver-fat and steatosis applications and trained physician interpretation; exact biopsy reference, threshold, sequence, and population limits apply.

Clinical takeaway. Clinical role: HepaFat-AI assesses volumetric liver fat fraction, proton-density fat fraction, and steatosis grade in confirmed or suspected fatty-liver disease, supports monitoring of liver fat during weight loss, and may aid assessment or screening of living liver donors under trained physician interpretation.

Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports software verification and validation and a clinical evaluation using HepaFat-Scan as the reference standard, including limit of agreement, NPA/PPA and repeatability assessments. HepaFat-AI and HepaFat-Scan were tested against biopsy steatosis grades using HepaFat-Scan data from two independent studies of 145 adult and paediatric NAFLD/NASH patients with liver biopsy; for Grade 0 vs Grades 1-3, HepaFat-AI sensitivity was 97.6 (93.3% to 99.2%) and specificity 88.2 (65.7% to 96.7%). Results are as reported in the FDA submission, not independent validation.

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
HepaFat-AI assesses volumetric liver fat fraction, proton-density fat fraction, and steatosis grade in confirmed or suspected fatty-liver disease, supports monitoring of liver fat during weight loss, and may aid assessment or screening of living liver donors under trained physician interpretation.
  • Exact FDA submission
  • Checked 2026-09-04
Workflow role
Liver segmentation, ROI selection, quantitative mapping, and non-invasive liver assessment support.
  • Exact FDA submission
  • Checked 2026-09-04
Required input
Supported abdominal or liver DICOM MR studies.
  • Exact FDA submission
  • Checked 2026-09-04
Output and clinician action
Liver segmentations, ROI values, pixel maps, and liver fat or relaxation measurements.
  • Exact FDA submission
  • Checked 2026-09-04
Care setting
Abdominal MRI and hepatology or radiology workflows.
  • Exact FDA submission
  • Checked 2026-09-04
Intended users
Trained physicians and clinicians experienced in liver MRI interpretation.
  • Exact FDA submission
  • Checked 2026-09-04
Limitations
Use is limited to the labeled liver-fat and steatosis applications and trained physician interpretation; exact biopsy reference, threshold, sequence, and population limits apply.
  • Exact FDA submission
  • Checked 2026-09-04
Evidence summary
The exact FDA document reports software verification and validation and a clinical evaluation using HepaFat-Scan as the reference standard, including limit of agreement, NPA/PPA and repeatability assessments. HepaFat-AI and HepaFat-Scan were tested against biopsy steatosis grades using HepaFat-Scan data from two independent studies of 145 adult and paediatric NAFLD/NASH patients with liver biopsy; for Grade 0 vs Grades 1-3, HepaFat-AI sensitivity was 97.6 (93.3% to 99.2%) and specificity 88.2 (65.7% to 96.7%). Results are as reported in the FDA submission, not independent validation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Analytical Validation: HepaFat-AI software has been developed, verified and validated following the Design Control principles" … "Valid Clinical Association: using HepaFat-Scan as the reference standard.". Read from the exact FDA decision document on 2026-11-14.

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
The exact FDA document reports software verification and validation and a clinical evaluation using HepaFat-Scan as the reference standard, including limit of agreement, NPA/PPA and repeatability assessments. HepaFat-AI and HepaFat-Scan were tested against biopsy steatosis grades using HepaFat-Scan data from two independent studies of 145 adult and paediatric NAFLD/NASH patients with liver biopsy; for Grade 0 vs Grades 1-3, HepaFat-AI sensitivity was 97.6 (93.3% to 99.2%) and specificity 88.2 (65.7% to 96.7%). Results are as reported in the FDA submission, not independent validation.
  • FDA source
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Analytical Validation: HepaFat-AI software has been developed, verified and validated following the Design Control principles" … "Valid Clinical Association: using HepaFat-Scan as the reference standard.". Read from the exact FDA decision document on 2026-11-14.

Reported sensitivity
Standalone sensitivity for any steatosis (Grade 0 vs Grades 1-3) against liver biopsy grades on 145 biopsied cases: 97.6 (95% CI 93.3% to 99.2%).
  • FDA source
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Sensitivities and specificities of HepaFat-Scan and HepaFat-AI generated for the 145 cases with biopsy at the three previously determined VLFF thresholds." … "at the clinically important boundary separating no steatosis from any steatosis (Grade 0 vs Grades 1-3), the sensitivities and specificities of HepaFat-AI are no worse than HepaFat-Scan.". Read from the exact FDA decision document on 2026-11-14; this is the submission-reported standalone result, not independent validation.

Reported specificity
Standalone specificity for any steatosis (Grade 0 vs Grades 1-3) against liver biopsy grades on 145 biopsied cases: 88.2 (95% CI 65.7% to 96.7%).
  • FDA source
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Sensitivities and specificities of HepaFat-Scan and HepaFat-AI generated for the 145 cases with biopsy at the three previously determined VLFF thresholds." … "at the clinically important boundary separating no steatosis from any steatosis (Grade 0 vs Grades 1-3), the sensitivities and specificities of HepaFat-AI are no worse than HepaFat-Scan.". Read from the exact FDA decision document on 2026-11-14; this is the submission-reported standalone result, not independent validation.

Biopsy-referenced clinical validation cohort

145 patients

  • EndpointClinical validation cohort size reported by the FDA package
  • PopulationAdult and pediatric patients with suspected or confirmed NAFLD or NASH
  • Tested versionHepaFat-AI configuration described in K201039

K201039 FDA evidence package for HepaFat-AI

  • DesignFDA 510(k) clinical validation against biopsy reference grades in two independent HepaFat-AI studies.
  • PopulationAdult and pediatric patients with suspected or confirmed NAFLD or NASH evaluated with liver MRI and biopsy reference data.
  • Scopeexact submission
  • Tested versionHepaFat-AI configuration described in K201039
  • Samplen=145
  • IndependenceSponsor or vendor study

K201039

The FDA package reports 145 patients in the described validation cohort; exact threshold metrics are not promoted here without the full table context.

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 2026-09-02 openFDA device-recall snapshot contained no record matched to K201039 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.

Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not publicly available: Reviewed sources do not publish an exact-product procurement price with a stated offer scope.

Reimbursement

Reimbursement
No separate named-product Medicare payment was identified in the reviewed CMS coverage material. Evaluate the product within the applicable imaging or clinical service line and verify payer, site-of-service, coding, and coverage assumptions independently.
  • Service-level, not product-specific
  • Checked 2026-09-04

No product-specific code

No separate named-product payment identified in reviewed public material

Centers for Medicare & Medicaid Services · United States

This is not a product-specific reimbursement determination. Build a local total-cost and value model and verify payer, site-of-service, coding, and coverage assumptions independently.

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: Supported abdominal or liver DICOM MR studies.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-04 · FDA 510(k) decision material K201039: HepaFat-AI

  2. Routing

    Source context, not route validation: The FDA package describes supported abdominal or liver MR image input; the complete local interface and output contract remain unverified.

    Scope: Exact FDA submission. This is the interface boundary described in the exact FDA package; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.

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

    Field checked 2026-09-04 · FDA 510(k) decision material K201039: HepaFat-AI

  3. AI processing

    Source context, not route validation: The exact FDA package describes a software platform to which the user uploads raw DICOM images, with its hosting platform listed as cloud-based or onsite. Current hosting, data flow, and commercial configuration require vendor confirmation.

    Scope: Exact FDA submission. Packet wording: "To carry out an analysis, the user simply uploads raw DICOM images to the HepaFat-AI Analysis System." … "Hosting platform 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 510(k) decision material K201039: HepaFat-AI

  4. Returned objects

    Source context, not route validation: Liver segmentations, ROI values, pixel maps, and liver fat or relaxation measurements.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-04 · FDA 510(k) decision material K201039: HepaFat-AI

  5. Viewer/worklist/report

    Unresolved route: Liver segmentations, ROI values, pixel maps, and liver fat or relaxation measurements.

    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.

    Field checked 2026-09-04 · FDA 510(k) decision material K201039: HepaFat-AI

  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 a software platform to which the user uploads raw DICOM images, with its hosting platform listed as cloud-based or onsite. Current hosting, data flow, and commercial configuration require vendor confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "To carry out an analysis, the user simply uploads raw DICOM images to the HepaFat-AI Analysis System." … "Hosting platform 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 FDA package describes supported abdominal or liver MR image input; the complete local interface and output contract remain unverified.
  • Exact FDA submission
  • Checked 2026-09-04

This is the interface boundary described in the exact FDA package; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.

Training
Only trained physicians and clinicians experienced in liver mri interpretation should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
  • Exact FDA submission
  • Checked 2026-09-04
Monitoring
Monitor K201039 by exact hardware, software, model, and algorithm 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: Use is limited to the labeled liver-fat and steatosis applications and trained physician interpretation; exact biopsy reference, threshold, sequence, and population limits apply.
  • Exact FDA submission
  • Checked 2026-09-04

Monitoring guidance is buyer-facing implementation guidance derived from the exact cleared scope; it is not a claim that the FDA package provides a live monitoring service.

Release and scope verification

Map installed model, build, options, population, anatomy, inputs, outputs, and enabled functions to K201039 before acceptance.

exact submission · checked 2026-09-04

Later product-family features are not evidence that this cleared release includes them.

Deployment boundary

The exact public deployment topology remains incomplete; establish hosting responsibility, data flow, availability, upgrade, service, and downtime boundaries locally.

exact submission · checked 2026-09-04

FDA-described deployment boundaries do not establish current hosting contracts, security controls, uptime, or local qualification.

Interoperability acceptance

The FDA package describes supported abdominal or liver MR image input; the complete local interface and output contract remain unverified.

exact submission · checked 2026-09-04

Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.

Clinical acceptance

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. Use is limited to the labeled liver-fat and steatosis applications and trained physician interpretation; exact biopsy reference, threshold, sequence, and population limits apply.

exact submission · checked 2026-09-04

Define stop-use, escalation, rollback, and revalidation triggers before production use.

Economic evaluation

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.

product family · checked 2026-09-04

No exact-product price was found in the reviewed public material; productivity or value claims require local evidence.

Lifecycle monitoring

Monitor K201039 by exact hardware, software, model, and algorithm 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: Use is limited to the labeled liver-fat and steatosis applications and trained physician interpretation; exact biopsy reference, threshold, sequence, and population limits apply.

exact submission · checked 2026-09-04

Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. liver MRI analysis software limits remain submission-specific.

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
K201039
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
MRI
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Anatomy
Liver
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2020-12-07
  • 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.

Human reviewedStatus
2026-09-20Last searched
27Fields 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, acr ai central product, 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 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
  • 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 publicly available - checked 2026-09-04 - Exact FDA submission

    Public materials reviewed for this exact release do not establish the complete security posture. Request data-flow, identity, audit, encryption, retention, remote-access, vulnerability-management, backup, and incident-response evidence.

  • Installation timeline: Not yet reviewed

7 sources - 3 history items

Source ledger

  1. FDA 510(k) decision material K201039: HepaFat-AI

    U.S. Food and Drug Administration - Published 2020-12-07 - Accessed 2026-09-04

    Scope: identity, purpose, clinicalUse, modality, anatomy, intendedUsers, careSetting, workflowRole, input, output, limitations, evidenceSummary

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. HepaFat-AI model card (K201039)

    American College of Radiology - Published 2026-06-26 - Accessed 2026-09-01

  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. Medicare Coverage Database

    Centers for Medicare & Medicaid Services - Accessed 2026-09-01

    Scope: coverage, codingContext

  7. openFDA Device Recall API

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

    Scope: recallDiscovery, nativeSubmissionMatching

Research history

  1. K201039 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    human 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 K213776

LiverSmart

Resonance Health Analysis Services Pty Ltd

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.

Modality
MRI
Anatomy
Liver
Decision
2021-12-29

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