Updating and consolidating troubleshooting guides

Author: msjasteppe

.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/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 errors](troubleshoot-errors.md) for assistance resolving 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 errors](troubleshoot-errors.md) for assistance resolving common MedTech service errors.
 
 ## Next steps
 

articles/healthcare-apis/iot/toc.yml

@@ -71,13 +71,11 @@ items:
       href: how-to-configure-metrics.md
     - name: Enable diagnostic settings
       href: how-to-enable-diagnostic-settings.md
-  - name: Troubleshoot and problem solve
+  - name: Troubleshoot
     expanded: false
     items:
-    - name: Errors and conditions
-      href: troubleshoot-error-messages-and-conditions.md
-    - name: Device and FHIR destination mappings
-      href: troubleshoot-mappings.md
+    - name: Errors
+      href: troubleshoot-errors.md
 - name: Concepts
   expanded: false
   items:

articles/healthcare-apis/iot/troubleshoot-error-messages-and-conditions.md renamed to articles/healthcare-apis/iot/troubleshoot-errors.md

@@ -1,18 +1,18 @@
 ---
-title: Troubleshoot MedTech service error messages and conditions - Azure Health Data Services
-description: This article helps users troubleshoot MedTech service errors messages and conditions.
+title: Troubleshoot MedTech service errors - Azure Health Data Services
+description: This article assist troubleshooting and resolving MedTech service errors.
 services: healthcare-apis
 author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: iomt
 ms.topic: troubleshooting
-ms.date: 12/15/2022
+ms.date: 1/12/2023
 ms.author: jasteppe
 ---
 
-# Troubleshoot MedTech service error messages and conditions
+# Troubleshoot MedTech service errors
 
-This article provides steps for troubleshooting and fixing MedTech service error messages and conditions.
+This article provides assistance troubleshooting and resolving MedTech service errors.
 
 > [!TIP]
 > Having access to metrics and logs are essential tools for assisting you in troubleshooting and assessing the overall performance of your MedTech service. Check out these MedTech service articles to learn more about how to enable, configure, and use these monitoring features: