FDA-cleared profile

DeepCatch

MEDICALIP Co., Ltd · CT/CTA · FDA-cleared (510(k))

DeepCatch analyzes whole-body CT images to segment skin, bone, muscle, visceral fat, subcutaneous fat, internal organs, and central nervous system structures, then calculates volumes, proportions, and three-dimensional models for physician confirmation.

Clinical role
Medical-image processing, measurement, quantification, visualization, and reporting support.
Images and patients
CT/CTA · Multi-region
Key limitation
Outputs supplement accepted interpretation methods and require review against source images; supported modality, anatomy, protocol, and version limits apply.

Overview status: Field-derived fact summary This section is assembled from the sourced field records below; it is not a source-reviewed editorial overview.

Report a correction
Clinical details Purpose, 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

  • Imaging and anatomyCT/CTA · Multi-region
  • Workflow roleMedical-image processing, measurement, quantification, visualization, and reporting support.
  • Required inputSupported DICOM images and release-specific user inputs.
  • Output and human actionMeasurements, segmentations, visualizations, calculations, and reports for professional review.

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
DeepCatch analyzes whole-body CT images to segment skin, bone, muscle, visceral fat, subcutaneous fat, internal organs, and central nervous system structures, then calculates volumes, proportions, and three-dimensional models for physician confirmation.
  • Exact FDA submission
  • Checked 2026-09-03
Workflow role
Medical-image processing, measurement, quantification, visualization, and reporting support.
  • Exact FDA submission
  • Checked 2026-09-03
Required input
Supported DICOM images and release-specific user inputs.
  • Exact FDA submission
  • Checked 2026-09-03
Output and clinician action
Measurements, segmentations, visualizations, calculations, and reports for professional review.
  • Exact FDA submission
  • Checked 2026-09-03
Care setting
Hospital or outpatient imaging analysis and reporting environments.
  • Exact FDA submission
  • Checked 2026-09-03
Intended users
Qualified imaging professionals and physicians trained for the represented anatomy and workflow.
  • Exact FDA submission
  • Checked 2026-09-03
Limitations
Outputs supplement accepted interpretation methods and require review against source images; supported modality, anatomy, protocol, and version limits apply.
  • Exact FDA submission
  • Checked 2026-09-03
Evidence summary
The exact FDA document reports software verification and validation and a performance test using data from Korea (562) and France (18): internal-dataset DSC means versus GT were greater than or equal to 90%, and external-dataset DSC means were more than 90%, with mean volume and area differences less than 10%. In a predicate comparison on 100 whole body CT images collected using two scanner models available in the United States, DeepCatch DSC was not inferior to MEDIP PRO. Results are as reported in the FDA submission, not independent validation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "The software was designed and developed according to a software development process and was verified and validated." … "Performance test using data set from Korea (562) and France (18) with DeepCatch". Read from the exact FDA decision document on 2026-11-14.

Evidence

Performance evidence

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 software verification and validation and a performance test using data from Korea (562) and France (18): internal-dataset DSC means versus GT were greater than or equal to 90%, and external-dataset DSC means were more than 90%, with mean volume and area differences less than 10%. In a predicate comparison on 100 whole body CT images collected using two scanner models available in the United States, DeepCatch DSC was not inferior to MEDIP PRO. Results are as reported in the FDA submission, not independent validation.
  • FDA source
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "The software was designed and developed according to a software development process and was verified and validated." … "Performance test using data set from Korea (562) and France (18) with DeepCatch". Read from the exact FDA decision document on 2026-11-14.

Reported sensitivity
Not applicable
  • Not applicable
  • Not applicable
  • Checked 2026-09-03

Sensitivity is not the primary endpoint for this system, 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 system, 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.

K223556 FDA performance package for DeepCatch

  • DesignManufacturer deep-learning segmentation, quantitative-analysis, and software validation
  • PopulationWhole-body CT examinations with physician-confirmed body-composition and organ segmentation
  • Scopeexact submission
  • Tested versionDeepCatch
  • IndependenceSponsor or vendor study

K223556

Manufacturer evidence submitted for FDA clearance or approval; local clinical, technical, and workflow acceptance remains necessary.

4 unlinked candidate evidence records are retained for source review and excluded from this evidence display.

Safety and lifecycle

Postmarket record

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 K223556 by exact submission identifier. This does not exclude product-family, later, or adverse-event information.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-03

Exact-identifier review does not prove absence of all product-family safety signals.

Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not publicly available: Reviewed sources do not publish an exact-product procurement price with a stated offer scope.

Reimbursement

Reimbursement
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.
  • Service-level, not product-specific
  • Checked 2026-09-03

No product-specific code

No separate named-product payment identified in reviewed public material

Centers for Medicare & Medicaid Services · United States

Build a local total-cost and value model; do not infer reimbursement from FDA clearance or approval.

IT implementation Deployment, 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.

Review Merge, Visage, Sectra, AGFA and IntelePACS context

Integration chain: evidence at each hop

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.

  1. Acquisition/source

    Source context, not route validation: Supported DICOM images and release-specific user inputs.

    Scope: Exact FDA submission.

    Confirm scanner/model, protocol, series completeness and both software builds.

    Field checked 2026-09-03 · K223556 FDA decision source

  2. Routing

    Source context, not route validation: DICOM import and output to PACS, reporting, or downstream systems; validate identifiers, series selection, measurements, units, geometry, routing, and round trips.

    Scope: Product family. Current vendor materials are product-family evidence for K223556; confirm the exact cleared version, enabled options, deployment, and local compatibility.

    Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.

    Field checked 2026-09-03 · K223556 FDA decision source · MEDICAL IP DeepCatch

  3. AI processing

    Source context, not route validation: Software on a workstation, server, or supported virtual environment with release-specific licenses.

    Scope: Product family. Current vendor materials are product-family evidence for K223556; confirm the exact cleared version, enabled options, deployment, and local compatibility.

    Confirm processing location, queue ownership, exclusions and exact AI build.

    Field checked 2026-09-03 · K223556 FDA decision source · MEDICAL IP DeepCatch

  4. Returned objects

    Source context, not route validation: Measurements, segmentations, visualizations, calculations, and reports for professional review.

    Scope: Exact FDA submission.

    Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.

    Field checked 2026-09-03 · K223556 FDA decision source

  5. Viewer/worklist/report

    Unresolved route: Measurements, segmentations, visualizations, calculations, and reports 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.

    Field checked 2026-09-03 · K223556 FDA decision source

  6. Support owner

    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.

  1. Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
  2. Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
  3. Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
  4. Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
  5. Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
  6. Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
  7. 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.

Open the printable evaluation checklist

Deployment
Software on a workstation, server, or supported virtual environment with release-specific licenses.
  • Product family
  • Checked 2026-09-03

Current vendor materials are product-family evidence for K223556; confirm the exact cleared version, enabled options, deployment, and local compatibility.

Integration
DICOM import and output to PACS, reporting, or downstream systems; validate identifiers, series selection, measurements, units, geometry, routing, and round trips.
  • Product family
  • Checked 2026-09-03

Current vendor materials are product-family evidence for K223556; confirm the exact cleared version, enabled options, deployment, and local compatibility.

Training
Only qualified imaging professionals and physicians trained for the represented anatomy and workflow should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
  • Exact FDA submission
  • Checked 2026-09-03
Monitoring
Monitor 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: Outputs supplement accepted interpretation methods and require review against source images; supported modality, anatomy, protocol, and version limits apply.
  • Product family
  • Checked 2026-09-03

Current vendor materials are product-family evidence for K223556; confirm the exact cleared version, enabled options, deployment, and local compatibility.

Release and scope verification

Map the installed model, build, options, population, anatomy, inputs, outputs, and enabled AI functions to K223556 before acceptance.

exact submission · checked 2026-09-03

Later product-family features are not evidence that this cleared release includes them.

Interoperability acceptance

DICOM import and output to PACS, reporting, or downstream systems; validate identifiers, series selection, measurements, units, geometry, routing, and round trips.

product family · checked 2026-09-03

Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally. Vendor statements are current product-family context; confirm the exact cleared release and installed options.

Clinical acceptance

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. Outputs supplement accepted interpretation methods and require review against source images; supported modality, anatomy, protocol, and version limits apply.

exact submission · checked 2026-09-03

Define stop-use, escalation, rollback, and revalidation triggers before production use.

Economic evaluation

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

No exact-product price was found in the reviewed public material; vendor productivity claims are scenario inputs, not guaranteed local savings.

Lifecycle monitoring

Monitor 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: Outputs supplement accepted interpretation methods and require review against source images; supported modality, anatomy, protocol, and version limits apply.

product family · checked 2026-09-03

Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. Vendor statements are current product-family context; confirm the exact cleared release and installed options.

Sources & review details FDA 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.

FDA submission
K223556
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
CT/CTA
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-03
Anatomy
Multi-region
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-03
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2023-06-16
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
FDA status
FDA-cleared
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31

Research record

What has been checked

This audit distinguishes completed source review from fields that have not yet been researched.

Human reviewedStatus
2026-09-04Last searched
25Fields reviewed
11Source classes checked
4Awaiting review PubMed leads
1Awaiting review trial leads
0Unreviewed FDA recall leads

Recovered from the prior exact-submission extraction and normalized under the current provenance rules. Exact FDA decision materials were reviewed for identity, indication, users, workflow, limitations, and submitted performance. Current vendor material is labeled product-family context where it does not establish the exact release. PubMed and ClinicalTrials.gov results are retained as candidate evidence with version applicability pending; CMS reimbursement context and exact-identifier openFDA postmarket results were also checked. Pricing, final security architecture, contracted services, enabled options, and local interoperability remain organization-specific evidence. Automated exact-name discovery found 4 PubMed and 1 ClinicalTrials.gov candidate records. Candidates require human product and version matching; zero candidates is not evidence that no studies exist. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.

Candidate leads remain unpublished until a human confirms the exact product and tested version.

Source classes: fda ai list, fda decision summary, fda decision material, vendor product page, 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-03 - 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.

  • 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
  • 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 verified - checked 2026-09-03 - Exact FDA submission

    Public materials reviewed for this exact release do not establish the complete security posture. Request data-flow, identity, audit, encryption, retention, remote-access, vulnerability-management, backup, and incident-response evidence.

  • Installation timeline: Not yet reviewed

12 sources - 2 history items

Source ledger

  1. K223556 FDA decision source

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, purpose, modality, anatomy

  2. Artificial Intelligence-Enabled Medical Devices

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, modalityContext

  3. PubMed biomedical literature index

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery

  4. ClinicalTrials.gov study registry

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery, studyStatus

  5. Medicare Coverage Database

    Centers for Medicare & Medicaid Services - Accessed 2026-09-01

    Scope: coverage, codingContext

  6. openFDA Device Recall API

    U.S. Food and Drug Administration - Accessed 2026-09-02

    Scope: recallDiscovery, nativeSubmissionMatching

  7. MEDICAL IP DeepCatch

    MEDICAL IP - Accessed 2026-09-03

    Scope: productFamilyContext, workflowRole, implementationCapabilities

  8. Enhanced opportunistic CT screening for osteoporosis using Machine learning derived volumetric vertebral and complementary body composition information.

    U.S. National Library of Medicine - Accessed 2026-09-03

    Scope: evidenceStudies, productFamilyContext, evidenceDiscovery

  9. Deep learning-based detection of ascending aortic dilatation on chest radiographs: A diagnostic study.

    U.S. National Library of Medicine - Accessed 2026-09-03

    Scope: evidenceStudies, productFamilyContext, evidenceDiscovery

  10. Abdominal CT-derived metabolic phenotypes are associated with the MRI-derived brain age gap in women.

    U.S. National Library of Medicine - Accessed 2026-09-03

    Scope: evidenceStudies, productFamilyContext, evidenceDiscovery

  11. Incremental diagnostic value of multiregional single-slice CT muscle areas over L3 for sarcopenia: a deep learning-based segmentation study.

    U.S. National Library of Medicine - Accessed 2026-09-03

    Scope: evidenceStudies, productFamilyContext, evidenceDiscovery

  12. Body Composition and Fatty Liver Disease

    U.S. National Library of Medicine - Accessed 2026-09-03

    Scope: evidenceStudies, productFamilyContext, evidenceDiscovery

Research history

  1. K223556 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    human reviewed

Alternatives

Related tools to compare

FDA-cleared K253944

Data Analysis Facilitation Suite (DAFS)

Voronoi Health Analytics Incorporated

Authorized purpose: DAFS automatically segments anatomy on DICOM Part 10 CT images and supports reviewed two- and three-dimensional visualization, editing, and area, volume, and intensity measurements; it does not provide diagnostic interpretation.

Modality
CT/CTA
Anatomy
Multi-region
Decision
2026-03-16
FDA-cleared K260322

Acorn 3D Software (AC-SEG-4009); Acorn 3DP Model (AC-101-XX)

Mighty Oak Medical

Authorized purpose: Acorn 3D Software and Acorn 3DP Model process CT, synthetic CT, and CT angiography for segmentation, visualization, measurement, treatment planning, and three-dimensional printing, including adult and pediatric spine trajectory planning.

Modality
CT/CTA
Anatomy
Spine; craniomaxillofacial; musculoskeletal anatomy; and patient-specific printed models
Decision
2026-06-11
FDA-cleared K253649

Spectral CT Verida Family

Philips Medical Systems Technologies, Ltd.

Authorized purpose: Spectral CT Verida Family supports the labeled spectral CT acquisition, reconstruction, material-map, and professional-interpretation workflow; exact models, protocols, and derived outputs remain submission-specific.

Modality
CT/CTA
Anatomy
Multi-region
Decision
2026-03-27

Correct this exact record

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.

Open existing correction destination

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.

Correction policy and limits · Public repository change history