Authorized purpose: MaxFOV 2 is a deep-learning CT image reconstruction method for head and whole-body axial, helical, and cine acquisitions. It extends the nominal display field of view when patient size or positioning places part of the body outside that field. Extended-field images are intended for radiation-therapy planning and may also visualize anatomy outside the field for non-therapy CT; the labeling identifies patients of all ages, especially bariatric patients.
Clinical role
CT acquisition, reconstruction, visualization, and release-specific image processing under professional review.
Images and patients
CT/CTA · Head and whole body; anatomy outside the nominal display field of view
Key limitation
Keep in mind: Use only the cleared system, software, protocol, anatomy, population, and reconstruction limits; image quality, dose, and interpretation remain the responsibility of qualified professionals.
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: MaxFOV 2 is a deep-learning CT image reconstruction method for head and whole-body axial, helical, and cine acquisitions. It extends the nominal display field of view when patient size or positioning places part of the body outside that field. Extended-field images are intended for radiation-therapy planning and may also visualize anatomy outside the field for non-therapy CT; the labeling identifies patients of all ages, especially bariatric patients.
Which images or clinical context are in scope?Modality: CT/CTA Anatomy or clinical context: Head and whole body; anatomy outside the nominal display field of view Input: X-ray transmission data acquired with the supported CT system, protocols, and patient positioning.
Who uses it?Intended users: Trained and qualified physicians and CT technologists.
What does the software produce?Output: Cross-sectional CT volumes, whole-organ volume sets, reconstructions, and spectral or quantitative views for professional review.
What is its most important limitation?Key limitation: Use only the cleared system, software, protocol, anatomy, population, and reconstruction limits; image quality, dose, and interpretation remain the responsibility of qualified professionals.
Clinical takeaway. Clinical role: MaxFOV 2 is a deep-learning CT image reconstruction method for head and whole-body axial, helical, and cine acquisitions. It extends the nominal display field of view when patient size or positioning places part of the body outside that field. Extended-field images are intended for radiation-therapy planning and may also visualize anatomy outside the field for non-therapy CT; the labeling identifies patients of all ages, especially bariatric patients.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports engineering bench testing using phantoms to evaluate image quality, including patient contour and CT number accuracy, repeated on different GE CT system platforms, and a clinical reader study of 49 CT exams scored by 5 external clinical readers on a 5 point Likert scale for skin surface depiction, tissue densities in the extended FOV region, and overall image quality, with results reported as supporting 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
MaxFOV 2 is a deep-learning CT image reconstruction method for head and whole-body axial, helical, and cine acquisitions. It extends the nominal display field of view when patient size or positioning places part of the body outside that field. Extended-field images are intended for radiation-therapy planning and may also visualize anatomy outside the field for non-therapy CT; the labeling identifies patients of all ages, especially bariatric patients.
Use only the cleared system, software, protocol, anatomy, population, and reconstruction limits; image quality, dose, and interpretation remain the responsibility of qualified professionals.
The exact FDA document reports engineering bench testing using phantoms to evaluate image quality, including patient contour and CT number accuracy, repeated on different GE CT system platforms, and a clinical reader study of 49 CT exams scored by 5 external clinical readers on a 5 point Likert scale for skin surface depiction, tissue densities in the extended FOV region, and overall image quality, with results reported as supporting substantial equivalence. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "A suite of engineering bench testing using phantoms was performed to evaluate image quality performance of MaxFOV 2." … "MaxFOV 2 Patient contour (Skin line) accuracy and CT Number accuracy". 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 engineering bench testing using phantoms to evaluate image quality, including patient contour and CT number accuracy, repeated on different GE CT system platforms, and a clinical reader study of 49 CT exams scored by 5 external clinical readers on a 5 point Likert scale for skin surface depiction, tissue densities in the extended FOV region, and overall image quality, with results reported as supporting substantial equivalence. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "A suite of engineering bench testing using phantoms was performed to evaluate image quality performance of MaxFOV 2." … "MaxFOV 2 Patient contour (Skin line) accuracy and CT Number accuracy". 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, study design, and source if separately 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, study design, and source if separately verified.
Extended display field of view
80 cm
EndpointMaximum nominal display field of view described for MaxFOV 2
PopulationPatients of all ages, especially bariatric patients, with anatomy outside the nominal display field
Tested versionMaxFOV 2 configuration described in K203617
K203617 FDA decision evidence package for MaxFOV 2
DesignFDA decision evidence including the exact submission's labeled performance or verification material; endpoints remain submission-specific.
PopulationHead and whole body; anatomy outside the nominal display field of view
Scopeexact submission
Tested versionMaxFOV 2 configuration described in K203617
IndependenceSponsor or vendor study
K203617
FDA decision material is manufacturer-submitted regulatory evidence. It is not independent clinical validation unless the exact source expressly establishes that distinction; 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 K203617 by exact native submission identifier. This does not exclude product-family, later-version, 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.
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: X-ray transmission data acquired with the supported CT system, protocols, and patient positioning.
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 public FDA decision material does not establish a complete integration contract. Confirm supported inputs, outputs, identity, routing, archive behavior, audit behavior, 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 public 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: Cross-sectional CT volumes, whole-organ volume sets, reconstructions, and spectral or quantitative views for professional review.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Cross-sectional CT volumes, whole-organ volume sets, reconstructions, and spectral or quantitative views 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.
GE HealthCare's Product Security Portal is described as a credentialed global portal giving customers security updates, vulnerability status and required actions for GE HealthCare products potentially impacted by critical vulnerabilities, plus historical patch views; GE HealthCare references its Cybersecurity Risk Management System and publishes a Coordinated Vulnerability Disclosure Statement for reporting vulnerabilities in GE HealthCare products.
Vendor-wide
Checked 2026-10-26
Vendor statement, not an attestation. Identity bridge: GE HealthCare's own Privacy Shield page on gehealthcare.com names GE Medical Systems LLC as a US entity of the GEHC group. Corporate program statement; portal content is credentialed; exact-release scope is not established.
Only trained and qualified physicians and ct technologists should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor K203617 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 only the cleared system, software, protocol, anatomy, population, and reconstruction limits; image quality, dose, and interpretation remain the responsibility of qualified professionals.
Exact FDA submission
Checked 2026-09-04
This is buyer-facing monitoring 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 topology does not establish current hosting contracts, security controls, uptime, or local qualification.
The exact public integration contract remains incomplete; establish and test supported input, output, identity, routing, archive, and downtime behavior locally.
exact submission · checked 2026-09-04
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. Use only the cleared system, software, protocol, anatomy, population, and reconstruction limits; image quality, dose, and interpretation remain the responsibility of qualified professionals.
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.
exact submission · checked 2026-09-04
No exact-product price or reimbursement determination was promoted.
Monitor K203617 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 only the cleared system, software, protocol, anatomy, population, and reconstruction limits; image quality, dose, and interpretation remain the responsibility of qualified professionals.
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.
Exact FDA record reviewedStatus
2026-09-20Last searched
27Fields reviewed
9Source 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, 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 authorized configuration was found. Obtain a written quote separating license or hardware 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
Reimbursement: Not publicly available - checked 2026-09-04 - Exact FDA submission
No exact-product reimbursement determination was promoted in this timeboxed review. Verify payer, site-of-service, coding, coverage, and local payment assumptions independently.
Deployment: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact public 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 public FDA decision material does not establish a complete integration contract. Confirm supported inputs, outputs, identity, routing, archive behavior, audit behavior, and downtime locally.
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: 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.
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.