Merge pull request #209689 from msjasteppe/iot-minor-updates

Minor adjustments based on feedback.

Author: 19BMG00

articles/healthcare-apis/iot/how-to-use-custom-functions.md

@@ -5,22 +5,17 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 08/16/2022
+ms.date: 08/30/2022
 ms.author: jasteppe
 ---
 
 # How to use custom functions
 
 Many functions are available when using **JmesPath** as the expression language. Besides the functions available as part of the JmesPath specification, many more custom functions may also be used. This article describes the MedTech service-specific custom functions for use with the MedTech service [device mapping](how-to-use-device-mappings.md) during the device message [normalization](iot-data-flow.md#normalize) process.
 
-> [!NOTE]
->
+> [!TIP]
 > For more information on JmesPath functions, see the JmesPath [specification](https://jmespath.org/specification.html#built-in-functions).
 
->[!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 the MedTech service device and FHIR destination mappings. Export mappings for uploading to the MedTech service in the Azure portal or use with the [open-source version](https://github.com/microsoft/iomt-fhir) of the MedTech service.
-
 ## Function signature
 
 Each function has a signature that follows the JmesPath specification. This signature can be represented as:
@@ -32,7 +27,6 @@ return_type function_name(type $argname)
 The signature indicates the valid types for the arguments. If an invalid type is passed in for an argument, an error will occur.
 
 > [!NOTE]
->
 > When math-related functions are done, the end result **must** be able to fit within a C# [long](/dotnet/csharp/language-reference/builtin-types/integral-numeric-types#characteristics-of-the-integral-types) value. If the end result in unable to fit within a C# long value, then a mathematical error will occur.
 
 ## Exception handling

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

@@ -1,21 +1,21 @@
 ---
-title: IotJsonPathContentTemplate mappings in MedTech service Device mappings - Azure Health Data Services
-description: This article describes how to use IotJsonPathContentTemplate mappings with MedTech service Device mappings templates. 
+title: IotJsonPathContentTemplate mappings in MedTech service device mapping - Azure Health Data Services
+description: This article describes how to use IotJsonPathContentTemplate mappings with MedTech service device mapping. 
 author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 03/22/2022
+ms.date: 08/31/2022
 ms.author: jasteppe
 ---
 
 # How to use IotJsonPathContentTemplate mappings
 
+This article describes how to use IoTJsonPathContentTemplate mappings with the MedTech service [device mapping](how-to-use-device-mappings.md).
+
 > [!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 the MedTech service Device and FHIR destination mappings. Export mappings for uploading to the MedTech service in the Azure portal or use with the [open-source version](https://github.com/microsoft/iomt-fhir) of the MedTech service.
 
-This article describes how to use IoTJsonPathContentTemplate mappings with the MedTech service Device mappings templates.
-
 ## IotJsonPathContentTemplate
 
 The IotJsonPathContentTemplate is similar to the JsonPathContentTemplate except the `DeviceIdExpression` and `TimestampExpression` aren't required.
@@ -27,7 +27,7 @@ When you're using these SDKs, the device identity and the timestamp of the messa
 >[!IMPORTANT]
 >Make sure that you're using a device identifier from Azure Iot Hub or Azure IoT Central that is registered as an identifier for a device resource on the destination FHIR service.
 
-If you're using Azure IoT Hub Device SDKs, you can still use the JsonPathContentTemplate, assuming that you're using custom properties in the message body for the device identity or measurement timestamp
+If you're using Azure IoT Hub Device SDKs, you can still use the JsonPathContentTemplate, assuming that you're using custom properties in the message body for the device identity or measurement timestamp.
 
 > [!NOTE]
 > When using `IotJsonPathContentTemplate`, the `TypeMatchExpression` should resolve to the entire message as a JToken. For more information, see the following examples:
@@ -39,6 +39,7 @@ If you're using Azure IoT Hub Device SDKs, you can still use the JsonPathContent
 *Message*
 
 ```json
+
 {
     "Body": {
         "heartRate": "78"        
@@ -50,34 +51,37 @@ If you're using Azure IoT Hub Device SDKs, you can still use the JsonPathContent
         "iothub-connection-device-id" : "device123"
     }
 }
+
 ```
 
 *Template*
 
 ```json
 
-    "templateType": "JsonPathContent",
-    "template": {
-        "typeName": "heartrate",
-        "typeMatchExpression": "$..[?(@Body.heartRate)]",
-        "deviceIdExpression": "$.deviceId",
-        "timestampExpression": "$.endDate",
-        "values": [
-            {
-                "required": "true",
-                "valueExpression": "$.Body.heartRate",
-                "valueName": "hr"
-            }
-        ]
-    }
-}
+{
+  "templateType": "IotJsonPathContentTemplate",
+  "template": {
+    "typeName": "heartrate",
+    "typeMatchExpression": "$..[?(@Body.heartRate)]",
+    "timestampExpression": "$.endDate",
+    "values": [
+      {
+            "required": "true",
+            "valueExpression": "$.Body.heartRate",
+            "valueName": "hr"
+      }
+    ]
+  }
+}   
+
 ```
 
 **Blood pressure**
 
 *Message*
 
 ```json
+
 {
     "Body": {
         "systolic": "123",
@@ -90,37 +94,43 @@ If you're using Azure IoT Hub Device SDKs, you can still use the JsonPathContent
         "iothub-connection-device-id" : "device123"
     }
 }
+
 ```
 
 *Template*
 
 ```json
+
 {
+  "templateType": "IotJsonPathContentTemplate",
+  "template": {
     "typeName": "bloodpressure",
     "typeMatchExpression": "$..[?(@Body.systolic && @Body.diastolic)]",
     "values": [
-        {
+      {
             "required": "true",
             "valueExpression": "$.Body.systolic",
             "valueName": "systolic"
-        },
-        {
+      },
+      {
             "required": "true",
             "valueExpression": "$.Body.diastolic",
             "valueName": "diastolic"
-        }
+      }
     ]
+  }
 }
+
 ```
 
 > [!TIP]
 > See the MedTech service [troubleshooting guide](./iot-troubleshoot-guide.md) for assistance fixing common errors and issues.
 
 ## Next steps
 
-In this article, you learned how to use Device mappings. To learn how to use FHIR destination mappings, see
+In this article, you learned how to use IotJsonPathContentTemplate mappings with the MedTech service device mapping. To learn how to use MedTech service FHIR destination mapping, see
 
 >[!div class="nextstepaction"]
->[How to use FHIR destination mappings](how-to-use-fhir-mappings.md)
+>[How to use FHIR destination mapping](how-to-use-fhir-mappings.md)
 
-(FHIR®) is a registered trademark of [HL7](https://hl7.org/fhir/) and is used with the permission of HL7.
+FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.