You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/healthcare-apis/iot/how-to-create-mappings-copies.md
+25-12Lines changed: 25 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,38 +6,51 @@ author: msjasteppe
6
6
ms.service: healthcare-apis
7
7
ms.subservice: iomt
8
8
ms.topic: how-to
9
-
ms.date: 07/19/2022
9
+
ms.date: 07/20/2022
10
10
ms.author: jasteppe
11
11
---
12
12
13
-
# How to create copies of device and FHIR destination mappings
13
+
# How to create copies of the MedTech service device and FHIR destination mappings
14
14
15
15
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.
16
16
17
17
> [!TIP]
18
18
> 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.
19
19
20
20
> [!NOTE]
21
-
> 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.
21
+
> 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.
22
22
23
23
## Copy creation process
24
24
25
-
1. Select **"MedTech service"** on the left side of the Azure Health Data Services workspace.
25
+
1. Select **"MedTech service"** on the left side of your Azure Health Data Services workspace under **Services**.
26
26
27
-
:::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":::
27
+
:::image type="content" source="media/iot-mappings-copies/iot-mappings-copies-select-medtech-service-in-workspace.png" alt-text="Screenshot of select MedTech service." lightbox="media/iot-mappings-copies/iot-mappings-copies-select-medtech-service-in-workspace.png":::
28
28
29
-
2. Select the name of the **MedTech service** that you'll be copying the device and FHIR destination mappings from.
29
+
2. Select the name of the **MedTech service** that you'll be copying the device and FHIR destination mappings from. In this example, we'll be making copies from a MedTech service name **mt-azuredocsdemo**. You'll be selecting your MedTech service as part of this process.
30
30
31
-
:::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":::
31
+
:::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":::
32
32
33
-
> [!NOTE]
34
-
> This process may also be used for copying and saving the contents of the **"Destination"** FHIR destination mapping.
33
+
> [!TIP]
34
+
> This process can also be used for copying and saving the contents of the Destination (also know as the FHIR destination) mapping also under **Settings**.
35
+
>
36
+
> This example will be for copying and saving the device mapping for your MedTech service within Notepad
35
37
36
-
3. Select the contents of the JSON and do a copy operation (for example: Press **Ctrl + C**).
38
+
3. Select the **Device mapping** button under **Settings**.
37
39
38
-
:::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":::
40
+
:::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":::
39
41
40
-
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.
42
+
4. Select the contents of the JSON (for example: press **Ctrl + a**) and do a copy operation (for example: press **Ctrl + c**).
43
+
44
+
:::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":::
45
+
46
+
5. Do a paste operation (for example: Press **Ctrl + v**) into a new file within an editor application like Notepad or [Microsoft Visual Studio Code](https://code.visualstudio.com/) and do a save operation (for example: press **Ctrl + s**). For this example, we'll be using Notepad.
47
+
48
+
:::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":::
49
+
50
+
1. Select the folder to save the file in.
51
+
2. Name your file.
52
+
3. Leave the remaining fields at their defaults (for example: **Save as type** and **Encoding**)
0 commit comments