Skip to content

Commit 23da03c

Browse files
v-stsavellv-stsavell
authored
Merge pull request #225229 from msjasteppe/faq-updates
Additional updates and edits
2 parents e0dff39 + 509ef80 commit 23da03c

File tree

2 files changed

+25
-22
lines changed

2 files changed

+25
-22
lines changed

‎articles/healthcare-apis/iot/frequently-asked-questions.md

Lines changed: 23 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -6,62 +6,65 @@ author: msjasteppe
66
ms.custom: references_regions
77
ms.service: healthcare-apis
88
ms.topic: reference
9-
ms.date: 1/5/2023
9+
ms.date: 1/26/2023
1010
ms.author: jasteppe
1111
---
1212

1313
# Frequently asked questions about the MedTech service
1414

15-
Here are some of the frequently asked questions (FAQs) about the MedTech service.
15+
This article provides answers to frequently asked questions (FAQs) about the MedTech service.
1616

17-
## The MedTech service: The basics
18-
19-
### Where is the MedTech service available?
17+
## Where is the MedTech service available?
2018

2119
The MedTech service is available in these Azure regions: [Products available by region](https://azure.microsoft.com/global-infrastructure/services/?products=health-data-services).
2220

23-
### Can I use the MedTech service with a different FHIR service other than the Azure Health Data Services FHIR service?
21+
## Can I use the MedTech service with a different FHIR service other than the Azure Health Data Services FHIR service?
2422

25-
No. The Azure Health Data Services MedTech service currently only supports the Azure Health Data Services Fast Healthcare Interoperability Resources (FHIR®) service for the persistence of data. The open-source version of the MedTech service supports the use of different FHIR services.
23+
No. The MedTech service currently only supports the Azure Health Data Services Fast Healthcare Interoperability Resources (FHIR®) service for the persistence of transformed device message data. The open-source version of the MedTech service supports the use of different FHIR services.
2624

2725
To learn more about the MedTech service open-source projects, see [Open-source projects](git-projects.md).
2826

29-
### What versions of FHIR does the MedTech service support?
27+
## What versions of FHIR does the MedTech service support?
28+
29+
The MedTech service currently only supports the persistence of [HL7 FHIR® R4](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=491).
30+
31+
## How long does it take for device message data to show up on the FHIR service?
3032

31-
The MedTech service currently only supports the persistence of [HL7 FHIR® R4](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=491).
33+
The MedTech service buffers the FHIR Observations resources created during the transformation stage and provides near real-time processing. However, it can potentially take up to five minutes for FHIR Observation resources to be persisted in the FHIR service. To learn how the MedTech service transforms device message data into FHIR Observations resources, see [Understand the MedTech service device message data transformation](understand-service.md).
3234

33-
### Does the MedTech service perform backups of device messages?
35+
## Why do I have to provide device and FHIR destination mappings to the MedTech service?
36+
37+
The MedTech service requires the device and FHIR destination mappings to perform normalization and transformation processes on the device message data. To learn how the MedTech service transforms device message data into FHIR Observations resources, see [Understand the MedTech service device message data transformation](understand-service.md).
38+
39+
## Does the MedTech service perform backups of device messages?
3440

3541
No. The MedTech service doesn't back up the device messages that come into the customer's event hub. The customer controls the device message retention period within their event hub, which can be from 1-7 days. If the device message data is successfully processed by the MedTech service, it's persisted in the FHIR service, and the FHIR service backup policy applies.
3642

3743
To learn more about event hub message retention, see [What is the maximum retention period for events?](/azure/event-hubs/event-hubs-faq#what-is-the-maximum-retention-period-for-events-)
3844

39-
### What are the subscription quota limits for the MedTech service?
45+
## What are the subscription quota limits for the MedTech service?
4046

4147
* 25 MedTech services per Subscription (not adjustable)
4248
* 10 MedTech services per workspace (not adjustable)
4349
* One FHIR destination* per MedTech service (not adjustable)
4450

4551
(* - FHIR Destination is a child resource of the MedTech service)
4652

47-
### Can I use the MedTech service with device messages from Apple®, Google®, or Fitbit® devices?
53+
## Can I use the MedTech service with device messages from Apple®, Google®, or Fitbit® devices?
4854

4955
Yes. The MedTech service supports device messages from all these vendors through the open-source version of the MedTech service.
5056

5157
To learn more about the MedTech service open-source projects, see [Open-source projects](git-projects.md).
5258

53-
## More frequently asked questions
54-
55-
[FAQs about the Azure Health Data Services](../healthcare-apis-faqs.md)
56-
57-
[FAQs about Azure Health Data Services FHIR service](../fhir/fhir-faq.md)
58-
59-
[FAQs about Azure Health Data Services DICOM service](../dicom/dicom-services-faqs.yml)
60-
6159
## Next steps
6260

6361
In this article, you learned about the MedTech service frequently asked questions (FAQs)
6462

63+
To learn about the MedTech service, see
64+
65+
> [!div class="nextstepaction"]
66+
> [What is the MedTech service?](overview.md)
67+
6568
To learn about methods for deploying the MedTech service, see
6669

6770
> [!div class="nextstepaction"]

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

Lines changed: 2 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: iomt
88
ms.topic: how-to
9-
ms.date: 1/25/2023
9+
ms.date: 1/26/2023
1010
ms.author: jasteppe
1111
---
1212

@@ -99,7 +99,7 @@ If you choose to include your Log Analytics workspace as a destination option fo
9999

100100
:::image type="content" source="media/how-to-enable-diagnostic-settings/select-logs-button.png" alt-text="Screenshot of logs option." lightbox="media/how-to-enable-diagnostic-settings/select-logs-button.png":::
101101

102-
2. Copy the below table query string into your Log Analytics workspace query area and select **Run**. Using the *AHDSMedTechDiagnosticLogs* table will provide you with all logs contained in the entire table for the selected **Time range** setting (the default value is **Last 24 hours**). The MedTech service provides five pre-defined queries that will be addressed in the article section titled [Accessing the MedTech service pre-defined Azure Log Analytics queries](how-to-enable-diagnostic-settings.md#accessing-the-medtech-service-pre-defined-azure-log-analytics-queries).
102+
2. Copy the below table query string into your Log Analytics workspace query area and select **Run**. Using the *AHDSMedTechDiagnosticLogs* table will provide you with all logs contained in the entire table for the selected **Time range** setting (the default value is **Last 24 hours**). The MedTech service provides five pre-defined queries that will be addressed in the article section titled [Accessing the MedTech service pre-defined Azure Log Analytics queries](#accessing-the-medtech-service-pre-defined-azure-log-analytics-queries).
103103

104104
```Kusto
105105
AHDSMedTechDiagnosticLogs

0 commit comments

Comments
 (0)