---
AI Summary: "\\- Conducted software safety and cybersecurity gap analysis for the\
  \ zero‑footprint DICOM viewer.  \n- Authored Design History File, user needs, requirements,\
  \ and verification plans using existing manuals.  \n- Scoped device, excluded backend,\
  \ negotiated FDA review, achieving 510(k) clearance in 4 months."
Anonymous: false
Assignee: []
Last Edited Time: '2026-05-09T20:10:00+00:00'
case_study_510ks:
- 359bd5b7-a754-8122-a240-d2d5ddb9a256
client_logo:
- 18dbd5b7-a754-808e-8a36-f743ad260943
client_name: Medweb
date: '2026-01-25'
featured: true
medical_panel: Radiology
name: We Submitted a 510(k) in 7 Weeks and Cleared it in 4 Months
services:
- 30311ab9-66a7-48a7-9dff-2927e1468480
summary: Completed DHF and 510(k) documentation in 7 weeks. FDA cleared 4 months after
  submission.\"
tags: []
testimonials:
- 2a6bd5b7-a754-80e0-9f9c-fb7603bc7bc2
---

## The Outcome

510(k) submitted in 7 weeks --- one week ahead of an 8-week deadline. FDA clearance December 20, 2024, ~4 months after submission and 6 months after project kickoff.

## The Problem

Medweb came to us with a zero-footprint DICOM viewer and a hard deadline: clear the device in time for RSNA 2024. They needed a complete Design History File and 510(k) submission package built in eight weeks on top of engineering work that had never been packaged for FDA. No in-house regulatory writing capacity to hit that timeline alone.

## What We Did

![](/img/portfolio/We_Submitted_a_510k_in_7_Weeks_and_Cleared_it_in_4_Months-35bbd5b7a75480c9a12ce9c9f0d026a6.png)

- Read the existing user manual and test cases. Reused them to author user needs, requirements, device description, substantial equivalence rationale, and verification test plans instead of starting from scratch.
- Ran a software safety and cybersecurity gap analysis. Specified the remediations needed to meet FDA expectations.
- Scoped the device tight. Recommended excluding several candidate features and the Medweb backend from the medical device boundary which simplified predicate selection, lowered the risk classification, and shrank the document set.
- Translated the document set into language Medweb\'s team could review and own. No jargon walls. No template overwhelm.
- When FDA challenged a feature during review, we saved the day by brokering a deal between the client and FDA to still allow the FDA clearance through. Trade-off: a narrower first clearance, with a clean foundation to add the feature back through a follow-on submission.

## Timeline

- **June 18, 2024** --- Project kickoff
- **August 8, 2024** --- 510(k) submitted (1 week ahead of schedule)
- **October 7, 2024** --- Additional Information (AINN) request received
- **November 21, 2024** --- AINN response submitted
- **December 20, 2024** --- 510(k) cleared