Merge pull request #205413 from msjasteppe/iot-create-copies

Major update to document including screenshots.

Author: v-regandowner

articles/healthcare-apis/iot/how-to-create-mappings-copies.md

@@ -6,42 +6,53 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: iomt
 ms.topic: how-to
-ms.date: 07/19/2022
+ms.date: 07/21/2022
 ms.author: jasteppe
 ---
 
-# How to create copies of device and FHIR destination mappings
+# How to create copies of the MedTech service device and FHIR destination mappings
 
 This article provides steps for creating copies of your MedTech service's device and Fast Healthcare Interoperability Resources (FHIR®) destination mappings that can be used outside of Azure. These copies can be used for editing, troubleshooting, and archiving.
 
 > [!TIP]
 > Check out the [IoMT Connector Data Mapper](https://github.com/microsoft/iomt-fhir/tree/master/tools/data-mapper) tool for editing, testing, and troubleshooting MedTech service device and FHIR destination mappings. Export mappings for uploading to the MedTech service in the Azure portal or use with the [open-source version](https://github.com/microsoft/iomt-fhir) of the MedTech service.
 
 > [!NOTE]
-> When opening 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 to assist in the troubleshooting process.
+> When opening an [Azure Technical Support](https://azure.microsoft.com/support/create-ticket/) ticket for your MedTech service, include copies of your device and FHIR destination mappings to assist in the troubleshooting process.
 
-## Copy creation process
+## Device mapping copy creation process
 
-1. Select **"MedTech service"** on the left side of the Azure Health Data Services workspace.
+1. Select **"MedTech service"** on the left side of your Azure Health Data Services workspace under **Services**.
 
-   :::image type="content" source="media/iot-troubleshoot/iot-connector-blade.png" alt-text="Screenshot of select MedTech service." lightbox="media/iot-troubleshoot/iot-connector-blade.png":::
+   :::image type="content" source="media/iot-mappings-copies/iot-mappings-copies-select-medtech-service-button-in-workspace.png" alt-text="Screenshot of select MedTech service within the workspace." lightbox="media/iot-mappings-copies/iot-mappings-copies-select-medtech-service-button-in-workspace.png":::
 
-2. Select the name of the **MedTech service** that you'll be copying the device and FHIR destination mappings from.
+2. Select the name of the **MedTech service** that you'll be copying the device mapping from. In this example, we'll be making a copy of the device mapping from a MedTech service named **mt-azuredocsdemo**. You'll be selecting your own MedTech service as part of this process.
 
-   :::image type="content" source="media/iot-troubleshoot/map-files-select-connector-with-box.png" alt-text="Screenshoot of select the MedTech service that you will be making mappings copies from." lightbox="media/iot-troubleshoot/map-files-select-connector-with-box.png":::
+   :::image type="content" source="media/iot-mappings-copies/iot-mappings-copies-select-medtech-service.png" alt-text="Screenshot of select the MedTech service that you'll be making mappings copies from." lightbox="media/iot-mappings-copies/iot-mappings-copies-select-medtech-service.png":::  
 
-   > [!NOTE]
-   > This process may also be used for copying and saving the contents of the **"Destination"** FHIR destination mapping.
+3. Select the **Device mapping** button under **Settings**.
 
-3. Select the contents of the JSON and do a copy operation (for example: Press **Ctrl + C**). 
+   :::image type="content" source="media/iot-mappings-copies/iot-mappings-copies-select-device-mapping.png" alt-text="Screenshot of select Device mapping button." lightbox="media/iot-mappings-copies/iot-mappings-copies-select-device-mapping.png":::
 
-   :::image type="content" source="media/iot-troubleshoot/map-files-select-device-json-with-box.png" alt-text="Screenshot of select and copy contents of the mapping." lightbox="media/iot-troubleshoot/map-files-select-device-json-with-box.png":::
+   > [!TIP]
+   > This process can also be used for copying and saving the contents of the **Destination** (also know as the FHIR destination) mapping which is also under **Settings** within your workspace.
 
-4. Do a paste operation (for example: Press **Ctrl + V**) into a new file within an editor like Microsoft Visual Studio Code or Notepad. Make sure to save the file with the **.json** extension.
+4. Select the contents of the device mapping (for example: press **Ctrl + a**) and do a copy operation (for example: press **Ctrl + c**). 
+
+   :::image type="content" source="media/iot-mappings-copies/iot-mappings-copies-select-device-mapping-contents.png" alt-text="Screenshot of select and copy contents of the mapping." lightbox="media/iot-mappings-copies/iot-mappings-copies-select-device-mapping-contents.png":::
+
+5. Open an editor application like Notepad or [Microsoft Visual Studio Code](https://code.visualstudio.com/) and do a paste operation (for example: press **Ctrl + v**) and a save operation (for example: press **Ctrl + s**) to create a file copy of your MedTech service device mapping. For this example, we'll be using Notepad. 
+
+   :::image type="content" source="media/iot-mappings-copies/iot-mappings-copies-save-in-notepad.png" alt-text="Screenshot of using Notepad with the device mapping copy." lightbox="media/iot-mappings-copies/iot-mappings-copies-save-in-notepad.png":::
+
+   1. Select a folder to save the file in.
+   2. Select a name for your file.
+   3. Leave the remaining fields at their defaults (for example: **Save as type** and **Encoding**). 
+   4. Select the **Save** button.
 
 ## Next steps
 
-In this article, you learned how to make copies of the MedTech service device and FHIR destination mappings. To learn how to troubleshoot device and FHIR destination mappings, see
+In this article, you learned how to make copies of your MedTech service device and FHIR destination mappings. To learn how to troubleshoot device and FHIR destination mappings, see
 
 >[!div class="nextstepaction"]
 >[Troubleshoot the MedTech service device and FHIR destination mappings](iot-troubleshoot-mappings.md)