Merge pull request #226933 from msjasteppe/calculated-updates

Updating file to reflect template type

Author: Stacyrch140

.openpublishing.redirection.healthcare-apis.json

@@ -634,7 +634,11 @@
         "redirect_document_id": false
     },
     {   "source_path_from_root": "/articles/healthcare-apis/iot/how-to-use-calculated-functions-mappings.md",
-        "redirect_url": "/azure/healthcare-apis/iot/how-to-use-calculatedcontenttemplate-mappings",
+        "redirect_url": "/azure/healthcare-apis/iot/how-to-use-calculatedcontent-mappings",
+        "redirect_document_id": false
+    },
+    {   "source_path_from_root": "/articles/healthcare-apis/iot/how-to-use-calculatedcontenttemplate-mappings.md",
+        "redirect_url": "/azure/healthcare-apis/iot/how-to-use-calculatedcontent-mappings",
         "redirect_document_id": false
     },
     {   "source_path_from_root": "/articles/healthcare-apis/iot/how-to-use-iot-jsonpath-content-mappings.md",

articles/healthcare-apis/iot/how-to-configure-device-mappings.md

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 1/12/2023
+ms.date: 02/09/2023
 ms.author: jasteppe
 ---
 
@@ -198,7 +198,7 @@ You can define one or more templates within the MedTech service device mapping.
 
 |Template Type|Description|
 |-------------|-----------|   
-|[CalculatedContentTemplate](how-to-use-calculatedcontenttemplate-mappings.md)|A template that supports writing expressions using one of several expression languages. Supports data transformation via the use of JMESPath functions.|
+|[CalculatedContent](how-to-use-calculatedcontent-mappings.md)|A template that supports writing expressions using one of several expression languages. Supports data transformation via the use of JMESPath functions.|
 |[IotJsonPathContentTemplate](how-to-use-iot-jsonpath-content-mappings.md)|A template that supports messages sent from Azure Iot Hub or the Legacy Export Data feature of Azure Iot Central.
 
 > [!TIP]

articles/healthcare-apis/iot/how-to-use-calculatedcontenttemplate-mappings.md renamed to articles/healthcare-apis/iot/how-to-use-calculatedcontent-mappings.md

@@ -1,21 +1,21 @@
 ---
-title: How to use CalculatedContentTemplate mappings with the MedTech service device mappings - Azure Health Data Services
-description: This article describes how to use CalculatedContentTemplate mappings with the MedTech service device mappings. 
+title: How to use CalculatedContentT mappings with the MedTech service device mappings - Azure Health Data Services
+description: This article describes how to use CalculatedContent mappings with the MedTech service device mappings. 
 author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 1/12/2023
+ms.date: 02/09/2023
 ms.author: jasteppe
 ---
 
-# How to use CalculatedContentTemplate mappings
+# How to use CalculatedContent mappings
 
-This article describes how to use CalculatedContentTemplate mappings with MedTech service device mapping template.
+This article describes how to use CalculatedContent mappings with MedTech service device mappings.
 
-## CalculatedContentTemplate
+## CalculatedContent mappings
 
-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. 
+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. 
 
 > [!NOTE]
 > 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:
 ```
 
 > [!TIP]
-> 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.
+> 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.
 
 ```json
 "templateType": "CalculatedContent",
@@ -55,7 +55,7 @@ In the example below, *typeMatchExpression* is defined as:
     }
 ```
 
-The default expression language to use for a MedTech service device template can be explicitly set using the `defaultExpressionLanguage` parameter:
+The default expression language to use for a MedTech service device mappings can be explicitly set using the `defaultExpressionLanguage` parameter:
 
 ```json
 "templateType": "CalculatedContent",
@@ -67,7 +67,7 @@ The default expression language to use for a MedTech service device template can
     }
 ```
 
-The CalculatedContentTemplate allows matching on and extracting values from an Azure Event Hubs message using **Expressions** as defined below:
+The CalculatedContent mappings allow matching on and extracting values from an Azure Event Hubs message using **Expressions** as defined below:
 
 |Property|Description|Example|
 |--------|-----------|-------|
@@ -92,13 +92,13 @@ When specifying the language to use for the expression, the below values are val
 | JMESPath            | **JmesPath** |
 
 >[!TIP]
-> 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.
+> For more information on JSONPath, see [JSONPath](https://goessner.net/articles/JsonPath/). CalculatedContent mappings use the [JSON .NET implementation](https://www.newtonsoft.com/json/help/html/QueryJsonSelectTokenJsonPath.htm) for resolving JSONPath expressions.
 >
-> 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.
+> For more information on JMESPath, see [JMESPath](https://jmespath.org/specification.html). CalculatedContent mappings use the [JMESPath .NET implementation](https://github.com/jdevillard/JmesPath.Net) for resolving JMESPath expressions.
 
 ### Custom functions
 
-A set of MedTech service custom functions is also available. The MedTech service custom functions are outside of the functions provided as part of the JMESPath specification. For more information on the MedTech service custom functions, see [How to use MedTech service custom functions](how-to-use-custom-functions.md).
+A set of MedTech service custom functions are also available. The MedTech service custom functions are outside of the functions provided as part of the JMESPath specification. For more information on the MedTech service custom functions, see [How to use MedTech service custom functions](how-to-use-custom-functions.md).
 
 ### Matched Token
 
@@ -542,7 +542,7 @@ In the below example, height data arrives in either inches or meters. We want al
 
 ## Next steps
 
-In this article, you learned how to configure the MedTech service device mappings using CalculatedContentTemplate mappings. 
+In this article, you learned how to configure the MedTech service device mappings using CalculatedContent mappings. 
 
 To learn how to configure FHIR destination mappings, see
 

articles/healthcare-apis/iot/toc.yml

@@ -46,8 +46,8 @@ items:
       items:
       - name: Device mappings
         href: how-to-configure-device-mappings.md
-      - name: CalculatedContentTemplate mappings
-        href: how-to-use-calculatedcontenttemplate-mappings.md
+      - name: CalculatedContent mappings
+        href: how-to-use-calculatedcontent-mappings.md
       - name: IotJsonPathContentTemplate mappings
         href: how-to-use-iotjsonpathcontenttemplate-mappings.md
       - name: Custom functions

articles/healthcare-apis/release-notes.md

@@ -537,7 +537,7 @@ Enabled DICOM service to work with workspaces that have names beginning with a l
 
 **MedTech service normalized improvements with calculations to support and enhance health data standardization.** 
 
-See [Use Device mappings](./../healthcare-apis/iot/how-to-use-device-mappings.md) and [Calculated Content Templates](./../healthcare-apis/iot/how-to-use-calculatedcontenttemplate-mappings.md)  
+See [Use device mappings](./../healthcare-apis/iot/how-to-use-device-mappings.md) and [CalculatedContent](./../healthcare-apis/iot/how-to-use-calculatedcontent-mappings.md)