Skip to content

Commit 792a086

Browse files
msjasteppenamalu
andauthored
Update articles/healthcare-apis/iot/frequently-asked-questions.md
Co-authored-by: namalu <[email protected]>
1 parent a7db23e commit 792a086

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -60,7 +60,7 @@ The MedTech service buffers FHIR Observation resources created during the transf
6060

6161
## Does the MedTech service perform backups of device messages?
6262

63-
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.
63+
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.
6464

6565
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-)
6666

0 commit comments

Comments
 (0)