Skip to content

Commit 6830f49

Browse files
committed
Updated based on feedback
1 parent 3a0b048 commit 6830f49

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

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

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ author: msjasteppe
66
ms.custom: references_regions
77
ms.service: healthcare-apis
88
ms.topic: reference
9-
ms.date: 03/28/2023
9+
ms.date: 04/03/2023
1010
ms.author: jasteppe
1111
---
1212

@@ -35,9 +35,9 @@ The MedTech service supports the [HL7 FHIR® R4](https://www.hl7.org/impleme
3535

3636
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).
3737

38-
### Is JSONPATHContent still supported by the MedTech service device mapping?
38+
### Is JsonPathContent still supported by the MedTech service device mapping?
3939

40-
Yes. JSONPathContent can be used as a template type within [CollectionContent](overview-of-device-mapping.md#collectioncontent). It's recommended that CalculatedContent is used as it supports all of the features of JSONPathContent with extra support for more advanced features.
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.
4141

4242
### How long does it take for device message data to show up in the FHIR service?
4343

@@ -94,11 +94,11 @@ For an overview of the MedTech service, see
9494
To learn about the MedTech service device message data transformation, see
9595

9696
> [!div class="nextstepaction"]
97-
> [Understand the MedTech service device message data transformation](overview.md)
97+
> [Understand the MedTech service device message processing stages](overview.md)
9898
9999
To learn about methods for deploying the MedTech service, see
100100

101101
> [!div class="nextstepaction"]
102102
> [Choose a deployment method for the MedTech service](deploy-new-choose.md)
103103
104-
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

Comments
 (0)