IF MedTechStart a project

Embedded Firmware & BLE

The firmware inside the device, written under the IEC 62304 lifecycle. Battery life, wireless reliability and update security are design decisions, not later fixes.

When Embedded Firmware and BLE Are the Right Step

When a device has a microcontroller, a wireless link or a battery life to meet. The firmware is medical device software, so its process follows from the risk it carries.

  • Connect a Device to a Phone

    A wearable or bedside device that sends data over Bluetooth Low Energy to an app or a gateway.

  • Make a Battery Last

    A device that must run for days or weeks on a small battery, where sleep modes and radio use decide the design.

  • Secure the Device

    Pairing, encryption and firmware updates that protect patient data and guard the device against tampering.

How Embedded Firmware and BLE Work

  1. Step 1

    Classify and Plan

    The software safety class, and a development plan to match it.

  2. Step 2

    Build the Architecture

    Drivers, the real-time design and the wireless stack.

  3. Step 3

    Test as You Go

    Unit and integration tests, run on every build.

  4. Step 4

    Secure and Release

    Security controls, and releases under configuration control.

What you get

What You Bring and What You Get

You Bring

  • What the device does, and how long it must run
  • The hardware, or its schematics
  • The risk analysis so far
  • The app or gateway it must talk to
  • Any existing code, and the third-party libraries in it

You Get Back

  • Software development plan
  • Architecture and detailed design
  • Unit and integration test records
  • List of third-party software (SOUP)
  • Security controls and their records
  • Release notes for each controlled release
Questions

Questions Clients Ask

Is our firmware medical device software?

If it runs on a medical device and affects how the device works, yes. IEC 62304 then applies to how it is developed and maintained.

What is SOUP?

Software of unknown provenance: third-party code, such as a real-time operating system, a Bluetooth stack or a library, that was not built under your process. IEC 62304 asks you to list it, state what you need from it and assess its known faults.

Do we need Bluetooth qualification?

A product that uses Bluetooth technology and its name or logo must complete the Bluetooth SIG qualification process. A pre-qualified module can reduce the work.

Have a question about Embedded firmware & BLE?

Opens the contact form with this service named. Nothing is sent until you press send.