Merge pull request #236290 from msjasteppe/cleanup-edits

Cleanup edits

Author: JamesJBarnett

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

@@ -1,11 +1,11 @@
 ---
 title: The MedTech service and Azure Machine Learning Service - Azure Health Data Services
-description: In this article, you'll learn how to use the MedTech service and the Azure Machine Learning Service
+description: Learn how to use the MedTech service and the Azure Machine Learning Service
 author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: conceptual
-ms.date: 02/27/2023
+ms.date: 04/28/2023
 ms.author: jasteppe
 ---
 
@@ -14,11 +14,11 @@ ms.author: jasteppe
 > [!NOTE]
 > [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
 
-In this article, we'll explore using the MedTech service and Azure Machine Learning Service.
+In this article, we explore using the MedTech service and the Azure Machine Learning Service.
 
 ## The MedTech service and Azure Machine Learning Service reference architecture
 
-The MedTech service enables IoT devices seamless integration with FHIR services. This reference architecture is designed to accelerate adoption of Internet of Medical Things (IoMT) projects. This solution uses Azure Databricks for the Machine Learning (ML) compute. However, Azure ML Services with Kubernetes or a partner ML solution could fit into the Machine Learning Scoring Environment.
+The MedTech service enables IoT devices to seamless integration with FHIR services. This reference architecture is designed to accelerate adoption of Internet of Things (IoT) projects. This solution uses Azure Databricks for the Machine Learning (ML) compute. However, Azure Machine Learning Services with Kubernetes or a partner ML solution could fit into the Machine Learning Scoring Environment.
 
 The four line colors show the different parts of the data journey.
 
@@ -34,7 +34,7 @@ The four line colors show the different parts of the data journey.
 1. Data from IoT device or via device gateway sent to Azure IoT Hub/Azure IoT Edge.
 2. Data from Azure IoT Edge sent to Azure IoT Hub.
 3. Copy of raw IoT device data sent to a secure storage environment for device administration.
-4. PHI IoMT payload moves from Azure IoT Hub to the MedTech service. Multiple Azure services are represented by the MedTech service icon.
+4. PHI IoT payload moves from Azure IoT Hub to the MedTech service. The MedTech service icon represents multiple Azure services.
 5. Three parts to number 5: 
  a. The MedTech service requests Patient resource from the FHIR service. 
  b. The FHIR service sends Patient resource back to the MedTech service. 
@@ -43,18 +43,18 @@ The four line colors show the different parts of the data journey.
 **Machine Learning and AI Data Route – Steps 6 through 11**
 
 6. Normalized ungrouped data stream sent to an Azure Function (ML Input).
-7. Azure Function (ML Input) requests Patient resource to merge with IoMT payload.
-8. IoMT payload with PHI is sent to an event hub for distribution to Machine Learning compute and storage.
-9. PHI IoMT payload is sent to Azure Data Lake Storage Gen 2 for scoring observation over longer time windows.
-10. PHI IoMT payload is sent to Azure Databricks for windowing, data fitting, and data scoring.
+7. Azure Function (ML Input) requests Patient resource to merge with IoT payload.
+8. IoT payload with PHI is sent to an event hub for distribution to Machine Learning compute and storage.
+9. PHI IoT payload is sent to Azure Data Lake Storage Gen 2 for scoring observation over longer time windows.
+10. PHI IoT payload is sent to Azure Databricks for windowing, data fitting, and data scoring.
 11. The Azure Databricks requests more patient data from data lake as needed. a. Azure Databricks also sends a copy of the scored data to the data lake.
 
 **Notification and Care Coordination – Steps 12 - 18**
 
 **Hot path**
 
 12. Azure Databricks sends a payload to an Azure Function (ML Output).
-13. RiskAssessment and/or Flag resource submitted to FHIR service. a. For each observation window, a RiskAssessment resource will be submitted to the FHIR service. b. For observation windows where the risk assessment is outside the acceptable range a Flag resource should also be submitted to the FHIR service.
+13. RiskAssessment and/or Flag resource submitted to FHIR service. a. For each observation window, a RiskAssessment resource is submitted to the FHIR service. b. For observation windows where the risk assessment is outside the acceptable range a Flag resource should also be submitted to the FHIR service.
 14. Scored data sent to data repository for routing to appropriate care team. Azure SQL Server is the data repository used in this design because of its native interaction with Power BI.
 15. Power BI Dashboard is updated with Risk Assessment output in under 15 minutes.
 

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

@@ -1,11 +1,11 @@
 ---
 title: MedTech service Microsoft Power BI - Azure Health Data Services
-description: In this article, you'll learn how to use the MedTech service and Power BI
+description: Learn how to use the MedTech service and Power BI
 author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: conceptual
-ms.date: 02/27/2023
+ms.date: 04/28/2023
 ms.author: jasteppe
 ---
 
@@ -14,11 +14,11 @@ ms.author: jasteppe
 > [!NOTE]
 > [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
 
-In this article, we'll explore using the MedTech service and Microsoft Power Business Intelligence (BI).
+In this article, we explore using the MedTech service and Microsoft Power Business Intelligence (BI).
 
 ## The MedTech service and Power BI reference architecture
 
-This reference architecture shows the basic components of using the Microsoft cloud services to enable Power BI on top of Internet of Medical Things (IoMT) and FHIR data.
+This reference architecture shows the basic components of using the Microsoft cloud services to enable Power BI on top of Internet of Things (IoT) and FHIR data.
 
 You can even embed Power BI dashboards inside the Microsoft Teams client to further enhance care team coordination. For more information on embedding Power BI in Teams, visit [here](/power-bi/collaborate-share/service-embed-report-microsoft-teams).
 

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

@@ -1,11 +1,11 @@
 ---
 title: The MedTech service and Teams notifications - Azure Health Data Services
-description: In this article, you'll learn how to use the MedTech service and Teams notifications
+description: Learn how to use the MedTech service and Teams notifications
 author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: conceptual
-ms.date: 02/27/2023
+ms.date: 04/28/2023
 ms.author: jasteppe
 ---
 
@@ -14,11 +14,11 @@ ms.author: jasteppe
 > [!NOTE]
 > [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
 
-In this article, we'll explore using the MedTech service and Microsoft Teams for notifications.
+In this article, we explore using the MedTech service and Microsoft Teams for notifications.
 
 ## The MedTech service and Teams notifications reference architecture
 
-When combining the MedTech service, a FHIR service, and Teams, you can enable multiple care solutions.
+When combining the MedTech service, the FHIR service, and Teams, you can enable multiple care solutions.
 
 The diagram is a MedTech service to Teams notifications conceptual architecture for enabling the MedTech service, the FHIR service, and the Teams Patient App.
 

articles/healthcare-apis/iot/media/overview-of-fhir-destination-mapping/fhir-destination-mapping-templates-diagram.png

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: overview
-ms.date: 04/14/2023
+ms.date: 04/24/2023
 ms.author: jasteppe
 ---
 
@@ -52,7 +52,7 @@ The normalization process validates the device mapping before allowing it to be
 |values[].required       |True                         |True                          |
 
 > [!NOTE] 
-> `values[].valueName, values[].valueExpression`, `values[].required` and elements are only required if you have a value entry in the array. It's valid to have no values mapped. These elements are used when the telemetry being sent is an event.
+> The `values[].valueName, values[].valueExpression`, and `values[].required` elements are only required if you have a value entry in the array. It's valid to have no values mapped. These elements are used when the telemetry being sent is an event.
 >
 > For example, some scenarios may require creating a FHIR Observation in the FHIR service that does not contain a value.