Authorized purpose: The EPIQ and Affiniti systems are intended for diagnostic ultrasound imaging and fluid-flow analysis of the human body. The FDA indication lists abdominal, adult, fetal and pediatric cardiac, cerebral vascular, cephalic, fetal and obstetric, gynecological, intraoperative, intraluminal, intracardiac echo, musculoskeletal, ophthalmic, urologic, pediatric, peripheral-vessel, small-organ, transesophageal, transrectal, transvaginal, and lung applications.
Clinical role
Diagnostic ultrasound acquisition, fluid or signal analysis, measurement, and image review under professional control.
Keep in mind: Use is limited by the exact system, probe, application, mode, patient, and clinical environment. The FDA material requires appropriately trained healthcare professionals and sound clinical judgment.
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: The EPIQ and Affiniti systems are intended for diagnostic ultrasound imaging and fluid-flow analysis of the human body. The FDA indication lists abdominal, adult, fetal and pediatric cardiac, cerebral vascular, cephalic, fetal and obstetric, gynecological, intraoperative, intraluminal, intracardiac echo, musculoskeletal, ophthalmic, urologic, pediatric, peripheral-vessel, small-organ, transesophageal, transrectal, transvaginal, and lung applications.
Which images or clinical context are in scope?Modality: Ultrasound Anatomy or clinical context: Fetal/obstetric, abdominal, pelvic, cardiac, vascular, cephalic, small-organ, musculoskeletal, ophthalmic, pulmonary, and urologic anatomy Input: Ultrasound data acquired with the exact labeled system, transducers, patient, application, and operating mode.
Who uses it?Intended users: Appropriately trained healthcare professionals qualified for direct use of diagnostic ultrasound devices.
What does the software produce?Output: Ultrasound images, signals, measurements, calculations, and displayed or recorded results for professional review.
What is its most important limitation?Key limitation: Use is limited by the exact system, probe, application, mode, patient, and clinical environment. The FDA material requires appropriately trained healthcare professionals and sound clinical judgment.
Clinical takeaway. Clinical role: The EPIQ and Affiniti systems are intended for diagnostic ultrasound imaging and fluid-flow analysis of the human body. The FDA indication lists abdominal, adult, fetal and pediatric cardiac, cerebral vascular, cephalic, fetal and obstetric, gynecological, intraoperative, intraluminal, intracardiac echo, musculoskeletal, ophthalmic, urologic, pediatric, peripheral-vessel, small-organ, transesophageal, transrectal, transvaginal, and lung applications.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports non-clinical software verification testing, with all tests meeting acceptance criteria, and a retrospective data analysis study comparing Auto ElastQ 2D-SWE liver stiffness measurements with manual measurements by expert readers used as ground truth; it reports high agreement meeting the study's acceptance criteria and states clinical data were not required for substantial equivalence. 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
The EPIQ and Affiniti systems are intended for diagnostic ultrasound imaging and fluid-flow analysis of the human body. The FDA indication lists abdominal, adult, fetal and pediatric cardiac, cerebral vascular, cephalic, fetal and obstetric, gynecological, intraoperative, intraluminal, intracardiac echo, musculoskeletal, ophthalmic, urologic, pediatric, peripheral-vessel, small-organ, transesophageal, transrectal, transvaginal, and lung applications.
Use is limited by the exact system, probe, application, mode, patient, and clinical environment. The FDA material requires appropriately trained healthcare professionals and sound clinical judgment.
The exact FDA document reports non-clinical software verification testing, with all tests meeting acceptance criteria, and a retrospective data analysis study comparing Auto ElastQ 2D-SWE liver stiffness measurements with manual measurements by expert readers used as ground truth; it reports high agreement meeting the study's acceptance criteria and states clinical data were not required for substantial equivalence. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Non-clinical verification testing was conducted to address the change and performance test data were provided to support the introduction of the subject software algorithm for the Auto ElastQ software feature. All software verification tests met the acceptance criteria." … "The Auto ElastQ software feature is intended to assist users in making stiffness measurements using 2D-SWE in the liver". 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 non-clinical software verification testing, with all tests meeting acceptance criteria, and a retrospective data analysis study comparing Auto ElastQ 2D-SWE liver stiffness measurements with manual measurements by expert readers used as ground truth; it reports high agreement meeting the study's acceptance criteria and states clinical data were not required for substantial equivalence. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Non-clinical verification testing was conducted to address the change and performance test data were provided to support the introduction of the subject software algorithm for the Auto ElastQ software feature. All software verification tests met the acceptance criteria." … "The Auto ElastQ software feature is intended to assist users in making stiffness measurements using 2D-SWE in the liver". Read from the exact FDA decision document on 2026-11-14.
Sensitivity is not a product-wide endpoint for this system or software function. 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 a product-wide endpoint for this system or software function. 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.
K242020 FDA decision evidence for EPIQ Series Diagnostic Ultrasound System; Affiniti Series Diagnostic Ultrasound System
DesignFDA 510(k) substantial-equivalence review of the exact submission, device description, indications, and verification or validation documentation.
Tested versionEPIQ Series Diagnostic Ultrasound System and Affiniti Series Diagnostic Ultrasound System
IndependenceSponsor or vendor study
K242020
The FDA decision material is manufacturer-submitted regulatory evidence. It is not independent clinical validation, and local technical, clinical, privacy, security, 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 K242020 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, procedural, surgical, or diagnostic 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: Ultrasound data acquired with the exact labeled system, transducers, patient, application, and operating mode.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The exact FDA decision material does not establish a complete integration contract. Confirm DICOM, worklist, identity, interfaces, exports, routing, audit behavior, archive, and downtime locally.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Field checked 2026-09-04 ·
AI processing
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The exact FDA decision material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-04 ·
Returned objects
Source context, not route validation: Ultrasound images, signals, measurements, calculations, and displayed or recorded results for professional review.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Ultrasound images, signals, measurements, calculations, and displayed or recorded results for professional review.
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.
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 appropriately trained healthcare professionals qualified for direct use of diagnostic ultrasound devices should operate or interpret this product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor by exact hardware, software, model, algorithm, reconstruction, or configuration 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 by the exact system, probe, application, mode, patient, and clinical environment. The FDA material requires appropriately trained healthcare professionals and sound clinical judgment.
Map installed model, build, options, population, anatomy, inputs, outputs, and enabled functions to K242020 before acceptance. Later family features are not evidence for this exact submission.
The exact FDA material does not establish a complete interoperability contract. Establish and test supported input, output, identity, routing, archive, and downtime behavior locally.
The exact FDA material does not establish hosting, deployment topology, availability, upgrade path, or service responsibility. Obtain site-specific evidence before procurement.
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 by the exact system, probe, application, mode, patient, and clinical environment. The FDA material requires appropriately trained healthcare professionals and sound clinical judgment.
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. No exact-product price was found.
Monitor by exact hardware, software, model, algorithm, reconstruction, or configuration 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 by the exact system, probe, application, mode, patient, and clinical environment. The FDA material requires appropriately trained healthcare professionals and sound clinical judgment.
exact submission · checked 2026-09-04
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.
Human reviewedStatus
2026-09-20Last searched
33Fields reviewed
12Source 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, 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 or approved 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
Deployment: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact FDA decision material does not establish the complete deployment topology, hosting responsibility, availability, upgrade path, or service contract.
Integration: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact FDA decision material does not establish a complete integration contract. Confirm DICOM, worklist, identity, interfaces, exports, routing, audit behavior, archive, and downtime locally.
Authorized purpose: The 5000 Compact ultrasound systems are intended for diagnostic ultrasound imaging and fluid-flow analysis of the human body. The FDA indication lists abdominal, adult and pediatric cardiac, carotid and cerebral vascular, adult and neonatal cephalic, fetal and obstetric, gynecologic, intraoperative vascular, lung, musculoskeletal, ophthalmic, pediatric, peripheral-vessel, small-parts, transesophageal cardiac, transrectal, transvaginal, and urology applications.
Authorized purpose: The EPIQ ultrasound diagnostic system is intended for diagnostic ultrasound imaging and fluid-flow analysis of the human body. The FDA material lists abdominal, adult, fetal and pediatric cardiac, cerebral vascular, adult and neonatal cephalic, fetal and obstetric, gynecologic, intraoperative, musculoskeletal, urologic, pediatric, peripheral-vessel, small-organ, transesophageal, transrectal, transvaginal, and lung applications.
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
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.