Skip to content

Commit 42579a3

Browse files
committed
Updating video URLs
1 parent 94265c5 commit 42579a3

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ 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]
26+
> [!VIDEO https://youtube.com/embed/OEGuCSGnECY]
2727
2828
## Overview of the Mapping debugger
2929

articles/healthcare-apis/iot/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ 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]
22+
> [!VIDEO https://youtube.com/embed/_nMirYYU0pg]
2323
2424
## How the MedTech service works
2525

0 commit comments

Comments
 (0)