You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/healthcare-apis/iot/frequently-asked-questions.md
+7-3Lines changed: 7 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ author: msjasteppe
6
6
ms.custom: references_regions
7
7
ms.service: healthcare-apis
8
8
ms.topic: reference
9
-
ms.date: 03/28/2023
9
+
ms.date: 04/03/2023
10
10
ms.author: jasteppe
11
11
---
12
12
@@ -35,6 +35,10 @@ The MedTech service supports the [HL7 FHIR® R4](https://www.hl7.org/impleme
35
35
36
36
The MedTech service requires device and FHIR destination mappings to perform normalization and transformation processes on device message data. To learn how the MedTech service transforms device message data into [FHIR Observations](https://www.hl7.org/fhir/observation.html), see [Understand the MedTech service device message processing stages](understand-service.md).
37
37
38
+
### Is JsonPathContent still supported by the MedTech service device mapping?
39
+
40
+
Yes. JsonPathContent can be used as a template type within [CollectionContent](overview-of-device-mapping.md#collectioncontent). It's recommended that [CalculatedContent](how-to-use-calculatedcontent-mappings.md) is used as it supports all of the features of JsonPathContent with extra support for more advanced features.
41
+
38
42
### How long does it take for device message data to show up in the FHIR service?
39
43
40
44
The MedTech service buffers [FHIR Observations](https://www.hl7.org/fhir/observation.html) created during the transformation stage and provides near real-time processing. However, this buffer can potentially delay the persistence of FHIR Observations to the FHIR service up to ~five minutes. To learn how the MedTech service transforms device message data into FHIR Observations, see [Understand the MedTech service device message processing stages](understand-service.md).
@@ -90,11 +94,11 @@ For an overview of the MedTech service, see
90
94
To learn about the MedTech service device message data transformation, see
91
95
92
96
> [!div class="nextstepaction"]
93
-
> [Understand the MedTech service device message data transformation](overview.md)
97
+
> [Understand the MedTech service device message processing stages](overview.md)
94
98
95
99
To learn about methods for deploying the MedTech service, see
96
100
97
101
> [!div class="nextstepaction"]
98
102
> [Choose a deployment method for the MedTech service](deploy-new-choose.md)
99
103
100
-
FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
104
+
FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.
0 commit comments