Merge pull request #256809 from msjasteppe/medtech-include-statement-phase-1

Updating with trademark include

Author: Jill Grant

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

@@ -3,22 +3,19 @@ title: MedTech service and Azure Machine Learning Service - Azure Health Data Se
 description: Learn how to use the MedTech service and the Azure Machine Learning Service
 author: msjasteppe
 ms.service: healthcare-apis
-ms.subservice: fhir
+ms.subservice: iomt
 ms.topic: conceptual
 ms.date: 07/21/2023
 ms.author: jasteppe
 ---
 
 # MedTech service and Azure Machine Learning Service
 
-> [!NOTE]
-> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
-
 In this article, learn about 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 to seamlessly integrate 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 MedTech service enables IoT devices to seamlessly integrate 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.
 
@@ -57,9 +54,9 @@ The four line colors show the different parts of the data journey.
 12. Azure Databricks sends a payload to an Azure Function (ML Output).
 13. RiskAssessment and/or Flag resource submitted to FHIR service. 
     1. For each observation window, a RiskAssessment resource is submitted to the FHIR service. 
-    2. For observation windows where the risk assessment is outside the acceptable range a Flag resource should also be submitted to the FHIR service.
+    2. For observation windows where the RiskAssessment 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.
+15. Power BI Dashboard is updated with RiskAssessment output in under 15 minutes.
 
 **Warm path**
 
@@ -68,22 +65,11 @@ The four line colors show the different parts of the data journey.
 18. Care Coordination through Microsoft Teams for Healthcare Patient App.
 
 ## Next steps
-
-In this article, you learned about the MedTech service and Machine Learning service integration. 
-
-For an overview of the MedTech service, see
-
-> [!div class="nextstepaction"]
-> [What is the MedTech service?](overview.md)
-
-To learn about the MedTech service device message data transformation, see
-
-> [!div class="nextstepaction"]
-> [Understand the MedTech service device data processing stages](overview-of-device-data-processing-stages.md)
-
-To learn about methods for deploying the MedTech service, see
-
-> [!div class="nextstepaction"]
-> [Choose a deployment method for the MedTech service](deploy-new-choose.md)
-
-FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+ 
+[What is the MedTech service?](overview.md)
+ 
+[Understand the MedTech service device data processing stages](overview-of-device-data-processing-stages.md)
+ 
+[Choose a deployment method for the MedTech service](deploy-new-choose.md)
+ 
+[!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

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

@@ -3,22 +3,19 @@ title: MedTech service Microsoft Power BI - Azure Health Data Services
 description: Learn how to use the MedTech service and Power BI
 author: msjasteppe
 ms.service: healthcare-apis
-ms.subservice: fhir
+ms.subservice: iomt
 ms.topic: conceptual
 ms.date: 07/21/2023
 ms.author: jasteppe
 ---
 
 # MedTech service and Microsoft Power BI
 
-> [!NOTE]
-> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
-
 In this article, learn about using the MedTech service and Microsoft Power Business Intelligence (Power 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 Things (IoT) 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, see [Embed Power BI content in Microsoft Teams](/power-bi/collaborate-share/service-embed-report-microsoft-teams).
 
@@ -38,21 +35,10 @@ Azure IoT Edge can be used in with IoT Hub to create an on-premises endpoint for
 
 ## Next steps
 
-In this article, you've learned about the MedTech service and Power BI integration. 
-
-For an overview of the MedTech service, see
-
-> [!div class="nextstepaction"]
-> [What is the MedTech service?](overview.md)
-
-To learn about the MedTech service device message data transformation, see
-
-> [!div class="nextstepaction"]
-> [Understand the MedTech service device data processing stages](overview-of-device-data-processing-stages.md)
+[What is the MedTech service?](overview.md)
 
-To learn about methods for deploying the MedTech service, see
+[Understand the MedTech service device data processing stages](overview-of-device-data-processing-stages.md)
 
-> [!div class="nextstepaction"]
-> [Choose a deployment method for the MedTech service](deploy-new-choose.md)
+[Choose a deployment method for the MedTech service](deploy-new-choose.md)
 
-FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+[!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

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

@@ -3,22 +3,19 @@ title: MedTech service and Teams notifications - Azure Health Data Services
 description: Learn how to use the MedTech service and Teams notifications
 author: msjasteppe
 ms.service: healthcare-apis
-ms.subservice: fhir
+ms.subservice: iomt
 ms.topic: conceptual
 ms.date: 07/21/2023
 ms.author: jasteppe
 ---
 
 # MedTech service and Microsoft Teams notifications
 
-> [!NOTE]
-> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
-
 In this article, learn about using the MedTech service and Microsoft Teams for notifications.
 
 ## The MedTech service and Teams notifications reference architecture
 
-When combining the MedTech service, the 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.
 
@@ -40,21 +37,10 @@ Azure IoT Edge can be used in with IoT Hub to create an on-premises end point fo
 
 ## Next steps
 
-In this article, you've learned about the MedTech service and Teams notifications integration. 
-
-For an overview of the MedTech service, see
-
-> [!div class="nextstepaction"]
-> [What is the MedTech service?](overview.md)
-
-To learn about the MedTech service device message data transformation, see
-
-> [!div class="nextstepaction"]
-> [Understand the MedTech service device data processing stages](overview-of-device-data-processing-stages.md)
+[What is the MedTech service?](overview.md)
 
-To learn about methods for deploying the MedTech service, see
+[Understand the MedTech service device data processing stages](overview-of-device-data-processing-stages.md)
 
-> [!div class="nextstepaction"]
-> [Choose a deployment method for the MedTech service](deploy-new-choose.md)
+[Choose a deployment method for the MedTech service](deploy-new-choose.md)
 
-FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+[!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

articles/healthcare-apis/iot/deploy-arm-template.md

@@ -3,7 +3,7 @@ title: Deploy the MedTech service using an Azure Resource Manager template - Azu
 description: Learn how to deploy the MedTech service using an Azure Resource Manager template.
 author: msjasteppe
 ms.service: healthcare-apis
-ms.subservice: fhir
+ms.subservice: iomt
 ms.custom: devx-track-arm-template
 ms.topic: quickstart
 ms.date: 07/05/2023
@@ -12,9 +12,6 @@ ms.author: jasteppe
 
 # Quickstart: Deploy the MedTech service using an Azure Resource Manager template
 
-> [!NOTE]
-> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
-
 To implement infrastructure as code for your Azure solutions, use Azure Resource Manager templates (ARM templates). The template is a [JavaScript Object Notation (JSON)](https://www.json.org/) file that defines the infrastructure and configuration for your project. The template uses declarative syntax, which lets you state what you intend to deploy without having to write the sequence of programming commands to create it. In the template, you specify the resources to deploy and the properties for those resources. 
 
 In this quickstart, learn how to:
@@ -107,7 +104,7 @@ When deployment is completed, the following resources and access roles are creat
 
 * Health Data Services workspace.
 
-* Health Data Services Fast Healthcare Interoperability Resources FHIR service.
+* Health Data Services FHIR® service.
 
 * Health Data Services MedTech service with the [system-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md) enabled and granted the following access roles:
 
@@ -130,21 +127,10 @@ After you have successfully deployed an instance of the MedTech service, you'll
 
 ## Next steps
 
-In this quickstart, you learned how to deploy the MedTech service in the Azure portal using an ARM template with the **Deploy to Azure** button. 
-
-To learn about other methods of deploying the MedTech service, see
-
-> [!div class="nextstepaction"]
-> [Choose a deployment method for the MedTech service](deploy-new-choose.md)
-
-For an overview of the MedTech service device data processing stages, see
-
-> [!div class="nextstepaction"]
-> [Overview of the MedTech service device data processing stages](overview-of-device-data-processing-stages.md)
+[Choose a deployment method for the MedTech service](deploy-new-choose.md)
 
-For frequently asked questions (FAQs) about the MedTech service, see
+[Overview of the MedTech service device data processing stages](overview-of-device-data-processing-stages.md)
 
-> [!div class="nextstepaction"]
-> [Frequently asked questions about the MedTech service](frequently-asked-questions.md)
+[Frequently asked questions about the MedTech service](frequently-asked-questions.md)
 
-FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+[!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

articles/healthcare-apis/iot/deploy-bicep-powershell-cli.md

@@ -3,7 +3,7 @@ title: Deploy the MedTech service using a Bicep file and Azure PowerShell or the
 description: Learn how to deploy the MedTech service using a Bicep file and Azure PowerShell or the Azure CLI.
 author: msjasteppe
 ms.service: healthcare-apis
-ms.subservice: fhir
+ms.subservice: iomt
 ms.custom: devx-track-bicep, devx-track-azurepowershell, devx-track-azurecli
 ms.topic: quickstart
 ms.date: 07/12/2023
@@ -12,9 +12,6 @@ ms.author: jasteppe
 
 # Quickstart: Deploy the MedTech service using a Bicep file and Azure PowerShell or the Azure CLI
 
-> [!NOTE]
-> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
-
 Bicep is a domain-specific language (DSL) that uses declarative syntax to deploy Azure resources. In a Bicep file, you define the infrastructure you want to deploy to Azure, and then use that file throughout the development lifecycle to repeatedly deploy your infrastructure. Your resources are deployed in a consistent manner Bicep provides concise syntax, reliable type safety, and support for code reuse. Bicep offers a first-class authoring experience for your infrastructure-as-code solutions in Azure.
 
 In this quickstart, learn how to use Azure PowerShell or the Azure CLI to deploy an instance of the MedTech service using a Bicep file. 
@@ -173,7 +170,7 @@ When deployment is completed, the following resources and access roles are creat
 
 * Health Data Services workspace.
 
-* Health Data Services FHIR service.
+* Health Data Services FHIR® service.
 
 * Health Data Services MedTech service with the required [system-assigned managed identity](../../active-directory/managed-identities-azure-resources/overview.md) roles:
 
@@ -219,21 +216,10 @@ For example: `az group delete --resource-group BicepTestDeployment`
 
 ## Next steps
 
-In this quickstart, you learned how to use Azure PowerShell or the Azure CLI to deploy an instance of the MedTech service using a Bicep file. 
-
-To learn about other methods of deploying the MedTech service, see
-
-> [!div class="nextstepaction"]
-> [Choose a deployment method for the MedTech service](deploy-new-choose.md)
-
-For an overview of the MedTech service device data processing stages, see
-
-> [!div class="nextstepaction"]
-> [Overview of the MedTech service device data processing stages](overview-of-device-data-processing-stages.md)
+[Choose a deployment method for the MedTech service](deploy-new-choose.md)
 
-For frequently asked questions (FAQs) about the MedTech service, see
+[Overview of the MedTech service device data processing stages](overview-of-device-data-processing-stages.md)
 
-> [!div class="nextstepaction"]
-> [Frequently asked questions about the MedTech service](frequently-asked-questions.md)
+[Frequently asked questions about the MedTech service](frequently-asked-questions.md)
 
-FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+[!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]

articles/healthcare-apis/iot/deploy-choose-method.md

@@ -3,7 +3,7 @@ title: Choose a deployment method for the MedTech service - Azure Health Data Se
 description: Learn about the different methods for deploying the MedTech service.
 author: msjasteppe
 ms.service: healthcare-apis
-ms.subservice: fhir
+ms.subservice: iomt
 ms.custom: devx-track-azurecli, devx-track-azurepowershell, devx-track-arm-template, devx-track-bicep
 ms.topic: quickstart
 ms.date: 07/05/2023
@@ -12,9 +12,6 @@ ms.author: jasteppe
 
 # Quickstart: Choose a deployment method for the MedTech service
 
-> [!NOTE]
-> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
-
 The MedTech service provides multiple methods for deployment into Azure. Each deployment method has different advantages that allow you to customize your deployment to suit your needs and use cases.
 
 In this quickstart, learn about these deployment methods:
@@ -27,13 +24,13 @@ In this quickstart, learn about these deployment methods:
 
 ## Deployment overview
 
-The following diagram outlines the basic steps of the MedTech service deployment. These steps may help you analyze the deployment options and determine which deployment method is best for you.
+The following diagram outlines the basic steps of the MedTech service deployment. These steps might help you analyze the deployment options and determine which deployment method is best for you.
 
 :::image type="content" source="media/get-started/get-started-with-medtech-service.png" alt-text="Diagram showing MedTech service deployment overview." lightbox="media/get-started/get-started-with-medtech-service.png":::
 
 ## ARM template including an Azure Iot Hub using the Deploy to Azure button
 
-Using an ARM template with the **Deploy to Azure** button is an easy and fast deployment method because it automates the deployment, most configuration steps, and uses the Azure portal. The deployed MedTech service and Azure IoT Hub are fully functional including conforming and valid device and FHIR destination mappings. Use the Azure IoT Hub to create devices and send device messages to the MedTech service.
+Using an ARM template with the **Deploy to Azure** button is an easy and fast deployment method because it automates the deployment, most configuration steps, and uses the Azure portal. The deployed MedTech service and Azure IoT Hub are fully functional including conforming and valid device and FHIR® destination mappings. Use the Azure IoT Hub to create devices and send device messages to the MedTech service.
 
 [![Deploy to Azure](https://aka.ms/deploytoazurebutton)](https://portal.azure.com/#create/Microsoft.Template/uri/https%3A%2F%2Fraw.githubusercontent.com%2FAzure%2Fazure-quickstart-templates%2Fmaster%2Fquickstarts%2Fmicrosoft.healthcareapis%2Fworkspaces%2Fiotconnectors-with-iothub%2Fazuredeploy.json)
 
@@ -61,7 +58,7 @@ To learn more about deploying the MedTech service using a Bicep file and Azure P
 
 ## Azure portal
 
-Using the Azure portal allows you to see the details of each deployment step. The Azure portal deployment has many steps, but it provides valuable technical information that may be useful for customizing and troubleshooting your MedTech service.
+Using the Azure portal allows you to see the details of each deployment step. The Azure portal deployment has many steps, but it provides valuable technical information that might be useful for customizing and troubleshooting your MedTech service.
 
 To learn more about deploying the MedTech service using the Azure portal, see [Deploy the MedTech service using the Azure portal](deploy-manual-portal.md).
 
@@ -78,21 +75,10 @@ To learn more about deploying the MedTech service using the Azure portal, see [D
 
 ## Next steps
 
-In this quickstart, you learned about the different types of deployment methods for the MedTech service. 
-
-To learn about other methods of deploying the MedTech service, see
-
-> [!div class="nextstepaction"]
-> [Choose a deployment method for the MedTech service](deploy-new-choose.md)
-
-For an overview of the MedTech service device data processing stages, see
-
-> [!div class="nextstepaction"]
-> [Overview of the MedTech service device data processing stages](overview-of-device-data-processing-stages.md)
+[Choose a deployment method for the MedTech service](deploy-new-choose.md)
 
-For frequently asked questions (FAQs) about the MedTech service, see
+[Overview of the MedTech service device data processing stages](overview-of-device-data-processing-stages.md)
 
-> [!div class="nextstepaction"]
-> [Frequently asked questions about the MedTech service](frequently-asked-questions.md)
+[Frequently asked questions about the MedTech service](frequently-asked-questions.md)
 
-FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
+[!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]