# Mapping from IEEE 11073-10201 DIM to FHIR - Point-of-Care Device Implementation Guide v1.0.0

* [**Table of Contents**](toc.md)
* [**Technical Implementation Guidance**](guidance.md)
* **Mapping from IEEE 11073-10201 DIM to FHIR**

## Mapping from IEEE 11073-10201 DIM to FHIR

| |
| :--- |
| *Page standards status:*[Informative](http://hl7.org/fhir/R4/versions.html#std-process) |

Within the context of the ISO/IEEE 11073 Point-of-care medical device communication standards, ISO/IEEE 11073-10201 provides an abstract, object-oriented domain information model (DIM) that defines a hierarchical model for structuring medical device data as well as events and services.

### DIM Object Classes

Most object classes in ISO/IEEE 11073 DIM can be mapped to FHIR resources as outlined in the following table.

| | |
| :--- | :--- |
| SimpleMDSHydraMDSCompositeSingleBedMDSCompositeMultipleBedMDS | [Device](http://hl7.org/fhir/R4/device.html)(according to the[MDS Device profile](StructureDefinition-MdsDevice.md)) and[Location](http://hl7.org/fhir/R4/location.html)(if needed) |
| VMD | [Device](http://hl7.org/fhir/R4/device.html)(according to the[VMD Device profile](StructureDefinition-VmdDevice.md)) |
| Channel | [Device](http://hl7.org/fhir/R4/device.html)(according to the[Channel Device profile](StructureDefinition-ChannelDevice.md)) |
| Numeric | [DeviceMetric](http://hl7.org/fhir/R4/devicemetric.html)(according to the[Numeric DeviceMetric profile](StructureDefinition-NumericDeviceMetric.md)) and[Observation](http://hl7.org/fhir/R4/observation.html)(according to the[Numeric Observation profile](StructureDefinition-NumericObservation.md)or[Compound Numeric Observation profile](StructureDefinition-CompoundNumericObservation.md)) |
| Enumeration | [DeviceMetric](http://hl7.org/fhir/R4/devicemetric.html)(according to the[Enumeration DeviceMetric profile](StructureDefinition-EnumerationDeviceMetric.md)) and[Observation](http://hl7.org/fhir/R4/observation.html)(according to the[Enumeration Observation profile](StructureDefinition-EnumerationObservation.md)) |
| TimeSampleArrayRealTimeSampleArrayDistributionSampleArray | [DeviceMetric](http://hl7.org/fhir/R4/devicemetric.html)(according to the[Sample Array DeviceMetric profile](StructureDefinition-SampleArrayDeviceMetric.md)) and[Observation](http://hl7.org/fhir/R4/observation.html)(according to the[Sample Array Observation profile](StructureDefinition-SampleArrayObservation.md)) |
| AlertAlertStatusAlertMonitor | **to be completed** |
| PatientDemographics | [Patient](http://hl7.org/fhir/R4/patient.html) |

### DIM Object Attributes

Please refer to the Mappings tab of each profile page for mapping ISO/IEEE 11073 DIM object attributes to FHIR resource elements.

### Mapping Details

#### Measurement Status

Observed values in ISO/IEEE 11073 DIM include a bit field that indicates measurement status. FHIR Observations do not have a single element for this purpose. Instead there is security metadata, dataAbsentReason for missing values, and interpretation to report significance of a result.
 Measurement status information is mapped to `Resource.meta.security`, `Observation.dataAbsentReason` or `Observation.component.dataAbsentReason`, and `Observation.interpretation` or `Observation.component.interpretation` elements. The interpretation value set binding is extended to add relevant codes from the [Measurement status codes](CodeSystem-measurement-status.md) defined in this implementation guide.

| | | | |
| :--- | :--- | :--- | :--- |
| invalid (0) | UNRELIABLE | error |   |
| questionable (1) | UNCERTREL |   | questionable |
| not-available (2) |   | not-performed |   |
| calibration-ongoing (3) | UNCERTREL |   | calibration-ongoing |
| test-data (4) | HTEST |   |   |
| demo-data (5) | HTEST |   |   |
| validated-data (8) | HRELIABLE |   | validated-data |
| early-indication (9) |   |   | early-indication |
| msmt-ongoing (10) |   | temp-unknown | msmt-ongoing |
| msmt-state-in-alarm (14) |   |   | in-alarm |
| msmt-state-al-inhibited (15) |   |   | alarm-inhibited |

Note that dataAbsentReason and interpretation are mutually exclusive: dataAbsentReason shall only be present if there is no observation value, whereas interpretation adds relevant information about an existing observation value.

