---
tags:
  - iints/source
  - iints/source/regulatory
source_id: "fda_k193510_780g"
source_bucket: "docs_only_device_emulation"
category: "regulatory"
component: "medtronic_780g_emulation_context"
url: "https://www.accessdata.fda.gov/"
doi: ""
status: active
---

# U.S. FDA 510(k) K193510 - MiniMed 780G System

> [!info] What this source supports
> Regulatory context for device-emulation documentation.

| Field | Value |
| --- | --- |
| Source ID | `fda_k193510_780g` |
| Bucket | `docs_only_device_emulation` |
| Category | `regulatory` |
| SDK component | `medtronic_780g_emulation_context` |
| DOI | n/a |
| URL | https://www.accessdata.fda.gov/ |
| Origin file | `docs/EVIDENCE_BASE.md` |

## Citation

U.S. FDA. 510(k) K193510 - MiniMed 780G System.

## User Interpretation

Use this source to explain **why the SDK default, metric, dataset, or hardware-safety boundary exists**. It is evidence support for pre-clinical simulation and documentation, not a medical approval claim.
