Minor updates to docset

Author: msjasteppe

articles/healthcare-apis/iot/deploy-new-arm.md

@@ -6,7 +6,7 @@ ms.service: healthcare-apis
 ms.subservice: fhir
 ms.custom: devx-track-arm-template
 ms.topic: quickstart
-ms.date: 03/10/2023
+ms.date: 04/14/2023
 ms.author: jasteppe
 ---
 
@@ -124,9 +124,9 @@ When deployment is completed, the following resources and access roles are creat
 
 After you've successfully deployed an instance of the MedTech service, you'll still need to provide conforming and valid device and FHIR destination mappings.
 
- - To learn about the device mapping, see [How to configure the device mapping](how-to-configure-device-mappings.md).
+ - To learn about the device mapping, see [Overview of the MedTech service device mapping](overview-of-device-mapping.md).
 
- - To learn about the FHIR destination mapping, see [How to configure the FHIR destination mapping](how-to-configure-fhir-mappings.md).
+ - To learn about the FHIR destination mapping, see [Overview of the MedTech service FHIR destination mapping](overview-of-fhir-destination-mapping.md).
 
 ## Next steps
 

articles/healthcare-apis/iot/deploy-new-bicep-powershell-cli.md

@@ -6,7 +6,7 @@ ms.service: healthcare-apis
 ms.subservice: fhir
 ms.custom: devx-track-bicep, devx-track-azurepowershell, devx-track-azurecli
 ms.topic: quickstart
-ms.date: 03/10/2023
+ms.date: 04/14/2023
 ms.author: jasteppe
 ---
 
@@ -190,9 +190,9 @@ When deployment is completed, the following resources and access roles are creat
 
 After you've successfully deployed an instance of the MedTech service, you'll still need to provide conforming and valid device and FHIR destination mappings.
 
-- To learn about the device mapping, see [How to configure the device mapping](how-to-configure-device-mappings.md).
+- To learn about the device mapping, see [Overview of the device mapping](overview-of-device-mapping.md).
 
-- To learn about the FHIR destination mapping, see [How to configure the FHIR destination mapping](how-to-configure-fhir-mappings.md).
+- To learn about the FHIR destination mapping, see [Overview of the FHIR destination mapping](overview-of-fhir-destination-mapping.md).
 
 ## Clean up Azure PowerShell deployed resources
 

articles/healthcare-apis/iot/deploy-new-config.md

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 03/10/2023
+ms.date: 04/14/2023
 ms.author: jasteppe
 ---
 
@@ -101,9 +101,9 @@ For Azure docs information about the device mapping, see [How to configure the M
 
 ## Configure the Destination tab
 
-In order to configure the destination mapping tab, you can use the IoMT Connector Data Mapper tool to visualize, edit, and test the destination mapping. This open source tool is available from [IoMT Connector Data Mapper](https://github.com/microsoft/iomt-fhir/tree/master/tools/data-mapper). You need to configure destination mapping so that your instance of MedTech service can send and receive data to and from the FHIR service.
+In order to configure the **Destination** tab, you can use the [Mapping debugger](how-to-use-mapping-debugger.md) tool to create, edit, and test the FHIR destination mapping. You need to configure FHIR destination mapping so that your instance of MedTech service can send transformed device data to the FHIR service.
 
-To begin configuring destination mapping, go to the Create MedTech service page and select the **Destination mapping** tab. There are two parts of the tab you must fill out:
+To begin configuring FHIR destination mapping, go to the **Create** MedTech service page and select the **Destination mapping** tab. There are two parts of the tab you must fill out:
 
  1. Destination properties
  2. JSON template request
@@ -141,13 +141,13 @@ Under the **Destination** tab, use these values to enter the destination propert
 
 For more information regarding destination mapping, see the FHIR service GitHub documentation at [FHIR mapping](https://github.com/microsoft/iomt-fhir/blob/master/docs/Configuration.md#fhir-mapping).
 
-For Azure docs information about destination mapping, see [How to use FHIR destination mappings](how-to-configure-fhir-mappings.md).
+For Azure docs information about the FHIR destination mapping, see [Overview of the FHIR destination mapping](overview-of-fhir-destination-mapping.md).
 
 ### JSON template request
 
 Before you can complete the FHIR destination mapping, you must get a FHIR destination mapping code. Follow these four steps:
 
-1. Go to the [IoMT Connector Data Mapper Tool](https://github.com/microsoft/iomt-fhir/tree/master/tools/data-mapper) and get the JSON template for your FHIR destination. 
+1. Go to the [Mapping debugger](how-to-use-mapping-debugger.md) and get the JSON template for your FHIR destination. 
 1. Go back to the Destination tab of the Create MedTech service page. 
 1. Go to the large box below the boxes for FHIR server name, Destination name, and Resolution type. Enter the JSON template request in that box.
 1. You'll then receive the FHIR Destination mapping code, which will be saved as part of your configuration.

articles/healthcare-apis/iot/deploy-new-powershell-cli.md

@@ -6,7 +6,7 @@ ms.service: healthcare-apis
 ms.subservice: fhir
 ms.custom: devx-track-arm-template, devx-track-azurepowershell, devx-track-azurecli
 ms.topic: quickstart
-ms.date: 03/10/2023
+ms.date: 04/14/2023
 ms.author: jasteppe
 ---
 
@@ -185,9 +185,9 @@ When deployment is completed, the following resources and access roles are creat
 
 After you've successfully deployed an instance of the MedTech service, you'll still need to provide conforming and valid device and FHIR destination mappings.
 
- - To learn about the device mapping, see [How to configure the device mapping](how-to-configure-device-mappings.md).
+ - To learn about the device mapping, see [Overview of the MedTech service device mapping](overview-of-device-mapping.md).
 
- - To learn about the FHIR destination mapping, see [How to configure the FHIR destination mapping](how-to-configure-fhir-mappings.md).
+ - To learn about the FHIR destination mapping, see [Overview of the FHIR destination mapping](overview-of-fhir-destination-mapping.md).
 
 ## Clean up Azure PowerShell resources
 

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

@@ -53,9 +53,9 @@ The MedTech service buffers [FHIR Observations](https://www.hl7.org/fhir/observa
 |Potential issue|Fix|
 |---------------|---|
 |Data is still being processed.|Data is egressed to the FHIR service in batches (every ~five minutes). It’s possible the data is still being processed and extra time is needed for the data to be persisted in the FHIR service.|
-|Device mapping hasn't been configured.|Configure and save a conforming and valid [device mapping](how-to-configure-device-mappings.md).|
-|FHIR destination mapping hasn't been configured.|Configure and save a conforming and valid [FHIR destination mapping](how-to-configure-fhir-mappings.md).|
-|The device message doesn't contain an expected expression defined in the device mapping.|Verify the [JsonPath](https://goessner.net/articles/JsonPath/) or [JMESPath](https://jmespath.org/specification.html) expressions defined in the [device mapping](how-to-configure-device-mappings.md) match tokens defined in the device message.|
+|Device mapping hasn't been configured.|Configure and save a conforming and valid [device mapping](overview-of-device-mapping.md).|
+|FHIR destination mapping hasn't been configured.|Configure and save a conforming and valid [FHIR destination mapping](overview-of-fhir-destination-mapping.md).|
+|The device message doesn't contain an expected expression defined in the device mapping.|Verify the [JsonPath](https://goessner.net/articles/JsonPath/) or [JMESPath](https://jmespath.org/specification.html) expressions defined in the [device mapping](overview-of-device-mapping.md) match tokens defined in the device message.|
 |A Device resource hasn't been created in the FHIR service (**Resolution type**: **Lookup** only)*.|Create a valid [Device resource](https://www.hl7.org/fhir/device.html) in the FHIR service. Ensure the Device resource contains an identifier that matches the device identifier provided in the incoming message.|
 |A Patient resource hasn't been created in the FHIR service (**Resolution type**: **Lookup** only)*.|Create a valid [Patient resource](https://www.hl7.org/fhir/patient.html) in the FHIR service.|
 |The Device.patient reference isn't set, or the reference is invalid (**Resolution type**: **Lookup** only)*.|Make sure the Device resource contains a valid [reference](https://www.hl7.org/fhir/device-definitions.html#Device.patient) to a Patient resource.| 
@@ -94,7 +94,7 @@ For an overview of the MedTech service, see
 To learn about the MedTech service device message data transformation, see
 
 > [!div class="nextstepaction"]
-> [Understand the MedTech service device message processing stages](overview.md)
+> [Understand the MedTech service device data processing stages](overview-of-device-data-processing-stages.md)
 
 To learn about methods for deploying the MedTech service, see
 

articles/healthcare-apis/iot/get-started.md

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: quickstart
-ms.date: 04/04/2023
+ms.date: 04/14/2023
 ms.author: jasteppe
 ms.custom: mode-api
 ---
@@ -144,7 +144,7 @@ For more information on the MedTech service device data transformation, see [Ove
 
 ## Step 6: Verify the processed device data
 
-You can verify that the device data was processed correctly by checking to see if there's now a new Observation resource in the FHIR service. If the device data isn't mapped or if the mapping isn't authored properly, the device data will be skipped. If there are any problems, check the [device mapping](overview-of-device-mapping.md) or the [FHIR destination mapping](how-to-configure-fhir-mappings.md).
+You can verify that the device data was processed correctly by checking to see if there's now a new Observation resource in the FHIR service. If the device data isn't mapped or if the mapping isn't authored properly, the device data will be skipped. If there are any problems, check the [device mapping](overview-of-device-mapping.md) or the [FHIR destination mapping](overview-of-fhir-destination-mapping.md).
 
 ### Metrics
 

articles/healthcare-apis/iot/git-projects.md

@@ -5,7 +5,7 @@ services: healthcare-apis
 author: msjasteppe
 ms.service: healthcare-apis
 ms.topic: reference
-ms.date: 02/27/2023
+ms.date: 04/14/2023
 ms.author: jasteppe
 ---
 # Open-source projects
@@ -24,10 +24,6 @@ Check out our open-source projects on GitHub that provide source code and instru
 
 * [microsoft/iomt-fhir](https://github.com/microsoft/iomt-fhir): Open-source version of the Azure Health Data Services MedTech service managed service. Can be used with any FHIR service that supports [FHIR R4®](https://www.hl7.org/implement/standards/product_brief.cfm?product_id=491)
 
-### Device and FHIR destination mappings
-
-* [IoMT Connector Data Mapper](https://github.com/microsoft/iomt-fhir/tree/master/tools/data-mapper): Tool for editing, testing, and troubleshooting MedTech service device and FHIR destination mappings. Export mappings for uploading to the MedTech service in the Azure portal or use with the open-source version.
-
 ### Wearables integration
 
 Fitbit

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

@@ -81,7 +81,7 @@ CalculatedContent mappings allow matching on, and extracting values from, an Azu
 |`PatientIdExpression`|The expression to extract the patient identifier. *Required* when `IdentityResolution` is in `Create` mode, and *optional* when `IdentityResolution` is in `Lookup` mode.|`$.matchedToken.patientId`|
 |`EncounterIdExpression`|*Optional*: The expression to extract the encounter identifier.|`$.matchedToken.encounterId`|
 |`CorrelationIdExpression`|*Optional*: The expression to extract the correlation identifier. You can use this output to group values into a single observation in the FHIR destination mappings.|`$.matchedToken.correlationId`|
-|`Values[].ValueName`|The name to associate with the value that the next expression extracts. Used to bind the wanted value or component in the FHIR destination-mapping template.|`hr`|
+|`Values[].ValueName`|The name to associate with the value that the next expression extracts. Used to bind the wanted value or component in the FHIR destination mapping.|`hr`|
 |`Values[].ValueExpression`|The expression to extract the wanted value.|`$.matchedToken.heartRate`|
 |`Values[].Required`|Requires the value to be present in the payload. If the MedTech service doesn't find the value, it won't generate a measurement, and it will create an `InvalidOperationException` instance.|`true`|
 
@@ -101,7 +101,7 @@ When you're specifying the language to use for the expression, the following val
 
 ## Custom functions
 
-A set of custom functions for the MedTech service is also available. The MedTech service custom functions are outside the functions provided as part of the JMESPath specification. For more information on the MedTech service custom functions, see [How to use custom functions with device mappings](how-to-use-custom-functions.md).
+A set of custom functions for the MedTech service is also available. The MedTech service custom functions are outside the functions provided as part of the JMESPath specification. For more information on the MedTech service custom functions, see [How to use custom functions](how-to-use-custom-functions.md).
 
 ## Matched token
 
@@ -550,6 +550,6 @@ In this article, you learned how to configure MedTech service device mappings by
 To learn how to configure FHIR destination mappings, see:
 
 > [!div class="nextstepaction"]
-> [How to configure FHIR destination mappings](how-to-configure-fhir-mappings.md)
+> [Overview of the FHIR destination mapping](overview-of-fhir-destination-mapping.md)
 
 FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office, and is used with permission.

articles/healthcare-apis/iot/how-to-use-custom-functions.md

@@ -14,7 +14,7 @@ ms.author: jasteppe
 > [!NOTE]
 > [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
 
-Many functions are available when using **JMESPath** as the expression language. Besides the functions available as part of the JMESPath specification, many more custom functions may also be used. This article describes the MedTech service-specific custom functions for use with the MedTech service [device mapping](how-to-configure-device-mappings.md) during the device message [normalization](understand-service.md#normalize) process.
+Many functions are available when using **JMESPath** as the expression language. Besides the functions available as part of the JMESPath specification, many more custom functions may also be used. This article describes the MedTech service-specific custom functions for use with the MedTech service [device mapping](overview-of-device-mapping.md) during the device message [normalization](overview-of-device-data-processing-stages.md#normalize) process.
 
 > [!TIP]
 > For more information on JMESPath functions, see the [JMESPath specification](https://jmespath.org/specification.html#built-in-functions).
@@ -194,6 +194,6 @@ In this article, you learned how to use the MedTech service custom functions wit
 To learn how to configure the MedTech service device mappings, see
 
 > [!div class="nextstepaction"]
-> [How to configure device mappings](how-to-configure-device-mappings.md)
+> [Overview of the MedTech service device mapping](overview-of-device-mapping.md)
 
 FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.

articles/healthcare-apis/iot/how-to-use-iotjsonpathcontent-mappings.md

@@ -5,7 +5,7 @@ author: msjasteppe
 ms.service: healthcare-apis
 ms.subservice: fhir
 ms.topic: how-to
-ms.date: 04/13/2023
+ms.date: 04/14/2023
 ms.author: jasteppe
 ---
 
@@ -14,7 +14,7 @@ ms.author: jasteppe
 > [!NOTE]
 > [Fast Healthcare Interoperability Resources (FHIR®)](https://www.hl7.org/fhir/) is an open healthcare specification.
 
-This article describes how to use IoTJsonPathContent mappings with the MedTech service [device mappings](overview-of-device-mapping.md).
+This article describes how to use IoTJsonPathContent mappings with the MedTech service [device mapping](overview-of-device-mapping.md).
 
 ## IotJsonPathContent
 
@@ -61,7 +61,7 @@ With each of these examples, you're provided with:
 > [!NOTE]
 > The IoT Hub enriches the device message before sending it to the MedTech service device event hub with all properties starting with `iothub`. For example: `iothub-creation-time-utc`.
 >
-> `patientIdExpression` is only required for MedTech services in the **Create** mode, however, if **Lookup** is being used, a Device resource with a matching Device Identifier must exist in the FHIR service. These examples assume your MedTech service is in a **Create** mode. For more information on the **Create** and **Lookup** **Destination properties**, see [Configure Destination properties](deploy-05-new-config.md#destination-properties). 
+> `patientIdExpression` is only required for MedTech services in the **Create** mode, however, if **Lookup** is being used, a Device resource with a matching Device Identifier must exist in the FHIR service. These examples assume your MedTech service is in a **Create** mode. For more information on the **Create** and **Lookup** **Destination properties**, see [Configure Destination properties](deploy-new-config.md#destination-properties). 
 
 ```json
 
@@ -142,7 +142,7 @@ With each of these examples, you're provided with:
 > [!NOTE]
 > The IoT hyub enriches the device message before sending it to the MedTech service device event hub with all properties starting with `iothub`. For example: `iothub-creation-time-utc`.
 >
-> `patientIdExpression` is only required for MedTech services in the **Create** mode, however, if **Lookup** is being used, a Device resource with a matching Device Identifier must exist in the FHIR service. These examples assume your MedTech service is in a **Create** mode. For more information on the **Create** and **Lookup** **Destination properties**, see [Configure Destination properties](deploy-05-new-config.md#destination-properties).
+> `patientIdExpression` is only required for MedTech services in the **Create** mode, however, if **Lookup** is being used, a Device resource with a matching Device Identifier must exist in the FHIR service. These examples assume your MedTech service is in a **Create** mode. For more information on the **Create** and **Lookup** **Destination properties**, see [Configure Destination properties](deploy-new-config.md#destination-properties).
 
 ```json
 
@@ -277,6 +277,6 @@ In this article, you learned how to use IotJsonPathContent mappings with the Med
 To learn how to configure the MedTech service FHIR destination mapping, see
 
 > [!div class="nextstepaction"]
-> [How to configure FHIR destination mappings](how-to-configure-fhir-mappings.md)
+> [Overview of the FHIR destination mapping](overview-of-fhir-destination-mapping.md)
 
 FHIR® is a registered trademark of Health Level Seven International, registered in the U.S. Trademark Office and is used with their permission.