Merge pull request #295450 from KendalBond007/MedTechServiceChanges_27Feb25

Stacyrch140 · web-flow · commit 316bd7313ac6 · 2025-02-27T17:15:47.000-05:00
Med tech service changes 27 feb25
diff --git a/articles/healthcare-apis/iot/concepts-machine-learning.md b/articles/healthcare-apis/iot/concepts-machine-learning.md
@@ -11,6 +11,9 @@ ms.author: chrupa
 
 # MedTech service and Azure Machine Learning Service
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 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
diff --git a/articles/healthcare-apis/iot/concepts-power-bi.md b/articles/healthcare-apis/iot/concepts-power-bi.md
@@ -11,6 +11,9 @@ ms.author: chrupa
 
 # MedTech service and Microsoft Power BI
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 In this article, learn about using the MedTech service and Microsoft Power Business Intelligence (Power BI).
 
 ## The MedTech service and Power BI reference architecture
diff --git a/articles/healthcare-apis/iot/concepts-teams.md b/articles/healthcare-apis/iot/concepts-teams.md
@@ -11,6 +11,9 @@ ms.author: chrupa
 
 # MedTech service and Microsoft Teams notifications
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 In this article, learn about using the MedTech service and Microsoft Teams for notifications.
 
 ## The MedTech service and Teams notifications reference architecture
diff --git a/articles/healthcare-apis/iot/configure-metrics.md b/articles/healthcare-apis/iot/configure-metrics.md
@@ -11,6 +11,10 @@ ms.author: chrupa
 ---
 
 # Monitor performance metrics for the MedTech service
+
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 Gain insights into the health, availability, latency, traffic, and errors of your organization's MedTech services by monitoring MedTech service metrics in the Azure portal. To help you identify patterns or trends, pin tiles for the metrics to an Azure portal dashboard for easy access and visualization.
 
 ## Configure service metrics
diff --git a/articles/healthcare-apis/iot/deploy-arm-template.md b/articles/healthcare-apis/iot/deploy-arm-template.md
@@ -12,6 +12,9 @@ ms.author: chrupa
 
 # Quickstart: Deploy the MedTech service using an Azure Resource Manager template
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 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:
diff --git a/articles/healthcare-apis/iot/deploy-bicep-powershell-cli.md b/articles/healthcare-apis/iot/deploy-bicep-powershell-cli.md
@@ -12,6 +12,9 @@ ms.author: chrupa
 
 # Quickstart: Deploy the MedTech service using a Bicep file and Azure PowerShell or the Azure CLI
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 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. 
diff --git a/articles/healthcare-apis/iot/deploy-choose-method.md b/articles/healthcare-apis/iot/deploy-choose-method.md
@@ -12,6 +12,9 @@ ms.author: chrupa
 
 # Quickstart: Choose a deployment method for the MedTech service
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 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:
diff --git a/articles/healthcare-apis/iot/deploy-json-powershell-cli.md b/articles/healthcare-apis/iot/deploy-json-powershell-cli.md
@@ -12,6 +12,9 @@ ms.author: chrupa
 
 # Quickstart: Deploy the MedTech service using an Azure Resource Manager template and Azure PowerShell or the Azure CLI
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 To implement infrastructure as code for your Azure solutions, use Azure Resource Manager templates (ARM templates). The template is a JavaScript Object Notation (JSON) 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 use Azure PowerShell or the Azure CLI to deploy an instance of the MedTech service using an Azure Resource Manager template (ARM template).
diff --git a/articles/healthcare-apis/iot/deploy-manual-portal.md b/articles/healthcare-apis/iot/deploy-manual-portal.md
@@ -11,6 +11,9 @@ ms.author: chrupa
 
 # Quickstart: Deploy the MedTech service using the Azure portal
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 The MedTech service deployment using the Azure portal is divided into the following three sections:
 
 * [Deploy prerequisite resources](#deploy-prerequisite-resources)
diff --git a/articles/healthcare-apis/iot/device-messages-through-iot-hub.md b/articles/healthcare-apis/iot/device-messages-through-iot-hub.md
@@ -13,6 +13,9 @@ ms.author: chrupa
 
 # Tutorial: Receive device messages through Azure IoT Hub
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 The MedTech service can receive messages from devices you create and manage through an IoT hub in [Azure IoT Hub](../../iot-hub/iot-concepts-and-iot-hub.md). This tutorial uses an Azure Resource Manager template (ARM template) and a **Deploy to Azure** button to deploy a MedTech service. The template also deploys an IoT hub to create and manage devices, and message routes device messages to an event hub for the MedTech service to read and process. After device data processing, the FHIR&reg; resources are persisted in the FHIR service, which is also included in the template.
 
 :::image type="content" source="media\device-messages-through-iot-hub\device-message-flow-with-iot-hub.png" border="false" alt-text="Diagram of the IoT device message flow through an IoT hub and event hub, and then into the MedTech service." lightbox="media\device-messages-through-iot-hub\device-message-flow-with-iot-hub.png":::
diff --git a/articles/healthcare-apis/iot/frequently-asked-questions.md b/articles/healthcare-apis/iot/frequently-asked-questions.md
@@ -9,9 +9,11 @@ ms.topic: faq
 ms.date: 06/05/2024
 ms.author: chrupa
 ---
-
 # MedTech service FAQ
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 ## Where is the MedTech service available?
 
 The MedTech service is available in these Azure regions: [Products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=health-data-services).
diff --git a/articles/healthcare-apis/iot/get-started.md b/articles/healthcare-apis/iot/get-started.md
@@ -12,6 +12,9 @@ ms.custom: mode-api
 
 # Get started with the MedTech service 
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 This article and diagram outlines the basic steps to get started with the MedTech service in the [Azure Health Data Services](../healthcare-apis-overview.md). These steps might help you to assess the [MedTech service deployment methods](deploy-choose-method.md) and determine which deployment method is best for you.
 
 As a prerequisite, you need an Azure subscription and granted the proper permissions to deploy Azure resource groups and resources. You can follow all the steps, or skip some if you have an existing environment. Also, you can combine all the steps and complete them in Azure PowerShell, Azure CLI, or REST API scripts.
diff --git a/articles/healthcare-apis/iot/git-projects.md b/articles/healthcare-apis/iot/git-projects.md
@@ -9,8 +9,12 @@ ms.topic: reference
 ms.date: 04/28/2023
 ms.author: chrupa
 ---
+
 # Open-source projects
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 Check out our open-source software (OSS) projects on GitHub, which provide source code and instructions to deploy services for various use cases with the MedTech service.
 
 > [!IMPORTANT]
diff --git a/articles/healthcare-apis/iot/how-to-enable-diagnostic-settings.md b/articles/healthcare-apis/iot/how-to-enable-diagnostic-settings.md
@@ -12,6 +12,9 @@ ms.author: chrupa
 
 # How to enable diagnostic settings for the MedTech service
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 In this article, learn how to enable diagnostic settings for the MedTech service to:
 
 * Create a diagnostic setting to export logs and metrics for audit, analysis, or troubleshooting of the MedTech service.
diff --git a/articles/healthcare-apis/iot/how-to-use-calculatedcontent-templates.md b/articles/healthcare-apis/iot/how-to-use-calculatedcontent-templates.md
@@ -8,9 +8,11 @@ ms.topic: how-to
 ms.date: 08/01/2023
 ms.author: chrupa
 ---
-
 # How to use CalculatedContent templates with the MedTech service device mapping
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 This article provides an overview of how to use CalculatedContent templates within a MedTech service device mapping.
 
 ## CalculatedContent template basics
diff --git a/articles/healthcare-apis/iot/how-to-use-custom-functions.md b/articles/healthcare-apis/iot/how-to-use-custom-functions.md
@@ -11,6 +11,9 @@ ms.author: chrupa
 
 # How to use custom functions with the MedTech service device mapping
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 Many functions are available when using **JMESPath** as the expression language. Besides the built-in functions available as part of the [JMESPath specification](https://jmespath.org/specification.html#built-in-functions), many more custom functions can also be used. This article describes how to use the MedTech service-specific custom functions with the MedTech service [device mapping](overview-of-device-mapping.md).
 
 You can use the MedTech service [Mapping debugger](how-to-use-mapping-debugger.md) for assistance creating, updating, and troubleshooting the MedTech service device and FHIR&reg; destination mappings. The Mapping debugger enables you to easily view and make inline adjustments in real-time, without ever having to leave the Azure portal. The Mapping debugger can also be used for uploading test device messages to see how they'll look after being processed into normalized messages and transformed into FHIR Observations.
diff --git a/articles/healthcare-apis/iot/how-to-use-iotjsonpathcontent-templates.md b/articles/healthcare-apis/iot/how-to-use-iotjsonpathcontent-templates.md
@@ -11,6 +11,9 @@ ms.author: chrupa
 
 # How to use IotJsonPathContent templates with the MedTech service device mapping
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 This article provides an overview of how to use IotJsonPathContent templates within a MedTech service device mapping.
 
 ## IotJsonPathContent template basics
diff --git a/articles/healthcare-apis/iot/how-to-use-mapping-debugger.md b/articles/healthcare-apis/iot/how-to-use-mapping-debugger.md
@@ -12,6 +12,9 @@ ms.author: chrupa
 
 # How to use the MedTech service Mapping debugger (Preview)
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 > [!IMPORTANT]
 > This capability is currently available for Public Preview and is subject to change. For more information, see [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/).
 
@@ -105,4 +108,4 @@ For this troubleshooting example, we're using a test device message that is [mes
 [Overview of the MedTech service scenario-based mappings samples](overview-of-samples.md)
 
 [!INCLUDE[FHIR trademark statement](../includes/healthcare-apis-fhir-trademark.md)]
- 
+ 
diff --git a/articles/healthcare-apis/iot/how-to-use-monitoring-and-health-checks-tabs.md b/articles/healthcare-apis/iot/how-to-use-monitoring-and-health-checks-tabs.md
@@ -12,6 +12,9 @@ ms.author: chrupa
 
 # How to use the MedTech service monitoring and health checks tabs
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 In this article, learn how to use the MedTech service monitoring and health check tabs in the Azure portal. The monitoring and health check tabs provide access to crucial MedTech service metrics and health checks. These metrics and health checks can be used in assessing the health and performance of your MedTech service and can be useful seeing patterns and/or trends or assisting with troubleshooting your MedTech service.
 
 ## Use the MedTech service monitoring tab
diff --git a/articles/healthcare-apis/iot/overview-of-device-data-processing-stages.md b/articles/healthcare-apis/iot/overview-of-device-data-processing-stages.md
@@ -12,6 +12,9 @@ ms.author: chrupa
 
 # Overview of the MedTech service device data processing stages 
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 This article provides an overview of the device data processing stages within the [MedTech service](overview.md). The MedTech service transforms device data into [FHIR&reg; Observations](https://www.hl7.org/fhir/observation.html) for persistence in the [FHIR service](../fhir/overview.md).
 
 The MedTech service device data processing follows these stages and in this order:
diff --git a/articles/healthcare-apis/iot/overview-of-device-mapping.md b/articles/healthcare-apis/iot/overview-of-device-mapping.md
@@ -11,6 +11,9 @@ ms.author: chrupa
 
 # Overview of the MedTech service device mapping
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 This article provides an overview of the MedTech service device mapping.
 
 The MedTech service requires two types of [JSON](https://www.json.org/) mappings that are added to your MedTech service through the Azure portal or Azure Resource Manager (ARM) API. The device mapping is the first type and controls mapping values in the device data sent to the MedTech service to an internal, normalized data object. The device mapping contains expressions that the MedTech service uses to extract types, device identifiers, measurement date time, and measurement value(s). The [FHIR&reg; destination mapping](overview-of-fhir-destination-mapping.md) is the second type and controls the mapping for [FHIR Observations](https://www.hl7.org/fhir/observation.html).
diff --git a/articles/healthcare-apis/iot/overview-of-fhir-destination-mapping.md b/articles/healthcare-apis/iot/overview-of-fhir-destination-mapping.md
@@ -11,6 +11,9 @@ ms.author: chrupa
 
 # Overview of the MedTech service FHIR destination mapping
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 This article provides an overview of the MedTech service FHIR&reg; destination mapping.
 
 The MedTech service requires two types of [JSON](https://www.json.org/) mappings that are added to your MedTech service through the Azure portal or Azure Resource Manager API. The [device mapping](overview-of-device-mapping.md) is the first type and controls mapping values in the device data sent to the MedTech service to an internal, normalized data object. The device mapping contains expressions that the MedTech service uses to extract types, device identifiers, measurement date time, and measurement value(s). The FHIR destination mapping is the second type and controls how the normalized data is mapped to [FHIR Observations](https://www.hl7.org/fhir/observation.html).
diff --git a/articles/healthcare-apis/iot/overview-of-samples.md b/articles/healthcare-apis/iot/overview-of-samples.md
@@ -12,6 +12,10 @@ ms.author: chrupa
 
 # Overview of the MedTech service scenario-based mappings samples
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
+
 The [MedTech service](overview.md) scenario-based [samples](https://github.com/Azure-Samples/azure-health-data-and-ai-samples/tree/main/samples/medtech-service-mappings) provide conforming and valid [device](overview-of-device-mapping.md) and [FHIR&reg; destination](overview-of-fhir-destination-mapping.md) mappings and test device messages. Theses samples can be used to help with the authoring and troubleshooting of your own MedTech service mappings.
 
 ## Sample resources
diff --git a/articles/healthcare-apis/iot/overview.md b/articles/healthcare-apis/iot/overview.md
@@ -12,6 +12,9 @@ ms.author: chrupa
 
 # What is the MedTech service?
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 The MedTech service is a Platform as a Service (PaaS) within the Azure Health Data Services. The MedTech service enables you to ingest device data, transform it into a unified FHIR&reg; format, and store it in an enterprise-scale, secure, and compliant cloud environment. 
 
 The MedTech service is built to help customers that are dealing with the challenge of gaining relevant insights from device data coming in from multiple and diverse sources. No matter the device or structure, the MedTech service normalizes that device data into a common format, allowing the end user to then easily capture trends, run analytics, and build Artificial Intelligence (AI) models. In the enterprise healthcare setting, the MedTech service is used in the context of remote patient monitoring, virtual health, and clinical trials.
diff --git a/articles/healthcare-apis/iot/troubleshoot-errors-deployment.md b/articles/healthcare-apis/iot/troubleshoot-errors-deployment.md
@@ -12,6 +12,9 @@ ms.author: chrupa
 
 # Troubleshoot MedTech service deployment errors
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 This article provides troubleshooting steps and fixes for MedTech service deployment errors.
 
 > [!TIP]
diff --git a/articles/healthcare-apis/iot/troubleshoot-errors-logs.md b/articles/healthcare-apis/iot/troubleshoot-errors-logs.md
@@ -12,6 +12,9 @@ ms.author: chrupa
 
 # Troubleshoot errors using the MedTech service logs
 
+> [!IMPORTANT]
+> As of 2/26/2025 the MedTech service will no longer be available in the following regions: UK West, UAE North, South Africa North, Qatar Central.
+
 This article provides troubleshooting steps and fixes for errors found in the MedTech service logs. 
 
 > [!TIP]
