Authorized purpose: Fibresolve analyzes lung CT in patients with pulmonary symptoms to provide an adjunct diagnostic-subtype classification for suspected interstitial lung disease and support referral to a multidisciplinary discussion.
Clinical role
Adjunct lung-CT classification and referral support before invasive testing.
Images and patients
CT/CTA · Lungs and interstitial lung disease patterns
Key limitation
Keep in mind: The FDA labeling states that Fibresolve is adjunctive, must be used with history, symptoms, other tests, and professional judgment, and is not a replacement for multidisciplinary or invasive evaluation.
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: Fibresolve analyzes lung CT in patients with pulmonary symptoms to provide an adjunct diagnostic-subtype classification for suspected interstitial lung disease and support referral to a multidisciplinary discussion.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Lungs and interstitial lung disease patterns Input: DICOM-compliant lung CT studies from patients aged over 22 years with pulmonary symptoms.
Who uses it?Intended users: Clinicians qualified in care of lung disease, including clinicians caring for patients with interstitial lung disease.
What does the software produce?Output: A report containing patient and technical information and a binary result suggesting the classified disease pattern.
What is its most important limitation?Key limitation: The FDA labeling states that Fibresolve is adjunctive, must be used with history, symptoms, other tests, and professional judgment, and is not a replacement for multidisciplinary or invasive evaluation.
Clinical takeaway. Clinical role: Fibresolve analyzes lung CT in patients with pulmonary symptoms to provide an adjunct diagnostic-subtype classification for suspected interstitial lung disease and support referral to a multidisciplinary discussion.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports only non-clinical testing: software verification and validation per IEC 62304, whose results indicate the subject device is equivalent to the predicate. It also describes a predetermined change control plan under which future model modifications are evaluated via pre-specified statistical analyses to ensure, at minimum, non-inferior absolute performance. No clinical performance results are reported in the document. 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
Fibresolve analyzes lung CT in patients with pulmonary symptoms to provide an adjunct diagnostic-subtype classification for suspected interstitial lung disease and support referral to a multidisciplinary discussion.
The FDA labeling states that Fibresolve is adjunctive, must be used with history, symptoms, other tests, and professional judgment, and is not a replacement for multidisciplinary or invasive evaluation.
The exact FDA document reports only non-clinical testing: software verification and validation per IEC 62304, whose results indicate the subject device is equivalent to the predicate. It also describes a predetermined change control plan under which future model modifications are evaluated via pre-specified statistical analyses to ensure, at minimum, non-inferior absolute performance. No clinical performance results are reported in the document. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "SUMMARY OF NON-CLINICAL TESTING Software Verification and Validation (per IEC 62304) were performed to demonstrate safety based on current industry standards. The results of these tests indicate that the subject device is equivalent to the predicate device." … "Fibresolve includes a predetermined change control plan (PCCP), detailing the specific modifications (SaMD Pre-Specifications (SPS)) that may be made to the device". 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 only non-clinical testing: software verification and validation per IEC 62304, whose results indicate the subject device is equivalent to the predicate. It also describes a predetermined change control plan under which future model modifications are evaluated via pre-specified statistical analyses to ensure, at minimum, non-inferior absolute performance. No clinical performance results are reported in the document. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "SUMMARY OF NON-CLINICAL TESTING Software Verification and Validation (per IEC 62304) were performed to demonstrate safety based on current industry standards. The results of these tests indicate that the subject device is equivalent to the predicate device." … "Fibresolve includes a predetermined change control plan (PCCP), detailing the specific modifications (SaMD Pre-Specifications (SPS)) that may be made to the device". Read from the exact FDA decision document on 2026-11-14.
Do not generalize an endpoint across populations, thresholds, versions, or workflows; use only exact evidence.metrics records.
Reported specificity
Not applicable
Not applicable
Not applicable
Checked 2026-09-04
Do not generalize an endpoint across populations, thresholds, versions, or workflows; use only exact evidence.metrics records.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K252041 FDA evidence package for Fibresolve (with PCCP)
DesignFDA 510(k) decision evidence and product verification for the exact submission.
PopulationLungs and interstitial lung disease patterns
Scopeexact submission
Tested versionFibresolve with PCCP
IndependenceSponsor or vendor study
K252041
FDA-submitted evidence for the exact decision; it is not independent clinical validation and does not establish local production qualification.
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Postmarket safety review
No record matched K252041 by exact native submission identifier in the 2026-09-02 openFDA snapshot; this does not exclude product-family, later-version, or adverse-event information.
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: DICOM-compliant lung CT studies from patients aged over 22 years with pulmonary symptoms.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The FDA package describes lung CT DICOM input, a cloud image receiver API, image ingestion and analysis, and output through an API to a hospital or clinic workflow.
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 FDA package describes cloud software and API integration or manual manufacturer submission; current hosting, security, availability, retention, and contractual boundaries remain unknown.
Scope: Exact FDA submission.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: A report containing patient and technical information and a binary result suggesting the classified disease pattern.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: A report containing patient and technical information and a binary result suggesting the classified disease pattern.
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 FDA package describes cloud software and API integration or manual manufacturer submission; current hosting, security, availability, retention, and contractual boundaries remain unknown.
The FDA package describes lung CT DICOM input, a cloud image receiver API, image ingestion and analysis, and output through an API to a hospital or clinic workflow.
Use by clinicians qualified in care of lung disease, including clinicians caring for patients with interstitial lung disease. Follow the exact labeling, local training, supervision, and escalation requirements.
The FDA package describes cloud software and API integration or manual manufacturer submission; current hosting, security, availability, retention, and contractual boundaries remain unknown.
The FDA package describes lung CT DICOM input, a cloud image receiver API, image ingestion and analysis, and output through an API to a hospital or clinic workflow.
Monitor labeling, software version, complaints, recalls, failed inputs, overrides, and postmarket signals against the exact submission and installed configuration.
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-04Last searched
27Fields reviewed
11Source classes checked
8Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads
No evidence was promoted. The records name Fibresolve but do not identify the K252041 with-PCCP configuration or tested build; PMID 42587682 identifies an FDA-authorized product through the earlier DEN220040 record rather than K252041. The current discovery snapshot contains 8 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, 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 or commercial contract for the exact submission and version was identified.
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-04 - Exact FDA submission
No exact-product payer coverage or reimbursement determination was identified in reviewed public material.
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 submission do not establish the complete security posture. Request data-flow, identity, audit, encryption, retention, remote-access, vulnerability-management, backup, and incident-response evidence.
Authorized purpose: Enhanced Boundary for PCCT is a deep-learning CT processing function for improved soft-tissue delineation in routine head examinations with or without contrast.
Authorized purpose: SurgiTwin is a web pre-surgical knee-planning system that uses patient CT images to provide two-dimensional and three-dimensional planning information and a PDF report for adults older than 22.
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.