Merge branch 'troubleshooting' of https://github.com/msjasteppe/azure-docs-pr into troubleshooting

Author: msjasteppe

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

@@ -37,9 +37,9 @@ The MedTech service requires device and FHIR destination mappings to perform nor
 
 ## How long does it take for device message data to show up in the FHIR service?
 
-The MedTech service buffers the FHIR Observations resources created during the transformation stage and provides near real-time processing. However, it can potentially take up to five minutes for FHIR Observation resources to be persisted in the FHIR service. To learn how the MedTech service transforms device message data into FHIR Observations resources, see [Understand the MedTech service device message data transformation](understand-service.md).
+The MedTech service buffers FHIR Observation resources created during the transformation stage and provides near real-time processing. However, this buffer can potentially delay the persistence of FHIR Observations to the FHIR service up to five minutes. To learn how the MedTech service transforms device message data into FHIR Observations resources, see [Understand the MedTech service device message data transformation](understand-service.md).
 
-## Why is the MedTech service device message data not showing up in the FHIR service?
+## Why are the device messages added to the event hub not showing up as FHIR Observation resources in the FHIR service?
 
 > [!TIP]
 > Having access to MedTech service logs is essential for troubleshooting and assessing the overall health and performance of your MedTech service.
@@ -51,7 +51,7 @@ The MedTech service buffers the FHIR Observations resources created during the t
 |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 conforming and valid [device mapping](how-to-configure-device-mappings.md).|
 |FHIR destination mapping hasn't been configured.|Configure and save 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](how-to-configure-device-mappings.md).|Verify JsonPath expressions defined in the device mapping match tokens defined in the device message.|
+|The device message doesn't contain an expected expression defined in the [device mapping](how-to-configure-device-mappings.md).|Verify the [JsonPath](https://goessner.net/articles/JsonPath/) or [JMESPath](https://jmespath.org/specification.html) expressions defined in the device mapping 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.| 
@@ -60,7 +60,7 @@ The MedTech service buffers the FHIR Observations resources created during the t
 
 ## Does the MedTech service perform backups of device messages?
 
-No. The MedTech service doesn't back up the device messages that come into the customer's event hub. The customer controls the device message retention period within their event hub, which can be from one to seven days. If the device message data is successfully processed by the MedTech service, it's persisted in the FHIR service, and the FHIR service backup policy applies. 
+No. The MedTech service doesn't back up the device messages that is sent to the event hub. The event hub owner controls the device message retention period within their event hub, which can be from one to ninety days (Event hubs can be deployed in [3 different service tiers](https://learn.microsoft.com/en-us/azure/event-hubs/event-hubs-quotas?source=recommendations#basic-vs-standard-vs-premium-vs-dedicated-tiers). Message retention limits are tier dependent: Basic 1 day, Standard 1-7 days, Premium 90 days.). If the device message data is successfully processed by the MedTech service, it's persisted in the FHIR service, and the FHIR service backup policy applies. 
 
 To learn more about event hub message retention, see [What is the maximum retention period for events?](/azure/event-hubs/event-hubs-faq#what-is-the-maximum-retention-period-for-events-) 
 

articles/healthcare-apis/iot/troubleshoot-errors-deployment.md

@@ -90,7 +90,7 @@ Here's a list of errors that can be found in the Azure Resource Manager (ARM) AP
 
 |Error:|
 |------|
-|[The maximum number of resource type iotconnectors/destinations has been reached.](#the-maximum-number-of-resource-type-iotconnectorsdestinations-has-been-reached)|
+|[The maximum number of resource type iotconnectors/fhirdestinations has been reached.](#the-maximum-number-of-resource-type-iotconnectorsdestinations-has-been-reached)|
 |[The fhirServiceResourceId provided is invalid.](#the-fhirserviceresourceid-provided-is-invalid)|
 |[Ancestor resources must be fully provisioned before a child resource can be provisioned.](#ancestor-resources-must-be-fully-provisioned-before-a-child-resource-can-be-provisioned-1)
 |[The location property of child resources must match the location property of parent resources.](#the-location-property-of-child-resources-must-match-the-location-property-of-parent-resources-1)

articles/healthcare-apis/iot/troubleshoot-errors-logs.md

@@ -62,7 +62,7 @@ The health checks' names are listed in the following table, and the fixes for an
 
 ### CredentialStore:IsCustomerFacingMiCredentialBundlePresent
 
-**Description**: Checks if a MedTech service’s system-assigned managed identity exists and is enabled.
+**Description**: Checks if a MedTech service’s system-assigned managed identity has been enabled or if a user-assigned managed identity is configured.
 
 **Severity**: Blocking
 
@@ -135,7 +135,7 @@ The errors' names are listed in the following table, and the fixes for them are
 
 ### FhirResourceNotFoundException
 
-**Description**: This error occurs when a FHIR resource with the identifier given in the device message can't be found in the FHIR destination. If the FHIR resource’s type is Patient, then the error may be that the Device FHIR resource with the device identifier given in the device message doesn't reference a Patient FHIR resource. The FHIR resource’s type (for example, Device, Patient, Encounter, or Observation) is specified in the error message. **Note**: This error occurs when the MedTech service’s resolution type is set to **Lookup**.
+**Description**: This error occurs when a FHIR resource with the identifier given in the device message can't be found in the FHIR destination. If the FHIR resource’s type is Patient, then the error may be that the Device FHIR resource with the device identifier given in the device message doesn't reference a Patient FHIR resource. The FHIR resource’s type (for example, Device, Patient, Encounter, or Observation) is specified in the error message. **Note**: This error can only occur when the MedTech service’s resolution type is set to **Lookup**.
 
 **Severity**: Non-blocking
 
@@ -241,19 +241,19 @@ The template’s type and line with the error are specified in the error message
 
 **Severity**: Blocking
 
-**Fix**: Ensure that your device messages are in JSON format. Also, on the Azure portal, go to the **Device mapping** blade of your MedTech service, and fix any validation errors that are shown when editing and saving the device mapping.
+**Fix**: On the Azure portal, go to the **Device mapping** blade of your MedTech service, and fix any validation errors that are shown when editing and saving the device mapping.
 
 ### PatientDeviceMismatchException
 
-**Description**: A Device FHIR resource in the FHIR destination references a Patient FHIR resource with an identifier that doesn’t match the patient identifier given in the device message (meaning, the device is linked to another patient).
+**Description**: A FHIR Device resource in the FHIR destination references a Patient FHIR resource with an identifier that doesn’t match the patient identifier given in the device message (meaning, the device is linked to another patient).
 
 **Severity**: Non-blocking
 
 **Fix**: Ensure that a patient identifier isn't assigned to more than one device.
 
 ### ResourceIdentityNotDefinedException
 
-**Description**: This error occurs when the FHIR resource’s identifier isn’t present in a device message, or when the expression to parse the FHIR resource’s identifier from the device message isn’t configured in the device mapping. The FHIR resource’s type (for example, Device, Patient, Encounter, or Observation) is specified in the error message. **Note**: This error occurs when the MedTech service’s resolution type is set to **Create**.
+**Description**: This error occurs when the FHIR resource’s identifier isn’t present in a device message, or when the expression to parse the FHIR resource’s identifier from the device message isn’t configured in the device mapping. The FHIR resource’s type (for example, Device, Patient, Encounter, or Observation) is specified in the error message. **Note**: This error can only occur when the MedTech service’s resolution type is set to **Create**.
 
 **Severity**: Non-blocking