Authorized purpose: LiverMultiScan LMSv4 processes abdominal MRI, including liver images, to generate pixel maps and measurements for proton-density fat fraction, T2 star, and corrected T1, with automated liver segmentation and region-of-interest tools for trained clinician interpretation.
Clinical role
Liver segmentation, ROI selection, quantitative mapping, and non-invasive liver assessment support.
Images and patients
MRI · Abdomen including liver
Key limitation
Keep in mind: Use is limited to supported abdominal or liver MR studies and trained clinician interpretation; the FDA package states that no clinical investigation was performed for this submission.
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: LiverMultiScan LMSv4 processes abdominal MRI, including liver images, to generate pixel maps and measurements for proton-density fat fraction, T2 star, and corrected T1, with automated liver segmentation and region-of-interest tools for trained clinician interpretation.
Which images or clinical context are in scope?Modality: MRI Anatomy or clinical context: Abdomen including 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 supported abdominal or liver MR studies and trained clinician interpretation; the FDA package states that no clinical investigation was performed for this submission.
Clinical takeaway. Clinical role: LiverMultiScan LMSv4 processes abdominal MRI, including liver images, to generate pixel maps and measurements for proton-density fat fraction, T2 star, and corrected T1, with automated liver segmentation and region-of-interest tools for trained clinician interpretation.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports bench testing using purpose-built phantoms, with accuracy measured against the gold standard, and in-vivo volunteer precision testing across supported scanners, including inter and intra operator variability; it states no clinical investigations or studies were conducted. Bench cT1 limits of agreement were -189.5 to -35.11 ms at 1.5T and -187.0 to -19.12 ms at 3T. In-vivo IDEAL PDFF (ROI) limits of agreement were -1.48 to 1.42% for repeatability and -2.88 to 2.53% for reproducibility. 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
LiverMultiScan LMSv4 processes abdominal MRI, including liver images, to generate pixel maps and measurements for proton-density fat fraction, T2 star, and corrected T1, with automated liver segmentation and region-of-interest tools for trained clinician interpretation.
Use is limited to supported abdominal or liver MR studies and trained clinician interpretation; the FDA package states that no clinical investigation was performed for this submission.
The exact FDA document reports bench testing using purpose-built phantoms, with accuracy measured against the gold standard, and in-vivo volunteer precision testing across supported scanners, including inter and intra operator variability; it states no clinical investigations or studies were conducted. Bench cT1 limits of agreement were -189.5 to -35.11 ms at 1.5T and -187.0 to -19.12 ms at 3T. In-vivo IDEAL PDFF (ROI) limits of agreement were -1.48 to 1.42% for repeatability and -2.88 to 2.53% for reproducibility. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "using purpose-built phantoms containing vials with different relaxation times corresponding to the physiological range of liver tissue values expected to be seen in-vivo. Accuracy was measured by the proximity of quantified LMSv4 values to the gold standard." … "1.5T 3T Limits of Agreement cT1 -189.5 to -35.11 ms -187.0 to -19.12 ms". 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 bench testing using purpose-built phantoms, with accuracy measured against the gold standard, and in-vivo volunteer precision testing across supported scanners, including inter and intra operator variability; it states no clinical investigations or studies were conducted. Bench cT1 limits of agreement were -189.5 to -35.11 ms at 1.5T and -187.0 to -19.12 ms at 3T. In-vivo IDEAL PDFF (ROI) limits of agreement were -1.48 to 1.42% for repeatability and -2.88 to 2.53% for reproducibility. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "using purpose-built phantoms containing vials with different relaxation times corresponding to the physiological range of liver tissue values expected to be seen in-vivo. Accuracy was measured by the proximity of quantified LMSv4 values to the gold standard." … "1.5T 3T Limits of Agreement cT1 -189.5 to -35.11 ms -187.0 to -19.12 ms". Read from the exact FDA decision document on 2026-11-14.
Sensitivity is not promoted as a product-wide endpoint. 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 promoted as a product-wide endpoint. 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.
K202170 FDA evidence package for LiverMultiScan
DesignFDA 510(k) non-clinical performance testing for the exact LiverMultiScan LMSv4 configuration.
PopulationSupported abdominal MRI studies and derived liver maps.
Scopeexact submission
Tested versionLiverMultiScan configuration described in K202170
IndependenceSponsor or vendor study
K202170
The FDA package states that no clinical investigations or studies were performed for this submission.
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 K202170 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 or clinical service line and verify payer, site-of-service, coding, and coverage assumptions independently.
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 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 abdominal or liver DICOM MR studies.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The FDA package describes DICOM 3.0-compatible MR input from abdominal studies and derived image or map output.
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.
Source context, not route validation: The exact FDA package describes post-processing software designed to run on general-purpose computing hardware, where a trained operator generates a summary report that is subsequently sent to an interpreting clinician at the acquiring site. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "Both the subject and predicate devices are designed to run on general-purpose computing hardware and intended to be used in the same environment." … "from which a summary report is generated. The summary report is subsequently sent to an interpreting clinician at the acquiring site.". 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: 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.
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 post-processing software designed to run on general-purpose computing hardware, where a trained operator generates a summary report that is subsequently sent to an interpreting clinician at the acquiring site. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Both the subject and predicate devices are designed to run on general-purpose computing hardware and intended to be used in the same environment." … "from which a summary report is generated. The summary report is subsequently sent to an interpreting clinician at the acquiring site.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The FDA package describes DICOM 3.0-compatible MR input from abdominal studies and derived image or map output.
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.
Perspectum's compliance and trust page states the company has attained ISO 27001 certification for information security management systems and ISO 13485 for medical-device quality management, and adheres to UK GDPR, EU GDPR, and HIPAA with measures to safeguard personal data, with dedicated teams continuously assessing and updating security practices.
Vendor-wide
Checked 2026-10-27
Vendor statement; certificates were not read. Applicant name variants (Perspectum, Perspectum Ltd/LTD, Perspectum Diagnostics Ltd) are bridged via the identical distinctive name and LiverMultiScan/Hepatica/MRCP+ product naming on the owning domain. Exact-release scope is not established.
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.
Monitor K202170 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 supported abdominal or liver MR studies and trained clinician interpretation; the FDA package states that no clinical investigation was performed for this submission.
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.
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.
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 supported abdominal or liver MR studies and trained clinician interpretation; the FDA package states that no clinical investigation was performed for this submission.
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.
product family · checked 2026-09-04
No exact-product price was found in the reviewed public material; productivity or value claims require local evidence.
Monitor K202170 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 supported abdominal or liver MR studies and trained clinician interpretation; the FDA package states that no clinical investigation was performed for this submission.
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 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
27Fields reviewed
13Source classes checked
20Screened PubMed leads
10Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains 20 PubMed and 10 ClinicalTrials.gov candidate records. Discovery metadata alone does not establish exact tested-product, version, population, and endpoint applicability, so all candidates remain quarantined and none was promoted. The current discovery snapshot contains 20 PubMed and 10 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.
Authorized purpose: LiverMultiScan LMSv3 is MR diagnostic software for non-invasive liver evaluation from abdominal MR images, including automated liver segmentation and proton-density fat fraction, T2 star, and corrected T1 measurements.
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.
Authorized purpose: TumorSight Viz processes dynamic contrast-enhanced breast MRI for patients with biopsy-proven early-stage or locally advanced breast cancer, providing registration, subtraction, segmentation, 3D renderings, measurements, kinetic curves, parametric maps, MIPs, and reformats for physician visualization and analysis; results are not the sole basis for patient management.
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.