embedded-medical-device

Automate TinyGo firmware validation and capability attestation for embedded medical devices.

1|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/bmorphism/boxxy --skill embedded-medical-device
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: embedded-medical-device
Source: https://github.com/bmorphism/boxxy/tree/main/skills/embedded-medical-device
Command: npx skills add https://github.com/bmorphism/boxxy --skill embedded-medical-device

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github.com/tinygo-org/bluetooth, github.com/waj334/tinygo-cryptoauthlib, github.com/bmorphism/boxxy/internal/skill, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill enables secure embedded medical device firmware development by providing a compact capability registry, integrity checks, and attestation pathways compliant with FDA/IEC standards.

Core Features & Use Cases

  • Capability attestation: hardware-backed identity and cryptographic validation for TinyGo-based medical firmware.
  • FHIR/IEEE 11073 bridging: local conversion and validation pipeline to transform sensor data into compliant observations.
  • Secure gateway interoperability: supports BLE-based telemetry with HMAC integrity tags and secure element integration for device attestation in clinical workflows.

Quick Start

Run the embedded-medical-device skill to initialize a compact capability registry on your TinyGo firmware and publish it over BLE for gateway attestation.

Frequently Asked Questions about embedded-medical-device

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement firmware attestation for TinyGo-based medical devices?

Firmware attestation for TinyGo medical devices is automated by generating a compact capability registry, applying integrity checks, and using secure element integration for hardware-backed cryptographic validation.

How does BLE capability advertising work for secure medical device workflows?

BLE capability advertising publishes the device's compact registry over BLE/GATT with HMAC integrity tags, allowing clinical gateways to verify device identity and attestation before processing telemetry.

Can I convert IEEE 11073 sensor data to FHIR observations on embedded medical devices?

Yes, WASI-based FHIR conversion transforms IEEE 11073 sensor data into compliant FHIR observations locally on the device, enabling direct interoperability with clinical gateway systems.

Does this Skill support nRF52840, STM32, and RP2040 targets for medical firmware validation?

Yes, the Skill coordinates firmware validation, BLE/GATT security, and secure element usage across nRF52840, STM32, and RP2040 targets using TinyGo.

What's the best way to ensure FDA and IEC compliance for embedded medical device firmware?

Compliance is achieved by combining hardware-backed identity attestation, GF(3) conservation checks, and standardized IEEE 11073/FHIR data handling pipelines within the firmware validation workflow.

Do I need a secure element to use BLE telemetry with HMAC integrity tags in medical devices?

A secure element like those supported by tinygo-cryptoauthlib provides the hardware-backed cryptographic validation necessary for reliable HMAC integrity tagging and device attestation in clinical environments.