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/how-to-use-calculatedcontent-mappings.md
+13-13Lines changed: 13 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,21 +1,21 @@
1
1
---
2
-
title: How to use CalculatedContentTemplate mappings with the MedTech service device mappings - Azure Health Data Services
3
-
description: This article describes how to use CalculatedContentTemplate mappings with the MedTech service device mappings.
2
+
title: How to use CalculatedContentT mappings with the MedTech service device mappings - Azure Health Data Services
3
+
description: This article describes how to use CalculatedContent mappings with the MedTech service device mappings.
4
4
author: msjasteppe
5
5
ms.service: healthcare-apis
6
6
ms.subservice: fhir
7
7
ms.topic: how-to
8
-
ms.date: 1/12/2023
8
+
ms.date: 02/09/2023
9
9
ms.author: jasteppe
10
10
---
11
11
12
-
# How to use CalculatedContentTemplate mappings
12
+
# How to use CalculatedContent mappings
13
13
14
-
This article describes how to use CalculatedContentTemplate mappings with MedTech service device mapping template.
14
+
This article describes how to use CalculatedContent mappings with MedTech service device mappings.
15
15
16
-
## CalculatedContentTemplate
16
+
## CalculatedContent
17
17
18
-
MedTech service provides an expression-based content template to both match the wanted template and extract values. **Expressions** may be used by either JSONPath or JMESPath. Each expression within the template may choose its own expression language.
18
+
The MedTech service provides an expression-based content template to both match the wanted template and extract values. **Expressions** may be used by either JSONPath or JMESPath. Each expression within the template may choose its own expression language.
19
19
20
20
> [!NOTE]
21
21
> If an expression language isn't defined, the default expression language configured for the template will be used. The default is JSONPath but can be overwritten if needed.
@@ -44,7 +44,7 @@ In the example below, *typeMatchExpression* is defined as:
44
44
```
45
45
46
46
> [!TIP]
47
-
> The default expression language to use for a MedTech service device mapping template is JsonPath. If you want to use JsonPath, the expression alone may be supplied.
47
+
> The default expression language to use for a MedTech service device mappings is JsonPath. If you want to use JsonPath, the expression alone may be supplied.
48
48
49
49
```json
50
50
"templateType": "CalculatedContent",
@@ -55,7 +55,7 @@ In the example below, *typeMatchExpression* is defined as:
55
55
}
56
56
```
57
57
58
-
The default expression language to use for a MedTech service device template can be explicitly set using the `defaultExpressionLanguage` parameter:
58
+
The default expression language to use for a MedTech service device mappings can be explicitly set using the `defaultExpressionLanguage` parameter:
59
59
60
60
```json
61
61
"templateType": "CalculatedContent",
@@ -92,9 +92,9 @@ When specifying the language to use for the expression, the below values are val
92
92
| JMESPath |**JmesPath**|
93
93
94
94
>[!TIP]
95
-
> For more information on JSONPath, see [JSONPath](https://goessner.net/articles/JsonPath/). The [CalculatedContentTemplate](#calculatedcontenttemplate) uses the [JSON .NET implementation](https://www.newtonsoft.com/json/help/html/QueryJsonSelectTokenJsonPath.htm) for resolving JSONPath expressions.
95
+
> For more information on JSONPath, see [JSONPath](https://goessner.net/articles/JsonPath/). [CalculatedContent](#calculatedcontent) uses the [JSON .NET implementation](https://www.newtonsoft.com/json/help/html/QueryJsonSelectTokenJsonPath.htm) for resolving JSONPath expressions.
96
96
>
97
-
> For more information on JMESPath, see [JMESPath](https://jmespath.org/specification.html). The [CalculatedContentTemplate](#calculatedcontenttemplate) uses the [JMESPath .NET implementation](https://github.com/jdevillard/JmesPath.Net) for resolving JMESPath expressions.
97
+
> For more information on JMESPath, see [JMESPath](https://jmespath.org/specification.html). [CalculatedContent](#calculatedcontent) uses the [JMESPath .NET implementation](https://github.com/jdevillard/JmesPath.Net) for resolving JMESPath expressions.
98
98
99
99
### Custom functions
100
100
@@ -542,11 +542,11 @@ In the below example, height data arrives in either inches or meters. We want al
542
542
543
543
## Next steps
544
544
545
-
In this article, you learned how to configure the MedTech service device mappings using CalculatedContentTemplate mappings.
545
+
In this article, you learned how to configure the MedTech service device mappings using CalculatedContent mappings.
546
546
547
547
To learn how to configure FHIR destination mappings, see
548
548
549
549
> [!div class="nextstepaction"]
550
-
> [How to configure FHIR destination mappings](how-to-configure-fhir-mappings.md)
550
+
> [How to configure the FHIR destination mappings](how-to-configure-fhir-mappings.md)
551
551
552
552
(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