Additional edits and formatting

msjasteppe · msjasteppe · commit 77f3704830f5 · 2023-01-12T14:51:01.000-08:00
diff --git a/articles/healthcare-apis/iot/concepts-machine-learning.md b/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&#174; is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
diff --git a/articles/healthcare-apis/iot/concepts-power-bi.md b/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&#174; is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
diff --git a/articles/healthcare-apis/iot/concepts-teams.md b/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&#174; is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
diff --git a/articles/healthcare-apis/iot/git-projects.md b/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)
diff --git a/articles/healthcare-apis/iot/how-to-configure-device-mappings.md b/articles/healthcare-apis/iot/how-to-configure-device-mappings.md
@@ -202,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 errors](troubleshoot-errors.md) for assistance resolving common MedTech service errors. 
+> See the MedTech service article [Troubleshoot MedTech service errors](troubleshoot-errors.md) for assistance fixing common MedTech service errors. 
 
 ## Next steps
 
diff --git a/articles/healthcare-apis/iot/how-to-configure-fhir-mappings.md b/articles/healthcare-apis/iot/how-to-configure-fhir-mappings.md
@@ -275,7 +275,7 @@ Represents the [CodeableConcept](http://hl7.org/fhir/datatypes.html#CodeableConc
 ```
 
 > [!TIP]
-> See the MedTech service article [Troubleshoot MedTech errors](troubleshoot-errors.md) for assistance resolving common MedTech service errors.
+> See the MedTech service article [Troubleshoot MedTech service errors](troubleshoot-errors.md) for assistance fixing common MedTech service errors.
 
 ## Next steps
 
diff --git a/articles/healthcare-apis/iot/how-to-configure-metrics.md b/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)
diff --git a/articles/healthcare-apis/iot/how-to-create-mappings-copies.md b/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&#174;) is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
diff --git a/articles/healthcare-apis/iot/how-to-use-calculatedcontenttemplate-mappings.md b/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
 
diff --git a/articles/healthcare-apis/iot/how-to-use-custom-functions.md b/articles/healthcare-apis/iot/how-to-use-custom-functions.md
@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 12/15/2022
+ms.date: 1/12/2023
 ms.author: jasteppe
 ---
 
@@ -182,13 +182,13 @@ Examples:
 | {"unix": 0}              | fromUnixTimestampMs(unix) | "1970-01-01T00:00:00+0" |
 
 > [!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 MedTech service errors. 
 
 ## Next steps
 
-In this article, you learned how to use the MedTech service custom functions. 
+In this article, you learned how to use the MedTech service custom functions with the device mappings. 
 
-To learn how to configure the MedTech service device mapping, see
+To learn how to configure the MedTech service device mappings, see
 
 > [!div class="nextstepaction"]
 > [How to configure device mappings](how-to-configure-device-mappings.md)
diff --git a/articles/healthcare-apis/iot/how-to-use-iotjsonpathcontenttemplate-mappings.md b/articles/healthcare-apis/iot/how-to-use-iotjsonpathcontenttemplate-mappings.md
@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 12/15/2022
+ms.date: 1/12/2023
 ms.author: jasteppe
 ---
 
@@ -265,13 +265,13 @@ With each of these examples, you're provided with:
 ```
 
 > [!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 MedTech service errors.
 
 ## Next steps
 
-In this article, you learned how to use IotJsonPathContentTemplate mappings with the MedTech service device mapping. 
+In this article, you learned how to use IotJsonPathContentTemplate mappings with the MedTech service device mappings. 
 
-To learn how to configure the MedTech service FHIR destination mapping, see
+To learn how to configure the MedTech service FHIR destination mappings, see
 
 > [!div class="nextstepaction"]
 > [How to configure FHIR destination mappings](how-to-configure-fhir-mappings.md)
diff --git a/articles/healthcare-apis/iot/how-to-use-monitoring-tab.md b/articles/healthcare-apis/iot/how-to-use-monitoring-tab.md
@@ -6,7 +6,7 @@ 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
 ---
 
@@ -62,7 +62,7 @@ Metric category|Metric name|Metric description|
 
 ## Next steps
 
-In this article, you learned about how to use the MedTech service monitoring tab.
+In this article, you learned how to use the MedTech service monitoring tab.
 
 To learn how to configure the MedTech service metrics, see
 
diff --git a/articles/healthcare-apis/iot/troubleshoot-errors.md b/articles/healthcare-apis/iot/troubleshoot-errors.md
@@ -1,6 +1,6 @@
 ---
 title: Troubleshoot MedTech service errors - Azure Health Data Services
-description: This article assist troubleshooting and resolving MedTech service errors.
+description: This article assists troubleshooting and resolving MedTech service errors.
 services: healthcare-apis
 author: msjasteppe
 ms.service: healthcare-apis
@@ -12,7 +12,7 @@ ms.author: jasteppe
 
 # Troubleshoot MedTech service errors
 
-This article provides assistance troubleshooting and resolving MedTech service errors.
+This article provides assistance troubleshooting and fixing 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:
@@ -26,11 +26,11 @@ This article provides assistance troubleshooting and resolving MedTech service e
 > [!NOTE]
 > When you open an [Azure Technical Support](https://azure.microsoft.com/support/create-ticket/) ticket for the MedTech service, include [copies of your device and FHIR destination mappings](how-to-create-mappings-copies.md) to assist in the troubleshooting process.
 
-## Error messages and conditions
+## Errors and fixes
 
 ### The operation being performed by the MedTech service
 
-This property represents the operation being performed by the MedTech service when the error has occurred. An operation generally represents the data flow stage while processing a device message. Below is a list of possible values for this property.
+This property represents the operation being performed by the MedTech service when the error has occurred. An operation generally represents the data flow stage while processing a device message. Here's a list of possible values for this property.
 
 > [!NOTE]
 > For information about the different stages of data flow in the MedTech service, see [The MedTech service data flow](data-flow.md).
@@ -45,7 +45,7 @@ This property represents the operation being performed by the MedTech service wh
 
 #### The severity of the error
 
-This property represents the severity of the occurred error. Below is a list of possible values for this property.
+This property represents the severity of the occurred error. Here's a list of possible values for this property.
 
 |Severity|Description|
 |---------------|-----------|
@@ -55,7 +55,7 @@ This property represents the severity of the occurred error. Below is a list of
 
 #### The type of error
 
-This property signifies a category for a given error, which it basically represents a logical grouping for similar types of errors. Below is a list of possible values for this property.
+This property signifies a category for a given error, which it basically represents a logical grouping for similar types of errors. Here's a list of possible values for this property.
 
 |Error type|Description|
 |----------|-----------|
@@ -69,7 +69,7 @@ This property signifies a category for a given error, which it basically represe
 
 #### The name of the error
 
-This property provides the name for a specific error. Below is the list of all error names with their description and associated error type(s), severity, and data flow stage(s).
+This property provides the name for a specific error. Here's the list of all error names with their description and associated error type(s), severity, and data flow stage(s).
 
 |Error name|Description|Error type(s)|Error severity|Data flow stage(s)|
 |----------|-----------|-------------|--------------|------------------|
@@ -120,9 +120,9 @@ This property provides the name for a specific error. Below is the list of all e
 
 In this article, you learned how to troubleshoot MedTech service error messages and conditions. 
 
-To learn how to troubleshoot the MedTech service device and FHIR destination mappings, see
+To learn about the MedTech service frequently asked question (FAQs), see
 
 > [!div class="nextstepaction"]
-> [Troubleshoot the MedTech service device and FHIR destination mappings](troubleshoot-mappings.md)
+> [Frequently asked questions about the MedTech service](frequently-asked-questions.md)
 
 FHIR&#174; is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
