Connected medical device security intake

Tools it calls

Each tool's price and track record across every agent today. Empty means the call worked and found nothing.

# Connected medical device security intake

For one device model a department wants to deploy. Clearance, radio certification and vulnerabilities live in three agencies; intake needs all three.

## 1. Regulatory status

1. Search @[FDA · Device clearances](alexandria:fda-gov/records/device_clearances) (query = applicant and device name). Keep the **k_number**, decision date and product code.
2. Check @[FDA · Device recalls](alexandria:fda-gov/records/device_recalls) (query = firm and product). Software or cybersecurity-related recalls go straight into the risk note.

## 2. The radio inside

3. Resolve the maker's FCC grantee code with @[FCC equipment authorization · Search grantees](alexandria:apps-fcc-gov/equipment-authorizations/search_grantees) (grantee_name), or read the FCC ID from the device label.
4. List its filings with @[FCC equipment authorization · Search authorizations](alexandria:apps-fcc-gov/equipment-authorizations/search_authorizations) (grantee_code, product_description). Read the matching grant with @[FCC equipment authorization · Get application grant](alexandria:apps-fcc-gov/equipment-authorizations/get_application_grant): frequency bands (2.4 GHz, 5 GHz, cellular) the network team must plan for.
5. List exhibits with @[FCC equipment authorization · Get application exhibits](alexandria:apps-fcc-gov/equipment-authorizations/get_application_exhibits); internal photos often name the wireless module vendor.

## 3. Known vulnerabilities

6. Search @[NVD · Search](alexandria:nvd-nist-gov/vulnerabilities/search) with keyword = device maker and product, and again with the wireless module vendor. Note severity and whether any are in KEV (in_kev).

## Write the intake note

- **Device:** k_number, product code, recalls.
- **Radio:** FCC ID, bands, module vendor if shown.
- **Vulnerabilities:** CVE, CVSS, KEV status, affected versions.
- **Conditions:** network segment, patch requirement, MDS2 request to the vendor.
- **Sources:** k_numbers, recall numbers, FCC application ids, CVE ids. Say what could not be found.

• Vaping policy impact snapshotby Firecrawl · uses 9 toolsUse when a tobacco control policy analyst at a health department or charity assesses vaping regulation for a briefing. Compares tobacco use prevalence across countries from WHO, tracks public search interest in vaping…
• Mosquito-borne disease season outlookby Firecrawl · uses 8 toolsUse when a state or county epidemiologist plans vector surveillance and messaging for the coming dengue or West Nile season. Compares recent temperature and rainfall with climate normals, checks rising public symptom…+1
• Measles resurgence early warningby Firecrawl · uses 6 toolsUse when a public-health analyst, NGO programme lead or travel-health team needs to know where measles is likely to come back next. Finds countries whose MCV1 and MCV2 coverage has slipped, checks whether search…
• Urgent care site demand and drive-time checkby Firecrawl · uses 8 toolsUse when an ambulatory network planner or urgent care development lead tests a proposed clinic address. Measures resident demand from Census data, counts competing urgent care and primary care nearby, checks drive time…
• Referral specialist vettingby Firecrawl · uses 10 toolsUse when a practice manager or care coordinator is deciding whether to add a specialist to a referral list. Checks the NPI record, state license status and discipline, Medicare procedure volume, patient review trend…+3
• Network adequacy gap check for a countyby Firecrawl · uses 7 toolsUse when a health plan network development manager must prove a county meets time-and-distance standards before a filing. Lists registered specialists and facilities near members, measures drive times from population…