Authorized purpose: Lumify Lung Application 3 assesses pleural-line appearance and lung-view quality in adults at least 18 years old using compatible Android devices and specified probes; it does not replace clinician interpretation.
Clinical role
Ultrasound acquisition, measurement, analysis, reporting, and release-specific AI assistance.
Images and patients
Ultrasound · Lung
Key limitation
Keep in mind: The Lung Application 3 is intended to assist in evaluations of adult patients (18 years and older); the appearance of the pleural line may provide non-diagnostic, contextual information when interpreted alongside other ultrasound features.
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: Lumify Lung Application 3 assesses pleural-line appearance and lung-view quality in adults at least 18 years old using compatible Android devices and specified probes; it does not replace clinician interpretation.
Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Lung Input: Incoming ultrasound frames from a compatible Android-based commercial off-the-shelf device connected to Lumify transducers (C5-2, S4-1, and L12-4 models).
Who uses it?Intended users: Trained professionals in clinical settings; healthcare professionals.
What does the software produce?Output: The application evaluates the adequacy of ultrasound frames and assesses the appearance of pleural lines as normal or irregular, with real-time feedback via visual indicators.
What is its most important limitation?Key limitation: The Lung Application 3 is intended to assist in evaluations of adult patients (18 years and older); the appearance of the pleural line may provide non-diagnostic, contextual information when interpreted alongside other ultrasound features.
Clinical takeaway. Clinical role: Lumify Lung Application 3 assesses pleural-line appearance and lung-view quality in adults at least 18 years old using compatible Android devices and specified probes; it does not replace clinician interpretation.
Evidence takeaway. Evidence from the reviewed source record: K252557 reports clinical performance and software validation that met prespecified acceptance criteria for pleural-line and view-quality functions; the public summary does not provide complete numerical tables.
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
Lumify Lung Application 3 assesses pleural-line appearance and lung-view quality in adults at least 18 years old using compatible Android devices and specified probes; it does not replace clinician interpretation.
Exact FDA submission
Checked 2026-09-19
Clinical-use display mirrors the exact FDA-supported purpose reconciled from the decision-summary packet.
Incoming ultrasound frames from a compatible Android-based commercial off-the-shelf device connected to Lumify transducers (C5-2, S4-1, and L12-4 models).
Exact FDA submission
Checked 2026-09-19
This replaces the current imported-data wording with the packet's stated Android host, transducer, and incoming-frame description.
The application evaluates the adequacy of ultrasound frames and assesses the appearance of pleural lines as normal or irregular, with real-time feedback via visual indicators.
Exact FDA submission
Checked 2026-09-19
The packet describes frame adequacy, pleural-line classification, and visual feedback; it does not state the current measurements, calculations, overlays, and reports.
The Lung Application 3 is intended to assist in evaluations of adult patients (18 years and older); the appearance of the pleural line may provide non-diagnostic, contextual information when interpreted alongside other ultrasound features.
Exact FDA submission
Checked 2026-09-19
This preserves the packet's adult and non-diagnostic-context limits and removes the current unsupported replacement-for-diagnosis wording.
K252557 reports clinical performance and software validation that met prespecified acceptance criteria for pleural-line and view-quality functions; the public summary does not provide complete numerical tables.
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
K252557 reports clinical performance and software validation that met prespecified acceptance criteria for pleural-line and view-quality functions; the public summary does not provide complete numerical tables.
Sensitivity is not the primary endpoint for this acquisition, reconstruction, segmentation, guidance, or quantitative function. Use the task-specific evidence below.
Reported specificity
Not applicable
Not applicable
Not applicable
Checked 2026-09-03
Specificity is not the primary endpoint for this acquisition, reconstruction, segmentation, guidance, or quantitative function. Use the task-specific evidence below.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K252557 FDA performance package for Lumify Diagnostic Ultrasound System
DesignManufacturer clinical performance and software validation
PopulationAdults at least 18 years old undergoing supported lung ultrasound
Scopeexact submission
Tested versionLumify Lung Application 3
IndependenceSponsor or vendor study
K252557
Manufacturer evidence submitted for clearance or approval; local clinical, technical, and workflow acceptance remains necessary.
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 K252557 by exact submission identifier. This does not exclude product-family or later safety information.
Public source
Exact FDA submission
Checked 2026-09-03
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, procedural, or surgical service line and verify payer, site-of-service, and coding 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: Incoming ultrasound frames from a compatible Android-based commercial off-the-shelf device connected to Lumify transducers (C5-2, S4-1, and L12-4 models).
Scope: Exact FDA submission. This replaces the current imported-data wording with the packet's stated Android host, transducer, and incoming-frame description.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: Validate supported probes and host devices, patient matching, DICOM or local export, PACS measurements, worklist, report transfer, and offline or downtime behavior.
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: Ultrasound hardware or software with supported probes, host devices, licensed options, and network configuration.
Scope: Exact FDA submission.
Confirm processing location, queue ownership, exclusions and exact AI build.
Source context, not route validation: The application evaluates the adequacy of ultrasound frames and assesses the appearance of pleural lines as normal or irregular, with real-time feedback via visual indicators.
Scope: Exact FDA submission. The packet describes frame adequacy, pleural-line classification, and visual feedback; it does not state the current measurements, calculations, overlays, and reports.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: The application evaluates the adequacy of ultrasound frames and assesses the appearance of pleural lines as normal or irregular, with real-time feedback via visual indicators.
Scope: Exact FDA submission. The packet describes frame adequacy, pleural-line classification, and visual feedback; it does not state the current measurements, calculations, overlays, and reports.
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.
Validate supported probes and host devices, patient matching, DICOM or local export, PACS measurements, worklist, report transfer, and offline or downtime behavior.
Philips' Responsible Disclosure Statement states that Philips maintains a global network of product security officers for developing and deploying security and privacy features for its products and services and for managing security events; that vulnerability reports to productsecurity@philips.com (PGP-encrypted) are acknowledged within two business days with a tracking number and an assigned contact; status updates approximately every 2-3 weeks; a 90-day resolution aim; and patch or advisory notification through existing customer notification processes. Vendor statement; no certification or test report was read.
Vendor-wide
Checked 2026-10-26
Vendor statement, not an attestation. Identity bridge: the statement is on philips.com (Royal Philips) and covers Philips products and services; the FDA applicant entity appears in Philips' own BCR members list on documents.philips.com (Philips Ultrasound LLC, Philips Medical Systems Nederland B.V., Philips Healthcare (Suzhou), Philips Medical Systems DMC GmbH, Philips Medical Systems Technologies Ltd., Philips Oy). Corporate policy; exact-release scope is not established.
Only qualified physicians, sonographers, and other trained ultrasound professionals. should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor by exact hardware, software and model 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: For adults aged 18 years or older; output does not replace clinician image-quality review, diagnosis, or management and requires a supported Android host and C5-2, S4-1, or L12-4 probe.
Validate supported probes and host devices, patient matching, DICOM or local export, PACS measurements, worklist, report transfer, and offline or downtime behavior.
exact submission · checked 2026-09-03
Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.
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. For adults aged 18 years or older; output does not replace clinician image-quality review, diagnosis, or management and requires a supported Android host and C5-2, S4-1, or L12-4 probe.
exact submission · checked 2026-09-03
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-03
Vendor productivity claims are scenario inputs, not guaranteed local savings.
Monitor by exact hardware, software and model 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: For adults aged 18 years or older; output does not replace clinician image-quality review, diagnosis, or management and requires a supported Android host and C5-2, S4-1, or L12-4 probe.
exact submission · checked 2026-09-03
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes.
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
27Fields reviewed
12Source classes checked
0Screened PubMed leads
1Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains 0 PubMed and 1 ClinicalTrials.gov candidate record. 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 0 PubMed and 1 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, fda decision material, vendor product page, reimbursement policy, fda device recall, fda decision summary packet, 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-03 - Exact FDA submission
No public list price for the exact cleared configuration was found. Obtain a written quote separating hardware or license basis, enabled features, implementation, interfaces, infrastructure, training, service, upgrades, renewal, consumables, and exit costs.
Authorized purpose: Alturion Series diagnostic ultrasound systems acquire and display ultrasound images and fluid-flow information for the labeled fetal, abdominal, cardiac, cephalic, obstetric, musculoskeletal, ophthalmic, urologic, vascular, small-organ, and lung examinations.
Modality
Ultrasound
Anatomy
Fetus; abdomen; pelvis; small organs; head; heart; peripheral vessels; musculoskeletal anatomy; ophthalmic; urologic organs; and lung
Authorized purpose: Supervised automatic ultrasound image acquisition of hand and wrist joints in adults being investigated or monitored for musculoskeletal disease.
Authorized purpose: WatchMate Software v1.2.0 processes transesophageal echocardiography data to reconstruct the left atrial appendage and assist preprocedural planning and device sizing during left-atrial-appendage closure.
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.