Merge pull request #222488 from msjasteppe/folder-renames

Renaming media folders.

Author: JamesJBarnett

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/15/2022
+ms.date: 12/27/2022
 ms.author: jasteppe
 ---
 
@@ -24,7 +24,7 @@ The four line colors show the different parts of the data journey.
 - **Red** = Hot path for data to inform clinicians of patient risk. The goal of the hot path is to be as close to real-time as possible.
 - **Orange** = Warm path for data. Still supporting clinicians in patient care. Data requests are typically triggered manually or on a refresh schedule.
 
-:::image type="content" source="media/iot-concepts/iot-connector-machine-learning.png" alt-text="Screenshot of the MedTech service and Machine Learning Service reference architecture." lightbox="media/iot-concepts/iot-connector-machine-learning.png":::
+:::image type="content" source="media/concepts-machine-learning/iot-connector-machine-learning.png" alt-text="Screenshot of the MedTech service and Machine Learning Service reference architecture." lightbox="media/concepts-machine-learning/iot-connector-machine-learning.png":::
 
 **Data ingest – Steps 1 through 5**
 

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/15/2021
+ms.date: 12/27/2021
 ms.author: jasteppe
 ---
 
@@ -19,19 +19,19 @@ The reference architecture below shows the basic components of using the Microso
 
 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).
 
-:::image type="content" source="media/iot-concepts/iot-connector-power-bi.png" alt-text="Screenshot of the MedTech service and Power BI." lightbox="media/iot-concepts/iot-connector-power-bi.png":::
+:::image type="content" source="media/concepts-power-bi/iot-connector-power-bi.png" alt-text="Screenshot of the MedTech service and Power BI." lightbox="media/concepts-power-bi/iot-connector-power-bi.png":::
 
 The MedTech service can ingest IoT data from most IoT devices or gateways whatever the location, data center, or cloud.
 
 We do encourage the use of Azure IoT services to assist with device/gateway connectivity.
 
-:::image type="content" source="media/iot-concepts/iot-connector-iot-hub-power-bi.png" alt-text="Screenshot of the MedTech service, IoT Hub, and Power BI." lightbox="media/iot-concepts/iot-connector-iot-hub-power-bi.png":::
+:::image type="content" source="media/concepts-power-bi/iot-connector-iot-hub-power-bi.png" alt-text="Screenshot of the MedTech service, IoT Hub, and Power BI." lightbox="media/concepts-power-bi/iot-connector-iot-hub-power-bi.png":::
 
 For some solutions, Azure IoT Central can be used in place of Azure IoT Hub.
 
 Azure IoT Edge can be used in with IoT Hub to create an on-premises endpoint for devices and/or in-device connectivity.
 
-:::image type="content" source="media/iot-concepts/iot-connector-iot-edge-power-bi.png" alt-text="Screenshot of the MedTech service, IoT Hub, IoT Edge, and Power BI." lightbox="media/iot-concepts/iot-connector-iot-edge-power-bi.png":::
+:::image type="content" source="media/concepts-power-bi/iot-connector-iot-edge-power-bi.png" alt-text="Screenshot of the MedTech service, IoT Hub, IoT Edge, and Power BI." lightbox="media/concepts-power-bi/iot-connector-iot-edge-power-bi.png":::
 
 ## Next steps
 

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/15/2022
+ms.date: 12/27/2022
 ms.author: jasteppe
 ---
 
@@ -21,19 +21,19 @@ Below is the MedTech service to Teams notifications conceptual architecture for
 
 You can even embed Power BI Dashboards inside the Microsoft Teams client. For more information on embedding Power BI in Microsoft Team visit [here](/power-bi/collaborate-share/service-embed-report-microsoft-teams).
 
-:::image type="content" source="media/iot-concepts/iot-connector-teams.png" alt-text="Screenshot of the MedTech service and Teams." lightbox="media/iot-concepts/iot-connector-teams.png":::
+:::image type="content" source="media/concepts-teams/iot-connector-teams.png" alt-text="Screenshot of the MedTech service and Teams." lightbox="media/concepts-teams/iot-connector-teams.png":::
 
 The MedTech service for can ingest IoT data from most IoT devices or gateways regardless of location, data center, or cloud.
 
 We do encourage the use of Azure IoT services to assist with device/gateway connectivity.
 
-:::image type="content" source="media/iot-concepts/iot-connector-iot-hub-teams.png" alt-text="Screenshot of the MedTech service and IoT Hub." lightbox="media/iot-concepts/iot-connector-iot-hub-teams.png":::
+:::image type="content" source="media/concepts-teams/iot-connector-iot-hub-teams.png" alt-text="Screenshot of the MedTech service and IoT Hub." lightbox="media/concepts-teams/iot-connector-iot-hub-teams.png":::
 
 For some solutions, Azure IoT Central can be used in place of Azure IoT Hub.
 
 Azure IoT Edge can be used in with IoT Hub to create an on-premises end point for devices and/or in-device connectivity.
 
-:::image type="content" source="media/iot-concepts/iot-connector-iot-edge-teams.png" alt-text="Screenshot of the MedTech service and IoT Edge." lightbox="media/iot-concepts/iot-connector-iot-edge-teams.png":::
+:::image type="content" source="media/concepts-teams/iot-connector-iot-edge-teams.png" alt-text="Screenshot of the MedTech service and IoT Edge." lightbox="media/concepts-teams/iot-connector-iot-edge-teams.png":::
 
 ## Next steps
 

articles/healthcare-apis/iot/data-flow.md

@@ -6,7 +6,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: iomt
 ms.topic: conceptual
-ms.date: 12/15/2022
+ms.date: 12/27/2022
 ms.author: jasteppe
 ---
 
@@ -16,11 +16,11 @@ This article provides an overview of the MedTech service data flow. You'll learn
 
 Data from health-related devices or medical devices flows through a path in which the MedTech service transforms data into FHIR, and then data is stored on and accessed from the FHIR service. The health data path follows these steps in this order: ingest, normalize, group, transform, and persist. Health data is retrieved from the device in the first step of ingestion. After the data is received, it's processed, or normalized per a user-selected/user-created schema template called the device mapping. Normalized health data is simpler to process and can be grouped. In the next step, health data is grouped into three Operate parameters. After the health data is normalized and grouped, it can be processed or transformed through a FHIR destination mapping, and then saved or persisted on the FHIR service.
 
-This article goes into more depth about each step in the data flow. The next steps are [Deploy the MedTech service using the Azure portal](deploy-iot-connector-in-azure.md) by using a device mapping (the normalization step) and a FHIR destination mapping (the transformation step).
+This article goes into more depth about each step in the data flow. The next steps are [Choose a deployment method for the MedTech service](deploy-new-choose.md) by using a device mapping (the normalization step) and a FHIR destination mapping (the transformation step).
 
 This next section of the article describes the stages that IoMT (Internet of Medical Things) device data goes through as it processed through the MedTech service.
 
-:::image type="content" source="media/iot-data-flow/iot-data-flow.png" alt-text="Screenshot of IoMT data as it flows from IoT devices into an Azure event hub. IoMT data is ingested by the MedTech service as it is normalized, grouped, transformed, and persisted in the FHIR service." lightbox="media/iot-data-flow/iot-data-flow.png":::
+:::image type="content" source="media/data-flow/iot-data-flow.png" alt-text="Screenshot of IoMT data as it flows from IoT devices into an Azure event hub. IoMT data is ingested by the MedTech service as it is normalized, grouped, transformed, and persisted in the FHIR service." lightbox="media/data-flow/iot-data-flow.png":::
 
 ## Ingest
 Ingest is the first stage where device data is received into the MedTech service. The ingestion endpoint for device data is hosted on an [Azure Event Hubs](../../event-hubs/index.yml). The Azure Event Hubs platform supports high scale and throughput with ability to receive and process millions of messages per second. It also enables the MedTech service to consume messages asynchronously, removing the need for devices to wait while device data gets processed.

articles/healthcare-apis/iot/deploy-new-button.md

@@ -63,23 +63,23 @@ To begin deployment in the Azure portal, select the **Deploy to Azure** button:
 
    - **Destination Mapping** - Don't change the default values for this quickstart.
 
-   :::image type="content" source="media\iot-deploy-quickstart-in-portal\iot-deploy-quickstart-options.png" alt-text="Screenshot of Azure portal page displaying deployment options for the Azure Health Data Service MedTech service." lightbox="media\iot-deploy-quickstart-in-portal\iot-deploy-quickstart-options.png":::
+   :::image type="content" source="media\deploy-new-button\iot-deploy-quickstart-options.png" alt-text="Screenshot of Azure portal page displaying deployment options for the Azure Health Data Service MedTech service." lightbox="media\deploy-new-button\iot-deploy-quickstart-options.png":::
 
 2. To validate your configuration, select **Review + create**.
 
-   :::image type="content" source="media\iot-deploy-quickstart-in-portal\iot-review-and-create-button.png" alt-text="Screenshot that shows the Review + create button selected in the Azure portal.":::
+   :::image type="content" source="media\deploy-new-button\iot-review-and-create-button.png" alt-text="Screenshot that shows the Review + create button selected in the Azure portal.":::
 
 3. In **Review + create**, check the template validation status. If validation is successful, the template displays **Validation Passed**. If validation fails, fix the detail that's indicated in the error message, and then select **Review + create** again.
 
-   :::image type="content" source="media\iot-deploy-quickstart-in-portal\iot-validation-completed.png" alt-text="Screenshot that shows the Review + create pane displaying the Validation Passed message.":::
+   :::image type="content" source="media\deploy-new-button\iot-validation-completed.png" alt-text="Screenshot that shows the Review + create pane displaying the Validation Passed message.":::
 
 4. After a successful validation, to begin the deployment, select **Create**.
 
-   :::image type="content" source="media\iot-deploy-quickstart-in-portal\iot-create-button.png" alt-text="Screenshot that shows the highlighted Create button.":::
+   :::image type="content" source="media\deploy-new-button\iot-create-button.png" alt-text="Screenshot that shows the highlighted Create button.":::
 
 5. In a few minutes, the Azure portal displays the message that your deployment is completed.
 
-   :::image type="content" source="media\iot-deploy-quickstart-in-portal\iot-deployment-complete-banner.png" alt-text="Screenshot that shows a green checkmark and the message Your deployment is complete.":::
+   :::image type="content" source="media\deploy-new-button\iot-deployment-complete-banner.png" alt-text="Screenshot that shows a green checkmark and the message Your deployment is complete.":::
 
    > [!IMPORTANT]
    > If you're going to allow access from multiple services to the device message event hub, it is highly recommended that each service has its own event hub consumer group.

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

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 12/15/2022
+ms.date: 12/27/2022
 ms.author: jasteppe
 ---
 
@@ -42,7 +42,7 @@ To learn more about using a manual deployment with the Azure portal, see [Deploy
 
 The following diagram outlines the basic steps of the MedTech service deployment and shows how these steps fit together with its data processing procedures. These basic steps may help you analyze the deployment options and determine which deployment method is best for you.
 
-:::image type="content" source="media/iot-get-started/get-started-with-iot.png" alt-text="Diagram showing MedTech service architecture overview." lightbox="media/iot-get-started/get-started-with-iot.png":::
+:::image type="content" source="media/get-started/get-started-with-iot.png" alt-text="Diagram showing MedTech service architecture overview." lightbox="media/get-started/get-started-with-iot.png":::
 
 > [!IMPORTANT]
 > If you're going to allow access from multiple services to the device message event hub, it is highly recommended that each service has its own event hub consumer group.

articles/healthcare-apis/iot/get-started.md

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 12/15/2022
+ms.date: 12/27/2022
 ms.author: jasteppe
 ms.custom: mode-api
 ---
@@ -18,7 +18,7 @@ This article will show you how to get started with the Azure MedTech service in
 
 The following diagram outlines the basic architectural path that enables the MedTech service to receive data from a medical device and send it to the FHIR service. This diagram shows how the six-step implementation process is divided into three key development stages: deployment, post-deployment, and data processing.
 
-:::image type="content" source="media/iot-get-started/get-started-with-iot.png" alt-text="Diagram showing MedTech service architectural overview." lightbox="media/iot-get-started/get-started-with-iot.png":::
+:::image type="content" source="media/get-started/get-started-with-iot.png" alt-text="Diagram showing MedTech service architectural overview." lightbox="media/get-started/get-started-with-iot.png":::
 
 ### Deployment
 

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/15/2022
+ms.date: 12/27/2022
 ms.author: jasteppe
 ---
 
@@ -40,7 +40,7 @@ The normalized data model has a few required properties that must be found and e
 
 Below is an example of what happens during normalization and transformation process within the MedTech service. For the purposes of the device mapping, we'll be focusing on the **Normalized data** process:
 
-:::image type="content" source="media/iot-data-transformation/iot-data-normalization-high-level.png" alt-text="Diagram of IoT data normalization flow example zoomed out." lightbox="media/iot-data-transformation/iot-data-normalization-high-level.png":::
+:::image type="content" source="media/how-to-configure-device-mappings/iot-data-normalization-high-level.png" alt-text="Diagram of IoT data normalization flow example zoomed out." lightbox="media/how-to-configure-device-mappings/iot-data-normalization-high-level.png":::
 
 The content payload itself is an Azure Event Hubs message, which is composed of three parts: Body, Properties, and SystemProperties. The `Body` is a byte array representing an UTF-8 encoded string. During template evaluation, the byte array is automatically converted into the string value. `Properties` is a key value collection for use by the message creator. `SystemProperties` is also a key value collection reserved by the Azure Event Hubs framework with entries automatically populated by it.
 

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/15/2022
+ms.date: 12/27/2022
 ms.author: jasteppe
 ---
 
@@ -15,7 +15,7 @@ This article describes how to configure the MedTech service using the Fast Healt
 
 Below is a conceptual example of what happens during the normalization and transformation process within the MedTech service:
 
-:::image type="content" source="media/iot-data-transformation/iot-data-normalization-high-level.png" alt-text="Diagram of IoT data normalization flow." lightbox="media/iot-data-transformation/iot-data-normalization-high-level.png":::
+:::image type="content" source="media/how-to-configure-fhir-destination-mappings/iot-data-normalization-high-level.png" alt-text="Diagram of IoT data normalization flow." lightbox="media/how-to-configure-fhir-destination-mappings/iot-data-normalization-high-level.png":::
 
 ## FHIR destination mappings