Skip to content

Commit 4c4063d

Browse files
committed
More edits
1 parent 2648941 commit 4c4063d

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

articles/healthcare-apis/iot/how-to-use-mapping-debugger.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,9 @@ ms.author: jasteppe
1717
1818
In this article, you'll learn how to use the MedTech service Mapping debugger in the Azure portal. The Mapping debugger is a tool used for creating, updating, and troubleshooting the MedTech service device and FHIR destination mappings. 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 for persistence in the FHIR service. This new self-service tool allows you to easily view and make inline adjustments in real-time, without ever having to leave the Azure portal.
1919

20+
> [!TIP]
21+
> To learn about how the MedTech service transforms and persists device message data into the FHIR service see, [Understand the device message data transformation](understand-service.md).
22+
2023
## Overview of the Mapping debugger
2124

2225
1. To access the MedTech service's Mapping debugger, select **Mapping debugger** within your MedTech service on the Azure portal. For this article, we'll be using a MedTech service named **mt-azuredocsdemo**. You'll select your own MedTech service. From this screen, we can see the Mapping debugger is presenting the device and FHIR destination mappings associated with this MedTech service and has provided a **Validation** of those mappings.
@@ -84,7 +87,7 @@ In this article, you'll learn how to use the MedTech service Mapping debugger in
8487

8588
## Next steps
8689

87-
In this article, you learned about how to use the Mapping debugger to edit/troubleshoot the MedTech service device and FHIR destination mappings, and view normalized message and FHIR Observation from a test device message.
90+
In this article, you learned about how to use the Mapping debugger to edit/troubleshoot the MedTech service device and FHIR destination mappings and view normalized message and FHIR Observation from a test device message.
8891

8992
To learn how to troubleshoot MedTech service deployment errors, see
9093

0 commit comments

Comments
 (0)