Skip to content

Commit 32788d3

Browse files
Merge pull request #228803 from msjasteppe/overview
Minor edits
2 parents 54b2537 + 9567cee commit 32788d3

File tree

4 files changed

+22
-10
lines changed

4 files changed

+22
-10
lines changed

articles/healthcare-apis/iot/how-to-configure-metrics.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,15 @@ author: msjasteppe
66
ms.service: healthcare-apis
77
ms.subservice: iomt
88
ms.topic: how-to
9-
ms.date: 02/09/2023
9+
ms.date: 02/27/2023
1010
ms.author: jasteppe
1111
---
1212

1313
# How to configure the MedTech service metrics
1414

15+
> [!NOTE]
16+
> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
17+
1518
In this article, you'll learn how to configure the MedTech service metrics in the Azure portal. You'll also learn how to pin the MedTech service metrics tile to an Azure portal dashboard for later viewing.
1619

1720
The MedTech service metrics can be used to help determine the health and performance of your MedTech service and can be useful with troubleshooting and seeing patterns and/or trends with your MedTech service.
@@ -26,7 +29,7 @@ Metric category|Metric name|Metric description|
2629
|Errors|Total Error Count|The total number of errors.|
2730
|Latency|Average Group Stage Latency|The average latency of the group stage. The [group stage](understand-service.md#group---optional) performs buffering, aggregating, and grouping on normalized messages.|
2831
|Latency|Average Normalize Stage Latency|The average latency of the normalized stage. The [normalized stage](understand-service.md#normalize) performs normalization on raw incoming messages.|
29-
|Traffic|Number of Fhir resources saved|The total number of Fast Healthcare Interoperability Resources (FHIR®) resources [updated or persisted](understand-service.md#persist) by the MedTech service.|
32+
|Traffic|Number of Fhir resources saved|The total number of FHIR resources [updated or persisted](understand-service.md#persist) by the MedTech service.|
3033
|Traffic|Number of Incoming Messages|The number of received raw [incoming messages](understand-service.md#ingest) (for example, the device events) from the configured source event hub.|
3134
|Traffic|Number of Measurements|The number of normalized value readings received by the FHIR [transformation stage](understand-service.md#transform) of the MedTech service.|
3235
|Traffic|Number of Message Groups|The number of groups that have messages aggregated in the designated time window.|

articles/healthcare-apis/iot/how-to-enable-diagnostic-settings.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,15 @@ author: msjasteppe
66
ms.service: healthcare-apis
77
ms.subservice: iomt
88
ms.topic: how-to
9-
ms.date: 1/26/2023
9+
ms.date: 02/27/2023
1010
ms.author: jasteppe
1111
---
1212

1313
# How to enable diagnostic settings for the MedTech service
1414

15+
> [!NOTE]
16+
> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
17+
1518
In this article, you'll learn how to enable diagnostic settings for the MedTech service to:
1619

1720
> [!div class="checklist"]
@@ -168,4 +171,4 @@ In this article, you learned how to enable the diagnostics settings for the MedT
168171
To learn about the MedTech service frequently asked questions (FAQs), see
169172

170173
> [!div class="nextstepaction"]
171-
> [Frequently asked questions about the MedTech service](frequently-asked-questions.md)
174+
> [Frequently asked questions about the MedTech service](frequently-asked-questions.md)

articles/healthcare-apis/iot/how-to-use-monitoring-tab.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,15 @@ author: msjasteppe
66
ms.service: healthcare-apis
77
ms.subservice: iomt
88
ms.topic: how-to
9-
ms.date: 02/09/2023
9+
ms.date: 02/27/2023
1010
ms.author: jasteppe
1111
---
1212

1313
# How to use the MedTech service monitoring tab
1414

15+
> [!NOTE]
16+
> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
17+
1518
In this article, you'll learn how to use the MedTech service monitoring tab in the Azure portal. The monitoring tab provides access to crucial MedTech service metrics. These metrics can be used in assessing the health and performance of your MedTech service and can be useful seeing patterns and/or trends or assisting with troubleshooting your MedTech service.
1619

1720
## Display the MedTech service monitoring tab metrics
@@ -54,7 +57,7 @@ Metric category|Metric name|Metric description|
5457
|Errors|**Total Error Count**|The total number of errors.|
5558
|Latency|**Average Group Stage Latency**|The average latency of the group stage. The [group stage](understand-service.md#group---optional) performs buffering, aggregating, and grouping on normalized messages.|
5659
|Latency|**Average Normalize Stage Latency**|The average latency of the normalized stage. The [normalized stage](understand-service.md#normalize) performs normalization on raw incoming messages.|
57-
|Traffic|Number of Fhir resources saved|The total number of Fast Healthcare Interoperability Resources (FHIR®) resources [updated or persisted](understand-service.md#persist) by the MedTech service.|
60+
|Traffic|Number of Fhir resources saved|The total number of FHIR resources [updated or persisted](understand-service.md#persist) by the MedTech service.|
5861
|Traffic|**Number of Incoming Messages**|The number of received raw [incoming messages](understand-service.md#ingest) (for example, the device events) from the configured source event hub.|
5962
|Traffic|**Number of Measurements**|The number of normalized value readings received by the FHIR [transformation stage](understand-service.md#transform) of the MedTech service.|
6063
|Traffic|**Number of Message Groups**|The number of groups that have messages aggregated in the designated time window.|

articles/healthcare-apis/iot/overview.md

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

1313
# What is the MedTech service?
1414

15-
This article provides an introductory overview of the MedTech service. The MedTech service in Azure Health Data Services is a Platform as a service (PaaS) that enables you to gather data from diverse devices and convert it into a Fast Healthcare Interoperability Resources (FHIR®) service format. The MedTech service's device data translation capabilities make it possible to transform a wide variety of data into a unified FHIR format that provides secure data management in a cloud environment.
15+
> [!NOTE]
16+
> [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
17+
18+
This article provides an introductory overview of the MedTech service. The MedTech service in Azure Health Data Services is a Platform as a service (PaaS) that enables you to gather data from diverse devices and convert it into a FHIR service format. The MedTech service's device data translation capabilities make it possible to transform a wide variety of data into a unified FHIR format that provides secure data management in a cloud environment.
1619

1720
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.
1821

@@ -34,7 +37,7 @@ After the PaaS deployment is completed, high-velocity and low-velocity data can
3437

3538
### Event Hubs service
3639

37-
IoT data is then sent from a device over the Internet to Event Hubs service to hold it temporarily in the cloud. The event hub can asynchronously process millions of data points per second, eliminating data traffic jams, making it possible to easily handle huge amounts of information in real time.
40+
IoT data is then sent from a device over the Internet to Event Hubs service to hold it temporarily in the cloud. The event hub can asynchronously process millions of data points per second, eliminating data traffic jams, making it possible to easily handle huge amounts of information in real-time.
3841

3942
### The MedTech service
4043

@@ -66,7 +69,7 @@ The MedTech service delivers your data to FHIR service in Azure Health Data Serv
6669

6770
### Configurable
6871

69-
The MedTech service can be customized and configured by using [device](how-to-configure-device-mappings.md) and [FHIR destination](how-to-configure-fhir-mappings.md) mappings to define the filtering and transformation of your data into FHIR observation resources.
72+
The MedTech service can be customized and configured by using [device](how-to-configure-device-mappings.md) and [FHIR destination](how-to-configure-fhir-mappings.md) mappings to define the filtering and transformation of your data into FHIR Observation resources.
7073

7174
Useful options could include:
7275

0 commit comments

Comments
 (0)