Skip to content

Commit 94265c5

Browse files
committed
Adding videos to articles
1 parent 1837347 commit 94265c5

File tree

2 files changed

+7
-3
lines changed

2 files changed

+7
-3
lines changed

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

Lines changed: 3 additions & 1 deletion
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/04/2023
9+
ms.date: 04/06/2023
1010
ms.author: jasteppe
1111
---
1212

@@ -23,6 +23,8 @@ In this article, you'll learn how to use the MedTech service Mapping debugger. T
2323
> [!TIP]
2424
> 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).
2525
26+
> [!VIDEO https://youtu.be/OEGuCSGnECY]
27+
2628
## Overview of the Mapping debugger
2729

2830
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.

articles/healthcare-apis/iot/overview.md

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

@@ -19,6 +19,8 @@ This article provides an introductory overview of the MedTech service. The MedTe
1919

2020
The MedTech service is important because data can be difficult to access or lost when it comes from diverse or incompatible devices, systems, or formats. If this information isn't easy to access, it may have a negative effect on gaining key insights and capturing trends. The ability to transform many types of device data into a unified FHIR format enables the MedTech service to successfully link device data with other datasets to support the end user. As a result, this capability can facilitate the discovery of important clinical insights and trend capture. It can also help make connections to new device applications and enable advanced research projects.
2121

22+
> [!VIDEO https://youtu.be/_nMirYYU0pg]
23+
2224
## How the MedTech service works
2325

2426
The following diagram outlines the basic elements of how the MedTech service transforms device data into a standardized FHIR resource in the cloud.
@@ -107,7 +109,7 @@ The following Microsoft solutions can use MedTech service for extra functionalit
107109

108110
## Next steps
109111

110-
In this article, you learned about the MedTech service and its capabilities.
112+
In this article, you've learned about the MedTech service and its capabilities.
111113

112114
To learn about how the MedTech service processes device messages, see
113115

0 commit comments

Comments
 (0)