Merge pull request #177635 from msjasteppe/iot-minor-edits

Minor edits of IoT connector documentation.

Author: Court72

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

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: conceptual
-ms.date: 10/12/2021
+ms.date: 10/26/2021
 ms.author: jasteppe
 ---
 
@@ -23,6 +23,9 @@ The two types of mappings are composed into a JSON document based on their type.
 > [!NOTE]
 > Mappings are stored in an underlying blob storage and loaded from blob per compute execution. Once updated they should take effect immediately. 
 
+> [!TIP]
+> Check out the [IoMT Connector Data Mapper](https://github.com/microsoft/iomt-fhir/tree/master/tools/data-mapper) tool for editing, testing, and troubleshooting IoT connector Device and FHIR destination mappings. Export mappings for uploading to IoT connector in the Azure portal or use with the [open-source version](https://github.com/microsoft/iomt-fhir) of IoT connector.
+
 ## Device mapping
 
 Device mapping provides mapping functionality to extract device content into a common format for further evaluation. Each message received is evaluated against all templates. This approach allows a single inbound message to be projected to multiple outbound messages, which are later mapped to different observations in FHIR. The result is a normalized data object representing the value or values parsed by the templates. The normalized data model has a few required properties that must be found and extracted:
@@ -446,6 +449,6 @@ The IotCentralJsonPathContentTemplate also doesn't require DeviceIdExpression an
 ## Next steps
 
 >[!div class="nextstepaction"]
->[How to use FHIR destination mapping](how-to-use-fhir-mapping-iot.md)
+>[How to use FHIR destination mappings](how-to-use-fhir-mapping-iot.md)
 
 (FHIR®) is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.

articles/healthcare-apis/iot/how-to-use-fhir-mapping-iot.md

@@ -5,18 +5,21 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: conceptual
-ms.date: 10/12/2021
+ms.date: 10/26/2021
 ms.author: jasteppe
 ---
 
-# How to use the FHIR destination mapping
+# How to use the FHIR destination mappings
 
 > [!IMPORTANT]
 > Azure Healthcare APIs is currently in PREVIEW. The [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) include additional legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
 
 This article describes how to configure IoT connector using the Fast Healthcare Interoperability Resources (FHIR®) destination mapping.
 
-## FHIR destination mapping
+> [!TIP]
+> Check out the [IoMT Connector Data Mapper](https://github.com/microsoft/iomt-fhir/tree/master/tools/data-mapper) tool for editing, testing, and troubleshooting IoT connector Device and FHIR destination mappings. Export mappings for uploading to IoT connector in the Azure portal or use with the [open-source version](https://github.com/microsoft/iomt-fhir) of IoT connector.
+
+## FHIR destination mappings
 
 Once the device content is extracted into a normalized model, the data is collected and grouped according to device identifier, measurement type, and time period. The output of this grouping is sent for conversion into a FHIR resource ([Observation](https://www.hl7.org/fhir/observation.html) currently). The FHIR destination mapping template controls how the data is mapped into a FHIR observation. Should an observation be created for a point in time or over a period of an hour? What codes should be added to the observation? Should value be represented as [SampledData](https://www.hl7.org/fhir/datatypes.html#SampledData) or a [Quantity](https://www.hl7.org/fhir/datatypes.html#Quantity)? These data types are all options the FHIR destination mapping configuration controls.
 
@@ -259,6 +262,6 @@ Represents the [CodeableConcept](http://hl7.org/fhir/datatypes.html#CodeableConc
 ## Next steps
 
 >[!div class="nextstepaction"]
->[How to use Device mapping](how-to-use-device-mapping-iot.md)
+>[How to use Device mappings](how-to-use-device-mapping-iot.md)
 
 (FHIR®) is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.

articles/healthcare-apis/iot/index.yml

@@ -13,7 +13,7 @@ metadata:
   ms.collection: collection
   author: msjasteppe
   ms.author: jasteppe
-  ms.date: 10/12/2021
+  ms.date: 10/26/2021
 
 # linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
 
@@ -32,9 +32,9 @@ landingContent:
         links:
           - text: IoT connector data flow
             url: iot-data-flow.md
-          - text: Device mapping
+          - text: Device mappings
             url: how-to-use-device-mapping-iot.md
-          - text: FHIR destination mapping
+          - text: FHIR destination mappings
             url: how-to-use-fhir-mapping-iot.md
           - text: IoMT Connector Data Mapper tool
             url: https://github.com/microsoft/iomt-fhir/tree/master/tools/data-mapper

articles/healthcare-apis/iot/iot-troubleshoot-guide.md

@@ -19,11 +19,14 @@ This article provides steps for troubleshooting common IoT connector error messa
 > [!TIP]
 > When opening an [Azure Technical Support](https://azure.microsoft.com/support/create-ticket/) ticket for the IoT connector, include copies of your Device and FHIR destination mappings to assist in the troubleshooting process.
 
-## Device and FHIR destination mapping validations
+## Device and FHIR destination mappings validations
 
 This section describes the validation process that IoT connector does. The validation process validates the Device and FHIR destination mappings before allowing them to be saved for use. These elements are required in the Device and FHIR destination mappings.
 
-**Device mapping**
+> [!TIP]
+> Check out the [IoMT Connector Data Mapper](https://github.com/microsoft/iomt-fhir/tree/master/tools/data-mapper) tool for editing, testing, and troubleshooting IoT connector Device and FHIR destination mappings. Export mappings for uploading to IoT connector in the Azure portal or use with the [open-source version](https://github.com/microsoft/iomt-fhir) of IoT connector.
+
+**Device mappings**
 
 |Element|Required|
 |:-------|:------|
@@ -41,7 +44,7 @@ This section describes the validation process that IoT connector does. The valid
 > 
 >When a wearable IoMT device is put on or removed, the element(s) don't have any values except for a name that IoT connector matches and emits. On the FHIR conversion, IoT connector maps it to a code-able concept based on the semantic type. This means that no actual values are populated.
 
-**FHIR destination mapping**
+**FHIR destination mappings**
 
 |Element|Required|
 |:------|:-------|
@@ -150,7 +153,7 @@ The mapping copies should be provided to Azure Technical Support when opening a
 > JSON is the only supported format for Device and FHIR destination mappings at this time.
 
 > [!TIP]
-> Learn more about IoT connector [Device and FHIR destination mappings](how-to-use-fhir-mapping-iot.md)
+> Learn more about IoT connector [Device mappings](how-to-use-device-mapping-iot.md) and [FHIR destination mappings](how-to-use-fhir-mapping-iot.md)
 
 1. Select **"IoT connectors"** on the left side of the Healthcare APIs Workspace.