Skip to content

Commit 760efe8

Browse files
committed
Additional updates and edits
1 parent 33e53d4 commit 760efe8

File tree

2 files changed

+12
-4
lines changed

2 files changed

+12
-4
lines changed

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

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,13 +22,21 @@ The MedTech service is available in these Azure regions: [Products available by
2222

2323
### Can I use the MedTech service with a different FHIR service other than the Azure Health Data Services FHIR service?
2424

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.
25+
No. The 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.
2626

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

2929
### What versions of FHIR does the MedTech service support?
3030

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).
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).
32+
33+
### How long does it take for device message data to show up on the FHIR service?
34+
35+
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).
36+
37+
### Why do I have to provide device and FHIR destination mappings to my MedTech service?
38+
39+
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).
3240

3341
### Does the MedTech service perform backups of device messages?
3442

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)