Skip to content

Commit 4097892

Browse files
committed
More edits.
1 parent bae32b3 commit 4097892

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: msjasteppe
66
ms.service: healthcare-apis
77
ms.subservice: iomt
88
ms.topic: how-to
9-
ms.date: 04/06/2023
9+
ms.date: 04/10/2023
1010
ms.author: jasteppe
1111
---
1212

@@ -21,10 +21,10 @@ ms.author: jasteppe
2121
In this article, learn how to use the MedTech service Mapping debugger. The Mapping debugger is a self-service tool that is used for creating, updating, and troubleshooting the MedTech service device and FHIR 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.
2222

2323
> [!TIP]
24-
> To learn about how the MedTech service transforms and persists device message data into the FHIR service see, [Overview of the MedTech service device message processing stages](overview-of-device-message-processing-stages.md).
24+
> To learn about how the MedTech service transforms and persists device message data into the FHIR service see, [Overview of the MedTech service device data processing stages](overview-of-device-message-processing-stages.md).
2525
2626
The following video presents an overview of the Mapping debugger:
27-
27+
>
2828
> [!VIDEO https://youtube.com/embed/OEGuCSGnECY]
2929
3030
## Overview of the Mapping debugger
@@ -62,7 +62,7 @@ The following video presents an overview of the Mapping debugger:
6262
:::image type="content" source="media\how-to-use-mapping-debugger\mapping-debugger-save-mappings.png" alt-text="Screenshot of the Mapping debugger and the Save button." lightbox="media\how-to-use-mapping-debugger\mapping-debugger-save-mappings.png":::
6363

6464
> [!NOTE]
65-
> The MedTech service only saves the mappings that have been changed/updated. For example: If you only made a change to the **device mapping**, only those changes are saved to your MedTech service and no changes would be saved to the FHIR destination mapping. This is by design and to help with performance of the MedTech service.
65+
> The MedTech service only saves the mappings that have been changed/updated. For example: If you only made a change to the **device mapping**, only those changes are saved to your MedTech service and no changes would be saved to the **FHIR destination mapping**. This is by design and to help with performance of the MedTech service.
6666
6767
4. Once the device and FHIR destination mappings are successfully saved, a confirmation from **Notifications** is created within the Azure portal.
6868

articles/healthcare-apis/iot/overview.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -81,13 +81,13 @@ The MedTech service can be customized and configured by using [device](how-to-co
8181

8282
Useful options could include:
8383

84-
- Linking devices and consumers together for enhanced insights, trend captures, interoperability between systems, and proactive and remote monitoring.
84+
- Link devices and consumers together for enhanced insights, trend captures, interoperability between systems, and proactive and remote monitoring.
8585

86-
- FHIR Observations that can be created or updated according to existing or new mappings.
86+
- Update or create FHIR Observations according to existing or new mapping template types.
8787

88-
- Being able to choose data terms that work best for your organization and provide consistency in device data ingestion.
88+
- Choose data terms that work best for your organization and provide consistency in device data ingestion.
8989

90-
- Facilitating customization, editing, testing, and troubleshooting MedTech service device and FHIR destination mappings with the [Mapping debugger](how-to-use-mapping-debugger.md) tool.
90+
- Customize, edit, test, and troubleshoot MedTech service device and FHIR destination mappings with the [Mapping debugger](how-to-use-mapping-debugger.md) tool.
9191

9292
### Scalable
9393

0 commit comments

Comments
 (0)