Skip to content

Commit ce934a0

Browse files
authored
Merge pull request #217625 from msjasteppe/iot-hub-updates
Major revision to using IoT Hub tutorial
2 parents 44b52c7 + a44fbb5 commit ce934a0

12 files changed

+154
-53
lines changed

articles/healthcare-apis/iot/device-data-through-iot-hub.md

Lines changed: 149 additions & 48 deletions
Large diffs are not rendered by default.

articles/healthcare-apis/iot/how-to-use-device-mappings.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,11 +5,11 @@ author: msjasteppe
55
ms.service: healthcare-apis
66
ms.subservice: fhir
77
ms.topic: how-to
8-
ms.date: 10/25/2022
8+
ms.date: 11/08/2022
99
ms.author: jasteppe
1010
---
1111

12-
# Device mappings overview
12+
# How to configure device mappings
1313

1414
This article provides an overview and describes how to configure the MedTech service device mappings.
1515

@@ -22,7 +22,7 @@ The second type, **Fast Healthcare Interoperability Resources (FHIR®) desti
2222
2323
The two types of mappings are composed into a JSON document based on their type. These JSON documents are then added to your MedTech service through the Azure portal. The device mapping is added through the **Device mapping** page and the FHIR destination mapping through the **Destination** page.
2424

25-
## How to configure device mappings
25+
## Device mappings overview
2626

2727
Device mappings provide functionality to extract device message content into a common format for further evaluation. Each device message received is evaluated against all device mapping templates. A single inbound device message can be separated into multiple outbound messages that are later mapped to different observations in the FHIR service. The result is a normalized data object representing the value or values parsed by the device mapping templates.
2828

3.26 KB
Loading
35.6 KB
Loading
110 KB
Loading
5.31 KB
Loading
5.23 KB
Loading
31.2 KB
Loading
35.8 KB
Loading
35.8 KB
Loading

0 commit comments

Comments
 (0)