Health Device Data Transfer
Version 1.0.0-rc2 - release

Specification of health data transfer from devices to DiGA (§ 374a SGB V)

ValueSet: Device Type of personal health devices

Official URL: https://gematik.de/fhir/hddt/ValueSet/hddt-device-type Version: 1.0.0-rc2
Active as of 2026-03-04 Computable Name: HddtDeviceType

Copyright/Legal: The copyright for the compilation of this value set is held by gematik GmbH and by Federal Institute for Drugs and Medical Devices (BfArM).

Dieses ValueSet enthält Codes zur Identifikation von Personal Health Devices und Device Data Recordern.

Die Definition dieses ValueSets ist eine Teilmenge der Definition des FHIR R5 ValueSet Device Type, angepasst für die Verwendung mit den auf FHIR R4 basierenden HDDT-Profilen.

Dieses Material enthält SNOMED Clinical Terms® (SNOMED CT®), die mit Genehmigung der International Health Terminology Standards Development Organisation (IHTSDO) verwendet werden. Alle Rechte vorbehalten. SNOMED CT® wurde ursprünglich vom College of American Pathologists entwickelt. ‘SNOMED’ und ‘SNOMED CT’ sind eingetragene Warenzeichen der IHTSDO.

Dieses ValueSet ist Teil der Health Device Data Transfer Spezifikation (HDDT), die Profile, Operationen und ValueSets für den Datenaustausch zwischen Hilfsmitteln und digitalen Gesundheitsanwendungen (DiGA) definiert. Der Inhalt des ValueSets umfasst immer mindestens alle Gerätetypen, für die HDDT Mandatory Interoperable Values (MIVs) definiert. Damit kann dieses ValueSet zukünftig auch Codes enthalten, die nicht Teil des FHIR ValueSet Device Type sind.

This ValueSet includes codes used to identify Personal Health Devices and Device Data Recorders.

This ValueSet’s definition is a subset of the definition of the FHIR R5 ValueSet Device Type, adapted for use with the FHIR R4 based HDDT profiles.

This material includes SNOMED Clinical Terms® (SNOMED CT®) which is used by permission of the International Health Terminology Standards Development Organisation (IHTSDO). All rights reserved. SNOMED CT®, was originally created by The College of American Pathologists. ‘SNOMED’ and ‘SNOMED CT’ are registered trademarks of the IHTSDO.

CAVE: This ValueSet is part of the Health Device Data Transfer specification (HDDT) which defines profiles, operations, and value sets for sharing data between medical aids and digital health applications (DiGA). The content of the value set will always at latest cover all types of device types for whoch HDDT defines Mandatory Interoperable Values (MIVs). By this, this value set MAY in the future include codes which are not part of the FHIR ValueSet Device Type.

References

Logical Definition (CLD)

Language: en

Profile: Shareable ValueSet

  • Include these codes as defined in http://snomed.info/sct version 📍http://snomed.info/sct/11000274103/version/20251115
    CodeDisplay
    337414009Blood glucose meter (physical object)
    700585005Invasive interstitial-fluid glucose monitoring system (physical object)
    701815004Non-invasive interstitial-fluid glucose monitoring system (physical object)
    702203005Invasive interstitial fluid glucose monitoring/insulin infusion system (physical object)
    463729000Point-of-care blood glucose continuous monitoring system (physical object)
    701750003Subcutaneous glucose sensor (physical object)
    70665002Blood pressure cuff, device (physical object)
    334990001Peak flow meter (physical object)
    303501006Spirometer (physical object)

 

Expansion

No Expansion for this valueset (Unsupported Code System Version)


Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code