Skip to content

Commit 85ce214

Browse files
committed
More edits
1 parent 80e7e9e commit 85ce214

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/healthcare-apis/iot/device-messages-through-iot-hub.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,7 @@ When deployment is completed, the following resources and access roles are creat
137137

138138
- For the FHIR service, the FHIR Data Writer role is assigned in the [Access control section (IAM)](../../role-based-access-control/overview.md) of the FHIR service.
139139

140-
- Conforming and valid MedTech service [device](how-to-configure-device-mappings.md) and [FHIR destination mappings](how-to-configure-fhir-mappings.md).
140+
- Conforming and valid MedTech service [device](overview-of-device-mapping.md) and [FHIR destination mappings](how-to-configure-fhir-mappings.md). **Resolution type** is set to **Create**.
141141

142142
> [!IMPORTANT]
143143
> In this tutorial, the ARM template configures the MedTech service to operate in **Create** mode. A Patient resource and a Device resource are created for each device that sends data to your FHIR service.
@@ -235,7 +235,7 @@ You complete the steps by using Visual Studio Code with the Azure IoT Hub extens
235235
> }
236236
> ```
237237
>
238-
> `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. This example assumes your MedTech service is in a **Create** mode. For more information on the **Destination properties**: **Create** and **Lookup**, see [Configure Destination properties](deploy-05-new-config.md#destination-properties).
238+
> `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. This example assumes your MedTech service is in a **Create** mode. For more information on the **Destination properties**: **Create** and **Lookup**, see [Configure Destination properties](deploy-05-new-config.md#des). The **Resolution type** for this tutorial set to **Create**.
239239

240240
## Review metrics from the test message
241241

0 commit comments

Comments
 (0)