IEEE 11073
IoT & Roboticsconcept · 6 मिनट · अपडेट 19 जुल॰ 2026

IEEE 11073

लेखक Rajendra Sharma, RN, CPC, CPBसमीक्षक Rajendra Sharma, RN, CPC, CPB · 29 जून 2026

The standards family for how medical devices describe themselves and their measurements — the device-side counterpart to FHIR.

IEEE 11073

In one line

IEEE 11073 standardises medical-device semantics — a shared nomenclature of measurement types, units, and device models — so a blood-pressure reading means the same thing regardless of vendor.

PHD device 11073 domain info model manager e.g. BP cuff, scalephone / gateway
IEEE 11073 PHD standardises how a personal health device describes its measurements, so any manager can read it.

The problem it solves

BLE moves the bytes, but bytes aren't meaning: one scale reports kilograms, another pounds; one labels a field "SYS", another "systolic". Without a shared vocabulary, every device integration is bespoke. IEEE 11073 supplies that shared semantics — a coded nomenclature so a measurement is unambiguous across vendors.

How the family is organised

  • Point-of-Care (PoC) standards — bedside monitors, ventilators, anaesthesia machines (the high-acuity hospital side).
  • Personal Health Device (PHD) standards — the -104xx series: thermometers, weight scales, glucose meters, pulse oximeters, blood-pressure cuffs (home/consumer side).

At the heart is a coded nomenclature (MDC codes) for observables and units, plus device information models describing each device's capabilities (a "domain information model").

The integration stack

11073 is one layer in a chain — knowing the whole chain is the skill:

radio (BLE)  →  meaning (IEEE 11073 MDC)  →  record (FHIR Observation/Device)

The Bluetooth SIG health profiles and HL7's Personal Health Devices FHIR IG both build on 11073: BLE carries the bytes, 11073 gives them meaning, FHIR carries them into the record as Observation / Device / DeviceMetric.

Where it shows up in digital health

Any serious device-integration project: mapping vendor streams into MDC-coded observations, then into FHIR resources. Connectathon-tested gateways — and this platform's IoT lab — walk exactly that chain: radio → 11073 semantics → FHIR.

Common pitfalls

  • Skipping the semantics layer — mapping raw GATT straight to FHIR without 11073 codes re-introduces the vendor-ambiguity problem.
  • Unit mismatches — 11073 MDC units must map cleanly to UCUM in FHIR; getting this wrong is a patient-safety bug.
  • Assuming all devices conform — many consumer devices implement only part of the standard.

Key takeaways

  • IEEE 11073 standardises device semantics (MDC nomenclature + device models), not the radio.
  • Two arms: Point-of-Care (hospital) and Personal Health Device (consumer).
  • It's the meaning layer in BLE → 11073 → FHIR — the device-integration backbone.
  • Map MDC units to UCUM carefully; that boundary is where safety bugs hide.

अपना स्मरण जाँचें

2 में से 0 याद

दोबारा पढ़ने से बेहतर है सक्रिय स्मरण — पहले उत्तर सोचें, फिर देखें।

  1. What does IEEE 11073 standardise that BLE doesn't?

  2. The device-integration stack in three layers?

संदर्भ

  1. IEEE 11073 Standards Family
  2. HL7 FHIR Devices on FHIR / PHD Implementation Guide

संबंधित entries