The ISO/IEEE 11073-10101 Nomenclature standard (MDC) provides a comprehensive terminology for device models according to the ISO/IEEE 11073-10201 Domain information model (DIM). It's the preferred code system for profiles in this implementation guide. Reference identifiers, terminology codes, and descriptions are available at the Rosetta Terminology Mapping Management System (RTMMS).

The PoCD profiles define rules for terminology usage:

• Device.type shall have a coding from the MDC Device nomenclature if there is an appropriate code available. This ensures consistent coding using the ISO/IEEE 11073-10101 Nomenclature standard, which provides MDS, VMD, and Channel codes for device models according to the DIM. If there is no code available, proposed or private MDC codes or coding from an alternative code system may be used. As this element is of type CodeableConcept there can be additional coding from other code systems.
• Same for the DeviceMetric.type, which shall have a coding from the MDC Metric nomenclature if there is an appropriate code available.
• DeviceMetric.unit is an optional element of type CodeableConcept. If present, it shall have a coding from the MDC Units of measurement if there is an appropriate code available. Additional other coding is allowed as well. This element is the place for the MDC unit code, because the Observation resource has other constraints - see below.

The Vital Signs Profile, which is part of FHIR core specification, applies for some commonly used measurement observations (e.g., heart rate, blood pressure, respiratory rate, oxygen saturation, body temperature):

• The PoCD profiles require an MDC coding in Observation.code and, for compound metrics, in Observation.component.code. Depending on the type of measurement, the Vital Signs profile may require LOINC codes as additional coding. Note that the MDC code can be more specific than the Vital Signs LOINC code.
• The Quantity data type in Observation.value[x] and Observation.component.value[x] contains the units of measure. There is only a single coding that needs to be UCUM for all vital signs. Therefore the PoCD profiles require UCUM coding for all numerics.

Regenstrief, developers of LOINC, and IEEE, developers of the 11073 standards, are working together to support interoperable communications of medical and personal health devices. There is a LOINC/IEEE Medical Device Code Mapping Table available as product of this collaboration.

Code Systems

Value Sets