Merge pull request #223836 from msjasteppe/troubleshoot-consolidation

Updating and consolidating troubleshooting guides

Author: jborsecnik

.openpublishing.redirection.healthcare-apis.json

@@ -610,11 +610,15 @@
         "redirect_document_id": false
     },
     {   "source_path_from_root": "/articles/healthcare-apis/iot/iot-troubleshoot-error-messages-and-conditions.md",
-        "redirect_url": "/azure/healthcare-apis/iot/troubleshoot-error-messages-and-conditions",
+        "redirect_url": "/azure/healthcare-apis/iot/troubleshoot-errors",
+        "redirect_document_id": false
+    },
+    {   "source_path_from_root": "/articles/healthcare-apis/iot/troubleshoot-error-messages-and-conditions.md",
+        "redirect_url": "/azure/healthcare-apis/iot/troubleshoot-errors",
         "redirect_document_id": false
     },
     {   "source_path_from_root": "/articles/healthcare-apis/iot/iot-troubleshoot-mappings.md",
-        "redirect_url": "/azure/healthcare-apis/iot/troubleshoot-mappings",
+        "redirect_url": "/azure/healthcare-apis/iot/troubleshoot-errors",
         "redirect_document_id": false
     },
     {   "source_path_from_root": "/articles/healthcare-apis/iot/iot-connector-faqs.md",
@@ -637,6 +641,10 @@
         "redirect_url": "/azure/healthcare-apis/iot/deploy-new-arm",
         "redirect_document_id": false
     },
+    {   "source_path_from_root": "/articles/healthcare-apis/iot/troubleshoot-mappings.md",
+        "redirect_url": "/azure/healthcare-apis/iot/troubleshoot-errors",
+        "redirect_document_id": false
+    },
     {   "source_path_from_root": "/articles/healthcare-apis/events/events-display-metrics.md",
         "redirect_url": "/azure/healthcare-apis/events/events-use-metrics",
         "redirect_document_id": false

articles/healthcare-apis/iot/concepts-machine-learning.md

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: conceptual
-ms.date: 12/27/2022
+ms.date: 1/12/2023
 ms.author: jasteppe
 ---
 
@@ -68,6 +68,6 @@ In this article, you learned about the MedTech service and Machine Learning serv
 For an overview of the MedTech service, see
 
 > [!div class="nextstepaction"]
-> [The MedTech service overview](overview.md)
+> [What is the MedTech service?](overview.md)
 
 FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.

articles/healthcare-apis/iot/concepts-power-bi.md

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: conceptual
-ms.date: 12/27/2021
+ms.date: 1/12/2023
 ms.author: jasteppe
 ---
 
@@ -40,6 +40,6 @@ In this article, you've learned about the MedTech service and Power BI integrati
 For an overview of the MedTech service, see
 
 > [!div class="nextstepaction"]
-> [The MedTech service overview](overview.md)
+> [What is the MedTech service?](overview.md)
 
 FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.

articles/healthcare-apis/iot/concepts-teams.md

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: conceptual
-ms.date: 12/27/2022
+ms.date: 1/12/2023
 ms.author: jasteppe
 ---
 
@@ -42,6 +42,6 @@ In this article, you've learned about the MedTech service and Teams notification
 For an overview of the MedTech service, see
 
 > [!div class="nextstepaction"]
-> [The MedTech service overview](overview.md)
+> [What is the MedTech service?](overview.md)
 
 FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.

articles/healthcare-apis/iot/git-projects.md

@@ -1,11 +1,11 @@
 ---
 title: GitHub projects for the MedTech service - Azure Health Data Services
-description: MedTech service has a robust open-source (GitHub) library for ingesting device messages from popular wearable devices.
+description: The MedTech service has a robust open-source (GitHub) library for ingesting device messages from popular wearable devices.
 services: healthcare-apis
 author: msjasteppe
 ms.service: healthcare-apis
 ms.topic: reference
-ms.date: 12/15/2022
+ms.date: 1/12/2023
 ms.author: jasteppe
 ---
 # Open-source projects
@@ -49,7 +49,7 @@ Health Data Sync
 
 In this article, you learned about the open-source projects for the MedTech service.
 
-Learn about the different deployment methods for the MedTech service, see
+To learn about the different deployment methods for the MedTech service, see
 
 > [!div class="nextstepaction"]
 > [Choose a deployment method for the MedTech service](deploy-new-choose.md)

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

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 12/27/2022
+ms.date: 1/12/2023
 ms.author: jasteppe
 ---
 
@@ -61,6 +61,29 @@ The content payload itself is an Azure Event Hubs message, which is composed of
     }
 }
 ```
+
+## Device mappings validations
+
+The validation process validates the device mappings before allowing them to be saved for use. These elements are required in the device mapping templates.
+
+**Device mappings**
+
+|Element|Required|
+|:-------|:------|
+|TypeName|True|
+|TypeMatchExpression|True|
+|DeviceIdExpression|True|
+|TimestampExpression|True|
+|Values[].ValueName|True|
+|Values[].ValueExpression|True|
+
+> [!NOTE]
+> `Values[].ValueName and Values[].ValueExpression` elements are only required if you have a value entry in the array. It's valid to have no values mapped. This is used when the telemetry being sent is an event. 
+>
+> For example:
+> 
+> Some IoMT scenarios may require creating an Observation Resource in the FHIR service that does not contain a value.
+
 ## CollectionContentTemplate
 
 The CollectionContentTemplate is the **root** template type used by the MedTech service device mappings template and represents a list of all templates that will be used during the normalization process.
@@ -179,7 +202,7 @@ You can define one or more templates within the MedTech service device mapping.
 |[IotJsonPathContentTemplate](how-to-use-iot-jsonpath-content-mappings.md)|A template that supports messages sent from Azure Iot Hub or the Legacy Export Data feature of Azure Iot Central.
 
 > [!TIP]
-> See the MedTech service article [Troubleshoot MedTech service device and FHIR destination mappings](troubleshoot-mappings.md) for assistance fixing common errors and issues related to MedTech service mappings. 
+> See the MedTech service article [Troubleshoot MedTech service errors](troubleshoot-errors.md) for assistance fixing common MedTech service errors. 
 
 ## Next steps
 

articles/healthcare-apis/iot/how-to-configure-fhir-mappings.md

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 12/27/2022
+ms.date: 1/12/2023
 ms.author: jasteppe
 ---
 
@@ -25,6 +25,19 @@ configuration controls.
 > [!NOTE]
 > Mappings are stored in an underlying blob storage and loaded from blob per compute execution. Once updated they should take effect immediately. 
 
+## FHIR destination mappings validations
+
+The validation process validates the FHIR destination mappings before allowing them to be saved for use. These elements are required in the FHIR destination mappings templates.
+
+**FHIR destination mappings**
+
+|Element|Required|
+|:------|:-------|
+|TypeName|True|
+
+> [!NOTE]
+> This is the only required FHIR destination mapping element validated at this time.
+
 ### CodeValueFhirTemplate
 
 The CodeValueFhirTemplate is currently the only template supported in FHIR destination mapping at this time.  It allows you to define codes, the effective period, and the value of the observation. Multiple value types are supported: [SampledData](https://www.hl7.org/fhir/datatypes.html#SampledData), [CodeableConcept](https://www.hl7.org/fhir/datatypes.html#CodeableConcept), and [Quantity](https://www.hl7.org/fhir/datatypes.html#Quantity). Along with these configurable values, the identifier for the Observation resource and linking to the proper Device and Patient resources are handled automatically.
@@ -262,7 +275,7 @@ Represents the [CodeableConcept](http://hl7.org/fhir/datatypes.html#CodeableConc
 ```
 
 > [!TIP]
-> See the MedTech service article [Troubleshoot the MedTech service device and FHIR destination mappings](troubleshoot-mappings.md) for assistance fixing common errors and issues related to MedTech service mappings.
+> See the MedTech service article [Troubleshoot MedTech service errors](troubleshoot-errors.md) for assistance fixing common MedTech service errors.
 
 ## Next steps
 

articles/healthcare-apis/iot/how-to-configure-metrics.md

@@ -1,12 +1,12 @@
 ---
 title: Configure the MedTech service metrics - Azure Health Data Services
-description: This article explains how to display MedTech service metrics.
+description: This article explains how to configure the MedTech service metrics.
 services: healthcare-apis
 author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: iomt
 ms.topic: how-to
-ms.date: 12/27/2022
+ms.date: 1/12/2023
 ms.author: jasteppe
 ---
 
@@ -85,7 +85,7 @@ To learn how to create an Azure portal dashboard and pin tiles, see [Create a da
 
 In this article, you learned about how to configure the MedTech service metrics.
 
-To learn how to enable the MedTech service diagnostic settings to export logs and metrics to another location (for example: an Azure storage account) for audit, backup, or troubleshooting, see
+To learn how to enable the MedTech service diagnostic settings to export logs and metrics to another location (for example: Azure Log Analytics workspace) for audit, backup, or troubleshooting, see
 
 > [!div class="nextstepaction"]
 > [How to enable diagnostic settings for the MedTech service](how-to-enable-diagnostic-settings.md)

articles/healthcare-apis/iot/how-to-create-mappings-copies.md

@@ -6,7 +6,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: iomt
 ms.topic: how-to
-ms.date: 12/15/2022
+ms.date: 1/12/2023
 ms.author: jasteppe
 ---
 
@@ -54,9 +54,9 @@ This article provides steps for creating copies of your MedTech service's device
 
 In this article, you learned about how to make copies of your MedTech service device and FHIR destination mappings. 
 
-To learn how to troubleshoot device and FHIR destination mappings, see
+To learn how to troubleshoot MedTech service errors, see
 
 > [!div class="nextstepaction"]
-> [Troubleshoot the MedTech service device and FHIR destination mappings](troubleshoot-mappings.md)
+> [Troubleshoot MedTech service errors](troubleshoot-errors.md)
 
 (FHIR®) is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.

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

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 12/27/2022
+ms.date: 1/12/2023
 ms.author: jasteppe
 ---
 
@@ -538,11 +538,11 @@ In the below example, height data arrives in either inches or meters. We want al
 ```
 
 > [!TIP]
-> See the MedTech service article [Troubleshoot MedTech service device and FHIR destination mappings](troubleshoot-mappings.md) for assistance fixing common errors and issues related to the MedTech service mappings.
+> See the MedTech service article [Troubleshoot MedTech service errors](troubleshoot-errors.md) for assistance fixing MedTech service errors.
 
 ## Next steps
 
-In this article, you learned how to configure the MedTech service device mappings. 
+In this article, you learned how to configure the MedTech service device mappings using CalculatedContentTemplate mappings. 
 
 To learn how to configure FHIR destination mappings, see